Understanding Orchestration Life Cycle Management (Release 9.2.1)
Starting with EnterpriseOne Tools 9.2.1 and Orchestrator Studio 3.0.1, orchestration components created in the Orchestrator Studio are stored as user defined objects (UDOs) in EnterpriseOne. Each orchestration component type—orchestration, service request, rule, cross reference, white list—is a separate UDO type in EnterpriseOne. Orchestrator Studio 6.0.x provides the capability to create notification and schedule components, which are also stored and managed as UDOs in EnterpriseOne.
Storing orchestration components as UDOs enables you to use the following EnterpriseOne administration tools to manage the life cycle and security for orchestration UDOs:
Object Management Workbench - Web (P98220W)
Use this application to move orchestration UDOs between projects, check out and check in objects, and transfer objects between path codes. After Orchestrator Studio users create and test orchestrations in a test environment, use P98220W to transfer the objects to an AIS Server in a production environment. See the JD Edwards EnterpriseOne Tools Object Management Workbench for the Web Guide for more information.
User Defined Object Administration (P98220U)
An administrator or person in a supervisor role uses this application to approve or reject orchestration UDOs for sharing. Typically, you can inspect UDOs in P98220U before approving them or rejecting them. However, you can only inspect orchestration component UDOs in the Orchestrator Studio. See the JD Edwards EnterpriseOne Tools Using and Approving User Defined Objects Guide for more information on how to use P98220U.
Security Workbench (P00950)
Use Security Workbench to set up UDO feature, UDO action, and UDO view security, which authorizes access to the Orchestrator Studio design pages and determines the actions users can perform in the design pages. See Setting Up UDO Security for Orchestrator Studio Users (Release 9.2.1) in this guide for more information.
It is recommended to set up different instances of the AIS Server: one instance for designing and testing orchestrations and another instance for production. Running two instances can also help with troubleshooting orchestration issues in a production environment. In the Object Management Workbench - Web application, you can move an orchestration from a production environment to a test environment for troubleshooting.