ModusBox’s JDE Connector

This configuration must be done by CNC administrator. Refer to JD Edwards EnterpriseOne Tools Interoperability Guide

The following matrix displays the Oracle’s JD Edwards EnterpriseOne™ Tools versions supported by version

You can install JDE Connector in Anypoint Studio using the instructions in Installing a Connector from Anypoint™ Exchange

If you’re currently using an older version of the connector, a small popup appears in the bottom right corner of Anypoint Studio with an "Updates Available" message.

Additionally, we recommend that you keep Studio up to date with its latest version.

These are the changes that you need to consider after the update.

These exceptions are extended of JDEConnectorException.

In addition to meeting the requirements listed in the Prerequisites and Requirements section, a bundle has to be created to establish a connection to the JDE Enterprise Server. This bundle will be created only for the first time and it can be reused in other applications.

This adapter is a bundle of JAR files that come with the JD Edwards EnterpriseOne distribution.

These steps illustrate how to create bundle connector component so that you can include in the flow that needs connect to JDE Enterprise Server.

Step 1

Create a folder in the file system that it will include the following subfolder:

In the folder Server_jar_files we need all the jar file that come with the JD Edwards EnterpriseOne distribution. The files can be found at <Enterprise Server directory>\system\classes on the JDE Enterprise Server to which you are connecting.

For Tools Release 8.98, copy these files:

For Tools Releases Tools Release 9.1 prior Update 4, copy these files:

For Tools Releases Tools Release 9.1 Update 4 and later updates, copy these files:

For Tools Releases Tools Release 9.2 and later, copy these files:

In the folder JDBC_Vendor_Drivers we need the JDBC driver files that correspond to the database to which you are connecting.

The folder Bundle will be an empty folder that will be used be the JD Edwards Setup to prepare the bundle jar file.

To ensure correct operation of all of the JDE Connector features the Enterprise Server requires the following jde.ini file settings:

Please refer to JD Edwards EnterpriseOne Tools Interoperability Guide to check updates.

Use these settings for a Microsoft Windows platform:

Please refer to JD Edwards EnterpriseOne Tools Interoperability Guide to get provides the different .dll extensions for other platforms.

Use these settings for a Microsoft Windows platform:

Please refer to JD Edwards EnterpriseOne Tools Interoperability Guide to get provides the different .dll extensions for other platforms.

Use these settings for a Microsoft Windows platform:

Please refer to JD Edwards EnterpriseOne Tools Interoperability Guide to get provides the different .dll extensions for other platforms.

Use these settings for a Microsoft Windows platform:

When there is a firewall between the Mulesoft ESB and the Enterprise Server, set the PredfinedJDENETPorts setting to 1 in the JDE.INI file of the Enterprise Server. This setting enables JDENET network process to use a predefined range of TCP/IP ports. This port range starts at the port number that is specified by serviceNameListen and ends at the port that is calculated by the equation serviceNameListen = maxNetProcesses - 1. You must open these ports in a firewall setup to successfully connect the Mulesoft ESB to the Enterprise Server.

Please refer to JD Edwards EnterpriseOne Tools Security Administration Guide to check updates.

The JDE Connector relies on Oracle’s Java Dynamic Connector to establish the link to the server. In order to achieve this, setting up the follwing standard configuration files is needed:

These files are distributed with both Fat Clients or Enterprise Server modules. In case you get the files from a Fat Client, the folder containing them can be found under the path ini/sbf of your installation.

This file is used by Dynamic Java Connector of JD Edwards to introspects business function metadata.

One point to start is seeing HTML server jdbj configuration. Using JD Edwards EnterpriseOne Server Manager inside HTML instance and under Configuration section, there is one option called Database.

One point to start is seeing HTML server jas configuration. Using JD Edwards EnterpriseOne Server Manager inside HTML instance and under Configuration section, there are options called Miscellaneous, Network and Security.

There is addtional configurations needed inside JDEINTEROP.INI. You need to add the following section:

If you need to run the application on CloudHub, you will need to add the section OCM_SERVERS with the servers that the JDE Connector will use in the connection. The JDE Servers Names are in the column OMSRVR of F98611 table. To add these servers on the OCM_SERVERS section you will need to follow this format is simple: JDE Server Name = FQDN or IP

