Skip to main content
Version: NG-2.14

IBM WAS

Introduction

IBM WebSphere Application Server (WAS) is a comprehensive and robust application server designed to support Java applications, enterprise applications, and web services. It provides a flexible and scalable platform for deploying, managing, and running applications. As an integral part of IBM's middleware suite, WebSphere Application Server offers support for Java EE (Enterprise Edition) standards, making it ideal for complex, large-scale enterprise applications. It enables seamless integration with databases, messaging systems, and other technologies, offering high availability, security, and performance, making it a key solution for businesses in various industries.

Getting Started

Compatibility

The IBM WAS O11ySource is compatible with all versions equal to greater than 8.5.5.

Data Collection Method

vuSmartMaps collects health and performance data for IBM WebSphere Application server using VuNet's vuAppAgent. This agent collects data based on the source configuration.

Prerequisites

Dependent Configuration

To configure this O11ySource, create a 'credential' of type 'user' under the 'Definition' tab.

Inputs for Configuring Data Source

  • IBM WAS Server: The IP Address/FQDN of the IBM WAS server. This field is the key to identify each server you add here.

  • Port: SOAP connector port for Deployment Manager.

  • Security: Select if administrative security to be included/excluded from monitoring.

  • SSL: Select if SSL Certificate to be included/excluded from monitoring

  • Client Trusted Keystore file Path: Client Trusted Keystore file. This file would be in (WAS_HOME)/profiles/(DMGR_NAME)/etc. For example, DummyClientTrustFile.jks

  • Client Trusted Keystore password: Client Trusted Keystore password. By default, this is “WebAS”.

  • Client Keystore file path: Client Keystore file. This file would be in (WAS_HOME)/profiles/(DMGR_NAME)/etc/. For example, DummyClientKeyFile.jks.

  • Client Keystore password: Client Keystore password. By default, this is “WebAS”.

  • Credential: Select the credential.

  • Period [in seconds]: How frequently data is gathered. The period should be between 60 seconds – 3000 seconds.

Firewall Requirement

To collect data from this O11ySource, ensure the following ports are opened:

Source IPDestination IPDestination PortProtocolDirection
IP address of the IBM WebSphere Application serverData Collector End Point8879*TCPInbound

*Before providing the firewall requirements, please update the port based on the customer environment.

Configuring the Target

IBM WebSphere metrics are collected using VuNet's VuApp agent, which connects to WebSphere's monitoring endpoints. The server provides monitoring capabilities via the administrative console or through JMX (Java Management Extensions) metrics.

To check whether the monitoring feature is enabled, verify the settings in the administrative console. Ensure that the WebSphere Performance Monitoring Infrastructure (PMI) is enabled using the following admin console steps:

  • Go to Monitoring and Tuning > Performance Monitoring Infrastructure in the Admin Console.
  • Select Servers, then select the Currently monitored statistic set (None, Basic, Extended, All, or Custom).
  • Choose metrics such as response times, thread pools, garbage collection, and memory usage, then click Apply.

Configuration Steps

Configure Metrics and Logs Collection from IBM WebSphere Application Server

  • Enable the IBM WAS O11ySource
  • Select the Sources tab and press the + button to add a new WebSphere host to be monitored.
  • Set up metrics collection configurations for WebSphere. In the configuration screen, specify the desired metrics you wish to collect from your WebSphere server.
  • After configuring, click Save and Continue to proceed with downloading the agent.
  • The following packages will be available for download based on the OS: Download <OS> vuAppAgent Installation Binary - Downloads the full vuAppAgent package with required configurations for a fresh installation. Download <OS> vuAppAgent Update Configuration Binary - Downloads the agent configuration package to update an existing vuAppAgent installation.
  • Download the agent installation or update package, then click Finish to close the data source window.

Metrics Collected

