JView 2004 Agent Installation Guide For WebLogic

JView 2004 Agent Installation for WebLogic
JView 2004 Agent Installation

Guide for WebLogic
Copyright 2004 - DevStream Corporation Page 1 of 31

The information in this document is subject to change without notice. If you find any problems in the
documentation, please report them to us in writing. DevStream Corporation does not warrant that this
documentation is error free. DevStream Corporation could make improvements and/or changes in the
products described in this documentation at any time without notice.
The customer acknowledges and agrees that (a) the System and all related documentation are confidential
trade secrets of DevStream Corporation and (b) title to and intellectual property rights in the System and
related documentation (including without limitation all copyright, trademark, trade secret and patent
rights) are and shall remain the confidential proprietary property and information of DevStream
Corporation.
The customer shall use the system only in accordance with this Agreement. The customer shall not
disclose, copy, or reproduce any portion of the system or documentation in any form to any third person
without the prior written consent of DevStream Corporation, nor allow third parties to do the same. The
customer shall keep the System and all confidential information in the strictest confidence.

1 Introduction.......................................................... 5
1.1 JView 2004 Enterprise Edition ..........................................5
1.2 JView 2004 Documentation ..............................................7
1.2.1 JView 2004 Installation Guide ........................................7
1.2.2 JView 2004 Agent Installation Guide for Application Servers 7
1.2.3 JView 2004 Users Guide................................................8
1.3 Purpose and Scope .........................................................8
1.4 Supporting Documents ....................................................8
1.5 Other DevStream Resources ............................................9
2 Overview of Installation ...................................... 10
2.1 JView 2004 Application Overview ...................................10
2.1.1 JView 2004 Agent ...................................................... 11
2.1.2 JView 2004 Nucleus Server (NS)................................... 11
2.1.3 JView 2004 Performance Console (PConsole) .................. 11
2.2 JView Terms and Definitions ..........................................12
2.3 System Requirements ...................................................14
2.3.1 Agent Requirements................................................... 14
2.4 Supported Platforms, Application Servers, JDKs, and
Databases ..........................................................................14
2.5 Order of Installation ......................................................15
3 Preparing for Installation .................................... 16
3.1 Information required before Install.................................16
3.2 Upgrading from Previous Versions ..................................16
4 Agent Installation Instructions for Windows ........ 17
4.1 Pre-Install ....................................................................17
4.2 JView Agent Installation ................................................17
5 Agent Installation Instructions for Solaris............ 19
5.1 Pre-Install ....................................................................19
6 Agent Installation Instructions for Linux.............. 21
6.1 Pre-Install ....................................................................21
7 Agent Installation Instructions for HP-UX ............ 23
7.1 Pre-Install ....................................................................23
8 Agent Installation Instructions for AIX................. 25
8.1 Pre-Install ....................................................................25
9 Agent Installation Instructions for Tru64 ............. 27

9.1 Pre-Install ....................................................................27
10 Troubleshooting ................................................ 29
10.1 Agent .........................................................................29
11 Assistance......................................................... 31
11.1 DevStream Customer Support .....................................31

1 Introduction
DevStream delivers J2EE performance tuning solutions, from JView 2004 Enterprise
Edition to professional service consulting for performance tuning.
JView 2004 Enterprise Edition is a comprehensive performance monitoring tool

designed to help customers quickly detect bottlenecks in their performance of Java
custom code and J2EE-driven applications. JView 2004 helps organizations accelerate
their debug time, reduce and manage overall costs, and customize their production
performance monitoring as their business needs change over time.
JView uses JavaScape technology (Patent Pending) - a technology which provides a

detailed visual landscape display of J2EE Component-based performance metrics,
J2EE component interactions, and analysis of performance short-comings.
1.1 JView 2004 Enterprise Edition

DevStream's JView 2004 Enterprise Edition is an advanced J2EE production
performance monitoring and Java Application Performance Management solution.
JView 2004 obtains precise real-time method CPU time and transaction time, JVM
Heap memory usage, as well as SQL metric data in an easy-to-use interface.
JView 2004 is the industry's only Production Ready native code Java Performance
Monitor, allowing for in-depth Production Java performance monitoring due to its low
overhead. JView 2004 delivers full spectrum analysis of method metric transaction
time and method CPU time, along with thread stack views and SQL runtime
statistics.
In production mode, JView's low overhead monitoring provides detail on end-to-end

transactions, helping J2EE developers, QA testers, and Administrators quickly
pinpoint and resolve performance issues.
You can benefit from JView 2004 Enterprise Edition in the following ways:
• Accelerate solution time. Organizations can more quickly realize a

return on their investment since they do not have to spend time researching
where the performance bottlenecks are. Customers will spend more time
getting the problems fixed instead of using all of their resources to track them
down.

• Reduce likelihood of production downtime. The visual landscape and

