2 Discovering Exalytics Targets

This section provides instructions for discovery of the Oracle Exalytics In-Memory System and Machine through Enterprise Manager Cloud Control 12c.

The following sections describe how to discover the Exalytics In-Memory System and Machine and other supported targets:

Note:

The Oracle TimesTen In-Memory Database is part of most Exalytics systems. See the Oracle® Enterprise Manager System Monitoring Plug-in for Oracle TimesTen In-Memory Database User's Guide for complete installation, discovery, and configuration details:

http://docs.oracle.com/cd/E24628_01/timesten.121/e28645/toc.htm

2.1 Prerequisites

Complete the following prerequisites before beginning the discovery process:

2.1.1 Create the em-context.info File

Before the Exalytics host can be discovered by Enterprise Manager Cloud Control, there are some configuration step that must first be completed and the em-context.info file, which provides Enterprise Manager with the system identifier of your Exalytics System, must be created. To make sure this file is available:

  1. Log on to Oracle Integrated Lights Out Manager (ILOM) and select ILOM Administration, then Identification, and then System Information. Ensure that the SP System Identifier value is populated with a unique value, such as Oracle Exalytics X2-2 AK00026925.
  2. Log on to the same Oracle Exalytics machine where you extracted the Oracle Exalytics X2-4 Configuration Utilities v 1.0.0.5.
  3. As root, update the permissions to make the configure_for_emcc.sh script executable: 
    # chmod +x configure_for_emcc.sh
  4. As root, run the configure_for_emcc.sh script to create the file: 
    # ./configure_for_emcc.sh
  5. Review the output and ensure that the contents of the /var/exalytics/info/em-context.info file correctly displays the system identifier for the Oracle Exalytics machine. The system identifier should be identical to the system identifier you saw in Step 1.
  6. Once created verify that the file exists in the /var/exalytics/info directory. As root, run: 
    # cat /var/exalytics/info/em-context.info

    The output of this command would look like this:

    system_identifier = Oracle Exalytics 1229FMJ01K

    Note:

    The output from this command will display differently for older Exalytics images.

  7. Verify that the agent user has permissions to read the file.

2.1.2 Prerequisites for Virtualized Exalytics

Before proceeding to discovery, verify that the following prerequisites are met for your virtualized Exalytics Machine:

2.1.2.1 Export NFS Directory

A directory should be NFS exported before it can be mounted on other host. Follow the steps below as the root user:

  1. Edit the exports file: 
    vi /etc/exports
  2. Add the following line to the exports file: 
    <location given during swlib nfs creation>  *(rw,sync)
  3. Run the following commands 
    service nfs restart
service portmap restart
showmount -e <ip addr of source>

    The last command (showmount -e) shows the location exported.

  4. Save the exports file.

2.1.2.2 Other Virtualized Exalytics Machine Prerequisites

2.1.3 Discover Fusion Middleware Domain

Generally, Oracle Fusion Middleware domains do not remain static. Instead, membership in the domain changes regularly, for example: 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 the domains, which have been configured as managed targets. However the application does provide the ability to discover and uptake new or modified domain members.

For details about discovering Fusion Middleware domains (including new, modified, and multiple domains), see the "Discovering Middleware Targets" chapter of the Oracle® Enterprise Manager Cloud Control Getting Started with Oracle Fusion Middleware Management:

http://docs.oracle.com/cd/E25178_01/install.1111/e24215/fmw_discovery.htm

2.1.3.1 Automatic Discovery

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.

  1. From the Targets menu, select Middleware.

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

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

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

2.1.3.2 Manual Discovery

You can use Cloud Control to check a domain for new or modified members on a periodic basis:

  1. From the Targets menu, select Middleware.
  2. Click on the WebLogic Domain you want to enable the job for in the Middleware home page.
  3. From either the Farm or WebLogic Domain menu, select Refresh WebLogic Domain. The Refresh WebLogic Domain dialog opens.
  4. Click Continue. Cloud Control will search the domain for new and modified targets.
  5. 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.

  6. 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.
  7. Click Close in the processing window when finished. The Results page displays the targets and Agent assignments.
  8. 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.

2.1.4 Prerequisites for Cisco Monitoring

Cisco monitoring in 13c target uses the System Infrastructure Plug-in, where the Agent requires SSH access to Cisco Switch.

12c Target Type: Can monitor Cisco switch via SNMP. SSH access is not mandatory.

13c Target Type: SSH access information is required when adding this target type.

  • You will need to have your Cisco IOS and SNMP credentials available.

2.2 Discovering the Exalytics System Target

An Exalytics system consists of multiple Exalytics machines that are clustered. For monitoring, there are two targets in Enterprise Manager:

  • The Exalytics Machine target that represents one physical machine.

  • The Exalytics System target which represents multiple machines that are clustered and need to be monitored as a whole.

Regardless of the target type to be monitored, you will always select an Exalytics System for discovery - even if there is only one Exalytics Machine.

To discover an Exalytics System target:

  1. From the Targets menu, select Systems as shown in Figure 2-1:

    Figure 2-1 Targets Menu


    img/GUID-CFC0C4DA-BDA0-48DB-AB64-3DF41E90D0A1-default.gif

  2. On the Systems page, click Add and select Exalytics System, as shown in Figure 2-2.

    Figure 2-2 Add Exalytics System


    img/GUID-BA169ACA-11BD-4FAC-AAD0-A1E17AE3A462-default.gif

  3. On the Exalytics System, begin the discovery of the Exalytics System. Click Add Machine (Add Machine button) and provide the following information:

    • Machine Name

    • Agent

    • Deployment Type

    • Host Name

    • Bare Metal/Oracle Virtual Server Username and Password

    • IP Address/Hostname

    • ILOM Credentials Username and Password

  4. Click Next.
  5. A confirmation will appear as the discovery of the Exalytics System progresses. Once complete, click Close.
  6. Click Add Targets to complete the discovery process.