If you are deploying an Application on Cloudhub, you need to use the tmp directory. This is an example:

Additionally, The new JDE Connector version will redirect JDE Logger to Mule Logger. It will allow seeing JDE activity in both Console and JDE file defined in jdelog.properties. To activate this redirect, It will require adding these Asyng loggers to log4j2.xml file

Create a new Mule Project with Mule Server 3.8.0 or larger EE as runtime:

We will need this project to generate Bundle.

After create the project, you need to build the Oracle JD Edwards' lib bundle.

This jar bundle will be created once and it can be reused for all the projects that it needs connect to JD Edwards.

Step 1

Select the project created and press right mouse button to show context menu.

Select JD Edwards setup from the JDE Context Menu options.

This option will open the following screen:

Step 2

In this screen you need to enter:

JDE Edwards libraries directory: the folder SERVER_jar_File created in section Preliminary Setup.

Select the JDBC driver for you vendor: The driver inside the folder JDBC_Vendor_Drivers created in section Preliminary Setup.

Target directory for your bundle: the folder Bundle created in section Preliminary Setup..

Press the button Finish and wait at the process end. You can see the advanced in the Progress tab at the bottom:

Step 3

When the process finishes, a windows show you the result.

You can open the bundle folder to see the JDE Edwards jar file generated:

This JAR file will be used in the connector setup.

Step 1

Put the files inside the project folder in the folder:

Step 2

Edit jdeinterop.ini, jdelog.properties, and jdbj.ini for proper settings.

To use the ModusBox’s JDE Connector in your Mule application, you must configure a global ModusBox’s JDE Connector element that can be used by the ModusBox’s JDE Connector (read more about Global Elements).

The ModusBox’s JDE Connector offers the following global configuration(s), requiring the following credentials:

General → Connection

General → Check Enable DataSense (Only on old Anypoint Studio)

General → Required Dependency

The first step is create a JDE Global Mule Configuration Elements:

To include the Oracle JD Edwards' lib bundle generated previously:

Press button Add File and select JD Edwards' bundle created.

the result will be:

For Maven Project:

Press button Add Dependency and select JD Edwards' bundle created.

the result will be:

Before continue, you need to test connection pressing TEST CONNECTION…​ button

When designing your application in Studio, the act of dragging the connector from the palette onto the Anypoint Studio canvas should automatically populate the XML code with the connector namespace and schema location.

Namespace: http://www.mulesoft.org/schema/mule/jde

Schema Location: http://www.mulesoft.org/schema/mule/jde http://www.mulesoft.org/schema/mule/jde/current/mule-jde.xsd

If you are coding a Mavenized Mule application, this XML snippet must be included in your pom.xml file.

This use case example will create a simple flow to get the address book name from the Address Book table (A/B) invoking the Master Business Function (MBF) on Oracle’s JDE EnterpriseOne Server.

Step 1

Use Mule Project created in the Section Create Mule Project.

Step 2

Locate the HTTP Endpoint connector on the right hand-side palette:

Step 3

Drag the connector over to the canvas:

Step 4

The connector requires an Connector Configuration; click on Add to create a connector configuration.

Step 5

Give the HTTP endpoint a more descriptive name like get-AddressBookName-http-endpoint and press OK to go back to the global HTTP endpoint dialog box:

Step 6

Add a path to the URL like getaddressbookname and press SAVE the project. The connector will be ready to process requests.

Step 7

Back to the Message Flow view, you need to Locate the JDE Connector on the right hand-side palette:

Step 8

Drag the connector over to the canvas:

Step 9

You need to select Connector Configuration created in Configure Global Element section:

Step 10

You need to select the operation Call BSFN

Step 11

Now, you need to select the bsfn to call in the Entity Type field and press ENTER. In this example we will use AddressBookMasterMBF.

The connector will get the specification from the server and it will put the specification in the local repository.

Step 12

You need to select the option: Create Object manually

The first time that the BSFN is used, the connector get the specs from the server.

