JD Edwards EnterpriseOne

Application Pack for Oracle Enterprise Manager Cloud Control Implementation Guide

Release 8.98 Update 4

E22498-01

November 2011

JD Edwards EnterpriseOne Application Pack for Oracle Enterprise Manager Cloud Control Implementation Guide, Release 8.98 Update 4

E22498-01

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

List of Figures

Preface

- Audience

- Documentation Accessibility

- Conventions

1 Introduction

- 1.1 Additional Information

- 1.1.1 Oracle Enterprise Manager Cloud Control (EMCC)

- 1.1.2 JD Edwards EnterpriseOne Tools Documentation

- 1.1.3 JD Edwards EnterpriseOne Applications Release Installation Documentation

- 1.1.4 JD Edwards EnterpriseOne Tools 8.98 Server Manager Guide (Doc ID 705509.1)

- 1.1.5 JD Edwards EnterpriseOne Reference Guides

- 1.1.5.1 JD Edwards EnterpriseOne Tools Release Reference Guides (Doc ID 705462.1)

- 1.1.5.2 JD Edwards EnterpriseOne HTML Web Server Reference Guides

- 1.1.5.3 JD Edwards EnterpriseOne Transaction Server Reference Guides

- 1.1.5.4 JD Edwards EnterpriseOne PIMSync Server Reference Guides

- 1.1.5.5 JD Edwards EnterpriseOne Collaborative Portal Server Reference Guides

- 1.1.5.6 JD Edwards EnterpriseOne Business Services Server Reference Guides

- 1.1.5.7 JD Edwards EnterpriseOne Data Access Server Reference Guides

- 1.2 Minimum Technical Requirements for JDE AppPack

- 1.3 Minimum Technical Requirements for EMCC

- 1.4 JDE AppPack Installer Versions

- 1.5 Obtaining Oracle Software Components from the Oracle Software Delivery Cloud

- 1.6 Compatible JDE AppPack and EMCC Versions

- 1.7 Overview Server Manager 8.98.1 for JD Edwards EnterpriseOne

- 1.8 Features at a Glance

- 1.9 Features of Server Manager That Are Not Supported by EMCC

- 1.9.1 jdelog.properties Logging

- 1.9.2 Java Environment

- 1.9.3 Kernel Ranges

- 1.9.4 Disk Space Usage

- 1.10 Limitations

- 1.10.1 EMCC Web App Services

- 1.10.2 Microsoft Windows Collection

- 1.11 Network Performance Considerations

- 1.12 Glossary of Terms

- 1.12.1 Administrator Account

- 1.12.2 Alerts

- 1.12.3 Beacon

- 1.12.4 Corrective Actions

- 1.12.5 Dashboard

- 1.12.6 Discovery Process

- 1.12.7 Enterprise Manager Cloud Control 12c (EMCC)

- 1.12.8 EMCC Agent

- 1.12.9 JD Edwards EnterpriseOne System

- 1.12.10 JD Edwards EnterpriseOne Global Unique Identifier (GUID)

- 1.12.11 Managed Targets

- 1.12.12 Management Repository

- 1.12.13 Oracle Management Agent (OMA)

- 1.12.14 Oracle Management Service (OMS)

- 1.12.15 Policies

- 1.12.16 Preferred Credentials

- 1.12.17 Roles

- 1.12.18 Service

- 1.12.19 System

- 1.12.20 Super Administrator Account

- 1.12.21 Topology Viewer

- 1.13 Deployment Architecture

2 Install the Database for Enterprise Manager

- 2.1 Running the Oracle Database Installer

- 2.2 Post Installation Required Database Configuration

3 Install Enterprise Manager Cloud Control (EMCC)

4 Set Up the Software Library within EMCC

5 Import the JD Edwards Application Pack OPAR

6 Deploy the JDE App Pack into the Management Server

- 6.1 Prerequisites to Deploying the JDE AppPack into the Management Server

- 6.2 Deploy the JDE AppPack into the Management Server

7 Deploy the JDE AppPack into the Management Agent

- 7.1 Prerequisites to Deploying the JDE AppPack into the Management Agent

- 7.2 Deploy the JDE AppPack into the Management Agent

8 Using EMCC with JD Edwards EnterpriseOne

- 8.1 Additional Information for EMCC

- 8.2 Using EMCC for the First Time

- 8.3 Accessing the EMCC Console

- 8.4 EMCC Home Page

- 8.5 Targets

- 8.6 Adding the JD Edwards EnterpriseOne Domain

- 8.7 JDE EnterpriseOne Domain Home Page

- 8.8 Members of the JD Edwards EnterpriseOne Domain

- 8.9 Updating the JD Edwards EnterpriseOne Domain (Refresh Discovery)

- 8.10 Configuration Topology

- 8.11 System Monitoring Dashboard

- 8.12 Monitoring Configuration

- 8.13 Latest Configuration Data

- 8.14 Runtime Metrics (Status, User Count, and Performance)

- 8.15 Configuration Metrics for JD Edwards EnterpriseOne

- 8.15.1 All Metrics for JD Edwards EnterpriseOne Enterprise Server

- 8.15.2 All Metrics for JD Edwards EnterpriseOne HTML Server

- 8.16 Accessing Server Manager from EMCC

- 8.17 Removing the JD Edwards EnterpriseOne Domain

- 8.18 Starting and Stopping Components of Enterprise Manager Environments

- 8.18.1 Starting Enterprise Manager Environment Components

- 8.18.2 Stopping Enterprise Manager Environment Components

9 Undeploy JDE AppPack Components

- 9.1 Undeploy the JD Edwards AppPack from the Management Agent

- 9.2 Undeploy the JD Edwards AppPack from Management Servers

10 Deinstall the Oracle Database and EMCC

- 10.1 Stop the Agent, OMS, and Database Using Line Commands

- 10.2 Deinstall the Oracle Database and EMCC Using OUI

List of Figures

- 1-1 Deployment Architecture Example

Preface

Welcome to the JD Edwards EnterpriseOneApplication Pack for Oracle Enterprise Manager Cloud Control Implementation Guide.

Audience

This guide is intended for system administrators and managers who are responsible for monitoring enterprise management systems.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Introduction

The JD Edwards EnterpriseOne Application Pack for Oracle Enterprise Manager Cloud Control, which hereafter in this document referred to as the JDE AppPack and EMCC, respectively.

The JDE AppPack allows you to use the graphical user interface of EMCC to monitor and manage your JD Edwards Server products. This product leverages the existing JD Edwards Server Manager functionality that monitors all entities constituting an EnterpriseOne installation. For example, Server Manager collects real time data for user sessions, Java memory usage, JDBj connection cache, EnterpriseOne kernel specific metrics, and prepared statement configurations.

Examples include:

- Service level management

- History and trending (usage, server metrics, uptime)

- Enhanced graphics and dashboards for administrators

- Reporting capabilities

- Single view of an organization's complete system topology, including JD Edwards EnterpriseOne, database, operating systems, non-JD Edwards EnterpriseOne applications

- Enhanced alerts for CPU and memory usage on a JD Edwards EnterpriseOne server, database usage, and overall application server usage

- JD Edwards EnterpriseOne Kernel Specific Metrics

This chapter contains the following topics:

- Section 1.1, "Additional Information"

- Section 1.2, "Minimum Technical Requirements for JDE AppPack"

- Section 1.3, "Minimum Technical Requirements for EMCC"

- Section 1.4, "JDE AppPack Installer Versions"

- Section 1.5, "Obtaining Oracle Software Components from the Oracle Software Delivery Cloud"

- Section 1.6, "Compatible JDE AppPack and EMCC Versions"

- Section 1.7, "Overview Server Manager 8.98.1 for JD Edwards EnterpriseOne"

- Section 1.8, "Features at a Glance"

- Section 1.9, "Features of Server Manager That Are Not Supported by EMCC"

- Section 1.10, "Limitations"

- Section 1.11, "Network Performance Considerations"

- Section 1.12, "Glossary of Terms"

- Section 1.13, "Deployment Architecture"

1.1 Additional Information

The JDE AppPack runs within the framework of Oracle EMCC. Therefore, as you install and use the features of EMCC, you may require additional information outside of what is provided in this guide.

1.1.1 Oracle Enterprise Manager Cloud Control (EMCC)

Oracle Enterprise Manager Cloud Control (EMCC) is Oracle's single, integrated solution for managing all aspects of the Oracle Grid and the applications running on it. EMCC also allows you to manage single instances of Oracle Database, Application Server, or Collaboration Suite using standalone consoles. For documents related to Enterprise Manager Cloud Control Patch Sets, such as Patch Set Notes and Bug List, refer to My Oracle Support.

The complete suite of EMCC guides is available at this link:

http://download.oracle.com/docs/cd/B16240_01/doc/nav/portal_booklist.htm

1.1.2 JD Edwards EnterpriseOne Tools Documentation

Many of the concepts and tasks described in this guide relate to JD Edwards EnterpriseOne administration tasks. These tasks are described in:

