Nimsoft Monitor weblogic Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/weblogic/1.3/... · 1.3 January 2013 Added support for WebLogic version 12c. Added support for WebLogic

weblogic Guide v1.3 series

Nimsoft® Monitor™

Legal Notices Copyright © 2013, CA. All rights reserved.

Warranty

The material contained in this document is provided "as is," and is subject to being changed, without notice, in future editions. Further, to the maximum extent permitted by applicable law, Nimsoft LLC disclaims all warranties, either express or implied, with regard to this manual and any information contained herein, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Nimsoft LLC shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or of any information contained herein. Should Nimsoft LLC and the user have a separate written agreement with warranty terms covering the material in this document that conflict with these terms, the warranty terms in the separate agreement shall control.

Technology Licenses

The hardware and/or software described in this document are furnished under a license and may be used or copied only in accordance with the terms of such license.

No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Nimsoft LLC as governed by United States and international copyright laws.

Restricted Rights Legend

If software is for use in the performance of a U.S. Government prime contract or subcontract, Software is delivered and licensed as "Commercial computer software" as defined in DFAR 252.227-7014 (June 1995), or as a "commercial item" as defined in FAR 2.101(a) or as "Restricted computer software" as defined in FAR 52.227-19 (June 1987) or any equivalent agency regulation or contract clause. Use, duplication or disclosure of Software is subject to Nimsoft LLC’s standard commercial license terms, and non-DOD Departments and Agencies of the U.S. Government will receive no greater than Restricted Rights as defined in FAR 52.227-19(c)(1-2) (June 1987). U.S. Government users will receive no greater than Limited Rights as defined in FAR 52.227-14 (June 1987) or DFAR 252.227-7015 (b)(2) (November 1995), as applicable in any technical data.

Trademarks

Nimsoft is a trademark of CA.

Adobe®, Acrobat®, Acrobat Reader®, and Acrobat Exchange® are registered trademarks of Adobe Systems Incorporated.

Intel® and Pentium® are U.S. registered trademarks of Intel Corporation.

Java(TM) is a U.S. trademark of Sun Microsystems, Inc.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Netscape(TM) is a U.S. trademark of Netscape Communications Corporation.

Oracle® is a U.S. registered trademark of Oracle Corporation, Redwood City, California.

UNIX® is a registered trademark of the Open Group.

ITIL® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries.

All other trademarks, trade names, service marks and logos referenced herein belong to their respective companies.

For information on licensed and public domain software, see the Nimsoft Monitor Third-Party Licenses and Terms of Use document at: http://docs.nimsoft.com/prodhelp/en_US/Library/index.htm?toc.htm?1981724.html.

http://docs.nimsoft.com/prodhelp/en_US/Library/index.htm?toc.htm?1981724.html

Contact Nimsoft

For your convenience, Nimsoft provides a single site where you can access information about Nimsoft products.

At http://support.nimsoft.com/, you can access the following:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ Nimsoft Support policies and guidelines

■ Other helpful resources appropriate for your product

Provide Feedback

If you have comments or questions about Nimsoft product documentation, you can send a message to [email protected].

http://support.nimsoft.com/

mailto:[email protected]

Contents 5

Contents

Chapter 1: weblogic 1.3 7

weblogic Overview ....................................................................................................................................................... 7

Chapter 2: weblogic Probe Deployment 9

Prerequisites ................................................................................................................................................................ 9

JVM........................................................................................................................................................................ 9

Supported Platforms .................................................................................................................................................. 12

System Requirements ................................................................................................................................................ 12

Software Requirements ............................................................................................................................................. 13

Monitoring System Requirements ............................................................................................................................. 13

Probe Deployment Information ................................................................................................................................. 13

weblogic Installation Wizard ...................................................................................................................................... 14

Chapter 3: weblogic Configuration 17

Probe Configuration Interface Installation ................................................................................................................. 17

Probe GUI ................................................................................................................................................................... 18

The Left Pane ...................................................................................................................................................... 19

The Right Pane .................................................................................................................................................... 21

The Toolbar Buttons ............................................................................................................................................ 22

Probe Configuration ................................................................................................................................................... 23

General Setup ..................................................................................................................................................... 23

Create New Group .............................................................................................................................................. 24

Create a Resource ............................................................................................................................................... 24

Create a Profile.................................................................................................................................................... 32

Launch the Message Pool Manager .................................................................................................................... 34

Rescan the Host .................................................................................................................................................. 36

Adding Monitors......................................................................................................................................................... 36

Add Monitors to be Measured ............................................................................................................................ 37

Edit Monitor Properties ...................................................................................................................................... 38

Enable QoS and Alarming for Monitors .............................................................................................................. 40

Error Codes ................................................................................................................................................................. 41

Enable IIOP on the Weblogic Server ........................................................................................................................... 42

Chapter 4: QoS Threshold Metrics 45

weblogic QoS Metrics ................................................................................................................................................. 45

6 weblogic Guide

weblogic Alert Metrics Default Settings ..................................................................................................................... 45

Chapter 1: weblogic 1.3 7

Chapter 1: weblogic 1.3

This description applies to weblogic probe version 1.3.

This section contains the following topics:

weblogic Overview (see page 7) Documentation Changes (see page 8)

weblogic Overview

The NMS weblogic monitoring probe has the capability to handle all the common monitoring and data collection tasks on WebLogic servers. The probe collects and stores data and information from the monitored system at customizable intervals. You can easily define alarms to be raised and propagated to the NMS console when the specified thresholds are breached.

weblogic Overview

8 weblogic Guide

Documentation Changes

This table describes the version history for the weblogic document.

Version Date What's New?

1.3 January 2013 ■ Added support for WebLogic version 12c.

■ Added support for WebLogic version 11g.

■ Added new mechanism of Mbean handling.

■ Added i18n and TNT2 support.

Related Documentation

Documentation for other versions of the weblogic probe

The Release Notes for the weblogic probe

Getting Started with CA Nimsoft® Probes

Monitor Metrics Reference Information for CA Nimsoft Probes


Chapter 2: weblogic Probe Deployment

This section contains the prerequisites, system requirements and deployment information for the weblogic probe.


Prerequisites (see page 9) Supported Platforms (see page 12) System Requirements (see page 12) Software Requirements (see page 13) Monitoring System Requirements (see page 13) Probe Deployment Information (see page 13) weblogic Installation Wizard (see page 14)

Prerequisites

The weblogic probe can be installed on either a server running WebLogic or on a remote computer.

For WebLogic version 9 and 10, you must enable IIOP on the WebLogic server. For more details, refer section Enable IIOP on the Weblogic Server (see page 42).

Any older version of the probe cannot be upgraded to version 1.3.

JVM

A Java Virtual Machine (JVM) of version 1.6 or higher must be installed on the computer running the WebLogic probe, and the PATH has to contain the java executable.

Check that Java (version 1.6 or higher) exists in the path on the computer hosting the probe as described below:

Note: If the probe does not start, you should check the probe log-file.

If the following lines appear in the log, it probably means that java is not installed, or it is not included in the path

'java' is not recognized as an internal or external command, operable program or batch file.

Prerequisites

10 weblogic Guide

Verify Java on Unix System

Follow these steps:

1. Open a shell as user root and go to opt/nimbus/bin.

2. Use the command java –version. The output should show that java version =>1.6 is installed.

3. Restart NMS to "read" the path by giving the two following commands in the shell:

./niminit stop

./niminit start

4. Open the Controller probe GUI in the Infrastructure Manager and click the Robot environment button.

5. Double-click Path in the list and verify that NMS has java included in the path.

Prerequisites


Verify Java on Windows System

Follow these steps:

1. Open a cmd window and use the command java –version. The output should show that java version =>1.6 is installed.

Note: If not found, you must manually place the java.exe in the path. This is done in the Control Panel > System > Advanced > Environment Variables. Run the command described above again.

2. When OK, open the Infrastructure Service Controller by selecting Programs > Nimsoft Monitoring > Infrastructure Service Controller.

3. Click Force Stop and then Start to enable NMS to include java in the path.

Supported Platforms

12 weblogic Guide

4. Open the Controller probe GUI in the Infrastructure Manager and click the Robot environment button.

5. Double-click Path in the list popping up and verify that NMS has java included in the path.

Supported Platforms

The weblogic probe supports the same set of operating systems and databases as supported by the Nimsoft Server solution. Please refer to the Nimsoft Compatibility Support Matrix for the latest information on supported platforms.

System Requirements

The weblogic probe should be installed on systems with the following minimum resources:

■ Memory: 2-4 GB of RAM. This probe OOTB configuration requires 256 MB of RAM.

■ CPU: 3 GHz dual-core processor, 32-bit or 64-bit.

http://support.nimsoft.com/downloads/doc/Compatibility_SupportMatrix_current.pdf

http://support.nimsoft.com/downloads/doc/Compatibility_SupportMatrix_current.pdf

Software Requirements


Software Requirements

The weblogic probe requires the following software environment:

■ WebLogic 9.x, 10.x, 11g and 12c

■ Nimsoft Monitor Server 5.1.1 or later

■ Nimsoft Robot 5.23 or later

■ Java Virtual Machine 1.6 or later (typically installed with NMS 5.0 and above)

Monitoring System Requirements

The weblogic monitoring probe has the capability to handle all the common monitoring and data collection tasks on WebLogic servers.

The following WebLogic Server entities may be monitored:

■ The Java Virtual machine (JVM).

■ Execution queues and threads.

■ Enterprise Java Beans (EJB).

■ Servlets and Java Server Pages (JSP).

■ Java Transaction API (JTA).

■ Java Database Connection Pools. (JDBC).

■ Java Messaging Services (JMS).

■ Java Connector Architecture (JCA).

Probe Deployment Information

There are two ways to distribute archive packages. You can distribute the package within Infrastructure Manager or use the standalone Nimsoft Distribution application.

See Probe Deployment for more information on deploying probes.

http://docs.nimsoft.com/prodhelp/en_US/Probes/GettingStarted/1931642.html

weblogic Installation Wizard

14 weblogic Guide


Follow these steps:

1. The first time you double-click the line representing the probe in the Infrastructure Manager after the probe has been distributed, the installation wizard automatically will be launched.

The Welcome picture appears on your screen.



2. Read the instructions and browse to the folders containing the Java executable and click the Next button.

Note: Only Java versions 1.6.x or higher are supported.

The Finish dialog validates the files. The first line should say ‘Requirements met!’

3. Click the Next button to finish the wizard.

If something goes wrong, the output listed in the window will have a red color, and the first line will state that the requirements was NOT met. In that case, you must click the Back button, check that you have the correct environment files and try again.

4. You will be asked to restart the probe to initialize the probe. Click the Yes button.


Chapter 3: weblogic Configuration

Businesses based on the Web depend on a high degree of quality and availability. It is therefore important that the security, availability and performance of the WebLogic servers are as high as possible. This is done by monitoring and managing the servers, components and services to ensure optimal performance.

The Nimsoft weblogic monitoring probe has the capability of handling all common monitoring and data collection tasks.

The probe collects and stores data and information from the monitored system at customizable intervals. You can easily define alarms to be raised and propagated to the Enterprise Console when the specified thresholds are breached.

Note: If making any configuration changes on the WebLogic server, you must restart the WebLogic server. Otherwise, the communication between the probe and the WebLogic server may be lost. Also note that IIOP must be enabled for WebLogic 9 and 10 (as described in the section Enable IIOP on the Weblogic Server (see page 42)).


Probe Configuration Interface Installation (see page 17) Probe GUI (see page 18) Probe Configuration (see page 23) Adding Monitors (see page 36) Error Codes (see page 41) Enable IIOP on the Weblogic Server (see page 42)

Probe Configuration Interface Installation

The probe configuration interface is automatically downloaded and installed by the Nimsoft Infrastructure Manager when the probe is deployed on a robot.

Probe GUI

18 weblogic Guide

Probe GUI

Double-click the line representing the probe in the Infrastructure Manager to bring up the GUI.

The GUI will initially appear as the one shown below: an empty group called Default Group and a QoS node containing some default QoS definitions.

You have to define what to monitor:

1. Start by creating a resource. This is described in the section Create a Resource (see page 24).

A resource is the computer in the cluster running the Network Node software.

2. Create one or more profiles. A profile is a cluster member.

Note that one profile will automatically be created under the resource created in the previous step.

To add more profiles, do as described in the section Create a Profile (see page 32).

Probe GUI


3. Add monitors to be measured. This is described in the section Add Monitors to be Measured (see page 37).

Note that you must click the Apply button to activate any configuration modifications done.

The window consists of a row of tool buttons and two window panes.

The Left Pane

The left pane shows the monitoring groups defined and the QoS definitions. During the initial probe configuration wizard, the Default group (with an underlying resource and one or more profiles) and the standard QoS definitions are created and will appear in the pane.

Group

Using groups makes the management easier when monitoring large configurations. You can create new groups by right-clicking a group and selecting New Group (or by clicking the Create New Group tool button).

■ Resources

A group contains one or more resources. A resource is a computer being monitored, identified with its hostname or IP address. You can create new resources by right-clicking a group and selecting New Resource (or by clicking the Create New Resource tool button)

Probe GUI

20 weblogic Guide

■ Profiles One or more profiles can be defined for each resource. You can create new profiles by right-clicking a Resource and selecting New Profile (or by clicking the Create New Profile tool button).

A profile is initially "empty" (contains no monitors). To add monitors, see the section Add Monitors to be measured (see page 37).

QoS

This node contains the standard QoS definitions included with the probe package. These can be selected when editing the monitoring properties for a monitor. To define your own QoS definitions, right-click the QoS node and select New.

Right-clicking in the pane opens a pop-up menu, giving you the following possibilities:

■ New Resource

Available only when a group, resource or profile is selected.

Opens the Resource dialog, enabling you to define a new resource to be monitored.

■ New Profile

Available only when a resource or a profile is selected.

Opens the Profile dialog, enabling you to define a new profile to be monitored.

■ New Group

Available only when a group, resource or profile is selected.

Creates a new group where you may place resources (with their underlying profiles and monitors) to be monitored. The new group will appear in the pane with the name New Group.

Right-click the new group and select Rename to give the group a name of your own choice.

To move a resource from one group to another, right-click the resource and select Edit to open the Resource dialog, where you may select the group you want the resource to belong to (see also the section Create a Resource (see page 24)).

■ Edit

Available only when a resource or profile is selected.

Lets you edit the properties for the selected element, depending what you have selected (resource, profile or QoS definition).

■ Delete

Lets you delete the selected element (group, resource, profile or QoS definition). Note that the Default group cannot be deleted, but if you remove all elements from the group, it will not appear the next time you restart the probe.

Probe GUI


The Right Pane

The contents of the right pane depend on what you select in the left pane:

■ QoS definitions when the QoS sub-node is selected in the left-pane.

■ Resources when a group is selected in the left-pane.

■ Profiles when a resource is selected in the left-pane.

■ Monitors when a profile is selected in the left-pane.

Right-clicking in the pane gives you the following possibilities:

■ When the QoS definitions are listed in the pane: Right-clicking in the list opens a small menu, giving you the possibility to add or delete a QoS definition.

■ When the resources are listed in the pane: Right-clicking in the list opens a small menu, giving you the following options:

■ New

Opens the Resource dialog, allowing you to define a new resource. Refer section Create a Resource (see page 24).

■ Edit

Opens the Resource dialog for the selected resource, allowing you to modify the properties. Refer section Edit Properties for a Resource (see page 31).

■ Delete

Deletes the selected resource.

■ Activate

Activates the selected resource.

■ Deactivate

Deactivates the selected resource.

■ When the profiles are listed in the pane: Right-clicking the list opens a small menu, giving you the following options:

■ New

Opens the Profiles dialog, allowing you to define a new resource. Refer section Create a Profile (see page 32).

■ Edit

Opens the Profiles dialog for the selected resource, allowing you to modify the properties. Refer section Create a Profile (see page 32).

■ Delete

Deletes the selected profile.

Probe GUI

22 weblogic Guide

■ Activate

Activates the selected profile.

■ Deactivate

Deactivates the selected profile.

■ When the monitors are listed in the pane: Right-clicking in the list opens a small menu, giving you the following options:

■ Edit

Opens the Monitor properties dialog for the selected monitor, allowing you to modify the properties.

■ Delete

Deletes the selected monitor.

■ Refresh

Refreshes the window to display the most current measured values for the monitors.

■ Monitor

Opens the monitor window and starts filling a graph with the values measured of the selected monitor.

The Toolbar Buttons

The configuration tool also contains a row of toolbar buttons:

Probe Configuration


■ General Setup (see page 23)

■ Create New Group (see page 24)

■ Create New Resource (see page 24)

■ Create New Profile (see page 32)

■ Message Pool Manager (see page 34)

■ Rescan for host (see page 36)

Probe Configuration

This section describes the configuration concepts and procedures for setting up the weblogic probe.

General Setup

Click the General Setup button to open the Setup dialog.

The Setup dialog contains the General and Environment tabs.

Probe Configuration

24 weblogic Guide

The fields in the above dialog are explained below:

General

Sets the level of details written to the log file. Log as little as possible during normal operation, to minimize disk consumption.

Environment

Reflects the folder containing the local Weblogic installation as defined during the probe installation wizard.

Create New Group

You may create a new group using this functionality.

Follow these steps:

1. Selecting the Create New Group button in the menu-bar.

The new group will appear in the pane with the name New Group.

2. Right-click the new group and select Rename to give the group a name of your own choice.

Create a Resource

You may create a resource using this functionality.

Follow these steps:

1. Select the group it should belong to and clicking the Create New Resource button on the toolbar.

A wizard will be launched, guiding you through the process of creating a resource.

Probe Configuration


2. The first dialog contains only information. Read the instructions in the dialog and click the Next button.

Probe Configuration

26 weblogic Guide

3. Specify the host name (or IP address) of the WebLogic server (later also called resource) to monitor and the port, which by default is 7001 and click the Next button to continue.

Probe Configuration


4. Specify a user name and password with administrative privileges to the WebLogic server and click the Next button to continue.

The probe now lists the clusters found on the host. If a standalone installation, this will be indicated in the list.

Probe Configuration

28 weblogic Guide

5. Select the one you want to monitor from the list and click the Next button to continue.

6. Select your managed servers.

The managed servers found are listed.

7. Select the servers (profiles) you want to add to the resource group. Select the Select All option to add all servers listed.

Probe Configuration


8. Click the Finish button to complete the wizard

9. Click the Apply button in the main window to activate your new resource.

Probe Configuration

30 weblogic Guide

The new resource should now appear in the left pane of the probe GUI. All node/server combinations detected during the Resource wizard will be listed as Profile child-nodes under the Profile node.

When selecting a profile, the WebLogic browser will appear as a tree-structure. The browser lists all monitors available in a tree structure. Selecting a folder in this tree-structure, the monitors found will be listed in the right pane of the probe GUI enabling you to select the ones you want to monitor.

