Single server tags as the name suggests are used for defining single server instances which are not clustered. Single server tags can be used to define AdminServer, ProxyServer, PortalServer.
Single server tags
Single server tag can be specified as follows:
Single server tag has a name attribute that is the unique name for the server.
For Admin server: adminServer
For Proxy server: proxyServer
For Portal server: portalServer
It also has the elements <address>, <jndi-port>, and <http-port> for the IP address/host name and the port on which the server listens.
Important: adminServer, ejbServer, and portalServer should be valid active server instances that should already exist before starting the cluster setup.
While defining the cluster configuration file, ensure that the order of tags in the file oebps-cluster.xml is the same as defined in the file oebps-cluster.dtd. The order of the elements as defined in the DTD file is as follows:
If the sequence is not the same as defined in the DTD file, then while starting the cluster setup, the following exception is displayed:
java.io.IOException: IO error: The content of element type "cluster-configuration" must match (domain-name?, protocol?, synchronize-time?, authentication?, multicast?, persistence?, cluster+, adminserver?, proxyserver?, documentserver?, ejbserver?,portalserver?, jmsserver?, deploy?)"
Single server tag has a name attribute that is the unique name for the server.