To set up Cosminexus HTTP Server for server cluster, follow the steps below:
Note the following points when configuring environments.
As a result of a failover, the server name returned to the client might change. Therefore, be sure to set the ServerName directive on virtual hosts.
Instead of an IP address specified in the LAN card (which is not portable to another node), use a relocatable IP address (which is assigned to a resource module, and is portable to another node) for the directives that need an IP address to be specified (<VirtualHost>, BindAddress, Listen, and NameVirtualHost.)
Before starting the server cluster, run httpsd -t in the directory where it is installed to make sure that the server settings are correct. If resources belonging to the services or applications in the cluster (such as an IP address or memory space) are referenced in the Cosminexus HTTP Server configuration file, move the services and applications to the node you are checking, and then run httpsd -t.
You can change the settings of Cosminexus HTTP Server without placing offline the services being used by the server cluster, by restarting the Cosminexus HTTP Server services with the httpsd command or from the start menu, in the node on which the services are running online. Your changes to the configuration files need to be applied to the other nodes as well
In the standby node, you need to set the same type of CRL as the one being used for the primary node.
When you specify Cosminexus HTTP Server in the resources, specify it by universal services rather than by universal applications. Cosminexus HTTP Server does not work properly as a universal application.