- JD Edwards EnterpriseOne Server and Workstation Administration Guide

All JD Edwards EnterpriseOne Tools guides, with the exception of installation and upgrade, are located on the Oracle Technology Network at this link:

http://www.oracle.com/technetwork/documentation/jdedent-098169.html

1.1.3 JD Edwards EnterpriseOne Applications Release Installation Documentation

JD Edwards EnterpriseOne applications release installation documentation and updates to the documentation are available on My Oracle Support. For example, for Applications Release 9.0, the guides are available in Doc ID 705463.1.

1.1.4 JD Edwards EnterpriseOne Tools 8.98 Server Manager Guide (Doc ID 705509.1)

Server Manager for JD Edwards EnterpriseOne is a web based application used to manage the complete lifecycle of the JD Edwards EnterpriseOne server products, specifically including the installation, configuration, and management of JD Edwards server products. The Tools Release 8.98 version of Server Manager and relevant updates of the guide are in Doc ID 705509.1.

1.1.5 JD Edwards EnterpriseOne Reference Guides

Additionally, various reference guides provide details on applicable tasks and topics external to Server Manager. For example, separate versions of the JD Edwards EnterpriseOne HTML Web Server Reference Guides contain installation and configuration information for the Oracle Application Server and the WebSphere Application Server. Platform and application server specific versions of these guides are available.

1.1.5.1 JD Edwards EnterpriseOne Tools Release Reference Guides (Doc ID 705462.1)

These guides contain reference information for JD Edwards EnterpriseOne Enterprise Servers. For Tools Release 8.98, refer to Doc ID 705462.1.

1.1.5.2 JD Edwards EnterpriseOne HTML Web Server Reference Guides

These guides contain reference information for JD Edwards EnterpriseOne HTML Web Servers. Platform-specific guides are provided for each type of Application Server. For Tools Release 8.98, refer to these Doc IDs:

- HTML Web Server running on Oracle Application Server

Doc ID 705507.1

- HTML Web Server running on WebSphere 6.0

Doc ID 705519.1

- HTML Web Server running on WebSphere 6.1

Doc ID 705495.1

1.1.5.3 JD Edwards EnterpriseOne Transaction Server Reference Guides

These guides contain reference information for JD Edwards EnterpriseOne Transaction Servers. Platform-specific guides are provided for each type of Application Server. For Tools Release 8.98, refer to these links:

- Transaction Server running on Oracle Application Server

Doc ID 705457.1

- Transaction Server running on WebSphere Application Server

Doc ID 705459.1

1.1.5.4 JD Edwards EnterpriseOne PIMSync Server Reference Guides

These guides contain reference information for JD Edwards EnterpriseOne PIM Sync Servers. Platform-specific guides are provided for each type of Application Server. For Tools Release 8.98, refer to Doc ID 705508.1.

1.1.5.5 JD Edwards EnterpriseOne Collaborative Portal Server Reference Guides

This guide contains reference information for all JD Edwards EnterpriseOne portals and platforms. For Tools Release 8.98, refer to Doc ID 705513.1.

1.1.5.6 JD Edwards EnterpriseOne Business Services Server Reference Guides

This guide contains reference information for all JD Edwards EnterpriseOne Business Servers on all platforms. For Tools Release 8.98, refer Doc ID 705461.

1.1.5.7 JD Edwards EnterpriseOne Data Access Server Reference Guides

These guides contain reference information for all JD Edwards EnterpriseOne Data Access Servers. Note that the installation of DAS is described in the Server Manager Guide.

- JD Edwards EnterpriseOne Interoperability Guide

- JD Edwards Enterprise Tools Release 8.98 BI Publisher for JD Edwards EnterpriseOne

These guides are located on the Oracle Technology Network at this link:

http://www.oracle.com/technology/documentation/jdedent.html

1.2 Minimum Technical Requirements for JDE AppPack

Customers must conform to the supported platforms for the release as detailed in the JD Edwards EnterpriseOne Minimum Technical Requirements. In addition, JD Edwards EnterpriseOne may integrate, interface, or work in conjunction with other Oracle products. Refer to the following link for cross-reference material in the Program Documentation for Program prerequisites and version cross-reference documents to assure compatibility of various Oracle products. Access the current Minimum Technical Requirements (MTR) for the JD Edwards EnterpriseOne products from My Oracle Support:

https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=747323.1

1.3 Minimum Technical Requirements for EMCC

Oracle Application Management Pack and Agent are supported on the same platforms where Oracle Enterprise Manager 11g is released and supported. Refer to certification information in the Oracle Enterprise Manager 11g Cloud Control Certification Checker on My Oracle Support. Patch sets are available on My Oracle Support or Oracle Technology Network.

1.4 JDE AppPack Installer Versions

Releases and versioning of the installer for the JDE AppPack are scheduled to closely follow the releases and versions of EMCC; however, the releases of cumulative patches will occur with each update release of JD Edwards EnterpriseOne. A full installer is provided for each version of the JDE AppPack.

When you install the full JDE AppPack, or upgrade it with a cumulative patch, you must ensure that your JD Edwards EnterpriseOne Server Manager is at the same release level as the JDE AppPack.

1.5 Obtaining Oracle Software Components from the Oracle Software Delivery Cloud

All Oracle software components are downloaded from the Oracle Software Delivery Cloud at this link:

https://edelivery.oracle.com/

1.6 Compatible JDE AppPack and EMCC Versions

The JDE AppPack for Oracle EMCC 12c depends on and coincides with JD Edwards EnterpriseOne 8.98.1 of Server Manager. The JDE AppPack is scheduled to be versioned with new versions of EMCC.

1.7 Overview Server Manager 8.98.1 for JD Edwards EnterpriseOne

Server Manager for JD Edwards EnterpriseOne is a web based application used to manage the complete lifecycle of the JD Edwards EnterpriseOne server products. The JDE AppPack leverages the existing JD Edwards Server Manager functionality. Server Manager is required for all JD Edwards EnterpriseOne installations running Tools Release 8.97 and later.

For the JD Edwards domain, only the combination of Server Manager 8.98.4 and Tools Release 8.98.4 is fully certified to support the JDE AppPack. Although not certified, it is expected that the JDE AppPack (running Server Manager and Tools Release 8.98.4) will also be functional with downstream targets running JD Edwards EnterpriseOne Tools Release 8.97. However, due to changes in configuration settings and some internal structures between releases, there may be some functionality that is not common or supported across targets running JD Edwards Tools Releases 8.97 and 8.98.

Tip:
Server Manager must be used for the daily administration of the JD Edwards EnterpriseOne servers. This is especially true in the area of runtime and configuration settings because Server Manager natively presents these settings in a different (user-friendly) manner than what can be displayed by the JDE AppPack. That is, although the native settings are translated into user-friendly settings by Server Manager, they are passed to EMCC untranslated. You can use the Server Manager Guide Appendix B: Reference - Server Configuration Settings to determine the correlation between a literal configuration setting and that displayed by the Server Manager user interface.

1.8 Features at a Glance

The JDE AppPack:

- Discovers and registers JD Edwards EnterpriseOne targets.

- Monitors metrics for JD Edwards EnterpriseOne targets.

- Displays configuration data in a graphical user interface that is driven by metadata.

- Creates a JD Edwards EnterpriseOne system in EMCC that enables you to see how all the targets in the system are related to the JD Edwards EnterpriseOne application database.

- Allows the user to create a graphical topology that displays the relationships between targets and allows you to execute selected actions on targets from this view.

- Allows the user to create a service that simulates a transaction, such as login and logout, to monitor the availability of an application. Using the EMCC Service Level Monitoring feature, you can also check the availability of a system or a feature of an application.

- Additional EMCC functions can be added or referenced. Refer to the EMCC Advanced Configuration Guide at this link:http://download.oracle.com/docs/cd/B16240_01/doc/em.102/e10954/toc.htm

1.9 Features of Server Manager That Are Not Supported by EMCC

Below is a listing of a subset of Server Manager functionality that is beyond the scope of standard functionality supported by Enterprise Manager Cloud Control (EMCC). That is, while this information is captured and displayed within Server Manager, there might be an equivalent capture and display from within EMCC depending on the targets types available to your grid installation.

1.9.1 jdelog.properties Logging

The display of logging for jdelog.properties is not supported in EMCC for any JD Edwards EnterpriseOne server.

1.9.2 Java Environment

The display of Java Environment properties is not supported in EMCC for these JD Edwards EnterpriseOne servers:

- HTML Server

- DAS Server

Note:
Although not available in the base installations of EMCC, this feature could be exposed depending on what Management Packs or Plug-ins are installed in EMCC. For example, the Diagnostics Pack for Oracle Middleware and the Diagnostic Pack for Oracle Database. Also various Host Server Packs and Plug-ins are available depending on host type.

1.9.3 Kernel Ranges

The display of Kernel Ranges is not supported in EMCC for this JD Edwards EnterpriseOne server:

- Enterprise Server

1.9.4 Disk Space Usage

The display of Disk Space Usage is not supported in EMCC for this JD Edwards EnterpriseOne server:

- Enterprise Server

Note:
Although not available in the base installations of EMCC, this feature could be exposed depending on what Management Packs or Plug-ins are installed in EMCC. For example, the Diagnostics Pack for Oracle Middleware and the Diagnostic Pack for Oracle Database. Also various Host Server Packs and Plug-ins are available depending on host type.

1.10 Limitations

1.10.1 EMCC Web App Services

In order to provide complete functionality, EMCC assumes an EMCC agent is installed on each target. The function of the agent enables a wide range of EMCC-defined services and functionality to run within the EMCC framework. However, for the JDE AppPack, since the EMCC agent is not required to be installed on each JD Edwards EnterpriseOne target, only a subset of EMCC Services is supported. That subset is confined to the Web App Services of EMCC.

1.10.2 Microsoft Windows Collection

The initial release of the JDE AppPack was developed and certified on the Linux platform. While the design goal is for complete compatibility on Microsoft Windows systems, it is possible that some metric collection issues may be encountered when EMCC and the JDE AppPack are run on Microsoft Windows systems.

1.11 Network Performance Considerations

If your network uses DHCP servers to manage network IP addresses, and your EMCC and Server Manager machines are not on the same local subnet, for performance reasons you may want to consider adding explicit IP addresses into the IP address mapping is available in the DNS database, the Hosts or Lmhosts file, or the WINS database. You may need to reboot any machine on which you modify an IP address file.

1.12 Glossary of Terms

This section describes common terms used in this guide.

1.12.1 Administrator Account

Administrator accounts provide users permission to perform administrative tasks and access administrative information. You can set up each administrator account to have its own roles, privileges, and notification rules. There are two types of administrator accounts: Super Administrator and Administrator.

1.12.2 Alerts

Indicates a potential problem; either a warning or critical threshold for a monitored metric has been crossed. An alert can also be generated for various target availability states. EMCC provides various options to respond to alerts. Administrators can be automatically notified when an alert triggers and can set up corrective actions to resolve an alert condition automatically.

1.12.3 Beacon

A special target installed on an agent that runs a defined service test and reports the results to the Oracle Management Service to determine the status and performance of a service.

1.12.4 Corrective Actions

Corrective actions allow you to specify automated responses to alerts and policy violations.

1.12.5 Dashboard

Presents information using intuitive icons and graphics that let you spot recent changes and quickly identify and respond to problems.

1.12.6 Discovery Process

The discovery process identifies and registers targets in EMCC so that they can be monitored and managed from the EMCC console. Targets are discovered one host at a time.

1.12.7 Enterprise Manager Cloud Control 12c (EMCC)

The Oracle EMCC 12c is a web-based user interface for centrally managing your entire computing environment. From the EMCC, you can monitor and administer your entire computing environment from one location on the network. All the services within your enterprise, including hosts, databases, listeners, application servers, HTTP Servers, and Web applications, are easily managed as one cohesive unit.

1.12.8 EMCC Agent

The EMCC Agent is responsible for monitoring all targets on the host, for communicating that information to the middle-tier Management Service, and for managing and maintaining the host and its targets.

1.12.9 JD Edwards EnterpriseOne System

A group of targets that are associated with one JD Edwards EnterpriseOne domain.

1.12.10 JD Edwards EnterpriseOne Global Unique Identifier (GUID)

A unique identifier that ties each target together and defines it as a system. The GUID is generated and resides at the database layer. During the discovery process, the application server connects to the JD Edwards EnterpriseOne application database and retrieves the GUID.

1.12.11 Managed Targets

EMCC Agents monitor and perform administrative functions on managed targets in your enterprise. Targets include but are not limited to Databases, Application Servers, Listeners, and Third-party Applications.

1.12.12 Management Repository

This is an Oracle database that contains all the available information about administrators, targets, and applications managed within EMCC. Captured data is uploaded to the repository through the Oracle Management Service. The Repository organizes the data and makes it available for data retrieval-allowing the data to be shared between any administrators accessing the EMCC console.

1.12.13 Oracle Management Agent (OMA)

A process deployed as binaries on each of the monitored hosts. It is responsible for monitoring all targets in the host, communicating the information to the middle-tier management service, and managing and maintaining the host and its targets.

The Oracle Management Agent on a host collects host configuration information for the host and database configuration information for the Oracle Databases on the host and client configuration information and communicates that information over HTTPS to the Oracle Management Service, which stores it in the Oracle Management Repository.

1.12.14 Oracle Management Service (OMS)

A web application (J2EE-compliant) that renders the user interface for the Oracle EMCC console. It works with all JDE AppPack Agents to process monitoring and job information, and uses the Management Repository as its data store. The Oracle Management Service resides in the layer above an Oracle Application Server (OAS). Therefore, when the Oracle Management Service is installed, it also installs the application server.

1.12.15 Policies

Define the desired behavior or characteristics of systems. By using preconfigured or custom policies, automated assessments of systems and applications are performed. Through alerts, you are notified of any deviations, such as inappropriate settings or incorrect system configurations.

1.12.16 Preferred Credentials

Simplify access to managed targets by storing target login credentials in the Management Repository. With preferred credentials set, users can access a target that recognizes those credentials without being prompted to log in to the target's host machine. Preferred credentials are set on a per user per target basis, thus ensuring the security of the environment.

1.12.17 Roles

Enable you to group EMCC system and target privileges, and grant these to administrators or to other roles. Privileges give the administrator rights to perform management actions within EMCC. Creating roles is an easy way to grant a predefined set of privileges to a group of administrators. If you change a role, the changes are automatically propagated to all administrators who are assigned that role.

1.12.18 Service

An entity that models a business process or application. Examples of services are CRM applications, online banking, and email services. You can define services by creating one or more service tests that simulate common end-user functions. Using these service tests, you can measure the performance and availability of critical business functions, receive alerts when there is a problem, identify common issues, and diagnose causes of failures.

1.12.19 System

A set of targets (hosts, databases, application servers, and so on) that function together to host one or more applications or services.

1.12.20 Super Administrator Account

Can manage all other administrator accounts and set up all administrator credentials. In addition, the super administrator can:

- Create privileges and roles

- Perform the initial setup of EMCC

- Add targets to EMCC

- Perform actions on targets in the system

Note:
EMCC is installed with a default super administrator account named SYSMAN. You use the SYSMAN account for the initial login to EMCC. Then, create new super administrator accounts as needed in your system.

1.12.21 Topology Viewer

Enables you to view the relationships between targets within the context of a system. You can perform some management actions from this view.

1.13 Deployment Architecture

This architectural diagram shows a conceptual view of the deployment architecture for the various operational components required to integrate existing JD Edwards EnterpriseOne functionality of Server Manager with EMCC:

Figure 1-1 Deployment Architecture Example

2 Install the Database for Enterprise Manager

This chapter shows an example of a new installation of Enterprise Manager. For existing installations, refer to the Caution below. After you have reviewed the Caution, existing installations of Enterprise Manager can proceed to Chapter 5, "Import the JD Edwards Application Pack OPAR".

An Oracle database must be installed that is configured expressly for use by Enterprise Manager (see Caution below). For reference purposes, this chapter shows an example of installing the Oracle database for use by Enterprise Manager. However, Oracle strongly recommends that you use the OEM Oracle database installation software instructions under the direction of an Oracle DBA.

Caution:
Both new and existing installation of the Oracle database must perform the procedures in the section of this chapter entitled: Section 2.2, "Post Installation Required Database Configuration".

This chapter contains the following topics:

- Section 2.1, "Running the Oracle Database Installer"

- Section 2.2, "Post Installation Required Database Configuration"

2.1 Running the Oracle Database Installer

Note:
This procedure assumes you have obtained the software component for the Oracle database as described in the chapter of this guide entitled: Section 1.5, "Obtaining Oracle Software Components from the Oracle Software Delivery Cloud".

On the machine where you have downloaded the Oracle 11g database installer:

1. Change directory to directory where you downloaded the installer. For example:
cd /u01/downloads/db11gr2/database

2. Launch the installer using this command:
./runInstaller

3. On Configure Security Updates, in order to be informed of security issues you must either provide an email address or choose to receive security updates via My Oracle Support. If you have an Oracle Support account, it will be easier if click the checkbox to choose to receive security updates via My Oracle Support.

4. Click the Next button.

5. On Select Installation Option, click this radio button:
Create and configure a database

6. Click the Next button.

7. On System Class, click this radio button to install on a server class system.
Server Class

This option allows for more advanced configuration options.

8. Click the Next button.

9. On Node Selection, choose this radio button:
Single instance database installation

10. Click the Next button.

11. On Select Install Type, click this radio button:
Typical Install

12. Click the Next button.

13. On Typical Install Configuration, complete these fields:

- Oracle base
Enter your Oracle base location. For example:

/u01/app/oracle

- Software location
Enter or browse to the location of your Oracle base folder. This location must exist and be empty. For example:

/u01/app/oracle/oradata

- Global database name
Enter the global database name. For example:

emrep

- Administrative Password
Enter the administrative password for the global database.

- Confirm Password
Reenter the administrative password for the global database.

14. Click the Next button.

15. On Create Inventory, if this is your first installation on this host, you are prompted to enter an Inventory Directory. The installer automatically sets up subdirectories for each product to contain inventory data. The subdirectory for each product typically requires 150 KB of disk space. Optionally you can also choose between the available values in the oraInventory Group Name pulldown. For example, your inventory directory might be:
/u01/app/oraInventory

Note:
This directory must exist and be empty.

16. Click the Next button.

The installer begins the prerequisite check and displays the progress as it verifies that the target environment meets the minimum installation and configuration requirements for products you have selected.

When the requisites check completes, the Summary screen is displayed.

17. On Summary, review the contents. Optionally you can click the Save Response File... button to save the contents of the Summary screen.

18. Click the Finish button to begin the actual installation.

The installer displays a progress bar of In Progress and Pending tasks.

After the point in the installation when the database is successfully created, the installer displays an Xterm window for the Database Configuration Assistant.

Note:
All database accounts except SYS, SYSTEM, DBSNMP, and SYSMAN are locked. Optionally you can click the Password Management... button to view a complete list of locked accounts or manage the database accounts (except DBSNMP and SYSMAN). From the Password Management window, unlock only the accounts you will use. Oracle Corporation strongly recommends changing the default passwords immediately after unlocking the account.

19. If you clicked the Password Management... button this Xterm window for Password Management is displayed:

20. On Password Management, you can Lock or unlock database user accounts and/or change the default passwords.
If you choose to change accounts settings or passwords, click the OK button. Otherwise, click Cancel to return to the Database Configuration Assistant Xterm window.

21. On Database Configuration Assistant, click the OK button to resume the remaining installer tasks.

22. On the Xterm window for Execute Configuration scripts, you must execute the configuration scripts as the "root" user. To execute the configuration scripts:

- Open a terminal window.

- Log in as "root".

- Run the scripts and verify that they ran successfuly.

- Return to this window.

23. On Execute Configuration Scripts, after you have executed the scripts as described in the preceding step, click the OK button to continue.

24. On Finish, verify the installation of the Oracle Database was successful and click the Close button.

2.2 Post Installation Required Database Configuration

After you install a new Oracle database for exclusive use by EMCC 12c, the EMCC documentation recommends you configure your database using this procedure.

1. Drop the management repository using this line command:
emca -deconfig dbcontrol db -repos drop

A sample of the resulting console session is shown below.

[oracle@denlx01 bin]$ ./emca -deconfig dbcontrol db -repos drop

STARTED EMCA at Aug 10, 2011 11:44:38 AM
EM Configuration Assistant, Version 11.2.0.0.2 Production
Copyright (c) 2003, 2005, Oracle.  All rights reserved.

Enter the following information:
Database SID: emrep
Listener port number: 1521
Password for SYS user:
Password for SYSMAN user:

Do you wish to continue? [yes(Y)/no(N)]: Y
Aug 10, 2011 11:44:55 AM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /home/oracle/cfgtoollogs/emca/emrep/emca_2011_08_10_11_44_37.log.
Aug 10, 2011 11:44:55 AM oracle.sysman.emcp.util.DBControlUtil stopOMS
INFO: Stopping Database Control (this may take a while) ...
Aug 10, 2011 11:45:19 AM oracle.sysman.emcp.EMReposConfig invoke
INFO: Dropping the EM repository (this may take a while) ...
Aug 10, 2011 11:47:10 AM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully dropped
Enterprise Manager configuration completed successfully
FINISHED EMCA at Aug 10, 2011 11:47:14 AM
You have new mail in /var/spool/mail/oracle
[oracle@denlx01 bin]$

2. Per requirements for EMCC, you must change the Oracle database init parameters.
Connected to the Oracle database as sysdba, use this command sequence:

alter system set session_cached_cursors=200 scope=spfile;
alter system set remote_login_passwordfile=SHARED scope=spfile;
alter system set aq_tm_processes=1 scope=spfile;
alter system set processes=500 scope=spfile;
alter system set log_buffer=10485760 scope=spfile;
shutdown immediate
startup

3 Install Enterprise Manager Cloud Control (EMCC)

This chapter shows an example of a new installation of Enterprise Manager Cloud Control (EMCC). If you are using an existing EMCC installation, you can proceed to Chapter 5, "Import the JD Edwards Application Pack OPAR".

An Oracle database must be installed expressly for use by EMCC prior to installing EMCC. For reference purposes, this chapter shows an example of installing the Oracle database for use by Enterprise Manager. However, Oracle strongly recommends that you use the OEM Oracle database installation software instructions under the direction of an Oracle DBA.

Note:
This procedure assumes you have obtained the software component for the Oracle EMCC as described in the chapter of this guide entitled: Section 1.5, "Obtaining Oracle Software Components from the Oracle Software Delivery Cloud".

On the machine where you have downloaded the Oracle Enterprise Manager 12c Cloud Control installer:

1. Change directory to directory where you downloaded the installer. For example:
cd u01/downloads/emgc12c/numeric_date/Disk1

where numeric_date is the date of the installer; for example: 110728.

2. Launch the installer using this command:
./runInstaller

3. On My Oracle Support Details, in order to be informed of security issues you must either provide an email address or choose to receive security updates via My Oracle Support. If you have an Oracle Support account, it will be easier if click the checkbox to choose to receive security updates via My Oracle Support.

4. Click the Next button.

5. On Software Updates:

1. Press the Skip radio button to skip the search for Updates (Prerequisites, Critical Patches, Interim Patches, etc.).

2. Press the Search for Updates (Prerequisites, Critical Patches, Interim Patches, etc.) button to choose to search in a local directory if you have previously downloaded patches, or if you have an Oracle support account and Internet access, you can choose to search My Oracle Support.

6. Click the Next button.

7. On Prerequisite Checks, verify the last line of the displayed log reads:
Check complete: The overall result of this check is: Passed

Also review the list of Prerequisite Names and their Status, where values can be Succeeded, Warning, or Failed. A status of Warning does not necessarily indicate an overal failure status. If you fix a Warnings or Failure, you can further choose the Rerun or Ignore buttons.

If you had a failed check of prerequisites, you will receive this error message.

On Warning, you can click Yes to proceed with the installation. If you click No, you can fix the error and then click Rerun to verify the fix.

8. Click the Next button.

9. On Install Types, click this radio button:
Create a new Enterprise Manager System

Under the above radio button, click this radio button:

Advanced

10. In the field Middleware Home Location, either browse or enter a location into which the WebLogic Server will be installed. This location must exist and be empty. For example:
/u01/app/emgc12

11. Click the Next button.

12. On WebLogic Server Configuration Details, complete these fields:

- WebLogic User Name
Enter a name for your WebLogic Server. For example:

weblogic

Enter and confirm a password for the WebLogic User.

- Node Manager User Name
This value is populated by default from the existing Node Manager installation. You must enter and confirm a password.

- OMS Base Installation
By default this value is populated with the Middleware Home Location path you entered on the previous screen. You should append the path with a directory name for the OMS Base Installation. For example, where gc_inst is the appended value:

/u01/app/emgc12/gc_inst

13. Click the Next button.

14. On Database Connection Details, complete these fields:

Note:
These values can be derived from the tnsnames.ora file for the Oracle database for the Management Repository.

- Database Host Name
Enter the name of the machine on which your Oracle database for the Management Repository. For example:

denlx01

- Port
Enter the port on which the Oracle database for the Management Repository is listening. For example:

1521

- Service/SID
Enter the Service/SID for the Oracle database for the Management Repository. For example:

emrep

- SYS Password
Enter the SYS user password for the Oracle database for the Management Repository.

15. Click the Next button.

16. You may receive the above Error dialog indicating that a prerequisite check failed because the Oracle database, where the Management Repository will be configured, does not meet the configuration requirements.
To let the installer fix the issue automatically, click the Yes button. To fix the issue yourself, click the No button.

17. You may receive the above Warning dialog indicating that prequisite checks failed because receive the above Error dialog indicating that a prerequisite check failed because the Oracle database, where the Management Repository will be configured, does not meet the configuration requirements.
These failures do not impact the installation, but you may encounter performance issues with the product later.

You can either fix the issue manually right away based on the recommended offered for this prerequisite, and click the OK button, or you can fix it after the installation ends.

18. On Repository Configuration Details, complete these fields:

- SYSMAN Password
Enter and confirm a password for the EMCC system manager.

- Registration Password
Enter and confirm a password for the EMCC registration.

- Management Tablespace
Enter the path to the Management Tablespace. This can be derived from the tnsnames.ora file for the Oracle database for the Management Repository. For example:

/u01/app/oracle/oradata/emrep/mgmt.dbf

- Configuration Data Tablespace
Enter the path to the Configuration Data Tablespace. This can be derived from the tnsnames.ora file for the Oracle database for the Management Repository. For example:

/u01/app/oracle/oradata/emrep/mgmt_ecm_depot1.dbf

- JVM Diagnostics Data Tablespace
Enter the path to the JVM Diagnostics Data Tablespace. This can be derived from the tnsnames.ora file for the Oracle database for the Management Repository. For example:

/u01/app/oracle/oradata/emrep/mgmt_ad4j.dbf

19. Click the Next button.

20. On Port Configuration Details, review the default port assignments.

Note:
Configuration of the Enterprise Manager system requires the allocation of several ports to facilitate internal communication between system components as well as to provide access to the console via a browser. The table on this screen contains the ports that will be allocated, along with the recommend port ranges, for each component.
By default, the first available port in the specified port range has been chosen.

Alternatively, you can click the Import staticports.ini file button.

21. Click the Next button.

22. On Review, review the information you have provided.

23. Click the Install button to begin the installation process.

The installer displays the Installation Progress Details screen that shows detailed status.

On the Xterm window for Execute Configuration scripts, you must execute the configuration scripts as the "root" user. To execute the configuration scripts:

- Open a terminal window.

- Log in as "root".

- Run the script and verify that it ran successfuly.

- Return to this window.

24. On Execute Configuration Scripts, after you have executed the script as described in the preceding step, click the OK button to continue.

25. On Finish, verify the installation has completed with no errors. Click the Close button to exit the installer.

Note:
The setupinfo.txt file contains information about the setup. This screen indicates the location of the file. For example:
/u01/app/emgc12/oms/install/setupinfo.txt

This screen also displays the URL you can use to access EMCC and the Admin server. Also listed are the details that need to be provided during the subsequent OMS install:

1. Admin Server Hostname
For example:

denlx01

2. Admin Server Port
For example:

7101

The screen also states the encryption key has been generated to encrypt snesitive data in the Management Repository. You can determine this key by issuing this command as the root user:

emctl exportconfg oms -dir <backup location>

4 Set Up the Software Library within EMCC

This section describes the procedure to set up the software library into Oracle Enterprise Manager Cloud Control (EMCC). This step is required before you can import the JD Edwards EnterpriseOne Application Pack, which is described in the next chapter of this guide enittled: Chapter 5, "Import the JD Edwards Application Pack OPAR".

To set up the Software Library within EMCC:

1. From the EMCC Home Page, navigate Grid > Provisioning and Patching > Software Library.

2. On Software Library, navigate Actions > Administration.

3. On Software Library: Administration, click the Add button.

4. On the Add OMS Shared Filesystem Location, complete these fields:

- Name
Provide a name for the Software Library. For example:

swlib1

- Location
Provide a file system location. The location should be accessible from all Oracle Management Server (OMS) instances. For example:

/u01/app/swlib1

5. Click the OK button and wait for the processing to finish. When complete, the new software library is displayed with Status of Activeas shown in the below example.

5 Import the JD Edwards Application Pack OPAR

This section describes the procedure to set up the software library and then import and deploy the JD Edwards Application OPAR into Oracle Enterprise Manager Cloud Control (EMCC) and to the EMCC agent.

Note:
This procedure assumes you have obtained the JD Edwards Application Pack OPAR for Oracle EMCC as described in the chapter of this guide entitled: Section 1.5, "Obtaining Oracle Software Components from the Oracle Software Delivery Cloud".
This procedure also assumes you have already set up the Software Library as described in the preceding chapter of this guide entitled: Chapter 4, "Set Up the Software Library within EMCC".

To import the JD Edwards Application Pack OPAR, use this sequence of line commands:

1. Change to the oms/bin directory of your EMCC installation. For example:

cd /u01/app/emgc12/oms/bin/

2. Enter this command to set up the import of the JD Edwards EnterpriseOne Application Pack into EMCC:

./emcli setup -url=https://denlx01:7799/em -username=sysman -password=Oracle123 -trustall

3. Verify the console display indicates the command was successful as shown in this example:

Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.0.0.
Copyright (c) 1996, 2011 Oracle Corporation and/or its affiliates. All rights reserved.

Emcli setup successful

4. Run this command to perform the import of the JD Edwards EnterpriseOne Application Pack OPAR into EMCC:

./emcli import_update -file=/u01/app/AddOnDevKitWork/jde_plugin/plugin_opar/12.1.0.0.0_oracle.apps.jded_2000_0.opar -omslocal

5. Verify the console display indicates the command was successful as shown in this example:

Processing update: Plug-in - Oracle Jdedwards EnterpriseOne Plugin consists of monitoring and management for Oracle Jdedwards EnterpriseOne system.
Operation completed successfully. Update has been uploaded to Enterprise Manager. Please use the Self Update Home to manage this update.

At this point the import of the JD Edwards EnterpriseOne Application Pack OPAR into EMCC is complete.

6 Deploy the JDE App Pack into the Management Server

This chapter contains the following topics:

- Section 6.1, "Prerequisites to Deploying the JDE AppPack into the Management Server"

- Section 6.2, "Deploy the JDE AppPack into the Management Server"

See Also

Chapter 9, "Undeploy JDE AppPack Components"

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:

- JD Edwards EnterpriseOne Server Manager 8.98.1
Refer to Section 1.7, "Overview Server Manager 8.98.1 for JD Edwards EnterpriseOne" in this guide.

- Oracle Database for EMCC Repository
An Oracle database must be installed for exclusive use by EMCC. Refer to Chapter 2, "Install the Database for Enterprise Manager" in this guide.

- Oracle Enterprise Manager Cloud Control
Refer to Section 1.1.1, "Oracle Enterprise Manager Cloud Control (EMCC)" and Chapter 3, "Install Enterprise Manager Cloud Control (EMCC)" in this guide.

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 EMCC".

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 EMCC. As a prerequisite, you must have an existing EMCC and Oracle database installation. The JDE AppPack must be deployed into each existing EMCC 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).

1. In Oracle EMCC, navigate Setup > Extensibility > Plugins

2. On the list of plugs, locate this item in the Name column:
Oracle JD Edwards EnterpriseOne

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

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

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

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.

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

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

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.

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

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.

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.

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.

7 Deploy the JDE AppPack into the Management Agent

This chapter contains the following topics:

- Section 7.1, "Prerequisites to Deploying the JDE AppPack into the Management Agent"

- Section 7.2, "Deploy the JDE AppPack into the Management Agent"

See Also

Chapter 9, "Undeploy JDE AppPack Components"

7.1 Prerequisites to Deploying the JDE AppPack into the Management Agent

You can deploy the JDE AppPack to the Enterprise Manager Management Agent after you have:

- Imported the JDE AppPack, as described in the preceding chapter of this guide enitlted: Chapter 5, "Import the JD Edwards Application Pack OPAR"

- Deployed the JDE AppPack into the Management Server (OMS) as described in the chapter of this guide entitled: Chapter 6, "Deploy the JDE App Pack into the Management Server"

7.2 Deploy the JDE AppPack into the Management Agent

You should follow the steps in this section to deploy the JDE AppPack into the Management Agent.

1. In Oracle EMCC, navigate Setup > Extensibility > Plugins.

2. With the undeployed plugin highlighted, right click and choose Deploy On > Management Agent...

3. On Deploy Plug-in on Management Agent, General, in the Selected Management Agent section, click the Add button to add the JD Edwards EnterpriseOne target.

4. On Search and Select: Targets - Oracle Enterprise Manager, highlight the target which is automatically found by Enterprise Manager and click the Select button.

5. On Deploy Plug-in on Management Agent, General, verify the JD Edwards EnterpriseOne target machine is added and click the Next button.

On Deploy Plug-in on Management Agent, Review, a warning is displayed indicating that the deployment of the plug-in on a managed host will restart the agent.

6. Click the Deploy button.

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

The EM interface shows the progress of the deployment.

Once the status indicates the agent is being started, the deployment is complete, depending on how long the actual startup takes to complete and that the EMCC session will soon be available.

8 Using EMCC with JD Edwards EnterpriseOne

This chapter contains the following topics:

- Section 8.1, "Additional Information for EMCC"

- Section 8.2, "Using EMCC for the First Time"

- Section 8.3, "Accessing the EMCC Console"

- Section 8.4, "EMCC Home Page"

- Section 8.5, "Targets"

- Section 8.6, "Adding the JD Edwards EnterpriseOne Domain"

- Section 8.7, "JDE EnterpriseOne Domain Home Page"

- Section 8.8, "Members of the JD Edwards EnterpriseOne Domain"

- Section 8.9, "Updating the JD Edwards EnterpriseOne Domain (Refresh Discovery)"

- Section 8.10, "Configuration Topology"

- Section 8.11, "System Monitoring Dashboard"

- Section 8.12, "Monitoring Configuration"

