JD Edwards EnterpriseOne Connector 1.0.0.0

The JD Edwards EnterpriseOne Connector lets you import and run JD Edwards EnterpriseOne orchestrations and reports.

Prerequisites

• Version 9.2.9 or higher.
• Connection component 1.0.0.4 or later. Note that the Connections component will be installed or updated automatically if necessary when you install this extension.
• Privileges Required to Use the JD Edwards EnterpriseOne Connector.
• JD Edwards EnterpriseOne Application Interface Services (AIS) Server, with a REST API that can be reached via outbound HTTP from the Secure Gateway (for SaaS customers) or the RunMyJobs Scheduler (for on-site installations).

Contents of the Component

The JD Edwards EnterpriseOne Connector consists of the following objects.

Redwood_EnterpriseOne_ImportOrchestrations

Imports orchestrations from JD Edwards EnterpriseOne.

Parameters

Redwood_EnterpriseOne_RunOrchestration

Runs an orchestration in JD Edwards EnterpriseOne.

Parameters

Redwood_EnterpriseOne_RunOrchestrationTemplate

Template definition to run an orchestration in JD Edwards EnterpriseOne.

Parameters

Redwood_EnterpriseOne_RunReport

Runs a report in JD Edwards EnterpriseOne.

Parameters

Redwood_EnterpriseOne_RunReportTemplate

Template Definition to run a report in JD Edwards EnterpriseOne.

Parameters

Redwood_EnterpriseOne_ShowOrchestrations

Lists all existing orchestrations in JD Edwards EnterpriseOne.

Parameters

Setup

1. Locate the JD Edwards EnterpriseOne component in the Catalog and install it.
2. Navigate to Custom > Connections.
3. Click .

4. Select the EnterpriseOne connection type.

   

5. Click Next or Basic Properties, then create a Queue and Process Server for the connector. All required settings will be set up automatically.

   

6. ClickNext or Security, then click to specify which roles can access the connection information. It is recommended to grant the role at least the following additional privileges: View on the JD Edwards Connector Process Server, View Processes on the JD Edwards Connector Jobs Queue, View on library REDWOOD.Redwood_EnterpriseOne, and Submit on any Process Definitions users with this role are to submit.
   
7. ClickNext or EnterpriseOne Properties
8. Enter the URL of the JD Edwards AIS server in the Endpoint field.
9. Enter your JD Edwards Username and Password.
10. Click Save & Close.
11. Optionally, enter your JD Edwards Environment identifier and Role.
12. Navigate to Environment > Process Server, locate your JD Edwards Connector Process Server, start it, and ensure it reaches status Running.

Finding JD Edwards Orchestrations

To retrieve the list of orchestrations available for scheduling:

1. Navigate to Applications > Redwood > JD Edwards EnterpriseOne , and submit Redwood_EnterpriseOne_ShowOrchestrations.

2. Select the Connection.

3. To specify a search string, enter a value in the Orchestration Name Filter field. Wildcards * and ? are supported.

   

4. Once the process has finished, right-click it and choose Monitor Related Processes, then select the process run and click listing.rtx in the Detail View. Sample output is shown below.

   

Running a JD Edwards Orchestration

To run an orchestration:

1. In the JD Edwards EnterpriseOne Application, submit Redwood_EnterpriseOne_RunOrchestration.

2. Select the Connection.

3. Specify the Orchestration Name to run.

   

4. If you specify Parameters, use a key=value format for each parameter, as demonstrated in the following screen shot.

   

5. Submit the Process Definition.

Running a JD Edwards Orchestration with a Template

To create a customized Process Definition, optionally with default values, for an orchestration:

1. Right-click the Redwood_EnterpriseOne_RunOrchestrationTemplate Process Definition and choose New (from Template) from the context menu. The New Process Definition pop-up window displays.

2. In the Definition tab, delete the default Application value (if any) and substitute your own Application name if desired.

3. In the Parameters tab, enter any Default Expressions you want to use.

   • When specifying the Connection value, use the format EXTCONNECTION:<partition>.<connection name>.

