WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

444 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

Figure 12-27 Web server status

WebSphere Application Server reports server status using the web server host name and

port that you defined. This is normally port 80. Do not use the remote administration port. If

Use secure protocol is defined, SSL is used. See Figure 12-28 on page 446.

12.4.3 Starting and stopping a web server

You can start or stop a web server using either the administrative console or a command

window.

From the administrative console

You can start or stop the following web servers from the WebSphere administrative console:

 All web servers on a managed node

The node agent is used to start or stop the web server.

 IBM HTTP Server on an unmanaged node

The IBM HTTP Server administration must be running on the web server node.

To start or stop a web server from the administrative console:

1. Click Servers  Web servers.

2. Select the check box to the left of each web server that you want to start or stop.

3. Click Start or Stop.

If you have problems starting or stopping an IBM HTTP Server, check the WebSphere

console logs (trace) and, if using the IBM HTTP administration server, check the

admin_error.log file.

If you have problems starting and stopping IBM HTTP Server on a managed node using the

node agent, you can try to start and stop the server by setting up the managed profile. After

setting up the profile, issue the startserver <IBM HTTP Server> -nowait -trace command

and check the startServer.log file for the IBM HTTP Server specified.

From a command window

You can also use the native startup or shutdown procedures for the supported web server.

From a command window, change to the directory of your IBM HTTP Server installed image

or to the installed image of a supported web server.

Chapter 12. Configuring and managing web servers 445

You can use one of the following two ways to start or stop the web server:

 To start or stop the IBM HTTP Server for UNIX platforms, enter one of the following

commands at a command prompt:

– # <ihs_install>/bin/apachectl start

– # <ihs_install>/bin/apachectl stop

 To start or stop the IBM HTTP Server on a Windows platform, select the IBM HTTP

Server 8.0 service from the Services window, and invoke the appropriate action.

12.4.4 IBM HTTP Server remote administration

You can administer and configure IBM HTTP Server V8.0 using the WebSphere

administrative console. On a managed node, administration is performed using the node

agent. This is true of all web server types. However, unlike other web servers, administration

is possible for an IBM HTTP Server installed on an unmanaged node. In this case,

administration is done through the IBM HTTP administration server. This server must be

configured and running. Administration is limited to generation and propagation of the plug-in

configuration file.

Remote administration set up

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 window of the

administrative console. Complete the following steps to set or change these properties:

1. Click Servers  Web servers.

2. Select the name of the web server.

3. In the Additional Properties section, click Remote Web server management.

4. Enter the remote web server management information, as shown in Figure 12-28 on

page 446.

Note: When the web server is started or stopped with the native methods, the web

server status on the web servers page of the administrative console is updated

accordingly.