You should consider refreshing the system whenever you upgrade the Exalogic Rack, for example, from a quarter to half. You should also consider refreshing when you discover Oracle VM Manager or ZFS targets after the Exalogic system is discovered. To refresh the Exalogic Elastic Cloud, follow these steps:
If you want to monitor Oracle applications either on a physical or virtual node, then a Enterprise Manager Management Agent needs to be installed to enable the Software tab. This Management Agent allows you to manage the servers, operating system, and software (for example, WebLogic, Oracle Database) through Enterprise Manager Cloud Control.
Modify the agentpush.properties file present in the <OMS_HOME>/sysman/prov/agentpush/agentpush.properties directory. Change:
oracle.sysman.prov.agentpush.pdpShellOutEnabled=true
to:
oracle.sysman.prov.agentpush.pdpShellOutEnabled=false
Note:
This step needs to be performed for all OMS instances.
After the Exalogic network has been configured, deploy the Management Agent by following instructions listed below:
Ensure that you have downloaded and applied the Management Agent software for the platforms of the hosts on which you want to install Management Agents.
In Enterprise Manager Cloud Control, do one of the following:
From the Setup menu, select Add Target, then select Auto Discovery Results. On the Auto Discovery Results page, click the Host and Oracle VM Manager tab and select a host that you want to monitor from the displayed list. Click Promote.
From the Setup menu, select Add Target, then select Add Targets Manually. On the Add Targets Manually page, select Add Host Targets and click Add Host.
On the Host and Platform page, do the following:
Accept the default name assigned for this session or enter a unique name of your choice. The custom name you enter can be any intuitive name, and need not necessarily be in the same format as the default name. For example, add_host_operation_1.
A unique deployment activity name enables you to save the installation details specified in this deployment session and reuse them in the future without having to enter all the details all over again in the new session.
Click Add to enter the fully qualified name and select the platform of the host on which you want to install the Management Agent.
Click Next.
On the Installation Details page, do the following:
In the Deployment Type section, select Fresh Agent Install.
From the table, select the first row that indicates the hosts grouped by their common platform name.
In the Installation Details section, provide the installation details common to the hosts selected in Step b. For Installation Base Directory, enter the absolute path to the agent base directory where you want the software binaries, security files, and inventory files of the Management Agent to be copied.
For Instance Directory, accept the default instance directory location or enter the absolute path to a directory of your choice where all Management Agent-related configuration files can be stored.
From Named Credential list, select an appropriate profile whose credentials can be used for setting up the SSH connectivity between the OMS and the remote hosts, and for installing a Management Agent on each of the remote hosts.
For Privileged Delegation Setting, validate the Privilege Delegation setting to be used for running the root scripts. By default, it is set to the Privilege Delegation setting configured in Enterprise Manager Cloud Control.
For Port, accept the default port (3872) that is assigned for the Management Agent to communicate, or enter a port of your choice.
Repeat for every other row you have in the table in step b.
Click Next.
If you want to deploy Management Agents on the selected hosts in a rolling manner, such that the deployment proceeds continuously from one deployment phase to another, ignoring the failed hosts in each deployment phase, specify the following in the $OMS_HOME/sysman/prov/agentpush/agentpush.properties file:
oracle.sysman.prov.agentpush.continueIgnoringFailedHost=true
On the Review page if you are satisfied with the details, then click Deploy Agent to install the Management Agent. You are automatically taken to the Add Host Status page that enables you to monitor the progress of the deployment session.
For more information about installing the agent, see the "Installing Oracle Management Agent" chapter of the Oracle® Enterprise Manager Cloud Control Basic Installation Guide:
http://docs.oracle.com/cd/E24628_01/install.121/e22624/install_agent.htm
Health check targets are discovered independently of Exalogic. This target can be accessed by a menu item which is added as part of integration of Health Check with Exalogic. The HealthCheck menu item is hidden in Exalogic system and rack menu if the HealthCheck target is not discovered. Once the HealthCheck target is discovered, you must refresh the Exalogic Cloud, which will then enable the menu item. You can then navigate to the HealthCheck page from the Exalogic system and rack menu.
Each rack has its own HealthCheck target and you can navigate to its own HealthCheck target (in case of multi rack scenario) while the Exalogic system displays the HealthCheck target of the primary rack.
For more information about configuring Oracle Exalogic Engineered System Healthchecks, see the Oracle® Enterprise Manager System Monitoring Plug-In Installation Guide for Oracle Engineered System Healthchecks:
http://docs.oracle.com/cd/E24628_01/install.121/e27420/toc.htm