Chapter 9.  Integrating Oracle Enterprise Manager (OEM) with Oracle NoSQL Database

Table of Contents

Importing and Deploying the EM Plug-in
Adding NoSQL Database Targets
Components of a NoSQL Store
Store Targets
Store Page
Storage Node Page
Shard Page
Replication Node Page

The monitoring of a store in Oracle NoSQL Database (Oracle NoSQL Database) can be done through its native command-line interface (CLI). The native web-based Admin Console also does monitoring, and the monitoring data is available through Simple Network Management Protocol (SNMP) and Java Management Extensions (JMX) interfaces - allowing customers to build their own monitoring solutions. For more information, see Standardized Monitoring Interfaces .

In this current release, the integration of Oracle’s Enterprise Manager (OEM) with Oracle NoSQL Database (Oracle NoSQL Database) provides a graphical management interface tool to discover and monitor a deployed store.

The integration of Oracle NoSQL Database with OEM primarily takes the form of an EM plug-in. The plug-in allows monitoring through Enterprise Manager of NoSQL Database store components, their availability, performance metrics, and operational parameters. The current 12.1.0.9.0 version of the plug-in is compatible with Oracle Enterprise Manager Cloud Control 12c Release 3 (Version 12.1.0.3.0).

Note

For a Storage Node Agent (SNA) to be discovered and monitored, it must be configured for JMX. JMX is not enabled by default. You can tell whether JMX is enabled on a deployed SNA issuing the show parameters command and checking the reported value of the mgmtClass parameter. If the value is not oracle.kv.impl.mgmt.jmx.JmxAgent, then you need to issue the change-parameters plan command to enable JMX.

For example:

plan change-parameters -service sn1 -wait \
-params mgmtClass=oracle.kv.impl.mgmt.jmx.JmxAgent

For more information, see Standardized Monitoring Interfaces .

Also, the EM agent process must have read permission on the contents of $KVROOT.

Importing and Deploying the EM Plug-in

Follow the steps below to import and deploy the EM plug-in:

  1. Import the file (.opar) into the Enterprise Manager before deploying it. The plug-in is delivered to the user as a file inside the release package: lib/12.1.0.9.0_oracle.nosql.snab_2000_0.opar

    For more information, see Importing Plug-In Archives section (15.4.4.4) of the Oracle Enterprise Manager Cloud Control Administrator's Guide, which you can find here: http://docs.oracle.com/cd/E24628_01/doc.121/e24473/plugin_mngr.htm#autoId27

  2. Copy the .opar file to the host where Oracle Management Service (OMS) is running, and run the command:

    Example:

    $emcli import_update 
    -file=/home/guy/12.1.0.9.0_oracle.nosql.snab_2000_0.opar -omslocal
  3. Deploy the plug-in to the Oracle Management Service (OMS). You can deploy multiple plug-ins to an OMS instance in graphical interface or command line interface. For more information, see Deploying Plug-Ins to Oracle Management Service section (15.4.5) of the Oracle Enterprise Manager Cloud Control Administrator's Guide, which you can find here: http://docs.oracle.com/cd/E24628_01/doc.121/e24473/plugin_mngr.htm#autoId28

    CLI Example:

    $emcli deploy_plugin_on_server -plugin
    =oracle.nosql.snab:12.1.0.9.0 -sys_password=sysmanpass
  4. Deploy the plug-in to the EM Agents where NoSQL Database components are running. For more information, see step 4, Deploying Plug-Ins on Oracle Management Agent section (15.4.7) of the Oracle Enterprise Manager Cloud Control Administrator's Guide, which you can find here: http://docs.oracle.com/cd/E24628_01/doc.121/e24473/plugin_mngr.htm#autoId33

    CLI Example:

    $emcli deploy_plugin_on_agent -agent_names=agent1.somewhere.com:3872;
    agent2.somewhere.com:3872 -plugin=oracle.nosql.snab:12.1.0.9.0

Note

The plugin components are now installed and can be configured.