This page lists down resources related to Oracle Server Manager including weblogic, Java Runtime Engine for the Server Manager Agent, managed server and SiteKey.
Tools 9.1: The Server Manager console is available for either OAS (OC4J) or WAS.
Tools 9.2: The Server Manager console is available for WebLogic Server and WebSphere. OC4J was removed and OAS was deprecated.
Action: You must obtain and install either WebLogic Server (WLS) or WebSphere (WAS).
For WLS, a 64-bit JRE must be installed as a prerequisite.
For WAS, the product includes its own JRE.
Important: There is no upgrade path from OC4J to WebLogic. For 9.2, if you want to use Oracle Middleware for Server Manager, you must perform a fresh install of WebLogic.
For more information, see Installing the Management Console on WebLogic Server Tools in the JD Edwards EnterpriseOne Server Manager Guide.
This refers to the JRE used by JD Edwards EnterpriseOne on the Enterprise Server on which the Server Manager Agent is installed. Note that the Oracle Universal Installer (OUI) includes its own JRE that is used only by the OUI.
Tools 9.1: The JRE for use by EnterpriseOne runtime is bundled with Server Manager Agent installer.
Tools 9.2: The JRE for use by EnterpriseOne runtime is not bundled with the Server Manager Agent installer.
Action: You must obtain and install a 32-bit JRE on the target Enterprise Server prior to running the Server Manager Agent installer. The installer prompts for and validates the location of the JRE for EnterpriseOne and ensures that it is the requisite 32-bit version.
Supported JRE versions are specified on Oracle Certifications.
For more information, see Run the Management Agent Installer in the JD Edwards EnterpriseOne Server Manager Guide.
Tools 9.1: Deployment Servers are not managed by Server Manager.
The Tools Release on the Deployment Server is delivered by InstallShield.
Tools 9.2: Deployment Server is a Server Manager Managed Instance.
The Tools Release is installed on the Deployment Server using standard Server Manager functionality.
Action: You must install a Server Manager agent on the Deployment Server.
You must register the Deployment Server with Server Manager.
You must deploy the Tools Release component to the managed Deployment Server.
For more information, see these topics in the JD Edwards EnterpriseOne Server Manager Guide:
Tools 9.1: Not applicable.
Tools 9.2: Provided functionality to encrypt sensitive data in the .ini files used by JD Edwards EnterpriseOne.
Starting with EnterpriseOne Tools Release 9.2, the EnterpriseOne encryption system uses a site key to add a higher level of security for sensitive data stored in configuration files and databases. The site key is combined with other values to create an AES key. The encryption system then uses the AES key to encrypt individual data items. Encryption using AES is the industry-standard for achieving a highly secure encryption.
The site key values are not stored in the program code. Because site keys are stored and encrypted in the JDE.INI file, each customer has a unique site key, which provides a higher level of security.
Legacy encryption is used with an Oracle local database when using Tools Releases prior to 9.2.0.0 or with SQL Server Express (using any supported Tools Release).
Action: Set up encryption before an EnterpriseOne installation using a command line utility program on the Deployment Server. You can also set up encryption after an installation through Server Manager. Both methods involve using a site key for encryption.
For more information, see Encrypting Sensitive Data in EnterpriseOne in the JD Edwards EnterpriseOne Security Administration Guide.