3 Configuring JD Edwards EnterpriseOne

After configuring your Transaction Server, you must set up the Transaction Server Components data for your JD Edwards EnterpriseOne environments to properly generate events.

This chapter discusses:

3.1 Verifying User Defined Codes (UDCs)

The Transaction Server Components requires the specific User Defined Codes (UDCs) to be populated as shown in this table.

Note:

By default, the UDCs are delivered and populated correctly. The information in this section is only provided for verification purposes.
UDC Purpose
H90/EC Event Category
H90/TP Event Transport Parameter Type

3.2 Verifying Tables

The Transaction Server Components requires the use of the tables listed below. The default configuration for RTE is where all of the F907* tables (event tables) reside in one datasource. Out of the box these tables are included in the System datasource database (that is, SY910). Using this default configuration, only one Transaction Server may be configured to monitor the F907* tables. Verify that these tables were created in the JD Edwards EnterpriseOne environments that will generate Real Time Events (RTE) events. Ensure that the server map OCMs and client map OCMs point to the same set of tables.

Table Description
F90701 Interoperability Event Definition
F90705 Event Activation
F90706 Event Subscriber
F90707 Event Subscription
F907071 Subscribed Events
F907072 Subscribed Environments
F90708 Event Sequence
F90710 Event Transfer
F90711 Event Transport Parameters
F90712 Event Transfer Failure
F90715 Event Subscriber Queues
F90720 Event Metrics
F90730 Unique Sequence

3.3 Verifying Serialized Objects

Serialized objects for tables, specs, and data structures must exist on the database machine. Verify that the serialized objects have been generated and copied to the database machine. For more information on performing the generation, see the JD Edwards EnterpriseOne HTML Web Server Reference Guide, specific for your platform, and the Generating JD Edwards EnterpriseOne Serialized Objects chapter.

3.4 Activating Events

Using this procedure, you must use JD Edwards EnterpriseOne universal batch engine (UBE) processes to convert the existing event data to be compatible with the new tables.

  1. Run the Populate Event Activation Status Table (R90705) to create an activation record for every environment for every event defined in the F90701 table. Through use of the processing options you can process this UBE for all events and all environments or for a single event and/or environment. You can run this UBE multiple times if necessary.

    This image is described in surrounding text.

  2. On Processing Options, Create Event Activation Rules, complete these fields:

    Field Description
    Specify the event name to create records for: If you leave this field blank, records are created for all events. If you specify a value for this field, records are only created for the specified event name regardless of what is specified in the event type specification.
    Specify the interoperability event type to create records for: If you leave this field blank, records are created for all event types. Valid event types are:

    • RTE

    • WF

    • XAPI

    • ZFILE
    Specify the release of the environments that records are to be create for: If you leave this field blank, records are created for all environments. Values are supported releases of JD Edwards EnterpriseOne, specified by internal designations.

    Note:

    You may use data selection to select on events that are currently active in the event system to convert.

  3. Run the Convert Event Subscriptions (R90706) UBE to populate the Queue Assignment Table (F90715) with the subscriber queues defined in the Transaction Server. You can use processing options to initially create your subscriber queue records and convert your subscribers and subscriptions. Later if you add new subscribers you can use this UBE to only create the new subscriber queue records. Initially there are 16 subscriber queues delivered with JD Edwards EnterpriseOne.

    Note:

    The R90706 program does not create the subscriber queues. Instead, 16 of these subscriber queues were created during the initial installation of the Transaction Server Components on an Application Server. If you have more than 16 subscribers you will need to create the additional queues using Application Server administrator tools prior to running this program.
    This image is described in surrounding text.

  4. On the Conversion Parameters tab, complete these fields:

    Field Description
    Enter the number of subscriber queues to create: Set this value to the number of subscriber queues for your installation. You must create a queue for every subscriber.
    Enter the description that will be assigned to all converted subscriptions. If this field is left blank the default description will be "Subscription converted by R90706". Enter a value to describe all converted description. If you leave this field blank the default description is "Subscription converted by R90706".
    Do not convert subscriptions Values are:

    0: Convert subscriptions

    1: Do not convert subscribers and subscriptions. The R90706 program only creates the number of subscriber queues that you specify and does not perform any conversions.

    Note:

    You may use data selection to select on events that are currently active in the event system to convert.

  5. Run the Synch Z Events in F47002 with F90701 (R90701A) UBE to create event records in the F90701 for the z-event records in the F47002 table for records that do not currently exist in the F90701 table. There are no processing options for this UBE.

3.5 Creating Triggers

You must create a trigger on the F90710 table. Prior to running the trigger creation script, ensure that you have adequate database privileges required to create a trigger. This table lists the privileges by database.

Note:

Additionally, as described in the Prerequisites sections of this guide, you must obtain and install a specific ESU to enable the creation of triggers for Transaction Server Components.
Database Required Privilege
IBM DB2 for System i No special privileges are required.
IBM DB2 Grant the following privileges to the database proxy user. Replace jde in the following script with the actual database proxy user name.

GRANT CONTROL ON TABLE SY900.F90710 TO USER jde
Oracle Grant the following privileges to the JDE_ROLE or the database proxy user. 
GRANT CREATE ANY SEQUENCE TO JDE_ROLE;
GRANT DROP ANY SEQUENCE TO JDE_ROLE;
GRANT CREATE ANY TRIGGER TO JDE_ROLE;
GRANT DROP ANY SEQUENCE TO JDE_ROLE;
SQL Server The database proxy user must have the privileges to create database triggers. Replace jde with the actual database proxy user name. 
Exec sp_addrolemember db_owner,jde

You must create the (F90710) Event Transfer and the (F90730) Unique Sequence in the same JD Edwards EnterpriseOne data source. You should verify this configuration using OCM.

  1. Run this script from a JD Edwards EnterpriseOne Microsoft Windows-based Web Development Client:

    x:\JDEdwards\E900\system\bin32\dbtemplates.exe -create

  2. After the scripts complete successfully, you should revoke any special privileges you granted in order to create the triggers. This table lists the revocation commands by database.

    Database Required Privilege
    IBM DB2 for System i No special privileges are required.
    IBM DB2 Revoke the following privileges to the database proxy user. Replace

    jde in the following script with the actual database proxy user name.

    REVOKE CONTROL ON TABLE SY900.F90710 TO USER jde
    Oracle Revoke the following privileges to the JDE_ROLE or the database proxy user. 
    REVOKE CREATE ANY SEQUENCE  TO JDE_ROLE;
REVOKE DROP ANY SEQUENCE  TO JDE_ROLE;
REVOKE CREATE ANY TRIGGER  TO JDE_ROLE;
REVOKE DROP ANY SEQUENCE  TO JDE_ROLE;
    SQL Server Replace jde with the actual database proxy user name. 
    exec sp_droprolemember db_owner,jde

3.6 Activating Journaling

Note:

This procedure is only applicable to DB2/400 JD Edwards EnterpriseOne databases running on IBM iSeries machines.

As described by this procedure, for DB2/400 databases you must activate journaling on the Unique Sequence (F90730) table.

  1. Verify that journaling is activated by entering this command on the DB2/400 machine:

    WRKOBJ OBJ(library_name/table_name)OBJTYPE(*FILE)

    Where table_name is F90730.

    Select option 8. Page down to see Journaling information. If Currently journaled is No, it means Journaling is not turned on.

  2. To turn journaling on for the table enter this command:

    STRJRNPF FILE(library_name/table_name JRN(OWJRNL/OW_JRNL)

    Where table_name is F90730.