Unable to manage a Web server

WebSphere Application Server V6 has the ability to manage the IBM HTTP Server V6 from within the administrative console.

You are having problems starting, stopping, or getting the status of the Web server.

àData to collect:

The following logs can be helpful in determining why you cannot mange a Web   server

. Deployment manager logs
. Node agent logs
. Web server logs

àWhat to look for:

You can start and stop any of the supported Web servers using the WebSphere administrative console. The Web server must be installed on a managed node. A WebSphere Application Server node agent executes the appropriate start or stop command.

When you are using IBM HTTP Server V6.0, you do not need to install the Web server on a managed node because administration can be performed through the IBM HTTP Administration Server. In addition to starting and stopping the IBM HTTP Server V6.0, you can also manage its configuration file and view the Web server logs.

 

IBM HTTP Server on an unmanaged node

If you cannot administer the IBM HTTP Server from the WebSphere administrative console, verify that the IBM HTTP Server administration server has been properly set up.

In order for the administrative console to access the IBM HTTP administration server, you must define a valid user ID and password to access the IBM HTTP Server administration server. The user ID and password are stored in the Web server’s IBM HTTP Server administration server properties.

You can update your IBM HTTP Server administration server properties in the Web server definition through the Remote Web server management properties page of the administrative console. To set or change these properties, do the following:

1. Click Servers àWeb servers.
2. Select the Web server.
3. Click Remote Web server management in the Additional Properties section.
4. Ensure that the user ID and password are correct by entering values that are defined to the IBM HTTP administration server.
5. Click OK and save the configuration.

——————————————————————————————————–

Setting the user ID and password in the IBM HTTP administration server:
The IBM HTTP administration server is set, by default, to look at the following
file to get the user ID and passwords to use for authentication:
<ihs_install>/conf/admin.passwd

To initialize this file with a user ID, use the htpasswd command. The following
example initializes the file with the user ID webadmin:
C:\IBM HTTP Server\bin>htpasswd “C:\IBM HTTP Server\conf\admin.passwd”   webadmin
Automatically using MD5 format.
New password: ******
Re-type new password: ******
Adding password for user webadmin

When you are managing an IBM HTTP Server using the WebSphere administrative console, you must ensure that the following conditions are met:

àVerify that the IBM HTTP Server administration server is running.

àVerify that the Web server host name and port that are defined in the WebSphere administrative console match the IBM HTTP Server administration host name and port.

àVerify that the firewall is not preventing you from accessing the IBM HTTP Server administration server from the WebSphere administrative console.

àIf you are trying to administer the IBM HTTP Server over a secure SSL connection, verify that you have exported the IBM HTTP Server administration server key database personal certificate and imported it into the WebSphere key database as a signer certificate. The key database will be identified in the com.ibm.ssl.trustStore parameter in the sas.client.props file.

àVerify the IBM HTTP Server admin_error.log file and the WebSphere Application Server logs (trace.log) do not contain any errors.