Ensuring All Configuration Changes Are Implemented on a Server
When you use Enterprise Manager to make configuration changes to a managed server Server that is managed by the Enterprise Manager application., the configuration changes are not applied to the managed server instantaneously. Enterprise Manager places configuration changes in a queue Entity that represents demand in WFM. Queues help predict workload by multiplying the volume of customer interactions by their expected handling time., converts the changes to configuration messages, and then sends them on the network to a managed server. The managed server then implements (or applies) the configuration changes. This configuration change process can result in a short delay. The delay occurs between the time you make a configuration change in Enterprise Manager and the time that this configuration change is applied to the server.
Problem:
You are not sure that all the configuration changes you have made are implemented on a server.
Solution:
This procedure explains how to verify that all configuration changes that you have made from Enterprise Manager are implemented on a managed server.
-
Go to System Management Module that allows performing suite-wide system management activities from a single, Web-based application, the Enterprise Manager.. Under Enterprise, select Settings and in the Installations tree (left pane), select the server.
-
Check to see if the Pending Messages (asterisk) icon
displays in the right pane of a screen associated with the server.If the Pending Messages icon
does not display, all the configuration messages have been sent from the Enterprise Manager to the managed server. Go to step 4.If the Pending Messages icon displays, go to step 3.
-
If the Pending Changes icon displays, check the status of configuration messages, as described here:
-
Select System Management, Enterprise, Configuration Status and in the Installations tree (left pane), select the managed server that is the target for the configuration changes.
-
Select the View Message Status button (if it displays in the lower-right corner of the screen).
-
In the Status column, check to see if any messages have either the Pending or Retrying status.
If there are no messages with either the Pending or Retrying status, all the configuration messages are sent from the Enterprise Manager to the server. Go to step 4.
If there are messages with the Pending or Retrying status, wait for those messages to disappear from the Configuration Status screen before proceeding to step 4.
-
-
Open the Enterprise Manager Agent Web application installed on every system server that communicates with the Enterprise Manager regarding any configuration changes or alarm messages for the relevant server. (EMA) application on the managed server.
To open the EMA application, enter the following URL in your web browser:
http://servername/EMA
Where servername is the host name of the managed server on which the EMA (or Tomcat server) listens for connections. For example:
http://recorderserver1/EMA
-
In the EMA application, select Status and then select System Monitor.
In the Status Messages section at the bottom of the screen, verify that there are status messages that indicate the configuration changes are applied on the server.
-
In the Enterprise Manager application, determine if the server has active alarms. Resolve any active alarms on the server, including any alarm that indicate a service restart is needed.
For information about resolving active alarms on a server, see
When you have completed all these steps, the server configuration is up-to-date and is applied on the server.