component interaction map can be configured to throw alarms, such as
sending of a page or email, to alert administrators of degraded performance,
resource starvation, hung transactions, system response time issues, or the
approach of system transaction capacity.
• Meet your SLA's. Companies can feel confident that they can meet their
Service Level Agreements by using JView's configurable SLA Monitoring View.
Key Features and Benefits of JView 2004:

• Real-time monitoring
• Landscape view of J2EE Components
• SNMP v2/v3 support for Enterprise Application Monitor Integration
• Precision Call Trace Analysis
• Microsecond Precision for demanding applications
• SLA Monitoring and Automated Operational Awareness Alerts
• SQL Call statistics
• CPU Thread time statistics
• Thread stack analysis and Stalled Thread alerts
• MReports - Reporting of problematic components
• PerfPoint - Collect detailed data in Production for problem analysis
• Easy-to-use Performance Console - Install and begin tuning in minutes.
• Transaction Exp lorer - Drill down into where your application is spending
Transaction time and CPU
• Transaction Scope – Review an individual transaction through the server,
obtaining stack trace, URL, username, and more
• Isolated resource consumption using Method and SQLyzer HotSpot Views
• Supports J2EE Application Servers as well as stand-alone applications
• Identify performance issues proactively before they impact users

1.2 JView 2004 Documentation

1.2.1 JView 2004 Installation Guide
The JView 2004 Installation Guide is intended as a first point of reference when
installing the JView Nucleus Server (NS), Agent, and Performance Console. This
guide is intended to be used by system administrators or J2EE developers. This
document will walk you through the following:
• Overview of the JView 2004 System Architecture
• System Requirements
• Pre-Installation Instructions
• Installation Instructions for Windows, UNIX (Solaris, HP-UX, AIX and Tru64),
and Linux for each of the JView components
• First-Use Application Launch Instructions
• Upgrade Instructions
1.2.2 JView 2004 Agent Installation Guide for

Application Servers
There is a vendor specific JView 2004 Agent Installation Guide for each of the
application servers that are officially supported by DevStream’s JView. Each of these
documents is intended to supplement the general JView 2004 Installation Guide for
those customers who wish to run the JView Agent in an Application Server
environment. The document includes the following information:
• Overview of the JView 2004 System Architecture
• System Requirements
• JView 2004 Agent Installation instructions are available for the following
Application Servers:
o WebLogic 6.x, 7.x, 8.x
o WebSphere 5.x
o Oracle 9iAS/10iAS
o Orion Server
o JBoss 3.x, 4.x
o SunOne 6.x, 7.x
o JRun 4.x
o Tomcat 3.x, 4.x, 5.x
o Caucho Resin 2.x

1.2.3 JView 2004 Users Guide
The JView 2004 Users Guide will assist you in configuring JView to meet your J2EE
Performance Monitoring needs. The guide includes:
• Detailed description of Performance Console Views and configuration of each
• Agent Configuration Options
• Tuning your Application using JView 2004
• Capacity Planning Using JView 2004
• JView 2004 MReports
• SLA Monitoring using JView 2004
• Custom Reporting using JView Database schema design and descriptions
• Configuring Users and Groups
1.3 Purpose and Scope

The purpose of this Agent Installation Guide for WebLogic is to ensure successful
installation of the JView 2004 Agent for use on a WebLogic Application Server. This
guide includes detailed instructions for installing the JView 2004 Agent, but will not
cover the Nucleus Server or Performance Console installation. Installation of the
JView Agent is detailed for the following operating systems: Windows (all versions),
Solaris, Linux, HP-UX, AIX, and Tru64.
This Agent Installation Guide for WebLogic is intended to be used by systems

administrators and/or developers or support personnel who are familiar with the
overall environment and have access to install software on the WebLogic Application
Server(s) in the environment.
For instructions on Nucleus Server or Performance Console installation, please refer

to the JView 2004 Installation Guide. Please note: the Nucleus Server should be
installed prior to the Agent installation.
1.4 Supporting Documents

Additional assistance and technical documentation can be found by going to the
DevStream online help web pages. http://www.devstream.com/help
For instructions on Nucleus Server or Performance Console installation, please refer

to the JView 2004 Installation Guide. Please note: the Nucleus Server should be
installed prior to the Agent installation.
DevStream provides additional Agent Installation Guides for the following Application
Servers: WebLogic, WebSphere, Oracle 9iAS/10iAS and Orion Servers, JBoss,
SunOne, JRun, Tomcat, and Caucho Resin.

1.5 Other DevStream Resources

Other resources you may find helpful include:
• Online product demo – the online demo provides a walk-through of JView’s

features and functionality and can be viewed at any time by going to
http://www.devstream.com/JView2004/demo
• JView 2004 Product Brief – download the JView 2004 Product Brief to
easily distribute and summarize the benefits and features of JView to the rest
of your team members.
http://www.devstream.com/JView2004/JView2004Brief.pdf
• Release Notes – find out what’s new in each version by going to

