InfoCenter Home >
7: Multimachine management >
7.2 Managing workloads >
7.2.4 Using models and clones >
7.2.4.3 Advice for cloning

7.2.4.3 Advice for cloning

Create clones based on your knowledge of the application and on the expected workload. Some considerations:

  • Clones do not need to reside on the same machine.
  • Clients can have inconsistent views of configuration information in the model. This can occur when an application server instance is stopped, started, added, or deleted. The period of inconsistency is short-lived, however. Clients eventually refresh their caches of server information. Application server instances that are unchanged during the period of inconsistency remain available.
  • If you make changes to a model, clients do not need to be restarted. The changes are eventually propagated to them.
  • You can make changes to a model while application servers are running. However, incremental changes (such as adding or removing one or two clones) have less impact on client performance than wholesale changes.
  • It is always best to make changes when few clients and application servers are running.
  • You can add or remove server clones later in response to the load on the application. Alternattively, you can clone the initial number of application server instances based on expected load.
  • If a machine becomes unavailable, you do not need to reconfigure the clones of other application servers to compensate for any unavailable application servers on that machine. However, if the machine is going to be unavailable for an extended period, you can reconfigure the other servers to optimize performance.
Go to previous article: Modifying models and clones Go to next article: Containment relationships

 

 
Go to previous article: Modifying models and clones Go to next article: Containment relationships