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

• RunMyJobs 9.2.9 or later
• Connection Management Extension 1.0.0.4 or later. Note that the Connection Management Extension will be installed or updated automatically if necessary when you install this Connector.
• 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

Setup

1. Locate the JD Edwards EnterpriseOne Connector in the Catalog and install it.
2. Navigate to Configure > Admin > Security > Connections.
3. Click New.

4. Select the EnterpriseOne Connection type.

5. Click Next or Basic Properties, then create a Queue and Job Server for the Connection. 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 Job Server, View Processes on the JD Edwards Connector Jobs Queue, View on library REDWOOD.Redwood_EnterpriseOne, and Run on any Job Definitions users with this role are to run.
   
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 Configure > Control > Job Servers, locate the JD Edwards Connector Job Server, start it, and make sure it reaches status Running.

Job Definitions

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 Job 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

Procedures

Finding JD Edwards Orchestrations

To retrieve the list of orchestrations available for scheduling:

1. Navigate to Applications > Redwood > JD Edwards EnterpriseOne , and run 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 Job has finished, right-click the Job Definition and choose Monitor Related Processes, then select the Job 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, run 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. Run the Job Definition.

Running a JD Edwards Orchestration with a Template

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

1. Right-click the Redwood_EnterpriseOne_RunOrchestrationTemplate Job Definition and choose New (from Template) from the context menu. The New Job Definition screen displays.

2. In the Definition tab, delete the default Folder value (if any) and substitute your own Folder 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 run the new Job 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 Out 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 Out 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 Job 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 In Parameters on the new Job Definitions, or N to not create them.
   Partition	The Partition to create the new Job Definitions in.
   Folder	The Folder to create the new Job Definitions in.
   Default Queue	The default Queue to assign to the generated Job Definitions.
   Definition Name Prefix	The prefix to add onto the name of the imported JD Edwards EnterpriseOne orchestration to create the Job Definition name.

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

Note: When you import a JD Edwards Orchestration, its Out Parameters will not be imported automatically. You must manually configure them on the generated Job 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 Job Definition for an orchestration, optionally with default values:

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

2. In the Definition tab, delete the default Folder value (if any) and substitute your own Folder 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 run the new Job 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.