Deploying Composites and Artifacts in SOA Enterprise Deployment Topology Managing Space in the SOA Infrastructure Database

12-2 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite Optimum performance will be achieved when: ■ Each Oracle IPM cluster instance has the maximum affordable number of parsing agents configured via the Work Manager without compromising the performance of the other IPM activities, such as the user interface and Web services. ■ The inbound flow of documents is partitioned into input files containing the appropriate number of documents. On average there should be two input files queued for every parsing agent within the cluster. ■ If one or more machines within a cluster fails, active machines will continue processing the input files. Input files from a failed machine will remain in limbo until the server is restarted. Smaller input files ensure that machine failures do not place large numbers of documents into this limbo state. For example, consider 10,000 inbound documents per hour being processed by two servers. A configuration of two parsing agents per server produces acceptable overall performance and ingests two documents per second per agent. The four parsing agents at two documents per second is eight documents per second, or 28,800 documents per hour. Note that a single input file of 10,000 documents will not be processed in an hour since a single parsing agent working at 7,200 documents per hour will be unable to complete it. However, if you divide the single input file up into eight input files of 1,250 documents, this ensures that all four parsing agents are fully utilized, and the 10,000 documents are completed in the one hour period. Also, if a failure should occur in one of the servers, the other can continue processing the work remaining on its parsing agents until the work is successfully completed.

12.3 Deploying Composites and Artifacts in SOA Enterprise Deployment Topology

When deploying SOA composites to the SOA subsystem used by IPM, deploy to a specific servers address and not to the LBR address ecm.mycompany.com. Deploying to the LBR address may require direct connection from the deployer nodes to the external LBR address, which may require additional ports to be opened in the firewalls used by the system.

12.4 Managing Space in the SOA Infrastructure Database

Although not all composites may use the database frequently, the service engines generate a considerable amount of data in the CUBE_INSTANCE and MEDIATOR_ INSTANCE schemas. Lack of space in the database may prevent SOA composites from functioning. Watch for generic errors, such as oracle.fabric.common.FabricInvocationException in the Oracle Enterprise Manager Fusion Middleware Control console dashboard for instances. Search also in the SOA server’s logs for errors, such as: Error Code: 1691 ... ORA-01691: unable to extend lob segment SOAINFRA.SYS_LOB0000108469C00017 by 128 in tablespace SOAINFRA These messages are typically indicators of space issues in the database that may likely require adding more data files or more space to the existing files. The SOA database administrator should determine the extension policy and parameters to be used when adding space. Additionally, old composite instances can be purged to reduce the SOA infrastructure database size. Oracle does not recommend using the Oracle Enterprise Manager Fusion Middleware Control for this type of operation as in most cases the 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