InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.22: Administering server groups (overview)

6.6.22: Administering server groups (overview)

Administrators can manage clones efficiently by managing the server group on which they are based:

After cloning an application server, modifying the application server group (model) automatically propagates the same changes to all of the application server clones. It is recommended that the administrator convert the original application server into one of the clones.

  Note that if an application server is used as a base to create a server group, its modules will be taken away from it, and put into server group context. Do not be alarmed if the modules seem to be missing from the original application server!

Properties of server groups and clones

The properties of server groups and clones are of two main types:

  • Properties matching the properties of the original application server
  • Properties that uniquely identify the server group or clone

The majority of a server group or clone's properties match those of the original application server. However, the server group or clone will have a unique name and location.

Server group and clone modifications

It is important to remember that to perform an administrative action on a clone, such as modifying the clone's properties, the administrator must perform the action on the associated server group instead.

For example, to add or remove a bean from an application server, the administrator adds or removes the bean from the server group container within the server group application server. With one action, the administrator can add or remove the bean from all clones of the application server.

Some properties must be set at each clone. For example, the port used for transport must be unique for all clones on a given machine.

Go to previous article: Analyzing resources with the Java administrative console Go to next article: Server group properties

 

 
Go to previous article: Analyzing resources with the Java administrative console Go to next article: Server group properties