Under java.io.tmpdir plus environment folder, the JDE Connector will save the specs.

After that you will need to populate the parameters. To do this press the button […​] and populate the parameters:

Action Code to "I" Inquire

And mnAddressBookNumber the address number that will be part of the URL parameter.

Ex: localhost:8081/getaddressbookname?addressbook=1

Enter:

Press OK button to return to JDE Connector configuration. Then, save the project.

Step 13

Back to the Message Flow view, and you need to Locate the Set Payload on the right hand-side palette to return the address book name.

Step 14

Drag the Transformer over to the canvas and write the answer.

Step 15

Finally, run the example as a Mule application

Step 16

Test the Mule Application

Write the URL:

and you will see the address book name:

This use case example will reuse the previous flow to add a Customer. In this case, we will need to invoke two Master Business Function (MBF) on Oracle’s JDE EnterpriseOne Server in the same transaction.

Step 1

Select the current JDE component to modify the Entity Data to use #[payload] instead of use Create Object manually:

Step 2

Locate the Transform Message component on the right hand-side palette. Drag the connector over to the canvas before JDE component.

Step 3

Switch to the XML view by clicking Configuration XML to replace CDATA element inside Transform Message definition:

with:

Step 4

Drag a new JDE component over to the canvas after current JDE component. You need to select the operation Call BSFN.

After that, you need to select the BSFN to call in the Entity Type field and press ENTER. In this case we will use MBFCustomerMaster.

Step 5

Back to the Message Flow view, and you need to Locate the Transform Message on the right hand-side palette.

Drag the connector over to the canvas between JDE components.

Step 6

Switch to the XML view by clicking Configuration XML to replace CDATA element inside Transform Message definition:

with:

Step 8

Back to the Message Flow view. Select the transformer Set Payload and replace the value with:

Step 9

Drag a new JDE component over to the canvas after current JDE component.

You need to select the operation BSFN Transaction.

After that, you need to select Begin Transaction in the Entity Type field.

Then, you need to populate the parameter Transaction ID with 0 pressing the button […​]:

Step 10

Wrap this component with the Scope: Message Enricher:

You need to create a new flow variable to save the Transaction Id.

This variable will be used to commit or rollback the transaction.

Step 11

Replaces both Call BSFN parameters with the new Transaction ID.

Step 12

Drag a new JDE component over to the canvas after last JDE component and before Set Payload.

You need to select the operation BSFN Transaction.

After that, you need to select Commit Transaction in the Entity Type field.

Then, you need to populate the parameter Transaction ID with 0 pressing the button […​]:

Step 13

Wrap this component with the Scope: Message Enricher:

You need to create a new flow variable to save the commit payload.

Step 14

Drag a new JDE component over to the canvas after components under Catch Exception Strategy.

You need to select the operation BSFN Transaction.

After that, you need to select Rollback Transaction in the Entity Type field.

Then, you need to populate the parameter Transaction ID with 0 pressing the button […​]:

Step 15

Back to the Message Flow view, and you need to select HTTP Connector to change the Path

Step 16

Finally, run the example as a Mule application

Step 17

Test the Mule Application

Write the URL:

and you will see the customer number created:

Step 18

Check Customer generated. Enter a Customer using Customer Master information:

Application: P03013

Version: ZJDE0002

This use case example will create a simple flow to submit an UBE to JDE Enterprise Server.

Step 1

Use Mule Project created in the Section Create Mule Project.

Step 2

Locate the HTTP Endpoint connector on the right hand-side palette:

Step 3

Drag the connector over to the canvas:

Step 4

The connector requires an Connector Configuration; click on Add or to create a connector configuration.

Step 5

Give the HTTP endpoint a more descriptive name like SubmitUBE-http-endpoint and press OK to go back to the globa HTTP endpoint dialog box.

Step 6

Add a path to the URL like submitube and press SAVE the project.

The connector will be ready to receive request.

Step 7

Back to the Message Flow view, you need to Locate the JDE Connector on the right hand-side palette:

Step 8

Drag the connector over to the canvas:

Step 9

You need to select Connector Configuration created in Configure Global Element section:

Step 10

You need to select the operation Submit batch process:

Step 11

Now, you need to write the UBE/Version (Ex. R0008P_XJDE0001) to submit in the Entity Type field and press ENTER:

The connector will get the specification from the server and it will put the specification in the local repository under java.io.tmpdir plus environment as destination folder

Step 12

After the connector get the specs from the server, you will need to populate the parameters.

To do this, you need to select the option: Create Object manually

Press the button […​] and populate the parameters:

_Job Queue: Enter the Job Queue or empty if you prefer default job queue for the UBE selected

_Selection: F0010.CO = ''00000''

cFiscalDatePattern: F

Press OK button to return to JDE Connector configuration. Save the project.

Step 13

Back to the Message Flow view, and you need to Locate the Set Payload on the right hand-side palette to return the address book name.

Step 14

Drag the Transformer over to the canvas and write the following payload:

Step 15

Finally, run the example as a Mule application

Step 16

Test the Mule Application

Write the URL:

and you will see the Job Id generated in the enterprise server.

Step 17

Check Work Submit Job from E1

This use case example will add an control to the previous example to get an UBE state from JDE Enterprise Server after Submit UBE.

Step 1

Back to the Message Flow view, you need to Locate the Variable on the right hand-side palette:

Step 2

Drag the Transformer over to the canvas after JDE Connector:

We use this transformer to save the JOB ID generated by the previous UBE Submit.

Edit Variable and add the following values:

Display Name: Save JOB ID

Name: JobIDSaved

Value: #[payload._Job_ID]

Step 3

Back to the Message Flow view, you need to Locate the JDE Connector on the right hand-side palette:

Step 4

Drag the connector over to the canvas after Variable Save JOB ID:

Step 5

You need to select the same Connector Configuration as previous connector.

Step 6

You need to select the operation Get batch process information

Step 7

Refresh metadata and select Get Job Status

Step 8

You will need to populate the parameters. To do this, you need to select the option: Create Object manually and press the button […​]:

Populate the parameters:

Set Job_ID to value: #[flowVars.JobIDSaved]

Step 9

Update the last "Set Payload" with the following value:

Step 10

Finally, run the example as a Mule application

Step 11

Test the Mule Application

Write the URL:

and you will see the Job Id generated and its status in the enterprise server.

The possible values of job status are:

This use case example will create a simple flow to get outbound events that it come from an application that uses a Master Business Function to generate transactions.

JDE outbound transactions requires that you set a Processing Option specifying a transaction type. Additionally, some entry programs enable you to specify a version of the Master Business Function Processing Options program that, in turn, enables you to specify a version of the Interoperability Processing Options program.

For example, to get customer entered by the application Customer Master information (P03013) is necessary setup the following Processing Options:

Then, the P0100042 version ZJDE0002 needs to have the following value in

The last configuration that is needed is inform to JDE connector the outbound table used by the MBF to inform the event:

Using "Flat File Cross-Reference (P47002)" form "Work With Flat File Cross-Reference" adds the following record:

Follow next steps to create a flow that it will capture Customers that it added using Customer Master information (P03013)*

Step 1

Use Mule Project created in the Section Create Mule Project section:

Step 2

Locate the Poll Endpoint connector on the right hand-side palette:

Step 3

Drag the JDE connector over to the canvas:

Step 4

You need to select the operation Poll Events:

Step 5

Now, you need to select Capture Event Transactions in the Entity Type field and press ENTER:

Step 6

Now, You will need to populate the parameters. To do this, you need to select the option: Create Object manually

Press the button […​] and populate the parameters:

Transaction Code Enter JDECM value

Max Qty Transactions to Read Enter 3 value

Last Batch Number (EDBT): #['']

Press OK button to return to JDE Connector configuration. Save the project.

Step 7

Back to the Message Flow view, and you need to Locate the Set Payload on the right hand-side palette to return the address book name.

Drag the component over to the canvas and write this value:

Step 8

Back to the Message Flow view, and you need to Locate the Filter Expression on the right hand-side palette to return the address book name.

Drag the component over to the canvas and write this value:

Step 9

Back to the Message Flow view, and you need to Locate the For Each on the right hand-side palette to return the address book name.

