| Oracle® Enterprise Manager Cloud Control Getting Started with Oracle Fusion Middleware Management 12c Release 1 (12.1.0.1) Part Number E24215-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Enterprise Manager Cloud Control Getting Started with Oracle Fusion Middleware Management 12c Release 1 (12.1.0.1) Part Number E24215-01 |
|
|
PDF · Mobi · ePub |
In order to manage and monitor Oracle Fusion Middleware components such as WebLogic Server instances and clusters, as well as the Java EE applications that depend on them, Enterprise Manager Cloud Control must first "discover" the Fusion Middleware Domain containing these components.
Once discovered, the domain and the components within it can be promoted to "managed target" status. In this process, Management Agents are assigned to each target, enabling Enterprise Manager Cloud Control to collect the data needed to monitor the target.
This chapter covers the following:
Cloud Control provides the ability to automatically search for potential Oracle Fusion Middleware targets on host machines that are already being managed by Cloud Control. You can configure automatic discovery to run on a regular schedule, such as every 2 days. Discovery is run every 24 hours by default.
Once automatic discovery has been configured, you can check the Auto Discovery Results page to see what new Oracle Fusion Middleware targets have been discovered. You can then promote targets to managed target status by assigning a Management Agent to monitor and manage the target.
The following describes the process for configuring automatic discovery of Oracle Fusion Middleware targets only. However, Cloud Control actually enables you to configure discovery of a variety of Oracle target types.
Note that the automatic discovery feature is not supported for Oracle WebLogic Server versions 7.x or 8.x.
Select Add Target>Configure Auto Discovery from the Setup menu.
Set the schedule at which the discovery job will be run, in days. This schedule will be applied to all selected hosts. By default the job will run every 24 hours.
Click Add Host. Select the host machine(s) you want to include in the discovery.
Select a host in the table, then click Edit Parameters to specify the Middleware Homes to search for targets. The Middleware Home is the top-level directory for all Oracle Fusion Middleware products, created when Oracle WebLogic Server is installed.
Enter * to search all Middleware Homes, or specify the path to one or more Middleware Homes on the host, each separated by a comma.
Click OK. At this point, automatic discovery has been enabled, and the discovery job will run at the scheduled frequency.
Once automatic discovery has been enabled, you should check Cloud Control regularly to view the list of discovered targets. Select Add Target>Auto Discovery Results from the Setup menu.
Click the Non-Host Targets tab to view the discovered Oracle Fusion Middleware targets.
Select a target, then click Promote.
If multiple targets of various types are listed, you can expand Search, then select the Target Type you are looking for (such as Oracle WebLogic Domain). Click Search to display the selected discovered target types.
Supply or accept values for the following parameters:
The hostname for the WebLogic Administration Server for the domain in the Administration Server Host field. For example: myhost06.us.oracle.com
The WebLogic Administration Server port.
If the WebLogic Administration Server is secured using the Secure Sockets Layer (SSL) protocol, specify the location of the trusted keystore file. The keystore is a protected database that holds keys and certificates for an enterprise.
For additional details on discovering a domain secured with SSL, see section "C" in My Oracle Support Note 1093655.1. You can access My Oracle Support at the following URL:
The WebLogic Administration Server username and password.
A Unique Domain Identifier. This value is used as a prefix to ensure farm names are unique in environments with the same domain name. By default, Enterprise Manager will assign the name "Farm", followed by a two-digit number, such as "Farm01".
The hostname for a Management Agent that will be used to discover the Fusion Middleware targets.
If a Management Agent exists on the WebLogic Administration Server host, the hostname for this Management Agent will be supplied by default. However, you can specify any Management Agent on any host that is managed by Cloud Control to perform the discovery.
Click Continue. Enterprise Manager will discover all Fusion Middleware targets within the domain.
Click Close in the Finding Targets dialog to automatically assign Management Agents to the discovered targets.
The Assign Agents page lists each Fusion Middleware target discovered and the Management Agent assigned to each. Agents are automatically assigned as follows:
If a local Management Agent is installed on the discovered target host, that Agent will be assigned.
If a local Management Agent cannot be found on the host, the Agent specified in the Targets page will be assigned.
Note that you can also manually assign Management Agents to specific targets, if desired.
Click Add Targets to assign Management Agents as listed in the Assign Agents page.
The Saving Target to Agent processing window appears, indicating how many total targets have been added and successfully saved. It will also indicate the number of targets that were unsuccessfully added.
Click Close in the processing window when finished. The Results page displays the targets and Agent assignments.
Click OK when finished. There may be a delay before these targets are visible and monitored. All the agents used for monitoring the targets must be up
This section covers the following:
Oracle WebLogic Server release 9.x and 10.x domains and their respective components can be discovered via Enterprise Manager Cloud Control. A wizard guides you through the discovery process.
Select Add Target>Configure Auto Discovery from the Setup menu.
Select the Add Non-Host Targets by Specifying Target Monitoring Properties option.
Select Oracle Fusion Middleware as the target type.
Click Add Using Guided Discovery.
Enter the hostname for the WebLogic Administration Server for the domain in the Administration Server Host field. For example: myhost06.us.oracle.com
Enter the WebLogic Administration Server port. The default value is 7001.
Enter the WebLogic Administration Server username and password.
If you want to discover the target only for monitoring purposes, then it is sufficient to provide a user name that has monitoring role. If you want to monitor the target and also perform start/stop operations, then ensure that you provide a user name that has either an operator role or an admin role.
Supply or accept values for the following parameters:
The hostname for the WebLogic Administration Server for the domain in the Administration Server Host field. For example: myhost06.us.oracle.com
The WebLogic Administration Server port.
If the WebLogic Administration Server is secured using the Secure Sockets Layer (SSL) protocol, specify the location of the trusted keystore file. The keystore is a protected database that holds keys and certificates for an enterprise.
For additional details on discovering a domain secured with SSL, see section "C" in My Oracle Support Note 1093655.1. You can access My Oracle Support at the following URL:
The WebLogic Administration Server username and password.
A Unique Domain Identifier. This value is used as a prefix to ensure farm names are unique in environments with the same domain name. By default, Enterprise Manager will name the farm "Farm", followed by a two-digit number, such as, "Farm01".
The hostname for a Management Agent that will be used to discover the Fusion Middleware targets.
If a Management Agent exists on the WebLogic Administration Server host, the hostname for this Management Agent will be supplied by default. However, you can specify any Management Agent on any host that is managed by Cloud Control to perform the discovery.
Specify a Unique Domain Identifier. This value is used as a prefix to ensure farm names are unique in environments with the same domain name. By default, Enterprise Manager will pre-pend the name with "Farm", followed by a two-digit number, such as, "Farm01".
If the target domain is secured, expand the Advanced node to specify the protocol to use in the Protocol field. The default value is t3.
For additional details on discovering a domain secured using the Secure Sockets Layer (SSL) protocol, see section "C" in My Oracle Support Note 1093655.1. You can access My Oracle Support at the following URL:
Optionally supply the Java Management Extensions (JMX) Service URL that will be used to establish a JMX connection to the WebLogic Administration Server. For example:
service:jmx:t3://shutter.company.com:5555/jndi/weblogic.management.mbeanservers.domainruntime
If you do not supply a value, Enterprise Manager will provide the Service URL based on the host port and protocol.
Optionally enter any system properties to be used by the Java process to connect to the WebLogic Administration Server in the Parameters field.
Supply space-separated name/value pairs. Preface each parameter with -D. For example:
-Dparam1=xxx -Dparam2=yyy -Dparam3=zzz
Click Continue. Enterprise Manager will discover all Fusion Middleware targets within the domain.
Click Close in the Finding Targets dialog to automatically assign Management Agents to the discovered targets.
The Assign Agents page lists each Fusion Middleware target discovered and the Management Agent assigned to each. Agents are automatically assigned as follows:
If a local Management Agent is installed on the discovered target host, that Agent will be assigned.
If a local Management Agent cannot be found on the host, the Agent specified in the Targets page will be assigned.
Note that you can also manually assign Management Agents to specific targets, if desired.
Click Add Targets to assign Management Agents as listed in the Assign Agents page.
The Saving Target to Agent processing window appears, indicating how many total targets have been added and successfully saved. It will also indicate the number of targets that were unsuccessfully added.
Click Close in the processing window when finished. The Results page displays the targets and Agent assignments.
Click OK when finished. There may be a delay before these targets are visible and monitored. All the agents used for monitoring the targets must be up
If you have multiple WebLogic domains that you want to manage through Enterprise Manager Cloud Control, you can use the Enterprise Manager Command Line Interface (EMCLI) discover_wls verb to discover them all at once, rather than discovering them one at a time using the discovery wizards.
The discover_wls verb can be used to discover WebLogic Server versions 7.x, 8.x, 9.x, and 10.x domains. The verb reads a file named domain_discovery_file that contains the information required to discover each domain.
See the Enterprise Manager Command Line Interface book for instructions on using the discover_wls verb.
In the typical enterprise, Oracle WebLogic domains do not remain static. Instead, membership in the domain changes regularly: New Java EE applications are deployed, WebLogic Server instances are created or removed, clusters are added, and so on.
By default, Enterprise Manger Cloud Control is not automatically aware of changes made to Oracle WebLogic domains that have been configured as managed targets. However the application does provide the ability to discover and uptake new or modified domain members.
This section covers the following:
You can enable a pre-defined Cloud Control job named "WebLogic Domain Refresh" to automatically discover new domain members and add them as managed targets.
Select Middleware from the Targets menu.
Click on the WebLogic Domain you want to enable the job for in the Middleware home page.
In the General region of the page, click the timestamp link next to the WebLogic Domain Refreshed property. The Refresh WebLogic Domain dialog opens.
Check the Enable Automatic Refresh box in the Refresh WebLogic Domain dialog, then click OK.
Once enabled, the job will check for new domain members once every 24 hours by default. To change the job settings, including the frequency at which it is run:
Click the Jobs tab.
Click the job title in the Job Activity page.
Click Edit.
You can use Cloud Control to check a domain for new or modified members on a periodic basis.
Select Middleware from the Targets menu.
Click on the WebLogic Domain you want to enable the job for in the Middleware home page.
Select Refresh WebLogic Domain from the Farm or WebLogic Domain menu. The Refresh WebLogic Domain dialog opens.
Click Continue. Cloud Control will search the domain for new and modified targets.
The Assign Agents page displays the Fusion Middleware targets discovered and the Management Agent assigned to each. Click Add Targets to assign Management Agents as listed in the Assign Agents page.
Agents are automatically assigned as follows:
If a local Agent can be found on the target host, that Agent will be assigned.
If a local Agent cannot be found on the host, the Agent specified in the Targets page will be assigned.
Note that you can also manually assign Agents to specific targets, if desired.
The Saving Target to Agent processing window appears, indicating how many total targets have been added and successfully saved. It will also indicate the number of targets that were unsuccessfully added.
Click Close in the processing window when finished. The Results page displays the targets and Agent assignments.
Click OK when finished. There may be a delay before these targets are visible and monitored. All the agents used for monitoring the targets must be up.
|
 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
