WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.

5 SP3 10/26/2004

WebSphere Network Deployment Configuration Guide

for WDK Apps 5.2.5 SP3

October 26, 2004

Page 1 of 16
WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.5 SP3 10/26/2004

WebSphere Network Deployment Configuration

Steps
This document contains:
• What's New in the SP3 Installer
• Limitations
• Steps to set up a WebSphere Network Deployment configuration supported by the
WDK App Installers.
• Steps to perform WDK App (Webtop) installation to this environment.
• Troubleshooting

Webtop is the application that is referenced throughout this document, but the instructions are
applicable to all 5.2.5 SP2 WDK applications.

What's New in the 5.2.5 SP3 Installer

• WDK Apps can be installed to servers that are part of a WebSphere Cluster.
• When the application war file is installed using Deployment Manager Admin Console,
the Application Name can be set to any value. Additionally, any value can be set for the
Context Root and it does not have to match the Application Name.
• Multiple renamed installations of a WDK App (e.g. webtop1, webtop2) can be installed
within a Network Deployment cell.
• WDK Apps do NOT have to be installed to the default location in WebSphere Admin
Console.
• There is a large help file available from the Help button in the 'Network Deployment
Installation Step' panel.

Limitations
• The DefaultApplication that ships with WebSphere does not work in Clusters because it
includes an EJB. Since Virtual Link support requires installation of DefaultApplication,
we provide a version of DefaultApplication with the EJB removed. More info on this
found in WebSphere Network Deployment Installation - Section F.

Page 2 of 16
WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.5 SP3 10/26/2004

Supported WebSphere Network Deployment

Configuration
WDK applications can be installed to the following WebSphere Network Deployment
configuration:

Deployment Manager Cell

DeploymentManager AppServer Installation Instance

Node 1
server Node x
dmgr

AppServer Installation Instance AppServer Installation Instance

Node x
server server2 Node 2 server server 2

server Node x Cluster x

AppServer Installation Instance

Machine 1 Machine y

• Deployment Manager can be on its own machine or on the same machine as one or
more Application Server installation instances (IBM recommends Deployment Manager
is on its own machine for production)
• A federation of multiple Application Server 'installation' instances managed by a
Deployment Manager installation can be installed to the same machine or across
multiple machines.
• Application Server 'Installation' instances are supported; 'Configuration' instances are NOT:
Deployment Manager only supports federation of 'installation' instances of Application Server
into a Deployment Manager cell. An 'installation' instance is an actual installation of the
Application Server (i.e. you create an 'installation' instance by actually running the WebSphere
installer to install the Application Server product in coexistence mode).
A 'configuration' instance is an additional instance created within the same Application Server
installation using [Link]/sh. You CANNOT federate a 'configuration' instance to a
Deployment Manager cell, so we do not support this configuration. NOTE: If you have created
an additional server within an Application Server installation using [Link]/sh, you have
created a 'configuration' instance, so it is not supported.
• Cluster configurations are supported.

Page 3 of 16
WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.5 SP3 10/26/2004

WebSphere Network Deployment Installation

The steps for installing a supported network deployment configuration are listed below. The top
level steps are:
A. Install Deployment Manager on Machine 1
B. Install Application Server on Machine 1
C. Install Application Server on Machine 2
D. Create a Network Deployment federation of the Deployment Manager and both App
Server installations
E. Set up Virtual Host for Application Server install on Machine 1
F. Map the DefaultApplication to both of the App Server installations
G. Verify that wsadmin launches properly from each 'installation' instance

A. Install Deployment Manager on Machine 1

Panel Action
1. Launch the WebSphere Deployment Manager Installer
2. Welcome Click Next
3. License Accept and then click Next
4. Features Select desired and then click Next (Deployment Manager is the only required
selection for Documentum apps)
5. Install Specify desired install locations and then click Next
Locations
6. Naming Verify the HostName and specify the desired names for Node / Cell and then
click Next
7. Service Select to run Deployment Manager as a service and then click Next (this option
is up to your personal preference)
8. Summary Click Next
9. Installation Wait until installation is completed
10. Registration Select to register is desired, then click Next
11. Completion Click Finish
12. Install required Fix Packs and Hot Fixes for this Deployment Manager
installation

B. Install Application Server on Machine 1

