Supported Versions
Minimum Support Version: Oracle weblogic 12c

Introduction

WebLogic Server allows you to quickly develop and deploy reliable, secure, scalable and manageable applications. It manages system-level details so you can concentrate on business logic and presentation.

WebLogic domain is a fundamental administrative unit for WebLogic Server. It comprises one or more WebLogic Server instances with their resources, which are collectively managed and configured using a single Administration Server.

The WebLogic domain infrastructure consists of three parts:

  • Administration Server: Guides the actions of managed servers.
  • Managed Servers: Stand-alone servers ruled by the Administration Server.
  • Clusters: Clusters are groups of managed servers managed by the Administration Server.
Weblogic Server

WebLogic Server Domains are referred to as Managed Servers, in which Java Enterprise Solutions are deployed. These Managed Servers are grouped into clusters for load balancing and failover, especially for critical applications. Multiple WebLogic domains are also set up according to application boundaries, system administrator responsibilities and server’s geographical location. Alternatively you can set up a single domain to manage all WebLogic Server administration activities.

The most common WebLogic Server user types are:

  • Evaluator: Users who performs product evaluations
  • Installer: Users who installs and sets up the WebLogic Server environment
  • System Administrator: Users who administers WebLogic Server after it is installed
  • Developer/Engineer: Users who develop applications to run in the WebLogic Server environment.
Weblogic Server

Prerequisites

  • OpsRamp Classic Gateway 12.0.1 and above (or) OpsRamp next-gen gateway.
  • To access Weblogic Enterprise Server Api’s the user should Enable RESTful Management Services in Weblogic Admin Console Configurations.

Key Use cases

Discovery Use cases

  • It discovers the oracle weblogic application server components like weblogic domain, clusters, servers and its related applications and data sources. the following are the resource structure.

→ WebLogic Enterprise Server
     → WebLogic Clusters
     → WebLogic Servers
     → Weblogic Server Applications
     → WebLogic Server Datasources

  • Publishes relationships between resources to have a topological view and ease of maintenance.

Monitoring Use cases

  • Provides metrics related to job scheduling time and status etc,.
  • Concern alerts will be generated for each metric to notify the administrator regarding the issue with the resource.

Default Monitoring Configurations

WebLogic application has a default Global Device Management Policies, Global Templates, Global Monitors, and Global Metrics in OpsRamp. You can customize these default monitoring configurations as per your business use cases by cloning respective Global Templates, and Global Device Management Policies. OpsRamp recommends performing the below activity before installing the application to avoid noise alerts and data.

  1. Default Global Device Management Policies

    OpsRamp has a Global Device Management Policy for each Native Type of WebLogic Server. You can find those Device Management Policies at Setup -> Resources -> Device Management Policies, search with suggested names in global scope. Each Device Management Policy follows below naming convention:

    {appName nativeType - version}

    Ex: weblogic-server WebLogic Servers- 1 (i.e, appName = weblogic-server, nativeType = WebLogic Servers, version = 1)

  2. Default Global Templates

    OpsRamp has a Global Template for each Native Type of WebLogic Server. You can find those templates at Setup -> Monitoring -> Templates, search with suggested names in global scope. Each template follows below naming convention:

    {appName nativeType 'Template' - version}

    Ex: weblogic-server WebLogic Servers Template - 1 (i.e, appName = weblogic-server, nativeType = WebLogic Servers, version = 1)

  3. Default Global Monitors

    OpsRamp has a Global Monitors for each Native Type which has monitoring support. You can find those monitors at Setup -> Monitoring -> Monitors, search with suggested names in global scope. Each Monitors follows below naming convention:

    {monitorKey appName nativeType - version}

    Ex: WebLogic Servers Monitor weblogic-server WebLogic Servers 1 (i.e, monitorKey = WebLogic Servers Monitor, appName = weblogic-server, nativeType = WebLogic Servers, version = 1)

Configure and install the integration

  1. From All Clients, select a client
  2. Go to Setup > Integrations and Apps.
  3. Click Manage Apps.
    Notes:
    • If there are already installed applications, it will redirect to the INSTALLED APPS page, where all the installed applications are displayed.
    • If there are no installed applications, it will navigate to the ADD APP page.
Weblogic Server
  1. Click + ADD on the INSTALLED APP page. The ADD APP page displays all the available applications along with the newly created application with the version.
    Note: You can even search for the application using the search option available. Also you can use the All Categories option to search.
