Restarting the Administration Server Configuring a JMS Persistence Store for Oracle IPM JMS

8-8 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite 2. Run the following commands on both ECMHOST1 and ECMHOST2 to start Node Manager: ECMHOSTn cd WL_HOMEserverbin ECMHOSTn .startNodeManager.sh

8.6 Restarting the Administration Server

Restart the Administration Server to make these changes take effect. To restart the Administration Server, stop it first using the Administration Console and then start it again as described in Section 5.5, Starting the Administration Server on SOAHOST1.

8.7 Configuring a JMS Persistence Store 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_BASEadmindomain_ namemserverdomain_nameserversserver_namedatastoredefault. You must change IPMs JMS server persistent store to use a shared base directory as follows: 1. Log in to the Oracle WebLogic Server Administration Console.

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

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

3. Click Lock Edit.

4. Click New, and then Create File Store.

5. Enter a name for example IPMJMSServer1Store, which allows you identify the

service it is created for and target WLS_IPM1. Enter a directory that is located in shared storage so that it is accessible from both ECMHOST1 and ECMHOST2 ORACLE_BASEadmindomain_nameipm_clusterjms.

6. Click OK and activate the changes.

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

Messaging-JMS Servers node. The Summary of JMS Servers page opens. 8. Click on the IpmJmsServer1 JMS Server represented as a hyperlink from the Name column of the table. The Settings page for the JMS server opens.

9. Click Lock Edit.

10. In the Persistent Store drop-down list, select IPMJMSServer1Store.

Note: You must use the StartScriptEnabled property to avoid class loading failures and other problems. See also Section 12.8.3, Incomplete Policy Migration After Failed Restart of SOA Server. Note: If the IPM server is sharing the MW_HOME in a local or shared storage with UCM, as suggested in the shared storage configuration described in Chapter 2, Database and Environment Preconfiguration, it is not required to run setNMProps.sh again. In this case, Node Manager has already been configured to use a start script and it is likely already running in the node for UCM. Extending the Domain with Oracle IPM 8-9

11. Click Save and Activate.

12. Repeat the steps and create IPMJMSServer2Store for IPMJMSServer2.

8.8 Configuring a Default Persistence Store for Transaction Recovery