3 Notification Setup

This chapter contains these topics:

3.1 Event Definition

  1. Sign on to the JD Edwards World A9.3 Environment and select the Service Enablement menu (G98S).

    Figure 3-1 Service Enablement screen

    Description of Figure 3-1 follows
    Description of "Figure 3-1 Service Enablement screen"

    Select Event Definitions (2) from the menu and then press Enter.

    From the Event Definitions screen, enter a 3 in the Options column on a blank line to add a new Event definition.

    Figure 3-2 Event Definitions screen

    Description of Figure 3-2 follows
    Description of "Figure 3-2 Event Definitions screen"

  2. From the Event Definition Maintenance screen, enter an Event Name, an Event Type that corresponds to an Approvals Rule (G00A). Also, add the World Writer Query Group, Version, and User ID. Click Enter.

    Update the Event Activation status with a Y. Exit the Event Definition Maintenance and the Event Maintenance screen.

    Field Explanation Sample Use Case Value
    Event Name The name of the event, for example JDEITEMOUT. Cannot be the same as existing names. Valid characters consist of 0 - 9, A - Z, blanks, period, and underscore. Leading blanks are not allowed. EMPLOYEE1
    Event Description The description of an event. Cannot be blank. Add Employee Event
    Event Type A value that represents the name of the event type, for example the value RTE denotes Real Time Event; the value ZFILE denotes Batch Upload Event. UDC Validation 98S/ET. EMP1
    Event Activation Status Indicates whether an event is active. Y or N. Y
    WW Query Group The World Writer Query Group that is used to create the XML payload. Must be a valid WW Query Group. Q98S
    WW Query Name The World Writer Version that is used to create the XML payload. Must be a valid WW Version. EMPLOYEERT
    WW Query User The World Writer Version User that is used to create the XML payload. Must be a valid IBM Profile and WW Version User (Export Parameters defined). Current user id

    Figure 3-3 Event Definition Maintenance screen

    Description of Figure 3-3 follows
    Description of "Figure 3-3 Event Definition Maintenance screen"

3.2 Event Subscription

Sign on to the JD Edwards World A9.3 Environment and select the Service Enablement menu (G98S).

Navigation

From the Service Enablement menu, select Event Subscriptions (3) and then press Enter.

From the Event Subscriptions screen, enter a 3 in the option field to add a new subscription.

Figure 3-4 Event Subscriptions screen

Description of Figure 3-4 follows
Description of "Figure 3-4 Event Subscriptions screen"

  1. From the Event Subscription Maintenance screen, enter the Event Name of the event added in step 4 of the Event Definition procedure. Enter a Subscription Name and Description. The User ID 2 field is automatically generated by the program.

    Update the Subscription Activation Status to Y and pick a Transportation Type Q for JMS Queue or T for JMS Topic.

    Enter the Parameter Value which is the endpoint URL for either the JMS Topic or Queue and then press Enter.

    Field Explanation Sample Use Case Value
    Event Name The name of the event the subscription is associated with, for example JDEITEMOUT. Must be a valid Event Name on F98S701. EMPLOYEE1
    Subscription Name Cannot be the same as existing name for a Subscription. Valid characters consist of 0 - 9, A - Z, blanks, period, and underscore. Leading blanks are not allowed. EMP_SUB1
    Subscription Description The description of an event. Cannot be blank. Employee Add Subscription
    Subscription Activation Status Indicates whether a subscription is active or not. Y or N. Y
    Transport Type The type of the transport driver that delivers events to the subscriber, either Topic or Queue. UDC Validation 98S/TT. Q
    Distribution Profile The EDD distribution profile to be used for sending out email notices when an event subscription notification fails.  
    Email Template The EDD e-mail template to be used for sending out e-mail notices when an event subscription notification fails.  
    Transport Parameter Name Description of the event transport value. Employee JMS Queue
    Transport Parameter Value Event Transport Value, Topic or Queue location (JNDI location) jms/World/Employee

    Figure 3-5 Event Subscription Maintenance screen

    Description of Figure 3-5 follows
    Description of "Figure 3-5 Event Subscription Maintenance screen"

  2. From the Event Subscription Maint-Page 2, update the Application Server Type field with the type of application server the Transaction Server is running on, ORACLE.

    Enter the Connection Factory from the application server. If the Transportation Type is JMS Queue, you need to enter the Initial Context Value and the Queue URL. Press Enter.

    Field Explanation Sample Use Case Value
    Event Name The name of the event the subscription is associated with, for example JDEITEMOUT. Must be a valid Event Name on F98S701. Protected Field
    Subscription Name Cannot be the same as existing names for a Subscription. Valid characters consist of 0 - 9, A - Z, blanks, period, and underscore. Leading blanks are not allowed. Protected Field
    Subscription Description The description of an event. Cannot be blank. Protected Field
    User ID 2 Program generated value. Protected Field
    Application Server Type The type of application server the Transaction Server is running on. Oracle or WebSphere. UDC Validation 98S/AT. ORACLE
    Connection Factory The JNDI location of the Queue Connection Factory or Topic Connection Factory From the application server where the Queue or Topic is deployed. jms/WorldConnectionFactory
    Initial Context Factory The name of the initial context factory object needed to create the JMS Queue object. com.evermind.server.rmi.RMIInitialContextFactory
    Queue URL The URL for the application server where the JMS queue is deployed. To find the ORMI Port, see To find the ORMI and Request Runtime Ports for the Oracle Application Server (OAS) For Local Server opmn:ormi://server.name:server_Request_Port:home

    For Remote Server ormi://server.name:server_ORMI_Port

    Figure 3-6 Event Subscription Maintenance - Page 2 screen

    Description of Figure 3-6 follows
    Description of "Figure 3-6 Event Subscription Maintenance - Page 2 screen"

To find the Weblogic Application Server Listening Port

  1. Log on to the Weblogic Administration Console OAS Enterprise Manager with the administrative log on.

    Figure 3-7 Weblogic Administration Console OAS Enterprise Manager screen

    Description of Figure 3-7 follows
    Description of "Figure 3-7 Weblogic Administration Console OAS Enterprise Manager screen"

  2. From the Administration Console Home page, select Servers under the Environment heading.

    Figure 3-8 Administration Console Home screen

    Description of Figure 3-8 follows
    Description of "Figure 3-8 Administration Console Home screen"

  3. On the Summary of Servers page, locate the Listen Port for the server you associated with the Employee JMS Queue. In the example above, the server set up for the Transaction Server is used. This is the value used for the Queue URL port setting for a Remote Server Instance (Transaction Server is on a different OAS than the JMS Queue).