Specifying Outbound Functionality for a Business Function

In this section:

You can specify outbound functionality for business functions and manage the flow of data. You enable outbound transaction processing using a processing option that controls how a transaction is written.


Top of page

x
Outbound Transaction Processing

To process outbound data, you use the:

The Data Export Control table manages the flow of the outbound data to third-party applications. The Processing Log table contains all the information about the EnterpriseOne event.



x
Procedure: How to Configure Outbound Transaction Processing

To configure outbound transaction processing:

  1. Set an environment variable called JAVA_HOME on the J.D. Edwards Enterprise Server.
  2. Set this to the location of your JDK installation, for example:
    SET JAVA_HOME=D:\jdk1.3
  3. Add the following to your PATH variable.
    %JAVA_HOME%\bin;%JAVA_HOME%\jre\bin;%JAVA_HOME%\jre\bin\classic;
  4. Add the installation location of the iwoevent.dll file to your PATH variable, for example:
    d:\mylocation
  5. Add the Connector. jar and kernel. jar files to your CLASSPATH, for example:
    d:\b7\system\classes\Connector.jar; d:\b7\system\classes\kernel.jar

    Note: You must add the required .JAR files as specified in the following table.

    J.D. Edwards EnterpriseOne Version

    Required .JAR Files

    B733

    Connector.jar

    kernel.jar

    ERP8 (B7334)

    Connector.jar

    kernel.jar

    EnterpriseOne B9

    Connector.jar

    kernel.jar

    jdeutil.jar

    log4.jar

    EnterpriseOne 8.10

    Connector.jar

    kernel.jar

    jdeutil.jar

    log4.jar

    EnterpriseOne 8.11

    Base_JAR.jar

    Connector.jar

    JdeNet_JAR.jar

    log4.jar

    System_JAR.jar

    EnterpriseOne 8.12 (Tools Release 8.96.2.0)

    Base_JAR.jar

    JdeNet_JAR.jar

    System_JAR.jar

    Connector.jar

    EventProcessor_EJB.jar

    EventProcessor_JAR.jar

    log4.jar

    EnterpriseOne 8.12 (Tools Release 8.97.1.2 and 8.97.2.0)

    Base_JAR.jar

    JdeNet_JAR.jar

    System_JAR.jar

    Connector.jar

    EventProcessor_EJB.jar

    EventProcessor_JAR.jar

    commons-httpclient-3.0.jar

    jmxri.jar

    ManagementAgent_JAR.jar

    log4.jar

  6. Set a system variable called IWOEVENT_HOME on the J.D. Edwards Enterprise Server and set this location to a folder, for example, Outbound, where iwoevent.dll and iwoevent.cfg are located. For more information, see How to Create a System Variable on Windows.

For more information on configuring EnterpriseOne for outbound processing, see Detailed Tasks for EnterpriseOne Operations in the J.D. Edwards Interoperability Guide for EnterpriseOne.



x
Procedure: How to Create a System Variable on Windows

To create a new system variable:

  1. Click Start, select Settings, and click Control Panel.

    The Control Panel window opens as shown in the following image.

  2. Double-click the System icon.

    The System Properties window opens as shown in the following image.

  3. Click the Advanced tab and click Environment Variables.

    The Environment Variables dialog box opens as shown in the following image.

  4. Click New in the System variables section.

    The New System Variable dialog box opens as shown in the following image.

  5. Perform the following steps:
    1. Type a name for the system variable in the Variable Name field.
    2. Type a valid path for the system variable in the Variable Value field.
    3. Click OK.


x
Procedure: How to Create a System Variable on UNIX

To create a new system variable:

  1. You must define and set the following variable to the location of your JDK installation:
    JAVA_HOME

    For example:

    JAVA_HOME=D:/jdk1.3/
    export JAVA_HOME

    Note: Be sure to include the trailing slash.

  2. The PATH variable must contain the JDK bin directory, for example:
    PATH=$PATH:/D:/jdk1.3/bin/
    export PATH


x
Procedure: How to Enable Outbound Transaction Processing

To enable outbound transaction processing:

  1. Right-click the application that contains the processing options for the Master Business Functions of the transaction.

    For a list of these options, see Appendix B of the J.D. Edwards Interoperability Guide.

  2. From the shortcut menu, select Prompt for Values.
  3. Click either the Outbound tab or the Interop tab.
  4. Enter the transaction type.

    The EnterpriseOne Event listener processes only the after image for the business function.

    You are not required to set the before image function.


Top of page

x
The Data Export Control Table and the Processing Log Table

The Data Export Control table manages the flow of the outbound data to third-party applications. EnterpriseOne allows for the subscription of multiple vendor-specific objects for an interoperability transaction.

The records in the Data Export Control table are used to determine the vendor-specific objects to call from the Outbound Subsystem batch process (R00460) or the Outbound Scheduler batch process (R00461).

The Processing Log table contains all the information about the EnterpriseOne event including the transaction type, order type, and sequence number from the Data Export Control table.



x
Procedure: How to Use the Data Export Controls

To use the data export controls:

  1. On the Work With Data Export Controls pane, click Add.
  2. Type values in the Transaction Type and Order Type fields.
  3. For each detail row, enter either a batch process name or version or a function name and the library.
  4. To launch the vendor-specific object for an add or insert, type 1.
  5. For the update, delete, and inquiry actions, type 1.
  6. In the Launch Immediately column, type 1.
  7. Click OK.

iWay Software