Click Finish. How To Use B2B Binding Components in a SOA Composite Application

Getting Started with Oracle B2B 2-23 ■ Destination Name: Enter the JNDI name of the queue or topic to produce the message or click Browse to select a name. The value of this field is typically the JNDI name. ■ Message Body Type: Select the message body payload type. – Text Message: Use this option when the payload is a string. – Bytes Message: Use this option when the payload is an array of primitive bytes. ■ Delivery Mode: Select a message delivery mode only if WebLogic JMS was selected. – Persistent: Use this option for messages that are persisted to a file system or database. – Non-Persistent: Use this option for messages that are not persisted and are typically held in process memory only. ■ Priority: Select a priority value, with 9 representing the highest priority and 0 representing the lowest priority. ■ Time To Live: Enter a value that indicates the life span of the message. If no subscribers consume the message in the given time, then the message is not delivered. There is no limit. A value of 0 indicates that there is no expiration time. ■ JNDI Name: Displays the JNDI name based on your selection in the Destination Name field only if WebLogic JMS or Advanced Queuing is selected. On the Consume Operation Parameters page, provide the following information and click Next: ■ Destination Name: Enter the JNDI name of the queue or topic to consume the message or click Browse to select a name. ■ Message Body Type: Select the message body payload type. – Text Message: Use this option when the payload is a string. – Bytes Message: Use this option when the payload is an array of primitive bytes. ■ Message Selector: Specify filtering logic that enables you to receive messages that match certain criteria. Enter an expression between 1 and 255 characters in length. Use SQL92 syntax in this field. The JMS server uses these criteria to filter messages received by this consumer. This works with variables defined in standard JMS headers and user-defined properties. You cannot use variables or elements that are in the payload of the message. ■ Use MessageListener: This option is set to false by default if you selected Oracle Weblogic JMS on the JMS Provider page. It is not editable. Select true or false if you selected Oracle Advanced Queueing on the JMS Provider page only if Oracle Advanced Queuing or Third Party is selected. ■ Durable Subscriber ID: Enter an ID for receiving messages from a JMS topic. If you do not specify an ID, then you must have an active subscription session to receive messages. If you specify an ID for topics, then you receive messages even if you do not currently have an active subscription session. When a durable subscriber is disconnected from the JMS server, the server stores messages. When the durable subscriber reconnects, the server sends the unexpired messages that accumulated only if Third Party is selected.