InfoCenter Home > 6.6.22.1.1: Specifying server groups with the Java administrative consoleA server group is a template for creating additional, nearly identical copies of an administrative resource and its contents. The administrative resource is usually an application server. To create a server group, click Console -> Wizards -> Create Server Group from the console menu bar. This leads to the Create Server Group task wizard. Note, this article also contains some steps you need to do after completing the wizard. Using the Create Server Group wizardYou use a Create Server Group wizard to define a new server group or to define one based on an existing server. The wizard enables you to set values for some server group properties. To view or change all properties, use the server group properties dialog.
Identifying your server groupOn the Specifying Server Group Properties panel:
Specifying services used by your server groupOn the Enabling Services panel is a list of services available to your server group. To view or change the property values for a service, select the service, click Edit Service Properties, and change the property values as needed. Then, click Next. Using application servers as clones in your server groupOn the Creating Application Servers as Clones panel:
Completing the server group wizardThe Completing the Create Server Group Wizard panel lists the server group name and the names of any clones. If you do not want to change the values specified, click Finish. The wizard will create a new server group, and display a message indicating whether the server group was successful created. If the wizard encounters an error, a message will display explaining why a server group could not be created. To change the values specified, click Back to return to the appropriate panel(s), make any needed changes, and then click Finish on this panel. Copying the application installation directories to other nodesAs it is completing, the wizard instructs you to "Copy the install directory of each enterprise application to the $WAS_HOME/installedApps directory of all the other nodes." The following scenario illustrates how to do this step, which is only necessary if the server group spans multiple nodes (it could be that all of the servers in the group reside on the same administrative node). Suppose you have created a server group based on Application_Server_A on Administrative_Node_A. Application_Server_A contains the enterprise application called My_Application. The server group is comprised of two servers: Application_Server_A and another Application_Server_B on a remote administrative node called Administrative_Node_B. (All of these names are the logical names by which the resources are displayed and administered in the administrative console tree view). $WAS_HOME refers to the product_installation_root. In such a scenario, you would do the following:
Repeat the steps for each administrative node that contains a server in the server group. For this scenario involving only Administrative_Node_A and Administrative_Node_B, no repetitions are required. Ensuring each server has a unique port number for its HTTP transportAn important step remains after you finish the wizard. Each server in a server group must have a unique port specified for the HTTP transport of its Web container. Furthermore, the port must have a corresponding virtual host alias. For each server in the server group:
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|