Monitoring Real Time Event Data with JD Edwards EnterpriseOne Transaction Server

By Nami Fujiyama

A standard method for integrating JD Edwards EnterpriseOne with external systems is through the use of “Real Time Events” (RTE). RTE allows EnterpriseOne to capture transactional information after it has been commited to the database and asynchronously deliver a snapshot of the transactional data to an external system.

The JD Edwards EnterpriseOne server that manages the delivery of these Real Time Event is called the “Transaction Server”. RTE messages are sent from JD Edwards EnterpriseOne and received and processed by the Transaction Server. These messages are stored within the OAS JMS subscriber queues until a valid subscriber (i.e. WSG, Java Listener, ESB, BPEL) connects and receives the events.

An important aspect of this process is the ability for an administrator to monitor and view event data within the Transaction Server. This document provides details on how an administrative user can view the information which is being stored in the JMS queues before they are successfully delivered to a subscriber. This information is only available to view as long as the subscriber has not connected and retrieved the event messages. The data contained within each message is viewable within the queue by using the procedure described below.

1. Login to Cluster Topology view


2. Click on your container for transaction server (CONTAINER3)
3. Click on the Administration link
4. Click on the “Go to Task” for the “System MBean Browser” under JMX

5. Go to oc4j::J2EEServer::standalone::JMSResource::JMS::JMSDestinationResource:: and click your queue (Queue.SubQueue00)

6. Click on the “Operations(5)” link

7. Click on “browse”

8. Type “0” in the “count” value and click on “Invoke Operation”.

Accessing User Defined Values From JDE Using BPEL

By Jim Li

EnterpriseOne utilizes user defined codes (UDC) to store list of code values. When the code is provided, other systems may not recognize the value. It becomes necessary to retrieve the description for the UDC code as well.
In this example, an input for the state would return the full description for the state value. Input of “CA” would return “California” based on the UDC.

This process flow is designed to work with the UDC code 00/S, which stores state values. It can also be used as a model for any other UDC code.

1. Using BSSV tool in EnterpriseOne, generate WSDL file (EOneUserDefinedCode) for getUDC business function.
2. Create BPEL process and add PartnerLink using WSDL

3. Modify XSD to designate State Code as input and Description as output

4. Create variables for invoking PartnerLink

5. Assign values for “system code” and “record type code. Since the state code is stored in the UDC 00/S, map as follows:
a. System code = ‘00’
b. Record type code = ‘S’

6. Assign input variable to PartnerLink variable

7. Create Assign statement after invoking PartnerLink and assign EOne output to the Output Variable

8. Deploy and execute process. Enter in a value of “CA” for the input, and will return the following XML document:

<part xmlns:xsi="" name="payload">

<UDCStateRetrieveResponseElement xmlns="">

<StateDescription>California</StateDescription >

</UDCStateRetrieveResponseElement >



9. Note the State Description received