Updating the Coherence Configuration for the SOA Managed Server Starting the WLS_OIM1 and WLS_SOA1 Managed Servers on OIMHOST1

14-12 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management 7. Start the Managed Servers in your domain, as described in Section 20.1, Starting and Stopping Oracle Identity Management Components, except for the following servers: ■ WLS_OIM1 ■ WLS_OIM2 ■ WLS_SOA1 ■ WLS_SOA2

14.6 Post-Installation Steps on OIMHOST1

This section describes post-installation steps. This section contains the following topics: ■ Section 14.6.1, Updating the Coherence Configuration for the SOA Managed Server ■ Section 14.6.2, Starting the WLS_OIM1 and WLS_SOA1 Managed Servers on OIMHOST1 ■ Section 14.6.3, Validating Oracle Identity Manager Instance on OIMHOST1

14.6.1 Updating the Coherence Configuration for the SOA Managed Server

Follow these steps to update the Coherence Configuration for the WLS_SOA Server.

1. Log in to the Oracle WebLogic Server Administration Console.

2. Click Lock and Edit.

3. In the Domain Structure window, expand the Environment node.

4. Click Servers. The Summary of Servers page appears.

5. Click the name of the server in the Name WLS_SOA1WLS_SOA2 column of the

table. The settings page for the selected server appears.

6. Click the Server Start tab.

7. Enter text into the Arguments field for WLS_SOA1 and WLS_SOA2. For WLS_SOA1, enter the following text on a single line, without a carriage return: -Dtangosol.coherence.wka1=soavhn1 -Dtangosol.coherence.wka2=soavhn2 -Dtangosol.coherence.localhost=soavhn1 For WLS_SOA2, enter the following text on a single line, without a carriage return: -Dtangosol.coherence.wka1=soavhn1 -Dtangosol.coherence.wka2=soavhn2 -Dtangosol.coherence.localhost=soavhn2 Extending the Domain with Oracle Identity Manager 14-13

8. Click Save and activate the changes.

14.6.2 Starting the WLS_OIM1 and WLS_SOA1 Managed Servers on OIMHOST1

Follow this sequence of steps to start the WLS_OIM1 and WLS_SOA1 Managed Servers on OIMHOST1: 1. Stop the WebLogic Administration Server on IDMHOST1 by using the WebLogic Administration Console as described in Section 20.1, Starting and Stopping Oracle Identity Management Components. 2. Start the Administration Server on IDMHOST1 using the Node Manager, as described in Section 20.1, Starting and Stopping Oracle Identity Management Components. 3. Validate that the Administration Server started up successfully by bringing up the Oracle WebLogic Administration Console. 4. Start NodeManager on OIMHOST1. Create the nodemanager.properties file by using the startNodemanager.sh script located under the MW_ HOME wlserver_10.3serverbin directory. 5. Before you can start the Managed Servers by using the console, node manager requires that the property StartScriptEnabled be set to true. You set it by Note: The Coherence cluster used for deployment uses port 8088 by default. You can change this port by specifying a different port for example, 8089 with the -Dtangosol.coherence.wkan.port and -Dtangosol.coherence.localport startup parameters. For example: For WLS_SOA1 on a single line: -Dtangosol.coherence.wka1=soavhn1 -Dtangosol.coherence.wka2=soavhn2 -Dtangosol.coherence.localhost=soavhn1 -Dtangosol.coherence.localport=8089 -Dtangosol.coherence.wka1.port=8089 -Dtangosol.coherence.wka2.port=8089 For WLS_SOA2 on a single line: -Dtangosol.coherence.wka1=soavhn1 -Dtangosol.coherence.wka2=soavhn2 -Dtangosol.coherence.localhost=soavhn2 -Dtangosol.coherence.localport=8089 -Dtangosol.coherence.wka1.port=8089 -Dtangosol.coherence.wka2.port=8089 Note: The multicast and unicast addresses are different from the ones used by the WebLogic Server cluster for cluster communication. SOA guarantees that composites are deployed to members of a single WebLogic Server cluster even though the communication protocol for the two entities the WebLogic Server cluster and the groups to which composites are deployed are different. Do not copy the text from this section to your Administration Consoles arguments text field. Doing so can cause HTML tags to be inserted in the Java arguments. The text should not include any text or characters other than the ones shown. 14-14 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management running the setNMProps.sh script located under the MW_HOMEoracle_ commoncommonbin directory. prompt MW_HOMEoracle_commoncommonbinsetNMProps.sh 6. Restart the Node Manager as described in Section 20.1, Starting and Stopping Oracle Identity Management Components so that the properties take effect. 7. Start the WLS_SOA1 Managed Server, using the WebLogic Administration Console as described in Section 20.1, Starting and Stopping Oracle Identity Management Components. 8. Start the WLS_OIM1 Managed Server using the WebLogic Administration Console as described in Section 20.1, Starting and Stopping Oracle Identity Management Components.

14.6.3 Validating Oracle Identity Manager Instance on OIMHOST1