Provide the BPEL port: 8001. Select the SSL option if the target BPEL system requires it. Click the Test Connection button to confirm the connection parameters and Click Next.

Configuring High Availability for Enterprise Content Management 11-41 default name used by OWSM and BPEL. However, the alias can be anything as long as it is unique within the map. 5. Run the list credentials command to verify that the credential was created: wls:ecm_domainserverConfig listCredmap=oracle.wsm.security, key=basic.credential {map=oracle.wsm.security, key=basic.credential} Already in Domain Runtime Tree [Name : weblogic, Description : null, expiry Date : null] PASSWORD: password_for_credential

11.3.8.5 Configuring the BPEL Connection

Perform these steps to configure the BPEL connection: 1. Log into the WLS_IPM1 imaging console at http:ECMHOST1VHN1:16000imaging.

2. In the Left pane, click Manage Connections, then Create Workflow Connection.

3. Click the Create BPEL Connection button.

4. Provide a BPEL machine name and, optionally, a description.

5. Click Next.

6. In the Connection Settings screen, do the following: a. In the provider name field, enter your two SOA server listen addresses separated by a comma: SOAHOST1VHN2, SOAHOST2VHN1

b. Provide the BPEL port: 8001.

c. Select the SSL option if the target BPEL system requires it.

d. Provide the credential alias created earlier in the Configuring BPEL CSF Credentials section.

e. Click the Test Connection button to confirm the connection parameters and

see what composites exist on that BPEL machine.

f. Click Next.

7. Modify the security grants if desired.

8. Click Next.

9. Click Submit.

11.3.8.6 Setting the Front End HTTP Host and Port

You must set the front end HTTP host and port for the Oracle WebLogic Server IPM cluster: 1. Log into the Oracle WebLogic Server Administration Console.

2. In the Change Center, click Lock Edit.

3. Expand the Environment node in the Domain Structure window.

4. Click Clusters.

5. Select IPM_Cluster.

6. Click the HTTP tab.

11-42 Oracle Fusion Middleware High Availability Guide 7. Set the following values: ■ Frontend Host : ecm.mycompany.com ■ Frontend HTTPS Port : 443 ■ Frontend HTTP Port : 80 if not using SSL

8. Click Save.

9. Click Activate Changes in the Change Center section of the Administration

Console. 10. Restart the servers to make the front end host directive in the cluster take effect.

11.3.8.7 Configuring Server Migration for Oracle IPM Instances

This section describes how to configure server migration for Oracle IPM instances.

11.3.8.7.1 About Configuring Server Migration The following steps enable server

migration for the Oracle IPM managed servers. This allows an Oracle IPM managed server to failover to another node in the case of server or process failure. Configuring server migration for the WebLogic managed servers consists of these steps: ■ Step 1: Setting Up a User and Tablespace for the Server Migration Leasing Table ■ Step 2: Creating a Multi Data Source Using the Oracle Weblogic Administration Console ■ Step 3: Editing Node Manager’s Properties File ■ Step 4: Setting Environment and Superuser Privileges for the wlsifconfig.sh Script ■ Step 5: Configuring Server Migration Targets ■ Step 6: Testing the Server Migration

11.3.8.7.2 Setting Up a User and Tablespace for the Server Migration Leasing Table Follow

these steps to set up a user and tablespace for the server migration leasing table:

1. Create a tablespace called ’leasing’. For example, log on to SQLPlus as the sysdba

user and run the following command: SQL create tablespace leasing logging datafile DB_ HOME oradataorclleasing.dbf size 32m autoextend on next 32m maxsize 2048m extent management local;

2. Create a user named ’leasing’ and assign to it the leasing tablespace:

SQL create user leasing identified by welcome1; SQL grant create table to leasing; SQL grant create session to leasing; SQL alter user leasing default tablespace leasing; SQL alter user leasing quota unlimited on LEASING; Note: If other servers in the same domain have already been configured with server migration, the same tablespace and data sources can be used. In that case, the data sources and multi data source for database leasing do not need to be re-created, but they will have to be retargeted to the cluster being configured with server migration, that is, the IPM_Cluster. Configuring High Availability for Enterprise Content Management 11-43 3. Create the leasing table using the leasing.ddl script: a. Copy the leasing.ddl file located in either the WL_HOMEserverdboracle 817 or the WL_HOMEserverdboracle920 directory to your database node.

b. Connect to the database as the leasing user.