Ordered Message Processing Use Cases

This section provides a high-level walkthrough of several ordered message processing use cases.

Queue and Dequeue a Single Message

This use case provides an overview of a single HL7 message being successfully queued and dequeued.

  • A queue named INT_QUEUE_SPRINT was created in the Queues section under Integration Integrations icon in a project.


    The queue is shown as configured.

  • The design-time integration looks as follows:


    The integration shows a trigger, map action, wait action, invoke, and wait action.

    • The MLLP Adapter trigger connection is configured with Enable FIFO Queue selected.
    • The first wait action is configured with a time delay of several seconds to simulate HL7 message processing time.
    • The MLLP Adapter invoke connection is configured with the INT_QUEUE_SPRINT queue selected from the Select a FIFO Queue list to queue messages in order.
    • The second wait action is configured with a time delay of several seconds to simulate HL7 message processing time.
  • A tool such as HL7 inspector simulates a client application sending an HL7 message to Oracle Integration. The MLLP Adapter trigger connection listens for incoming messages.
  • A message instance is created and visible on the Instances tab with a status of In Progress.


    The Integration, Instances (which is selected), Queues, Subscriptions, Future runs, and Audit tabs are shown. Search and filter icons appear below. A filter has been set on the display of data. A table with columns for Name, Instance ID, Business identifiers, Status, and Duration appears. The instance is in progress.

  • The Queues tab shows there is one message in the expanded queue in a Pending state.


    The Integration, Instances, Queues, Subscriptions, Future runs, and Audit tabs are shown. Search and filter icons appear below. A table with columns for Name, Messages in queues, and Delivery status appears. The first queue in the table is expanded to show columns for Message created on, Instance ID, Status, and Action.

  • Once the time delay in the wait action is reached, the message status changes to Sending.


    The Integration, Instances, Queues, Subscriptions, Future runs, and Audit tabs are shown. Search and filter icons appear below. A table with columns for Name, Messages in queues, and Delivery status appears. The first queue in the table is expanded to show columns for Message created on, Instance ID, Status, and Action.

  • The Instances tab shows that the message instance completed successfully. The activity stream shows that the message was successfully received and dequeued in the queue.


    The activity stream is expanded to show the message received the queue, being dequeued by the queue, and dequeued by the queue. The HL7 request is acknowledged. The wire message is sent and received by the MLLP Adapter invoke connection. Processing completes for the queue.

Maintain Message Order When Calling a Child Integration from a Parent Integration

This use case provides an overview of how ordered message processing is maintained when a parent integration invokes a child integration (local invocation).

  • A queue named QUEUE_TEST_DEMO was created in the Queues section under Integration Integrations icon in the project.


    The queue is shown as configured.

  • The Integration section shows parent (Parent_TEST_DEMO) and child (RestChild_TEST_DEMO) integrations.


    To integrations are shown as active. To connections are shown as configured.

  • The parent integration consists of an MLLP Adapter trigger connection configured with Enable FIFO Queue selected and an Integration action that calls a child integration (local invocation).


    The integration shows a trigger, map action, and integration action.

  • The child integration includes an MLLP Adapter invoke connection is configured with the QUEUE_TEST_DEMO queue selected from the Select a FIFO Queue list to queue messages in order.


  • The integration shows a trigger, map action, invoke, and map action.

  • A tool such as HL7 inspector simulates a client application sending an HL7 message to Oracle Integration. The MLLP Adapter trigger connection in the parent integration listens for incoming messages.
  • The Instances tab shows that the parent and child integrations completed successfully.


    The Integration, Instances (which is selected), Queues, Subscriptions, Future runs, and Audit tabs are shown. Search and filter icons appear below. A filter has been set on the display of data. A table with columns for Name, Instance ID, Business identifiers, Status, and Duration appears. The two instances show a status of succeeded.

  • The activity streams for both instances shows that messages were successfully received and dequeued in the queue.