Configuring Oracle Data Integrator Integration Properties

22-16 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite

22.7.1.1 Configuring the Adapter to Retry Sending Messages

If messages from BPEL process monitors are published when Oracle BAM Server is unavailable, the messages are not persisted and therefore are not published to the Oracle BAM data objects when Oracle BAM Server comes back online. You can change this behavior by setting the Oracle BAM Adapter property Block_On_Batch_Full to true in Oracle BAM Adapter configuration as described in Section 22.7.1, Configuring Oracle BAM Adapter Properties. For more information about BPEL process monitors see Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

22.7.2 Configuring Oracle BAM Connection Factories

Some configuration in the Oracle WebLogic Server Administration Console is necessary before using Oracle BAM Adapter. Use the Oracle WebLogic Server Administration Console to configure the Oracle BAM connection factories for connections with Oracle BAM Server. To configure Oracle BAM connection factories: 1. Go to the Oracle WebLogic Server Administration Console http:host_name:port_numberconsole, and log on.

2. In the Domain Structure menu, select Deployments.

3. In the Deployments summary table, search for OracleBamAdapter and click it.

Block_On_Batch_Full SOAP_Block_On_Batch_Full false The default setting for block on batch full, which indicates whether batching operations should block when the batch is full. If true then batching calls block until room is freed up in the batch for the operation. If false then BatchIsFullExcept ion exception is thrown. Number_Batches SOAP_Number_Batches 10 The limit of the number of pending calls allowed. Table 22–1 Cont. Oracle BAM Adapter Configuration Properties RMI Property SOAP Property Default Description Configuring Oracle Business Activity Monitoring 22-17

4. In the Settings for oracle-bam-adapter page, select the Configuration tab, and then

the Outbound Connection Pools tab in the second row.

5. Configure the connection factory interface that you intend to use in Oracle

JDeveloper, by expanding the appropriate Group and Instance target and clicking the Java Naming and Directory Interface JNDI name. To configure the connection factory for RMI-based calls, click to expand the oracle.bam.adapter.adc.RMIConnectionFactory group and select the JNDI name that the user uses in Oracle JDeveloper. The eisbamrmi connection factory is provided out of the box. To configure the connection factory for SOAP-based calls, click to expand the oracle.bam.adapter.adc.SOAPConnectionFactory group and select the JNDI name that the user uses in Oracle JDeveloper. The eisbamsoap connection factory is provided out of the box.