In WebSphere® Application Server,
the Attached Documents action uses the IBM® HTTP
Server to display attached documents. You must edit the httpd.conf
file to specify the root of the \doclinks folder to be the home directory
of WebSphere Application Server.
Procedure
- Go to the location of the httpd.conf file for the IBM HTTP Server. The default installation
location depends on your operating system:
Operating system |
Path |
Windows |
C:\IBM HTTP Server\conf\httpd.conf |
UNIX |
/home/IBMHTTPD/conf/httpd.conf |
- Back up the httpd.conf file.
- Open the httpd.conf file in a text editor. Find the section
that begins with the following line:
# This should
be changed to whatever you set DocumentRoot to.
- Change the Directory line you located in the previous step
to specify the doclinks directory that you created:
Operating system |
Directory line |
Windows |
<Directory C:\doclinks> |
UNIX |
<Directory /home/doclinks> |
- Find the section that begins with the following lines:
#
# Document Root: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
- Edit the DocumentRoot line to specify the doclinks directory
that you created:
Operating system |
Directory line |
Windows |
DocumentRoot C:\doclinks |
UNIX |
DocumentRoot /home/doclinks |
- Save and close the file.
- Restart the HTTP server.
- To verify that the HTTP server is configured correctly,
complete the following steps:
- Perform one of the following steps:
- For Windows, create a
test file, test.txt, at this location:
C:\doclinks\test.txt
- For UNIX, create a test
file, named test.txt, in the doclinks folder.
/home/doclinks/test.txt
- Open a browser session and type the following address:
http://<server_name or ip address>/test.txt
For
example:
http://localhost/test.txt
You can see your test.txt document in this window.
If you cannot open the file, you must reconfigure the IBM HTTP Server. To reconfigure the IBM HTTP Server, repeat all the preceding steps.
- Restart WebSphere Application Server and
the system.