2 Getting Started

This chapter describes how to download and install the components required to implement notifications. It contains the following topics:

Certifications (Formerly Known as Minimum Technical Requirements)

Customers must conform to the supported platforms for the release, which can be found in the Certifications tab on My Oracle Support: https://support.oracle.com. Specifically for the EnterpriseOne Orchestrator, refer to the certifications for the JD Edwards EnterpriseOne AIS Server product. For certifications for the Orchestrator Studio, refer to the JD Edwards EnterpriseOne ADF Foundation product.

For more information about JD Edwards EnterpriseOne Minimum Technical Requirements, see the following document on My Oracle Support: JD Edwards EnterpriseOne Minimum Technical Requirements Reference (Doc ID 745831.1), which is available here:

https://support.oracle.com/rs?type=doc&id=745831.1

Prerequisites

Complete the following prerequisites:

Installing Delivered Notification Content (Release 9.2.2.4)

Many notifications have been created and delivered for your use via UDOs. Each system has its own set of notifications that can be downloaded from the Update Center or by using Change Assistant. For a complete list of available notifications, along with additional information about them, see the JD Edwards EnterpriseOne Delivered Notifications document (2365066.1) on My Oracle Support. It can be accessed here:

https://support.oracle.com/epmos/faces/DocumentDisplay?id=2365066.1

Test the Orchestrator Studio Implementation for Notifications

To test the Orchestrator Studio implementation for notifications, you can create and run a simple notification to ensure that everything is working correctly. This section walks you through creating a very simple notification to test your set up.

To test the Orchestrator Studio implementation for notifications:

  1. Sign on to Orchestrator Studio.

  2. Click the Notifications icon.

  3. Click the New button on the side panel, if you are using the Orchestrator Studio 9.2.4.

    If you are using the previous version of the Orchestrator Studio, click the New Notification button.

  4. Give the new Notification a name (such as Test Notification).

  5. Leave the Notification Type as "Simple."

  6. Click the triangle to open the Message section of the Notification design page.

  7. Type a subject and a body for the notification.

  8. Click the Save icon.

  9. Click the Tools link.

  10. Click the JD Edwards EnterpriseOne icon to launch the EnterpriseOne web client in a new browser tab.

  11. Sign on to EnterpriseOne using the same user ID you used to sign on to Orchestrator Studio.

  12. Click the drop-down list under the user ID in the upper-right hand corner and choose My Subscriptions.

  13. Click Add Subscription and choose the notification you created in the Orchestrator Studio.

  14. Click the Save icon.

  15. Return to the Orchestrator Studio browser tab.

  16. Click the Notification link in the top-left corner and return to the notification you created.

  17. Click the Test button.

  18. Click the switch to Dispatch Notifications.

  19. Click the Execute button.

    You should receive a response that looks like this:

    {
      "success": true,
      "received": false
    }
    
  20. Go back to the browser tab with your EnterpriseOne web client session.

  21. Click the X button to close the Subscription Manager form.

  22. In the EnterpriseOne menu bar, click the Notification List (bell) icon to open the notification list. Verify that you received the notification you created.

Set Up Security for Notification Designers Using Orchestrator Studio

Notification designers will use the Orchestrator Studio to build and test notifications. After setting up the Orchestrator Studio and testing the Orchestrator implementation, you need to set up security to grant notification designers access to the Orchestrator Studio design pages and features. See "Administering the Orchestrator Studio and Orchestrations" in the JD Edwards EnterpriseOne Tools Orchestrator Guide for more information.

Tuning Your Configuration (Release 9.2.2.4)

After you have your notifications up and running, you may want to revisit some of the configuration settings to ensure that you are using the best setup for your organization.

Roles and Purging User Cache

Depending on how often role assignments change or how often users join and leave your organization, you should consider adjusting the User Cache Purge Interval in the Notifications section of the Server Manager configuration settings. The default value is 1440 minutes (24 hours).

If users are not seeing their changes, this could mean that role or enabled user changes are not in effect because this value is set too high and there is too much time between user cache purges.

If users are experiencing delays in receiving their notifications, this could be due to the value for this setting being too low and the system's resources being consumed by too many user cache refreshes.

Discrepancy in Results Between Notification Messages and Applications or Watchlists

If users are seeing a different number of records in their notification message than in the associated application or Watchlist, this could be the result of the notification being run as a proxy user rather than as the subscriber. In other words, the notification designer did not enable the Run as Subscriber option when creating the notification. If the data security settings differ between the proxy user (the person who started the notification job on the AIS Server) and the subscriber, this discrepancy can occur. If you decide not to use the Run As Subscriber option for a particular notification, consider any security implications and data discrepancies. Although running as a proxy user may improve performance, it can also create discrepancies in results. Because each notification is unique to your organization, you must decide what is appropriate on a case-by-case basis.