NameDescriptionData Type
@timestampThe original string timestamp from the source log.String
timestampThe timestamp for the data point with high precision (64-bit).DateTime64
targetThe target for the metrics, typically identifying the specific system or service being monitored.String
HostThis is the host/ip of the machine where JVM is running. This is just aString
tenant_idnanLowCardinality(String)
bu_idcopy of the "Host" field in the configuration file.LowCardinality(String)
StatisticTypeType of statistic being monitoredString
DisplayNameName to identify the WAS. It is cofigured in the Metadata section of theString
StatusCurrent status of the server or service (e.g., "Up", "Down").LowCardinality(String)
ProcessName of the WAS process.String
ProcessTypeProcess Type. The values would be ManageProcessString
CellName of the WAS cell.String
NodeName of the WAS NodeString
RolledbackCountThe total number of global transactions rolled backUInt64
CommittedCountThe total number of global transactions committedUInt64
ActiveCountThe number of concurrently active global transactionsUInt64
ConcurrentHungThreadCount_currentThe number of thread hangs cleared.UInt64
ClearedThreadHangCountThe number of thread hangs cleared.UInt64
CPUUsageSinceServerStarted_maxThe max percent CPU Usage that is busy once the server isUInt64
CPUUsageSinceServerStarted_countThe count CPU Usage that is busy once the server isUInt64
CPUUsageSinceServerStarted_meanThe average system CPU utilization taken over the time interval sinceFloat32
CPUUsageSinceLastMeasurementThe average system CPU utilization taken over the time interval since the last reading. Because the first call is required to perform initialization, a value such as 0, which is not valid, will be returned. All subsequent calls return the expected value. On SMP machines, the value returned is the utilization averaged over all CPUs.UInt64
FreeMemoryThe free memory in the JVM run time.UInt64
CPUUsageSinceServerStarted_minThe min percent CPU Usage that is busy once the server isUInt64
ActiveCount_currentAll subsequent calls return the expected value. On SMP machines,The number of concurrently active sessions. A session is active if the WebSphere® Application Server is currently processing a request that uses that session.UInt64
LiveCount_currentThe number of local sessions that are currently cached in memory from the time at which this metric is enabled.UInt64
HeapSize_currentApplies only to session in memory with AllowOverflow=false. The number of times that a request for a new session cannot be handled because it exceeds the maximum session count.UInt64
UsedMemoryThe used memory in the JVM run timeUInt64
UpTimeThe amount of time that the JVM is runningUInt64
UseTime_meanMean value of UseTime. UseTime is the average time in milliseconds that a connection is in use.UInt64
PercentUsed_currentThe percent of the pool that is in use.UInt64
UseTime_maxMax value of UseTime. UseTime is the average time in milliseconds that a connection is in use.UInt64
UseTime_countCurrent value of UseTime. UseTime is the average time in milliseconds that a connection is in use.UInt64
WaitingThreadCount_currentThe number of threads that are currently waiting for a connection.UInt64
WaitTime_maxMax of WaitTime. WaitTime is the average waiting time in milliseconds until a connection is granted if a connection is not currently available.UInt64
PoolSize_currentThe size of the connection pool.UInt64
UseTime_minMin value of UseTime. UseTime is the average time in milliseconds that a connection is in use.UInt64
FreePoolSize_currentThe number of managed connections that are in the free pool.UInt64
WaitTime_minMin of WaitTime. WaitTime is the average waiting time in milliseconds until a connection is granted if a connection is not currently available.UInt64
CreateCountThe total number of managed connections that were created since pool creation.UInt64
WaitTime_meanMean of WaitTime. WaitTime is the average waiting time in millisecondsUInt64
CloseCountThe total number of managed connections that were destroyed since pool creation.UInt64
WaitTime_countCurrent value of WaitTime. WaitTime is the average waiting time in milliseconds until a connection is granted if a connection is not currently available.UInt64
@timestampThe original string timestamp from the source log.String
timestampThe timestamp for the data point with high precision (64-bit).DateTime64
targetThe target for the metrics, typically identifying the specific system or service being monitored.String
HostThis is the host/ip of the machine where JVM is running. This is just aString
tenant_idnanLowCardinality(String)
bu_idcopy of the "Host" field in the configuration file.LowCardinality(String)
StatisticTypeType of statistic being monitoredString
DisplayNameName to identify the WAS. It is cofigured in the Metadata section of theString
StatusCurrent status of the server or service (e.g., "Up", "Down").LowCardinality(String)
ProcessName of the WAS process.String
ProcessTypeProcess Type. The values would be ManageProcessString
CellName of the WAS cell.String
NodeName of the WAS NodeString
@timestampThe original string timestamp from the source log.String
timestampThe timestamp for the data point with high precision (64-bit).DateTime64
targetThe target for the metrics, typically identifying the specific system or service being monitored.String
HostThis is the host/ip of the machine where JVM is running. This is just aString
tenant_idnanLowCardinality(String)
bu_idcopy of the "Host" field in the configuration file.LowCardinality(String)
StatisticTypeType of statistic being monitoredString
DisplayNameName to identify the WAS. It is cofigured in the Metadata section of theString
ProcessName of the WAS process.String
ProcessTypeProcess Type. The values would be ManageProcessString
CellName of the WAS cell.String
NodeName of the WAS NodeString
PercentUsed_currentThe percent of the pool that is in use.UInt64
WaitingThreadCount_currentThe number of threads that are currently waiting for a connection.UInt64
FaultCountThe total number of faults, such as timeouts, in the connection pool.UInt64
WaitTime_countCurrent value of WaitTime. WaitTime is the average waiting time in milliseconds until a connection is granted if a connection is not currently available.UInt64
PoolSize_currentThe size of the connection pool.UInt64
FreePoolSize_currentThe number of managed connections that are in the free pool.UInt64
CreateCountThe total number of managed connections that were created since pool creation.UInt64
CloseCountThe total number of managed connections that were destroyed since pool creation.UInt64
@timestampThe original string timestamp from the source log.String
timestampThe timestamp for the data point with high precision (64-bit).DateTime64
targetThe target for the metrics, typically identifying the specific system or service being monitored.String
HostThis is the host/ip of the machine where JVM is running. This is just aString
tenant_idnanLowCardinality(String)
bu_idcopy of the "Host" field in the configuration file.LowCardinality(String)
StatisticTypeType of statistic being monitoredString
DisplayNameName to identify the WAS. It is cofigured in the Metadata section of theString
ProcessName of the WAS process.String
ProcessTypeProcess Type. The values would be ManageProcessString
CellName of the WAS cell.String
NodeName of the WAS NodeString
ProcessCpuUsageCPU usage for this process.UInt64
FreeMemoryThe free memory in the JVM run time.UInt64
HeapSize_currentThe total memory in the JVM run time.UInt64
UsedMemoryThe used memory in the JVM run timeUInt64
UpTimeThe amount of time that the JVM is runningUInt64
@timestampThe original string timestamp from the source log.String
timestampThe timestamp for the data point with high precision (64-bit).DateTime64
targetThe target for the metrics, typically identifying the specific system or service being monitored.String
HostThis is the host/ip of the machine where JVM is running. This is just aString
tenant_idnanLowCardinality(String)
bu_idcopy of the "Host" field in the configuration file.LowCardinality(String)
StatisticTypeType of statistic being monitoredString
DisplayNameName to identify the WAS. It is cofigured in the Metadata section of theString
ProcessName of the WAS process.String
ProcessTypeProcess Type. The values would be ManageProcessString
CellName of the WAS cell.String
NodeName of the WAS NodeString
LiveCount_currentThe number of local sessions that are currently cached in memory from the time at which this metric is enabled.UInt64
ActiveCount_currentThe number of concurrently active sessions. A session is active if the WebSphere® Application Server is currently processing a request that uses that session.UInt64
HeapSize_currentApplies only to session in memory with AllowOverflow=false. The number of times that a request for a new session cannot be handled because it exceeds the maximum session count.UInt64
@timestampThe original string timestamp from the source log.String
timestampThe timestamp for the data point with high precision (64-bit).DateTime64
targetThe target for the metrics, typically identifying the specific system or service being monitored.String
HostThis is the host/ip of the machine where JVM is running. This is just aString
tenant_idnanLowCardinality(String)
bu_idcopy of the "Host" field in the configuration file.LowCardinality(String)
StatisticTypeType of statistic being monitoredString
DisplayNameName to identify the WAS. It is cofigured in the Metadata section of theString
ProcessName of the WAS process.String
ProcessTypeProcess Type. The values would be ManageProcessString
CellName of the WAS cell.String
NodeName of the WAS NodeString
CPUUsageSinceLastMeasurementThe average system CPU utilization taken over the time interval since the last reading. Because the first call is required to perform initialization, a value such as 0, which is not valid, will be returned. All subsequent calls return the expected value. On SMP machines, the value returned is the utilization averaged over all CPUs.UInt64
CPUUsageSinceServerStarted_meanThe average system CPU utilization taken over the time interval sinceUInt64
CPUUsageSinceServerStarted_countThe count CPU Usage that is busy once the server isUInt64
FreeMemoryThe free memory in the JVM run time.UInt64
@timestampThe original string timestamp from the source log.String
timestampThe timestamp for the data point with high precision (64-bit).DateTime64
targetThe target for the metrics, typically identifying the specific system or service being monitored.String
HostThis is the host/ip of the machine where JVM is running. This is just aString
tenant_idnanLowCardinality(String)
bu_idcopy of the "Host" field in the configuration file.LowCardinality(String)
StatisticTypeType of statistic being monitoredString
DisplayNameName to identify the WAS. It is cofigured in the Metadata section of theString
ProcessName of the WAS process.String
ProcessTypeProcess Type. The values would be ManageProcessString
CellName of the WAS cell.String
NodeName of the WAS NodeString
ActiveCount_currentThe number of concurrently active threadsUInt64
PoolSize_currentThe average number of threads in poolUInt64
DeclaredthreadHungCountThe number of threads declared hung.UInt64
ClearedThreadHangCountThe number of thread hangs cleared.UInt64
@timestampThe original string timestamp from the source log.String
timestampThe timestamp for the data point with high precision (64-bit).DateTime64
targetThe target for the metrics, typically identifying the specific system or service being monitored.String
HostThis is the host/ip of the machine where JVM is running. This is just aString
tenant_idnanLowCardinality(String)
bu_idcopy of the "Host" field in the configuration file.LowCardinality(String)
StatisticTypeType of statistic being monitoredString
DisplayNameName to identify the WAS. It is cofigured in the Metadata section of theString
ProcessName of the WAS process.String
ProcessTypeProcess Type. The values would be ManageProcessString
CellName of the WAS cell.String
NodeName of the WAS NodeString
ActiveCountThe number of concurrently active global transactionsUInt64
CommittedCountThe total number of global transactions committedUInt64
GlobalTimeoutCountThe number of global transactions timed outUInt64
RolledbackCountThe total number of global transactions rolled backUInt64
@timestampThe original string timestamp from the source log.String
timestampThe timestamp for the data point with high precision (64-bit).DateTime64
targetThe target for the metrics, typically identifying the specific system or service being monitored.String
HostThis is the host/ip of the machine where JVM is running. This is just aString
tenant_idnanLowCardinality(String)
bu_idcopy of the "Host" field in the configuration file.LowCardinality(String)
StatisticTypeType of statistic being monitoredString
DisplayNameName to identify the WAS. It is cofigured in the Metadata section of theString
ProcessName of the WAS process.String
ProcessTypeProcess Type. The values would be ManageProcessString
CellName of the WAS cell.String
NodeName of the WAS NodeString
ConcurrentRequestsThe number of requests that are concurrently processed.UInt64
RequestCountThe total number of requests processed for an URI associated with a servlet.UInt64
ErrorCountTotal number of errors in a servlet or JavaServer Page (JSP).UInt64
ResponseTimeThe average service response time, in milliseconds, for an URI associated with a servlet.Float32
StatisticSubTypeLevel1The Application name providerString