Skip Headers
JD Edwards EnterpriseOne Application Pack for Oracle Enterprise Manager Cloud Control Implementation Guide
Release 9.1

E26776-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

6 Deploy the JDE App Pack into the Management Server

This chapter contains the following topics:

6.1 Prerequisites to Deploying the JDE AppPack into the Management Server

You can install the JDE AppPack to the Enterprise Manager Management Server after you have installed:

Additionally you must have already set up a Software Library as described in the chapter of this guide entitled: Chapter 4, "Set Up the Software Library within Cloud Control".

Further, you must have already imported the JDE AppPack as described in the chapter of this guide entitled: Chapter 5, "Import the JD Edwards Application Pack OPAR".

The JDE AppPack is deployed using Cloud Control. As a prerequisite, you must have an existing Cloud Control and Oracle database installation. The JDE AppPack must be deployed into each existing Cloud Control Management Server.

6.2 Deploy the JDE AppPack into the Management Server

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

This image is described in surrounding text.
Description of the illustration deploy_oms_plugins.gif

  1. In Oracle Enterprise Manager Cloud Control, navigate Setup > Extensibility > Plugins

    This image is described in surrounding text.
    Description of the illustration deploys_oms_icon.gif

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

    Oracle JD Edwards EnterpriseOne

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

    This image is described in surrounding text.
    Description of the illustration hover_text.gif

    You can only deploy a plugin if the above icon is displayed.

    This image is described in surrounding text.
    Description of the illustration deploy_oms_man_server.gif

  3. With the undeployed plugin highlighted, right click and choose Deploy On > Management Servers...

    This image is described in surrounding text.
    Description of the illustration deploy_oms_general.gif

  4. On Deploy Plug-in on Management Servers, General, enter the password for the SYS user of the EM repository.

  5. Click the Continue button.

    This image is described in surrounding text.
    Description of the illustration deploy_oms_checks.gif

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

    This image is described in surrounding text.
    Description of the illustration deploy_oms_checks_done.gif

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

    This image is described in surrounding text.
    Description of the illustration deploy_oms_review.gif

    On Deploy Plug-in on Management Servers, Review, 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.

  7. Oracle recommends that you backup the repository or ensure appropriate recovery plans are in place prior to deploying the plug-in. Before you can proceed, you must click this checkbox:

    Have you backed up the repository?

  8. Click the Deploy button.

    This image is described in surrounding text.
    Description of the illustration deploy_oms_show_status.gif

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

    This image is described in surrounding text.
    Description of the illustration deploy_oms_status.gif

    The EM interface shows the beginning progress of the deployment.

    However, since OMS is shut down during the deployment process, after a certain point in the deployment you cannot use the EM user interface to check the status and verify that it is complete and that OMS is backup.

    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 will be prompted to provide the SYS user password for the EM database as shown in the sample below.
    This image is described in surrounding text.
    Description of the illustration prompt_sys_password.gif

    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 surrounding text.
    Description of the illustration deploy_oms_status_done.gif

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