http and service guard

[mmartini]

Hello...

i have a service guard 2 node cluster. This cluster runs 3 oracle dbs , (A package for every db), the dbs are configured to use 1 web server... which is the best way to start this server? I need to start it at boot time? It would be better to configure a web server for every db?
thank you very much

[A. Clay Stephenson]

Bear in mind that only 1 process can bind and listen on a given port (port 80, by default, fot http) so if you want clients to connect using port 80 then the httpd daemon should be started and stopped using an /sbin/rcN.d script and the packages supply data for this httpd daemon. If you want to dedicate an httpd daemon for each package then the package should start and stop httpd BUT this approach requires that you choose another port AND the clients will have to specify a port when they attempt to connect.

e.g. http:\\pkgname1.mickey.mouse.com:2501

to connect to port 2501.

[Geoff Wild]

Again this depends....

What happens if the Web server is down?

I would configure an Apache (or what have you) web server to be a package in the cluster - that way if you lose a node, it will automatically fail over.

Rgds...Geoff

[Doug O'Leary]

Hey;

To add my $.02 to G.Wild; I think you need to create a package for your web server. That way, if the node dies the dbs *and* the web server will fail over to the other node.

You'll have to do some magic with the httpd.conf file (assuming apache) to set the server name to the name that's assigned to the relocatable IP.

Having the web server as another package will give you much greater fault tolerance than you'll otherwise have.

The other option would be to run the web server on each node of the cluster; however, if the primary node fails, your users will have to manually connect to the adoptive node's web server.

Doug

[Steven E. Protter]

Shalom,

You don't have to use the httpd server that comes with Oracle at all. It is designed to provide a "gui" front end to let you more easily check database health and perhaps in later versions start and stop the database.

If you wish to use this crutch instead of learn how to check your database health on the command line, then I suggest you start the httpd server in the same serviceguard package that starts the database. That way the httpd server that monitors the database will be accessible from the floating IP address of your cluster.

SEP