Posted On: April 24, 2019
New Server Manager Features in 9.2
The JD Edwards EnterpriseOne Server Manager has always been an effective operational & technology tool. Historically speaking however, many customers & business partners have felt the need to supplement what is provided with more advanced capabilities. Recently, Oracle has introduced several valuable new features that are available at Release Level 9.2. Collectively, they serve to noticeably enhance an administrator’s ability to proactively manage, monitor & diagnose server-related issues. Some of the more useful features include:
1) Changing the WebLogic Server Admin Password.
This can be easily accomplished for any defined Weblogic instance (not WebSphere). Please note that this typically involves additional manipulation from within the Weblogic Admin Console. That’s required because of the need to synchronize the new/changed password in both places.
2) Setting Up an EnterpriseOne Server Managed Instance Site Key.
This is an important component of a new process for encrypting sensitive INI file data. That process involves setting up a site key for the security server. This greatly facilitates the preservation & integrity of passwords (for example) that should not be viewed indiscriminately.
3) Deploying ADF Applications Directly.
Oracle’s Application Development Framework (ADF) tool is being used with increasing frequency to create custom apps (e.g., Joint Venture Management). They can be easily deployed with this recently released Server Manager feature.
4) Broader Array of Supported Managed Instance Server Types.
In addition to BSSV servers, Oracle has now introduced the ability to manage all of their supported databases. That includes Oracle, Microsoft SQL & IBM iSeries. Consequently, all server types can now be fully monitored & administered via a single Server Manager entry point.
5) “Starting All” & “Stopping All” Managed Instances.
Rather than starting/stopping servers in the configuration manually & individually, that can now be done via a single “start all” or “stop all” command. Among other things, this ensures that all recycling activities occur in the proper sequence. For example, “stopping” should begin with the web components, followed by the enterprise servers &, finally, the databases. These new features serve to engender a much more efficient & error-free process overall.
6) On-Demand Health Check Monitoring.
For all practical purposes, this monitoring can be thought of as a form of quickly surface testing the various servers in a configuration. For web servers, that would include logging in to EnterpriseOne, running a sample interactive application & launching a batch UBE job. For enterprise servers, we’re talking about running a port test, a batch UBE & a “test” business function. All of this facilitates a quick & accurate system health assessment that historically has taken longer to complete manually.
Please refer to the JD Edwards EnterpriseOne Tools Server Manager Guide (Release 9.2.x) for more detailed information about how to invoke & utilize the above features. Please also look for additional blog articles regarding recommendations for optimizing that usage.
JD Edwards EnterpriseOne Tools Server Manager Guide: