The fixed portion is modeled on the standard MQ header pattern and consists of the following fields:

StrucId (MQCHAR4)

Structure identifier.

Must be "RFH ". Notice there is a space character after the letter H.

Version (MQLONG)

Structure version number.

Must be "2".

StrucLength (MQLONG)

Total length of MQRFH2, including the NameValueData fields. See below.

The value set into StrucLength must be a multiple of 4 (the data in the NameValueData fields may be padded with space characters to achieve this).

The MQ Adapter will try to calculate this value automatically if not set.

Encoding (MQLONG)

Data encoding.

Encoding of any numeric data in the portion of the message following MQRFH2 (the next header, or the message data following this header).

The commonly used value is "237".

CodedCharSetId (MQLONG)

Coded character set identifier.

Representation of any character data in the portion of the message following MQRFH2 (the next header, or the message data following this header).

The commonly used value is "819".

Format (MQCHAR8)

Format name.

Format name for the portion of the message following MQRFH2.

Must be "MQHRF2 ". Notice there are two space characters after the number 2.

Flags (MQLONG)

Flags.

MQRFH_NO_FLAGS =0. No flags set.

Commonly used value is "0".

NameValueCCSID (MQLONG)

The coded character set identifier (CCSID) for the NameValueData character part (see Variable Portion contained in this header. The NameValueData may be coded in a character set that differs from the other character strings that are contained in the header (StrucID and Format).

If the NameValueCCSID field is a 2-byte Unicode CCSID (1200, 13488, or 17584), then the byte order of the Unicode CCSID is the same as the byte ordering of the numeric fields in MQRFH2. (For example, Version, StrucLength, and NameValueCCSID itself.)

The NameValueCCSID field may take only values from Table 10-3:

The variable portion follows the fixed portion. The variable portion contains a variable number of MQRFH2 folders. Each folder can occur multiple times in the same RFH2 header. Other folders such as mqext, mq_usr, mqps and others. can also be part of the RFH2 header. For more information, refer to the IBM documentation regarding MQ RFH2 headers.

The related properties are grouped together. The MQRFH2 header can contain the following message service folders:

The <mcd> folder

This contains properties that describe the shape or format of the message. For example, the Msd property identifies the message as being Text, Bytes, Stream. Map, Object, or Null. This folder is always present in JMS MQRFH2.

The <jms> folder

This is used to transport JMS header fields, and JMSX properties that cannot be fully expressed in the MQMD. This folder is always present in a JMS MQRFH2.

The <usr> folder

This is used to transport any application-defined properties associated with the message. This folder is only present if the application has set some application-defined properties.

The <psc> folder

This is used to convey publish/subscribe command messages to the broker. Only one psc folder is allowed in the NameValueData field.

The <pscr> folder

This is used to contain information from the broker, in response to publish/subscribe command messages. Only one pscr folder is present in a response message.

Table 10-4 shows a full list of property names.

The syntax used to express the properties in the variable portion is as follows:

NameValueLength (MQLONG)

Length, in bytes, of the NameValueData string that immediately follows this length field. It does not include its own length. The value set into NameValueLength is always a multiple of 4. The NameValueData field is padded with space characters to achieve this.

NameValueData (MQCHARn)

A single character string, whose length in bytes is given by the preceding NameValueLength field. It contains a folder holding a sequence of properties. Each property is a name/type/value triplet, contained within an XML element whose name is the folder name, as follows:

<foldername> triplet1 triplet2 ..... tripletn </foldername>

In a scenario involving fail over, such as when the prepare phase completes successfully before a middleware fails, messages must be recovered within the adapter without restarting the MQSeries server. You must manually resolve the in-doubt transactions.

To view all in-doubt transactions for a Queue Manager, you must execute the following command at the command prompt:

dspmqtrn -m[ourQueueManager]

To backout the messages, use the following command:

rsvmqtrn -m[ourQueueManager] -b [Transaction],[Number]

To commit the messages, use the following command :

rsvmqtrn -m[ourQueueManager] -c [Transaction],[Number]

1. In the WebLogic Console, create a JNDI entry by specifying

   eis/activemq/XAQueue
   

   and specifying the ConnectionFactoryLocation as

    org.apache.activemq.ActiveMQXAConnectionFactory 
   

2. Provide FactoryProperties

   BrokerURL=tcp://<YOUR_HOST>:<YOUR_PORT>;ThirdPartyJMSProvider=true
   

3. Set IsTransacted : false

Before you configure the Oracle MQ Series Adapter for high availability, you must ensure that the following prerequisites are met:

• Clustered processes must use the same queue.

• Retries should be configured either at the binding level or by using fault policies to ensure that any intermittent errors can be resolved automatically.

The Oracle MQ Series Adapter must ensure that it participates in the XA transaction. For more information about the XA transaction, see XA Transactions.

The Oracle MQ Series Adapter supports a pull model for connecting to the back-end application for receiving events. Connection-related issues are considered recoverable and most inbound adapters keep retrying until the adapters are able to establish connection with the EIS.

In case of Oracle MQ Series Adapter, a message not being able to put to a queue is also retriable.

For more information about retry mechanism, see Error Handling.

Backout Queue is a queue for putting rejected messages from an inbound queue. The inbound adapter checks for the backout count of the messages and if this count exceeds the MaximumBcakoutCount value, then the adapter puts the messages to the specified Backout Queue. This mechanism is used by the Oracle MQ Series Adapter to handle inbound retries for the rejected messages.

If you specify the BackoutQueueName property in the .jca file, then Oracle MQ Series Adapter uses the message backout count for retries. You can specify the maximum retries using the MaximumBackoutCount property. The default value for this property is infinite. If you do not specify the MaximumBackoutCount value along with the BackoutQueueName, then the adapter retries infinitely. The adapter does not consider JCA retries (specified in composite.xml) when the BackOut Queue properties are specified.

The BackoutRetries property must be set to specify the number of retries for delivering the message to the Backout Queue with retry interval set using the BackoutRetryInterval property. The default value for BackoutRetries is 3 and BackoutInterval is 5 sec.

If a message gets rejected even after the MaximumBackoutCount value is reached, then the adapter puts the message to Backout Queue. If Oracle MQ Series Adapter is cannot put the message to Backout Queue, then the adapter tries till the BackoutRetries count with the BackoutInterval time delay. If even after the BackoutRetries the adapter cannot put the message to Backout Queue, then the adapter deactivates the endpoint.

You must also specify the name of the Queue Manager of the Backout Queue in the BackoutQueueManagerName property. You must not use this property if the BackoutQueue resides on the inbound queue QueueManager.

For more information about configuring Backout Queues, see Configuring a Backout Queue.

In this scenario, the Oracle MQ Series Adapter connects to a specific queue managed by a queue manager and then writes the message to the queue. For outbound messages sent from Oracle BPEL PM or Mediator, the Oracle MQ Series Adapter performs the following operations:

1. Receives message from Oracle BPEL PM or Mediator.

2. Formats the XML content as specified at design time.

3. Sets the properties of the message, such as priority, expiry, message type, and persistence. These properties are based on the selections that you made in the Adapter Configuration Wizard.

   For more information about message properties, see Messages Types.

4. Sends the message to the queue specified at design time in the Adapter Configuration Wizard.

Figure 10-7 displays the operation type that you must select in the Adapter Configuration Wizard.

The page that appears after selecting the Put Message into MQ operation type is shown in Figure 10-8.

You can specify the following properties in this page:

• Queue Name: The name of the queue on which the Oracle MQ Series Adapter enqueues the message. This is a mandatory field.

• Queue Manager: The name of the queue manager to which the queue belongs. This field is optional and is necessary when enqueuing message to a remote queue.

• Partial Delivery: This is applicable only when you specify multiple queues for outbound operation, which is also known as the Distribution List scenario. Partial Delivery takes either true or false. If assigned true, then even if the delivery of message fails for some queues, it would still go and put the message to the rest of the queues specified in the distribution list. If assigned false, it means even if one message fails, then the message is not put to any queue.

• Message Format: The format of the message.

  Note:

  When enqueuing a message, ensure that the various mandatory values, required for a specific format, are specified correctly.

• Priority: The priority of the message, ranging from 0 (low) to 9 (high).

• Persistence: The persistence of the message. You can also specify the persistence of the message to be taken from the default persistence attribute, as defined by the destination queue.

• Delivery Failure: If the delivery of message fails, then either it can be put to a dead letter queue or it can be discarded.

• Allow Messages to Be Segmented When Necessary: This is applicable to a message that is big enough for the queue to accommodate. In that case, if you have specified that it has to be segmented, then the single message can be broken into that many bytes the queue can take, which results in multiple messages.

• Expiry: The expiry time of the message. The message is discarded after the expiry time has elapsed.

For more information about these properties, see Message Properties.

The next Adapter Configuration Wizard page that appears is the Messages page, as shown in Figure 10-9. This page enables you to select the XML Schema Definition (XSD) file for translation.

If native format translation is not required (for example, a JPG or GIF image is being processed), then select the Native format translation is not required check box. The file is passed through in base-64 encoding.

XSD files are required for translation. To define a new schema or convert an existing data type description (DTD) or COBOL Copybook, select Define Schema for Native Format. This starts the Native Format Builder wizard. This wizard guides you through the creation of a native schema file from file formats, such as delimited by special characters, comma-delimited value (CSV), fixed-length, DTD, and COBOL Copybook. After the native schema file is created, you are returned to this Messages page with the Schema File URL and Schema Element fields filled in.

For more information, see Creating Native Schema Files with the Native Format Builder Wizard.

In this scenario, the Oracle MQ Series Adapter connects to a specific queue managed by a queue manager and then removes the message from the queue. For inbound messages sent to Oracle BPEL PM or Mediator, the Oracle MQ Series Adapter performs the following operations:

1. Connects to the queue specified at design time.

2. Dequeues the message from the queue when a message arrives.

3. Reads and translates the message based on the translation logic defined at design time.

4. Publishes the message as an XML message to Oracle BPEL PM or Mediator.

   Figure 10-10 displays the operation type that you must select in the Adapter Configuration Wizard.

   Figure 10-10 The Adapter Configuration Wizard: Consume Message Selection

   
   Description of "Figure 10-10 The Adapter Configuration Wizard: Consume Message Selection"

   The page that appears after selecting the Get Message from MQ operation type is shown in Figure 10-11.

   Figure 10-11 Get Message from MQ Page

   
   Description of "Figure 10-11 Get Message from MQ Page"

   You can specify the following properties in this page:

   • Queue Name: The name of the queue from which the Oracle MQ Series Adapter dequeues the message. This is a mandatory field.

   • Schema Options: This option enables you to specify the schema for the message to be dequeued.

     • Choose Other Schema: This option enables you to choose your schema for the message to be dequeued.

     • Choose a Predefined Schema: This option enables you to choose a readymade schema that the adapter provides.

   The next Adapter Configuration Wizard that appears is the Messages page, as shown in Figure 10-9. This page enables you to select the XSD schema file for translation.

   As with specifying the schema for the produce message operation, you can perform the following tasks in this page:

   • Specify if native format translation is not required.

   • Select the XSD schema file for translation.

   • Start the Native Format Builder wizard to create an XSD file from file formats such as CSV, fixed-length, DTD, and COBOL Copybook.

   For more information about the Messages page, see Enqueue Message.

In this scenario, the Oracle BPEL PM sends a request message and receives the corresponding response using a non-initiating receive activity. The invoke activity initiates the outbound invocation of the adapter to send the request. The Oracle MQ Series Adapter performs the following operations:

1. Receives message from Oracle BPEL PM.

2. Formats the XML content as specified at design time in the Adapter Configuration Wizard.

3. Sets properties and a correlation schema on the request message.

4. Sends the message to the queue specified at design time. The third-party application receives the message, processes it, generates the response, and then enqueues the response message to the replyTo queue specified in the request message. The Correlation ID and Message ID of the response message are generated based on the correlation schema specified in the request message.

5. The Oracle MQ Series Adapter dequeues the message from the replyTo queue.

6. Sends the response to the non-initiating receive activity of Mediator. To ensure that response is sent to the correct BPEL instance, correlation schemas are used.

Figure 10-12 displays the operation type that you must select in the Adapter Configuration Wizard.

The page that appears after selecting the Send Message to MQ and Get Reply/Reports operation type is shown in Figure 10-13.

You can specify the following properties in this page:

• Message Type: The type of the message. You can either send a normal message or a request message.

• Get Reports: Select this option if you want any kind of report. You can specify the type of report in the next page, as shown in Figure 10-14.

• Queue Name: The name of the queue to which the Oracle MQ Series Adapter enqueues the message. This is a mandatory field.

• Queue Manager: The name of the queue manager to which the queue belongs. This field is optional.

• Message Format: The format of the message.

• Priority: The priority of the message ranging from 0 (low) to 9 (high).

• Persistence: The persistence of the message. You can also specify the persistence of the message to be taken from the default persistence attribute, as defined by the destination queue.

• Delivery Failure: If the delivery of the message fails, then either it can be put to a dead letter queue or it can be discarded.

• Allow Messages to Be Segmented When Necessary: This is applicable to a message that is big enough for the queue to accommodate. In that case, if you have specified that it has to be segmented, then the single message can be broken into that many bytes the queue can take, which results in multiple messages.

• Expiry: The expiry time of the message. The message is discarded after the expiry time has elapsed.

For more information about these properties, see Message Properties and Report Messages.

The page that is displayed when you click Next in the Send Message to MQ and Get Reply/Reports page can be a Reports page (shown in Figure 10-14) or a Response page (shown in Figure 10-15).

The Reports page, shown in Figure 10-14, is displayed only if you have selected the Get Reports option in the Send Message to MQ and Get Reply/Reports page, as shown in Figure 10-13.

You can select the following types of reports in this page:

• Confirmation on Arrival

• Confirmation on Delivery

• Exception Report

• Expiry Report

For information about these report types, see Report Messages.

The Response page shown in Figure 10-15 is displayed when you click Next in the Reports page.

You can specify the following properties in the Response page:

• Reply to Queue Name: The name of the reply queue name.

• Correlation Scheme: The correlation schema that is necessary for the Oracle MQ Series Adapter.

  For information about correlation schemas, see Correlation Schemas.

• Schema Options: This option enables you to specify the schema for the message to be dequeued.

  • Choose Other Schema: This option enables you to choose your schema for the message to be dequeued.

  • Choose a Predefined Schema: This option enables you to choose a readymade schema that the adapter provides.

When you click Next in the Response page, a Messages page, shown in Figure 10-16, is displayed. This page enables you to select the XSD schema file for translation for request and as response message.

You can perform the following tasks in this page:

• Specify if native format translation is not required.

• Select the XSD schema file for translation.

• Start the Native Format Builder wizard to create an XSD file from file formats such as CSV, fixed-length, DTD, and COBOL Copybook.

For more information about the Messages page, see Enqueue Message.

In the solicit-request-response scenario, the reply message is expected in the reply queue specified with some correlation scheme that is provided through the request message. This reply queue, which is used by a particular process (BPEL/Mediator), should not be used by any other process.

If the same reply queue is used by some other application, then the message might be picked, irrespective of whether the reply message had the proper correlation or not, and eventually the message becomes lost.

In this scenario, the Oracle BPEL PM receives a request, processes it, and sends the response synchronously by using a reply activity. The Oracle MQ Series Adapter performs the following operations:

1. Dequeues the request message from the queue when the message arrives.

2. Reads and translates the message based on the translation logic defined at design time.

3. Publishes the message as an XML message to Oracle BPEL PM. The Oracle BPEL PM processes the request and sends the response to the Oracle MQ Series Adapter.

4. Receives the response message from the Oracle BPEL PM.

5. Formats the XML content as specified at design time.

6. Sets the properties of the message such as priority, expiry, message type, and persistence. These properties are based on the selections that you made in the Adapter Configuration Wizard.

7. Sends the message to the queue specified at design time in the Adapter Configuration Wizard.

Figure 10-17 shows a sample BPEL process for this scenario.

Figure 10-18 displays the operation type that you must select in the Adapter Configuration Wizard.

The page that appears after you select the Get Message from MQ and Send Reply/Reports operation type is shown in Figure 10-19. Specify the queue name from which the Oracle MQ Series Adapter dequeues the message in this page.

When you click Next in the Get Message from MQ and send Reply/Reports page, the Response page shown in Figure 10-20 is displayed.

You can specify the following properties in the Response page:

• Message Type: The message type of the message to be dequeued. This option affects the return message type.

• Message Format: The format of the message.

• Priority: The priority of the message.

• Persistence: The persistence of the message. You can also specify the persistence of the message to be taken from the default persistence attribute, as defined by the destination queue.

• Delivery Failure: If the delivery of the message fails, then either it can be put to a dead letter queue or it can be discarded.

• Allow Messages to Be Segmented When Necessary: This is applicable to a message that is big enough for the queue to accommodate. In that case, if you have specified that it has to be segmented, then the single message can be broken into that many bytes the queue can take, which results in multiple messages.

• Expiry: The expiry time of the message.

For more information about these properties, see Message Properties.

Click Next in the Response page, the Messages page is displayed, as shown in Figure 10-16. You can perform the following tasks in this page:

• Specify if native format translation is not required.

• Select the XSD schema file for translation.

• Start the Native Format Builder wizard to create an XSD file from file formats such as CSV, fixed-length, DTD, and COBOL Copybook.

For more information about the Messages page, see Enqueue Message.

In Oracle BPEL PM initiated request-response interaction, a BPEL process receives a request as an inbound message, processes it, and then sends the response through an invoke activity. For asynchronous request-reply scenario, the Oracle MQ Series Adapter performs the following operations:

1. Dequeues the message from the queue when a message arrives.

2. Reads and translates the message based on the translation logic defined at design time.

3. Publishes the message as an XML message to Oracle BPEL PM. The Oracle BPEL PM processes the request and sends the response to the Oracle MQ Series Adapter.

4. Receives messages from Oracle BPEL PM.

5. Formats the XML content as specified at design time.

6. Sets the properties of the message, such as priority, expiry, message type, and persistence. These properties are based on the selections that you made in the Adapter Configuration Wizard.

7. Sends the message to the queue specified at design time in the Adapter Configuration Wizard.

Figure 10-21 shows a sample BPEL process for this scenario.

Figure 10-22 displays the operation type that you must select in the Adapter Configuration Wizard.

The page that appears after selecting the Get Message from MQ and send Reply/Reports operation type is shown in Figure 10-19. Specify the queue name from which the Oracle MQ Series Adapter dequeues the message in this page.

When you click Next in the Get Message from MQ and send Reply/Reports page, the Response page shown in Figure 10-20 is displayed.

You can specify the following properties in the Response page:

• Message Type: The message type of the message to be dequeued. This option affects the return message type.

• Message Format: The format of the message.

• Priority: The priority of the message.

• Persistence: The persistence of the message. You can also specify the persistence of the message to be taken from the default persistence attribute, as defined by the destination queue.

• Delivery Failure: If the delivery of the message fails, then either it can be put to a dead letter queue or it can be discarded.

• Allow Messages to Be Segmented When Necessary: This is applicable to a message that is big enough for the queue to accommodate. In that case, if you have specified that it has to be segmented, then the single message can be broken into that many bytes the queue can take, which results in mulitple messages.

• Expiry: The expiry time of the message.

For more information about these properties, see Message Properties.

The page that is displayed when you click Next in the Get Message to MQ and Send Reply/Reports page is a Response page (shown in Figure 10-23 and Figure 10-24) but with two different set of options.

The Response page shown in Figure 10-24 is displayed only if you have selected the Normal option in Message Type field in the Get Message to MQ and Send Reply/Reports page.

You can specify the following properties in the Response page:

• (Optional) Fallback Reply to Queue: Enter a response fallback queue name. The response message is enqueued to the queue specified with the replyToQueue property of the request message. However, if the replyToQueue property is not set on the request message, then entering a name here ensures that the process does not fail to enqueue the response.

• (Optional) Fallback Reply to Queue Manager: Enter a secondary queue name. This name is used when the primary queue manager that was established when you specified the JNDI connection name cannot access the queue name entered in the Queue Name field. This is similar to the functionality described in the Fallback Reply to Queue field.

  To specify the other properties in this Response page, see properties mentioned for Figure 10-23.

When you click Next in the Response page, the Messages page shown in Figure 10-25 is displayed. You can perform the following tasks in this page:

• Specify if native format translation is not required.

• Select the XSD schema file for translation.

• Start the Native Format Builder wizard to create an XSD file from file formats such as CSV, fixed-length, DTD, and COBOL Copybook.

For more information about the Messages page, see Enqueue Message.

In asynchronous request-reply interaction, you must map the following properties from the inbound message header to the outbound message header:

• MsgID: Refers to the message ID.

• CorrelID: Refers to the correlation ID of a message.

• CorrelationScheme: Refers to a combination of both the msgid and the correlid of the request message.

  For more information, see Correlation Schemas.

• ReplyToQ : Refers to the name of the response queue name.

• ReplyToQueueManager: Refers to the name of the response queue manager.

You can use the Assign activity to map these properties.

1. Create a BPEL process and double-click to open the BPEL Designer page.

2. In the vertical menu that appears, click the Variables icon that appears as (x) grayed out. The Variables dialog is displayed, as shown in Figure 10-26.

   Figure 10-26 The Variables Dialog

   
   Description of "Figure 10-26 The Variables Dialog"

3. Capture the inbound header messages into these variables, as shown in Figure 10-27 and Figure 10-28.

   Figure 10-27 The Receive Dialog

   
   Description of "Figure 10-27 The Receive Dialog "

4. Assign the variables captured in Step 2 for the Outbound Reply message, as shown in Figure 10-28 and Figure 10-23.

   Figure 10-28 The Invoke Dialog

   
   Description of "Figure 10-28 The Invoke Dialog"

In this scenario, the Mediator receives a request, processes it, and sends the response synchronously. The Oracle MQ Series Adapter performs the following operations:

1. Dequeues the request message from the queue when the message arrives.

2. Reads and translates the message based on the translation logic defined at design time.

3. Publishes the message as an XML message to Mediator. The Mediator processes the request and sends the response to the Oracle MQ Series Adapter.

4. Receives the response message from the Mediator.

5. Formats the XML content as specified at design time.

6. Sets the properties of the message such as priority, expiry, message type, and persistence. These properties are based on the selections that you made in the Adapter Configuration Wizard.

7. Sends the message to the queue specified at design time in the Adapter Configuration Wizard.

Figure 10-19 displays the operation type that you must select in the Adapter Configuration Wizard.

From this page onwards, all the pages are similar to the pages explained in Synchronous Request-Response ( As Server).

The Oracle MQ Series Adapter supports the outbound synchronous-solicit-request-response scenario. In this scenario, the adapter enqueues a normal/request message in a queue and expects the report/reply synchronously. The report/reply message arrives in the ReplyToQueueName queue of the normal/request message.

Figure 10-29 displays the operation type that you must select in the Adapter Configuration Wizard.

The page that appears after selecting the Send Message to MQ and Get Reply/Reports operation type is shown in Figure 10-13.

You can specify the following properties in this page:

• Message Type: The type of the message. You can either send a normal message or a request message.

• Queue Name: The name of the queue to which the Oracle MQ Series Adapter enqueues the message. This is a mandatory field.

• Queue Manager: The name of the queue manager to which the queue belongs. This field is optional and is necessary when enqueuing message to a remote queue.

• Message Format: The format of the message.

• Priority: The priority of the message ranging from 0 (low) to 9 (high).

• Persistence: The persistence of the message. You can also specify the persistence of the message to be taken from the default persistence attribute, as defined by the destination queue.

• Delivery Failure: If delivery of the message fails, then either it can be put to a dead letter queue or it can be discarded.

• Allow Messages to Be Segmented When Necessary: This is applicable to a message that is big enough for the queue to accommodate. In that case, if you have specified that it has to be segmented, then the single message can be broken into that many bytes the queue can take, which results in multiple messages.

• Expiry: The expiry time of the message. The message is discarded after the expiry time has elapsed.

Click Next in the Send Message to MQ and Get Reply/Reports page, the Response page, as shown in Figure 10-30, is displayed.

For the Synchronous Request-Response scenario, you must also edit the following properties in the Response page:

• Reply to Queue Name: The name of reply queue name.

• Correlation Scheme: The correlation schema that must be used by the Oracle MQ Series Adapter.

  For more information about correlation schemas, see Correlation Schemas.

• Schema Options: This option enables you to specify the schema for the message to be dequeued.

  • Choose Other Schema: This option enables you to choose your schema for the message to be dequeued.

  • Choose a Predefined Schema: This option enables you to choose a readymade schema that the adapter provides.

• Response Wait Interval: The permitted value for this property is any interval value (>= 0). This is the time in milliseconds during which the adapter waits for the report/reply to arrive in replyToQueueName. By default, the value of this property is 0 milliseconds. You can change this value, but the value must be less than that of the timeout interval for the outbound activity. If the report/reply message does not arrive in the stipulated time, then the adapter throws an exception. This property is not mandatory.

The Oracle MQ Series Adapter also supports the outbound synchronous-solicit-request-response scenario. In this scenario, the adapter enqueues a normal/request message in a queue and expects the report/reply synchronously. The report/reply message arrives in the Reply to Queue Name queue of the normal/request message.

The Synchronous Request-Response scenario for Oracle Mediator as client is same as the Synchronous Request-Response for Oracle BPEL as client. For more information about the Synchronous Request-Response scenario, see Synchronous Request-Response ( As Client).

In this scenario, Oracle Mediator sends a request message and receives the corresponding response from the Mediator callback handler. Oracle Mediator sends an outbound invocation to send the request. The Oracle MQ Series Adapter performs the following operations:

1. Receives message from Oracle Mediator.

2. Formats the XML content as specified at design time in the Adapter Configuration Wizard.

3. Sets properties and a correlation schema on the request message.

4. Sends the message to the queue specified at design time. The third-party application receives the message, processes it, generates the response, and then enqueues the response message to the replyTo queue specified in the request message. The Correlation ID and Message ID of the response message is generated based on the correlation schema specified in the request message.

5. The Oracle MQ Series Adapter dequeues the message from the replyTo queue.

6. Sets the properties of the message such as priority, expiry, message type, and persistence. These properties are based on the selections that you made in the Adapter Configuration Wizard.

7. Sends the response to the non-initiating receive activity of the BPEL process. To ensure that response is sent to the correct BPEL instance, correlation schemas are used.

Figure 10-12 displays the operation type that you must select in the Adapter Configuration Wizard.

The page that appears after selecting the Send Message to MQ and Get Reply/Reports operation type is shown in Figure 10-13.

You can specify the following properties in this page:

• Message Type: The type of the message. You can either send a normal message or a request message.

• Queue Name: The name of the queue to which the Oracle MQ Series Adapter enqueues the message. This is a mandatory field.

• Message Format: The format of the message.

• Queue Manager: The name of the queue manager to which the queue belongs. This field is optional and is necessary when enqueuing message to a remote queue.

• Priority: The priority of the message ranging from 0 (low) to 9 (high).

• Persistence: The persistence of the message. You can also specify the persistence of the message to be taken from the default persistence attribute, as defined by the destination queue.

• Delivery Failure: If delivery of the message fails, then either it can be put to a dead letter queue or it can be discarded.

• Allow Messages to be Segmented When Necessary: This is applicable to a message that is big enough for the queue to accommodate. In that case, if you have specified that it has to be segmented, then the single message can be broken into that many bytes the queue can take, which results in mutliple messages.

• Expiry: The expiry time of the message. The message is discarded after the expiry time has elapsed.

For more information about these properties, see Message Properties and Report Messages.

The page that is displayed when you click Next in the Send Message to MQ and Get Reply/Reports page can be a Reports page (shown in Figure 10-14) or a Response page (shown in Figure 10-15).

The Reports page shown in Figure 10-14 is displayed only if you have selected the Get Reports option in the Send Message to MQ and Get Reply/Reports page shown in Figure 10-13.

The Response page shown in Figure 10-15 is displayed, irrespective of whether you select the Request or Normal option. The only difference is that if you select the Request option, then REPLY is displayed in the Message Type field of the Response page. On the other hand, if you select the Normal option, then REPORTS is displayed in the Message Type field of the Response page.

You can select the following types of reports in Figure 10-14:

• Confirmation on Arrival

• Confirmation on Delivery

• Exception Report

• Expiry Report

For information about these report types, see Report Messages.

The Response page, shown in Figure 10-15, is displayed when you click Next in the Reports page.

You can specify the following properties in the Response page:

• Reply to Queue Name: The name of reply queue name.

• Correlation Scheme: The correlation schema that is used by the Oracle MQ Series Adapter.

  For information about correlation schemas, see Correlation Schemas.

• Schema Options: This option enables you to specify the schema for the message to be dequeued.

  • Choose Other Schema: This option enables you to choose your schema for the message to be dequeued.

  • Choose a Predefined Schema: This option enables you to choose a readymade schema that the adapter provides.

When you click Next in the Response page, a Messages page shown in Figure 10-16 is displayed. This page enables you to select the XSD schema file for translation for request and as response message.

For more information about the Messages page, see Enqueue Message.

The outbound dequeue scenario dequeues a single message from a queue using the outbound Oracle MQ Series Adapter by using the Get Message from MQ option in the Operation Type page of the Adapter Configuration Wizard. To enable the outbound dequeue option, you must select the Synchronous option, as shown in Figure 10-29.

Click Next in the Send Message to MQ and Get Reply/Reports page, the Response page, as shown in Figure 10-30, is displayed. You must set the following properties in the Response page:

• QueueName: This is the name of the MQ Series queue from which the message is dequeued. This property is mandatory.

• Response Wait Interval: This is the time (in milliseconds) that the adapter waits if the message is not in the queue. The default value for this property is 0 milliseconds. This property is not mandatory. The permitted value for this property is any integer value (>=0). The value of this property must be less than that of the timeout for outbound activity.

  Note:

  The ResponseWaitInterval value must be less than the timeout interval for the outbound activity. If the ResponseWaitInterval value exceeds the outbound activity timeout, then the adapter can behave ambiguously.

Optionally, the following two header properties can be used to filter the dequeued message based on Message Id and Correlation Id.:

• jca.mq.MQMD.MsgId: This property sets the message filter option based on the messageId. The value provided for this property must be a hexadecimal-encoded value for some messageId.

• jca.mq.MQMD.CorrelId: This property sets the message filter option based on the correlationId. The value provided for this property must be a hexadecimal-encoded value for some correlationId.

The Oracle MQ Series Adapter supports the following four types of messages:

• Normal Message

  A normal message is sent by one program to another program without expecting any response.

• Request Message

  A request message is sent by one program to another program requesting a response.

• Reply Message

  A reply message is sent by a program in response to a request message.

• Report Message

  A report message is sent by a receiving program to a sending program as confirmation of successful or unsuccessful delivery of a message. A report message can be generated for any of the message types, normal message, request message, or reply message.

  For more information about acknowledgment messages supported by the Oracle MQ Series Adapter, see Report Messages.

You can specify the format for an outgoing message through the Adapter Configuration Wizard, as shown in Figure 10-8. The following message formats are supported:

• No format name (Default)

• Command server request/reply message

• Type 1 command reply message

• Type 2 command reply message

• Dead letter header

• Event message

• User-defined message in programmable command format

• Message consisting entirely of characters

• Trigger message

• Transmission queue header

You can specify the expiry time for an outgoing message by using the Adapter Configuration Wizard, as shown in Figure 10-8. The queue manager discards the message after the expiry time of a message has elapsed.

If a message has expiration notification set, then a notification is generated when the message is discarded. The notification is sent to the queue specified in the replyToQueue parameter. By default, NEVER is set for the expiry field.

You can specify the priority of an outgoing message through the Adapter Configuration Wizard, as shown in Figure 10-8. A priority can be in the range of 0 (low) to 9 (high). You can also specify the priority of the message to be taken from the default priority attribute, as defined by the destination queue. By default, AS_Q_DEF is set as message priority.

You can specify the persistence of an outgoing message through the Adapter Configuration Wizard, as shown in Figure 10-8. If message persistence is not set, then a message is lost when the queue manager restarts or there is a system failure. If you set persistence for a message to true, then it means that the message does not get lost even if there is system failure or the queue manager is restarted. You can also specify the persistence of the message to be taken from the default priority attribute, as defined by the destination queue. The Adapter writes persistent messages to log files and queue data files. If a queue manager is restarted after a failure, it recovers these persistent messages from these files.

For inbound processing, you can configure the inbound MQ Adapter for large payloads by the selecting the Use Large Message Support checkbox while configuring the inbound adapter through the MQ Series Adapter Configuration Wizard. The following screenshot shows this.

At outbound, there is no required configuration for large payload support. But two optional configurations are important for outbound processing:

1. SegmentIfRequired property: By default, this property is set to TRUE; you can configure this by using the Allow message to segmented when necessary checkbox while configuring the outbound MQ adapter. You must set this boolean property to true if you want the MQ Adapter to break large messages into smaller segments. If this property is set to false, and the size of the message exceeds the maximum message size allowed by the queue, channel or queue manager, the MQ server does not permit putting the message into the queue and the MQ Adapter throws an exception.

2. MaximumSegmentLength: By default set to Maximum Allowed, you can configure this property by using the Maximum Segment Length, radio buttons while configuring the outbound MQ adapter through the wizard. By selecting the Custom, radio button, you can configure a user-defined message segment length and the adapter segments the message in that size. When Maximum Allowed radio button is selected, the MQ Adapter segments the messages into the maximum segment size that the outbound queue, channel and queue manager allow.

Note that if the custom segment value provided is higher than that allowed on the MQ server, then the value specified by the server will be honored.

The following figure shows the two configurations.

The Message Selector feature appears on the Get Messages from MQ Screen in the MQ Adapter Wizard. When you specify a Message Selector, the Wizard places the selector information you specify in the activation-spec. As you can see in Figure 10-42, the Message Selector field is directly below the Queue Name field.

A message selector enables you to specify which messages the selector is interested in to dequeue from the MQ queue. Only those messages whose headers and properties match the selector are dequeued.

A message satisfies the selector if the selector evaluates to true when the message's header fields and property values are substituted for their corresponding identifiers in the selector.

A message selector is defined as an activation spec property when you use the MQ Configuration Wizard Adapter to configure the inbound MQ Adapter. A sample message selector follows:

Example - Sample Message Selector for Inbound MQ Adapter

<property name="MessageSelector" value="((jca.mq.MQMD.Priority BETWEEN 0 AND 3) AND NOT(jca.mq.MQMD.Priority = 1)) AND jca.mq.MQMD.PutApplName LIKE 'WebSph_re MQ%' AND jca.mq.MQMD.MsgType NOT IN (0, 1) AND (jca.mq.MQMD.ReplyToQ = 'test_q2' OR jca.mq.MQMD.ReplyToQ IS NULL) AND name = 'Joe'"/>

If the MessageSelector is not defined, the MQ Adapter does not do any message selection and dequeues all the messages that arrive on the queue.

<property name="MessageSelector" value="((jca.mq.MQMD.Priority BETWEEN 0 AND 3) AND NOT(jca.mq.MQMD.Priority = 1)) AND jca.mq.MQMD.PutApplName LIKE 'WebSph_re MQ%' AND jca.mq.MQMD.MsgType NOT IN (0, 1) AND (jca.mq.MQMD.ReplyToQ = 'test_q2' OR jca.mq.MQMD.ReplyToQ IS NULL) AND name = 'Joe'"/>

jca.mq.MQMD.MsgId LIKE '414D51206C6F63616C5F716D%'
    AND jca.mq.MQMD.Priority >
      AND NOT (jca.mq.MQMD.MsgType = 2) 
       AND jca.mq.MQMD.ReplyToQ IN ('queue12', 'queue49')

<property name="MessageSelector" value=
     " jca.mq.MQMD.MsgId LIKE '414D51206C6F63616C5F716D%'
        AND jca.mq.MQMD.Priority > 4 AND NOT 
         (jca.mq.MQMD.MsgType = 2) AND jca.mq.MQMD.ReplyToQ
          IN ('queue12', 'queue49')"/>

jca.mq.MQMD.CorrelId LIKE 
   '414D51206C6F63616C5F716D20202020%' 
    AND jca.mq.MQMD.MsgType = 2 

jca.mq.MQMD.CorrelId LIKE 
     '414D5120514D5F616E6B7072616B615F%' AND jca.mq.MQMD.MsgType
        = 2 AND jca.mq.MQMD.Priority > 5

<property name="MessageSelector" value=" 
             jca.mq.MQMD.CorrelId LIKE 
              '414D51206C6F63616C5F716D20202020%'
                 AND jca.mq.MQMD.MsgType = 2"/>

<property name="MessageSelector" value="        jca.mq.MQMD.CorrelId LIKE           '414D5120514D5F616E6B7072616B615F %            ' AND jca.mq.MQMD.MsgType = 2               AND jca.mq.MQMD.Priority > 5"/>

1. In JDeveloper, click File and select New.

   The New Gallery dialog is displayed.

2. Expand the General node, and select the Applications category.
3. In the Items list, select Generic Application and click OK. The Create Generic Application Wizard is displayed.
4. In the Name Your Application screen, enter De-queueEn-queue in the Application Name field, as shown in Figure 10-43, and then click Next. The Name Your Project screen is displayed.

   Figure 10-43 The Name Your Application Page

   
   Description of "Figure 10-43 The Name Your Application Page"
5. In the Project Name field, enter De-queueEn-queueComposite and from the Available list, select SOA and click the right-arrow button, as shown in Figure 10-44.

   Figure 10-44 The Name Your Project Page

   
   Description of "Figure 10-44 The Name Your Project Page"
6. Click Next. The Configure SOA Settings screen is displayed.
7. In the Composite Template list, select Composite With BPEL, as shown in Figure 10-45, and then click Finish. The Create BPEL Process dialog is displayed.

   Figure 10-45 The Configure SOA Settings Page

   
   Description of "Figure 10-45 The Configure SOA Settings Page"
8. Enter BPELdequeueenqueue in the Name field, and select Define Service Later from the Template box, as shown in Figure 10-46.

   Figure 10-46 The Create BPEL Process Dialog

   
   Description of "Figure 10-46 The Create BPEL Process Dialog"
9. Click OK. The De-queueEn-queue application and the De-queueEn-queue project appears in the design area, as shown in Figure 10-47.

   Figure 10-47 The JDeveloper - Composite.xml

   
   Description of "Figure 10-47 The JDeveloper - Composite.xml"
10. Copy the address-csv.xsd and address-fixedLength.xsd files that you created (see Prerequisites) to the xsd folder in your project.

1. Drag and drop MQ Adapter from the Components window into the Exposed Services swim lane. The Adapter Configuration Wizard Welcome page is displayed.
2. Enter InboundService in the Service Name field, and click Next. The MQ Series Connection screen is displayed.
3. Accept the default JNDI name for the MQ Series connection, and click Next. The Adapter Interface page is displayed.

   Figure 10-48 The MQ Series Connection Page

   
   Description of "Figure 10-48 The MQ Series Connection Page"
4. Select Define from operation and schema (specified later), and click Next. The Operation Type page is displayed.
5. Select Get Message from MQ, and click Next. The Get Message from MQ page is displayed.
6. Enter test_in in the Queue Name field, and click Next. The Messages page is displayed.

   Figure 10-49 The Get Message From MQ Page

   
   Description of "Figure 10-49 The Get Message From MQ Page"
7. Click Browse at the end of the URL field. The Type Chooser dialog is displayed.
8. Select Project Schema Files, address-csv.xsd, and then Root-Element.

   Figure 10-50 The Type Chooser Dialog

   
   Description of "Figure 10-50 The Type Chooser Dialog"
9. Click OK. The address-csv.xsd file appears in the URL field in the Messages page.

   Figure 10-51 The Messages Page

   
   Description of "Figure 10-51 The Messages Page"
10. Click Next. The JCA Endpoint Properties screen is displayed.
    The JCA Endpoint Properties screen appears for inbound only if you have selected the Reference Configuration option. For more information, see JCA Endpoint Properties in the Adapter Configuration Wizard.
11. Click Next. The Finish page is displayed.
12. Click Finish. You have now configured the inbound adapter service, and the composite.xml page is displayed.

    Figure 10-52 The JDeveloper Page - Composite.xml Page

    
    Description of "Figure 10-52 The JDeveloper Page - Composite.xml Page"

1. Drag and drop MQ Adapter from the Components window into the External References swim lane. The Adapter Configuration Wizard Welcome page is displayed.
2. Enter OutboundService in the Service Name field, and click OK. The MQ Series Connection page is displayed.
3. Accept the default JNDI name for the MQ Series connection, and click Next. The Adapter Interface page is displayed.
4. Select Define from operation and schema (specified later), and click Next. The Operation Type page is displayed.
5. Select Put Message into MQ, and click Next. The Put Message into MQ page is displayed.
6. Enter test_out in the Queue Name field, and click Next. The Advanced Options page is displayed.

   Figure 10-53 The Advanced Options Page

   
   Description of "Figure 10-53 The Advanced Options Page"
7. Accept the defaults and click Next. The Messages page is displayed.
8. Click Browse at the end of the URL field. The Type Chooser dialog is displayed.
9. Select Project Schema Files, address-fixedLength.xsd, and then Root-Element, and click OK. The address-fixedLength.xsd file appears in the URL field in the Messages page.
10. Click Next. The Finish page is displayed.
11. Click Finish. You have now configured the outbound adapter service, and the composite.xml page is displayed.

    Figure 10-54 The JDeveloper Page - composite.xml Page

    
    Description of "Figure 10-54 The JDeveloper Page - composite.xml Page"

1. Drag the small triangle in the InboundService in the Exposed Services area to the drop zone that appears as a green triangle in the BPEL process in the Components area.
2. Drag the small triangle in the BPEL process in the Components area to the drop zone that appears as a green triangle in OutboundService in the External References area.

   The JDeveloper Composite.xml appears, as shown in Figure 10-55.

   Figure 10-55 The JDeveloper - Composite.xml

   
   Description of "Figure 10-55 The JDeveloper - Composite.xml"
3. Click File, Save All.
4. Double-click BPELdequeueenqueue. The BPELdequeueenqueue.bpel page is displayed.
5. Drag and drop the Receive, Transform, and Invoke activities in the order mentioned from the Components window to the Components area.

   The JDeveloper BPELdequeueenqueue.bpel page is displayed, as shown in Figure 10-56.

   Figure 10-56 The BPELdequeueenqueue.bpel Page

   
   Description of "Figure 10-56 The BPELdequeueenqueue.bpel Page"
6. Drag and drop the Receive activity to InboundService. The Receive dialog is displayed.
7. Click the Auto Create Variable icon that appears at the end of the Variable field. The Create Variable dialog is displayed.
8. Accept the defaults, and click OK.
9. Check the Create Instance box, and click OK.
10. Drag and drop the Invoke activity to OutboundService. The Invoke dialog is displayed.
11. Click the Automatically Create Input Variable icon that appears at the end of the Input Variable field.
12. Accept the defaults, and click OK. The Invoke dialog is displayed.
13. Click OK.
14. Double-click the Transform activity. The Transform dialog is displayed.
15. Click the Create... (Alt+N) icon. The Source Variable dialog is displayed.
16. Accept the defaults, and click OK.
17. Select the invoke variable as target, and click OK. The Transformation_xsl page is displayed.
18. Drag and drop tns:Root-Element in the Sources pane to the fix:Root-Element in the Target pane. The Auto Map Preferences dialog is displayed.
19. Click OK. The Transformation_xsl page is displayed, as shown in Figure 10-57.

    Figure 10-57 The Transformation_xsl Page

    
    Description of "Figure 10-57 The Transformation_xsl Page "

    The BPELdequeueenqueue.bpel page appears, as shown in Figure 10-58.

    Figure 10-58 The BPELdequeueenqueue.bpel Page

    
    Description of "Figure 10-58 The BPELdequeueenqueue.bpel Page "

1. Create an application server connection. For more information, see Creating an Application Server Connection for Oracle JCA Adapters.
2. Deploy the application. For more information, see Deploying Oracle JCA Adapter Applications from JDeveloper.

1. Navigate to http://servername:portnumber/em. The composite you deployed appears in the application navigator.
2. In the left pane, navigate to SOA, soa-infra (soa_server1). A list of all the composites that are deployed appears.
3. Click De-queueEn-queueComposite[1.0]. The De-queueEn-queueComposite[1.0] page is displayed.
4. Copy the data.txt file and put it in the test_in queue.
5. Wait for some time and then refresh the Fusion Middleware Control Console. An instance appears on the console. This is the instance that was triggered because of the processing that occurred.
6. Click the Instances tab.
7. Click the instance associated with this deployment. The Flow Trace page is displayed.
8. Click the BPELdequeueenqueue component instance. The Audit Trail page is displayed.
9. Click the Flow tab to view the process flow. Click an activity to view the details of the activity.

1. In JDeveloper, click File and select New.

   The New Gallery dialog is displayed.

2. Expand the General node, and select the Applications category.
3. In the Items list, select Generic Application and click OK. The Create Generic Application Wizard is displayed.
4. In the Name Your Application screen, enter SyncReqRes in the Application Name field, and then click Next. The Name Your Project screen is displayed.
5. In the Project Name field, enter Sync_ReqRes and from the Available list, select SOA and click the right-arrow button.
6. Click Next. The Configure SOA Settings screen is displayed.
7. In the Composite Template list, select Composite With BPEL and then click Finish. The Create BPEL Process dialog is displayed.

   The Application Navigator of JDeveloper is updated with the new application and project and the Design tab contains, a blank palette.

8. Enter BPELsyncreqres in the Name field, select Define Service Later from the Template box.
9. Click OK. The SyncReqRes application and Sync_ReqRes project appear in the design area, as shown in Figure 10-59.

   Figure 10-59 The JDeveloper - Composite.xml

   
   Description of "Figure 10-59 The JDeveloper - Composite.xml"

1. Drag and drop MQ Adapter from the Components window into the Exposed Services swim lane. The Adapter Configuration Wizard Welcome page is displayed.
2. Enter inbound_reqres in the Service Name field, and click Next. The MQ Series Connection page is displayed.
3. Accept the default JNDI name for the MQ Series connection JNDI name, and click Next. The Adapter Interface page is displayed.
4. Select Define from operation and schema (specified later), and click Next. The Operation Type page is displayed.
5. Select Get Message from MQ and Send Reply/Reports, and select Synchronous, and click Next. The Get Message from MQ and Send Reply/Reports page is displayed.
6. Select Normal in the Message Type box, and enter test_in in the Queue Name field.
7. Click Next. The Response page is displayed.
8. Accept the defaults, and click Next. The Messages page is displayed.
9. Select Project Schema Files, address-csv.xsd, and then Root-Element, and click OK. The address-csv.xsd file appears in the URL field in the Messages page.
10. In the Send Message Schema group, click Browse at the end of the URL field. The Type Chooser dialog is displayed.
11. Select Project Schema Files, address-fixedLength.xsd, and then Root-Element, and click OK. The address-fixedLength.xsd file appears in the URL field in the Messages page.
12. Click Next. The JCA Endpoint Properties screen is displayed.
    The JCA Endpoint Properties screen appears for inbound if you have selected the Reference Configuration option. For more information, see JCA Endpoint Properties in the Adapter Configuration Wizard.
13. Click Next. The Finish page is displayed.
14. Click Finish. You have now configured the inbound adapter service, and the composite.xml page is displayed.

    Figure 10-60 The JDeveloper Page - Composite.xml Page

    
    Description of "Figure 10-60 The JDeveloper Page - Composite.xml Page"
15. Click File, then Save All.

1. Drag and drop the inbound_reqres adapter service to the BPELsyncreqres BPEL process.
2. Double-click BPELsyncreqres. The BPELsyncreqres.bpel page is displayed.
3. Drag and drop the Receive, Transform, and Reply activities in the order mentioned from the Components window to the Components area.
4. Drag and drop the Receive activity to the inbound_reqres adapter service. The Receive dialog is displayed.
5. Enter ReadMsg in the Name field.
6. Click the Auto Create Variable icon that appears at the end of the Variable field. The Create Variable dialog is displayed.
7. Accept the defaults, and click OK.
8. Check the Create Instance box in the Receive dialog, and click OK.
9. Drag and drop the Reply activity to the inbound_reqres adapter service. The Reply dialog is displayed.
10. Enter ReplyMsg in the Name field.
11. Click the Auto Create Variable icon that appears at the end of the Variable field. The Create Variable dialog is displayed.
12. Accept the defaults, and click OK. The variable appears in the Reply dialog.
13. Click OK.
14. Double-click the Transform activity. The Transform dialog is displayed.
15. Click the plus icon. The Source Variable dialog is displayed.
16. From the Source Variable list, select ReadMsg_DequeueEnqueue_InputVariable, and click OK.
17. From the Target Variable list, select ReplyMsg_DequeueEnqueue_OutputVariable.
18. Click the Create Mappings icon. The Transformation.xsl page is displayed, as shown in Figure 10-61.

    Figure 10-61 The Transformation.xsl Page

    
    Description of "Figure 10-61 The Transformation.xsl Page"
19. Drag the tns:Root-Element from <sources> panel to the fix:Root-Element of the <target> panel. The Auto Map Preferences dialog is displayed.
20. Click OK. The JDeveloper BPELsyncreqres.bpel page is displayed, as shown in Figure 10-62.

    Figure 10-62 The BPELsyncreqres.bpel Page

    
    Description of "Figure 10-62 The BPELsyncreqres.bpel Page "

1. Create an application server connection. For more information, see Creating an Application Server Connection for Oracle JCA Adapters.
2. Deploy the application. For more information, see Deploying Oracle JCA Adapter Applications from JDeveloper.

1. Navigate to http://servername:portnumber/em.
2. In the left pane, navigate to SOA, soa-infra (soa_server1). A list of all the composites that are deployed appears.
3. Click Sync_ReqRes[1.0]. The Sync_ReqRes[1.0] page is displayed.
4. Create an MQ message with the contents of the data.txt file and set replyToQueueName to test_reply. Put this message in the test_in queue.
5. Wait for some time and then refresh the Fusion Middleware Control Console. An instance appears on the console. This is the instance that was triggered because of the processing that occurred.
6. Click the Instances tab.
7. Click the instance associated with this deployment. The Flow Trace page is displayed.
8. Click the BPELsyncreqres component instance. The Audit Trail page is displayed.
9. Click the Flow tab to debug the instance. The BPEL process instance flow is displayed.
10. Click an activity to view the relevant payload details.

1. In JDeveloper, click File and select New.

   The New Gallery dialog is displayed.

2. Expand the General node, and select the Applications category.
3. In the Items list, select Generic Application and click OK. The Create Generic Application Wizard is displayed.
4. In the Name Your Application screen, enter Sync-Req-Rep in the Application Name field, and then click Next. The Name Your Project screen is displayed.
5. In the Project Name field, enter Sync-Req-RepComposite and from the Available list, select SOA and click the right-arrow button.
6. Click Next. The Configure SOA Settings screen is displayed.
7. In the Composite Template list, select Composite With BPEL and then click Finish. The Create BPEL Process dialog is displayed.
8. Enter BPELSyncreqrep in the Name field, select Define Service Later from the Template box.
9. Click OK. The Sync-Req-Rep application and Sync-Req-RepComposite project appear in the design area, as shown in Figure 10-63.

   Figure 10-63 The JDeveloper - Composite.xml

   
   Description of "Figure 10-63 The JDeveloper - Composite.xml"

1. Drag and drop MQ Adapter from the Components window into the Exposed Services swim lane. The Adapter Configuration Wizard Welcome page is displayed.
2. Enter InboundReqRepService in the Service Name field, and click Next. The MQ Series Connection page is displayed.
3. Accept the default JNDI name for the MQ Series connection, and click Next. The Adapter Interface page is displayed.
4. Select Define from operation and schema (specified later), and click Next. The Operation Type page is displayed.
5. Select Get Message from MQ and Send Reply/Reports and Synchronous in the Operation Name box, and click Next. The Get Message from MQ and Send Reply/Reports page is displayed.
6. Select Normal in the Message Type list and enter test_in in the Queue Name field and select Choose Other Schema in the Schema Options box, and click Next. The Response page is displayed.
7. Accept the defaults and click Next. The Message page is displayed.
8. Click Browse in the Get Message Schema box that appears at the end of the URL field. The Type Chooser dialog is displayed.
9. Select Project Schema Files, address-csv.xsd, and Root-Element, and then click OK. The Message page is populated with the address-csv.xsd file in the Get Message Schema box.
10. Click Browse in the Send Message Schema box that appears at the end of the URL field. The Type Chooser dialog is displayed.
11. Select Project Schema Files, address-fixedLength.xsd, and Root-Element, and then click OK. The Message page is populated with the address-fixedLength.xsd file in the Send Message Schema box.
12. Click Next. The JCA Endpoint Properties screen is displayed.
    The JCA Endpoint Properties screen appears for inbound if you have selected the Reference Configuration option. For more information, see JCA Endpoint Properties in the Adapter Configuration Wizard.
13. Click Next. The Finish page is displayed.
14. Click Finish. You have configured the InboundReqRepService adapter service, and the composite.xml page is displayed.

    Figure 10-64 The JDeveloper Page - Composite.xml Page

    
    Description of "Figure 10-64 The JDeveloper Page - Composite.xml Page"

1. Drag and drop MQ Adapter from the Components window into the External References swim lane. The Adapter Configuration Wizard Welcome page is displayed.
2. Enter OutboundReqRepService in the Service Name field, and click OK. The MQ Series Connection page is displayed.
3. Accept the defaults and click Next. The Adapter Interface page is displayed.
4. Select Define from operation and schema (specified later), and click Next. The Operation Type page is displayed.
5. Select Send Message to MQ and Get Reply/Reports, select Synchronous in the Operation Name box, and click Next. The Send Message to MQ and Get Reply/Reports page is displayed.
6. Enter test1 in the Queue Name field and click Next. The Response page is displayed.
7. Enter the name of the queue in the Reply To Queue Name field such as ReplyQ, select the Response Wait Interval option and enter a value, and select the Empty Response Message Allowed option.
8. Click Next. The Advanced Options page is displayed.
9. Accept the default values and click Next. The Messages page is displayed.
10. Click Browse in the Get Message Schema box that appears at the end of the URL field. The Type Chooser dialog is displayed.
11. Select Project Schema Files, address-csv.xsd, and Root-Element, and then click OK. The Message page is populated with address-csv.xsd file in the Get Message Schema box.
12. Click Browse in the Send Message Schema box that appears at the end of the URL field. The Type Chooser dialog is displayed.
13. Select Project Schema Files, address-fixedLength.xsd, and Root-Element, and then click OK. The Message page is populated with address-fixedLength.xsd file in the Send Message Schema box.
14. Click Next. The Finish page is displayed.
15. Click Finish. You have configured the OutboundReqRepService service, and the composite.xml page is displayed.

    Figure 10-65 The JDeveloper Page - Composite.xml Page

    
    Description of "Figure 10-65 The JDeveloper Page - Composite.xml Page"

1. Drag the small triangle in the InboundReqRepService service in the Exposed Services area to the drop zone that appears as a green triangle in BPELSyncreqrep in the Components area.
2. Drag the small triangle in BPELSyncreqrep in the Components area to the drop zone that appears as a green triangle in OutboundReqRepService in the External References area.
3. Similarly, drag the small triangle in BPELSyncreqrep in the Components area to the drop zone in OutboundReqRepService in the External References area.

   The JDeveloper composite.xml page appears, as shown in Figure 10-66.

   Figure 10-66 The JDeveloper - Composite.xml

   
   Description of "Figure 10-66 The JDeveloper - Composite.xml"
4. Click File, Save All.
5. Double-click BPELSyncreqrep. The BPELSyncreqrep.bpel page is displayed.
6. Drag and drop the Receive, Transform, Invoke, Assign, Reply activities in the order mentioned from the Components window to the Components area. The JDeveloper BPELSyncreqrep.bpel page is displayed, as shown in Figure 10-67.

   Figure 10-67 The BPELSyncreqrep.bpel Page

   
   Description of "Figure 10-67 The BPELSyncreqrep.bpel Page"
7. Drag and drop the Receive activity to InboundReqRepService. The Receive dialog is displayed.
8. Click the Auto Create Variable icon that appears at the end of the Variable field. The Create Variable dialog is displayed.
9. Accept the defaults, and click OK.
10. Check the Create Instance box, as shown in Figure 10-68, and click OK.

    Figure 10-68 The Receive Dialog

    
    Description of "Figure 10-68 The Receive Dialog"
11. Drag and drop the Reply activity to InboundReqRepService. The Reply dialog is displayed.
12. Click the Auto Create Variable icon to create the variable, and then click OK. The Reply dialog is displayed, as shown in Figure 10-69.

    Figure 10-69 The Reply Dialog

    
    Description of "Figure 10-69 The Reply Dialog"
13. Drag and drop the Invoke activity to the OutboundReqRepService service. The Invoke dialog is displayed.
14. Click the Automatically Create Input Variable icon that appears at the end of the Input Variable field. The Create Variable dialog is displayed.
15. Click OK.
16. Similarly, create the output variable. Accept the defaults, and click OK. The Invoke dialog is displayed, as shown in Figure 10-70.

    Figure 10-70 The Invoke Dialog

    
    Description of "Figure 10-70 The Invoke Dialog"
17. Click OK.
18. Double-click the Transform activity. The Transform dialog is displayed.
19. Click the plus icon, and select Receive_1_DequeueEnqueue_InputVariable as the source variable. Then, select Invoke_1_EnqueueDequeue_InputVariable for the target variable, as shown in Figure 10-71.

    Figure 10-71 The Transform Dialog

    
    Description of "Figure 10-71 The Transform Dialog"
20. Click Create Mapping. The Transformation_1.xsl page is displayed.
21. Drag and drop the tns:Root-Element from the from <sources> panel to fix:Root-Element in the <target> panel. The Auto Map Preferences dialog is displayed.
22. Click OK. The mappings appear in the Transformation.xsl page, as shown in Figure 10-72.

    Figure 10-72 The Transformation.xsl Page with Mappings

    
    Description of "Figure 10-72 The Transformation.xsl Page with Mappings"
23. Click the BPELSyncreqrep.bpel tab.
24. Double-click the Assign activity. The Assign dialog is displayed.
25. Click the plus icon, and select Copy Operation. The Create Copy Operation dialog is displayed.
26. Select the variables, as shown in Figure 10-73, and click OK.

    Figure 10-73 The Create Copy Operation Dialog

    
    Description of "Figure 10-73 The Create Copy Operation Dialog"
27. Click OK in the Assign dialog. The JDeveloper BPELSyncreqrep.bpel page is displayed, as shown in Figure 10-74.

    Figure 10-74 The BPELSyncreqrep.bpel Page

    
    Description of "Figure 10-74 The BPELSyncreqrep.bpel Page"

1. Create an application server connection. For more information, see Creating an Application Server Connection for Oracle JCA Adapters.
2. Deploy the application. For more information, see Deploying Oracle JCA Adapter Applications from JDeveloper.

1. Navigate to http://servername:portnumber/em.
2. In the left pane, navigate to SOA, soa-infra (soa_server1). A list of all the composites that are deployed appears.
3. Click Sync-Req-RepComposite[1.0]. The Sync-Req-RepComposite[1.0] page is displayed.
4. Create an MQ message with the contents of the data.txt file and set replyToQueueName to test_reply. Put this message in the test_in queue.
5. Wait for some time and then refresh the Fusion Middleware Control Console. An instance appears on the console. This is the instance that was triggered because of the processing that occurred.
6. Click the Instances tab.
7. Click the instance associated with this deployment. The Flow Trace page is displayed.
8. Click the BPELSyncreqrep component instance. The Audit Trail page is displayed.
9. Click the Flow tab to debug the instance. The BPEL process instance flow is displayed.
10. Click an activity to view the relevant payload details.

1. In JDeveloper, click File and select New.

   The New Gallery dialog is displayed.

2. Expand the General node, and select the Applications category.
3. In the Items list, select Generic Application and click OK. The Create Generic Application Wizard is displayed.
4. In the Name Your Application screen, enter AsynchronousRequestReply in the Application Name field, and then click Next. The Name Your Project screen is displayed.
5. In the Project Name field, enter Async-Req-RepComposite and from the Available list, select SOA and click the right-arrow button.
6. Click Next. The Configure SOA Settings screen is displayed.
7. In the Composite Template list, select Composite With BPEL and then click Finish. The Create BPEL Process dialog is displayed.
8. Enter BPELAsyncreqrep in the Name field, and select Define Service Later from the Template box.
9. Click OK. The AsynchronousRequestReply application and the Async-Req-RepComposite project appear in the design area, as shown in Figure 10-75.

   Figure 10-75 The JDeveloper - Composite.xml

   
   Description of "Figure 10-75 The JDeveloper - Composite.xml"

1. Drag and drop MQ Adapter from the Components window into the Exposed Services swim lane. The Adapter Configuration Wizard Welcome page is displayed.
2. Enter InboundService in the Service Name field, and click Next. The MQ Series Connection page is displayed.
3. Accept the default JNDI name for the MQ Series connection, and click Next. The Adapter Interface page is displayed.
4. Select Define from operation and schema (specified later), and click Next. The Operation Type page is displayed.
5. Select Get Message from MQ and click Next. The Get Message from MQ page is displayed.
6. Enter test_in in the Queue Name field and click Next. The Messages page is displayed.
7. Select Native Format Translation is not required (Schema is Opaque) and click Next. The Finish page is displayed.
8. Click Next. The JCA Endpoint Properties screen is displayed.
   The JCA Endpoint Properties screen appears for inbound if you have selected the Reference Configuration option. For more information, see JCA Endpoint Properties in the Adapter Configuration Wizard.
9. Click Finish. You have configured the inbound adapter service, and the composite.xml page is displayed.

   Figure 10-76 The JDeveloper Page - Composite.xml Page

   
   Description of "Figure 10-76 The JDeveloper Page - Composite.xml Page"

1. Drag and drop MQ Adapter from the Components window into the External References swim lane. The Adapter Configuration Wizard Welcome page is displayed.
2. Enter asyn-Req-Res in the Service Name field, and click OK. The MQ Series Connection page is displayed.
3. Accept the default JNDI name for the MQ Series connection, and click Next. The Adapter Interface page is displayed.
4. Select Define from operation and schema (specified later), and click Next. The Operation Type page is displayed.
5. Select Send Message to MQ and Get Reply/Reports and select Asynchronous in the Operation Name box, and then click Next. The Send Message to MQ and Get Reply/Reports page is displayed.
6. Select Normal in the Message Type box and enter test_out in the Queue Name field, and then select the Get Reports check box, and click Next. The Reports page is displayed.
7. Select Confirmation on Arrival, and click Next. The Response page is displayed.

   Figure 10-77 The Adapter Configuration Wizard Reports Page

   
   Description of "Figure 10-77 The Adapter Configuration Wizard Reports Page"
8. Enter test_out in the Reply To Queue Name field, and click Next. The Advanced Options page is displayed.
9. Accept the default values, and click Next. The Messages page is displayed.
10. Select Native Format Translation is not Required(Schema is Opaque) in both the Get Message Schema and Send Message Schema boxes, and click Next. The Finish page is displayed.
11. Click Finish. You have configured the async-Req-Res service, and the composite.xml page is displayed.

1. Drag and drop MQ Adapter from the Components window into the External References swim lane. The Adapter Configuration Wizard Welcome page is displayed.
2. Click Next. The Service Name page is displayed.
3. Enter OutboundService in the Service Name field, and click OK. The MQ Series Connection page is displayed.
4. Accept the default JNDI name for the MQ Series connection, and click Next. The Adapter Interface page is displayed.
5. Select Define from operation and schema (specified later), and click Next. The Operation Type page is displayed.
6. Select Put Message into MQ, and click Next. The Put Message into MQ page is displayed.
7. Enter test_demo in the Queue Name field, and click Next. The Advanced Options page is displayed.
8. Accept the default values, and click Next. The Messages page is displayed.
9. Select Native Format Translation is not required(Schema is Opaque), and click Next. The Finish page is displayed.
10. Click Finish. You have configured the OutboundService service, and the composite.xml page is displayed, as shown in Figure 10-79.

    Figure 10-79 The JDeveloper Page - Composite.xml Page

    
    Description of "Figure 10-79 The JDeveloper Page - Composite.xml Page"

1. Drag the small triangle in the InboundService service in the Exposed Services area to the drop zone that appears as a green triangle in the BPEL process in the Components area.
2. Drag the small triangle in the BPEL process in the Components area to the drop zone that appears as a green triangle in async-Req-Res in the External References area.
3. Similarly, drag the small triangle in the BPEL process in the Components area to the drop zone in OutboundService in the External References area.

   The JDeveloper Composite.xml appears, as shown in Figure 10-80.

   Figure 10-80 The JDeveloper - Composite.xml

   
   Description of "Figure 10-80 The JDeveloper - Composite.xml"
4. Click File, Save All.
5. Double-click BPELAsyncreqrep. TheDequeueEnqueueRFH2.bpel page is displayed.
6. Drag and drop the Receive, Assign, Invoke, Receive, Assign, Invoke activities in the order mentioned from the Components window to the Components area. The JDeveloper BPELAsyncreqrep.bpel page is displayed, as shown in Figure 10-81.

   Figure 10-81 The BPELAsyncreqrep.bpel Page

   
   Description of "Figure 10-81 The BPELAsyncreqrep.bpel Page"
7. Drag and drop the first Receive activity to the InboundService adapter service. The Receive dialog is displayed.
8. Click the Auto Create Variable icon that appears at the end of the Variable field. The Create Variable dialog is displayed.
9. Accept the defaults, and click OK.
10. Check the Create Instance box, and click OK.
11. Drag and drop the first Invoke activity to the async-Req-Res service. The Invoke dialog is displayed.
12. Click the Automatically Create Input Variable icon that appears at the end of the Input Variable field.
13. Accept the defaults, and click OK. The Invoke dialog is displayed.
14. Click OK.
15. Drag and drop the second Receive activity to the async-Req-Rep service. The Receive dialog is displayed.
16. Click the Auto Create Variable icon to create variable.

    Note:

    Do not check the Create Instance box.

17. Click OK in the Receive dialog.
18. Drag and drop the second Invoke activity to OutboundService. The Invoke dialog is displayed.
19. Click the Automatically Create Input Variable icon to create a variable.
20. Click OK in the Invoke dialog.
21. Double-click the first Assign activity. The Assign dialog is displayed.
22. Click the plus icon, and select Copy Operation. The Create Copy Operation dialog is displayed.
23. Select the variables, as shown in Figure 10-82, and click OK.

    Figure 10-82 The Create Copy Operation Dialog

    
    Description of "Figure 10-82 The Create Copy Operation Dialog"
24. Click OK in the Assign dialog.
25. Double-click the second Assign activity. The Assign dialog is displayed.
26. Click the plus icon, and select Copy Operation. The Create Copy Operation dialog is displayed.
27. Select the variables, as shown in Figure 10-83, and click OK.

    Figure 10-83 The Create Copy Operation Dialog

    
    Description of "Figure 10-83 The Create Copy Operation Dialog"
28. Click OK in the Assign dialog. The JDeveloper BPELAsyncreqrep.bpel page is displayed, as shown in Figure 10-84.

    Figure 10-84 The BPELAsyncreqrep.bpel Page

    
    Description of "Figure 10-84 The BPELAsyncreqrep.bpel Page"

1. Create an application server connection. For more information, see Creating an Application Server Connection for Oracle JCA Adapters.
2. Deploy the application. For more information, see Deploying Oracle JCA Adapter Applications from JDeveloper.

1. Navigate to http://servername:portnumber/em.
2. In the left pane, navigate to SOA, soa-infra (soa_server1). A list of all the composites that are deployed appears.
3. Click Async-Req-RepComposite[1.0]. The Async-Req-RepComposite[1.0] page is displayed.
4. Put a message that has the content that conforms to the address-csv.xsd and also contains the Reply Queue as the header in the test_in queue.
5. Wait for some time and then refresh the Fusion Middleware Control Console. An instance appears on the console. This is the instance that was triggered because of the processing that occurred.
6. Click the Instances tab.
7. Click the instance associated with this deployment. The Flow Trace page is displayed.
8. Click the BPELAsyncreqrep component instance. The Audit Trail page is displayed.
9. Click the Flow tab to debug the instance. The BPEL process instance flow is displayed.
10. Click an activity to view the relevant payload details.

1. In JDeveloper, click File and select New.

   The New Gallery dialog is displayed.

2. Expand the General node, and select the Applications category.
3. In the Items list, select Generic Application and click OK. The Create Generic Application Wizard is displayed.
4. In the Name Your Application screen, enter OutboundDequeue in the Application Name field, and then click Next. The Name Your Project screen is displayed.
5. In the Project Name field, enter OutboundDequeueComposite and from the Available list, select SOA and click the right-arrow button.
6. Click Next. The Configure SOA Settings screen is displayed.
7. In the Composite Template list, select Composite With BPEL and then click Finish. The Create BPEL Process dialog is displayed.
8. Enter BPELOutboundDequeue in the Name field, select Synchronous BPEL Process in the Template box.
9. Click Browse at the end of the Input field. The Type Chooser dialog is displayed.
10. Select Project Schema Files, singleString.xsd, singleString, and then click OK.
11. Click Browse at the end of the Output field. The Type Chooser dialog is displayed.
12. Select Project Schema Files, singleString.xsd, singleString, and then click OK.
13. Click OK. The OutboundDequeue application and OutboundDequeueComposite project appears in the design area, as shown in Figure 10-85.

    Figure 10-85 The JDeveloper - Composite.xml

    
    Description of "Figure 10-85 The JDeveloper - Composite.xml"

1. Drag and drop MQ Adapter from the Components window into the External References swim lane. The Adapter Configuration Wizard Welcome page is displayed.
2. Enter OutboundDequeueService in the Service Name field, and click OK. The MQ Series Connection page is displayed.
3. Accept the default JNDI name for the MQ Series connection, and click Next. The Adapter Interface page is displayed.
4. Select Define from operation and schema (specified later), and click Next. The Operation Type page is displayed.
5. Select Get Message from MQ and Synchronous, and click Next. The Get Message from MQ page is displayed.
6. Enter test_out in the Queue Name field and enter 10 in the Wait Interval field, and then click Next. The Messages page is displayed.
7. Click Browse at the end of the URL field. The Type Chooser dialog is displayed.
8. Select Project Schema Files, singleString.xsd, and then singleString, and click OK. The singleString.xsd file appears in the URL field in the Messages page.
9. Click Next. The Finish page is displayed.
10. Click Finish. You have now configured the inbound adapter service, and the composite.xml page is displayed.

    Figure 10-86 The JDeveloper Page - Composite.xml Page

    
    Description of "Figure 10-86 The JDeveloper Page - Composite.xml Page"
11. Click File, Save All.

1. Drag the small triangle in the BPEL process in the Components area to the drop zone that appears as a green triangle in OutboundDequeueService in the External References area.
2. Double-click BPELOutboundDequeue. The BPELOutboundDequeue.bpel page is displayed.
3. Drag and drop the Invoke and Assign activities in the order mentioned from the Components window to the Components area in between the receiveInput and replyOutput activities.

   The composite.xml page is displayed, as shown in Figure 10-87.

   Figure 10-87 The JDeveloper - Composite.xml Page

   
   Description of "Figure 10-87 The JDeveloper - Composite.xml Page"

   The JDeveloper BPELOutboundDequeue.bpel page is displayed, as shown in Figure 10-88.

   Figure 10-88 The BPELOutboundDequeue.bpel Page

   
   Description of "Figure 10-88 The BPELOutboundDequeue.bpel Page"
4. Drag and drop the Invoke activity to the OutboundDequeueService adapter reference. The Invoke dialog is displayed.
5. Click the Auto Create Variable icon that appears at the end of the Input Variable field. The Create Variable dialog is displayed.
6. Accept the defaults, and click OK.
7. Repeat the same for the output variable and click OK.
8. Double-click the Assign activity. The Assign dialog is displayed.
9. Click the plus icon and select Copy Operation. The Create Copy Operation dialog is displayed.
10. Select the variables, as shown in Figure 10-89, and then click OK.

    Figure 10-89 Create Copy Operation Dialog

    
    Description of "Figure 10-89 Create Copy Operation Dialog"
11. Click OK in the Assign dialog.

    The BPELOutboundDequeue.bpel page appears, as shown in Figure 10-90.

    Figure 10-90 The BPELOutboundDequeue.bpel Page

    
    Description of "Figure 10-90 The BPELOutboundDequeue.bpel Page "

1. Create an application server connection. For more information, see Creating an Application Server Connection for Oracle JCA Adapters.
2. Deploy the application. For more information, see Deploying Oracle JCA Adapter Applications from JDeveloper.

1. Navigate to http://servername:portnumber/em.
2. In the left pane, navigate to SOA, soa-infra (soa_server1). A list of all the composites that are deployed appears.
3. Click OutboundDequeueComposite[1.0]. The OutboundDequeueComposite[1.0] page is displayed.
4. Click Test. The Test Web Service page is displayed.
5. Click the Request tab, and scroll to the Input Arguments pane.
6. Enter Test Outbound Dequeue in the Input field, and then click Test Web Service.
7. Wait for some time and then click the Response tab. The message in the singleString xsd that you provided appears in the Response tab.
8. Click the Instances tab.
9. Click the instance associated with this deployment. The Flow Trace page is displayed.
10. Click the BPELOutboundDequeue component instance. The Audit Trail page is displayed, as shown in Figure 10-91.

    Figure 10-91 Audit Trail Page

    
    Description of "Figure 10-91 Audit Trail Page"
11. Click the Flow tab to debug the instance. The BPEL process instance flow is displayed.
12. Click an activity to view the relevant payload details.

1. In JDeveloper, click File and select New.

   The New Gallery dialog is displayed.

2. Expand the General node, and select the Applications category.
3. In the Items list, select Generic Application and click OK. The Create Generic Application Wizard is displayed.
4. In the Name Your Application screen, enter MQ_BackoutQ_Retry in the Application Name field, and then click Next. The Name Your Project screen is displayed.
5. In the Project Name field, enter SOA_BackoutQ_Retry and from the Available list, select SOA and click the right-arrow button.
6. Click Next. The Configure SOA Settings screen is displayed.
7. In the Composite Template list, select Composite With BPEL, and then click Finish. The Create BPEL Process dialog is displayed.
8. Enter BPELProcess_BackoutQ_Retry in the Name field, and select Define Service Later from the Template box.
9. Click OK. The MQ_BackoutQ_Retry application and the SOA_BackoutQ_Retry project appear in the design area.

1. Drag and drop MQ Adapter from the Components window into the Exposed Services swim lane. The Adapter Configuration Wizard Welcome page is displayed.
2. Enter InboundService in the Service Name field, and click Next. The MQ Series Connection page is displayed.
3. Accept the default JNDI name for the MQ Series connection, and click Next. The Adapter Interface page is displayed.
4. Select Define from operation and schema (specified later), and click Next. The Operation Type page is displayed.
5. Select Get Message from MQ and Send Reply/Reports (Synchronous), and click Next. The Get Message from MQ and Send Rep page is displayed.
6. Enter INBOUND_QUEUE in the Queue Name field, and click Next. The Response page is displayed.
7. Accept the defaults, and click Next. The Messages page is displayed.
8. Click Browse at the end of the URL fields. The Type Chooser dialog is displayed.
9. Select Project Schema Files, singleString.xsd, and then singleString.
10. Click OK. The singleString.xsd file appears in the URL fields in the Messages page.
11. Click Next. The JCA Endpoint Properties screen is displayed.
    The JCA Endpoint Properties screen appears for inbound if you have selected the Reference Configuration option. For more information, see JCA Endpoint Properties in the Adapter Configuration Wizard.
12. Click Next. The Finish page is displayed.
13. Click Finish. You have now configured the inbound adapter service, and the composite.xml page is displayed with an inbound adapter added.
14. Add the Backout Queue properties to the corresponding JCA file (ReqReply_mq.jca), as shown in the following sample:

    <property name="BackoutQueueName" value="BACKOUT.QUEUE"/>
    <property name="MaximumBackoutCount" value="5"/>    
    <property name="BackoutRetries" value="3"/>    
    

1. Drag and drop MQ Adapter from the Components window into the External References swim lane. The Adapter Configuration Wizard Welcome page is displayed.
2. Enter EQ in the Service Name field, and click Next. The MQ Series Connection page is displayed.
3. Accept the default JNDI name for the MQ Series connection, and click Next. The Adapter Interface page is displayed.
4. Select Define from operation and schema (specified later), and click Next. The Operation Type page is displayed.
5. Select Put Message into MQ, and click Next. The Put Message into MQ page is displayed.
6. Enter a test_out in the Queue Name field, and click Next. The Advanced Options page is displayed.
7. Accept the defaults and click Next. The Messages page is displayed.
8. Click Browse at the end of the URL field. The Type Chooser dialog is displayed.
9. Select Project Schema Files, singleString.xsd, and then singleString, and click OK. The singleString.xsd file appears in the URL field in the Messages page.
10. Click Next. The Finish page is displayed.
11. Click Finish. You have now configured the outbound adapter service, and the composite.xml page is displayed.

    Figure 10-92 The JDeveloper Page - Composite.xml Page

    
    Description of "Figure 10-92 The JDeveloper Page - Composite.xml Page"

1. Drag the small triangle in the InboundService in the Exposed Services area to the drop zone that appears as a green triangle in the BPEL process in the Components area.
2. Drag the small triangle in the BPEL process in the Components area to the drop zone that appears as a green triangle in OutboundService in the External References area.

   The JDeveloper Composite.xml appears, as shown in Figure 10-93.

   Figure 10-93 The JDeveloper - Composite.xml

   
   Description of "Figure 10-93 The JDeveloper - Composite.xml"
3. Click File, Save All.
4. Double-click BPELProcess_BackoutQ_Retry. The BPELProcess_backoutQ_Retry.bpel page is displayed.
5. Drag and drop the Receive, Assign, Invoke, and Reply activities in the order mentioned from the Components window to the Components area.
6. Drag and drop the Receive activity to ReqReply. The Receive dialog is displayed.
7. Click the Auto Create Variable icon that appears at the end of the Variable field. The Create Variable dialog is displayed.
8. Accept the defaults, and click OK.
9. Check the Create Instance box, and click OK.
10. Drag and drop the Reply activity to ReqReply. The Reply dialog is displayed.
11. Enter ReplyOutput in the Name field.
12. Click the Browse Variables icon that appears at the end of the Variable field. The Variable Chooser dialog is displayed.
13. Select replyOutput_DequeueEnqueue_OutputVariable, and click OK. The variable appears in the Reply dialog.
14. Click OK.
15. Drag and drop the Invoke activity to EQ. The Invoke dialog is displayed.
16. Click the Automatically Create Input Variable icon that appears at the end of the Input Variable field.
17. Accept the defaults, and click OK. The Invoke dialog is displayed.
18. Click OK.
19. Double-click the Assign activity. The Assign dialog is displayed.
20. Click the plus icon, and select Copy Operation. The Create Copy Operation dialog is displayed.
21. In the Create Copy Operation dialog, select receiveInput_DequeueEnqueue_InputVariable as the From Type and select the variable in the To pane to which the copy operation is being created.

    The following is a code snippet from the BPELProcess_BackoutQ_Retry.bpel file, with the copy operation defined:

    <assign name="Assign_1">
          <copy>
            <from variable="receiveInput_DequeueEnqueue_InputVariable"
                  part="singleString" query="/ns3:singleString/ns3:input"/>
            <to variable="Invoke_1_Enqueue_InputVariable" part="body"
                query="/ns3:singleString/ns3:input"/>
          </copy>
          <copy>
            <from variable="receiveInput_DequeueEnqueue_InputVariable"
                  part="singleString" query="/ns3:singleString/ns3:input"/>
            <to variable="replyOutput_DequeueEnqueue_OutputVariable"
                part="singleString" query="/ns3:singleString/ns3:input"/>
          </copy>
        </assign>
    

22. Click OK. The BPELdequeueenqueue.bpel page appears, as shown in Figure 10-94.

    Figure 10-94 The BPELProcess_BackoutQ_Retry.bpel Page

    
    Description of "Figure 10-94 The BPELProcess_BackoutQ_Retry.bpel Page "

1. Create an application server connection. For more information, see Creating an Application Server Connection for Oracle JCA Adapters.
2. Deploy the application. For more information, see Deploying Oracle JCA Adapter Applications from JDeveloper.

1. Navigate to http://servername:portnumber/em. The composite you deployed appears in the application navigator.
2. Disable (Put Inhibit) the test_out queue or the reply queue that is provided with the Inbound message and then put a message to the INBOUND_QUEUE.
3. Wait for some time and then refresh the Fusion Middleware Control Console. Instances that are triggered because of the processing appear on the console.

   Note:

   The number of instances that are triggered must be equal to BackoutRetries + 1.

4. Click the Instances tab.
5. Click an instance associated with this deployment. The Flow Trace page is displayed.
6. Click the BPELProcess_BackoutQ_Retry component instance. The Audit Trail page is displayed.
7. Click the Flow tab to debug the instance. The BPEL process instance flow is displayed.
8. Click an activity to view the relevant payload details.

1. In JDeveloper, click File and select New.

   The New Gallery dialog is displayed.

2. Expand the General node, and select the Applications category.
3. In the Items list, select SOA Application and click OK. The Create SOA Application Wizard is displayed.
4. In the Name Your Application screen, enter MQAsAttachment in the Application Name field, and then click Next. The Name Your Project screen is displayed.
5. In the Project Name field, enter MQAsAttachment and click Next. The Configure SOA Settings screen is displayed.
6. In the Composite Template list, select Composite With BPEL, and then click Finish. The Wizard displays the Create BPEL Process dialog.
7. Enter MQAsAttachment in the Name field, and select Define Service Later from the Template box.
8. Click OK. The MQAsAttachment application and the MQAsAttachment project appears in the design area.

1. Drag and drop MQ Adapter from the Components window into the Exposed Services swim lane. The Adapter Configuration Wizard Welcome page is displayed
2. Enter mqService in the Service Name field, and click Next. The MQ Series Connection page is displayed.
3. Accept the default JNDI name for the MQ Series connection, and click Next. The Adapter Interface page is displayed.
4. Select Define from operation and schema (specified later), and click Next. The Operation Type page is displayed.
5. Select Get Message from MQ (do not check Synchronous), and click Next. The Get Message from MQ page is displayed.
6. Enter queue1 in the Queue Name field.
7. Select the Read Message As Attachment check box and click Next.

   Note: Ignore Character Set, Encoding, and Content Type fields for this use case. Populate these fields with values only if you are using third-party applications that must read this attachment. The attachment in the present use case is finally consumed by an outbound Oracle MQ Adapter, rather than a third-party application, hence these values are not required.

   Figure 10-104 Selecting the Read Message as Attachment Checkbox

   
   Description of "Figure 10-104 Selecting the Read Message as Attachment Checkbox"
8. Click Next. The JCA Endpoint Properties screen is displayed.
   composite.xml. For more information, see JCA Endpoint Properties in the Adapter Configuration Wizard.
9. Click Finish. You have now configured the inbound adapter service, and the composite.xml page is displayed with an inbound adapter added.

1. Drag and drop an MQ Adapter from the Components into the External References swim lane. The Wizard displays the Adapter Configuration Wizard Welcome page.
2. Enter mqReference in the Service Name field, and click Next. The MQ Series Connection page is displayed.
3. Accept the default JNDI name for the MQ Series connection, and click Next. The Adapter Interface page is displayed
4. Select Define from operation and schema (specified later), and click Next. The Operation Type page is displayed.
5. Select Put Message into MQ and click Next. The Put Message into MQ page is displayed.
6. Enter queue2 in the Queue Name field and click Next. The Advanced Options page is displayed.
7. Accept the defaults and click Next. The Messages page is displayed.
8. Click Browse For Schema File that appears at the end of the URL field. The Type Chooser dialog is displayed.
9. Click Project WSDL Files, mqService.wsdl, Inline Schemas, and attachmentElement.

   Figure 10-105 Selecting attachmentElement

   
   Description of "Figure 10-105 Selecting attachmentElement"
10. Select OK. The Wizard populates the URL field in the Messages page with AttachmentIn.wsdl.
11. Click Next. The Finish page is displayed.
12. Select Finish. You have now configured the outbound adapter service, and the composite.xml page is displayed.

    Figure 10-106 Composite.xml after Outbound Adapter Service Configured

    
    Description of "Figure 10-106 Composite.xml after Outbound Adapter Service Configured"

1. Drag the small triangle in the mqService in the Exposed Services area to the drop zone that appears as a green triangle in the MQAsAttachment in the Components area.
2. Drag the small triangle in the MQAsAttachment in the Components area to the drop zone that appears as a green triangle in mqReference in the External References area.

   The JDeveloper Composite.xml appears as shown in .Figure 10-107.

   Figure 10-107 The composite.xml with Activities and Services Wired

   
   Description of "Figure 10-107 The composite.xml with Activities and Services Wired"
3. Click File, Save All.
4. Double-click MQAsAttachment. The MQAsAttachment.bpel page is displayed.
5. Drag and drop the Receive, Assign, and Invoke activities in the order mentioned from the Component Palette to the Components area.

   The JDeveloper MQAsAttachment.bpel page is displayed, as shown inFigure 10-108 below.

   Figure 10-108 The JDeveloper MQAsAttachment.bpel page

   
   Description of "Figure 10-108 The JDeveloper MQAsAttachment.bpel page"
6. Drag and drop the Receive activity to mqService. The Receive dialog is displayed.
7. Click the Auto Create Variable icon that appears at the end of the Variable field. The Create Variable dialog is displayed.
8. Accept the defaults, and click OK.
9. Check the Create Instance box, and click OK.
10. Drag and drop the Invoke activity to mqReference. The Invoke dialog is displayed.
11. Click the Automatically Create Input Variable icon that appears at the end of the Input Variable field.
12. Accept the defaults, and click OK. The Invoke dialog is displayed.
13. Click OK.
14. Double-click the Assign activity. The Assign dialog is displayed.
15. Select the variables, as shown in Figure 10-109, then select the Plus icon.

    Figure 10-109 The Assign Activity Dialog

    
    Description of "Figure 10-109 The Assign Activity Dialog "
16. Click OK in the Assign dialog. The JDeveloper MQAsAttachment.bpel page is displayed, as shown in Figure 10-110.

    Figure 10-110 The MQAsAttachment.bpel page

    
    Description of "Figure 10-110 The MQAsAttachment.bpel page"
17. Click File, Save All.

1. Create an application server connection. For more information, see Creating an Application Server Connection for Oracle JCA Adapters.
2. Deploy the application. For more information, see Deploying Oracle JCA Adapter Applications from JDeveloper.