208 IBM Enterprise Workload Manager
Diagnosis
Possible causes of this problem are the following:
? EWLM Control Center is supported on IE V6 SP1. If you are on a previous version, it may
work, but you may have intermittent problems.
? You need to enable cookies.
? You need to enable Javascript.
? Do not set security to the maximum on IE because this renders your login unsuccessful.
? You need a JVM plug-in to display graphs.
? The EWLM Control Center uses SSL/TLS for communications.
Solution
? We recommend you scan your computer and install all critical Internet Explorer updates.
For example, from Internet Explorer, choose Tools
→ Windows Update. This will take
you to the Microsoft Window Update internet site. Click Scan for updates. Apply the
latest critical updates, including KB831167, which is needed to allow a valid userid to log
in without first waiting one full minute after presentation of the login page.
? You need to set the security in your browser to use TLS. To do this follow these steps:
a. In IE, click Tools
→ Internet Options → Advanced.
b. Scroll down to Security and select Use TLS 1.0.
c. Click OK.
8.6.2 Manage options
Problem
Communication error
Error received
See “Problems with the managed servers” on page 205.
8.6.3 Monitor options
Problem
Application topology window does not show expected results.
Error received
The Application topology for our transaction class did not show our entire topology. The
Application Topology window should have looked similar to Figure 8-2 since we had an HTTP
Server as hop 0, two WebSphere Application Servers as hop 1, and the DB2 Universal
Database as hop 2 in our configuration. However, when we selected Application Topology
from the pull-down list from the Monitor
→ Transaction Class selection, we got a view that
looked either like Figure 8-3 (missing the DB2 hop) or Figure 8-4 (missing the HTTP hop).
Figure 8-2 Correct Application Topology view
Chapter 8. Troubleshooting and diagnostics 209
Figure 8-3 Broken Application Topology view 1
Figure 8-4 Broken Application Topology view 2
Expanded description
In our configuration, we have an HTTP Server (hop 0), two WebSphere Application Servers
(hop 1), and a DB2 database (hop 2). In the Enterprise Workload Manager Control Center,
under the Monitor option, we clicked Transaction classes, selected our transaction class,
clicked the pull-down, and chose Application Topology. We expected to see a chart in the
Application Topology view that looked like Figure 8-2, but one of the WebSphere Application
Servers and the DB2 were not there.
Since neither the WebSphere Application Server nor the DB2 were set up in a special
transaction class, they showed up as hop 0s in the EWLM Default Application Transaction
Class, as shown in Figure 8-4.
Diagnosis and solution
There are a number of reasons that this scenario may occur:
1. Managed server-related
The managed server was not started on the machine where the application was running.
2. DB2-related
The DB2 Universal JDBC driver supports JDBC type 2 and type 4. Since we were testing
the trade3 installation script, it was using the legacy DB2 JDBC driver in type 2 mode by
default (db2java.zip). The legacy driver does not propagate the ARM correlator to the next
hop, so we installed the new JCC driver in type 4 mode.
To verify that instrumentation has been set up correctly on AIX, issue the lsarm -a
command. You should see:
APPL: IBM DB2 Universal Database
210 IBM Enterprise Workload Manager
If ARM is not set up correctly for DB2, see “Enabling DB2 Universal Database for ARM” on
page 60.
3. HTTP-related
Verify that the HTTP is instrumented correctly. Turn tracing on for the HTTP Server so that
you can verify that the HTTP server has ARM enabled.
a. Edit the plug-in:
C:Program FilesWebSphereAppServerconfigurationcellsplugin-cfg.xml
b. Change the log level from whatever it is to Trace <Log Loglevel="Trace" Name=
"C:Program FilesWebSphereDeployment Managerlogshttp_plugin.log"/>
c. Restart the HTTP Server.
In the HTTP log (specified by the Name= variable in step b) there should be new entries
stating that the ARM library was successfully initialized.
If you see the ARM entries, the HTTP Server has been configured correctly and you
should turn TRACE off again since it will produce enormous amounts of data. If you do not
see the ARM messages in the log, review the steps in “Enabling IBM HTTP Server for
ARM” on page 65.
4. WebSphere Application Server-related
The WebSphere Application Server may not be instrumented correctly as described in
“Enabling WebSphere Application Server for ARM” on page 63.
To verify that instrumentation has been set up correctly on AIX, issue the lsarm -a
command. You should see:
APPL: WebSphere
5. Policy-related
Check your service class, transaction class, and policy definitions, as described in 5.5.2,
“Creating the domain policy at the EWLM Control Center” on page 144. It is possible that
there is a typo or an error in defining the transaction class to the correct service class.
6. Workload-related
Verify that the workload is currently running. If there is no workload or it is at the beginning
or end of the workload, EWLM might still be in the process of building the topology and is
not capable of displaying the full picture yet. If this is the case, verify that the workload is
running and wait at least the transaction average response time plus 10 seconds to let
EWLM build the application topology graphic and check the preference setup.
Related information is in 1.3, “EWLM supported platforms and applications” on page 16.
Problem
You cannot see the graphical displays in the EWLM Control Center.
Error received
The error received is shown in Figure 8-5.
Chapter 8. Troubleshooting and diagnostics 211
Figure 8-5 Application Topology: Lack of Java graphical data
Expanded description
When trying to look at the Application topology of a transaction class, the view that was
presented did not show the Java logo, then present the graphical display. Instead, the only
view that was received is shown in Figure 8-5.
Diagnosis and solution
JVM 1.4.1 needs to be installed on the system where the browser is running that is trying to
display the topology graph from the EWLM Control Center.
Problem
The domain manager did not provide topology data.
Expanded description
After selecting Monitor → Transaction class, and selecting Application topology from the
pull-down list, an error message pops up stating there is a communication problem with the
domain manager.
Figure 8-6 Communication problem with the domain manager
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.