Probe Configuration


Edit Properties for a Resource

You can edit the properties for a resource by right-clicking a resource and selecting Edit. This brings up the Resource dialog.


Name

Defines the name of the resource. By default, it is the same as the cluster. This field is read-only.

Active

Use this option to activate/deactivate monitoring of the resource.

Group

Specifies the group to which resource should belong.

Check interval

Defines how often the probe checks the values of the monitors on the resource.

Alarm message

Specifies the alarm message to be sent if the resource does not respond. Note that you can edit the message or define your own ones, using the Message Pool Manager.

Cluster

Defines the name of the cluster to monitor.

Probe Configuration

32 weblogic Guide

Host Information tab

User name and password

Defines the login user name and password for the probe to log on the resource, if necessary.

Host and port

Defines the IP address and port number of the administration server (as specified when the resource was created).

Advanced alarming tab

How many profiles must have a monitor in alarm state before an alarm is sent.

Defines the minimum number of profiles where the same monitor has exceeded the defined alarm threshold before an alarm is sent.

Note: This parameter can be individually overridden for each of the monitors by setting the Always alarm option in the Monitor Properties dialog.

Create a Profile

You may create a new profile by selecting the resource it should belong to and press the Create New Profile button in the menu-bar.

Probe Configuration


Normally all node/server combinations were detected and added during the resource wizard. You may also create new profiles by right-clicking a profile or a resource and selecting New Profile or edit the properties for an existing profile by right-clicking the profile and selecting Edit. This brings up the Profile dialog where the following properties can be edited.


Active

Allows you to activate/deactivate monitoring of the profile.

Name

Used to provide the new profile a unique and descriptive name. If you are editing the properties of an existing profile, this field is read-only.

Host

Specifies the IP address or hostname of the server in the cluster.

Resource

Specifies the resource to which the node/server belongs. If you are editing the properties of an existing profile, this field is read-only.

Port

Defines the port for administration. Default is 7001.

Alarm Message

Specifies the alarm message that will be sent if the profile does not respond.

Probe Configuration

34 weblogic Guide

Test button

Used to verify that the host specified responds.

If the newly defined node/server is not recognized, this is indicated with the following

symbol:

Launch the Message Pool Manager

Click the Message Pool Manager button in the toolbar to open the Message Pool.

The alarm messages for each alarm situation are stored in the Message Pool. Using the Message Pool Manager, you can customize the alarm text, and you may also create your own messages.

Note that variable expansion in the message text is supported. If you type ‘$’ in the Alarm text field, a dialog pops up offering a set of variables to be chosen:

■ Resource

The resource referred to in the alarm message.

Probe Configuration


■ Host

The host computer where the alarm condition occurs.

■ Port

The communication port on the host.

■ Profile

The name of the profile being monitored.

■ Node

The name of the node in the cluster.

■ Server

The name of the server in the cluster.

■ Monitor

The monitor (checkpoint) referred to in the alarm message.

■ Desc

The description of the monitor.

■ Key

The monitor key (normally the same as the name of the monitor).

■ Value

The value used in the alarm message.

■ Oper

The operand to be combined with the value and the threshold in the alarm message.

■ Thr

The alarm threshold defined.

■ Unit

The unit to be combined with the value in the alarm message (for example Boolean).

Adding Monitors

36 weblogic Guide

Rescan the Host

The weblogic probe automatically scans the profiles in the host server after a pre-configured interval (15 minutes) and loads any profiles available in the host server under the respective Resources nodes in the probe GUI.

If you wish to manually scan the profiles, click the Rescan for host button from toolbar.

A message appears informing the scan in progress.

If any of the profiles available in the host servers has not been added to weblogic probe, the profile is added from the probe GUI.

If all the profiles, currently available in the host server, are already loaded under the respective resources in the weblogic probe, the following message appears:

Adding Monitors

You can select additional monitors (checkpoints) to be monitored.

Adding Monitors


Add Monitors to be Measured

To select a monitor to be measured for a profile, select the desired folder in the left pane. The monitors found will be listed in the right pane of the probe GUI, enabling you to select the ones you want to monitor.

Selecting the Profiles node, all monitors currently being measured will be listed in the right pane. Note that you can also select/deselect monitors here.

Adding Monitors

38 weblogic Guide

Edit Monitor Properties

Edit the properties for monitor by right-clicking it in the window and selecting Edit.


Name

Defines the name of the monitor. The name will be inserted into this field when the monitor is fetched from the Weblogic browser, but you are allowed to modify the name.

Key

Indicates a read-only field, describing the monitor key.

Adding Monitors


Description

Provides a description of the monitor. This description will be inserted into this field when the monitor is fetched from the Weblogic browser, but you are allowed to modify it.

Value Definition

This drop-down list lets you select which value to be used, both for alarming and QoS:

You have the following options:

■ The current value: This means that the most current value measured will be used.

■ The delta value (current –previous): This means that the delta value calculated from the current and the previous measured sample will be used.

■ Delta per second: This means that the delta value calculated from the samples measured within a second will be used.

■ The average value of the last and current sample: (current + previous) / 2.

Active

Activates the monitoring of the probe.

Enable Monitoring

Selecting this option activates the monitoring.

Note: The monitor will also be selected in the list of monitors in the right window pane when this option is selected, and that you can enable/disable monitoring of the checkpoint from that list.

Operator

Specifies the operator to be used when setting the alarm threshold for the measured value.

Example:

=> 90 means alarm condition if the measured value is above 90.

= 90 means alarm condition if the measured value is exact 90.

Threshold

The alarm threshold value. An alarm message will be sent if this threshold is exceeded.

Unit

Specifies the unit of the monitored value.

(For example %, Mbytes etc.). The field is read-only.

Adding Monitors

40 weblogic Guide

Message Token

Specifies the alarm message to be issued if the specified threshold value is breached. These messages are kept in the message pool. The messages can be modified in the Message Pool Manager.

Key not found alarm

When this option is selected, an alarm will be sent if no key is detected. This may, for example, happen after a restart of the Weblogic server, where it takes some time before all monitors are restored.

Always alarm

When selected, a threshold breach for this monitor will result in an error message, independent of the value of this monitor on other profiles in the cluster. This overrides the option Advance Alarming on the Resource dialog.

Publish Quality of Service

Select this option if you want QoS messages to be issued on the monitor.

QoS Name

Specifies the name to be used on the QoS message issued.

Enable QoS and Alarming for Monitors

You can now see the current values for the monitors in the Values column in the monitor list of the GUI. To enable the probe to send QoS data and/or send alarms on threshold breaches, you have to modify the properties for each of the monitors. This is done by double-clicking a monitor (or right-clicking and selecting Edit), which brings up the monitor’s properties dialog. Refer Edit Monitor Properties (see page 38) section for details.

Error Codes


Error Codes

The error codes listed below may occur in the probe’s log file. This is available on right-clicking the probe in the Infrastructure Manager and selecting View Log. Error code 1500 and 1503 may also appear in the Weblogic browser window.

1500

Lost connection to the WebLogic server.

Not able to connect to the WebLogic server.

Subtext: The reason for the connection problem.

1501 and 1502

The given key (measurepoint) is not found on the server.

No subkeys found

When this message appears in the Weblogic browser window, it means that the key is currently not available.

Enable IIOP on the Weblogic Server

42 weblogic Guide


The following changes are required in WebLogic 9 and 10 to support the weblogic probe.

The changes are the same as needed for jConsole.

Follow these steps:

1. Open the AdminConsole for WebLogic server.

2. Select Environment > Server from the left panel.