Weblogic Server
  1. Click ADD in the WebLogic Application Server application.
  2. In the Configurations page, click + ADD. The Add Configuration page appears.
  3. Enter the below mentioned BASIC INFORMATION:
FunctionalityDescription
NameEnter the name for the configuration.
WebLogic IP Address / Host NameProvide the WebLogic IP Address / Host Name.
PortPort

Note: By default 7001 is added.
CredentialsSelect the credentials from the drop-down list.

Note: Click + Add to create a credential.

Notes:

  • By default the isSecure checkbox is selected.
  • Select App Failure Notifications; if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.
  1. In the RESOURCE TYPE section, select:
    • ALL: All the existing and future resources will be discovered.
    • SELECT: You can select one or multiple resources to be discovered.
  2. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
  3. Click ADD.
Weblogic Server
  1. Now the configuration is saved and displayed on the configurations page after you save it.

    Note: From the same page, you may Edit and Remove the created configuration.
  2. Click NEXT
  3. In the Installation page, select an existing registered gateway profile, and click FINISH.
Weblogic Server

The application is now installed and displayed on the Installed Integration page. Use the search field to find the installed application.

Modify the Configuration

View the Weblogic Server details

The Weblogic Server integration is displayed in the Infrastructure > Resources > Server, select the relationship. You can navigate to the Attributes tab to view the discovery details, and the Metrics tab to view the metric details for Weblogic Server.

Weblogic Server
Weblogic Server
Weblogic Server

Supported metrics

