MetaSolv Solution - How to Configure WebLogic Server Data Sources to Identify/Monitor JDBC Connections on the Oracle Database (Doc ID 2018598.1)

Last updated on JANUARY 17, 2017

Applies to:

Oracle Communications MetaSolv Solution - Version 6.2.0 and later
Information in this document applies to any platform.

Goal

Applications hosted on middleware like Oracle WebLogic Server use JDBC data source connection pools to manage database transactions. These JDBC resources often times connect to the database with an underlying user ID that does not represent a physical end user of the application. For Oracle Communications MetaSolv Solution, those user IDs are APP_MSLV, APP_API, and APP_INT.

This presents troubleshooting challenges when attempting to monitor end user activity on the database. These challenges are amplified by environments having multiple WebLogic server instances hosted on a single machine. This document provides information to facilitate more effective troubleshooting of the Oracle Communications MetaSolv Solution.

The diagram below represents a basic Oracle WebLogic Integration Server domain with a single managed server instance hosted on a single machine.  Directly below the diagram is a query followed by explanations of various results.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms