Scaling out SOA and WSM

11-8 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter

11.4.1.2 Scaling Up WebCenter

In this case, you already have a node that runs a managed server configured with Oracle WebCenter components. The node contains a Middleware home and a WebCenter directory in shared storage. You can use the existing installations Middleware home, and domain directories for creating new Oracle WebCenter managed servers. You do not need to install WebCenter binaries in a new location, or run pack and unpack commands. To scale up the topology:

1. Using the Administration Console, clone WC_Spaces1 or WC_Portlet1 into 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. To clone a managed server:

a. In the Administration Console, select Environment, and then Servers.

b. Select the managed server that you want to clone, for example, WC_Spaces1

or WC_Portlet1. c. Select Clone. d. Name the new managed server SERVER_NAMEn, where n is a number to identify the new managed server.

2. For the listen address, assign the host name or IP to use for this new managed

server, which should be the same as an existing server. Ensure that the port number for this managed server is available on this node.

3. Add the new managed server to the Java Object Cache Cluster. For details, see

Section 6.13, Setting Up the Java Object Cache.

4. Reconfigure the Oracle HTTP Server module with the new member in the cluster.

For more information see Section 6.19, Configuring Oracle HTTP Server for the WC_Spacesn, WC_Portletn, and WC_Collaborationn Managed Servers on WCHOST2. Add the host and port of the new server to the end of the WebLogicCluster parameter. ■ For Spaces, add the member to the Location blocks for webcenter, webcenterhelp, rss, rest, wcsdocs. ■ For Portlet, add the member to the Location blocks for portalTools, wsrp-tools, richtextportlet, pageletadmin, wcps.

11.4.2 Scaling Out the Topology Adding Managed Servers to New Nodes

When you scaling out the topology, you add new managed servers configured with SOA and or WSM-PM to new nodes.

11.4.2.1 Scaling out SOA and WSM

Before performing the steps in this section, check that you meet these requirements: Note: Running multiple managed servers on one node is supported only for the WC_Spaces servers and the WC_Portlet servers. Managing the Topology 11-9 Prerequisites ■ There must be existing nodes running managed servers configured with SOA and WSM-PM within the topology ■ The new node can access the existing home directories for WebLogic Server and SOA. Use the existing installations in shared storage for creating a new WLS_SOA or WLS_WSM managed server. You do not need to install WebLogic Server or SOA 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_HOMEouibinattachHome.sh. To update the Middleware home list to add or remove a WL_HOME, edit the user_ homebeabeahomelist file. See the steps below. To scale out the topology, complete these steps: 1. On the new node, mount the existing MW_Home, which should include the SOA installation and 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: SOAHOSTncd ORACLE_COMMON_HOMEouibinattachHome.sh SOAHOSTn.attachHome.sh -jreLoc ORACLE_BASEfmwjrockit_160_version To update the Middleware home list, create or edit, if another WebLogic installation exists in the node the HOMEbeabeahomelist file and add MW_HOME 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 machine’s Node Manager’s 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_ SOA1WLS_WSM1 into a new managed server. Name it WLS_SOAnWLS_ WSM-PMn, 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. 8. For WLS_WSM servers, run the Java Object Cache configuration utility again to include the new server in the JOC distributed cache as described in Section 4.17, Configuring the Java Object Cache for Oracle WSM. Note: These steps assume that you are adding a new server to node n, where no managed server was running previously. 11-10 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter 9. Create JMS Servers for SOA, BPM, if applicable and UMS on the new managed server. Create the JMS servers for SOA and UMS as follows: a. Use the Oracle WebLogic Server Administration Console to create a new persistent store for the new SOAJMSServer which will be created in a later step and name it, for example, SOAJMSFileStore_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_namejmsSOAJMSFileStore_N b. Create a new JMS server for SOA, for example, SOAJMSServer_N. Use the SOAJMSFileStore_N for this JMS server. Target the SOAJMSServer_N Server to the recently created managed server WLS_SOAn. c. Create a new persistence store for the new UMSJMSServer, and name it, for example, UMSJMSFileStore_N. As the directory for the persistent store, specify the path recommended in Section 2.3, Shared Storage and Recommended Directory Structure, as the directory for the JMS persistent stores: ORACLE_BASE admindomain_namecluster_namejmsUMSJMSFileStore _N

d. Create a new JMS server for UMS: for example, UMSJMSServer_N. Use the