http://www.devstream.com/JView2004/releasenotes.html
• Frequently Asked Questions (FAQs) – if you still have questions, try

looking at our online FAQs at http://www.devstream.com/support/FAQ.html
• DevStream Support – You may email our support team at

support@devstream.com. Customers with active support contracts may
login to the DevStream Customer Center and search/file support cases.

2 Overview of Installation
This document describes the procedures to successfully install the JView 2004 Agent
on a WebLogic Application Server. For detailed instructions on Nucleus Server and
Performance Console installation, please read the JView 2004 Installation Guide for
BEFORE completing these instructions.
NOTE: If you are upgrading from a previous version of JView, please refer to
“Upgrading from a Previous Installation” under the “Preparing for Installation”
section of this document.
2.1 JView 2004 Application Overview

The JView 2004 Java monitoring solution is comprised of 3 components:
• JView 2004 J2EE Monitor Agent
• JView 2004 Nucleus Server (NS)
• JView 2004 Performance Console
Figure 1: JView 2004 Architecture Diagram

2.1.1 JView 2004 Agent

The JView 2004 Agent runs inside your Application Server's JVM, obtaining
performance metrics at low cost using Dynamic Bytecode Instrumentation. The JView
Agent sends this data, in real-time, back to the Nucleus Server, where the data is
stored and distributed to JView 2004 Performance Consoles.
Additionally, the agent obtains hardware CPU and JVM memory data. Unique to
JView 2004 is the calculation of the agent's overhead, displayed in the Performance
Console, to assist you in instrumentation configuration decisions.
2.1.2 JView 2004 Nucleus Server (NS)

The JView 2004 Nucleus Server (NS) is the central point for data retrieval and
storage in JView 2004. The NS receives data from JView 2004 Agents and makes this
data available to JView Performance Consoles. The NS also makes analyzed data
available to the Operational Alert Server (within the NS), which monitors and reports
on configured Server Level Agreement (SLA) watches.
The NS can also be configured to store data in the JView Enterprise database. This
allows historical reports to be generated via JView MReports, providing metric data
reports in multiple formats including HTML, XML, and PDF.
2.1.3 JView 2004 Performance Console

(PConsole)
The JView 2004 Performance Console (PConsole) is the main delivery point of JView
2004 data. The JView 2004 PConsole connects directly to the JView 2004 NS to
obtain method metric and SQL data, along with JVM and cluster node information. It
can also connect directly to the MReports database for reporting capability, as well as
opening historical session data.

2.2 JView Terms and Definitions

For ease of use of the JView application, you are encouraged to review this list of
common terms used throughout the JView application and documentation, including
this Installation Guide.
Table 1: GLOSSARY OF COMMON TERMS
Performance Point - Performance Point allows for the on-demand collection of

Method and CPU metric data on all of your classes. This dynamic parameter can
allow you to drill-down on a performance issue during production, while allowing you
to turn off the associated overhead during normal monitoring. By turning PerfPoint
on, you are enabling Dev Mode.
Dev Mode - During development testing, PerfPoint DevMode allows

continuous capture of detailed method stack statistics enabling you to fully
performance profile your Java code.
Prod Mode - In Production Mode, your J2EE components, or End-To-End user

transactions, are monitored, including JSPs, Servlets, Session, Entity, and
Message Driven EJB's, as well as SQL.
PerfPoint - In Production Mode, PerfPoint DevMode allows on-demand detail

for a specific short interval (15-45 seconds) for detailed method stack
statistics enabling you to fully performance profile your Java code. This is
useful when you have a performance issue in production and need to obtain
low-level data.
Nucleus Server – The Nucleus Server is the middleware component of JView 2004
Enterprise Edition. The JView 2004 Nucleus Server (NS) is the central point for data
retrieval and storage in JView 2004. The NS receives data from JView 2004 Agents
and makes this data available to JView Performance Consoles, while also storing the
data in the MReports/Historical database.
JView Agent - The JView 2004 Agent runs within inside your Application Server's
JVM, obtaining performance metrics at low cost using dynamic Bytecode
instrumentation.
PConsole - The JView 2004 Performance Console (PConsole) is the main delivery
point of JView 2004 data. The JView 2004 PConsole connects directly to the JView
2004 NS to obtain method metric and SQL data, along with JVM and cluster node
information. The PConsole contains 7 views, defined below:
JavaScape View - The JavaScape view uses JavaScape - a patent-pending

technology which paints a landscape view of your J2EE environment. This
view displays component interactions between JSPs, Servlets and
WebServices, Session, Entity, and Message-Driven beans as well as database
usage.

