The Management Console and the Management Agents have codependent release levels. The Management Console constantly monitors the version levels of the registered Management Agents and if it determines that a registered Management Agent is out of sync (mismatched) with the Management Console's own release level, then it notifies the user that an update is required for a specific Management Agent. This can happen any time you change the release level of the Management Console, either to a newer release or to an older release.
You must manually update a Management Agent when notified, as described in this chapter. If you do not update the Management Agent, unpredictable and undesirable results can occur in the execution of Server Manager requests on the target machine on which the Management Agent resides.
This chapter discusses:
If you update the Management Console to a new Tools Version (for example, 8.98.3), you must upgrade the Management Agents to the same version. Otherwise your Server Manager cannot communicate and operate with the target machines as expected.
You update the Management Console by changing its Software Component using the same method as changing any other Server Manager Managed Instance (refer to Managed Software Components).
Caution:Changing the Software Component version for the Management Console will automatically restart the Management Console application and terminate any active user sessions.
To update the Software Component:
On Managed Homes and Managed Instances, locate the Managed Home Location for your Software Component and click the link for the associated Managed Instance for home.
This is the location you specified when you installed the Software Component, where the default is
In the General section of the page, under Software Component Version, click the Change ... button.
The Management Console displays a popup with a list of available Managed Software Components is displayed. For example:
On the Change Tools Release popup, you can select a Software Component radio button and click the Change Component button to change to that version.
The update process starts immediately and upon completion the Management Console application will automatically restart. If the Management Console fails to restart as expected, refer to Section 27.3, "Troubleshooting an Unsuccessful Management Console Update" in this chapter for a description of symptoms and recovery.
Important:To update the WebLogic Server to 220.127.116.11, you must first update the Tools Release to 18.104.22.168.
After you update a Management Agent to a new tools version (for example, Tools Version 8.98.3), any existing WAS 6.x instances will display this message:
To resolve the Warning you must restart the Management Agent to complete the update process.
When the Management Console determines that a Management Agent version is out of sync (mismatched) with the version of the Management Console itself it displays a notification under the Managed Home Location of the applicable Management Agent. For example:
To update a Management Agent:
On Managed Homes, select the Managed Home Location for which indicates: Agent Update Required.
Use the check box to select the appropriate Managed Home Location.
Click the Update button.
The Management Console displays this confirmation dialog:
Click OK to immediately begin updating the selected Management Agent. Once the update is complete, Server Manager will automatically restart the Management Agent.
When the pre 9.2 Server Manager Agent is updated to 9.2 (the update process initiated from the Server Manager Console itself when the "Agent Update Required" message is seen by the Administrator and the Administrator selects the checkbox and performs the update operation) from an earlier tools release, it is necessary for the Administrator to manually change/replace the $SCFHA/jdk/jre within the Server Manager Agent after the update.
The Administrator should use a 32-bit jdk/jre if the Server Manager Agent is going to manage a Deployment/Enterprise Server, otherwise use a 64-bit jdk/jre.
It is recommended not to use the existing jdk/jre which came with the older Server Manager Agent installation.
(Release 9.2.1) To start or to stop all the instances, on Managed Homes and Managed instances, click Start All Instances or Stop All Instances button.
There may be times when updating the Management Console application is not successful. The symptoms of a failed updated is the lack of a logon screen after the update completes, even after restarting the Management Console. Server Manager provides a fallback script that can be used to redeploy the application and recover the Management Console without any data loss. The script will deploy the intended (change-to) release.
To troubleshoot an unsuccessful Management Console update:
Stop the Management Console service.
Start the Management Console service.
Open a command prompt and navigate to this directory:
jde_home is the install path of the Management Console.
redeployManagementConsole.cmd recovery script.
The script takes one parameter, which is the password used to initially install the Management Console. For example
Upon successful execution of this script, you can log on to the Management Console application.
(Release 22.214.171.124) If you updated WebLogic Server to 126.96.36.199 and the Management Console update was unsuccessful, troubleshoot the Management Console update before updating to EnterpriseOne Tools release 188.8.131.52 or later.
Ensure that the Server Manager Console is on a Tools Release earlier than 184.108.40.206.
Stop the Managed Server where Server Manager Console is installed on the WebLogic Server.
Extract the ManagementAgent_JAR file from 220.127.116.11 Server Manager JAR file. The ManagementAgent_JAR file is located at
Replace the ManagementAgent_JAR file with the file you have extracted in the previous step at following locations:
You need not replace the ManagementAgent-JAR file at this location if the lib folder is not available.
Start the Managed Server.
Update the Tools Release for Server Manager to 18.104.22.168.