Panel Action
13. Launch the WebSphere Application Server Installer
14. Welcome Click Next
15. License Accept and then click Next
16. Coexistence If you already have a WebSphere installation of the machine (Deployment
Manager or Application Server), select to coexist with other versions and then
click Next (if it is the first product installed, you do not need to select this option)
17. Setup Type Choose Full or Custom and then click Next

Page 4 of 16
WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.5 SP3 10/26/2004

18. Features Select desired and then click Next. The following are required for Documentum
(if custom) apps:
• Application Server and Sample Apps
• Administration
19. Install Specify desired install locations and then click Next
Locations
20. Naming Verify the HostName and specify the desired name for the Node and then click
Next
21. Service Select to run HTTP Server as service if desired and do NOT select to run the
Application Server as a service and then click Next. Note: App Server starting
and stopping will be controlled by Deployment Manager.
22. Summary Click Next
23. Installation Wait until installation is completed
24. Registration Select to register is desired, then click Next
25. Install required Fix Packs and Hot Fixes for Application Server installation

C. Install Application Server on Machine 2

Panel Action
26. Launch the WebSphere Application Server Installer
27. Welcome Click Next
28. License Accept and then click Next
29. Coexistence Select to coexist with other versions, note the port versions and then click Next.
It's not a bad idea to record all of the port values for future reference. At
minimum, you need to know the HTTP Transport Port for accessing the
applications, Admin Console Port and the SOAP Connector Port (SOAP
Connector Port used to identify the server when adding it to the Network
Deployment federation). The others are good to have to have if you ever run into
any port conflict problems or want to put more than two installations on a
machine.
30. Setup Type Choose Full or Custom and then click Next
31. Features Select desired and then click Next. The following are required for Documentum
(if custom) apps:
• Application Server and Sample Apps
• Administration
32. Install Specify desired install locations and then click Next
Locations
33. Naming Verify the HostName and specify the desired name for the Node and then click
Next
34. Service Do NOT select to run the Application Server as a service (unselect) and then
click Next. Note: App Server starting and stopping will be controlled by
Deployment Manager.
35. Summary Click Next

Page 5 of 16
WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.5 SP3 10/26/2004

36. Installation Wait until installation is completed

37. Registration Select to register is desired, then click Next
38. Install required Fix Packs and Hot Fixes for Application Server installation

NOTE: If you need to add additional Application Server installations, for

installation on its own machine, follow Step C, for installation on a machine with
other installations, follow Step B. If installing more than one Application Server
to the same machine, you will need to eliminate port duplications in the
[Link] and [Link] files after adding the installations to the
Network Deployment. Instead of adding another App Server installation to a
machine, it's a lot easier to just create additional servers within the App Server
installation (using Admin Console).

D. Create Network Deployment Federation

Panel Action
39. Start the Application Server and Deployment Manager on Machine 1
• <AppServerInstallRoot>\bin\startServer server1
• <DeploymentManagerInstallRoot>\bin\startManager
Start the Application Server on Machine 2
• <AppServerInstallRoot>\bin\startServer server1
40. Connect to Admin Console running on Deployment Manager on Machine 1
• [Link]
The port will depend on whether the installation was the first on the machine.
41. Home Add App Server Installed on Machine 1
Select System Administration – 'Nodes' link
42. Nodes Click on Add Node
43. Add Node Enter the Host for Machine 1 and select Include Applications, the click OK. Note:
If you get an error, this probably means you need a different value for JMX
Connector Port – try 8881, 8882 etc. (each Application Server installation on a
machine will have a different port number). Note: If you get a port conflict error
doing this and you are sure the App Server and Deployment Manager are
running (has been seen on UNIX), try adding using the addNode command
([Link] <host> <Deployment Manager port – usually 8879> -includeapps)
from the App Server bin directory.
44. Adding When addition completes, click on Logout from the WebSphere Administrative
Node Console
45. Home Add App Server Installed on Machine 2
Select System Administration – 'Nodes' link
46. Nodes Click on Add Node
47. Add Node Enter the Host for Machine 2 and select Include Applications, the click OK. Note:
If you get an error, this probably means you need a different value for JMX
Connector Port – try 8881, 8882 etc. (each Application Server installation on a
machine will have a different port number)

Page 6 of 16
WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.5 SP3 10/26/2004