JLinks - Lines are drawn between components which were executed in
the same thread from a parent method. These J2EE links grow thicker
as throughput is increased between the object component interactions.
JavaScape by Thread View - The JavaScape by Thread view enables you to

perform Java Thread analysis and quickly determine how long a particular
request has been active. Additionally, you'll be able to identify the J2EE
component thread stack of that thread. This can help debug where long-
running transactions are spending their time.
Transaction Explorer View - The Transaction Explorer view displays

method and SQL time calls in tree format. This lets you easily drill-down and
discover the call stack for problematic methods. The tree is organized in
largest consumers, from top to bottom. The tree can be sorted by CPU or
Transaction time period.
Transaction Scope View - The Transaction Scope View gives a detailed view
on each individual transaction that runs through your application. This will
allow you to trace specific users, IP addresses, and Request URL's, helping
you troubleshoot a specific issue by understanding the code path that a
particular request took.
Method Hot Spot View - The Method Hot Spot view lets you quickly take a
look at the biggest consumers in your application. The view can be sorted by
a number of data points. The Method Hot Spot view will enable you to
execute Java Performance tuning at ease, as you easily determine which
method is consuming your resources.
SQLyzer Hot Spot View - The SQLyzer Hot Spot view lets you quickly
pinpoint largest SQL consumers in your application, providing the SQL query
itself, runtime statistics, and whether or not the SQL statement was prepared.
SLA Monitoring View - The SLA Monitoring view displays currently

configured SLA rules. Note that the Nucleus Server, via the Operational Alert
Server, is also monitoring your SLA's, and will respond to any SLA violations.
MReports - JView 2004's internal method and SQL metric reporting tool. MReports
can produce reports such as: Agent Node CPU and/or Heap, Top Ten Methods, Top
Ten JSPs, Top Ten Servlets, etc.
MReports Database - The MReports database is populated by the Nucleus Server,

for reporting purposes. This database is also used for historical session retrieval.
Operational Awareness Alert - The JView 2004 Nucleus Server runs the
Operational Awareness Alert (OAA) Server, where your custom SLA's are monitored
and custom actions are initiated. The OAA Server can send alerts to email or pager,
log violations to a database and/or file, as well as execute custom commands.

2.3 System Requirements

2.3.1 Agent Requirements
The JView 2004 Agent runs within the monitored application server JVM. As such, the
following requirements are for the node on which you will run the monitored
application on:
• 100 MB of memory
• 5 MB of disk space
2.4 Supported Platforms, Application

Servers, JDKs, and Databases
To guarantee top performance of your JView 2004 Application, please read through
the following list of certified Application Servers, Operating Systems, Databases, and
JDK versions. If your environment runs on any of the above that is not yet certified,
please contact DevStream Support to work through any issues you may encounter
and to inquire about the product certification schedule.
Table 2: SUPPORTED ENVIRONMENTS
Operating Windows NT 4.0, Windows 2000 Professional, Windows 2000 Server,

Systems Windows XP Professional, Windows 2003 Server, Linux x86, Solaris 8
SPARC, Solaris 9 SPARC, HP-UX 11i PA-RISC 2.0, AIX 5, Tru64
Application BEA Weblogic 8.x, 7.x, 6.x,

Servers WebSphere 5.x
Sun One Application Server 7.x, 6.x
Oracle 10.x, 9.x iAS (On Sun/IBM JRE)
Caucho Resin 2.x
JBoss 4.x, 3.x
JRun 4.x
Apache Tomcat 5.x, 4.x, 3.x
Database Oracle 9.x, 8.x (Oracle and Weblogic Oracle jDrivers are supported)
Servers DB2 8.x
MS SQL Server 7.0, 2000
MySQL 3.x, 4.x
JDK 1.2 Sun 1.2.2_17/_017, Sun 1.2.2_16/_016, Sun 1.2.2_15/_015,

Sun 1.2.2_14/_014, Sun 1.2.2_14/_014, Sun 1.2.2_012,
Sun 1.2.2_011, Sun 1.2.2_010, Sun 1.2.2_009, Sun 1.2.2_008,
Sun 1.2.2_007, Sun 1.2.2_006, Sun 1.2.2_005, Sun 1.2.2_004

JDK 1.3 Sun/HP/IBM 1.3.1_08, Sun/HP/IBM 1.3.1_07, Sun/HP/IBM 1.3.1_06,
Sun/HP/IBM 1.3.1_05, Sun/HP/IBM 1.3.1_04, Sun/HP/IBM 1.3.1_03,
Sun/HP/IBM 1.3.1_02, Sun/HP/IBM 1.3.1_01a, Sun/HP/IBM 1.3.1_01,
Sun/HP/IBM 1.3.1, Sun 1.3.0_05, Sun 1.3.0_04, Sun 1.3.0_03,
Sun 1.3.0_02, Sun 1.3.0_01, Sun 1.3.0
JDK 1.4 Sun/HP/IBM 1.4.2_01, Sun/HP/IBM 1.4.2, Sun/HP/IBM 1.4.1_05,

Sun/HP/IBM 1.4.1_01, Sun/HP/IBM 1.4.1, Sun/HP/IBM 1.4.0_04,
Sun/HP/IBM 1.4.0, BEA JRockit 1.4.2, BEA JRockit 8.1, BEA JRockit 8.0
MReports Oracle 9.x, 8.x

Databases MySQL 3.x, 4.x
2.5 Order of Installation

The Nucleus Server(s) should be installed first. After the NS has successfully started
up, the JView Agent(s) and Performance Consoles can be installed next in either
order, keeping in mind that you will not be able to connect to or display data in the
PConsole until one or more Agents have been installed to collect the data. For
installation of the Nucleus Server, please refer to the JView 2004 Installation Guide.

3 Preparing for Installation

Prior to installing JView 2004 in your environment(s), you will want to take the time
to architect where best to place each of the components. It is important to have to
proper resources allocated to the stand-alone components such as the Nucleus
Server and MReports database.
3.1 Information required before Install

You’ll want to setup a separate Nucleus Server and MReports database for each
application type that you monitor. This allows reports to be created for specific
applications as well as ensures enough processing power is available for each
application’s Nucleus Server.
For each Nucleus Server, you’ll need to identify how many agent licenses will be
required to support the expected number of Agent/Nodes/CPUs for your application.
Once you have determined which applications should be monitored, walk through the
following steps with the architecture group:
1. Determine number of applications to be monitored.

2. Determine number of agent licenses per application (that is, the number of
CPUs per host * the number of hosts which serve that application).
Remember – JView 2004 agent licenses are by host, not by JVM.
3. Determine how many and where to place the Nucleus servers. For each
application, you’ll likely desire a single Nucleus Server. If you have greater
then 8 hosts for a specific application, you may want to consider multiple
Nucleus Servers.
4. Determine where to place the MReports database. An MReports database
schema is unique to a single Nucleus Server. 2 Nucleus servers must store
data in 2 separate MReports schemas.
5. SNMP Port Number – identify if there are any running SNMP Agents on the
host where the Nucleus Server(s) will run. If so, determine how you will
resolve the default port conflict of 161 (you can edit this in the Nucleus
Server configuration, or change the conflicting agent’s port).
6. SNMP Trap information – you should determine where (if at all) SNMP traps
will be send for SLA Violations.
7. SMTP Configuration – identify which SMTP server you will route your JView
Operational Awareness Alerts (for SLA Violation notifications). Identify if this
SMTP server requires authentication.
3.2 Upgrading from Previous Versions

If you are upgrading from a previous version of JView 2004, you can install directly
over the existing installation and your configuration files will be preserved. You will
need to recreate the MReports database, as the schema will have changed. Simply
run the MReports installation as normal (it will drop existing tables and recreate
them).

4 Agent Installation Instructions

for Windows
In order to install JView 2004 Agent you need to register and download the latest
JView installation executable from www.devstream.com/downloads. For any
components to be installed on a Windows server, please follow these steps:
4.1 Pre-Install
• Determine which Application Servers to install the Agent on. We suggest you
follow the pre-installation steps under the “Preparing for Installation” section
above.
• Ensure that your selected hosts meet the System Requirements (see “System
Requirements” and “Supported Platforms, Application Servers, JDKs, and
Databases” above).
4.2 JView Agent Installation

NOTE: This JView 2004 Agent Installation Guide for WebLogic provides
instructions for installing the JView 2004 Agent on WebLogic Application Server only.
The JView 2004 Agent runs within inside your Application Server's JVM. In order to
do so, you must make available the JView 2004 agent library (both native and Java
library). Once the Agent has been installed correctly, it will automatically run next
time you start up your application’s JVM.
To install the JView 2004 Agent on WebLogic applications:
• Install the JView 2004 download onto your Java application’s host.
o You may also simply copy the agent directory from <Your JView 2004
Install Dir>/agent to your Java Application server's file system.
• Edit your JVM's startup .bat file’s java startup command:
o Add the location of the <JView Install Dir>\agent\windows to the PATH.
• If you are setting the Java system property -Djava.library.path environment, add
the location of the <JView Install Dir>/agent/windows to the -Djava.library.path
variable.
• Add "-Xbootclasspath/a:<JView Install Dir>/agent/lib/JViewAgent.jar -
XrunJView:server=<IP of Nucleus Server>,port=4445,agentname=<MyAgent>"
directly after the "java" command (Note: replace tags with real data).