4. In the Parameters tab, specify orchestration parameters by adding them to a parameter group named Orchestration Parameters.

   

5. Save and then submit the new Process Definition.

Out Parameters

When configuring Out parameters in a Job Definition created from a template, use the following guidelines. The JSON below is a sample response used in this section.

{
  "Prop1": "value1",
  "Prop2": "value2",
  "SubObject": {
    "Prop1": "sub value 1",
    "Prop3": "value3"
  },
  "stringArray": [
    "string1",
    "string2"
  ]
}

The default behavior is to look up the first JSON node whose name matches an Out parameter name, and assign the node's value to the Out parameter. For example, using the above JSON, if you create an Out parameter named Prop1, its output value will be value1.

This rule applies to nested elements as well. If you add an Out parameter named Prop3, its output value will be value3.

If there are multiple occurrences of Prop1:

• If the parameter is an Array parameter, all matching values (here, [value1, sub value 1]) are in the parameter's value.

• If the parameter is NOT an Array parameter, only the first value (here, value1) are in the parameter's value.

If a property points to an object, it will be included in output as a JSON String. For example, if you add a String Out parameter named SubObject, the value of the output parameter will be {"Prop1": "sub value 1", "Prop3": "value3"}.

You can map arrays to Array parameters. For example, if you add an Array Out parameter named stringArray, the value of the output parameter will be an array (here, ["string1", "string2"]). However, if you map an array to an Out parameter that is not an Array parameter, only the first value of the array is assigned to the parameter (here, "string1")

String and Number parameters are supported for both single values and arrays.

• A number value or array of numbers can be assigned to a String parameter or a Number parameter.

• Only numbers can be assigned to a Number parameter. Attempting to provide a string to a Number parameter will result in that parameter not receiving a value. A warning message will be logged in the stdout.log file.

If an Out parameter does not map to any property in the JSON, the parameter will not be assigned a value. This will not fail the job automatically, but it will write a warning message to the stdout.log file.

Importing a JD Edwards Orchestration

To import an orchestration as a RunMyJobs Process Definition:

1. Submit Redwood_EnterpriseOne_ImportOrchestrations.

2. Select the Connection.

3. To specify a search string, enter a value in the Orchestration Name Filter field. Wildcards * and ? are supported.

   

4. In the Generation Settings tab, configure the options as follows.

   Name	Description
   Overwrite Existing Definition	Set to Y to overwrite existing orchestrations, or N to create new ones.
   Import Parameters	Set to Y to create any input parameters on the new Process Definitions, or N to not create them.
   Partition	The Partition to create the new Process Definitions in.
   Application	The Application to create the new Process Definitions in.
   Default Queue	The default Queue to assign to the generated Process Definitions.
   Definition Name Prefix	The prefix to add onto the name of the imported JD Edwards EnterpriseOne orchestration to create the Process Definition name.

5. Submit the Process Definition. When the process completes, you should have one or more new Process Definitions that are named after the imported orchestrations.

Note: When you import a JD Edwards Orchestration, its output parameters will not be imported automatically. You must manually configure them on the generated Process Definition(s).

Running a JD Edwards Report

In the JD Edwards EnterpriseOne Application, submit Redwood_EnterpriseOne_RunReport. Specify the Report Name and, optionally, Report Version.

Running a JD Edwards Report with a Template

To create a customized Process Definition for an orchestration, optionally with default values:

1. Right-click the Redwood_EnterpriseOne_RunReportTemplate Process Definition and choose New (from Template) from the context menu. The New Process Definition pop-up window displays.

2. In the Definition tab, delete the default Application value (if any) and substitute your own Application name if desired.

3. In the Parameters tab, enter any Default Expressions you want to use.

   • When specifying the Connection value, use the format EXTCONNECTION:<partition>.<connection name>.

   

4. Save and then submit the new Process Definition.

Configuration Options

You can configure the Connect and Read timeout values for EnterpriseOne via the registry keys listed below. To test that the values are set correctly, run the process in debug mode. RunMyJobs will log the configuration in the stdout.log file.