Resource Discovery

Promote to Full Monitoring of Auto-discovered Resources

Some resources types can be automatically discovered if you have enabled the Resource Discovery and Monitoring features of OS Management Service. After discovery, basic monitoring for these resources automatically starts. To enable full monitoring of these resources, you need to take it through the promote to full monitoring process.

Promotion to full monitoring involves specifying additional identifying parameters and monitoring credentials in order to compete the discovery and fully monitor the resource.

Promotion to full monitoring is supported for the following resource types:

  • Oracle Database
  • WebLogic Server

Promotion to full monitoring is currently not supported for these other types:

  • Listener
  • Oracle HTTP Server
  • Apache Server
  • Tomcat

The prerequisites and input parameters for promotion are the same as the user initiated discovery.

Note

Promotion, unlike discovery, pre-populates information related to the resource. Be sure to validate this information and make sure that it is correct.

User-Initiated Discovery

You can initiate resource discovery from the Stack Monitoring UI. To access Stack Monitoring, sign in to the Oracle Cloud Infrastructure Console and then access Stack Monitoring via the Oracle Cloud Infrastructure Console main menu. Open the navigation menu, click Observability & Management. Under Application Performance Monitoring, click Stack Monitoring.

  1. From the left pane, under Resources, click Resource Discovery. The Resource Discovery page displays.
  2. Click Discover New Resource. The Resource Discovery region displays.
  3. Select a resource type from the Resource Type drop-down menu.

    You can select from the following resource types:

  4. Enter the resource type discovery details.
  5. Click Discover New Resource. A new resource discovery job is created and is shown in the table.

Oracle Database/Pluggable Database

Prerequisites

You can discover external databases (outside OCI) using the Stack Monitoring service. The Stack Monitoring service supports non-container, container (CDB), and pluggable (PDB) Oracle Databases that use the following Oracle Database software versions: 11gR2, 12cR1, 12cR2, 18c, and 19c. Stack Monitoring can be used with both single-instance Oracle Databases and Oracle RAC instances.

Note

Prior to discovering a database within Stack Monitoring, ensure you have access to the monitoring user, DBSNMP. Before discovering a PDB, you must first discover the container database.

Note about databases configured with older password versions

For databases that are configured to use password version less than 12 (SQLNET.ALLOWED_LOGON_VERSION < 12 ), such as certain E-Business Suite databases, follow these additional steps to configure the Management Agent to communicate with the database using older password versions by setting an appropriate SQLNET.ALLOWED_LOGON_VERSION value in the agent configuration.

These instructions apply to the agent running on-premises:

  1. Modify this file /opt/oracle/mgmt_agent/agent_inst/config/emd.properties to add the property:
    dbaas.ALLOWED_LOGON_VERSION = 8 

    Values can be 8 / 10 / 11 /12 / 12a depending on the allowed login version you require. For E-Business Suite setups, a value of 8 works for both login versions 8 and 10.

  2. Restart the agent.
    sudo systemctl restart mgmt_agent

These instructions apply to the agent running on OCI Compute:

  1. Modify the file /var/lib/oracle-cloud-agent/plugins/oci-managementagent/polaris/agent_inst/config/emd.properties to add this property:
    dbaas.ALLOWED_LOGON_VERSION = 8

    Values can be 8 / 10 / 11 /12 / 12a depending on the allowed login version you require. For E-Business Suite setups, a value of 8 works for both login versions 8 and 10.

  2. Restart the agent.
    sudo systemctl restart oracle-cloud-agent

Discovery Input

Input field Description

Database Credentials for Monitoring

.
  • Username
Username of the Oracle Database monitoring credentials. (DBSNMP)
  • Password
Password of the Oracle Database monitoring credentials.
  • Role
Database role of the database monitoring user (Normal or SYSDBA).
DNS hostname or SCAN Name Domain Name System (DNS), or Single Client Access Name (SCAN) for the database.
Management Agent Management Agent monitoring the host on which the database is installed.
Resource Name Name of the database.
Port Port used by the database outside of Oracle Cloud Infrastructure for database connections.
Service Name Service name for the database outside of Oracle Cloud Infrastructure that will be used by the connection.
Select CDB Container DB that contains the Pluggable DB. This field only applies to Pluggable DB.

Oracle WebLogic Domain

Prerequisites

To enable monitoring of a Oracle WebLogic Server (WLS), use a WebLogic user with at least the Monitor role. The user can also have Operator or Administrator roles, which include the Monitor role.

Note

If you are not using SSL, the following prerequisites do not apply.

If you have enabled the Oracle WebLogic Server with SSL, you must export the certificate from its keystore and import it in the Management Agent KeyStore. For more information about configuring SSL in WebLogic Server, see Configuring SSL.

Import TrustStore to the Management Agent

  1. Export the certificate from the WLS instance JMX SSL keystore to the Management Agent's truststore. For example, on a UNIX host:

    keytool -exportcert -alias <alias of WLS SSL key> -file <Exported Cert Name> -keystore <path to the WLS SSL Keystore>.keystore -storepass <WLS SSL Keystore password> -rfc
  2. Import the WLS instance JMX SSL keystore to the Management Agent's truststore:

    keytool -importcert -noprompt -alias <alias agent's truststore key> -file <Exported Cert Name>.cer -keystore AgentTrust.jks -storepass <Agent truststore password, default is "welcome">
  3. Copy Management Agent's TrustStore and update its permissions

    Identify Management Agent readable secure location on the agent host, e.g. <secure_readable_dir>

    cp <path_to>/AgentTrust.jks <secure_readable_dir>/

    On OCI Compute:

     sudo chown oracle-cloud-agent:oracle-cloud-agent <secure_readable_dir>/AgentTrust.jks

    On on-premises Compute:

    sudo chown mgmt_agent:mgmt_agent <secure_readable_dir>/AgentTrust.jks
  4. Use the full TrustStore path, e.g. <secure_readable_dir>/AgentTrust.jks in the "TrustStore Path" of Resource Discovery if WebLogic Domain with T3S and "JKS" as the "TrustStore Type".

Configure MBeans on Oracle WebLogic Servers

To collect the JVM performance metrics from platform MBeans, the MBeans must be made accessible through the runtime MBeanServer. Activate MBeans by logging in to your Oracle WebLogic Server and verify the activation by running the WLST script:

  1. Activate MBeans on Oracle WebLogic Servers

    Activate MBeans by accessing each Oracle WebLogic Server by logging into it or from the WebLogic console as follows:

    • Log in to your Oracle WebLogic Server:

      Follow the user actions in the WebLogic Scripting Tool session demostration at Activating Platform MBeans on WebLogic Server 9.x to 10.3.2 versions in Enterprise Manager Cloud Control Middleware Management Guide.

    • Access your WebLogic console:

      Navigate to Domain > Configuration > General page > Advanced options. Select the Platform MBean Server Used check box.

    If MBeans are not registered after you’ve followed the above steps, then start the Oracle WebLogic Servers with the following system property:

    -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
  2. Verify the Activation of MBeans

    To verify if MBeans is successfully activated, run the WLST script that’s available at Using the Platform MBean Server in Fusion Middleware Developing Custom Management Utilities With JMX for Oracle WebLogic Server. The WLST script demonstrates how to use the Platform MXBeans to monitor the resources of a running Oracle WebLogic Server domain.

    Ensure that MBeans are registered under java.lang.

WebLogic Discovery Input

Input field Description
Resource Name Name of the WebLogic Domain.
Administration Server Host The fully-qualified host name where the WebLogic Administration Server is installed.
Administration Server Port The port used for WebLogic Administration Server (Console).
Protocol Protocol used for the WebLogic Server. The possible values are t3 and t3s. If you select t3s, TrustStore Path and TrustStore Type fields appear under WebLogic User for Monitoring.
Management Agent Management Agent installed on the host where the WebLogic Administration Server is installed.

WebLogic User for Monitoring

.
  • Username
WebLogic Server username.
  • Password
WebLogic Server user password.
  • TrustStore Path (t3s protocol)
Fully qualified path to the TrustStore file used to store public keys of trusted servers.
  • TrustStore Type (t3s protocol)
Type of the TrustStore used for CA certificate management when establishing an SSL connection. Specify either: JKS or PKCS12. If the TrustStore type is not specified, the default TrustStore type, JKS, is used.

E-Business Suite

Prerequisites

  1. Configure MBeans on Oracle WebLogic Servers
  2. Verify Collection of Forms Sessions Data
  3. Set Up DNS in an Oracle E-Business Suite Environment
  4. Add the Database used by the E-Business Suite application.

    If you haven't already done so, add the database that will be used for the E-Business Suite application. Refer to Oracle Database/Pluggable Database (Discovery)

  5. E-Business Suite Database Monitoring Requirements for Stack Monitoring

Verify Collection of Forms Sessions Data

Verify the collection of forms sessions data to view it later in the Forms System resource metrics by performing the following task. This is in addition to the steps performed in Oracle WebLogic Domain (Configure MBeans on Oracle WebLogic Servers). If this step is not configured, some of the Forms System metrics will not be collected.

When you log in to Oracle E-Business Suite, the system creates a user session in the database identified by a unique session ID (SID) by using the APPS schema credential. Each database session is associated with an Oracle E-Business Suite application user. This enables linking the database session with the application user for troubleshooting purposes. Using a Forms session, you can determine how the Oracle E-Business Suite user opened a database session.

  1. Log in to your Oracle E-Business Suite.
  2. From the user interface, navigate to System Administrator > Profile > System.
  3. Ensure that the value of Sign-On: Audit Level is set to FORM. Set this at the site level.
  4. Ensure that the value of AuditTrail: Activate is set to YES.

Save the changes.

Set Up DNS in an Oracle E-Business Suite Environment

The Oracle E-Business Suite hosts must be able to detect one another on the network. For example, in the UNIX environment, the DNS servers are configured in the file /etc/resolv.conf on each host.

To verify that the DNS servers are configured correctly, run the command:

nslookup any_publicDomain_hostname

E-Business Suite Database Monitoring Requirements for Stack Monitoring

Monitoring E-Business Suite requires specific privileges to access the EBS schema. The setup differs depending on type of database (Non-Container DB versus Container DB and Pluggable DB) used as your EBS datastore.

Pluggable DB

Stack Monitoring supports the use of the EBS schema owner, typically APPS, as the database credentials when discovering EBS. If the schema name is different in your setup, then replace APPS with the actual schema owner name when performing the EBS discovery.

Non-container DB

Stack Monitoring supports both the use of the schema owner, typically APPS, or DBSNMP. When monitoring E-Business Suite with a user other than the schema owner, it is necessary to grant additional privileges to the monitoring user, DBSNMP.

The specific privileges are defined in the code below. It assumes the EBS schema name of APPS. If the schema name is different in your setup, then replace APPS with the actual schema name in the following code. Replace <USER> with the database monitoring user, DBSNMP. Ensure the grants are applied to the DBSNMP user within non-container database where the APPS schema resides.

GRANT SELECT ON APPS.FND_OAM_CONTEXT_FILES TO <USER>;
GRANT SELECT ON APPS.FND_PRODUCT_GROUPS TO <USER>;
GRANT SELECT ON APPS.FND_CONC_PROG_ONSITE_INFO TO <USER>;
GRANT SELECT ON APPS.FND_CONCURRENT_PROGRAMS_VL TO <USER>;
GRANT EXECUTE ON APPS.FND_OAM_EM TO <USER>;
GRANT SELECT ON APPS.FND_CONCURRENT_REQUESTS TO <USER>;
GRANT SELECT ON APPS.FND_APPLICATION_VL TO <USER>;
GRANT SELECT ON APPS.FND_CONCURRENT_QUEUES TO <USER>;
GRANT SELECT ON APPS.FND_LOOKUPS TO <USER>;
GRANT SELECT ON APPS.FND_CONCURRENT_WORKER_REQUESTS TO <USER>;
GRANT SELECT ON APPS.FND_CONCURRENT_QUEUES_VL TO <USER>;
GRANT SELECT ON APPS.FND_OAM_FNDUSER_VL TO <USER>;
GRANT SELECT ON APPS.FND_FORM_SESSIONS_V TO <USER>;
GRANT SELECT ON APPS.FND_CP_SERVICES TO <USER>;
GRANT SELECT ON APPS.FND_CONCURRENT_PROCESSES TO <USER>;
GRANT SELECT ON APPS.FND_SVC_COMPONENTS TO <USER>;
GRANT SELECT ON APPS.FND_LOG_MESSAGES TO <USER>;
GRANT SELECT ON APPS.FND_CONCURRENT_PROGRAMS TO <USER>; 
GRANT SELECT ON APPS.FND_CONFLICTS_DOMAIN TO <USER>; 
GRANT SELECT ON APPS.FND_ORACLE_USERID TO <USER>; 
GRANT SELECT ON APPS.FND_APP_SERVERS TO <USER>; 
GRANT SELECT ON APPS.FND_NODES TO <USER>;
GRANT SELECT ON APPS.ICX_SESSIONS TO <USER>;
GRANT SELECT ON APPS.FND_USER TO <USER>;
GRANT SELECT ON APPS.FND_RESPONSIBILITY TO <USER>;
GRANT EXECUTE ON APPS.FND_PROFILE TO <USER>;
GRANT SELECT ON APPS.WF_DEFERRED TO <USER>;
GRANT SELECT ON APPS.WF_NOTIFICATION_IN TO <USER>;
GRANT SELECT ON APPS.WF_NOTIFICATION_OUT TO <USER>;
GRANT INHERIT PRIVILEGES ON USER "<USER>" TO "APPS";

E-Business Discovery Input

Input field Description
Resource Name Name of the E-Business Suite instance.
Version Version of E-Business Suite (12.1 or 12.2). If 12.2 is selected, E-Business Suite WebLogic Server and WebLogic Administration Server Credentials regions are displayed.
E-Business Suite Database .
  • Host Name
Host on which the external database is installed
  • Port
Port used by the database for database connections.
  • Service Name
Server name of the database used for database connections.

Database Credentials

.

  • Username

Database user who has the necessary privileges on the underlying views (e.g. DBSNMP, APPS).

Note

For Pluggable DBs, this should be the EBS schema owner.
  • Password
Database user password.
  • Database Role
Role of the database user (NORMAL, SYSDBA, or SYSASM)
E-Business Suite WebLogic Server (E-Business Suite 12.2) .
  • Host Name
Name of the host where the WebLogic Administration Server is installed.
  • Port
Port used for WebLogic Administration Server (Console).
  • Protocol
Remote Method Invocation (RMI) protocol: t3 or t3s. If you select t3s, the TrustStore Path and TrustStore Type fields appear under WebLogic User for Monitoring.
WebLogic Administration Server Credentials (E-Business Suite 12.2) .
  • Username
WebLogic Administration Server user.
  • Password
WebLogic Administration Server user password.
  • TrustStore Path (t3s protocol)
Path to the TrustStore file used to store public keys of trusted servers.
  • TrustStore Type (t3s protocol)
Type of the TrustStore used for CA certificate management when establishing an SSL connection. If the TrustStore type is not specified, the default TrustStore type, JKS, is used.
Management Agent Management Agent monitoring the host where E-Business Suite is installed.