Example Windows Bat File for Weblogic 8.x
##################################################
### JVIEW 2004 EXAMPLE FOR WEBLOGIC 8.X ON WINDOWS
### Please change variables as necessary
##################################################
echo on
set BEA_HOME=C:\bea
set WL_HOME=%BEA_HOME%\weblogic81
set JAVA_HOME=%BEA_HOME%\jdk141_02
set PATH=%PATH%;%WL_HOME%\server\bin\oci920_8
set CLASSPATH=%CLASSPATH%;%WL_HOME%\server\lib\xerces.jar;
%WL_HOME%\server\lib\weblogic.jar;
set JAVA_OPTIONS=-ms256m -mx1024m
set SERVER_NAME=examplesServer
set WLS_USER=weblogic
set WLS_PW=weblogic
REM ######## START JVIEW 2004 ADDITION #######

set JVIEW_HOME=C:\jview2004_2.1
set PATH=%JVIEW_HOME%\agent\windows;%PATH%
REM ######## END JVIEW 2004 ADDITION #######
"%JAVA_HOME%\bin\java" -
Xbootclasspath/a:%JVIEW_HOME%/agent/lib/JViewAgent.jar -
XrunJView:server=127.0.0.1,port=4445,agentname=examplesServer
%JAVA_OPTIONS% -Dweblogic.Name=%SERVER_NAME%
-Dweblogic.management.username=%WLS_USER%
-Dweblogic.management.password=%WLS_PW%
-Dweblogic.ProductionModeEnabled=%PRODUCTION_MODE%
-Djava.security.policy="%WL_HOME%\server\lib\weblogic.policy"
weblogic.Server


for Solaris
In order to install JView 2004 you need to register and download the latest JView
installation executable from www.devstream.com/downloads. For any components
to be installed on a UNIX Solaris server, please follow these steps:
5.1 Pre-Install
above.

• Edit your JVM's startup shell file’s java startup command:
o Add the location of the <JView>/agent/solaris to the LD_LIBRARY_PATH.
the locat ion of the <JView Install Dir>/agent/solaris to the -Djava.library.path
variable.

Example Solaris Shell File for Weblogic 8.x
##################################################
### JVIEW 2004 EXAMPLE FOR WEBLOGIC 8.X ON SOLARIS
##################################################
BEA_HOME=/opt/bea
WL_HOME=$BEA_HOME/weblogic81
JAVA_HOME=$BEA_HOME/jdk141_02
PATH=$PATH:$WL_HOME/server/bin/oci920_8
CLASSPATH=$CLASSPATH:$WL_HOME/server/lib/xerces.jar:$WL_HOME/server/lib
/weblogic.jar
JAVA_OPTIONS="-ms256m -mx1024m"
SERVER_NAME=examplesServer
WLS_USER=weblogic
WLS_PW=weblogic
######## START JVIEW ADDITION #######

JVIEW_HOME=/opt/jview2004
export LD_LIBRARY_PATH=$JVIEW_HOME/agent/solaris:$LD_LIBRARY_PATH
######## END JVIEW ADDITION #######
$JAVA_HOME/bin/java -
Xbootclasspath/a:$JVIEW_HOME/agent/lib/JViewAgent.jar -
$JAVA_OPTIONS -Dweblogic.Name=$SERVER_NAME
-Dweblogic.management.username=$WLS_USER
-Dweblogic.management.password=$WLS_PW
-Dweblogic.ProductionModeEnabled=$PRODUCTION_MODE
-Djava.security.policy="$WL_HOME/server/lib/weblogic.policy"
weblogic.Server


for Linux
to be installed on a Linux server, please follow these steps:
6.1 Pre-Install
above.

o Add the location of the <JView>/agent/linux to the LD_LIBRARY_PATH.
the location of the <JView Install Dir>/agent/linux to the -Djava.library.path
variable.

Example Linux Shell File for Weblogic 8.x
##################################################
### JVIEW 2004 EXAMPLE FOR WEBLOGIC 8.X ON Linux
##################################################
BEA_HOME=/opt/bea
/weblogic.jar
WLS_USER=weblogic
WLS_PW=weblogic

export LD_LIBRARY_PATH=$JVIEW_HOME/agent/linux:$PATH
weblogic.Server


for HP-UX
to be installed on a UNIX HP-UX server, please follow these steps:
7.1 Pre-Install
above.

• Install the JView 2004 download onto your Java applic ation’s host.
o Add the location of the <JView>/agent/hpux11 to the SHLIB_PATH, in
addition to the /usr/lib.
the location of the <JView Install Dir>/agent/hpux to the -Djava.library.path
variable.

Example HP- UX Shell File for Weblogic 8.x
##################################################
### JVIEW 2004 EXAMPLE FOR WEBLOGIC 8.X ON HPUX 11
##################################################
BEA_HOME=/opt/bea
export SHLIB_PATH=$SHLIB_PATH:$WL_HOME/server/bin/oci920_8
/weblogic.jar
WLS_USER=weblogic
WLS_PW=weblogic

