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

6.6.22: Administering cloned applications (overview)

Model and clone configurations provide information about copies of application servers. Administrators can manage clones efficiently by managing the model on which they are based:

After cloning an application server, modifying the application server 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.

Properties of models and clones

The properties of models and clones are of two main types:

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

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

Model 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 model instead.

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

  If you change a property in a clone and later change the same property in the model associated with the clone, the change you made directly to the clone could be overwritten when you modify the model (the situations in which it would and would not be overwritten are too complex to explain in this documentation). It is best to avoid modifying a clone directly.

Go to previous article: Viewing transactions and forcing outcomes with the Java administrative console Go to next article: Model and clone properties

 

 
Go to previous article: Viewing transactions and forcing outcomes with the Java administrative console Go to next article: Model and clone properties