Prerequisites

Complete the following prerequisites:

• You must be running a minimum of EnterpriseOne Tools Release 9.2.4 and apply any required ESUs for EnterpriseOne 9.2 as described on My Oracle Support.

  Always apply the latest EnterpriseOne Tools software update to be able to use the latest available features.

• Deploy an Application Interface Services (AIS) Server.

  You can use an existing AIS Server or deploy a new AIS Server instance through Server Manager for the sole purpose of running orchestrations. It is recommended that you set up two AIS Server instances for an Orchestrator configuration, one for testing notifications and one for production. See "Create an Application Interface Services (AIS) Server as a New Managed Instance" in the JD Edwards EnterpriseOne Tools Server Manager Guide.

  For an AIS Server deployed on Oracle WebLogic Server, there is an additional required configuration that enables the Orchestrator Client (the tool for testing orchestrations) to run properly. See "Configuring Oracle WebLogic Server Domain for HTTP Basic Authentication" in the JD Edwards EnterpriseOne Application Interface Services Server Reference Guide.

• Deploy the JD Edwards EnterpriseOne Orchestrator Studio 9.2.4. See "Getting Started" in the JD Edwards EnterpriseOne Tools Orchestrator Guide for details on the latest release. (Release 9.2.4.0)

  For the previous versions of the Orchestrator Studio, download the Orchestrator components from the Update Center on My Oracle Support: https://updatecenter.oracle.com/. See "Getting Started" in the JD Edwards EnterpriseOne Tools Orchestrator Guide for Studio Version 8 and Prior for details.

• Ensure that the Notifications feature is enabled and that all related UDO security is set up properly.

  For more information, see:

  • "Managing UDO Feature Security" in the JD Edwards EnterpriseOne Tools Security Administration Guide

  • "Define Allowed Actions for UDO Types" in the JD Edwards EnterpriseOne Tools Security Administration Guide

  • "Setting up UDO Security for Orchestrator Studio Users" in the JD Edwards EnterpriseOne Tools Orchestrator Guide for Studio Version 8 and Prior.

• Ensure that the EnterpriseOne HTML Server and AIS Server keystores are set so that both are either using the demo keystore or using the same certificate.

  If you want to configure your own keystore, see "Configuring EnterpriseOne HTML Server for JSON Web Token (JWT) (9.2.3.2)" or "Configuring EnterpriseOne HTML Server for JSON Web Token (JWT) (9.2.0.5)" in the JD Edwards EnterpriseOne Tools Security Administration Guide

• Ensure that the HTML Server is configured as a trusted node for the Security Server. This is necessary if you plan to use the "Run As Subscriber" functionality with your notifications.

  See "Setting Up JD Edwards EnterpriseOne Single Sign-On" in the JD Edwards EnterpriseOne Tools Security Administration Guide.

• Ensure that shortcuts are enabled for the default HTML Server so that any shortcuts emailed in notification messages function properly.

  For more information, see:

  • "Configuring Shortcuts" in the JD Edwards EnterpriseOne Tools Workflow Tools Guide.

  • "Defining Shortcut Links" in the JD Edwards EnterpriseOne Tools Workflow Tools Guide.

• Update the Enterprise Server Email (SMTP) Configuration to ensure that email functions properly.

  See "Updating the JDE.ini file on the Workstation and the Enterprise Server" in the JD Edwards EnterpriseOne Tools Workflow Tools Guide.

• If allowing subscribers to specify email addresses as a delivery method in Subscription Manager, ensure that the setting in Server Manager specifies this. To do so, go to the Notifications section of Server Manager configuration settings, and make sure that the Allowed External Delivery Methods setting contains the value "email." This is the default value for this setting. (Release 9.2.2.1)