48. Adding When addition completes, click on Logout from the WebSphere Administrative
Node Console
49. Home Select System Administration – 'Nodes' link
50. Nodes Verify that the nodes you added now show up along with the node for
Deployment Manager and that their status is synchronized. If they aren't
synchronized, select the App Server nodes and then click on Full Synchronize.
Note: If you have restarted any of the machines, you will need to execute the
'startNode' command in the bin directory of the App Servers ([Link] or
./[Link]) so Deployment Manager can access and synchronize them.
51. Home Start the Servers
Select Servers – 'Application Servers' link
52. Application Select the servers in the Network Deployment and then click on Start. Note:
Servers Avoid installing Application Server multiple times on the SAME MACHINE
whenever possible, because you have to manually change any duplicate
PORTS between these installations in the [Link] and [Link] files
(duplicates will always be created for at least the nodeagent ports). After making
the changes, copy the changed files into the config\.. directory locations for both
the App Server and Deployment Manager.
This is a very frustrating process, but you have to make sure there are NO
duplicates within or across the files. If you are able to start on of the servers on a
machine, but not the other, shut down the running port and try again with the
one that wouldn't start. If it starts you can be certain there is a port conflict. It's
possible to have port conflicts between Deployment Manager and an App Server
install on the same machine also, but not as likely. If you can only start one at a
time you have a port conflict. So whenever possible, just create additional
Servers using Admin Console within the App Server installation.

E. Set up Virtual Host for Application Server on Machine 1

Panel Action
53. The HTTP Transport ports for the Application Server install need to be added to
the default_host Virtual Host on Machine 1
Note: You only need to do this when multiple WebSphere installations are on the
same machine.
54. Home From Admin Console, select Environment – Virtual Host link
55. Virtual Host Select System Administration – 'Nodes' link
56. Nodes Click on 'default_host' link
57. default_host Click on 'Host Aliases' link
58. Host Click on New (you are going to add the HTTP Transport port numbers for the
Aliases Application Server installation you did on Machine 1 – the same machine
Deployment Manager is installed)
59. New Enter an asterisk (*) in the Host Name field and the non-secure port number
(e.g. 9085) in the Port field and then click OK Do the same with the secure port
number (e.g. 9444), click OK and then click on the 'Save' link
60. Save Click on the Save (be sure to have Synchronize changes with nodes selected)

Page 7 of 16
WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.5 SP3 10/26/2004

F. Map DefaultApplication to both Application Servers

Note: If you are utilizing Clusters, the standard DefaultApplication will not run
on servers in the Cluster because it contains an EJB. If you need Virtual Link
support, uninstall the existing DefaultApplication and install the
DefaultApplication available on the Documentum Download site (install
instructions included). This is exactly the same as the standard
DefaultApplication except the EJB components are removed (the only
functional difference is that the EJB related selections in the 'hitcount' sample
do not work).

Panel Action
61. Home Note: This step is only absolutely necessary for Web Publisher or if you want to
utilize Virtual Links. However, it's good to always do, since it will verify that your
Network Deployment is set up properly (it doesn't hurt anything and you can
unmap it later if you don't really need it)
From Admin Console, select Applications – Enterprise Applications link
62. Enterprise Click on 'DefaultApplication' link
Applications
63. Default Select the 'Map modules to application servers' link
Application
64. Selecting Select the 'Module' heading checkbox; highlight both servers in the upper field
Application and then click Apply. The servers and Clusters should now be listed in the
Servers server column next to the modules. Click on OK.
65. Default Select the Synchronize changes with nodes check box and click on the 'Save'
Application link
66. Save Click on the Save (be sure to have Synchronize changes with nodes selected)
67. Home Select System Administration – 'Nodes' link
68. Nodes Verify that all the nodes show as synchronized. Note: If you have at some point
restarted a server after added the App Server to the Network Deployment, you'll
need to start the node agent for that server with the startNode command in the
bin directory of that App Server installation.
69. Home Select Servers – 'Application Servers' link
70. Application Start the servers if they are not already running
Server
71. Home Select Applications – Enterprise Applications link
72. Enterprise Select DefaultApplication and then click on Start. Note: If the nodes are
Applications synchronized and the servers are running and DefaultApplication fails to start on
one of the servers, this means you do not have a supported Network
Deployment configuration set up. Either one or more of the servers is a
'configuration' instance or a server is in a Cluster and you have the standard
DefaultApplication installed (see the note at beginning of this section).
If you have problems getting DefaultApplication to run on multiple servers that
are not part of a Cluster, uninstall the standard DefaultApplication and install the

Page 8 of 16
WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.5 SP3 10/26/2004

Documentum version per the note at the beginning of this section.

G. Verify that wsadmin launches properly

Panel Action
73. The wsadmin utility needs to run properly from each installation instance in a
Network Deployment. Do NOT provide any parameters when you execute
wsadmin. When launched from the bin directory in an App Server installation
instance it actually runs as a Deployment Manager process.
NOTE: If you have Deployment Manager and App Server installations on the
same machine and you installed the App Server FIRST, there is a
WebSphere bug that you'll need to work around. Perform the following:
1. In Admin Console, go to System Administration - Deployment Manager -
End Points and get the value of the SOAP Connector Port.
2. Verify that this is the value that is set for the uncommented
[Link] entry in the [Link] file located in
the DeploymentManager\properties directory. Change the value to
match if it doesn't (for some reason this is improperly set when adding
an App Server to Deployment Manager when App Server is installed
first on the same machine).
74. Execute wsadmin in the bin directory of each app server installation. You should
see something similar to the following:

Connected to process "dmgr" on node abcManager using SOAP connector; The

type of process is: DeploymentManager
WASX7029I: For help, enter: "$Help help"
wsadmin>
If you get a message that shows wsadmin is running connected to the server
you launched it from, this installation is not part of a Network Deployment and
needs to be added.

If you get some other error and you have confirmed the node shows up as
synchronized and the servers show up as running, this means there is
something wrong with your configuration or you have modified the way that
wsadmin executes (e.g. requires one or more parameters - if you have done
this, this change must be removed while installing Webtop).

NOTE: You can set up servers that have been created as part of a Cluster in
the same way as the preceeding steps.

Webtop Installation
The steps for installing Webtop to a Network Deployment configuration are listed below. The
top level steps are:
A. Download the [Link] on Deployment Manager Machine
B. Install the [Link] file to the desired nodes/servers in the federation
C. Configure the nodes/servers where webtop has been installed
D. Run Webtop

Page 9 of 16
WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.5 SP3 10/26/2004

REMINDER: Only one installation of Webtop can be done within a

Network Deployment. You cannot rename the war or give the application
any name other than webtop.

A. Download Webtop War on Deployment Manager Machine

Panel Action
1. Verify that the Deployment Manager and App Servers are running and
synchronized. Launch the webtop installer exe or bin on the machine with
Deployment Manager.
2. Welcome Click Next
3. License Read, select Accept and then click Next
4. Runtime Select desired features and then click Next
Features
5. Destination* Specify desired location and then click Next
*if DFC not already installed
6. User Specify desired location and then click Next
Directory* *if DFC not already installed
7. App Server Select WebSphere and then click Next
Selection
8. Config Type Select Network Deployment Configuration and then click Next
9. Installation Select Download application war file and then click Next
Step
10. Server Specify the Deployment Manager home directory (e.g.
Home \WebSphere\DeploymentManager) and then click Next
11. Get Security Enter Admin User ID & Password and click Next
Information* * if Global Security On
12. War Specify the directory where you want the war file downloaded (this is the
Download directory you will select when you install the war file using WebSphere Admin
Directory Console.
13. Virtual Link Select if desired and then click Next
Support
14. Install Click Next
Preview
15. install Wait until the installation has completed
16. Install Click Finish
Summary

B. Install Webtop War using Admin Console

Panel Action
17. Connect to Admin Console
18. Home Select Applications – 'Install New Application' link

Page 10 of 16
WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.5 SP3 10/26/2004

19. Prep for - Enter or browse to the location of the webtop war file you just downloaded
App Install - - Enter 'webtop' in the Context Root field and then click Next
1
20. Prep for Click Next
App Install -
2
21. Install App - You can specify a location in 'Directory to Install Application' (must be absolute
Step 1 – path – do not use environment variables). If you leave the field blank, the
Provide binaries will be installed to the default location, which is under the installedApps
Options directory.
- Specify the desired app name in the 'Application Name' field (if you don't
remove the '_war', it will be part of the app name) and then click Next
22. Install App Click Next
Step 2 –
Map Virtual
Hosts
23. Install App - Select the 'Module' heading checkbox
Step 3 – - Highlight the servers you want webtop to run on in the 'Clusters and Servers'
Map field and then click Apply. Clusters or servers can be selected.
Modules to
Servers

- Verify that the Clusters and servers are now listed in the Server column and
then click Next
Note: if you add a server to the Network Deployment at a later date and want
Webtop to run on it, you will need to map Webtop to that new server. To do this,
select the Webtop app in Admin Console, select the 'Map modules to application
servers' link and update the list of servers (same way you did in this step)
24. Install App Click Finish
Step 4 –
Summary
25. Installing… After installation is completed, click on the 'Save to Master Configuration' link
26. Save Click on Save

C. Configure All App Server Installation Instances where Webtop is

Installed*
Panel Action

Page 11 of 16
WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.5 SP3 10/26/2004

Every App Server installation instance needs to be configured to run Webtop.

Configuring installs DFC, creates a WebSphere Shared Library of the classpaths
to the DFC jars / config directory for the node and configures the jvm of the
server.
Launch the Webtop installer and perform the sequence of steps below to each
App Server installation instance where Webtop is installed
27. Welcome Click Next
28. License Read, select Accept and then click Next
29. Runtime Select desired features and then click Next
Features
30. Destination* Specify desired location and then click Next
*if DFC not already installed
31. User Specify desired location and then click Next
Directory* *if DFC not already installed
32. App Server Select WebSphere and then click Next
Selection
33. Config Type Select Network Deployment Configuration and then click Next
34. Installation Select Configure server instances and then click Next
Step Note: Please read the extensive Help available on this panel.
Selection
35. Server Specify the home directory of the App Server installation instance and specify
Home the name of the application that needs to be configured and then click Next
36. Installation Select configure server instances on this server and then click Next
Step If you have installed to a Cluster, servers that are members of the Cluster and
are on the current App Server node will be listed. Their Cluster membership will
be identified in parentheses. Each server Cluster member must be configured.
37. Get Security Enter Admin User ID & Password and click Next
Information* * if Global Security On
38. Select Select the server to configure (in reality there won't be more than one) and then
Servers to click Next.
Configure Note: If none are found, verify that the servers are all running and that Webtop is
mapped to the server in the installation instance.
39. Virtual Link Select if desired and then click Next
Support Note: If you select Virtual Link support, it is probably worth taking a look at
Troubleshooting Section B to see if the situation it covers is going to be
applicable to you. If it is you can perform the troubleshooting steps and then
continue from here.
40. Content Specify the desired Content Transfer location and then click Next
Transfer
Location
41. Install Click Next
Preview
42. install Wait until the installation has completed

Page 12 of 16
WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.5 SP3 10/26/2004

43. Install Click Finish

Summary

* If Deployment Manger is NOT in the same parent directory as an App

Server where you have installed Webtop AND you want Global Security
ON, you will need to download the [Link] to the Deployment
Manager again. Doing this performs a configuration step to Deployment
Manager that can't be done until after [Link] has been installed
using Admin Console. Perform Webtop Install Step A above again and
then jump to Step D below. (This configuring is usually done during app
server installation instance configuring, but cannot be done when there
is no app server installation instance under the same directory as
Deployment Manager.)

D. Run Webtop
Panel Action
Be sure to configure each App Server installation instance and then connect to
Admin Console.
44. Welcome Select Servers – 'Application Servers' link
45. Application Select all of the servers and Stop then Start them
Servers
46. Welcome Select System Administration – Nodes link
47. Nodes Verify that all nodes are synchronized
48. Welcome Select Applications – Enterprise Applications link
49. Enterprise Select 'webtop' application and then click Start (if not already running)
Applications Note: If does not eventually show up as solid green start arrow, this means one
of the servers it is mapped to is not really running or the server is not a valid
member of the Network Deployment
50. Webtop should now run properly (you'll need to pass the appropriate port
number for each App Server installation instance in the url)

Page 13 of 16
WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.5 SP3 10/26/2004

Troubleshooting
If you are having problems installing Webtop to a Network Deployment that has not been set up
following the instructions above, the setup has been done the same way as instructed. Then:

1. Walk through the steps of 'Create Network Deployment Federation' and 'Set up Virtual
Host' and make sure everything looks OK. If necessary remove the node and re-add it
properly.
2. Perform the steps in 'Map DefaultApplication to both App Servers' for each server
3. Perform the steps in 'Verify that wsadmin launches properly' for each server

Some additional troubleshooting scenarios follow:

A. Webtop is Installed on a Server and the Server is Running, but

you get a 404 Error in browser when trying to access Webtop from
the URL (you DO NOT get a Webtop login panel)
Panel Action
If you have done all the verification in the steps in this document, but still get
a 404 Error when you try to access Webtop with the correct port number, for
some reason the server probably has not been configured. Follow the steps
below in Admin Console to verify the server has been configured.
1. Welcome Verify WebSphere Shared Library created for the server
Select Environment – 'Shared Libraries' link
2. Shared Enter or browse to the node the server is in and click on Apply. After clicking
Libraries Apply, a <nodename>_webtop_SharedLibrary should be listed below.
If the shared library DOES NOT exist and you're sure you have entered the
correct node (be sure you have set the node for the app server you
configured), this means the server is not configured and the installer must
be run to configure this server.
If you have definitely run the installer to configure the server and no shared
library has been created, it is possible the configuration changes were not
successfully saved. So immediately after you after you have run the installer
to configure the server, select the Servers – Application Servers link in Admin
Console. If the following is display at the top of the panel, click on the 'Save
or discard' link

Then choose to synchronize and Save. Then click on Save to same conflict
items every time the selection is displayed below. It may be come up multiple
times. Always choose to Overwrite.

You can now exit this procedure, Stop / Start the server and login to Webtop.

Page 14 of 16
WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.5 SP3 10/26/2004

If the shared library DOES exist, click on that link.

3. <nodename> Verify that the entries in the Classpath field look correct (they are the DFC jar
_webtop files and config directory locations)
_SharedLibrary
4. Welcome Verify WebSphere Shared Library is assigned to Webtop
Select Enterprise Applications – 'webtop' link
5. webtop Select 'Libraries' link
6. Library Ref The <nodename>_webtop_SharedLibrary should be listed. If it isn't, run
configure again.
Note: There may be multiple entries of the library. This is OK, but you can
delete the duplicates if you want (a new entry is created each time configure
is run and there isn't a way for the installer to remove the duplicates with the
current version WebSphere).
7. Welcome Verify the JVM for the server has been configured
Select Servers – 'Application Servers' link
8. Application Select the desired server link
Servers
9. <selected Select the 'Process Definition' link
server>
10. Process Select the 'Java Virtual Machine' link
Definition
11. Java Virtual Select the 'Java Virtual Machine' link
Machine
12. Java Virtual Select the 'Custom Properties' link
Machine
13. Custom Verify that entries for [Link], documentum, [Link], [Link]
Properties and [Link] exist and the locations are correct. If they are not
there, you need to run configure (if wrong entries exist, delete them and run
configure)
Note: There may be duplicate entries (as with shared library, entry made
each time configure is run) This is not a problem unless the install location
changed for one of the installs – IF THE LOCATIONS ARE NOT THE SAME
FOR DUPLICATE ENTRIES, THE ENTRY WITH THE NON-CURRENT
LOCATION MUST BE DELETED. If the duplicates have the same location,
you can delete them if you want.

B. Webtop is Installed on a Server and the Server is Running, but

you get a 404 Error in browser when you try to login to Webtop
(you DO get a Webtop login panel)
This means you probably do not have all the required WebSphere Fix Pack and Hot Fixes
installed. Please verify you have all that are required in the Webtop Release Notes.
The following was inadvertently removed from our SP2 release notes and is applicable to
Webtop SP2:

Page 15 of 16
WebSphere Network Deployment Configuration Guide for WDK Apps 5.2.5 SP3 10/26/2004

*** You must apply IBM WebSphere Fix (APAR): PQ76313 to your WebSphere
installation prior to deploying (installing) any Documentum product on WebSphere.
If you do not install this IBM WebSphere fix, Documentum's signed jar files will
be corrupted. You can download the PQ76313 for WebSphere Application Server
5.0.x from [Link]
WebSphere 5.0.2 is not supported with browsers on Mac OS 9.2.2.

C. Webtop or DefaultApplication was uninstalled, then reinstalled

and it is does not run properly or the installer does not detect it.
WebSphere has a problem with uninstallation followed by reinstall of the same application. The
application will show up in Admin Console as installed, but the binaries are not actually
installed. The solution to this is to uninstall a second time and then reinstall again.

Please be sure to read the Help in the 'Network Deployment

Installation Step' panel for additional information.

Page 16 of 16