|
CPS implements Java Messaging (JMS) |
|
|
|
|
Java Messaging Services (JMS) is now available for distributed communications between instances of CPS and other applications or other instances of CPS. CPS can be configured to generate JMS Messages (a producer), or can be configured to receive JMS Messages (a consumer). CPS as JMS Producer - JMS Messages can be generated from within CPS. Typical message structures are XML based formats, accommodating a wide variety of requirements. There are several options for configuring CPS as a JMS producer: Type 1: CPS Portal / CPS Web Developer - Interactive web pages, where the user triggers a message from a screen event such as a push button or keystroke. Type 2: Model Tree & Detail Definitions - Base CPS configuration point for event models and data models. Type 3: Stored Procedures - Oracle PL/SQL procedures and functions where business logic may be executed. Type 4: Database Triggers - Insert, Update, and Delete events directly on a table can trigger the creation of messages.
CPS as JMS Consumer - JMS Messages can be consumed by the CPS Portal. Typical message structures are XML based formats, accommodating a wide variety of requirements. The following are key configuration points: XML messages conform to the same SOAP message structure used in CPS Portal and CPS Web Services. Model Tree & Detail Definitions provide the event model and data model for JMS consumption and replies. XSL can be used to transform inbound or outbound messages for specific requirements.
Please login or register to add comments |
Blog