. 20
( 87 .)


Installing WebSphere Portal Tools and Problem Analysis 99

Figure 5-11 The ILWWCM Content Viewer Portlet.

¬rewalls and external HTTP servers. In other words, try to duplicate the
error using WAS internal HTTP server on a single machine. When trying to
isolate a problem, change only one parameter at a time. Check the infocen-
ter and the WebSphere Portal developer Community Zone. The probability
is that you are not the ¬rst to encounter the problem.
Try to ¬nd the errors before production by doing extensive load and stress
testing. The time you spend on load testing will be one-¬fth the time you
will spend if you ¬nd the error during production (and a lot less stressful
on yourself).
Remember, there is nothing magical about WebSphere Portal. It is a col-
lection of applications that run under WebSphere Application Server and
as such suffer the same problems as many other WebSphere Applications
such as miscon¬gured HTTP plug-ins, memory, native, and application
heap leaks. You can also suffer because of problems from miscon¬gured
secured, classloaders, JVMs, and Session Managers. Problems can also be
caused (most probably) by poorly written portlets.
WebSphere Portal helps you ¬nd your problems by logging everything.
During the installation, log ¬les are created in <wp-root>\log. How-
ever, before the Portal Server directory is created, the install logs are in the
WY009-05 WY009-BenNatan-v1.cls May 11, 2004 18:52

100 Chapter 5

Table 5-1 WebSphere Portal Installation Logs
Installation trace information

Installation messages that are generated during

Trace information generated by WPCP

Trace information generated by WP

Portlet installation messages

WebSphere Application Server Fix Pack 1 trace

WebSphere Application Server Enterprise Edition Fix
Pack 1 trace information

WebSphere Application Server trace information.
Located in <was_root>/logs directory

WebSphere Application Server Enterprise Edition trace
information. Located in <was_root>/logs directory

system temporary directory. The logs created during installation are shown
in Table 5-1.
Finding problems during WebSphere Portal provides extensive trace ca-
pability (see Chapter 10 for grammar and trace string con¬guration). Trace
logging is set by enabling properties in the <wp_root>/shared/app/
config/log.properties ¬le. When the trace is set, it creates a ¬le <wp-
root>/log/wps_<date_time>.log. In the WebSphere Portal Adminis-
tration guide under Using Logs, IBM lists in detail the trace settings needed
to analyze if a component is having a problem.

Tivoli Web Site Analyzer
A useful tool to help you understand your WebSphere Portal site character-
istics is Tivoli Web Site Analyzer. This tool comes with WebSphere Portal
Enables and also comes with features precon¬gured to help analyze Web-
Sphere Portal.
Tivoli Web Site Analyzer analyses WebSphere Portal data that is stored
in site analysis logs. You have to enable these logs by doing the following:

1. Open <wp-root>/shared/app/config/services/
SiteAnalyzerLogService.properties with a text editor.
WY009-05 WY009-BenNatan-v1.cls May 11, 2004 18:52

Installing WebSphere Portal Tools and Problem Analysis 101

2. Accept the default values. Data will be stored in log/sa.log and
the backup log will be log/sa_$CREATE_TIME.log where
$CREATE TIME is the time and date when the ¬le was created.
3. Accept the default date and time format used as part of the log ¬le
name. The default value is yyyy.MM.dd-HH-mm.ss
4. Uncomment one of the following parameters to control the interval
at which the log ¬le is being backed up.
SiteAnalyzerFileHandler.minutesPerLogFile if you
want to log in intervals of minutes, and set the value to an integer
in the range 1“60.
SiteAnalyzerFileHandler.hoursPerLogFile if you want
to log in intervals of hours, and set the value to an integer in the
range 1“24.
SiteAnalyzerFileHandler.daysPerLogFile If you want to
log in intervals of days, and set the value to an integer that
indicates the number of days.
5. Enable the logger you want activated by removing the comment
indicator (#). If you disable the logger, you re-add the comment
indicator in front of it. Table 5-2 shows which WebSphere Portal
URLs the loggers track.
6. Restart WebSphere Portal.
For purpose of demonstration, we enabled all the loggers, logged in as
wpsadmin, and clicked on various pages and portlets. Remember, this is
for demonstration. Normally you would not enable all the loggers (unless
you are doing a major stress test on the box) and you would monitor more
than one user.
Once enabled, WebSphere Portal started tracking the URL usuage as
sa.txt. If you look in sa.txt, you would see entries like the following:
rsgornit.us.ibm.com - wpsadmin [10/Feb/2004:17:34:32 +0000] "GET
ortletMode=View&PortletState=Normal HTTP/1.1" 200 -1
"http://rsgornit.us.ibm.com/Page/6_0_6A/Home" "Mozilla/4.0 (compatible;
MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)" "JSES-SIONID=QUXWVc

These entries show the following:
The IP address or the domain name: rsgornit rsgornit.us.ibm
The identi¬er used to identify the client. If it is not known then a
dash (-) is used.
WY009-05 WY009-BenNatan-v1.cls May 11, 2004 18:52

102 Chapter 5

Table 5-2 Tivoli Web Site Analysis WebSphere Portal Loggers







The WebSphere Portal user ID: wpsadmin.
The date and time of the HTTP request: [10/Feb/2004:17:34:32
The HTTP request:
B&PortletMode=View&PortletState=Normal HTTP/1.1"

The HTTP status code: 200.
The number of bytes transferred from the client due to the request. -1
means unknown: -1.
The URL that linked the client to the Web site:

The type of Web browser:
"Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR

The name and value of the cookie sent:
WY009-05 WY009-BenNatan-v1.cls May 11, 2004 18:52

Installing WebSphere Portal Tools and Problem Analysis 103

Figure 5-12 Tivoli Web Site analysis of the log.

You can then import your logs into Tivoli Web Site Analyzer or have
it sample the logs automatically at scheduled intervals. Tivoli Web Site
has special report elements de¬ned for portal server. You can view pages,
portlets, and logins rank by visitors. You can summarize statistics by com-
mands or view hoe many times a page has been edited. Figure 5-12 shows
how many times each page has been hit based on the logs generated.

In this chapter we reviewed how to install two very important tools: Por-
tal Toolkit and ILWWCM. We also discussed problem analyses and using
Tivoli Web Site Analyzer helped you understand the performance and user
characteristics of your Web site. We slightly touched on the Tivoli Web Site
Analyzer with the objective that you just understand the power and wealth
of information that it can provide.
Now that we have dealt with installation issues in detail, the next logical
step is to discuss migration, which is the topic of Chapter 6.
WY009-05 WY009-BenNatan-v1.cls May 11, 2004 18:52

WY009-06 WY009-BenNatan-v1.cls May 9, 2004 9:35


Migrating to WebSphere
Portal Version 5.0

It would be great if you didn™t have to worry about migration. How-
ever, you have dealt with a previous version so you have to deal with
it even though it can be a tedious and dif¬cult process. In this chapter,
we will discuss the supported migration paths for WebSphere Version 5.0
and show you how to migrate the security attributes, portlets, skins, and
themes. Due to the nature of this topic, this coverage is straightforward. For
the purpose of being succinct, we will mention our examples using Win-
dows format; however, you can easily determine the Unix/Linux format for


. 20
( 87 .)