On the new node, mount the existing Middleware home, which should include the To attach ORACLE_HOME in shared storage to the local Oracle Inventory, execute Log in to the Oracle WebLogic Administration Console. Assign the host name or IP to use for the ne

Managing the Topology 12-13 ■ The new node can access the existing home directories for WebLogic Server and Fusion Middleware. Use the existing installations in shared storage for creating a new managed server. You do not need to install WebLogic Server or Fusion Middleware binaries in a new location, but you do need to run pack and unpack to bootstrap the domain configuration in the new node. ■ When an ORACLE_HOME or WL_HOME is shared by multiple servers in different nodes, it is recommended that you keep the Oracle Inventory and Middleware home list in those nodes updated for consistency in the installations and application of patches. To update the oraInventory in a node and attach an installation in a shared storage to it, use ORACLE_HOMEouibin attachHome.sh. To update the Middleware home list to add or remove a WL_ HOME, edit the User_Homebeabeahomelist file. See the steps below. ■ The new server can use a new individual domain directory or, if the other managed servers domain directories reside on shared storage, reuse the domain directories on those servers.

12.6.2.1 Scale-out Procedure for Oracle IPM

Perform these steps to scale out the Oracle IPM servers in the topology:

1. On the new node, mount the existing Middleware home, which should include the

ECM installation and optionally, if the domain directory for managed servers in other nodes resides on shared storage the domain directory, and ensure that the new node has access to this directory, just like the rest of the nodes in the domain.

2. To attach ORACLE_HOME in shared storage to the local Oracle Inventory, execute

the following command: ECMHOSTn cd ORACLE_COMMON_HOMEouibin ECMHOSTn .attachHome.sh -jreLoc ORACLE_BASEproductfmwjrockit_160_version To update the Middleware home list, create or edit, if another WebLogic installation exists in the node the MW_HOMEbeabeahomelist file and add ORACLE_BASEproductfmw to it.

3. Log in to the Oracle WebLogic Administration Console.

4. Create a new machine for the new node that will be used, and add the machine to the domain. 5. Update the machines Node Manager address to map the IP of the node that is being used for scale-out. 6. Use the Oracle WebLogic Server Administration Console to clone WLS_IPM1 into a new managed server. Name it WLS_IPMn, where n is a number.

7. Assign the host name or IP to use for the new managed server for the listen

address of the managed server. If you are planning to use server migration for this server which Oracle recommends, this should be the VIP also called a floating IP for the server. This VIP should be different from the one used for the existing managed server. Note: These steps assume that you are adding a new server to node n, where no managed server was running previously. 12-14 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite Also, assign the newly created server to the machine you added in the step 4. Without this, the machine name of the cloned server will remain. 8. Create a JMS server for IPM on the new managed server: a. Use the Oracle WebLogic Server Administration Console to first create a new persistent store for the new IPMJMSServer which will be created in a later step and name it, for example, IPMJMSFileStore_N. Specify the path for the store as recommended in Section 2.3, Shared Storage and Recommended Directory Structure as the directory for the JMS persistent stores: ORACLE_BASE admindomain_namecluster_namejms b. Create a new JMS server for IPM; for example, IPMJMSServer_N. Use the IPMJMSFileStore_N created above for this JMS server. Target the IPMJMSServer_N server to the recently created managed server WLS_IPMn. 9. Run the pack command on SOAHOST1 to create a template pack: SOAHOST1 cd ORACLE_COMMON_HOMEcommonbin SOAHOST1 .pack.sh -managed=true -domain=ORACLE_BASEadmindomain_name aserverdomain_name -template=edgdomaintemplateScale.jar -template_ name=edgdomain_templateScale

10. Run the following command on SOAHOST1 to copy the created template file to