SHLIB_PATH=$JVIEW_HOME/agent/hpux11:/usr/lib:$SHLIB_PATH
weblogic.Server


for AIX
to be installed on a UNIX AIX server, please follow these steps:
8.1 Pre-Install
above.

o Add the location of the <JView>/agent/aix5 to the LIBPATH.
• Add the "export AIXTHREAD_ENRUSG=ON" in your startServer script.
the location of the <JView Install Dir>/agent/aix to the -Djava.library.path
variable.

Example AIX Shell File for Weblogic 8.x
##################################################
### JVIEW 2004 EXAMPLE FOR WEBLOGIC 8.X ON AIX
##################################################
BEA_HOME=/opt/bea
/weblogic.jar
WLS_USER=weblogic
WLS_PW=weblogic

export LIBPATH=$JVIEW_HOME/agent/aix5:$LIBPATH
export AIXTHREAD_ENRUSG=ON
weblogic.Server


for Tru64
to be installed on a UNIX Tru64 server, please follow these steps:
9.1 Pre-Install
above.

o Add the location of the <JView>/agent/tru64 to the LD_LIBRARY_PATH.
the location of the <JView Install Dir>/agent/tru64 to the -Djava.library.path
variable.
• Add "-Xbootclasspath/a:<JView Install Dir>/agent/tru64/Tru64JViewAgent131
(or 141 depending on your VM Version).jar -DJViewParams=server=<IP of
Nucleus Server>,port=4445,agentname=<MyAgent>" directly after the "java"
command (Note: replace tags with real data).

Example Tru64 Shell File for Weblogic 8.x
##################################################
### JVIEW 2004 EXAMPLE FOR WEBLOGIC 8.X ON TRU64
##################################################
BEA_HOME=/opt/bea
/weblogic.jar
WLS_USER=weblogic
WLS_PW=weblogic

export LD_LIBRARY_PATH=$JVIEW_HOME/agent/tru64:$LD_LIBRARY_PATH
Xbootclasspath/a:$JVIEW_HOME/agent/tru64/Tru64JViewAgent131.jar -
DJViewParams=server=127.0.0.1,port=4445,agentname=examplesServer
weblogic.Server

10 Troubleshooting
If you should run into issues with the installation of any the Agent, please use these
frequently asked questions or contact a DevStream support representative to assist
you.
10.1 Agent
An error occurred during initialization of VM - Could not find -Xrun
library: JView.dll
The JView.dll is not set in your application's startup script's PATH. If you are having
difficulty setting your PATH following the instructions in the Installation Guide, you
can set this at your system level in Windows via your System's Environment
Variables (Under Control Panel - > System -> Advanced). You may need to restart
windows for this setting to take affect.
I am receiving message: "java.lang.NoClassDefFoundError:

com/dstream/jview/MethodTimer"
Check the "-Xbootclasspath/a:$JVIEW_PATH/agent/lib/JViewAgent.jar" option (or

%JVIEW_PATH% for windows). The JViewAgent.jar path needs to be in the
bootclasspath (otherwise you will receive the "java.lang.NoClassDefFoundError"
error).
Could not find -Xrun library: JView.so (Linux/Solaris)
There are two possibilities for why this error appears:
A. The JView.so is not in your LD_LIBRARY_PATH for your application's startup

script.
B. JView dependant libraries are not in your LD_LIBRARY_PATH. You can
determine what the dependant libraries are by executing "ldd JView.so" in the
same directory of the JView.so file (the <install>/agent/your_os). Ensure that
the dependencies are also added into the LD_LIBRARY_PATH in your
application's startup script.

Could not find -Xrun library: JView.a (AIX)
A. The JView.a is not in your LIBPATH for your application's startup script.
B. JView dependant libraries are not in your LIBPATH. You can determine what
the dependant libraries are by executing "ldd JView.a" in the same directory
of the JView.a file (the <install>/agent/aix5). Ensure that the dependencies
are also added into the LIBPATH in your application's startup script.
Could not find -Xrun library: JView.sl (HP-UX)
A. The JView.sl is not in your SHLIB_PATH for your application's startup script.
B. JView dependant libraries are not in your SHLIB_PATH. You can determine
what the dependant libraries are by executing "ldd JView.sl" in the same
directory of the JView.sl file (the <install>/agent/hpux11). Ensure that the
dependencies are also added into the SHLIB_PATH in your application's
startup script.
How do I configure my application server to run with JView 2004?
Please refer to the Agent Installation Guide for you specific application server.
Can I run multiple application servers using JView 2004?
JView 2004 has built-in cluster capability. You can monitor multiple application
servers with one Nucleus Server, and one Performance Console. During agent
configuration, you can set an Agent Name, which will identify each server uniquely.
How much memory does the JView 2004 Agent require?
The JView 2004 Agent has a very light memory footprint. Applications will typically
experience less than 10 MB of overhead.
How much CPU overhead does the JView 2004 Agent cause?
JView 2004 is the only leading production monitor that displays estima ted overhead.
In production mode, most customers experience < 2% overhead. This overhead
depends on your configuration and instrumentation options, along with your
application's code path. In PerfPoint (Development) mode, most applications will
incur 20-30% overhead, using the out-of-box configuration. (PerfPoint collects
detailed statistics on each of your custom classes.) Instrumentation options can lead
to less/more overhead, depending on configuration.

