Click Lock Edit and then select the managed server that you want to clone Click Clone. In the Domain Structure window, expand the Services node and then click the Click Lock Edit. Click New, and then Create FileStore. The Create a New File Store page

Managing the Topology 12-5

12.6.1 Scaling Up the Topology Adding Managed Servers to Existing Nodes

When scaling up the topology, you already have a node that runs a managed server that is configured with the necessary components. The node contains a WebLogic Server home and an Oracle Fusion Middleware home in shared storage. Use these existing installations such as WebLogic Server home, Oracle Fusion Middleware home, and domain directories when you create the new managed servers. You do not need to install WebLogic Server binaries at a new location or to run pack and unpack.

12.6.1.1 Scale-up Procedure for Oracle IPM

Perform these steps to scale up the topology for Oracle IPM: 1. Using the Oracle WebLogic Server Administration Console, clone WLS_IPM1 to a new managed server. The source managed server to clone should be one that already exists on the node where you want to run the new managed server. Perform these steps to clone a managed server: a. In the Domain Structure window of the Oracle WebLogic Server Administration Console, expand the Environment node and then Servers. The Summary of Servers page opens.

b. Click Lock Edit and then select the managed server that you want to clone

WLS_IPM1.

c. Click Clone.

d. Name the new managed server WLS_IPMn, where n is a number that identifies the new managed server. 2. For the listen address, assign the host name or IP to use for this new managed server. If you are planning to use server migration for this server which Oracle recommends, this should be the virtual host name for the server. This virtual host name should be different from the one used for the existing managed server. 3. Configure a JMS persistence store and JMS servers for Oracle IPM JMS. Configure the location for the JMS persistence stores as a directory that is visible from both nodes. By default, the JMS servers used by Oracle IPM are configured with no persistent store and use WebLogic Servers store ORACLE_BASEadmin domain_namemserverdomain_nameserversserver_namedatastoredefault. You must change Oracle IPMs JMS server persistent store to use a shared base directory as follows: a. Log in to the Oracle WebLogic Server Administration Console. Note: The remainder of the steps assume that you are adding a new server to ECMHOST1, which is already running WLS_IPM1. Note: You must enable a VIP on ECMHOST1 say, ECMHOST1VHN2, and you must also correctly resolve the host names in the network system used by the topology either by DNS server or host resolution. To enable the VIPs, follow the example described in Section 6.2, Enabling SOAHOST1VHN1 on SOAHOST1 and SOAHOST2VHN1 on SOAHOST2. 12-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite

b. In the Domain Structure window, expand the Services node and then click the

Persistence Stores node. The Summary of Persistence Stores page opens.

c. Click Lock Edit.

d. Click New, and then Create FileStore. The Create a New File Store page

opens. e. Enter the following information: - Name: IPMJMSServernStore for example, IPMJMSServer3Store, which allows you identify the service it is created for - Target: WLS_IPMn for example, WLS_IPM3. - Directory: Specify a directory that is located in shared storage so that it is accessible from both ECMHOST1 and ECMHOST2 ORACLE_BASEadmin domain_nameipm_clusterjms.

f. Click OK and activate the changes.