Configuring UMS Drivers Oracle Fusion Middleware Online Documentation Library

Managing the Topology 12-3 operations cause a transaction timeout. There are specific packages provided with the Repository Creation Utility to purge instances. For example: DECLARE FILTER INSTANCE_FILTER := INSTANCE_FILTER; MAX_INSTANCES NUMBER; DELETED_INSTANCES NUMBER; PURGE_PARTITIONED_DATA BOOLEAN := TRUE; BEGIN . FILTER.COMPOSITE_PARTITION_NAME:=default; FILTER.COMPOSITE_NAME := FlatStructure; FILTER.COMPOSITE_REVISION := 10.0; FILTER.STATE := fabric. STATE_UNKNOWN; FILTER.MIN_CREATED_DATE := to_timestamp2010-09-07,YYYY-MM-DD; FILTER.MAX_CREATED_DATE := to_timestamp2010-09-08,YYYY-MM-DD; MAX_INSTANCES := 1000; . DELETED_INSTANCES := FABRIC.DELETE_COMPOSITE_INSTANCES FILTER = FILTER, MAX_INSTANCES = MAX_INSTANCES, PURGE_PARTITIONED_DATA = PURGE_PARTITIONED_DATA ; This deletes the first 1,000 instances of the FlatStructure composite version 10 created between 2010-09-07 and 2010-09-08 that are in UNKNOWN state. Refer to Chapter 8, Managing SOA Composite Applications in the Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite for more details on the possible operations included in the sql packages provided. Always use the scripts provided for a correct purge. Deleting rows in just the composite_dn table may leave dangling references in other tables used by the Oracle Fusion Middleware SOA Infrastructure.

12.5 Configuring UMS Drivers

UMS driver configuration is not automatically propagated in a SOA cluster. When UMS is used by the SOA system that IPM invokes, this implies that you need to do the following: 1. Apply the configuration of UMS drivers in each and every one of the servers in the EDG topology that is using the driver. 2. When server migration is used, servers are moved to a different nodes domain directory. It is necessary to pre-create the UMS driver configuration in the failover node. The UMS driver configuration file location is: ORACLE_BASE admindomain_namemserverdomain_nameserversserver_nametmp _WL_userums_driver_nameconfigurationdriverconfig.xml where represents a directory whose name is randomly generated by Oracle WebLogic Server during deployment, for example, 3682yq. In order to create the file in preparation for possible failovers, users can force a server migration and copy the file from the source node. For example, for IPM: Note: This step is required only if the SOA system used by Oracle IPM is using Unified Messaging System UMS. 12-4 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite 1. Configure the driver for WLS_IPM1 in SOAHOST1. 2. Force a failover of WLS_IPM1 to SOAHOST2. Verify the directory structure for the UMS driver configuration in the failover node: cd ORACLE_BASEadmindomain_namemserverdomain_nameserversserver_nametmp_ WL_userums_driver_nameconfiguration where represents a directory whose name is randomly generated by WLS during deployment, for example, 3682yq. 3. Do a remote copy of the driver configuration file from SOAHOST1 to SOAHOST2: SOAHOST1 scp ORACLE_BASEadmindomain_namemserverdomain_nameserversserver_ name tmp_WL_userums_driver_nameconfigurationdriverconfig.xml oracleSOAHOST2:ORACLE_BASEadmindomain_namemserverdomain_nameservers server_name tmp_WL_userums_driver_nameconfiguration where represents a directory whose name is randomly generated by Oracle WebLogic Server during deployment, for example, 3682yq. It is required to restart the driver for these changes to take effect that is, for the driver to consume the modified configuration. Perform these steps to restart the driver: 1. Log in to the Oracle WebLogic Administration console. 2. Expand the environment node on the navigation tree.

3. Click Deployments.

4. Select the driver.

5. Click Stop-When work completes and confirm the operation.

6. Wait for the driver to transition to the Prepared state refresh the administration console page, if required.

7. Select the driver again, and click Start-Servicing all requests and confirm the

operation. Make sure that you verify in Oracle Enterprise Manager Fusion Middleware Control that the properties for the driver have been preserved.

12.6 Scaling the Topology