WebLogic 6.x/7.x Application Server Monitor

The SiteScope WebLogic 6.x/7.x Application Server Monitor allows you to monitor the statistics of a WebLogic version 6 Servers . The error and warning thresholds for the monitor can be set on as many as ten WebLogic server statistics.

Usage Guidelines

Use the WebLogic 6.x/7.x Application Server Monitor to monitor performance statistics data from WebLogic 6.x, 7.x, and 8.x servers. You can monitor multiple parameters or counters with a single monitor instance. This allows you to watch server loading for performance, availability, and capacity planning. Create a separate WebLogic 6.x/7.x Application Server Monitor instance for each WebLogic server in your environment.

The BEA WebLogic Application Server monitor uses the Java JMX interface to access run-time MBeans on the WebLogic server. An MBean is a container that holds the performance data. You must set certain permissions on the WebLogic server for SiteScope to be able to monitor MBeans.

SiteScope access to WebLogic 6.x Servers

To set permissions for monitoring WebLogic 6.x servers, create a new ACL on the WebLogic server with the name weblogic.admin.mbean. Set the permission type to access and set the Users and Groups to be the user or group account that SiteScope will use to monitor the WebLogic server.

SiteScope access to WebLogic 7.x Servers

WebLogic 7.x and later servers use "Security Policies" instead of ACL's to control access to the server resources. In order to be able to monitor WebLogic 7.x servers with SiteScope, the WebLogic administrator will need to add the user account that is running SiteScope to a WebLogic user group. The WebLogic group containing the SiteScope user must then be associated with with a "role statement" that will grant the necessary security role for accessing the desired WebLogic resources. The same security role must also be associated with the applicable "policy statement" that will grant SiteScope access to the WebLogic resources. See the WebLogic server documentation for more information.

The default run schedule for this monitor is every 10 minutes, but you can change it to run more or less often using the Update every setting.

Completing the WebLogic 6.x/7.x Application Server Monitor Form

To display the WebLogic 6.x/7.x Application Server Monitor Form, either click the Edit link for an existing WebLogic 6.x/7.x Application Server Monitor in a monitor table, or click the add a Monitor link on a group's detail page and click the Add WebLogic 6.x/7.x Application Server Monitor link.

Complete the items on the WebLogic 6.x/7.x Application Server Monitor Form as follows. When the required items are complete, click the Add Monitor button.

Server

Choose the server you want to monitor. Use the choose server link to view a list of servers or to enter a path name and other information as follows:

Server: Enter the name of the server where WebLogic is running.
Port Number: Enter the port number that the WebLogic server is responding on. The default port is 7001.
User Name: Enter the username required to log into the WebLogic server.
Password: Enter the password required to log into the WebLogic server.
Secure Server: Check this box if you are using a secure server connection option. Note: If you select this option, you must enter the applicable port number used by the WebLogic server for secure connections. The default secure server port is 7002.
WebLogic Jar File: Enter the absolute path name to the weblogic.jar file on the SiteScope machine. This file must be installed on the SiteScope server and can be downloaded from the WebLogic server. An example path is: c:\bea\weblogic7\ebcc\lib\ext\weblogic.jar. This file is not strictly required for monitoring some earlier versions of WebLogic 6. In this case, leaving this box blank will normally cause any necessary classes to be downloaded directly from the WebLogic server. Note that this is not as efficient as loading the classes from the a *.jar file on the server where SiteScope is running.
Note: Do not install the weblogic.jar file in the SiteScope directory tree. For example, do not install it in the <SiteScope install path>/SiteScope/java/lib/ext directory as this will cause the Weblogic monitor to fail. You must create a separate directory on the server where SiteScope is running for this file.

Counters

Choose the server performance parameters or counters you want to check with this monitor. The table list to the right of this item displays those currently selected for this monitor. Use the choose counters link to bring up the counters selection screen. Check or clear the check boxes on the choose counters screen to select between one to ten counters to monitor on this server. The performance parameters or counters available for the WebLogic 6.x Application Server Monitor include:

MessagesLogged
Registered
CachingDisabled
UnlockedUsersTotalCount
InvalidLoginUsersHighCount
LoginAttemptsWhileLockedTotalCount
Registered
LockedUsersCurrentCount
CachingDisabled
InvalidLoginAttemptsTotalCount
UserLockoutTotalCount

The following categories of measurements also exist for the WebLogic 6.x Application Server Monitor. For more information on the measurements that each of these categories contains, refer to the following page on the Mercury Interactive Web site: http://www.mercuryinteractive.com/products/loadrunner/load_testing_monitors/supported.html .