11 Assistance
11.1 DevStream Customer Support
You may email our support team at support@devstream.com. Customers with
active support contracts may login to the DevStream Customer Center and
search/submit support cases. For Platinum Support customers, you may reach
support at (877) DEV-STREAM ext. 2.
DevStream Corporation
4164 Austin Bluffs Pkwy Ste 230
Colorado Springs, CO 80918
(877) DEV-STREAM (338-7873)
support@devstream.com

JView 2004 Agent Installation Guide For WebLogic

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

JView 2004 Agent Installation Guide For WebLogic

Загружено:

Авторское право:

Доступные форматы

JView 2004 Agent Installation for WebLogic

JView 2004 Agent Installation

Copyright 2004 - DevStream Corporation Page 1 of 31

Copyright 2004 - DevStream Corporation Page 2 of 31

Copyright 2004 - DevStream Corporation Page 3 of 31

Copyright 2004 - DevStream Corporation Page 4 of 31

JView 2004 Enterprise Edition is a comprehensive performance monitoring tool

JView uses JavaScape technology (Patent Pending) - a technology which provides a

1.1 JView 2004 Enterprise Edition

In production mode, JView's low overhead monitoring provides detail on end-to-end

• Accelerate solution time. Organizations can more quickly realize a

Copyright 2004 - DevStream Corporation Page 5 of 31

• Reduce likelihood of production downtime. The visual landscape and

Key Features and Benefits of JView 2004:

Copyright 2004 - DevStream Corporation Page 6 of 31

1.2 JView 2004 Documentation

1.2.2 JView 2004 Agent Installation Guide for

Copyright 2004 - DevStream Corporation Page 7 of 31

1.3 Purpose and Scope

This Agent Installation Guide for WebLogic is intended to be used by systems

For instructions on Nucleus Server or Performance Console installation, please refer

1.4 Supporting Documents

For instructions on Nucleus Server or Performance Console installation, please refer

Copyright 2004 - DevStream Corporation Page 8 of 31

1.5 Other DevStream Resources

• Online product demo – the online demo provides a walk-through of JView’s

• Release Notes – find out what’s new in each version by going to

• Frequently Asked Questions (FAQs) – if you still have questions, try

• DevStream Support – You may email our support team at

Copyright 2004 - DevStream Corporation Page 9 of 31

2.1 JView 2004 Application Overview

Figure 1: JView 2004 Architecture Diagram

Copyright 2004 - DevStream Corporation Page 10 of 31

2.1.1 JView 2004 Agent

2.1.2 JView 2004 Nucleus Server (NS)

2.1.3 JView 2004 Performance Console

Copyright 2004 - DevStream Corporation Page 11 of 31

2.2 JView Terms and Definitions

Table 1: GLOSSARY OF COMMON TERMS

Performance Point - Performance Point allows for the on-demand collection of

Dev Mode - During development testing, PerfPoint DevMode allows

Prod Mode - In Production Mode, your J2EE components, or End-To-End user

PerfPoint - In Production Mode, PerfPoint DevMode allows on-demand detail

JavaScape View - The JavaScape view uses JavaScape - a patent-pending

Copyright 2004 - DevStream Corporation Page 12 of 31

JavaScape by Thread View - The JavaScape by Thread view enables you to

Transaction Explorer View - The Transaction Explorer view displays

SLA Monitoring View - The SLA Monitoring view displays currently

MReports Database - The MReports database is populated by the Nucleus Server,

Copyright 2004 - DevStream Corporation Page 13 of 31

2.3 System Requirements

2.4 Supported Platforms, Application

Table 2: SUPPORTED ENVIRONMENTS

Operating Windows NT 4.0, Windows 2000 Professional, Windows 2000 Server,

Application BEA Weblogic 8.x, 7.x, 6.x,

JDK 1.2 Sun 1.2.2_17/_017, Sun 1.2.2_16/_016, Sun 1.2.2_15/_015,

Copyright 2004 - DevStream Corporation Page 14 of 31

JDK 1.4 Sun/HP/IBM 1.4.2_01, Sun/HP/IBM 1.4.2, Sun/HP/IBM 1.4.1_05,

MReports Oracle 9.x, 8.x

2.5 Order of Installation

Copyright 2004 - DevStream Corporation Page 15 of 31

3 Preparing for Installation