IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Oracle E-Business Suite > Configure the module for deployment > Configure the module for advanced queue integration

Configure the module for inbound processing

To configure the module for the advanced queue interface, use the external service wizard in Integration Designer and configure the advanced queue to be polled by the adapter inbound at run time.

You must place the required JAR files for the advanced queue interface in a local directory.

This task is to create an inbound application module that integrates to an advanced queue interface.


Procedure

  1. Create a project. For information about how to create a project, see Create the project.

  2. In the Select the Processing Direction window, select Inbound. Click Next.

  3. In the Specify the Discovery Properties window, select Oracle E-Business Suite > Advanced Queue.

  4. Select the Oracle E-Business Suite version, and specify the connection information for the advanced queue interface.

    1. In the System ID field, specify the system ID (SID) to connect to the Oracle E-Business Suite.

    2. In the Host name field, enter the host name or IP address of the system on which Oracle E-Business Suite is installed.

    3. In the Port number field, specify the port number to connect to the Oracle database.

    4. In the User name and Password fields, type the user name and password to connect to the Oracle database.

  5. Click Next.

  6. In the Find Objects in the Enterprise System window, click Edit Query.

  7. In the Specify the Query Properties window, specify the schema name or pattern you want to work with.

  8. Click OK to save your changes to the query. In the Find Objects in the Enterprise System window, click Run Query to use the query to discover the objects. The Discovered objects pane lists the different queues supported by the adapter for the dequeue operation. The result of running a typical query is shown in the following figure:

  9. Select the queue from the Discovered objects list, and click the > (Add) button to add the queue to the Selected objects list. Advanced Queue is the source, which the adapter polls to retrieve messages. As an inbound module can poll only one source, you can select only one queue. Click OK.

  10. In the Specify Composite Properties window, specify the information for the dequeue operation.

  11. Click Next.

  12. In the Specify the Service Generation and Deployment Properties window, select Using an existing JAAS alias (recommended) or Using security properties from the managed connection factory.

    Properties for Advanced Queue Dequeue Operation:

    1. Required: In the Advanced Queue Consumer Name field, enter the consumer or recipient name based on target messages that the adapter polls. Setting the recipient or consumer name is mandatory while enqueuing a message as messages are dequeued based on this name.

    2. Optional: In the Advanced Queue Dequeue Condition field, enter the condition for the dequeue operation. The dequeue condition is specified as a Boolean expression using a syntax similar to the WHERE clause of a SQL query. The dequeue condition parameter cannot exceed 4000 characters.

    3. Optional: In the Advanced Queue Correlation ID field, enter the identifier to group or correlate messages. This identifier is set during the enqueue operation.
    Properties related to staging event table and data source:

    1. From the Dequeue using list, select the dequeue mechanism used for the dequeue operation. If you select PL/SQL, the wrapper stored procedure ( <schema>_<queue selected>_WPKG) and the required types are created by default at run time. If you select JMS, ensure that you selected the aqapi.jar file in the Locate the Required Files and Libraries window.

    2. In the Staging event table field, enter the name of the staging table. This table is automatically created during run time.

    3. In the Staging data source JNDI field, enter the name of the JNDI data source used to connect to the staging table.
    For information about other properties in the Specify the Service Generation and Deployment Properties window, see Setting deployment properties and generating the service.

    In the Advanced Queue Consumer Name field, you can also enter the recipient ID of the consumer or the subscription ID of the subscriber (of AQ). However, if multiple inbound modules using AQ inbound are configured to run on a server, ensure that they have different subscription IDs and that they use different staging tables. Using a common staging table across different subscribers can result in errors.

  13. In the Specify the Location Properties window, select or create a module name, and then click Finish.


What to do next

You can test or deploy your module.

Configure the module for advanced queue integration


Previous topic: Configure the module for outbound processing


Related concepts:

Dequeue operation

Enqueue operation

Limitations of JMS dequeue mechanism

Advanced Queue integration overview