This chapter contains these topics:
The Notifications User Guide includes the following topics for the JD Edwards World A9.3 Transaction Server:
Overview
Pre-Notification Setup
Notifications Setup
Approvals for Notifications
Transformation Template Setup
Testing the Sample Use Case
JD Edwards World A9.3 Transaction Server, hereafter, is referred to in this document as Transaction Server. This Java-based program is a modified version of the JD Edwards EnterpriseOne Transaction Server.
The Transaction Server transfers business transactions from JD Edwards World to other systems using the Java Message Service (JMS) API.
The JD Edwards World A9.3 Notifications enhancement uses Approvals Management, Export, and Electronic Document Delivery (EDD) to create an eXtensible Markup Language (XML) representation of a business transaction called a notification Real-Time Event (RTE). After creating the RTE, Notifications processing places it on an Event Transfer table as a new event record.
New event records on the Event Transfer table are read by the Transaction Server, which creates JMS messages from the event record and writes them to one or more JMS queues or topics, based on the subscriptions defined for each type of business transaction.
This guide provides an overview of how to interact with the various parts of the Transaction Server.
Notification services to capture transactional events from JD Edwards World consist of several different parts. A business transaction event is defined using the World Approvals rules structure. Once an event is created, the transaction information is loaded as an XML payload into an Event Transfer table. When the payload is added to an event record, the Transaction Server selects the Events that are ready to be processed. Once an Event is read by the Transaction Server, it is transformed into a Java Messaging Service (JMS) message and then submitted to the appropriate subscription queue or topic.
The starting point for each Event is a World RPG application where a business transaction is created. The Approvals rules structure is used in conjunction with application defined transaction boundaries to determine when a transaction is complete (and approved, if applicable) and an Event is created. Multiple Events can be created from a single transaction depending on the Approval rules set up.
The payload XML data is created using the World Export application. Export is based on World Writers to collect the data and create an XML message. The data can be pre-staged into a temporary work file using an application-specific extract program.
The Transaction Server uses the XML payload to populate a Java Messaging Service (JMS) message. The JMS message can then be published to the appropriate subscriber JMS queue or JMS topic so that listening applications, such as an Enterprise Service Bus, can access it. JMS queues use a point-to-point protocol where there is usually one sender and one receiver, both using the same queue to transfer information. JMS topics use a publish-subscribe model, where many publishers can publish to a topic and many subscribers can subscribe.
Double-Byte Note:
This initial release of JD Edwards World A9.3 Transaction Server is supported on single-byte only.To enable you to have a clearer picture of how a real time event might be set up and used, a simple use case was added throughout the documentation. The sample set up creates a real-time transaction event when an employee is added to the Address Book in a World environment. An XML document is published to a JMS Queue set up on the Oracle Application Server.