Salesforce

Configuring the JD Edwards Enterprise One Connector (Magic xpi 3.x)

Printable View
« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Configuring the JD Edwards Enterprise One Connector (Magic xpi 3.x)

To configure the JD Edwards Enterprise One connector, follow these steps:

  1. Define a JD Edwards Enterprise One resource. For more information on the resource's parameters, click here.

  2. Set the JD Edwards Enterprise One server .ini configuration files. The .ini configuration files that reside under the JDE installation (shown in the image below) should be copied into the JD Edwards Enterprise One component directory:

    \ifclib\jdedwards\config\<JDE server name>_<JDE env>

     The <JDE server name> and the <JDE env> should be the same values that you defined in the JDE resource. The resource name is not used in this folder name.

  3. Set the following .jar files that are required by Magic xpi to work with the JD Edwards Enterprise One Dynamic connector:

    Version

    Required Files

    8.10 with Tools Release version 8.93, 8.94, 8.95, and 8.96

    Connector.jar

    Kernel.jar

    database.jar

    jdeutil.jar

    log4j.jar

    xerces.jar

    8.11 with Tools Release version 8.94, 8.95, and 8.96

    Connector.jar

    Kernel.jar

    database.jar

    jdeutil.jar

    log4j.jar

    xerces.jar

    8.12 with Tools Release version 8.96 and 9.0

    ApplicationAPIs_JAR.jar

    ApplicationLogic_JAR.jar

    Base_JAR.jar

    BizLogicContainer_JAR.jar

    BizLogicContainerClient_JAR.jar

    BusinessLogicServices_JAR.jar

    castor.jar

    commons-httpclient-3.0.jar

    commons-logging.jar

    Connector.jar

    Generator.jar

    j2ee1_3.jar

    JdbjBase_JAR.jar

    JdbjInterfaces_JAR.jar

    JdeNet_JAR.jar

    jmxremote.jar

    jmxremote_optional.jar

    jmxri.jar

    log4j.jar

    ManagementAgent_JAR.jar

    Metadata.jar

    MetadataInterface.jar

    owra.jar

    PMApi_JAR.jar

    Spec_JAR.jar

    System_JAR.jar

    SystemInterfaces_JAR.jar

    xerces.jar

    xmlparserv2.jar

    JDBC driver jar files supplied by the database vendor. (For the Microsoft SQL Server™, you need the JDBC driver, the msbase.jar, the mssqlserver.jar, and the msutil.jar.)

    All versions

    The JDBC files for the corresponding database (The Microsoft SQL Server™ JDBC driver requires the msbase.jar, mssqlserver.jar, and msutil.jar files.)

Note:

You should save the above jars to a dedicated folder (for example, <Magic xpi installation>/JDE_lib), and reference them one by one in either the machine's CLASSPATH or in the Magic.ini file's CLASSPATH.

In the following example, the JDE JCA classes were placed underneath the Magic xpi installation in the JDE_lib folder. This example connects to JDE with an Oracle database. This is why the Oracle JDBC driver's ojdbc5.jar is loaded.

CLASSPATH=support\edevUtils.jar;JDE_lib\ApplicationAPIs_JAR.jar;JDE_lib\App+

licationLogic_JAR.jar;JDE_lib\Base_JAR.jar;JDE_lib\BizLogicContainer_JAR.ja+

r;JDE_lib\BizLogicContainerClient_JAR.jar;JDE_lib\BusinessLogicServices_JAR+

.jar;JDE_lib\castor.jar;JDE_lib\commons-httpclient-3.0.jar;JDE_lib\commons-+

logging.jar;JDE_lib\Connector.jar;JDE_lib\Generator_JAR.jar;JDE_lib\j2ee1_3+

.jar;JDE_lib\JdbjBase_JAR.jar;JDE_lib\JdbjInterfaces_JAR.jar;JDE_lib\JdeNet+

_JAR.jar;JDE_lib\jmxremote.jar;JDE_lib\jmxremote_optional.jar;JDE_lib\jmxri+

.jar;JDE_lib\log4j.jar;JDE_Lib\ManagementAgent_JAR.jar;JDE_Lib\Metadata.jar+

;JDE_lib\MetadataInterface.jar;JDE_lib\ojdbc5.jar;JDE_lib\owra.jar;JDE_lib\+

PMApi_JAR.jar;JDE_Lib\Spec_JAR.jar;JDE_Lib\System_JAR.jar;JDE_Lib\SystemInt+

  1. Configure the JD Edwards Enterprise One connector. For more information on the connector's various configuration parameters, click here.


    If you know the Module Name and the Business Function that you want to call, you can enter them directly. Otherwise, you can zoom into the list of Business Functions through the JD Edwards Enterprise One Contexts list, and select the function you want to use.

  2. Click the Business Function List button to connect to the JD Edwards Enterprise One server and to retrieve the current Contexts list.

  3. To retrieve a specific Context Module list, park on the Context name and click Get. If you want to retrieve a specific Module Business Functions list, park on the Module name and click Get.

  4. After retrieving the information from the JD Edwards Enterprise One server, you can use the "find" functionality. To do this, press Ctrl+F. To bring the next value found, press Ctrl+F3.

  5. Click OK to retrieve the Business Function schema. It will then be displayed in the Data Mapper. Here, you can map data to JD Edwards Enterprise One.



Reference
Attachment 
Attachment