Native Resource TypeMetric NameMetric Display NameUnitsDescription
WebLogic Server Datasourcesweblogic_server_datasource_activeConnectionsAverageCountActive Connections Average CountcountDisplays the average number of active connections in this instance of the data source. This value is only valid if the resource is configured to allow shrinking.
weblogic_server_datasource_activeConnectionsCurrentCountActive Connections Current CountcountDisplays the number of connections currently in use by applications.
weblogic_server_datasource_connectionDelayTimeConnection Delay Time (ms)msDisplays the average amount of time, in milliseconds, that it takes to create a physical connection to the database.
weblogic_server_datasource_connectionsTotalCountConnections Total CountcountDisplays the cumulative total number of database connections created in this data source since the data source was deployed.
weblogic_server_datasource_currentConnectionPoolCapacitycurrentConnectionPoolCapacitycountDisplays the current count of JDBC connections in the connection pool in the data source.
weblogic_server_datasource_failedReserveRequestCountFailed Reserve Request CountcountDisplays the cumulative, running count of requests for a connection from this data source that could not be fulfilled.
weblogic_server_datasource_failuresToReconnectCountFailures To Reconnect CountcountDisplays the number of times that the data source attempted to refresh a database connection and failed. Failures may occur when the database is unavailable or when the network connection to the database is interrupted.
weblogic_server_datasource_leakedConnectionCountLeaked Connection CountcountDisplays the number of leaked connections. A leaked connection is a connection that was reserved from the data source but was not returned to the data source by calling close().
weblogic_server_datasource_numberOfAvailableConnectionsNum AvailablecountDisplays the number of database connections that are currently idle and available to be used by applications in this instance of the data source.
weblogic_server_datasource_prepStmtCacheAccessCountPrep Stmt Cache Access CountcountDisplays the number of prepared and callable statements currently cached in the statement cache. Each connection in the connection pool has its own cache of statements. This number is the sum of the number of statements in the caches for all connections in the connection pool.
weblogic_server_datasource_waitingForConnectionCurrentCountWaiting For Connection Current Count (Threads Waiting for connection)countDisplays the number of connection requests waiting for a database connection.
weblogic_server_datasource_activeConnectionsPercentActive Connections in %%Displays the Active connections in Percentage.
weblogic_server_datasource_connectionPoolUtilizationConnection pool utilization%Displays the connection pool utilization in percentage.
WebLogic Server Applicationsweblogic_server_application_stateStateN/ADisplays the WebLogic Server Application State and provides the possible application state values are STATE_ACTIVE (1),STATE_FAILED (0),STATE_NEW (2),STATE_RETIRED (3),STATE_PREPARED (4),STATE_ADMIN (5),STATE_UPDATE_PENDING (6)
weblogic_server_application_healthStatusHealth StatusN/ADisplays the Health status of the WebLogic Server Application and provides the possible application health status values are HEALTH_OK (1),UNKNOWN (0),HEALTH_WARN (2),HEALTH_CRITICAL (3),HEALTH_FAILED (4) and HEALTH_OVERLOADED (5)
weblogic_server_application_openSessionsCurrentCountNumber of active sessionscountProvides a count of the current total number of open sessions in this module. Returns the current total number of open sessions in this component.
weblogic_server_application_openSessionsHighCountMaximum number of sessionscountProvides a count of the maximum number of sessions in this server.
weblogic_server_application_sessionsOpenedTotalCountTotal number of sessionscountProvides a count of the total number of sessions opened in this server.
weblogic_server_application_numberOfServletsNumber of servletscountProvides the total number of servlets
weblogic_server_application_executionAverageTimeExecution Time AveragemsDisplays the average amount of time all invocations of the servlet have executed since created.
weblogic_server_application_invocationTotalCountInvocation Total CountcountDisplays the total count of the times this servlet has been invoked.
weblogic_server_application_averageResponseTimeAverage Response TimemsAverage response time of an application is calculated by dividing the number of active requests generated between two consecutive time intervals (the time when the agent collects the data from the server), by the time taken for processing these requests.
weblogic_server_application_executionTimeTotalCurrent Client Processing TimemsAmount of time taken to execute the servlet during the last interval.
WebLogic Clustersweblogic_server_cluster_weblogicPluginEnabledweblogicPluginEnabledN/ADisplays the weblogic server cluster plugin status, provides the possible weblogic plugin values are false (0) and true (1)
WebLogic Serverweblogic_server_stateweblogic_serverStateN/ADisplays the state of the WebLogic Server and provides the possible server state values RUNNING (1),SHUTDOWN (0),STARTING (2),STANDBY (3),ADMIN (4),RESUMING (5) and FAILED_NOT_RESTARTABLE (6)
weblogic_server_helathStateweblogic_serverHelathStateN/ADisplays the Health status of the WebLogic Server and provides the possible server health status values: HEALTH_OK (1),UNKNOWN (0),HEALTH_WARN (2),HEALTH_CRITICAL (3),HEALTH_FAILED (4) and HEALTH_OVERLOADED (5).
weblogic_server_openSocketsCurrentCountopenSocketsCurrentCountcountDisplays the open sockets current count of the WebLogic Server.
weblogic_server_heapMemoryJVM Runtime: Heap Free CurrentBytesDisplays the heap memory that is available in the JVM heap in bytes.
weblogic_server_uptimeJVM Runtime: UptimemsDisplays the Server uptime value in milliseconds.
weblogic_server_heapFreePercentJVM Runtime: Heap Free Percent%Displays the percentage of the memory that is used.
weblogic_server_processCpuLoadProcess cpu load%Displays the process cpu load.
weblogic_server_completedRequestCountCompleted Request CountcountDisplays the number of completed requests in the priority queue.
weblogic_server_executeThreadIdleCountExecute Thread Idle CountcountDisplays the number of idle threads in the pool. This count does not include standby threads and stuck threads. The count indicates threads that are ready to pick up new work when it arrives.
weblogic_server_executeThreadTotalCountExecute Thread Total CountcountDisplays the total number of threads in the pool.
weblogic_server_hoggingThreadCountHogging Thread CountcountDisplays the threads that are held by a request right now. These threads will either be declared as stuck after the configured timeout or will return to the pool.
Note: The self-tuning mechanism will backfill if necessary.
weblogic_server_minThreadsConstraintsCompletedMin Threads Constraints CompletedcountDisplays the number of requests with minimum threads constraint picked up from out of order for execution immediately, since their minimum threads requirement were not met.
Note: This does not include the case where threads are idle during schedule.
weblogic_server_minThreadsConstraintsPendingMin Threads Constraints PendingcountDisplays the number of requests that should be executed now to satisfy the minimum threads requirement.
weblogic_server_overloadRejectedRequestsCountOverload Rejected Requests CountcountDisplays the number of requests rejected due to configured Shared Capacity for work managers have been reached.
weblogic_server_pendingUserRequestCountPending User Request CountcountDisplays the number of pending user requests in the priority queue. The priority queue contains requests from internal subsystems and users. This is just the count of all user requests.
weblogic_server_queueLengthQueue LengthcountDisplays the number of waiting requests in the queue.
weblogic_server_sharedCapacityForWorkManagersShared Capacity For Work ManagerscountDisplays the maximum amount of requests that can be accepted in the priority queue.
Notes:
  • a request with higher priority will be accepted in place of a lower priority request already in the queue even after the threshold is reached.
  • The lower priority request is kept waiting in the queue till all high priority requests are executed.
  • Further enqueues of the low priority requests are rejected right away.
