Orchestration components (UDO)

Начиная с TR 9.2.3 система автоматически запускает orchestration или notification по следующим позициям:

• A table trigger
• A button on a form
• Changing the status of an event
• A UBE

Orchestrator использует следующие компоненты (из Orchestrator Studio) для трансформации RAW-данных в данные используемые EnterpriseOne:

• Orchestration. The master process that defines the inputs for the orchestration and provides a unique name for the orchestration process in the Orchestrator. An orchestration uses the next four components in this list to run a single orchestration instance.

• Service request. An invocation of a JD Edwards EnterpriseOne interactive application or a Java application via a REST service call to the EnterpriseOne Application Interface Services (AIS) Server.

• Rule. Contains a set of conditions against which the orchestration input is evaluated to produce a true or false state. Rules can be nested to produce complex evaluations. Rules determine how the orchestration is processed at runtime. You can also use custom Java to define additional rules.

• Cross reference. A set of data relationships defined by the designer of the orchestration that enriches the minimal input from devices. For example, a device's serial number can be cross-referenced to a JD Edwards EnterpriseOne Equipment Number for use in service requests.

• White list. An initial rudimentary pass/fail check of the incoming message's device signature against a predefined list of signatures. A white list provides an additional layer of security to the Orchestrator security.