Skip Headers
Oracle® Enterprise Manager Getting Started with Oracle Fusion Middleware Management
11g Release 1 (11.1.0.1)

E17558-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Discovering Middleware Targets

In order to manage and monitor Fusion Middleware components such as WebLogic Server instances, services and clusters, as well as the Java EE applications that depend on them, Enterprise Manger Grid Control must first "discover" the Fusion Middleware Domain containing these components.

Once discovered, the domain and the components within it are added as "managed targets". Management Agents are then assigned to each target, enabling Enterprise Manager Grid Control to collect the data needed to monitor the target.

This chapter covers the following:

Discovering a WebLogic 9.x or 10.x Domain Via Grid Control

Oracle WebLogic Server release 9.x and 10.x domains and their respective components can be discovered via Enterprise Manager Grid Control. A wizard guides you through the discovery process.

  1. Log into Enterprise Manager Grid Control.

  2. Click the Targets tab, then click the Middleware tab.

  3. Select Oracle Fusion Middleware/WebLogic Domain from the Add menu, then click Go.

  4. Enter the hostname for the WebLogic Administration Server for the domain in the Administration Server Host field. For example: myhost06.us.oracle.com

  5. Enter the WebLogic Administration Server port. The default value is 7001.

  6. 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.

  7. Select or specify the hostname and port of the Management Agent that will monitor the domain. An 11.1 Management Agent is required.

  8. 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 name the farm "Farm", followed by a two-digit number, such as, "Farm01".

  9. 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:

    https://support.oracle.com/CSP/ui/flash.html

  10. Optionally supply the Java Managment 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.

  11. 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

  12. Click Continue. Enterprise Manager will discover all Fusion Middleware targets within the domain.

  13. 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 Agent can be found on the domain host, that Agent will be assigned.

    • If a local Agent cannot be found, the Agent specified in the Targets page will be assigned.

    Note that you can also manually assign Agents to specific targets, if desired.

  14. 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 were unsuccessfully added.

  15. Click Close in the processing window when finished. The Results page displays the targets and Agent assignments.

  16. 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

Discovering a WebLogic Server 7.x or 8.x Domain Via Grid Control

Oracle WebLogic Server release 7.x and 8.x domains and their respective components can be discovered via Enterprise Manager Grid Control. A wizard guides you through the target discovery process.

  1. Log into Enterprise Manager Grid Control.

  2. Click the Targets tab, then click the Middleware tab.

  3. Select Oracle WebLogic Domain 7.x and 8.x from the Add menu, then click Go.

  4. Enter the hostname for the WebLogic Administration Server for the domain in the Administration Server Host field. For example: myhost06.us.oracle.com

  5. Enter the WebLogic Administration Server port.

  6. 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:

    https://support.oracle.com/CSP/ui/flash.html

  7. Supply 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.

  8. Supply or select the hostname for the Management Agent that will monitor the domain.

    If the Management Agent is not running on the same host as the Administration Server, then specify the hostname for the host the Management Agent is running on.

    If the Management Agent is running on the same host as the Administration Server, then set the BEA_HOME environment variable for the Management Agent user, and also ensure that the user has access to the BEA home directory.

  9. Optionally specify the absolute path to the directory where the wljmxclient.jar and wlclient.jar files are located as the value for Administration Server Home Directory. For example: <WL-HOME>/server/lib

    If the Management Agent is running on a different host than the host where Oracle WebLogic Server is running, copy the JAR files from the Oracle WebLogic Server host (which should be <WL-HOME>/server/lib) and place them in a directory on the Agent host. Then provide the path to that directory.

  10. Click Next.

  11. Supply the credentials of the operating system user who installed the Oracle WebLogic Administration Server on the Management host specified in the previous step. If the Administration Server and Management host are on different hosts, then specify the operating system credentials. These credentials will be used by the Management Agent to discover domains.

  12. Click Next.

  13. Select the Oracle WebLogic Server Domain that you want Grid Control to monitor.

  14. Click Next. Enterprise Manager will discover the WebLogic Server targets within the domain.

  15. Select the target(s) you want to add.

    Note that only active WebLogic Clusters, Admin Servers, Managed Servers, and Oracle Service Bus instances that are up and running are discovered and shown. There may be other Clusters, Admin Servers, Managed Servers, and OSBs in the domain, but if they are not running, then they are not shown in this page.

    If you want to add non-running targets later, go to the Oracle WebLogic Server Domain Home page and click Refresh Domain.

  16. Click Next.

  17. Review the target details, then click Next to finish.

Discovering Multiple WebLogic Domains Via EMCLI

If you have multiple WebLogic domains that you want to manage through Enterprise Manager Grid 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.

Enabling Automatic Discovery of New Domain Members

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 Service instances are created or removed, clusters are added, and so on.

By default, Enterprise Manger Grid Control is not automatically aware of changes made to Oracle WebLogic domains that have been configured as managed targets. However, you can enable a pre-defined Grid Control job named "WebLogic Domain Refresh" to automatically discover new domain members and add them as managed targets.

Note that targets that have been removed from the domain - such as Java EE applications that have been un-deployed - are NOT automatically removed as managed targets. Because historical performance and configuration data is stored in the Oracle Management Repository for all managed targets, targets remain unless they are explicitly removed by selecting Target Setup>Remove Target from the WebLogic Domain menu.

  1. Log into Enterprise Manager Grid Control.

  2. Click the Targets tab, then click the Middleware tab.

  3. Click on the WebLogic Domain you want to enable the job for in the Middleware home page.

  4. In the General region of the page, click the timestamp link next to the WebLogic Domain Refreshed property. The Refresh WebLogic Domain dialog opens.

  5. 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:

  1. Click the Jobs tab.

  2. Click the job title in the Job Activity page.

  3. Click Edit.