Configuring the EnterpriseOne Event Listener

In this section:

How to:

The EnterpriseOne Event Listener is installed as part of the basic installation. The adapter is automatically installed in the appropriate directory. If application server is not installed on the same computer as the J.D. Edwards application server, you must configure the EnterpriseOne Event Listener. For more information, see the J.D. Edwards Interoperability Guide.

The EnterpriseOne Event Listener is invoked by J.D. Edwards for specific business functions as configured in the EnterpriseOne environment.

The EnterpriseOne Event listener includes the following components:

The EnterpriseOne Event listener exit is the function that passes the key fields for a record in the EnterpriseOne outbound transaction tables to an application server. The EnterpriseOne Event listener is deployed under the J.D. Edwards EnterpriseOne Server. The Java class for the EnterpriseOne Event listener is called IWOEvent (the file extension depends on the operating system) and is case-sensitive.
Top of page
x
Procedure: How to Configure J.D. Edwards OneWorld Enterprise Server for Events

This section describes how to configure the J.D. Edwards OneWorld Enterprise Server for Events.

  1. Create a folder called Outbound under the JDE structure on the JDE Enterprise Sever. For example: 
    \\ JDEdwards\E812\DDP\Outbound
  2. Copy the iwoevent.dll and iwoevent.cfg files in the new Outbound folder.

    The following is a sample iwoevent.cfg file that is provided as an example:

    common.trace=onalias.iwserv14=172.30.162.48:1236, trace=ontrans.JDESOOUT=iwserv14

    Currently, the J.D. Edwards OneWorld supports 100 entries (alias names) in the configuration file.

  3. Create a folder using the alias names that are specified in the iwoevent.cfg file under the following directory: 
    \\ JDEdwards\E812\DDP\Outbound
  4. Make the following changes to your environment variables:
    1. Create a new variable called JAVA_HOME.
    2. Set this to the location of your JDK installation location. For example: 
      D:\jdk1.3
    3. Add the following to your PATH variable: 
      %JAVA_HOME%\bin; %JAVA_HOME%\jre\bin; %JAVA_HOME%\jre\bin\classic;
    4. Create a new variable called IWOEVENT HOME.The value should be set to the full path of the Outbound directory. For example: 
      D:\JDEdwards\E812\DDP\Outbound
Top of page
x
Creating the iwoevent.cfg File

After EnterpriseOne invokes the EnterpriseOne Event listener, the listener accesses the configuration file, called iwoevent.cfg (case-sensitive). Based on the information in the configuration file, the listener sends the event notification to application server. If the application server is unavailable or an exception occurs, the EnterpriseOne Event listener saves the event information in a file under the folder that is created on the corresponding alias names in the outbound folder.
x
Procedure: How to Create the iwoevent.cfg File
  1. On the J.D. Edwards EnterpriseOne Server, create an iwoevent.cfg file in the defined directory. For information about the contents of this file, see Adding Connection Information.
  2. Create an environment variable, IWOEVENT_HOME, to point to the directory containing the iwoevent.cfg file.

    On Windows, add IWOEVENT_HOME to the system environment variables.

    On UNIX, add the following command to your start-up script:

    export IWOEVENT_HOME =/directory_name
Top of page
x
Adding Connection Information

The EnterpriseOne Event listener requires connection information to initiate events properly. This information is contained in the iwoevent.cfg file. You must create this file and add the connection information to it.

The EnterpriseOne Event listener requires connection information for the associated integration server to function properly. This information is contained in the iwoevent.cfg file.

A sample iwoevent.cfg file is installed on the J.D. Edwards server and is in the root path. The iwoevent.cfg file includes the following distinct sections:

The common section of the configuration file contains basic configuration options. Currently, only the trace option is supported.

The alias section of the configuration file contains the connection information required to send transactions to specific servers. The alias values to these entries are as follows:

Alias.aliasname={ipaddressordnsname}:port, trace=on

where:

ipaddressordnsname

Is the IP address or DNS name for the server containing the iWay Application System Adapter for J.D. Edwards EnterpriseOne (required).

port

Is the TCP port waiting for the TCP request.

trace=on

Sets tracing on for the particular alias.

The trans section of the configuration file contains transaction information required to route EnterpriseOne transactions to specified servers.

Note: If a particular EnterpriseOne transaction is not defined to an alias, it is sent to all aliases. The trans values to these entries are as follows:

trans.jdeTransactionName=alias1,alias2,aliasn

where:

jdeTransactionName

Is the JDE-defined name for the outbound transaction.

alias1,alias2,alias3

Is the list of aliases to which the transactions are sent.
x
Procedure: How to Add Connection Information to iwoevent.cfg
  1. Add the server and port entries to the iwoevent.cfg file.
  2. To set the trace option, select on or off. 
    common.trace=on

    where:

    on

    Sets tracing on.
Example: Adding Connection Information to iwoevent.cfg

The following is a sample entry from iwoevent.cfg that supplies connection information.

common.trace=on
 
alias.edamcs1=172.1.1.1:3694
alias.edamcs1t=172.1.1.1:3694, trace=on
alias.edamcs2=222.2.2.2:1234
 
trans.JDESOW=edamcs1t,edamcs2
trans.JDEPOOUT=edamcs1
iWay Software