Page History
...
- Message Services are a common means for Enterprise Application Interation (EAI). Users who operate a Message Service want to integrate their applications with JobScheduler 1 or JS7. Patterns for Enterprise Application Integration include:
- applications send job start requests to JobScheduler 1.
- applications send add order requests to JS7 JOC API.
- applications receive processing results from jobs and job chains executed with JobScheduler 1.
- 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 Servcice.
- of error handling as a Message Service would be considered to be highly available.
- manage messages centrally
- reduce complexity
- The JMS integration scenario includes a separate Java based consumer to be implemented in order to receive and parse messages and to translate messages received into job start or add order requests. The reasons for this decision are:
- JMS is certainly standardized, however, the content and format of messages requires individual parsing.
- JobScheduler 1 offers an XML command interface that can be used by any consumer to request job starts.
- JS7 JOC offers an JSON API that can be used by any consumer to request job starts.
...
Overview
Content Tools