2.5.3 Send Message to Queue - Application

  • Article

 Context of Use: An application creates a message and interacts with the queue manager to send the message. The application optionally uses a Directory Service for looking up the queue name.

 Goal: This use case places a message in a queue.

 Actors

Application:  See section 2.5.

Application Users:  See section 2.5.

Directory Service:  See section 2.5.

 Stakeholders

Developers:  See section 2.5.

Testers:  See section 2.5.

Application Users:  See section 2.5.

 Preconditions

  • The queue exists.

  • The application is authorized to send messages to the queue.

  • If a Directory Service is not being used, the application is configured with the address of the queue prior to the send operation.

 Main Success Scenario

 Trigger: The direct actor triggers this use case based on the actions of the primary actor. It is also triggered by the Exchange Message – Application (section 2.5.8) use case.

The steps involved in this use case are:

  1. The application constructs a message to send.

  2. The application optionally obtains the queue name from the Directory Service.

  3. The application sends the message to the queue manager.

  4. The queue manager performs validation checks and fails the operation in case of an error.

  5.  If the queue is hosted by this queue manager, the queue manager puts the message in the queue and returns a response back to the application. An extension of this step is described in Send Message in Transaction - Application (section 2.5.4).

  6.  If the queue is hosted by a different queue manager, the queue manager puts the message in an outgoing queue and invokes a separate use case to complete the message transfer operation, as described in Transfer Message (section 2.5.5).

 Postcondition

The message is placed in the destination queue.

 Extensions

See Send Message in Transaction - Application.