<<

. 19
( 87 .)



>>

directory and click OK.
13. As seen in Figure 5-4, a Con¬guration Changes dialog should
appear. Expand the detected changes and verify whether the Server
P1: GIG
WY009-05 WY009-BenNatan-v1.cls May 11, 2004 18:52




Installing WebSphere Portal Tools and Problem Analysis 91




Figure 5-3 WebSphere Portal V5.0 location.




Figure 5-4 WebSphere Studio Con¬guration Changes dialog.
P1: GIG
WY009-05 WY009-BenNatan-v1.cls May 11, 2004 18:52




92 Chapter 5


Tools for WebSphere Portal version 5.0 Test Environment 5.1.0 and
WebSphere Portal Toolkit have been detected. Click Finish.
14. An Install/Update dialog appears and asks you to restart WSAD to
incorporate the changes, click Yes.
15. After the restart, WSAD should display the basic development
environment again.


Updating to WebSphere Portal Test Environment V5.0.2
Next you have to update the WebSphere Portal V5.0 Test Environment to
V5.0.2. Do this by performing the following steps:
1. Extract WebSphere Portal Fix Pack 2 to c:\fixpack2. The location
should be at the root path and have no blanks or special characters.
The batch ¬le will not work with a complex path. So make your life
easier and use c:\fixpack2.
2. Open a command prompt and change directory to <WSAD>\Portal
Toolkit.
3. Run updatePortalTestEnv502 C:\fixpack2. It should take
approximately 20 minutes for the update to complete.
4. Check results in the command prompt (as seen in Figure 5-5) for
updatePortalTestEnv502.bat to make sure it ended
successfully.
5. Verify the WebSphere Portal V5.0.2 Test Environment upgrade by
doing the following.




Figure 5-5 A successful update of the Portal Test Environment.
P1: GIG
WY009-05 WY009-BenNatan-v1.cls May 11, 2004 18:52




Installing WebSphere Portal Tools and Problem Analysis 93


a. Double-click the WebSphere Studio shortcut on the desktop.
b. In the WebSphere Studio dialog box, verify your workspace and
then click OK.
c. Click File ➪ New ➪ Project ➪ Portlet Development Portlet
Application Project.
d. To de¬ne the Portlet Project, enter Portlet1 for the Project Name
and click Finish.
e. After the wizard ¬nishes creating the project, right-click on
Portlet1 in the Project Navigator and select Debug on Server.
f. In the Server Selection dialog, select WebSphere Portal V5.0 Test
Environment under the Create a New Server Area. Check the Set
Server as Project Default (do not prompt) and click Finish.
g. The project will be published to the WebSphere Portal V5.0 Test
Environment server and the server will be started. Server startup
information will be displayed in the Console view in the bottom
center area.
h. After sometime, a browser should display a Debug page with
Portlet1 portlet on it (as seen in Figure 5-6). This veri¬es that the
Test Environment is running properly.




Figure 5-6 WebSphere Studio running Server in Debug mode.
P1: GIG
WY009-05 WY009-BenNatan-v1.cls May 11, 2004 18:52




94 Chapter 5


IBM Lotus Workplace Web Content Management
Version 1.1
Included with WebSphere Portal V5.0.2 is IBM Lotus Workplace Web Con-
tent Management (ILWWCM) version 1.1, which eventually replaces WPCP.
However, this component must be installed after you have installed Web-
Sphere Portal.
On a separate CD you will ¬nd a ¬le called C53YLML.exe. You will
also need to download JRE 1.3.1_09 and install it. To install ILWWCM,
perform the following steps.

Updating the Initialization Parameters
1. Log in to Windows as an Administrative user.
2. Double-click C53YLML.exe and unzip the ¬les to c:\wcm.
3. Open the WebSphere Application Assembly Tool by clicking Start ➪
Programs ➪ IBM WebSphere ➪ Application Server V5.0 ➪
Application Assembly Tool.
4. In Welcome to the Application Assembly Tool, select the Existing tab.
5. Browse to C:\wcm\app\config\websphere\ilwwcm.war. Click
Select and then click OK.
6. Navigate to and select Initialization Parameters by clicking
ILWWCM ➪ Web Components ➪ ILWWCM Framework ➪
Initialization Parameters.
7. As seen in Figure 5-7, replace parameter [ILWWCM_HOME] with
C:/wcm/app and click Apply. Click Save and exit the Application
Assembly Tool.

