Among the many functions of JD Edwards EnterpriseOne Orchestrator Studio, the tool simplifies data exchange. In a world that increasingly expects devices to talk to one another, this can mean the difference between transformation and stagnation. We last looked at the process for exporting JDE data to a format preferred by your external application, system, or device. Now, let's look at bringing data into JDE with orchestration.
The basics of importing data
REST services typically leverage JSON because the output notation is easy for people, applications, and web services to read. That being the case, JSON is the default input/output format for orchestration across all EnterpriseOne tools releases. JDE users running E1 126.96.36.199 up to 188.8.131.52 can write a custom Groovy script to convert XML or CSV to JSON before importing. But E1 184.108.40.206 users have it easy. The ability to import XML or CSV data is baked right in.
In our exporting data blog, we explored how to set your custom HTTP headers and shared sample JSON cURL commands. These apply to data imports as well. However, the process changes when working with CSV. EnterpriseOne 220.127.116.11 is the ideal for CSV orchestration because it allows multiple line entry. Oracle support has an excellent example in Doc ID 2564800.1.
E1 18.104.22.168 orchestrations for importing data
To create a CSV import orchestration in E1 22.214.171.124, your CSV must include an FTP connection and connector for your orchestration to read. Learn more about configuring the FTP connector/connection in Doc ID 2564800.1 and on learnjde.com. Then follow these three high-level steps:
- First, create a service request to import the data into the application, for example, P4210. You can create the request manually or by using the Orchestrator Process Recorder.
- Next, build an orchestration with generic JSON input. This way, you can test the basic service request flow before modifying the orchestration to handle CSV input.
- Finally, create a service request for an FTP connector. Then, configure a transformation to iterate over the lines/records in the CSV file you have mapped.
With template(s) in place and a bit of practice, the process becomes relatively straightforward.
Orchestration tips for importing data
- Remember, orchestrations operate with the same system/architecture settings as web users. Therefore, a CSV input orchestration is similar to a spreadsheet grid import. The JAS grid import is limited to 1,000 rows by default. But with enough JVM heap, you can increase it to 10,000 rows.
- If your application only allows 1,000 rows of input, use multiple sets of entry. Application limits are one reason some architectures separate the AIS/JAS instances on a dedicated server depending on business requirements/processes to provide more resources.
- Change the JAS instance Maximum Request Parameters default to ensure your record count is not limited. We generally set the parameter to 500,000. Learn more.
- Set the AIS and JAS instance Java heap min/max size. A good starting point for the AIS instance is between 256m and 1024m. The JAS instance used by AIS for orchestrations varies from 1024m to 6192m. We set most configurations between 1024m and 2048m then monitor the JVM heap usage.
JSON may be the standard for inputting data, but it isn't your only option. Get familiar. Get creative. Use a combination of input and output notations to automate data flow and connect your digital ecosystem.
ERP Suites is a JD Edwards Gold Partner and winner of the 2019 Oracle Distinguished Partner Award for Successful Adoption of Orchestrator. Look for more tech tips from our Orchestrator consultants at the Collaborate 20 virtual conference.