This section describes the required configurations as well as the optional configurations available for the Solution Package for Oracle WebLogic in the RTView Configuration Application. You must define the classpath to the Oracle WebLogic jar files and you must also define data source connections for each connection that you want to monitor.

Configuring Data Collection

To configure data collection:

  • Navigate to the Solution Package Configuration > Oracle WebLogic > CONNECTIONS tab.
  • On the CONNECTIONS tab, provide the correct full path to the directory containing the Oracle WebLogic jar files in the Classpath field.

  • Click the  icon.

The Add Connection dialog displays.

  • Specify the connection information and click SAVE where:

Connection Name: Enter the name of the connection.

URL: Specify the path to the JMX connection of the WebLogic Server to which you want to connect.

Username: The username defined to secure the connection. This field is only required when the connection has been secured.

Password: This password defined to secure the connection. This field is only required when the connection has been secured. By default, the password entered is hidden. Click the  icon to view the password text.

Properties

java.class.path: Specify the full path to the wlfullclient.jar and webserviceclient.jar files.

jmx.remote.provider.protocol.pkgs: Specify the jmx.remote.provider.protocol.pkgs key.

java.naming.security.principal: Specify the JMX username.

java.naming.security.credentials: Specify the JMX password. By default, the password entered is hidden. Click the  icon to view the password text.

Additional Properties

Name: Specify the Name and Value of any additional properties you want to use for monitoring your WebLogic Servers.

Value: Enter the value for the property. You can enter multiple properties by entering the name and value and clicking the associated Add button. The added property then displays on the line below. Once entered, you can click the X next to the property name to remove them. By default, the  icon sets the defined Value as secured once the connection is saved. Click this icon prior to clicking Add to make the defined Value visible when the connection is saved.

Once saved, the new connection displays in the Connections region on the CONNECTIONS tab.

  • Repeat the previous two steps for each connection to be monitored.
  • If you want to modify the default values for the update rates for all caches, you can update the default polling rates in Solution Package Configuration > Oracle WebLogic > DATA COLLECTION > Poll Rates.

Note: When modifying your update rates, you should take your system architecture and number of elements per cache into account and ensure that you are not changing your update rates to values that might negatively impact system performance.

  • By default, collecting auxiliary caches, bridge destinations, JMS persistent stores, JMS servers, servlets, and work managers data is disabled. To enable collecting this data, navigate to the Solution Package Configuration > Oracle WebLogic > DATA COLLECTION tab > Metric Selection section and enable the metrics for which you want to collect data.

  • When enabling Bridge Destinations, enter the JNDI URL (which appears after enabling the toggle). When enabling JMS Servers, specify the Runtime Filter (*, which means no filter, is the default) if you want to limit the collection of data to specific JMS Servers. When enabling Servlets, specify the Servlet Pattern to limit the collection of data to specific servlets (*, which means no filter, is the default for ApplicationRuntime and ServerRuntime).

Configuring Collection of Historical Data (Optional)

You can specify the number of history rows to store in memory, the compaction rules, the duration before metrics are expired and deleted, and the different types of metrics that you want the Historian to store in the DATA STORAGE tab in the RTView Configuration Application. This section is optional.

Defining the Storage of In Memory History

You can modify the maximum number of history rows to store in memory in the DATA STORAGE tab. The History Rows property defines the maximum number of rows to store for the WlsJmsPersistentStoreRuntime, WlsJmsPersistentStoreConnectionRuntime, WlsJmsConnection, WlsJmsProducer, WlsJmsConsumer, WlsJmsDurableSubscriber, WlsJmsPooledConnectionRuntime, WlsJmsRuntime, WlsJmsServerRuntime, WlsJrockitRuntime, WlsServerRuntime, WlsThreadPoolRuntime, WlsJdbcDatasourceRuntime, WlsJvmRuntime, WlsJvmStats, WlsServerTotalsByCluster, WlsServletStats, WlsServletTotalsByServer, WlsServletTotalsByApp, WlsSessionStats, WlsSessionTotalsByServer, WlsSessionTotalsByClusterApp, WlsServletTotalsByClusterApp, WlsWorkManagerStats, WlsWorkManagerTotalsByApp, and WlsWorkManagerTotalsByServer caches. The default setting for History Rows is 50,000. The History Rows Large property defines the maximum number of rows to store for the WlsJmsDestinationTotals and WlsJmsDestination caches. The default setting for History Rows Large is 100,000. To update the default settings:

  • Navigate to the Solution Package Configuration > Oracle WebLogic > DATA STORAGE tab.
  • In the Size region, click the History Rows and History Rows Large fields and specify the desired number of rows.