ServletRuntime
WebAppComponentRuntime
EJBStatefulHomeRuntime
JTARuntime
JVMRuntime
EJBEntityHomeRuntime.
DomainRuntime
EJBComponentRuntime
DomainLogHandlerRuntime
JDBCConnectionPoolRuntime
ExecuteQueueRuntime
ClusterRuntime

Update every

Select how often the monitor should read the server statistics. The default interval is to run or update the monitor once every 10 minutes. Use the drop-down list to the right of the text box to specify another update interval in increments of seconds, minutes, hours, or days. The update interval must be 15 seconds or longer.

Title

Enter a title text for this monitor. This text is displayed in the group detail page, in report titles, and other places in the SiteScope interface. If you do not enter a title text, SiteScope will create a title based on the host, server, or URL being monitored.

Advanced Options

The Advanced Options section presents a number of ways to customize monitor behavior and display. Use this section to customize error and warning thresholds, disable the monitor, set monitor-to-monitor dependencies, customize display options, and enter other monitor specific settings required for special infrastructure environments. The options for this monitor type are described below. Complete the entries as needed and click the Add or Update button to save the settings.

Disable

Check this box to temporarily disable this monitor and any associated alerts. To enable the monitor again, clear the box.

Verify Error

Check this box if you want SiteScope to automatically run this monitor again if it detects an error. When an error is detected, the monitor will immediately be scheduled to run again once.

Note: In order to change the run frequency of this monitor when an error is detected, use the Update every (on errors) option below.

Note: The status returned by the Verify Error run of the monitor will replace the status of the originally scheduled run that detected an error. This may cause the loss of important performance data if the data from the verify run is different than the initial error status.

Warning: Use of this option across many monitor instances may result in significant monitoring delays in the case that multiple monitors are rescheduled to verify errors at the same time.

Update Every (on error)

You use this option to set a new monitoring interval for monitors that have registered an error condition. For example, you may want SiteScope to monitor this item every 10 minutes normally, but as often as every 2 minutes if an error has been detected. Note that this increased scheduling will also affect the number of alerts generated by this monitor.

Schedule

By default, SiteScope monitors are enabled every day of the week. You may, however, schedule your monitors to run only on certain days or on a fixed schedule. Click the Edit schedule link to create or edit a monitor schedule. For more information about working with monitor schedules, see the section on Schedule Preferences for Monitoring.

Monitor Description

Enter additional information about this monitor. The Monitor Description can include HTML tags such as the <BR> <HR>, and <B> tags to control display format and style. The description will appear on the Monitor Detail page.

Report Description

Enter an optional description for this monitor that will make it easier to understand what the monitor does. For example, network traffic or main server response time. This description will be displayed on with each bar chart and graph in Management Reports and appended to the tool-tip displayed when you pass the mouse cursor over the status icon for this monitor on the monitor detail page.

Depends On

To make the running of this monitor dependent on the status of another monitor or monitor group, use the drop-down list to select the monitor on which this monitor is dependent. Select None to remove any dependency.

Depends Condition

If you choose to make the running of this monitor dependent on the status of another monitor, select the status condition that the other monitor or monitor group should have in order for the current monitor to run normally. The current monitor will be run normally as long as the monitor on which it depends reports the condition selected in this option.

List Order

By default, new monitors are listed last on the Monitor Detail page. You may use this drop-down list to choose a different placement for this monitor.

Setting Monitor Status Thresholds

SiteScope Application Monitors allow you to set multiple threshold conditions to determine the status reported by each monitor. The individual conditions are combined as logical OR relationships so that when one or more of the conditions (for example any of the conditions for Error if) are met the monitor status is set to the applicable condition. If multiple conditions are met for more than one status condition (such as conditions for both error and for warning), the status for the monitor is set to the highest valued condition. Thus a match of an error condition and a warning condition would be reported as an error status, error being the highest value, warning the next highest and good the lowest value.

Error if: Use one or more of the selection boxes in this item to define one or more error conditions for this monitor. Use the drop-down lists in these items to change error threshold(s) relative to the counters you have selected to check with this monitor. After choosing a counter or parameter, use the comparison operator drop-down list to specify an error threshold such as: >= (greater than or equal to), != (not equal to), or < (less than) and enter a comparison value in the box provided. Comparison values should be entered as whole numbers.
Warning if: Use one or more of the selection boxes in this item to define one or more warning conditions for this monitor. Use the drop-down lists in these items to change warning threshold(s) relative to the counters you have selected to check with this monitor. Set these values relative to those you set for the error threshold in the Error if item.
Good if: You can set this monitor to return a good status for certain conditions. You may define those conditions here. Complete this item as you would for the Error if and Warning if items.