Monitoring the Topology Configuring UMS Drivers

11 Managing the Topology 11-1 11 Managing the Topology This chapter describes some operations that you can perform after you have set up the topology. These operations include monitoring, scaling, and backing up your topology. This chapter contains the following sections: ■ Section 11.1, Monitoring the Topology ■ Section 11.2, Configuring UMS Drivers ■ Section 11.3, Managing Space in the SOA Infrastructure Database ■ Section 11.4, Scaling the Topology ■ Section 11.5, Performing Backups and Recoveries ■ Section 11.6, Troubleshooting ■ Section 11.7, Best Practices

11.1 Monitoring the Topology

For information on monitoring the topology, see chapter 15 of the Oracle Fusion Middleware Administrators Guide for Oracle WebCenter.

11.2 Configuring UMS Drivers

UMS driver configuration is not automatically propagated in a SOA cluster. This implies that users need to: 1. Apply the configuration of UMS drivers in each and every one of the servers in the Enterprise Deployment 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_BASEadmindomain_namemserverdomain_nameserversserver_name tmp_WL_userums_driver_nameconfigurationdriverconfig.xml where ’’ represents a directory whose name is randomly generated by WLS 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. It is required to restart the driver for these changes to take effect that is, for the driver to consume the modified configuration. To restart the driver: 11-2 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter 1. Log on to the Oracle WebLogic Administration console. 2. Expand the environment node on the navigation tree.

3. Click on 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.

11.3 Managing Space in the SOA Infrastructure Database