Defining Compaction Rules

Data compaction, essentially, is taking large quantities of data and condensing it using a defined rule so that you store a reasonably sized sample of data instead of all of your data, thus preventing you from potentially overloading your database. The available fields are:

Condense Interval -- The time interval at which the cache history is condensed for the following caches: WlsJmsConnection, WlsJmsProducer, WlsJmsConsumer, WlsJmsDurableSubscriber, WlsJmsDestination__$wlsCompactionRules: WlsJmsConnection, WlsJmsProducer, WlsJmsConsumer, WlsJmsDurableSubscriber, WlsJmsDestinationTotals, WlsJmsDestination, WlsJmsRuntime, WlsJmsServerRuntime, WlsJrockitRuntime, WlsServerRuntime, WlsThreadPoolRuntime, WlsJdbcDatasourceRuntime, WlsJvmRuntime, WlsJvmStats, WlsServerTotalsByCluster, WlsServletStats, WlsServletTotalsByServer, WlsServletTotalsByApp, WlsSessionStats, WlsSessionTotalsByServer, WlsSessionTotalsByClusterApp, WlsServletTotalsByClusterApp, WlsWorkManagerStats, WlsWorkManagerTotalsByApp, and WlsWorkManagerTotalsByServer. The default is 60 seconds.

Condense Raw Time -- The time span of raw data kept in the cache history table for the following caches: WlsJmsConnection, WlsJmsProducer, WlsJmsConsumer, WlsJmsDurableSubscriber, WlsJmsDestinationTotals, WlsJmsDestination, WlsJmsRuntime, WlsJmsServerRuntime, WlsJrockitRuntime, WlsServerRuntime, WlsThreadPoolRuntime, WlsJdbcDatasourceRuntime, WlsJvmRuntime, WlsJvmStats, WlsServerTotalsByCluster, WlsServletStats, WlsServletTotalsByServer, WlsServletTotalsByApp, WlsSessionStats, WlsSessionTotalsByServer, WlsSessionTotalsByClusterApp, WlsServletTotalsByClusterApp, WlsWorkManagerStats, WlsWorkManagerTotalsByApp, and WlsWorkManagerTotalsByServer. The default is 1200 seconds.

Compaction Rules -- This field defines the rules used to condense your historical data in the database for the following caches: WlsJrockitRuntime, WlsServerRuntime, WlsThreadPoolRuntime, WlsJdbcDatasourceRuntime, WlsJvmRuntime, WlsJvmStats, WlsServerTotalsByCluster, WlsServletStats, WlsServletTotalsByServer, WlsServletTotalsByApp, WlsSessionStats, WlsSessionTotalsByServer, WlsSessionTotalsByClusterApp, WlsServletTotalsByClusterApp, WlsWorkManagerStats, WlsWorkManagerTotalsByApp, and WlsWorkManagerTotalsByServer. By default, the columns kept in history will be aggregated by averaging rows with the following rule 1h -;1d 5m;2w 15m, which means the data from 1 hour will not be aggregated (1h - rule), the data over a period of 1 day will be aggregated every 5 minutes (1d 5m rule), and the data over a period of 2 weeks old will be aggregated every 15 minutes (2w 15m rule).

To modify these settings:

  • Navigate to the Solution Package Configuration > Oracle WebLogic > DATA STORAGE tab.
  • In the Compaction region, click the Condense Interval, Condense Raw Time, and Compaction Rules fields and specify the desired settings.

Note: When you click in the Compaction Rules field, the Copy default text to clipboard link appears, which allows you copy the default text (that appears in the field) and paste it into the field. This allows you to easily edit the string rather than creating the string from scratch.

