InfoCenter Home >
7: Multimachine management >
7.2 Managing workloads >
7.2.4 Using models and clones >
7.2.4.2 Modifying models and clones

7.2.4.2 Modifying models and clones

To perform an administrative action on a clone (such as modifying the clone's properties), perform the action on the associated model. For example, to add an enterprise bean to an application server clone, you must add the bean to the server group. With one action, you can add an enterprise bean to all clones of the application server.

Changes related to workload management (such as selection policy changes, starting clones, and stopping clones) are propagated to workload management clients. Other model changes (such as adding or removing enterprise beans from an application server) are picked up by the clones when they are restarted. System administrators can perform a ripple restart to propagate changes by stopping and restarting clones one after another without stopping the model.

If you modify a clone directly (instead of through its model), the clone no longer is identical to its model. However, it continues to be part of its model unless it is dissociated from the model.

Freestanding (disassociated) clones

A clone must be explicitly disassociated from its model. It then becomes a freestanding object and can be administered independently. Any changes you make to the former model of the clone are not propagated to the clone.

Freestanding clones can be created by using the wscp command-line utility.

Go to previous article: Cloning for workload management, failover, and scaling Go to next article: Advice for cloning

 

 
Go to previous article: Cloning for workload management, failover, and scaling Go to next article: Advice for cloning