3. Click the <server> link.

4. Click the Protocols > IIOP tab.



5. Click the Advanced link.

6. Enter the username and password for the IIOP connection:

7. The IIOP username and password are the same as given in the probe configuration.


44 weblogic Guide

8. Click Save.

It is necessary to restart the WebLogic server for the IIOP settings to take effect.

JAVA options

In addition, the following JAVA options have to be set for java.lang.MBean tree to be seen in the probe.

Windows

Set JAVA_OPTIONS=-Dcom.sun.management.jmxremote

-Dcom.sun.management.jmxremote.port=8888

-Dcom.sun.management.jmxremote.ssl=false

-Dcom.sun.management.jmxremote.authenticate=false

UNIX

JAVA_OPTIONS=-Dcom.sun.management.jmxremote

-Dcom.sun.management.jmxremote.port=8888

-Dcom.sun.management.jmxremote.ssl=false

-Dcom.sun.management.jmxremote.authenticate=false

export JAVA_OPTIONS

Note: The port 8888 is only an example, and the probe does not use the port. All access is through the 7001 port.

URLs

Refer to the following link for more details about monitoring and management using JMX:

http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html

http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html

Chapter 4: QoS Threshold Metrics 45

Chapter 4: QoS Threshold Metrics

Many Nimsoft Monitor probes ship with default QoS threshold values set. The default threshold values provide an idea of the type of values to be entered in the fields and are not necessarily recommended best practice values. To aid in tuning thresholds and reducing false-positive alarms, this section describes the QoS metrics and provides the default QoS thresholds.


weblogic QoS Metrics (see page 45) weblogic Alert Metrics Default Settings (see page 45)

weblogic QoS Metrics The following table describes the checkpoint metrics that can be configured using the weblogic probe.

Monitor Name Units Description

QOS_JAVA_HEAP_SIZE Bytes Java Heap Size

QOS_WEBLOGIC_CLASSLOADCOUNT Counter Counter

QOS_WEBLOGIC_CPU_USAGE Percent CPU Usage

QOS_WEBLOGIC_MEMORY_USAGE Kilobytes Memory in KB

QOS_WEBLOGIC_METHODCOUNT Number Number of calls

QOS_WEBLOGIC_THREADCOUNT Number Thread Counter

QOS_WEBLOGIC_TIME Seconds Measured time

weblogic Alert Metrics Default Settings

The following table describes the default settings for the weblogic metrics.

Alert Metric Error Threshold Error Severity Description

ClassLoadWarning - Minor Alarms to be issued when the classload value is above threshold.

CPUCritical - Critical Alarms to be issued when the CPU usage for monitor is above threshold.

weblogic Alert Metrics Default Settings

46 weblogic Guide

Alert Metric Error Threshold Error Severity Description

CPUWarning - Warning Alarms to be issued when the CPU usage for monitor is above threshold.

MemoryWarning - Minor Alarms to be issued when the memory usage for monitor is above threshold.

ConcurrentWaiters - Critical Alarms to be issued when the waiters for monitor is above threshold.

MethodCallsHigh - Major Alarms to be issued when the number of method calls for monitor is above threshold.

ThreadPoolHigh - Major Alarms to be issued when the used resources for monitor in the thread pool is too high.

ThreadPoolCritical - Critical Alarms to be issued when the used resources for monitor in the thread pool is above threshold.

MonitorWarning - Major Alarms to be issued when the monitor value exceeds the threshold value.

ProfileCritical - Critical Alarm to be issued when the profile is not responding.

ProfileWarning - Major Alarm to be issued when the profile is not responding.

ResourceCritical - Critical Alarm to be issued when the resource is not responding.

ResourceWarning - Minor Alarm to be issued when the resource is not responding.

Nimsoft Monitor weblogic Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/weblogic/1.3/... · 1.3 January 2013 Added support for WebLogic version 12c. Added support for WebLogic

Documents