| Oracle® Enterprise Manager Cloud Control Administrator's Guide 12c Release 1 (12.1.0.2) Part Number E24473-16 |
|
|
PDF · Mobi · ePub |
| Oracle® Enterprise Manager Cloud Control Administrator's Guide 12c Release 1 (12.1.0.2) Part Number E24473-16 |
|
|
PDF · Mobi · ePub |
This chapter provides an overview of Plug-In Manager, and describes how you can use it to view, deploy, administer, and undeploy plug-ins.
In particular, this chapter covers the following:
This section covers the following:
Enterprise Manager is system management software that delivers centralized monitoring, administration, and life cycle management functionality for the complete IT infrastructure, including systems running Oracle and non-Oracle technologies.
Enterprise Manager has grown in size and magnitude over the years to offer a spectrum of powerful IT management and monitoring solutions. This growth has lead to changes in managing support for new features, enhancements, and bug fixes.
Considering these developments, Oracle has carefully redesigned the architecture of Enterprise Manager in such a way that the framework or the core base on which the product runs is clearly separated from the layer that offers IT solutions by means of features. This new architecture implemented in Enterprise Manager 12c enables Oracle to provide a much stronger framework with capabilities to extend itself seamlessly from time to time for supporting new features and enhancements.
You no longer have to wait for the next release of Enterprise Manager to access the latest monitoring features for released products. You can get the features for targets as soon as the targets are released. You can install a new Enterprise Manager system or upgrade an existing one, as soon as the Enterprise Manager release is made available by Oracle.
Based on the new design, the Enterprise Manager 12c architecture constitutes the following logical parts:
EM Platform: Consists of a set of closely integrated UI and backend services that most monitoring and management functionality in Enterprise Manager depends on. Examples of platform subsystems include the Enterprise Manager target and metric model, the job, event, and provisioning framework. The platform also includes Oracle Management Agent (Management Agent) as well as the core background services such as the data loader, job dispatcher, and notification manager. The platform is delivered as part of an Enterprise Manager release, and can only be upgraded by upgrading to a new version of Enterprise Manager.
EM Plug-ins: Modules that can be plugged to an existing Enterprise Manager Platform to provide target management or other vertical functionality in Enterprise Manager. Plug-ins offer special solutions or new features, for example, connectivity to My Oracle Support, and extend monitoring and management capability to Enterprise Manager, which enable you to monitor a particular target on a host. Plug-ins work in conjunction with OMS and Management Agent to offer monitoring services, and therefore they are deployed to the OMS as well as the Management Agent.
The plug-in releases happen more often than Enterprise Manager Core Platform releases. The plug-ins enable Enterprise Manager 12c to be updated with new features and management support for the latest Oracle product releases, without having to wait for the next platform release to provide such functionality.
Plug-ins are modules that can be plugged into an existing Enterprise Manager Cloud Control deployment to extend target management or other vertical functionality in Enterprise Manager.
As a part of Enterprise Manager Cloud Control installation, a set of basic plug-ins is deployed by default. You can deploy other plug-ins to extend the basic functionality of Enterprise Manager Cloud Control.
Plug-in releases happen more often than Enterprise Manager Core platform releases. This new pluggable framework enables Enterprise Manager Cloud Control to be updated with management support for the latest Oracle product releases, without having to wait for the next platform release to provide such functionality.
For example, when a new version of Oracle Database is released, you can simply download and deploy the latest Oracle Database plug-in, which will include management support for the latest Oracle Database release.
Figure 22-1 illustrates the workflow of plug-in deployment—how you typically set up the Enterprise Manager infrastructure, deploy plug-ins to OMS, and discovery and monitor targets using the deployed plug-ins.
Step 1: Setting up Self-Update Console
Self Update console is a common dashboard used for reviewing, downloading, and applying new updates available for Enterprise Manager. The console frees you from having to monitor multiple channels to get informed about new updates that are available from Oracle. The updates automatically downloaded by Self Update include plug-ins. For checking the availability of plug-ins and downloading them to Enterprise Manager, you must set up the Self Update Console. Set up the Self Update Console as described in Oracle Enterprise Manager Cloud Control Administrator's Guide.
Step 2: Checking Plug-In Availability
Checking the plug-in availability essentially refers to the act of verifying whether the plug-ins are available on My Oracle Support for download and deployment in Enterprise Manager. This is a prerequisite before downloading plug-ins. To check plug-in availability, follow the steps outlined in Section 22.4.1.
Step 3: Viewing Plug-In Information
Viewing plug-in information refers to the act of viewing basic information related to a particular plug-in, such as the plug-in ID, the plug-in release number, and other basic information. You must view plug-in information to understand what targets and operating systems are certified for plug-ins. You can also check whether or not a particular plug-in has already been deployed. To view plug-in information, follow the steps outlined in Section 22.4.2.
Step 4: Downloading Plug-Ins
Downloading plug-ins is the act of downloading plug-in archives or components, and its metadata, from My Oracle Support to Oracle Software Library (Software Library), so that they can be deployed suitably for discovering and monitoring certain targets. If you find that a particular target is not being monitored by plug-ins, you must download the required plug-ins. You can download both in online mode and offline mode. To download plug-ins, follow the steps outlined in Section 22.4.3.
Step 5: Deploying Plug-Ins to OMS
Deploying plug-ins to OMS is the next natural course of action once a plug-in is downloaded from My Oracle Support. This is to ensure the OMS capabilities are extended to either manage a new target or to add a new vertical capability. The installation and configuration of plug-ins on the OMS is essentially referred to as Deployment.
Figure 22-2 illustrates how plug-ins are deployed to the OMS.
When the plug-in archives are deployed from the Software Library to the OMS, the OMS receives three different components for each plug-in, namely the OMS plug-in components, the discovery plug-in components, and the monitoring plug-in components.
Discovery plug-in components are those components that help in the discovery of unmanaged targets. Monitoring plug-in components are those components that help in the adding of discovered targets to Enterprise Manager Cloud Control Console for monitoring purposes.
To deploy plug-ins on OMS, follow the steps outlined in Section 22.4.4.
Discovering targets refers to the process of identifying unmanaged hosts and targets in your environment. During discovery of targets, the discovery components of plug-ins are deployed to the Management Agent home. Note that this enables Enterprise Manager Cloud Control to only identify a new target in your environment; it however does not monitor the target.
After converting unmanaged hosts to managed hosts in Enterprise Manager Cloud Control, you must configure automatic discovery of targets on those hosts so that the unmanaged targets running on those hosts can be identified.
For instructions to configure automatic discovery of targets on managed hosts, access the following URL:
http://docs.oracle.com/cd/E24628_01/doc.121/e24473/discovery.htm#CBAGJFHC
Note:
When you configure automatic discovery of targets on managed hosts, discovery plug-in components are copied to Management Agent.Once you have configured automatic discovery of targets on managed hosts, you must regularly check for discovered targets so that they can be promoted and monitored in Enterprise Manager Cloud Control.
For instructions to check for and promote discovered targets to managed status, access the following URL:
http://docs.oracle.com/cd/E24628_01/doc.121/e24473/discovery.htm#CBAFHEHC
Note:
The plug-in for a specific target type is automatically deployed to the Management Agent that will monitor targets of that type. For example, if you discover an Oracle Database target, the Oracle Database plug-in will be pushed to the Management Agent installed on the database host machine.When you check for and promote targets, monitoring plug-in components are copied to Management Agent.
Figure 22-3 illustrates how the discovery plug-in components are deployed to the Management Agent while discovering new targets.
Step 7: Adding Targets for Monitoring
Once the targets are discovered, they are added to the infrastructure, so that they can be monitored in Enterprise Manager Cloud Control. While adding targets, the monitoring components of plug-ins are deployed to the Management Agent home.
Figure 22-4 illustrates how the monitoring plug-in components are deployed to the Management Agent while adding targets.
This section introduces you to the Plug-In Manager, and describes some essential concepts you must understand before you start deploying or administering plug-ins. In particular, this section covers the following:
Plug-In Manager is a feature of Enterprise Manager Cloud Control, that serves as a single window solution for performing all plug-in deployment-related activities, through GUI as well as CLI. Using Plug-In Manager, you can:
View plug-ins available for download; plug-ins that have been downloaded; and plug-ins that have been deployed to Cloud Control.
View certification and critical information about plug-ins such as the name of the plug-in, the vendor who supplied it, the plug-in ID and version, and a short description.
Deploy plug-ins on OMS and Management Agent.
Undeploy plug-ins from OMS and Management Agent.
View the status of a plug-in deployment operations.
Figure 22-5 illustrates how you can navigate to the Plug-in Manager.
Figure 22-6 shows the operations you can perform using the Plug-In Manager.
This section describes the following actions or operations that are supported by the Plug-In Manager.
To check the availability of plug-ins, follow these steps:
Set up the Self Update Console as described in Oracle Enterprise Manager Cloud Control Administrator's Guide.
From the Setup menu, select Extensibility, then select Plug-ins.
On the Plug-ins page, in the Latest Available column of the table, check whether the plug-ins are available.
To refresh the list of available plug-ins, click Check Updates.
This section gives you more information on plug-ins, and functions related to plug-ins. This section covers the following sections:
Differentiating Plug-In Releases from Enterprise Manager Platform Releases
Viewing Targets and Operating Systems Certified for Deployed Plug-Ins
Plug-ins have independent release cycles and may or may not be tied to Enterprise Manager Cloud Control product releases.
While the Enterprise Manager platform releases happen every six months tentatively, the plug-in releases typically happen more often, possibly every three to four months.
Figure 22-7 describes how plug-in releases are numbered.
Figure 22-8 describes how Enterprise Manager platform releases are numbered.
To identify the ID of a plug-in, follow these steps:
From the Setup menu, select Extensibility, then select Plug-ins.
On the Plug-ins page, in the Plug-in ID column of the table, note the plug-in ID of the plug-in of your interest.
If you do not see this column, from the View menu, select Columns, then select Plug-in ID.
Figure 22-9 illustrates how you can identify the plug-in ID of the Oracle Database plug-in.
To view a list of targets and operating systems certified for a deployed plug-in, follow these steps:
From the Setup menu, select Extensibility, then select Plug-ins.
On the Plug-ins page, select the plug-in of your interest, and from the Actions menu, select Information.
On the Plug-in Information page, in the General tab, review the information provided in the Certified Targets and Certified Operating Systems tables.
To view and administer the deployed plug-ins, from the Setup menu, select Extensibility, then select Plug-ins. Enterprise Manager Cloud Control displays the Plug-ins page, which is essentially the Plug-In Manager console.
This section covers the following sections:
Identifying the Oracle Management Service on Which a Plug-In Is Deployed
Identifying the Oracle Management Agent on Which a Plug-In Is Deployed
Identifying the Plug-Ins Deployed on Oracle Management Service
Identifying the Plug-Ins Deployed on Oracle Management Agent
To identify the OMS instances on which the plug-in of your interest is deployed, follow these steps:
From the Setup menu, select Extensibility, then select Plug-ins.
On the Plug-ins page, select the plug-in of your interest, and from the Actions menu, select Information.
On the Plug-in Information page, in the Management Servers tab, review the Oracle Management Services on which the plug-in is deployed.
To identify the Management Agents on which the plug-in of your interest is deployed, follow these steps:
From the Setup menu, select Extensibility, then select Plug-ins.
On the Plug-ins page, select the plug-in of your interest, and from the Actions menu, select Information.
On the Plug-in Information page, in the Management Agent tab, review the Management Agents on which the plug-in is deployed.
To identify the Plug-ins deployed on OMS, on EMCLI, enter the following command:
emcli list_plugins_on_server
To identify the Plug-ins deployed on Management Agent, on EMCLI, enter the following command:
emcli list_plugins_on_agent
You can download the plug-ins in online or offline mode. Online refers to an environment where you have Internet connectivity to connect to Enterprise Manager Store. Offline refers to an environment where you do not have Internet connectivity. This section contains the following sections:
To download the plug-ins in online mode, follow these steps:
From the Setup menu, select Extensibility, then select Self Update.
On the Self Update page, in the table, click on Plug-in.
On the Plug-in Updates page, select the plug-in available for download, and click Download.
Multiple selection of plug-ins is not supported.
In the Schedule Download dialog, select an appropriate option to schedule the download. You can also select Immediately which schedules the job for immediate action. Select Notify Once downloaded if you want to be informed once the download is complete.
Click Select.
Enterprise Manager Cloud Control submits a job to download the selected plug-in from the Enterprise Manager Store to the Software Library.
A confirmation dialog appears to confirm that the job has been submitted successfully. In this confirmation dialog, you can click Job Details to track the status of the job.
To download the plug-ins in offline mode, follow these steps:
From the Setup menu, select Provisioning and Patching, then select Offline Patching.
In the Online and Offline Settings tab, select Offline.
Click Apply.
From the Setup menu, select Extensibility, then select Self Update.
On the Self Update page, click Check for Updates.
A message appears with a URL to an Oracle site from where the updates catalog file can be downloaded.
From an Internet-enabled computer, download the catalog file using the aforementioned URL.
Copy the downloaded catalog file to the OMS host or the Management Agent host where you plan to deploy the plug-ins.
Import the catalog file to Enterprise Manager. For instructions, refer to Importing Catalog Archives.
On the Self Update page, in the table, click Plug-in.
On the Plug-in Updates page, select the imported update that is available for download. Click Download.
A message appears with a URL to an Oracle site from where the update can be downloaded.
From a computer that is connected to the internet, download the update using the aforementioned URL.
Copy the downloaded file to the OMS host or the Management Agent host where you plan to deploy the plug-ins.
Import the downloaded plug-in archive to Enterprise Manager. For instructions, refer to Importing Plug-In Archives.
To import a catalog archive, follow these steps:
Download the catalog archive as described in Section 22.4.3.2.
Execute the following emcli command to import the downloaded catalog archive.
emcli import_update_catalog
-file="file"
-omslocal
emcli import_update_catalog
-file="file"
-host="hostname"
[-credential_set_name="setname"] | -credential_name="name" -credential_owner="owner"
Import plug-in archives to Oracle Software Library in the following cases:
When you want to deploy any non-Oracle plug-ins, that is, plug-ins that have been created by a company other than Oracle.
When you want to import other types of entity archives when Self Update is used in offline mode.
To import a plug-in archive, follow these steps:
Download the external archive as described in the previous section.
Set up the Enterprise Manager Command Line (EM CLI) utility. To do so, from the Setup menu, click Command Line Interface. Follow the instructions outlined on the Enterprise Manager Command Line Interface Download page.
Import the external archive in one of the following ways, depending on where EM CLI is installed.
If Enterprise Manager server is on the system on which you downloaded the plug-in archive (*.opar file), run the following command:
emcli import_update -file=”<path to *.opar file>” -omslocal
The -omslocal flag indicates that the plug-in archive path mentioned in the -file option is directly accessible to the EM server.
If Enterprise Manager server is on a different system than the plug-in archive, run the following command:
emcli import_update
-file=”<path to *.opar file you created>”
-host="host1.example.com"
-credential_name="host1_creds"
-credential_owner="admin1"
The command syntax is as follows:
-file: The absolute path to the *.opar file on the system where you created the archive.
-host: The target name for a host target where the file is available.
-credential_name: The name of the credentials on the remote system you are connecting to.
-credential_owner: The owner of the credentials on the host system you are connecting to.
Note:
As an alternative to the previous step, you can also run the following command:emcli import_update
-file=”<path to *.opar file you created>”
-host="hostname"
-credential_set_name="setname"
-credential_set_name: The set name of the preferred credential stored in the Management Repository for the host target. It can be one of the following:
HostCredsNormal: The default unprivileged credential set.
HostCredsPriv: The privileged credential set.
You can deploy plug-ins to an OMS instance in graphical or silent mode. While the graphical mode enables you to deploy one plug-in at a time, the silent mode enables you to deploy multiple plug-ins at a time, thus saving plug-in deployment time and downtime, if applicable.
Note:
Plug-ins must be deployed on the OMS prior to being deployed on Management Agents.
In a multi OMS environment, Plug-in Manager automates plug-in deployment on all the management servers.
A plug-in upgrade failure could put the Management Repository in an inconsistent state. Therefore it is strongly suggested that you back up the Management Repository before upgrading the plug-in.
The deployment time varies from one plug-in to another, depending on the volume of data populated in the Management Repository. A page is displayed that allows you to monitor the deployment status, as described in Section 22.4.4.1.
The deployment of some plug-ins requires the OMS to be stopped, and then restarted. This process occurs automatically as part of the plug-in deployment process.
While deploying plug-ins to the OMS, OMS plug-in components, discovery plug-in components, and monitoring plug-in components are deployed to the OMS.
To deploy plug-ins to the OMS in graphical mode, follow these steps:
From the Setup menu, select Extensibility, then select Plug-ins.
On the Plug-ins page, select the plug-in you want to deploy.
From the Deploy On menu, select Management Servers.
In the Deploy Plug-in on Management Servers dialog, enter the Management Repository SYS password, and click Continue. Proceed through the steps in the dialog box.
Click Deploy.
To deploy plug-ins to the OMS in silent mode, follow these steps:
Log in to EM CLI as follows:
$ORACLE_HOME/bin/emcli login -username=sysman
Run the following command:
$ORACLE_HOME/bin/emcli sync
To deploy the plug-ins on the OMS, run the following command:
emcli deploy_plugin_on_server
-plugin="plug-in_id[:version]
[-sys_password=sys_password]
[-prereq_check]"
Note:
For information on plug-in id, refer to Section 22.4.2.2.For example,
emcli deploy_plugin_on_server -plugin="oracle.sysman.db:12.1.0.2.0;oracle.sysman.emas:12.1.0.2.0"
Note:
The procedure for plug-in deployment remains the same even in a multi-OMS environment. Enterprise Manager automatically detects whether it is a single-OMS or a multi-OMS environment and in case of a multi-OMS environment, Enterprise Manager automatically deploys the selected plug-in on all OMS instances.If the plug-in deployment on any Oracle Management Service fails, perform the same steps again.
This section describes the procedure of monitoring the deployment status of plug-ins that do not require down time as well as those that do require down time. The following sections are covered in this section:
Tracking the Status of Plug-Ins that Do Not Require Down Time
Tracking the Deployment Status of Plug-Ins that Require Down Time
To monitor the status of deployment and undeployment operations for plug-ins that do not require down time, follow these steps:
From the Setup menu, select Extensibility, then select Plug-ins.
On the Plug-ins page, do one of the following:
From the Actions menu, select Deployment Activities.
Select a plug-in, and click the Recent Deployment Activities tab at the bottom of the page.
This section contains the following sections:
Upgrading Across Plug-In Versions Deployed to Oracle Management Service
Upgrading Across Plug-In Revisions Within a Plug-In Version Deployed to Oracle Management Service
You can upgrade across plug-in versions, that is, from one plug-in version to another higher plug-in version or a revision of another higher plug-in version. For example, from Oracle Database plug-in version 12.1.0.1.0 to version 12.1.0.2.0, or from Oracle Database plug-in version 12.1.0.1.0 to version 12.1.0.2.0 [u120427].
To upgrade across plug-in versions deployed to the OMS, follow these steps:
Check for the latest available versions and revisions in the Enterprise Manager Store as described in Section 22.4.1.
Download them as described in Section 22.4.3.
Deploy them to the OMS as described in Section 22.4.3.
This section describes how you can upgrade across plug-in revisions within a plug-in version, that is, from one revision of a plug-in version to another revision of the same plug-in version. For example, from Oracle Database plug-in version 12.1.0.2.0 [u120427] to version 12.1.0.2.0 [u120502].
Plug-in revisions of a particular version are usually released only for the OMS, therefore, when you upgrade across plug-in revisions, you essentially upgrade only the plug-in revisions deployed to the OMS.
To upgrade the plug-in revisions deployed to the OMS, follow these steps:
Check for the latest available revisions in the Enterprise Manager Store as described in Section 22.4.1.
Download them as described in Section 22.4.3.
Apply the patches required for the plug-in revision.
From the Setup menu, select Extensibility, then select Plug-ins.
On the Plug-ins page, select the plug-in revision you downloaded, and from the Actions menu, select Information.
On the Plug-in Information page, in the General tab, in the Dependencies section, in the Bug Fixes Required table, click View Bug Fixes.
In the Required Bug Fixes dialog, note the bug numbers listed in the Bug Number column of the Management Server Fixes table.
Download the patches that contain the fixes for the bugs you noted in the previous step.
Apply the downloaded patches on the OMS.
Deploy the latest available revisions to the OMS as described in Section 22.4.6.
While installing a Management Agent using the Add Host Targets Wizard, all the discovery plug-ins available on the OMS are automatically deployed to the Management Agent.
For information about discovery plug-ins, refer to Section 22.4.2.
If you want to deploy any additional plug-ins after installing the Management Agent, then follow these steps:
Set up the Self Update console.
Check whether the plug-ins are available on Enterprise Manager store. For instructions refer to Section 22.4.1.
Download the available plug-ins. For instructions, refer to Section 22.4.3.
Deploy the downloaded plug-ins to the Management Agent.
From the Setup menu, select Extensibility, then select Plug-ins.
On the Plug-ins page, select the plug-in you want to deploy.
From the Deploy On menu, select Management Agent.
Follow the steps mentioned in the Deploy Plug-ins on Management Agent dialogue box.
Click Deploy.
To deploy plug-ins in EM CLI, use the following command:
deploy_plugin_on_agent
To track the deployment status of plug-ins on Management Agent, refer to Section 22.4.4.1.
You can upgrade across plug-in versions, that is, from one plug-in version to another, higher plug-in version or a revision of another, higher plug-in version. For example, from Oracle Database plug-in version 12.1.0.1.0 to version 12.1.0.2.0, or from Oracle Database plug-in version 12.1.0.1.0 to version 12.1.0.2.0 [u120427].
Note:
You will upgrade the plug-in versions and revisions only on Management Agents that are already installed in your environment. All new Management Agent installations will automatically include the latest versions and revisions from the OMS.To upgrade across plug-in versions deployed to the Management Agent, follow these steps:
Check for the latest available versions and revisions in the Enterprise Manager Store as described in Section 22.4.1.
Download them as described in Section 22.4.3.
From the Setup menu, select Extensibility, then select Plug-ins.
On the Plug-ins page, select the plug-in you want to upgrade.
From the Deploy On menu, select Management Agent.
In the Deploy Plug-in on Management Agent dialog, select the version or revision of the plug-in you want to upgrade to.
Click Add and add the Management Agents from which you want to undeploy the plug-in. Click Continue. Then click Next. And then click Deploy.
On the Confirmation dialog, click Close.
To undeploy plug-ins from the Management Agent, follow the steps:
From the Setup menu, select Extensibility, then select Plug-ins.
On the Plug-ins page, select the plug-in you want to undeploy, and from the Actions menu, select Undeploy From, then select Management Agent.
In the Undeploy Plug-in From Management Agent dialog, click Add and add the Management Agents from which you want to undeploy the plug-in. Click Continue. Then click Undeploy.
On the Confirmation dialog, click Close.
To monitor the undeployment operation, click Show Status.
Note:
Undeployment of a plug-in from the Management Agent restarts the Management Agent. The Management Agent does not monitor any target during downtime.Undeploying a plug-in from Management Agent also removes all the targets that were monitored by the plug-in.
To undeploy a plug-in in EM CLI, use the following command:
undeploy_plugin_from_agent
To undeploy plug-ins from the OMS, follow the steps:
From the Setup menu, select Extensibility, then select Plug-ins.
On the Plug-ins page, select the plug-in you want to undeploy, and from the Actions menu, select Undeploy From, then select Management Servers.
In the Undeploy Plug-in From Management Server dialog, enter the Management Repository SYS password, and click Continue. Then click Undeploy.
On the Confirmation dialog, click Close.
To monitor the undeployment operation, click Show Status.
To undeploy a plug-in in EM CLI, use the following command:
undeploy_plugin_from_server
This section contains information on troubleshooting plug-in related issues. The following sections are covered in this section:
Plug-in homes are essentially Oracle homes that are dedicated for plug-ins. The plug-in home for plug-ins deployed to the OMS is different from the plug-in home for plug-ins deployed to the Management Agent.
Figure 22-10 shows the plug-in homes for plug-ins deployed to the OMS and the Management Agent, which is installed with the OMS, in the middleware home.
Figure 22-11 indicates the plug-in home for plug-ins deployed to a standalone Management Agent.
If plug-in deployment to the OMS fails, then review the log file available in the following location. Use them to debug the issue, and if you raise a service request to Oracle Support, then make sure you append these to the service request.
$<OMS_HOME>/cfgtoollogs/pluginca/*
If plug-in deployment to the Management Agent fails, then review the log file available in the following locations.
agent_inst/sysman/log/*
agent_inst/sysman/registry.xml
agent_inst/install/logs/*
Use the log files found in the aforementioned locations to debug the issue, and if you raise a service request to Oracle Support, then make sure you append these to the service request.
Note:
When you install an additional OMS by cloning an existing, running OMS instance, the plug-in deployed to the source OMS are automatically carried over to the cloned OMS as well. Therefore, you do not have to redeploy the plug-ins on the cloned OMS.In case of multi OMS environment, the OMS_HOME in the log file path indicates the root folder of the OMS where the failure occurs.
For information about installing an additional OMS, refer to the Oracle Enterprise Manager Cloud Control Basic Installation Guide.
|
 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
