This section discusses:
Before the introduction of Server Manager, the only mechanism to obtain an enterprise-wide view of the JD Edwards EnterpriseOne topology was through the machine key applications (application tables F9650 and F9651) and Support Assistant, which uses the same tables to obtain topology information. Functionally, these mechanisms did not provide insight into the actual topology because their accuracy was not enforced, especially regarding web-based products. In addition some products, such as Transaction Server Components (such as RTE and Performance Monitor), were not tracked at all.
Server Manager provides an accurate depiction of the true topology through the managed deployment of all server software. The integration of the Oracle Configuration Manager leverages this accuracy (see Section 2.8, "Oracle Configuration Manager (OCM)").
Using Server Manager through the web-based Management Console, the JD Edwards EnterpriseOne administrator can create a new JD Edwards EnterpriseOne server on a remote machine. The JD Edwards EnterpriseOne software used for installation is stored on the Management Console machine after being downloaded from the Customer Connection website or using Change Assistant.
The software may be distributed, or copied, to the remote machine from the Management Console. This server software (JD Edwards EnterpriseOne Tools Release) can now be used to create new JD Edwards EnterpriseOne server. The Management Home Agent performs the installation of the specific server type and automatically performs the requisite default configuration. After it is successfully installed, the server can be maintained entirely through the Management Console. This deployment process is similar for all JD Edwards EnterpriseOne server types.
Server Manager provides a complete configuration management system for all server types. Each configuration entry from the
.properties files has been defined in metadata contained within the Management Console. It is no longer necessary to directly edit any of these configuration files, or even to know where they exist.
The configuration items are grouped into logical configuration topics. These topics are presented on the management page for each JD Edwards EnterpriseOne Managed Instance. Selecting a configuration topic displays all the individual configuration items contained within. These items are further grouped and displayed for viewing or editing. Each configuration item is displayed with a plain text description. Configuration items with a list of allowed values are displayed using drop down boxes.
A link to display context sensitive help is displayed next to each configuration item. Clicking this link displays the name of
.INI file that is being viewed, the section and entry name in the file to which the
.INI pertains, the default value of the setting, and a full description of the configuration item. For items with an associated list of allowed values each value is displayed in the help text.
The contents of the contextual help for each setting are also available in reference form in the Management Console documentation.
Through the Server Manager Management Console, a JD Edwards EnterpriseOne administrator can compare configurations for each remote Managed Instance, even if they reside on separate physical machines. This capability significantly reduces the effort required to ensure consistency among configurations, especially for those installations containing numerous JD Edwards EnterpriseOne servers.
Before the introduction of Server Manager, many of steps in the software life cycle were not logged by any JD Edwards EnterpriseOne mechanism. With Server Manager, the Management Console records and makes available an audit trail of actions, such as:
Installing or changing tools releases on a JD Edwards EnterpriseOne Enterprise Server.
Installing or changing runtime code on a JD Edwards EnterpriseOne HTML Web Server.
Changing to configuration items of Server Metrics.
Recording implemented notifications (for example, for a critical failure).
An administrator can use the Management Console to troubleshoot any of the Managed Instances within the management domain. Troubleshooting includes:
Retrieving and modifying configuration entries of managed servers.
Retrieving log files.
Comparing configurations of a particular instance with any other
Before Server Manager, some of this functionality was available through the Server Administration Workbench (SAW) web interface. However, Server Manager greatly enhances the capability of the administrator by extending this ability to managing all JD Edwards EnterpriseOne server-based products (for a list of supported servers, refer to Section 184.108.40.206, "JD Edwards EnterpriseOne Server Components"). Additionally, unlike the previous SAW implementation, which was directly embedded in the product, the Server Manager configuration management and troubleshooting tools are available even if the target instance is not running or fails to start.
Using Server Manager, the JD Edwards EnterpriseOne administrator can remotely start any Managed Instance through the browser-based Management Console. This functionality reduces the effort required perform configuration or performance tuning changes by removing the necessity to have physical access to the machine.
Due to its inherent knowledge of the registered topology, Server Manager can accurately determine and subsequently monitor all entities constituting an EnterpriseOne installation. As such, Server Manager provides enterprise-wide views rather than machine specific views, which eliminates the potential for inaccurate monitoring of general information. For example, Server Manager contains real-time data for user sessions, Java memory usage, JDBj connection cache, and prepared statement configurations. Without Server Manager, such information is not available.
Oracle created Oracle Configuration Manager (OCM) for capturing and uploading customer configuration and diagnostic data. This data is primarily obtained for Oracle installed products and is stored in a central repository at Oracle. Relative to Server Manager, the Oracle Configuration Manager refers to the incorporation of an interface with JD Edwards EnterpriseOne so that similar information can be captured and uploaded. As such, functionally Oracle Configuration Manager is another type of Managed Resource.
Oracle Configuration Manager can be installed only by Oracle customers who have an Oracle Customer ID and an ID for My Oracle Support.
Note:The OCM product does not run natively on IBM i machines. The majority of JD Edwards EnterpriseOne configuration data for IBM i machines can be obtained from the JD Edwards EnterpriseOne Microsoft Windows-based Deployment Server. In order for OCM to collect configuration and diagnostic data, you must have a Management Console or a Management Agent installed on your Deployment Server.
As an exception, specific Server Metrics information for JD Edwards EnterpriseOne on IBM i servers is not available through Oracle Configuration Manager. Such non-available information includes configuration information extracted from .INI files, Service Pack information, and web product information.