Environment Discovery

In order for a target to be monitored, it must first be discovered and promoted. Discovery is the process of making a target instance known to OEM. Once this has been done, the target needs to be promoted from an unmanaged to a managed state. This process requires some prerequisite steps.

Note:

Oracle recommends after upgrading the plugin, delete existing targets and re-discover.
  1. All components of the environment should be up, namely, the web application, the web service and batch servers.

  2. JMX should be configured on the target environment. To test this, use jconsole and connect to the JMX servers using the JMX URLs. You can search the WebLogic log for the Web and EJB JMX URLs. Examples:

    
service:jmx:rmi:///jndi/rmi://{host}:{ejbJmxPort}/oracle/ouaf/ejbAppConnector
service:jmx:rmi:///jndi/rmi://{host}:{webJmxPort}/oracle/ouaf/webAppConnector

    The threadpoolworker logs would have the batch JMX URLs. For example, service:jmx:rmi:///jndi/rmi://{host}:{batchJmxPort}/oracle/ouaf/batchConnector

    In FW 2.2, this would be service:jmx:rmi:///jndi/rmi://{host}:{batchJmxPort}/spl/fw/jmxConnector

    Make sure you can connect to the URLs and that the OEMTargetsBean is present, as illustrated in the following image:

    Note:

    Here, the host should be fully qualified domain name.

    The OEMTargetsBean is present and the connections to the URLs are available after configuring JMX on the target environment.

    Expand the OEMTargetsBean, click Operations, then click the toXML button. A window should popup and return the XML of the targets that will be discovered. Do this for each JMX connection.

    Determine the XML of the targets to be discovered for the JMX connection by expanding OEMTargetsBean, selecting Operations, and clicking the toXML button.

  3. Target monitoring can be performed via JMX or REST API. You can prefer to use REST API option, if you have any firewall restrictions. Details, to enable "JMX over REST" feature, are available below.

    1. Run configreEnv using FW menu options, choose option 57 and provide appropriate values for the displayed variables.

    2. JMX_REST_SERVICE_FLAG: This flag in the Menu options is to enable the REST API. If this is false, then the communication happens using via JMX, the old way of the plugin communication.

    3. JMX_REST_SERVICE_FLAG is true and JMX_HTTPSSL_FLAG false, the communication happens over the HTTP. JMX_REST_SERVICE_FLAG is true and JMX_HTTPSSL_FLAG true, the communication happens over the HTTPS.

    4. More details are available in respective Utilities FW product documentation.

  4. The WebLogic domain/Fusion middleware must be discovered. To do this, perform the following:

    • The WebLogic admin server must be started. Verify that it is by logging into the WebLogic console.

    • Discover the WebLogic domain and Fusion middleware using guided discovery. On the grid console, go to Setup, and then Add Targets, and then Add Targets Manually. Select the following options on the page:

      Selecting the Setup, Add Targets then the Add Targets Manually menu items initiates the discovery of the WebLogic domain and Fusion middleware.

    • Click Add Using Guided Process, enter the entries for the WebLogic admin server, then continue until the WebLogic domain/Fusion middleware is discovered.

      If WebLogic is configured with SSL, use the t3s protocol.

      Selecting the Add Using Guided Process option facilitates the data entry of the WebLogic admin server details and the discovery of the WebLogic domain or Fusion middleware.

To discover OUAF target environments:

  1. Log in to Enterprise Manager.
  2. Choose Setup, and then Add target, and then Configure Auto Discovery.

    Figure 7-1 Selecting Auto Discovery

    Start the environment discovery configuration by navigating to the Setup Discovery page.
  3. On the Setup Discovery page, click the host where discovery is to be run, then click the Discovery Modules button.

    Figure 7-2 Setup Discovery

    Select the host in which to run the discovery and the appropriate modules.
  4. Ensure that the Enterprise Manager for Oracle Utilities module is on the Discovery Module list.

    Figure 7-3 Verifying the module

    Ensure the appropriate discovery modules appear on the list.
  5. Once back on the Setup Discovery page, select the host again to enable the buttons at the top. When the desired host is selected, click the Discover Now button.

    Figure 7-4 Running the discovery

    After setting up the discovery details, initiate the discovery by clicking the Discover Now button.

    The Target Discovery (Agent Based) window opens.

  6. Click OK in the Discover Now dialog to confirm that you want to run the discovery.

    Figure 7-5 Confirming the discovery

    Start the discovery run.
  7. A confirmation dialog appears on successful discovery of the host. Click Close to dismiss the confirmation dialog.

    Figure 7-6 Host discovery confirmation dialog

    Click the Close button after a successful discovery run.