Drag the component over to the canvas and write this value:

Step 10

Back to the Message Flow view, and you need to Locate the Dom to XML on the right hand-side palette to return the address book name.

Drag the component over to the canvas:

Step 11

Back to the Message Flow view, and you need to Locate the Variable on the right hand-side palette to return the address book name.

Drag the component over to the canvas and write this variable Name and its value:

Name:

Value:

Step 12

Back to the Message Flow view, and you need to Locate the File on the right hand-side palette to return the address book name.

Drag the component over to the canvas and write this values:

Path: demo File Name/Pattern: events_outbound_#[ediID].xml Connector: create a new connector configuration

Step 13

Finally, run the example as a Mule application

Step 14

Enter a Customer using Customer Master information:

Application: P03013

Version ZJDE0002*

Step 15

Check file generated

This use case example will create a simple flow to generate a Order Acknowledgments (855/ORDRSP) document in a local folder.

First, you need to create a new UBE version for R42565 or use standard XJDE0003 version.

and configure Processing Options:

The last configuration that is needed is inform to JDE connector the EDI outbound:

Using "Flat File Cross-Reference (P47002)" form "Work With Flat File Cross-Reference" adds the following record:

Follow next steps to create a flow that it will capture EDI outbound to generate EDI doc in a local folder.

Step 1

Use Mule Project created in the Create Mule Project Section.

Step 2

Locate the Poll Endpoint connector on the right hand-side palette:

Step 3

Drag the JDE connector over to the canvas:

Step 4

You need to select the operation EDI Outbounds:

Step 5

Now, you need to select Capure EDI Transactions in the Entity Type field and press ENTER:

Step 6

Now, You will need to populate the parameters. To do this, you need to select the option: Create Object manually

Press the button […​] and populate the parameters:

EDI Code Enter 855 value

EDI Document Type Enter SO value

EDI Last EDI Document: Enter #[0L] value

EDI UBE-VERSION to update Transaction Enter R47027-XJDE0001 value. Standard UBE to update Order Acknowledgments

Max Qty Transactions to Read: Enter 10 value

Press OK button to return to JDE Connector configuration. Save the project.

Step 7

Back to the Message Flow view, and you need to Locate the Set Payload on the right hand-side palette to return the address book name.

Drag the component over to the canvas and write this value:

Step 8

Back to the Message Flow view, and you need to Locate the Filter Expression on the right hand-side palette to return the address book name.

Drag the component over to the canvas and write this value:

Step 9

Back to the Message Flow view, and you need to Locate the For Each on the right hand-side palette to return the address book name.

Drag the component over to the canvas and write this Collection Expression:

Step 10

Back to the Message Flow view, and you need to Locate the Dom to XML on the right hand-side palette to return the address book name.

Drag the component over to the canvas:

Step 11

Back to the Message Flow view, and you need to Locate the Variable on the right hand-side palette to return the address book name.

Drag the component over to the canvas and write this variable Name and its value:

Name:

Value:

Step 12

Back to the Message Flow view, and you need to Locate the X12 on the right hand-side palette to return the address book name.

Drag the component over to the canvas and write this values:

Create a new Connector Configuration:

You will need to select the Schema. To do this, you need to select the option: Create Object manually and press the button […​]:

Then, you need to select Write Operation from Payload:

Now you need to configure Sender Identification and Receiver Identification:

Step 13

Back to the Message Flow view, and you need to Locate the Transform Message on the right hand-side palette.

Drag the component over to the canvas between Variable and X12 component:

Switch to the XML view by clicking Configuration XML and replace CDATA element inside Transform Message definition with:

with

Step 14

Back to the Message Flow view, and you need to Locate the File on the right hand-side palette to return the address book name.

Drag the component over to the canvas and write this values:

Folder: demo

File Name: events_outbound_#[ediID].edi

Connector: create a new connector configuration

Step 15

Finally, run the example as a Mule application

Step 16

Enter a Sales Order:

Then, invoke UBE R42565 XJDE0003 [ Batch EDI - P.O. Acknowledgment Transaction (855) ] for the order generated.

Step 17

Check file generated