Defining Expiration and Deletion Duration Metrics

The data for each metric is stored in a specific cache and, when the data is not updated in a certain period of time, that data will either be marked as expired or, if it has not been updated for an extended period of time, it will be deleted from the cache altogether. By default, metric data will be set to expired when the data in the cache has not been updated within 45 seconds. Also, by default, if the data has not been updated in the cache within 3600 seconds, it will be removed from the cache. The caches impacted by the Expire Time property are: WlsServerRuntime, WlsJvmRuntime, WlsClusterRuntime, WlsServerTotalsByCluster, WlsRuntime, WlsServletStats, WlsServletTotalsByServer, WlsServletTotalsByApp, WlsSessionStats, WlsSessionTotalsByServer, WlsSessionTotalsByClusterApp, WlsServletTotalsByClusterApp, WlsWorkManagerStats, WlsWorkManagerTotalsByApp, and WlsWorkManagerTotalsByServer. The caches impacted by the Delete Time property are: WlsServletStats, WlsServletTotalsByServer, WlsServletTotalsByApp, WlsSessionStats, WlsSessionTotalsByServer, WlsSessionTotalsByClusterApp, WlsServletTotalsByClusterApp, WlsWorkManagerStats, WlsWorkManagerTotalsByApp, and WlsWorkManagerTotalsByServer. To modify these defaults:

  • Navigate to the Solution Package Configuration > Oracle WebLogic > DATA STORAGE tab.
  • In the Duration region, click the Expire Time and Delete Time fields and specify the desired settings.

Enabling/Disabling Storage of Historical Data

The History Storage section allows you to select which metrics you want the Historian to store in the history database. By default, the following historical data is not saved to the database: JMS Connections (WlsJmsConnection cache), JMS Consumers (WlsJmsConsumer cache), JMS Destinations (WlsJmsDestination cache), JMS Destination Totals (WlsJmsDestinationTotals cache), JMS Durable Subscribers (WlsJmsDurableSubscriber cache), and Session Stats (WlsJmsSessionStats cache). The remaining historical data is saved to the database by default (WlsServerRuntime, WlsServerTotalsByCluster, WlsJRockitRuntime, WlsJvmRuntime, WlsJvmStats, WlsThreadPoolRuntime, WlsJdbcDatasourceRuntime, WlsServletStats, WlsServletTotalsByApp, WlsServletTotalsByServer, WlsServletTotalsByClusterApp, WlsSessionTotalsByServer, WlsSessionTotalsByClusterApp, WLSWorkManagerStats, WLSWorkManagerTotalsByServer, WLSWorkManagerTotalsByApp, WlsJmsRuntime, and WlsJmsServerRuntime caches). To enable/disable the collection of historical data, perform the following steps:

  • Navigate to the Solution Package Configuration > Oracle WebLogic > DATA STORAGE tab.
  • In the History Storage region, (de)select the toggles for the various metrics that you (do not) want to collect. Blue is enabled, gray is disabled.

Defining a Prefix for All History Table Names for Metrics

The History Table Name Prefix field allows you to define a prefix that will be added to the database table names so that the Monitor can differentiate history data between data servers when you have multiple data servers with corresponding Historians using the same solution package(s) and database. In this case, each Historian needs to save to a different table, otherwise the corresponding data server will load metrics from both Historians on startup. Once you have defined the History Table Name Prefix, you will need to create the corresponding tables in your database as follows:

  • Locate the .sql template for your database under rtvapm/wlm/dbconfig and make a copy of the template.
  • Add the value you entered for the History Table Name Prefix to the beginning of all table names in the copied .sql template.
  • Use the copied .sql template to create the tables in your database.

Note: If you are using Oracle for your Historian Database, you must limit the History Table Name Prefix to 1 character because Oracle does not allow table names greater than 30 characters (and the longest table name for the solution package is 29 characters).

To add the prefix:

  • Navigate to the Solution Package Configuration > Oracle WebLogic > DATA STORAGE tab.
  • Click on the History Table Name Prefix field and enter the desired prefix name.