InfoCenter Home >
7: Multimachine management >
7.2 Managing workloads >
7.2.4 Using server groups and clones >
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 server group.
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.
- In most cases, if you make changes to a server group, its clones and its clients do not
need to be restarted. The changes are eventually propagated to them. However, in
some cases you need to stop and restart the server group's clones, for example, if you
change the server group's selection policy.
- You can make changes to a server group while it is 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.
|
Related topics |
|
| Home (Getting started page) |
|
Peer topics |
|
| 7.2.4.1 Cloning for workload management, failover, and scaling |
|
| 7.2.4.2 Modifying server groups and clones |
|
| 7.2.4.4 Containment relationships |
|
| 7.2.4.5 Server selection policies and transaction affinity |
|
| 7.2.4.6 Security for cloned resources |
|
| 7.2.4.7: Creating clones on machines with different WebSphere installation directories or operating systems |
|
InfoCenter |
|
To launch the full documentation set in a separate browser window, click: |
| Display InfoCenter |
| |
PDF library |
|
To browse the PDF library for this product, containing this article and others, click: |
| PDF versions |
| |
Using this documentation |
|
Become an InfoCenter super user! To find out more about navigation, numbering, search, downloads, and more, click: |
| Using this documentation |
| |
|