Installing the ILWWCM Web Application
1. Start WebSphere Application Server.
2. Open the WebSphere Administration Console.
3. Select Applications ➪ Install New Applications.
4. Select Local Path, browse to C:\wcm\app\config\websphere\
ilwwcm.war, and click Open.
5. As seen in Figure 5-8, enter wcm in the Context Root ¬eld and then
click Next.
6. On all the next four screens, accept the defaults and click Next until
you see the last screen. Then hit Finish.
P1: GIG
WY009-05 WY009-BenNatan-v1.cls May 11, 2004 18:52




Figure 5-7 Con¬guring ILWWCM in WebSphere Application Assembly Tool.




Figure 5-8 Installing ILWWCM.




95
P1: GIG
WY009-05 WY009-BenNatan-v1.cls May 11, 2004 18:52




96 Chapter 5


7. If the installation is successful, click Save to Master Con¬guration
and then in the Save to Master Con¬guration window click Save.
8. Copy the contents of C:\wcm\web-app, which consists of three
directories (ac_admin, WEB-INF, and webinterface) to paste the
directories into the <WAS>\installedApps\<short_server_
name>\ilwwcm_war.ear\ilwwcm.war directory.



Updating the ILWWCM Con¬guration Files
1. Copy the con¬guration ¬les aptrixjpe.properties,
aptrixsearch.properties, and connect.cfg from
C:\wcm\app\config\samples to C:\wcm\app\config.
2. Now this process is tedious. Replace the following variables with the
given values in all the con¬guration ¬les.
[HOST] = Your host name.
[PORT] = 9080
[CONTEXT_ROOT] = wcm
[ILWWCM_HOME] = C:/wcm/app
[WEB_APP_HOME]= <WAS>/installedApps/<short_server_name>/
ilwwcm_war.ear/ilwwcm.war

Note that since these ¬les are Java property ¬les, the backward slash
used for Windows directory is represented as a forward slash. This is
not a typo in the book.
3. Save each ¬le.


Starting the ILWWCM Web Application
In the WebSphere Administration Console, ¬nd and select the ilwwcm_war
Enterprise Application and click Start. Verify ilwwcm_war has started by
checking for the green arrow in Enterprise Applications. You can also just
restart the WebSphere Application Server.


ILWWCM Administrative Client Setup
1. Make sure that JRE 1.3.1_09 is installed.
2. Initialize the ILWWCM Web application by entering
http://localhost:9080/ilwwcm/connect/?MOD=AJPEGUI in an
Internet Explorer browser. Figure 5-9 indicates a successful
initialization.
P1: GIG
WY009-05 WY009-BenNatan-v1.cls May 11, 2004 18:52




Installing WebSphere Portal Tools and Problem Analysis 97




Figure 5-9 A successful initialization of the ILWWCM Administrative Client.



3. In Enter Network Password, enter Administrator for the User Name
and password for Password. Verify that the Utility to update the User
Interface Manager is completed without errors.
4. Enter http://localhost:9080/ilwwcm/connect/aptrix in a browser. In
˜Java Plug-in Security Warning™ click Grant Always to allow the
Verisign authenticated ILWWCM applet to install and run. Expand
the components of the Home area and verify that Aptrix exists as a
Site Framework. If you see Figure 5-10, your ILWWCM administrator
client is now running.


Installing the WebSphere Portal Content
Management Portlet
To install the portlet, which will enable you to view your content managed
by ILWWCM, log on WP as an administrator:

1. Go to the Portal Administration screen.
2. Go to the Install Portlets view and Click Browse.
P1: GIG
WY009-05 WY009-BenNatan-v1.cls May 11, 2004 18:52




98 Chapter 5




Figure 5-10 The ILWWCM Administrator Client.

3. Select the wpsV5-j-ilwwcm-cportlet.war ¬le to install and click
Next. It is located at c:\wcm\contentportlet\wpsV5.
4. The Web Content Management Portlet is displayed (as seen in
Figure 5-11). Click Install to install. The portlet will be labeled as
Content Viewer, Java Edition when you look for it under Manage
Portlets.


Problem Analysis
The one law that most professionals in the computer ¬eld believe in reli-
giously is Murphy™s law: whatever can go wrong will go wrong. This is why
problem analysis is so important. You know something will go wrong. The
question is how fast you can diagnose it, correct the situation, and prevent
it from recurring.
WebSphere Portal is not a simple product. It is a framework that interacts
with numerous other disparate products. Many problems occur with these
interactions.
The ¬rst step to determine a problem is to isolate and simplify the en-
vironment. Try to duplicate problems in self-contained networks free of
P1: GIG
WY009-05 WY009-BenNatan-v1.cls May 11, 2004 18:52

<<

. 19
( 87 .)



>>