- Section 8.13, "Latest Configuration Data"

- Section 8.14, "Runtime Metrics (Status, User Count, and Performance)"

- Section 8.15, "Configuration Metrics for JD Edwards EnterpriseOne"

- Section 8.16, "Accessing Server Manager from EMCC"

- Section 8.17, "Removing the JD Edwards EnterpriseOne Domain"

- Section 8.18, "Starting and Stopping Components of Enterprise Manager Environments"

8.1 Additional Information for EMCC

For additional information, refer to these EMCC resources:

- Enterprise Manager Documentation
http://download.oracle.com/docs/cd/E11857_01/index.htm

The above Oracle web site includes HTML and PDF versions of these documents:

- Enterprise Manager Concepts

- Administrator's Guide

- Basic Installation Guide

- Advanced Installation and Configuration Guide

- Administrator's Guide for Software and Server Provisioning and Patching

- Oracle Enterprise Manager List of Books

8.2 Using EMCC for the First Time

The EMCC console provides support for creating and managing EMCC administrator accounts. The EMCC administrators you create and manage in the EMCC console are granted privileges and roles to log in to the EMCC console and to manage specific target types and to perform specific management tasks.

During installation, these tasks are performed automatically:

- A default Super Administrator SYSMAN account is created with the password you specified.

- The SYSMAN account is automatically configured to receive email notifications, if you provided the email notification settings at installation time. Email notifications are set up with default Notification Rules for the critical conditions.

After installation, you can immediately log in to the EMCC console with the SYSMAN username and your password to perform management tasks. The next step is to create a new Super Administrator account to monitor and manage the JD Edwards EnterpriseOne targets.

Note:
The SYSMAN account owns the database schema containing the Management Repository and should not be used after the initial log in.

8.3 Accessing the EMCC Console

To access EMCC, use the syntax of one of these URLs to log in to the EMCC console:

https://<Oracle Management Service_hostname>.<domain>:<port>/em

For example:

https://machine_host.company.com:1159/em

8.4 EMCC Home Page

On Select Enterprise Manager Home, you can choose a grid home page from the options shown on this screen. If these options do not match your job profile or role, you can use Setup > My Preferences to make any other page in Enterprise Manager as your home page. For instructions on making the JD Edwards Domain your home page in Enterprise Manager, refer to the Tip in the section in this chapter entitled: Section 8.7, "JDE EnterpriseOne Domain Home Page".

8.5 Targets

To view all existing EMCC targets, select the Targets pulldown control. This control displays rows that further define targets by type, such as groups, systems, services, hosts, databases, middleware (application servers), and composite applications.

8.6 Adding the JD Edwards EnterpriseOne Domain

To add the JD Edwards EnterpriseOne domain to EMCC:

1. On Targets > Systems, use the domain selection pulldown menu to select this domain:
JDE EnterpriseOne Domain

2. On Systems, with the JDE EnterpriseOne Domain selected, click the Add button.

3. On Add JDE EnterpriseOne Domain, complete these fields:

- EnterpriseOne Domain Target Name
Enter the name of the domain for JD Edwards EnterpriseOne. The name of the Server Manager host will be appended to this name if you do not specify it.

For example, your target name might be dev_env.

- Enterprise Manager Agent Host Machine
Enter the machine name on which the Enterprise Manager agent is installed. For example, your machine name might be: denlx01.

Note:
It is recommended that you type the machine name in the field instead of using the search button to locate the machine name.

- Server Manager Host
Enter the fully qualified machine name of your Server Manager host. For example, your machine name might be: denv030.mlab.jdedwards.com.

- Server Manager HTTP Port
Enter the HTTP port that will be used to connect to Server Manager. The default value is 8999.

- Server Manager JMX Port
Enter the JMX port that will be used to connect to Server Manager. The default value is 14501.

- Server Manager Admin User
The default value, which should not be changed, is jde_admin.

- Server Manager Admin Password
Enter a valid value for the password of your Server Manager administrator.

4. Click the OK button to add the domain.

5. As it adds the JD Edwards Domain and associated targets, EMCC performs these functions:

- Discovering: JD Edwards EnterpriseOne Domain

- Creating: JD Edwards EnterpriseOne Domain target

- Saving: JD Edwards EnterpriseOne Domain targets discovered

After the processing is complete the home page for the JD Edwards EnterpriseOne Domain is displayed, as shown below.

8.7 JDE EnterpriseOne Domain Home Page

1. On Targets > Systems , select the row where the Type column is JDE EnterpriseOne Domain.

2. On Systems, with the JDE EnterpriseOne Domain row highlighted, click the Edit button to display the Home page of the JDE EnterpriseOne Domain, as shown below.

Tip:
If your server is not listed, it may be because the Enterprise Manager default for the maximum number of servers to be shown in this list is 10. Refer to the Enterprise Manager documentation to customize this value.

3. Another way to navigate to the JD Edwards EnterpriseOne Domain Home page is on Systems, on the row with the JDE EnterpriseOne Domain, click the hyperlink in the Name column where the Type column is JDE EnterpriseOne Domain. This is shown in the example below.

4. Optionally you can set the JD Edwards Domain as your EMCC home page, with the JD Edwards Domain page as the current page in your EMCC session, navigate Setup > My Preferences > Set Current Page as My Home (see below figure).

8.8 Members of the JD Edwards EnterpriseOne Domain

To display members of the JD Edwards EnterpriseOne Domain:

1. With the JD Edwards EnterpriseOne Domain displayed, in the upper left hand portion of the EMCC display, choose the Custom Menu pulldown, and then Members and Show All.

2. EMCC displays a list of members as shown in the following example:

8.9 Updating the JD Edwards EnterpriseOne Domain (Refresh Discovery)

To update the JD Edwards EnterpriseOne domain to EMCC, you will use Refresh Discovery as described below.

1. On the JD Edwards EnterpriseOne Domain Home Page, navigate Custom Menu > Refresh Discovery.

2. EMCC displays this warning page:

3. On the Warning screen for refreshing the JD Edwards Enterprise Domain, verify the target and click the Yes button to complete the refresh action.

The EMCC system processes the refreshing of the JD Edwards EnterpriseOne Domain and associated targets. When the process is complete, you are returned to the JD Edwards EnterpriseOne Domain Home Page.

8.10 Configuration Topology

There are several methods to display the configuration topology of the JD Edwards EnterpriseOne Domain.

1. On the JD EnterpriseOne Domain home page, in the upper left hand portion of the EMCC display, choose either of these navigations:
Custom Menu > Members > Topology

Custom Menu > Configuration > Topology

2. EMCC displays a topology graphic as shown in the following example:

8.11 System Monitoring Dashboard

Use the System Dashboard to view the health of managed targets within a group or system in real time. The System Dashboard presents information using intuitive icons and graphics that let you spot recent changes and quickly identify and respond to problems. You can:

- Customize the display attributes to match information requirements of managed targets.

- Monitor status for recent problems.

To access the System Monitoring Dashboard, navigate Custom Menu > Members > Dashboard. Below is an example of the dashboard for the JD Edwards EnteprriseOne Domain.

8.12 Monitoring Configuration

EMCC automatically sets up the monitoring configuration for the JDE EnterpriseOne targets.

1. To confirm, with a JDE target selected (for example, the HTML Server), navigate Custom Menu > Target Setup > Monitoring Configuration.

In the Monitoring section of the screen that indicates that monitoring is automatically enabled for this target's availability and performance, so no further monitoring configuration is necessary. You can edit the metric thresholds from the target's home page.

8.13 Latest Configuration Data

Use this procedure to obtain the latest configuration data for members of the JD Edwards EnterpriseOne Domain. This allows you to see configuration information that is in such files as the jde.ini and jas.ini. In addition to viewing the configuration information, you can Export or Detach it.

1. With a JD Edwards EnterpriseOne target selected, navigate Target > Configuration > Last Collected.

2. EMCC displays the latest configuration for the selected Target.
Below is an example of the latest configuration for the JD Edwards EnterpriseOne HTML Server.

Below is an example of the latest configuration for the JD Edwards EnterpriseOne Enterprise Server.

3. To display additional configuration details, expand the node for the Target and click the subnode.
Below is an example of a JD Edwards EnterpriseOne HTML Server with the JDE EnterpriseOne Configuration subnode expanded.

8.14 Runtime Metrics (Status, User Count, and Performance)

You can use EMCC to monitor the status of all members of the JD Edwards domain. EMCC can also monitor the performance of these JD Edwards EnterpriseOne servers:

- Enterprise Server

- HTML Web Server

1. On Members for JDE EnterpriseOne Domain, for each member you can view:

- Status

- Alerts

- Policy Violations

2. For member Types EnterpriseOne Enterprise Server and EnterpriseOne HTML Server, you can view this type of performance data:

- Home tab
User Count

- Performance tab
Call Object Kernel Average Execute Time

- Java Heap

- Call Object Kernel Timeout Errors

