InfoCenter Home >
7: Multimachine management >
7.2 Managing workloads >
7.2.4 Using models and clones >
7.2.4.7: Creating clones on machines with different WebSphere installation directories or operating systems

7.2.4.7: Creating clones on machines with different WebSphere installation directories or operating systems

Different hardware and operating system platforms do not usually have the same WebSphere Application server product installation root directories. The following steps are required to create clones on multiple machines when WebSphere Application Server is installed in different directories on different machines or when different directory structures exist across multiple platforms:

  1. On one node, create a model of the application server to be cloned. The platform does not matter if all machines share the same administrative repository database.
  2. Make the original application server instance a clone and recursively model all instances under the application server. If you are creating a model of the default application server, make sure that it is not already installed on the machines that it will be cloned to.
  3. For all other nodes in the configuration:
    1. Create a clone on the machine. 
    2. If desired, copy the application files (the files containing servlet, enterprise bean, JavaServer Pages, and HTML code) to the machine.
    3. Modify the following properties of the clone.  The directory structures of these fields must be changed to match the directory structure of the product_ installation_root directory and the Web application file locations on the machine where the clone is running.
      • The Standard Output field of cloned application servers
      • The Standard Error field of cloned application servers
      • The JAR File field of cloned enterprise beans
      • The Document Root field of cloned web applications
      • The Classpath table of cloned web applications

      These changes do not make the clones freestanding.

    4. Start the cloned application server.

    Repeat these steps for each machine in the configuration. Changes made to individual clones are not propagated to the other clones in the system.

Inform.gif (183 bytes)   Modifying the model can overwrite these changes, requiring you to redo them.

Go to previous article: Security for cloned resources Go to next article: Using workload management - a sample procedure

 

 
Go to previous article: Security for cloned resources Go to next article: Using workload management - a sample procedure