Page History

...

Introduction

• Message Queue Services are a common means for Enterprise Application Interation Integration (EAI). Users who operate a Message Queue Service want to integrate their applications with JS7. Patterns for Enterprise Application Integration EAI include:
  • applications sends an add order requests to JS7 JOC send requests to add orders to workflows by use of the JS7 - REST Web Service API.
  • applications receive processing results from jobs and workflows executed with JS7.
• Such EAI scenarios provide the following advantages:
  • reduce complexity
    • at a the topological level , i.e. each application implements only one interface to the Message ServciceQueue Service.
    • of error handling as a Message Queue Service would be is considered to be highly available.
  • manage messages centrally.
• The JMS integration scenario includes a separate Java based consumer to be implemented in order to receive and to parse messages and to translate messages received into requests to add order requestsorders. The reasons Reasons for this decision areinclude:
  • JMS is certainly standardized, however, the content and format of messages requires individual parsing.
  • JS7 JOC offers a JSON based REST Web Service API that can be used by any consumer to request add order orders by REST API calls.

Use with Generic Jobs

Implementation

• The implementation is independent from the JS7 release and consists of Java examples that are separately available, see below references.

...

Scenario 1: Detached

...

JS7 JMS Interface

1. Use Case

• An application prompts JS7 JOC makes use of the JS7 REST Web Service API to start a JS7 workflow.

2. Producer

• Creates a text message in the JSON format for the queue "Workflows". The content of the message can be e.g.is for example:

  {"controllerId":"testsuite","orders":[{"workflowPath":"/JS7Demo/01_HelloWorld/jdHelloWorld","scheduledFor":"now"}],"auditLog":{}}

• sends the message to the specific queue.

3. Consumer

• Reads a message from the queue „Workflows" and sends the JSON body via HTTP(S) to a JS7 JOC API instance.

...

• by use of the JS7 REST Web Service API.

Scenario 2: Generic

...

JS7 JMS Interface

1. Use Case

• A Java job runs in a workflow and implements the Producer to send information to the Message Queue Service after completion of a number of job nodes JS7 - Job Instructions in a workflow.
• A Java job runs in a workflow and implements the Consumer, i.e. connects to the Message Queue Service to check for new messages that include possible add order requestsparameterization to add orders to JS7.
• The Producer as well as the Consumer run in any job chain/ workflow.

2. Producer

• Producer:
  • A job node sends some information to a message queue Message Queue to signal completion of a workflow.

3. Consumer

• Consumer:
  • Reads JS7 JOC API JSON command REST Web Service API body from a message in JSON format and hands over the JSON body to a JS7 JOC REST Web Service API call for execution.

TBD: Use with File Transfer jobs

Implementation

• YADE is extended to pre-process XML snippets from messages that have been received from a queue.
  

  Display feature availability
  StartingFromRelease 1.11

   

• JMS support is added with 

  Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key YADE-409

Starting Situation

The YADE Client reads a configuration from an ini file. The configuration items are mapped to an Option class. The file transfers are processed.

• The ini file configuration will be replaced with an XML configuration in the future.
• At the time of writing it is only possible to create an XML configuration via the XML Editor. To use the configuration it has to be exported to an ini configuration for YADE to use.

Desired Behavior

Extending the YADE Client with a pre-processing functionality.

...

Prerequisites
The XML snippet has to consist of YADE XML compliant elements.

Use with the

...

JS7 Monitoring Interface

Implementation

• The implementation allows a Message Service to be used in order to forward notifications to a System Monitor
  

  Display feature availability
  StartingFromRelease 1.11

   Monitor 
• Support for notifications via Message Services is added with 

  Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JITL-280

References

Change Management References

Further Resources

Resources

• JS7 - Example - How to send and receive messages with a JMS Message Queue Service
• JS7 - Example - How to send and receive messages with a JMS Message Queue Service
• Example - How to Send an XML Command Over a Message Queue
• Example - How to Write Java JobScheduler Jobs that communicate over a Message Queue