Should we start the http web server first before starting the websphere application server? Or the other way?

If we have http web server, websphere application server - database server configuration.

I suggest starting the HTTPd last and shutting it down first. If you start the HTTPd before the WAS, it might get requests that cannot be served yet because the WAS is unreachable.

----- For starting, start database server first, and then websphere, and then http web server.

----- For stopping, stop http web server first, then websphere, and then database server.

http://httpd.apache.org/docs/2.2/stopping.html

http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&ved=0CC8QFjAC&url=ftp%3A%2F%2Fftp.software.ibm.com%2Fsoftware%2Fwebserver%2Fhttpservers%2Flibrary%2FInstallGuide_en_v60.pdf&ei=AzXNTvvcApSnsQLs87EV&usg=AFQjCNFK95AlOJ4GRiQqR0ZQO5AdRbJltQ&sig2=IWrn0VHzGSRP3QdRCLEaSQ

Starting and stopping IBM HTTP Server
You can use the WebSphere administrative console to start and stop IBM HTTP Server. You can also use
commands.

See the following topics for more information:
Starting and stopping IBM HTTP Server with the WebSphere administrative console Use the
WebSphere administrative console to start and stop IBM HTTP Server.

1. Launch the WebSphere administrative console.
2. Click Servers > Web servers.
3. Select your server by clicking the check box.
4. Click Start.
You can stop IBM HTTP Server by clicking Stop.

Starting IBM HTTP Server on Linux and UNIX platforms
This section provides information on getting started with IBM HTTP Server on Linux and UNIX
platforms.

Installing IBM HTTP Server
3
The apachectl command is used to start and stop IBM HTTP Server. The apachectl command is
located in the bin subdirectory within the IBM HTTP Server installation directory. If that directory is not in your PATH, the full path should be given on the command line.

– Starting/Stopping IBM HTTP Server – use the default httpd.conf configuration file to run the apachectl command.

Issue the commands from the default directories, based on your operating system:
–
/usr/IBMIHS/bin/apachectl start|stop
–
/opt/IBMIHS/bin/apachectl start|stop
To start IBM HTTP Server using an alternate configuration file, run the apachectl -k start -f
path_to_configuration_file command . To stop IBM HTTP Server using an alternate configuration file,
run the apachectl -k stop -f path_to_configuration_file command.

Example:
# /usr/IBMIHS/bin/apachectl start
# /usr/IBMIHS/bin/apachectl stop
The apachectl command is not in your PATH, the IBM HTTP Server installation directory is
/opt/IBMIHS, and an alternate configuration file, /opt/IBMIHS/conf/nodeb.conf, is used as follows:
# /opt/IBMIHS/bin/apachectl -k start -f /opt/IBMIHS/conf/nodeb.conf
# /opt/IBMIHS/bin/apachectl -k stop -f /opt/IBMIHS/conf/nodeb.conf

To confirm that IBM HTTP Server started successfully, open a browser and type in your server name in
the URL box. If the IBM HTTP Server started successfully, you can configure your server for SSL, LDAP and FRCA.

Starting IBM HTTP Server on Windows operating systems
This section provides information on getting started with IBM HTTP Server on Windows operating
systems.
To start IBM HTTP Server as a Windows service:
1. Click Start > Programs > IBM HTTP Server 6.0 > Start Server. A message box is displayed that
indicates the server has started.
2. To confirm that IBM HTTP Server started successfully, open a browser and type your server name
in the URL box.

If you use the developer installation option, then the IBM HTTP Server does not install as a service.
Run the apache.exe command from a command line, instead.

If IBM HTTP Server does not start:
1. Go to Services in the Control Panel.
2. Double-click IBM HTTP Server 6.0 to start the server.
3. To confirm that IBM HTTP Server started successfully, open a browser and type your server name
in the URL box.

If IBM HTTP Server started successfully, you can configure your server for SSL, LDAP and FRCA .