This section describes the required configurations as well as the optional configurations available for the Solution Package for Solace in the RTView Configuration Application. You must define data source connections for each message router and Syslog connection that you want to monitor , and you can on the CONNECTIONS tab. You can also optionally modify the default data update rates and historical data collection configurations on the DATA COLLECTION and DATA STORAGE tabs.

Obtain SEMP Version

In order to properly request monitored data, the Monitor requires the exact SEMP version on your message routers. These instructions describe how to use SolAdmin to determine the SEMP version for each of your Solace Message Routers or VMRs. You will need this information when you connect your message routers and edit connection properties.

Note: These instructions are for SolAdmin on Windows. For Linux, only the path to the log file changes.

To obtain the SEMP Version"

• Navigate to the SolAdmin installation folder. For example, C:\Program Files (x86)\SolAdmin\.
• Change directory (cd) to the bin directory and open the log4j.properties file in a text editor.
• Change the logging level to DEBUG and provide the full path to the logging file (for example, C:\Logs) while retaining all other settings. The edited properties are as follows:

# full path to the location where you want the log file to be stored. In this example C:\Logs
log4j.appender.A1.File=C:\Logs\soladmin.log
# Set the logging category to DEBUG
log4j.category.com.solacesystems=DEBUG, A1

• Save the log4j.properties file.
• Start SolAdmin and add your message routers or VMRs as managed instances.
• Open the soladmin.log file and locate the semp-version tag in SEMP requests. The SEMP version that will be used by the Monitor replaces underscores (_) with dots (.). For example, if the SEMP request in the SolAdmin log file is 7_2VMR, you use 7.2VMR for the $solSempVersion substitution of the Monitor connection property.

Configuring Data Collection

To configure data collection:

• Navigate to the Solution Package Configuration > Solace Message Router > CONNECTIONS tab.On

Image Added

• To create connections to your message routers, click the MESSAGE ROUTER button on the CONNECTIONS tab , click the Message Router button and click the  icon to create connections to message routers.

The Add Connection dialog displays.

Image RemovedImage Added

• Specify the connection information and click SAVE where:

Connection Name: Enter the name of the connection Enter a unique string to identify the connection of the monitored message router.

URL: Specify  Enter the path URL to be used for the JMX connection of the WebLogic Server to which you want to connectconnection, which contains an IP address or the host name that can be resolved by your network name resolution method and the SEMP port number configured for your message router.

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

Password: This password defined to secure the connection This password is used when creating the connection to the message router. 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 Image Removed 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 Image Removed 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 Edition: Enable the toggle if the message router is a Solace Cloud Edition VMR.

SEMP Version: Specify the SEMP Version used by the message router.

VPN Name(s): Optionally enter the names of the VPNs that you want to monitor. Monitoring multiple VPNs could impact performance.

Once saved, your newly saved message router connection displays in the Message Router Connections region on the CONNECTIONS tab.

Image Added

• Repeat the previous two steps for each message router connection to be monitored.
• To create Syslog connections, click the SYSLOG button.

The Syslog Connections region displays.

Image Added

• Click the Image Added icon.

The Add Connection dialog displays.

Image Added

• Specify the connection information and click SAVE where:

Name: Enter a unique string to identify the connection of the monitored message router.

Protocol: Select either the TCP or UDP protocol.

Host: Enter the host name. The default for both TCP and UDP is localhost.

Port: Enter the port number. The default for TCP is 601. The default for UDP is 514. Only root can use ports 0 thru 1024 on UNIX/Linux systems.

Note: The syslog listener configuration requires the IP address assigned to the physical network interface. Host refers to the physical network interface that will be used to receive Syslog messages (there might be more than one network interface available on the receiving system). Typically, this will be the IP address assigned to the selected network interface. If the system where the Monitor Data Server is running is also the Syslog server/sender, then localhost can be used.

Once saved, your newly saved syslog connection displays in the Syslog Connections region on the CONNECTIONS tab.

Image Removed

Image Added

• 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 Solace Message Routers > 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.

Image Removed

• 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.

Image Removed

• 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).

Image Removed

Image Added

The following options are available:

Poll Rate: Enter the query interval, in seconds, to collect data updates. Caches impacted by this field are SolEndpointStats, SolEndpoints, SolClients, SolClientStats, SolBridges, SolAppliances, SolBridgeStats, SolApplianceInterfaces and SolApplianceMessageSpool.

Poll Rate Large: Enter the time interval, in seconds, to check for data updates. Caches impacted by this field are SolCspfNeighbors, SolApplicances and SolEnvironmentSensors.

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 WlsJmsPersistentStoreRuntimethe SolVpns, WlsJmsPersistentStoreConnectionRuntimeSolClientStats, WlsJmsConnectionSolAppliances, WlsJmsProducerSolEndpoints, WlsJmsConsumerSolCspfNeighbors, WlsJmsDurableSubscriberSolBridgeStats, WlsJmsPooledConnectionRuntimeSolApplianceInterfaces, WlsJmsRuntimeSolApplianceMessageSpool, WlsJmsServerRuntime, WlsJrockitRuntime, WlsServerRuntime, WlsThreadPoolRuntime, WlsJdbcDatasourceRuntime, WlsJvmRuntime, WlsJvmStats, WlsServerTotalsByCluster, WlsServletStats, WlsServletTotalsByServer, WlsServletTotalsByApp, WlsSessionStats, WlsSessionTotalsByServer, WlsSessionTotalsByClusterApp, WlsServletTotalsByClusterApp, WlsWorkManagerStats, WlsWorkManagerTotalsByApp, and WlsWorkManagerTotalsByServer SolEndpointStats, and SolAppliancesQuality. 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  To update the default settings:

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

Image RemovedImage Added

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: WlsJmsConnectionSolVpns, WlsJmsProducerSolClientStats, WlsJmsConsumerSolAppliances, 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 WlsWorkManagerTotalsByServerSolEndpoints, SolCspfNeighbors, SolBridgeStats, SolApplianceInterfaces, SolApplianceMessageSpool, and SolEndpointStatscaches.. The default is 60 seconds.

Condense Raw Time -- The time span of raw data kept in the cache history table for the following caches: WlsJmsConnectionSolVpns, WlsJmsProducerSolClientStats, WlsJmsConsumerSolAppliances, WlsJmsDurableSubscriberSolEndpoints, WlsJmsDestinationTotalsSolCspfNeighbors, WlsJmsDestinationSolBridgeStats, WlsJmsRuntime, WlsJmsServerRuntime, WlsJrockitRuntime, WlsServerRuntime, WlsThreadPoolRuntime, WlsJdbcDatasourceRuntime, WlsJvmRuntime, WlsJvmStats, WlsServerTotalsByCluster, WlsServletStats, WlsServletTotalsByServer, WlsServletTotalsByApp, WlsSessionStats, WlsSessionTotalsByServer, WlsSessionTotalsByClusterApp, WlsServletTotalsByClusterApp, WlsWorkManagerStats, WlsWorkManagerTotalsByApp, and WlsWorkManagerTotalsByServerSolApplianceInterfaces, SolApplianceMessageSpool, and SolEndpointStats. 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: WlsJrockitRuntimeSolVpns, WlsServerRuntimeSolClientStats, WlsThreadPoolRuntimeSolAppliances, WlsJdbcDatasourceRuntimeSolEndpoints, WlsJvmRuntimeSolCspfNeighbors, WlsJvmStatsSolBridgeStats, WlsServerTotalsByCluster, WlsServletStats, WlsServletTotalsByServer, WlsServletTotalsByApp, WlsSessionStats, WlsSessionTotalsByServer, WlsSessionTotalsByClusterApp, WlsServletTotalsByClusterApp, WlsWorkManagerStats, WlsWorkManagerTotalsByApp, and WlsWorkManagerTotalsByServerSolApplianceInterfaces, SolApplianceMessageSpool, and SolEndpointStats. 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 Solace Message Router > 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.

Image RemovedImage Added

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 cacheThe following fields are available:

Expire Time - The number of seconds to wait for a data update before cached history data is shown as Expired in displays. The caches impacted by

this field are SolVpns, SolBridges, SolClients, SolClientStats, SolAppliances, SolEndpoints, SolCspfNeighbors, SolBridgeStats, SolApplianceInterfaces, SolApplianceMessageSpool, SolEndpointStats, SolEnvironmentSensors and SolAppliancesQuality.

Delete Time - The number of seconds to wait for a data update before cached history data is removed from displays. The caches impacted by

this field are SolVpns, SolBridges, SolEndpoints, SolBridgeStats, SolEndpointStats and SolEnvironmentSensors.

Delete Time for Clients - The number of seconds to wait for a response from clients before removing client from displays. The caches impacted by this field are SolClients and SolClientStats.

To modify these defaults:

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

Image RemovedImage Added

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 Message Routers (WlsJmsConnection SolAppliances cache), JMS Consumers (WlsJmsConsumer cache), JMS Destinations (WlsJmsDestination cache), JMS Destination Totals (WlsJmsDestinationTotals cache), JMS Durable Subscribers (WlsJmsDurableSubscriber CSPF Neighbors (SolCspfNeighbors cache), and Session Stats VPNs (WlsJmsSessionStats SolVpns cache). The remaining historical data is not 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 cachesBridge Stats (SolBridgeStats cache), Client Stats (SolClientStats cache), Endpoint Stats (SolEndpointStats cache), Endpoints (SolEndpoints cache), Interface (SolApplianceInterfaces cache), Message Spools (SolApplianceMessageSpool cache), Syslog Events (SyslogEvents cache)). To enable/disable the collection of historical data, perform the following steps:

• Navigate to the Solution Package Configuration > Oracle WebLogic Solace Message Router > 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.

Image RemovedImage Added

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/wlmsolmon/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.

To add the prefix:

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

Image RemovedImage Added