Following are examples for each JD Edwards EnterpriseOne Server Type (Enterprise Server and HTML Server, respectively).

8.15 Configuration Metrics for JD Edwards EnterpriseOne

You can view all configuration metrics for these JDE EnterpriseOne member Types:

- Section 8.15.1, "All Metrics for JD Edwards EnterpriseOne Enterprise Server"

- Section 8.15.2, "All Metrics for JD Edwards EnterpriseOne HTML Server"

8.15.1 All Metrics for JD Edwards EnterpriseOne Enterprise Server

Use this procedure to view all metrics for the JD Edwards EnterpriseOne Enterprise Server

1. On Members for JDE EnterpriseOne Domain (or also from the Dashboard for the JDE EnterpriseOne Domain), click the link for the Name for the EnterpriseOne Enterprise Server.

2. With the JDE EntepriseOne target displayed in EMCC, navigate Target > Monitoring > All Metrics.

3. On All Metrics, you can view any of the metrics that are available for the JD Edwards EnterpriseOne Enterprise Server. These metrics include:

- Average CPU % Used by All Kernels

- Enterprise Server Process Manager

- Kernel Process

- Kernel Thread

- Network Process

- Response

- Total JDB Table Cache Count

- Total JDE Cache

- Total Number of DB Connections

- Total Number of Incoming Network Connections

- Total Number of Outstanding Requests

- Total Number of Users

- Other collected items

4. You can expand a metric node to view subnodes. The following screen is a sample of the metrics when you click on the Average Execution Time node.

5. You can also click on subnodes to display additional information. The following screen is a sample of the metrics shown when you click on the CallObj Avg Time subnode of the Average Execution Time node.

8.15.2 All Metrics for JD Edwards EnterpriseOne HTML Server

Use this procedure to view all metrics for the JD Edwards EnterpriseOne HTML Server

1. On Members for JDE EnterpriseOne Domain, click the link for the Name for the EnterpriseOne HTML Server.

2. With the JDE EntepriseOne target displayed in EMCC, navigate Target > Monitoring > All Metrics.

3. On All Metrics, you can view any of the metrics that are available for the JD Edwards EnterpriseOne Enterprise Server. These metrics include:

- Average Execution Time

- Cache Group

- Call Object (BSFN) Stats

- Current number of open applications (All Users)

- Database Datasource

- General System Info and Uptime

- JDB Service Cache

- JDBj Cache Prepared Statement

- JDBj Connection Manager

- JDBj Pooled Connection

- JDENET Connection Manager

- JDENET Connection Pool Socket

- Java Heap Memory Used

- OWVirtual Detail

- Response

- Total Number of System Errors

- Total Number of Timeout Errors

- Total number of current users

- User Sessions

- Other collected items

- You can expand a metric node to view subnodes. The following screen is a sample of the metrics when you click on the Call Object (BSFN) Stats node.

- You can also click on subnodes to display additional information. The following screen is a sample of the metrics shown when you click on the Application Errors subnode of the Call Object (BSFN) Stats node.

8.16 Accessing Server Manager from EMCC

You can directly access the JD Edwards EnterpriseOne Server Manager used in this installation of Enterprise Manager. On the JD Edwards EnterpriseOne Domain Home Page, navigate Custom Menu > Server Manager.

You will be redirected to the Server Manager login page with this URL syntax:

http://SM_Host:SM Port/manage/home

where SM_Host and SM_Port are retrieved from the monitoring configuration. For example, the URL might be:

http://globalwin2.mlab.jdedwards.com:8999/manage/home

The Server Manager target machine is derived from the values in these fields on Monitoring Configuration:

- Server Manager Hostname

- Server Manager HTTP Port

For example:

Below is the Server Manager login page that is displayed when you are redirected.

After you enter valid credentials for this Server Manager, the Server Manager Home page is displayed as shown in the following example:

8.17 Removing the JD Edwards EnterpriseOne Domain

1. On Targets > Systems, with the JDE EnterpriseOne Domain selected, click the Remove button.

2. EMCC displays a Warning and lists the Domain target and associated EnterpriseOne targets that will be deleted.

3. As shown in the screen sample below, click the Yes button to confirm the deletion.

After you click the Yes button, EMCC displays the below progress screen indicating the deletion of the JD Edwards EnterpriseOne targets.

After the processing is complete for deleting the system domain target, EMCC returns to the All Targets page as shown in example below.

8.18 Starting and Stopping Components of Enterprise Manager Environments

This section discusses:

- Section 8.18.1, "Starting Enterprise Manager Environment Components"

- Section 8.18.2, "Stopping Enterprise Manager Environment Components"

8.18.1 Starting Enterprise Manager Environment Components

Use these commands to start Enterprise Manager environment components:

- Start database

sqlplus '/as sysdba'
sql> startup

- Start Database Listener

/u01/app/oracle/home/bin/lsnrctl start

- Start WebLogic Node Manager

Stop ADMIN SERVER from console in case it is running without Node Manager
/u01/app/emgc12/wlserver_10.3/server/bin/setWLSEnv.sh
/u01/app/emgc12/wlserver_10.3/server/bin/startNodeManager.sh

- Start OMS

/u01/app/emgc12/oms/bin/emctl start oms

- Start Agent

/u01/app/emgc12/agent/agent_inst/bin/emctl start agent

8.18.2 Stopping Enterprise Manager Environment Components

Use these commands to stop Enterprise Manager environment components:

- Stop Agent

/u01/app/emgc12/agent/agent_inst/bin/emctl stop agent

- Stop OMS (this stops the OMS Server)

/u01/app/emgc12/oms/bin/emctl stop oms

- Stop Database Listener

/u01/app/oracle/home/bin/lsnrctl stop

- Stop Database

sqlplus '/as sysdba'
sql> shutdown immediate

9 Undeploy JDE AppPack Components

The proper sequence for undeploying JD Edwards AppPack Components is to undeploy from the Management Agent first, and then undeploy from Management Servers.

This chapter contains the following topics:

- Section 9.1, "Undeploy the JD Edwards AppPack from the Management Agent"

- Section 9.2, "Undeploy the JD Edwards AppPack from Management Servers"

9.1 Undeploy the JD Edwards AppPack from the Management Agent

Use this procedure to undeploy the JD Edwards AppPack from the Management Agent.

Caution:
You should do this step prior to undeploying the JD Edwards AppPack from Management Servers, which is described in the next section of this guide entitled: Section 9.2, "Undeploy the JD Edwards AppPack from Management Servers".

1. In Oracle EMCC, navigate Setup > Extensibility > Plugins

2. With the undeployed plugin highlighted, right click and choose Undeploy From > Management Agent...

3. On Undeploy Plug-in on Management Agent, General, click the Continue button to undeploy the auto-detected Management Agent.

4. On Undeploy Plug-in on Management Agent, Review, the panel warns that deployment of the plug-in on the Management Server will restart the agent.

5. Click the Undeploy button.

6. On Undeploy Plug-in on Management Agent, Confirmation, click the Show Status button. This Confirmation screen indicates that the undeployment is started on selected agents.

7. The undeployment is complete when the status shows a green check mark this Deployment Ste:p
Deconfiguring Plugin from Agent

9.2 Undeploy the JD Edwards AppPack from Management Servers

Use this procedure to undeploy the JD Edwards AppPack from Management Servers.

Caution:
Prior to undeployment the JD Edwards AppPack from Management Servers, you should undeploy it from the Management Agent. Refer to the previous section of this guide entitled: Section 9.1, "Undeploy the JD Edwards AppPack from the Management Agent".

1. In Oracle EMCC, navigate Setup > Extensibility > Plugins

2. With the undeployed plugin highlighted, right click and choose Undeploy From > Management Servers...

3. On Undeploy Plug-in from Server, General, enter the password for the SYS user of the EM repository.

4. Click the Continue button.

5. On Undeploy Plug-in from Server, 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.
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?

6. Click the Undeploy button.

7. On Undeploy Plug-in from Server, Confirmation, verify the undeployment is in progress and click the OK button.

8. On Plug-ins, the Recent Deployment Activities indicates that the undeployment of the Management Service has begun.
However, since OMS is shut down during the undeployment 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.

When the message appears indicating that OMS is being started it means that undeployment is complete and that the EM console should be available very soon, depending on how long the actual startup takes to complete.

10 Deinstall the Oracle Database and EMCC

If you only want to remove the JD Edwards EnterpriseOne Domain, refer to the chapter of this guide entitled: Section 8.17, "Removing the JD Edwards EnterpriseOne Domain".

To undeploy the JD Edwards EnterpriseOne Application Pack components, refer to the chapter of this guide enitlted: Chapter 9, "Undeploy JDE AppPack Components".

This chapter discusses these topics:

- Section 10.1, "Stop the Agent, OMS, and Database Using Line Commands"

- Section 10.2, "Deinstall the Oracle Database and EMCC Using OUI"

10.1 Stop the Agent, OMS, and Database Using Line Commands