weblogic_server_standbyThreadCountStandby Thread CountcountDisplays the number of threads in the standby pool. Threads that are not needed to handle the present workload are designated as standby and added to the standby pool. These threads are activated when more threads are needed.
weblogic_server_stuckThreadCountStuck Thread CountcountDisplays the number of stuck threads in the thread pool.
weblogic_server_throughputThroughputcountDisplays the mean number of requests completed per second.
weblogic_server_activeTransactionsTotalCountActive Transactions Total CountcountDisplays the number of active transactions on the server.
weblogic_server_transactionHeuristicsTotalCountTransaction Heuristics Total CountcountDisplays the number of transactions that completed with a heuristic status since the server was started.
weblogic_server_transactionLLRCommittedTotalCountTransaction LLR Committed Total CountcountDisplays the total number of LLR transactions that were committed since the server was started.
weblogic_server_transactionRolledBackTotalCountTransaction Rolled Back App Total CountcountDisplays the number of transactions that were rolled back due to an application error.
weblogic_server_transactionRolledBackResourceTotalCountTransaction Rolled Back Resource Total CountcountDisplays the number of transactions that were rolled back due to a resource error.
weblogic_server_transactionRolledBackSystemTotalCountTransaction Rolled Back System Total CountcountDisplays the number of transactions that were rolled back due to an internal system error.
weblogic_server_transactionRolledBackTimeoutTotalCountTransaction Rolled Back Timeout Total CountcountDisplays the number of transactions that were rolled back due to a timeout expiration.
weblogic_server_transactionTotalCountTransaction Total CountcountDisplays the total number of transactions processed. This includes all committed, rolled back, and heuristic transaction completions since the server was started.
weblogic_server_connectionsCurrentCountConnections Current CountcountDisplays the number of current connections to the WebLogic Server.
weblogic_server_connectionsHighCountConnections High CountcountDisplays the highest number of connections to this WebLogic Server since the last reset.
weblogic_server_connectionsTotalCountConnections Total CountcountDisplays the total number of connections made to this WebLogic Server since the last reset.
weblogic_server_JMSServersCurrentCountJMS Servers Current CountcountDisplays the current number of JMS servers that are deployed on this WebLogic Server instance.
weblogic_server_JMSServersHighCountJMS Servers High CountcountDisplays the highest number of JMS servers that were deployed on this WebLogic Server instance since this server was started.
weblogic_server_JMSServersTotalCountJMS Servers Total CountcountDisplays the total number of JMS servers that were deployed on this WebLogic Server instance since this server was started.
weblogic_server_invalidLoginAttemptsTotalCountServer Security Runtime: Invalid Login AttemptscountThis monitor returns the total number of invalid logins that have been attempted on this server instance.
weblogic_server_lockedUsersCurrentCountServer Security Runtime: Current Locked UserscountThis monitor returns the current number of locked users on this server instance.
weblogic_server_loginAttemptsWhileLockedTotalCountServer Security Runtime: Login Attempts While LockedcountThis monitor returns the total number of invalid logins that have been attempted on this server instance while a user was locked.
weblogic_server_unlockedUsersTotalCountServer Security Runtime: Unlocked UserscountThis monitor returns the total number of times a user of this server instance has been unlocked.
weblogic_server_userLockoutTotalCountServer Security Runtime: User LockoutcountThis monitor returns the total number of user lockouts that have occurred on this server instance.

Risks, Limitations & Assumptions

  • Application can handle Critical/Recovery failure notifications for below two cases when user enables App Failure Notifications in configuration:
    • Connectivity Exception
    • Authentication Exception
  • Application will not send any duplicate/repeat failure alert notification until the already existing critical alert is recovered.
  • Using metrics for monitoring the resources and generating alerts when the threshold values are breached.
  • Application cannot control monitoring pause/resume actions based on above alerts.
  • Macro replacement limitation (i.e, customization of threshold breach alert subject, description).
  • This application supports only Classic Gateway and NextGen Gateway. Not supported with Cluster Gateway.
  • Component level thresholds can be configured on each resource level.
  • No support of showing activity log and applied time.
  • No support for the option to get Latest snapshot metric.