JD Edwards services (AIS)
Nomajde reaches JD Edwards through its AIS server, with Oracle's documented REST services. It ships a catalogue of these services, ready to use: each one has a name, a description, named parameters that say what they expect with an example — and its own permission. They are the building blocks of everything Nomajde does with a live JD Edwards: screens on a JDE form, non-regression tests, jobs, and the requests made to the AI assistant.
At a glance
The catalogue
The services are the endpoints of the ais_connection connector, in Liberty Next → Data → Connectors.
Read
| Service | Returns | Parameters |
|---|---|---|
| AIS server configuration | The AIS release and its default environment. | — |
| Find a JDE object | The applications, tables, views, business functions and reports whose name or description holds a text. | FILTER, TYPES |
| Query a table or a view | Rows of a table or a business view, or their count. | TABLE, TYPE, KIND, COLUMNS, MAX, MATCH, CONDITIONS |
| A data item's labels | The title and description of a data dictionary item. | ITEM, SYSTEM |
| An application's processing options | The processing option values of an interactive application version. | APPLICATION, VERSION |
| A report's options and selection | The selection, the sequence and the options of a report version. | REPORT, VERSION |
| A report job's status | The state of a submitted report. | JOB, SERVER |
| A business function's parameters | Business functions and their parameters. | NAME, OBJECT or TEMPLATE |
| Orchestrations, One orchestration | The orchestrations AIS offers; for one, its description, its version, its inputs and outputs. | NAME |
| Notifications, Scheduled jobs | The notifications, the AIS scheduler and its jobs. | — |
Change JD Edwards
| Service | Does | Parameters |
|---|---|---|
| Run an orchestration | Runs an orchestration with its inputs, whatever its version. | NAME, VERSION, INPUTS |
| Run a business function | Runs a business function. | NAME, PARAMS, OUTPUTS |
| Submit a report | Submits a report version as it is saved. | REPORT, VERSION |
| Start a scheduled job, Stop a scheduled job | Starts or stops the schedule of an orchestration or a notification. | NAME |
These five are marked as changing data. Three parameters depend on the object and are written as JSON, with their example: the conditions of a query, the values of a business function, the inputs of an orchestration. To avoid the JSON, make an endpoint of its own for one report, one table, one function or one orchestration with Create from…: each input then becomes a labelled field.
Where a service is used
| From | How |
|---|---|
| The connector's Test tab | Fill the parameters and run it: the quickest way to try a service. |
| A screen | As an action in the toolbar or the row menu — submit a report for the selected row — or as the source of the screen's rows. |
| A job | As a step: nightly export, a report submitted and waited for, an orchestration run. See Jobs. |
| A test | As a step of a non-regression case. |
| The AI assistant | It reads with the reading services; for one that changes JD Edwards it shows a card to approve first. |
What JD Edwards sees
Every call runs under the JD Edwards account of the connector: JD Edwards security applies to that account, the audit records it, and texts come back in its language. Give it the rights the integrations need, no more.
What JD Edwards refuses is reported in its own words. A business function's error fails the call with its message; a warning — Duplicate Address Book record exists — is reported with the answer and the call stands.
Access
Each service has its permission, api:ais_connection:<service>, granted in a role's Beyond the menus rules. A role can therefore read tables without being able to submit a report, or run one orchestration and no other.
- Grant the reading services to the teams that build screens and tests.
- Grant the five services that change JD Edwards sparingly — or better, grant the specific endpoints made with Create from….
- The connector also holds a generic service, AIS service (generic, used by nomajde.ais), kept for Nomajde's own code: it reaches every AIS service, so it is granted to no role.
For the AI assistant, a service that changes JD Edwards also requires the user to be allowed to change data through the assistant, and is never called without an approved card.
Tips & best practices
- Try a service in the Test tab before putting it in a job or a screen.
- Query a table or a view with
KIND=COUNTanswers a volume question without reading the rows. - Use a dedicated JD Edwards account for the connector, so that the audit separates what Nomajde did from what a person did.
- When the same JSON is typed twice, it is time for Create from….
Related
- Create from… — endpoints and screens from JD Edwards.
- API endpoints — the endpoint editor of Liberty Next.
- Server Manager — the same approach for the Server Manager console.