You should these commands, in this sequence, to stop the Enterprise Manager Agent, the OMS, and the Oracle database using by Enterprise Manager prior to deinstalling any product.

1. On the machine where the database that is being used by Enterprise Manager is running, stop the database using these commands:
sqlplus '/as sysdba'

shutdown immediate

2. On the machine where the database that is being used by Enterprise Manager is installed, stop the database listener using the lsnrctl stop command. This command is run from the /oracle/home/bin directory. For example, your /oracle/home/bin directory and command line might be:
/u01/app/oracle/home/bin/lsnrctl stop

3. Stop OMS using the stop oms command, which stops both the Admin Server and the OMS Server. This command is run from the oms/bin directory. For example, your oms/bin directory and command line might be:
/u01/app/emgc12/oms/bin/emctl stop oms

4. Stop the EMCC agent using the stop Agent command. This command is run from the bin directory of the agent installation directory. For example, your /bin directory and command line might be:
/u01/app/emgc12/agent/agent_inst/bin/emctl stop agent

5. Verify there no additional Oracle processes are running using this command:
ps –r | grep oracle

Note:
A likely example of an Oracle process that might be running is for the WebLogic Server Node Manager.

6. Kill any Oracle-based java process which are listed as results from the above command.

10.2 Deinstall the Oracle Database and EMCC Using OUI

You use the Oracle Universal Installer (OUI) to deinstall the Oracle EMCC. This section provides an example deinstall based on the install examples described in the chapters of this guide entitled:

- Chapter 2, "Install the Database for Enterprise Manager"

- Chapter 3, "Install Enterprise Manager Cloud Control (EMCC)"

To deinstall the Oracle database and EMCC using OUI:

1. Change to the oui/bin directory and run the OUI runInstaller.sh script. For example, your oui/bin and command line might be:
/u01/app/oracle/home/oui/bin/runInstaller.sh

2. On Oracle Universal Installer: Welcome, click the Deinstall Products ... button.

3. On Inventory, check every checkbox except the checkbox for the Oracle Database Home. For example, do not select this checkbox:
OraDB11g_home1

4. Click the Remove button.

5. On Confirmation, click the Yes button to deinstall all Oracle components except the database home, which cannot be deinstalled until all other components are first deinstalled.

The Remove dialog shows the progress of the deinstallation actions.

6. On Inventory, verify the only remaining Oracle products is the Oracle database home. For example:
OraDB11g_home1

7. On Inventory, select the checkbox for the Oracle database home and click the Remove button.

8. A Warning displays this text:
Please run the command '/u01/app/oracle/home/deinstall/deinstall' to deinstall this Oracle home.

9. As instructed in the Warning, open a UNIX console window and issue these commands to change to the /oracle/home/deinstall directory and run the deinstall.sh script:

10. The deinstall.sh script launches the Oracle Deinstall and Deconfiguration Tool and displays the following console, where the bolded sections are user prompts. This console listing shows users responses that are applicable for this example. If no reponse is shown in the console session, then the default action is assumed as triggered by the user input pressing of the Enter key. You should refer to the Oracle OEM documentation and provide user responsibles applicable to your installation.

[oracle@denlx01 deinstall]$ cd /u01/app/oracle/home/deinstall
[oracle@denlx01 deinstall]$ ./deinstall
Checking for required files and bootstrapping ...
Please wait ...
Location of logs /tmp/deinstall2011-08-09_06-54-51-PM/logs/

############ ORACLE DEINSTALL & DECONFIG TOOL START ############

######################## CHECK OPERATION START ########################
Install check configuration START

Checking for existence of the Oracle home location /u01/app/oracle/home
Oracle Home type selected for de-install is: SIDB
Oracle Base selected for de-install is: /u01/app/oracle
Checking for existence of central inventory location /u01/app/oraInventory

Install check configuration END

Network Configuration check config START

Network de-configuration trace file location: /tmp/deinstall2011-08-09_06-54-51-PM/logs/netdc_check6212736737944149450.log

Specify all Single Instance listeners that are to be de-configured [LISTENER]:

Network Configuration check config END

Database Check Configuration START

Database de-configuration trace file location: /tmp/deinstall2011-08-09_06-54-51-PM/logs/databasedc_check5639182693098634058.log

Use comma as separator when specifying list of values as input

Specify the list of database names that are configured in this Oracle home [emrep]:

###### For Database 'emrep' ######

Single Instance Database
The diagnostic destination location of the database: /u01/app/oracle/diag/rdbms/emrep
Storage type used by the Database: FS
Database file location: /u01/app/oracle/oradata/emrep,/u01/app/oracle/flash_recovery_area/emrep
Flash recovery area location: /u01/app/oracle/flash_recovery_area/EMREP
database spfile location: /u01/app/oracle/home/dbs/spfileemrep.ora

The details of database(s) emrep have been discovered automatically. Do you still want to modify the details of emrep database(s)? [n]:

Database Check Configuration END

Enterprise Manager Configuration Assistant START

EMCA de-configuration trace file location: /tmp/deinstall2011-08-09_06-54-51-PM/logs/emcadc_check.log

Checking configuration for database emrep
Enterprise Manager Configuration Assistant END
Oracle Configuration Manager check START
OCM check log file location : /tmp/deinstall2011-08-09_06-54-51-PM/logs//ocm_check1704.log
Oracle Configuration Manager check END

######################### CHECK OPERATION END #########################

####################### CHECK OPERATION SUMMARY #######################
Oracle Home selected for de-install is: /u01/app/oracle/home
Inventory Location where the Oracle home registered is: /u01/app/oraInventory
Following Single Instance listener(s) will be de-configured: LISTENER
The following databases were selected for de-configuration : emrep
Database unique name : emrep
Storage used : FS
No Enterprise Manager configuration to be updated for any database(s)
No Enterprise Manager ASM targets to update
No Enterprise Manager listener targets to migrate
Checking the config status for CCR
Oracle Home exists and CCR is configured
CCR check is finished
Do you want to continue (y - yes, n - no)? [n]: y
A log of this session will be written to: '/tmp/deinstall2011-08-09_06-54-51-PM/logs/deinstall_deconfig2011-08-09_06-55-33-PM.out'
Any error messages from this session will be written to: '/tmp/deinstall2011-08-09_06-54-51-PM/logs/deinstall_deconfig2011-08-09_06-55-33-PM.err'

######################## CLEAN OPERATION START ########################

Enterprise Manager Configuration Assistant START

EMCA de-configuration trace file location: /tmp/deinstall2011-08-09_06-54-51-PM/logs/emcadc_clean.log

Updating Enterprise Manager ASM targets (if any)
Updating Enterprise Manager listener targets (if any)
Enterprise Manager Configuration Assistant END
Database de-configuration trace file location: /tmp/deinstall2011-08-09_06-54-51-PM/logs/databasedc_clean4559434184925448083.log
Database Clean Configuration START emrep
This operation may take few minutes.
Database Clean Configuration END emrep

Network Configuration clean config START

Network de-configuration trace file location: /tmp/deinstall2011-08-09_06-54-51-PM/logs/netdc_clean6305675544518456018.log

De-configuring Single Instance listener(s): LISTENER

De-configuring listener: LISTENER
Stopping listener: LISTENER
Warning: Failed to stop listener. Listener may not be running.
Deleting listener: LISTENER
Listener deleted successfully.
Listener de-configured successfully.

De-configuring Naming Methods configuration file...
Naming Methods configuration file de-configured successfully.

De-configuring backup files...
Backup files de-configured successfully.

The network configuration has been cleaned up successfully.

Network Configuration clean config END

Oracle Configuration Manager clean START
OCM clean log file location : /tmp/deinstall2011-08-09_06-54-51-PM/logs//ocm_clean1704.log
Oracle Configuration Manager clean END
Oracle Universal Installer clean START

Detach Oracle home '/u01/app/oracle/home' from the central inventory on the local node : Done

Oracle Universal Installer clean END

Oracle install clean START

Clean install operation removing temporary directory '/tmp/install' on node 'denlx01'

Oracle install clean END

######################### CLEAN OPERATION END #########################

####################### CLEAN OPERATION SUMMARY #######################
Successfully de-configured the following database instances : emrep
Following Single Instance listener(s) were de-configured successfully: LISTENER
Cleaning the config for CCR
Cleaning the CCR configuration by executing its binaries
CCR clean is finished
Successfully detached Oracle home '/u01/app/oracle/home' from the central inventory on the local node.
Failed to delete directory '/u01/app/oracle/home' on the local node.
Successfully deleted directory '/u01/app/oraInventory' on the local node.
Failed to delete directory '/u01/app/oracle' on the local node.
Oracle Universal Installer cleanup completed with errors.

Run 'rm -rf /etc/oraInst.loc' as root on node(s) 'denlx01' at the end of the session.

Oracle install successfully cleaned up the temporary directories.
#######################################################################

############# ORACLE DEINSTALL & DECONFIG TOOL END #############

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.