1. Application Pack for Oracle Enterprise Manager Cloud Control 13c Implementation Guide
  2. Deploy the JDE AppPack into the Management Server

Deploy the JDE AppPack into the Management Server

Follow the steps in this section to deploy the JDE AppPack into the Management Server (also called OMS).

  1. In Oracle Enterprise Manager Cloud Control, navigate to Setup, Extensibility, Plug-ins.

    This image is described in the surrounding text.

  2. On the list of plugs, locate this item in the Name column:

    Oracle JD Edwards EnterpriseOne

    This image is described in the surrounding text.

    Cloud Control displays an icon in the Downloaded column if an item has not been deployed. If the icon exists, its hover text displays the following message:

    This image is described in the surrounding text.

    You can deploy a plug-in only if the above icon is displayed.

  3. With the undeployed plug-in highlighted, right-click and select Deploy On, Management Servers.

    This image is described in the surrounding text.

  4. On the Deploy Plug-ins on Management Servers, Plug-ins form, complete the details.

    This image is described in the surrounding text.

  5. Click the Next button.

    A progress panel is displayed indicating that the prerequisite checks are running.

    This image is described in the surrounding text.

  6. On the Deploy Plug-in on Management Servers, Prerequisite Checks form, verify that the checks completed successfully and click the Next button.

    This image is described in the surrounding text.

  7. On the Deploy Plug-in on Management Servers, Repository form, complete the required fields and click the Next button.

    This image is described in the surrounding text.

    The system displays the Deploy Plug-ins on Management Servers: Review form.

    This image is described in the surrounding text.

    On the Deploy Plug-in on Management Servers: Review form, the panel warns that deployment of the plug-in on the Management Server will require downtime. All currently connected users will get disconnected from the Enterprise Manager. During the downtime period, users will not be able to connect to Enterprise Manager and Enterprise Manager will not monitor any targets.

    Note: Oracle recommends that you back up the repository or ensure appropriate recovery plans are in place prior to deploying the plug-in.

  8. Click the Deploy button.

    This image is described in the surrounding text.

  9. On the Deploy Plug-in on Management Servers: Confirmation form, click the Show Status button. This Confirmation screen indicates that the deployment has started.

    The Enterprise Manager interface shows the starting progress of the deployment.

    However, since OMS is shut down during the deployment process, after a certain time during deployment, you cannot use the Enterprise Manager user interface to verify if the deployment is complete and that the OMS is back up.

    To determine simple status and whether OMS is up or down, use this line command:

    ./emctl status oms

    To view the deployment details, you can append the -details flag using this line command:

    ./emctl status oms -details

    Note: Any time you issue the check status command with the -details flag, you are prompted to provide the SYS user password for the Enterprise Manager database as shown in the sample below.
    This image is described in the surrounding text.

    As the deployment progresses and you check status, a series of steps are performed. The step that indicates the deployment is complete is called Starting OMS, as shown in the sample below.

    This image is described in the surrounding text.

    At this point OMS is being started. This means that deployment is complete and that the Enterprise Manager console should be available very soon, depending on how long the actual startup takes to complete.