Every business wants to operate efficiently while keeping operational costs low, including technology costs, and driving innovation. JD Edwards EnterpriseOne Server Manager, the nerve center for administration, can help JD Edwards customers preserve their traditional high-value/low-TCO value proposition of running JDE by proactively managing, effectively monitoring, and easily diagnosing faults in components within your system.

Overview of Server Manager

There are several helpful features within Server Manager that are sometimes underutilized or unnoticed. Here are a few that were highlighted throughout the presentation:

• Single-click search for users: This is the number one spot for administrators to come to when troubleshooting issues that users report. It can show you what server a user is on, so you can narrow down where the issue is occurring.
• Simplified configuration management: This gives administrators the ability to compare INI file settings and servers. You can see what is different between them, and you it will help you find the reason behind issues in a certain instance. In addition to comparing and verifying configuration, it can also help you improve problem resolution time and send messages or end sessions entirely.
• Simplified monitor setup: This provides administrators with minor monitoring capabilities. You can link to an SMTP server, cause events or triggers, and establish thresholds for events. You can also set notification hours that determine the hours of the day in which email notifications can be set. This means you can set up “Do Not Disturb” quiet hours, prevent notifications from coming in while you’re away on vacation, etc.
• Server Manager security model: Server Manager has its own security structure that is independent from EnterpriseOne. However, it can be integrated with the EnterpriseOne security model. It is secure by default, meaning you have to grant users access to Server Manager. You can add JD Edwards users if you link Server Manager to EnterpriseOne, or you can create your own Server Manager users and assign them different roles and authorities. You can also grant access to server groups, so users can only see groups that they have been granted access to.
• Resource Management for JDE EnterpriseOne: This embodies Kernel Resource Manager (KRM), Memory and CPU diagnostics, recycling kernels, clearing your cache, JDEHeap Advanced Diagnostic Engine (JADE), BSFN Memory Diagnostics (BMD) tool, long-running SQL, long-running BSFN, long-running metadata and the clear cache table. These functionalities can help you identify performance issues and high memory consumption within your system. They will provide you with greater insight and diagnostics through instance level graphs and drill down capabilities.

What’s New in Server Manager

There are several new features that have been recently added to Server Manager. Now with Server Manager, you can:

• Change your WebLogic admin user password
• View EnterpriseOne Server Managed Instance details
• Set an EnterpriseOne Server Managed Instance sitekey
• Create an EnterpriseOne Server Instance with the app component
• Manage the following as Managed Instances:
  • BSSV
  • EnterpriseOne Server
  • Oracle Database
  • Microsoft SQL Database
  • IBM i Database
• Start All and Stop All Managed Instances
• Automate health monitoring capability for EnterpriseOne
• Install a code current installation for System i using REST APIs or UI
• Launch the JD Edwards One-Click Provisioning Console
• Leverage available REST API’s for authentication, provisioning, monitoring, and managing/updating operations

What’s on the Roadmap for Server Manager

In addition to the new and existing features within Server Manager, Oracle also has a few roadmap items that customers can expect to see in the future of Server Manager.

• Automated multi-foundation Tools release: This will give you the option to automatically create multi-foundation on your Deployment Server component change. This will be important as organizations begin to enable 64-bit. There are three different options for component changes—no multi-foundation/component change only, component change and backup current system for multi-foundation, or component download for multi-foundation only. Creating multi-foundation will move the existing foundation into a secondary directory structure. Packages that are using the default foundation will be modified to point to the new foundation.
• 64-bit impact on Server Manager Deployment Server: It’s important to remember that 64-bit enablement is completely optional, but if your organization does choose to enable it, there are some changes to the Deployment Server that you should be aware of. Software component descriptions will add bitness to Manifest SCF in PAR. The change component will also warn if bitness is being changed, validate that the bitness of the Target TR and JRE is the same, update INI file values, and copy or remove JDEJRE from E920.
• Service Enablement of Server Manager: Server Manager is already equipped with provisioning, monitoring and management capabilities. A REST Enablement layer has now been introduced in Server Manager to expose these functionalities as REST APIs. The goal moving forward is to pull REST APIs for provisioning, configurations, monitoring, and change management (Tools patching), into a single tool that can enable automation of common tasks.
• Mobile Server Manager (iOS Mobile): This roadmap item is still in the research phases, but the idea is to be able to access common Server Manager features and functions on a mobile device. Users would be able to monitor instances, start and stop instances, view instance details, etc.