1. Enable observability and management stack monitoring for Oracle E-Business Suite
  2. Get Started with the Deployment Process

Get Started with the Deployment Process

Deploying observability and management stack monitoring for E-Business Suite requires three major steps:

  1. Configure licensing for your chosen edition, Standard or Enterprise, and for any resources or compartments used in your deployment.
  2. Discover and promote the resources used in your deployment.
  3. Use the OCI command-line interface (CLI) to discover new resources, create required associations between Stack Monitoring resources, or refresh the entire topology.

Configure Licensing

Stack Monitoring offers two editions: Standard and Enterprise. The Standard Edition monitors on-premises and cloud-deployed applications and tech stacks, including WebLogic, Tomcat, Oracle Database, and hosts. The Enterprise Edition adds advanced features like Metric Extensions, performance baselines, anomaly detection, and OCI resource integration for enhanced monitoring.

In addition to these two editions, licenses must be configured either at the individual resource level or at the compartment level, as described below.

Note:

The steps for assigning licenses at either level are beyond the scope of this playbook. You can access the relevant procedures required for each assignment level, identified in the specific section, below, from "Explore More", elsewhere in this playbook.

Configure Licensing for Resource-Specific Features

Resource license assignment can done at the individual resource level during discovery or after discovery by using the Licensing UI. License changes applied to a composite apply to all children; that is, when applying Enterprise Edition License to a WebLogic Domain, all WebLogic Servers associated to the domain will also receive the Enterprise Edition.

During discovery, you can assign a license to the resource by selecting the corresponding radio button. You can also modify a resource license after a resource has been discovered by using the License UI. These procedures are described in "Licensing Assignment", in the Oracle Cloud Infrastructure documentation, which you can access from "Explore More".

Configure Licensing for Compartment-Specific Features

You can set the resource license auto-assignment to Enterprise or Standard for all newly resources discovered or promoted resources within a compartment. Configuring license auto-assignment is a convenient way to automatically assign a license instead of applying it on a per resource instance basis. Additionally, you can enable or disable enterprise extensibility for an entire compartment.

Procedures for configuring licensing for compartment-specific features are described in "Licensing Assignment", in the Oracle Cloud Infrastructure documentation, which you can access from "Explore More".

Discover and Promote Resources for Oracle E-Business Suite

To monitor resources by using Stack Monitoring, you must first discover and promote these resources. Promotion prepopulates information related to the resource. You should validate this information to make sure that it is correct. The prerequisites and input parameters for promotion are the same as those for user-initiated discovery.

Note:

The steps for discovering and promoting resources are beyond the scope of this playbook. You can access the relevant procedures required for each assignment level, identified in the specific section, below, from "Explore More", elsewhere in this playbook.
Before you can discover and promote these resources, you need to meet the following prerequisites:
  • Configure MBeans on Oracle WebLogic Servers.
  • Verify collection of Forms sessions data.
  • Set up the DNS in an E-Business Suite environment.
  • Add the database used by the E-Business Suite application.
  • Meet the E-Business Suite database monitoring requirements for Stack Monitoring.

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. The procedure fior running the script and associated details are beyond the scope of this playbook. See "Configure MBeans on Oracle WebLogic Servers" in the Oracle Cloud Infrastructure documentation, which you can access from "Explore More".

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 steps described below. 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 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 E-Business Suite user opened a database session.
Do the following:
  1. Log in to E-Business Suite.
  2. From the user interface, navigate to System Administrator, click Profile, and then 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.

Set Up DNS in an Oracle E-Business Suite Environment

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

Meet Oracle E-Business Suite Database Monitoring Requirements for Stack Monitoring

You need to discover the Oracle database used to monitor the E-Business Suite database before discovering the E-Business Suite application. If the database is discovered first, it will be automatically associated with the EBS application once the E-Business Suite application discovery completes. If the E-Business Suite application discovery is performed before the database has been discovered, you'll need to manually create the association .

Monitoring E-Business Suite requires specific privileges to access the E-Business Suite schema. The setup differs depending on type of database (non-container database versus container database and pluggable database) used as your E-Business Suite datastore. Stack Monitoring supports the use of the E-Business Suite schema owner, typically APPS, as the database credentials when discovering E-Business Suite. You should create a monitoring user with privileges limited to just those necessary to monitor an E-Business Suite application. You can use the same database user to monitor both the Oracle database containing the E-Business Suite schema and the E-Business Suite application. Steps to create a database monitoring user can be found in MOS Note: 2857604.1, "Creating the Oracle Database Monitoring Credentials for Oracle Cloud Infrastructure Database Management, Operations Insights and Stack Monitoring", which you can access from "Explore More", elsewhere in this playbook.

Update Application Topology

You can use the OCI Command Line Interface (CLI) to discover new resources, create required associations between Stack Monitoring resources, or refresh the entire topology. Specifically, you can use CLI commands to create associations between the database and the application, such as E-Business Suite or PeopleSoft.

For E-Business Suite, updating application topology requires these tasks:
  • Update E-Business Suite topology.
  • Refresh E-Business Suite instances
  • Refresh the Weblogic domain.

Update Oracle E-Business Suite Topology

When an E-Business Suite instance is discovered, both E-Business Suite and WebLogic resources are also discovered. Database discovery has to be done separately. If the database is discovered first and then E-Business Suite is discovered later, the association of type uses will be automatically created between the E-Business Suite resource and the database resource once E-Business Suite discovery completes. Here, E-Business Suite resource refers to a Stack Monitoring resource type ebs_instance and database resource refers to Stack Monitoring resource type oci_oracle_db or oci_oracle_pdb.
If the EBS is discovered prior to database discovery, you can update the topology one of two ways.
  • Create an association between E-Business Suite instance and database resources.
  • Refresh E-Business Suite topology

Procedures for these update techniques are beyond the scope of this playbook; however, you can find more details in "EBS Topology", which you can access from "Explore More", elsewhere in this playbook.

Refresh Oracle E-Business Suite Instances

Refreshing an E-Business Suite instance results in the refresh of a number of Stack Monitoring resource types, as well as the underlying Weblogic Domain resources.

The Stack Monitoring resources refreshed are:
ebs_instance
oracle_ebs_conc_mgmt_service
oracle_ebs_cp_node
oracle_ebs_forms_system
oracle_ebs_wf_group
oracle_ebs_wf_agent_lsnr
oracle_ebs_wf_bkgd_engine
oracle_ebs_wf_notification_mailer

You can refresh an E-Business Suite instance by using the discovery-job createfrom the OCI command-line interface or from the homepage of the resource. For more information on these techniques, see "EBS Refresh", which you can access from "Explore More".

Refresh the WebLogic Server Domain

When you refresh the WebLogic Server domain, these Stack Monitoring resources are also refreshed: 

weblogic_domain
weblogic_j2eeserver
weblogic_cluster
oracle_soainfra
oracle_mft
oracle_http_server
oracle_oam
oracle_oam_cluster
oracle_oim
oracle_oim_cluster
Use the OCI CLI command discovery-job create to refresh the WebLogic domain. If you want to delete a resource during the refresh operation, add the allow_delete_resources property to the payload; for example:
oci stack-monitoring discovery-job create  --compartment-id "Compartment_OCID" --discovery-type REFRESH --discovery-details file:///tmp/weblogic_refresh_dev.json

Where Compartment_OCID is the compartment ID.

For more information, see "Weblogic Domain Refresh" in the Oracle Cloud Infrastructure documenation, which you can access from "Explore More".