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:

This chapter contains the following topics:

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

Description of Figure 1-1 follows
Description of "Figure 1-1 Deployment Architecture Example"