Tag Archives: IBM WebSphere

PeopleSoft HR 8.9 Installation Steps

Posted by on August 28, 2009 No comments

Hardware/Software Specifications

Server Hostname

Server Description IP Address
GLWEBAPP GL Web & App Server 10.x.x.x
GLDBASE GL Database Server 10.x.x.x

The machines that were used in the installation of the PeopleSoft test environments were Dell PowerEdge 2950.

The operating system for both servers was Microsoft Windows Server 2003 R2 Enterprise Edition Service Pack 2.

The GLDBASE machine shall house only the database server software (Microsoft SQL Server 2005).

The GLWEBAPP machine shall house all the other server software:

  • File Server (PeopleTools)
  • Application Server (Tuxedo)
  • Web Server (IBM WebSphere)
  • Batch Server

These two servers were accessed remotely using Remote Desktop Connection. Local administrator accounts were set up on these two machines. The username for these accounts were ProjAdmin1, ProjAdmin2 and ProjAdmin3.

Installation Sequence

The following steps were performed in this sequence to install the PeopleSoft Demo instance:

 PeopleSoft Demo Installation (FSDMO)

  1. Install SQL Server [ok 10-Nov-08]
  2. Install PeopleTools 8.49 on Database Server [17-Nov-08]
  3. Install PeopleTools 8.49 on Application Server [ok 11-Nov-08]
  4. Install Application (Financials) on Database Server [ok 17-Nov-08]
  5. Install Application (Financials) on Application Server [ok 11-Nov-08]
  6. Install Tuxedo (Application Server) [ok 11-Nov-08]
  7. Install PeopleTools 8.49.15 Product Patch on Database Server [ok 17-Nov-08]
  8. Install PeopleTools 8.49.15 Product Patch on Application Server [ok 12-Nov-08]
  9. Install IBM WebSphere (Web Server) [ok 11-Nov-08]
  10. Create Database Manually [ok 18-Nov-08]
  11. Shutdown, Backup Database After Creating
  12. Install PIA for WebSphere (fsdmo) [ok 18-Nov-08] [reinstall WebLogic 28-Nov-08]
  13. Create Application Domain [ok 18-Nov-08]
  14. Install PeopleTools PeopleBooks [ok 18-Nov-08] [reinstall 1-Dec-08]
  15. Install Application PeopleBooks [ok 18-Nov-08] [reinstall 1-Dec-08]
  16. Create Process Scheduler [ok 18-Nov-08]
  17. Apply Maintenance Pack 5 (Financials)

PeopleSoft Demo Installation (FSDEMO)

This FSDEMO installation shall be a plain-vanilla installation (without MP5).

  1. Install SQL Server [already installed]
  2. Install PeopleTools 8.49 on Application Server [ok 15-Dec-08] [E:PSOFTFSDEMO]
  3. Install PeopleTools 8.49 on Database Server [ok 15-Dec-08] [D:PSOFTFSDEMO]
  4. Install Application CDs (Financials) on Database Server [ok 15-Dec-08]
  5. Install Application CDs (Financials) on Application Server [ok 15-Dec-08]
  6. Install PeopleTools 8.49.15 Product Patch on Database Server [ok 15-Dec-08]
  7. Install PeopleTools 8.49.15 Product Patch on Application Server [ok 15-Dec-08]
  8. Install Tuxedo CD (Application Server) [already installed in E:bea]
  9. Install IBM WebSphere CD (Web Server) [already installed in E:IBMWebSphere]
  10. Create Database Manually [ok 18-Nov-08]
  11. Shutdown, Backup Database After Creating
  12. Install PIA for WebSphere (fsdmo) [ok 18-Nov-08] [reinstall WebLogic 28-Nov-08]
  13. Create Application Domain [ok 18-Nov-08]
  14. Install PeopleTools PeopleBooks [ok 18-Nov-08] [reinstall 1-Dec-08]
  15. Install Application PeopleBooks [ok 18-Nov-08] [reinstall 1-Dec-08]
  16. Create Process Scheduler [ok 18-Nov-08]
  17. Apply Maintenance Pack 5 (Financials)

PeopleSoft Sys Installation

  1. Install SQL Server [ok 10-Nov-08]
  2. Install PeopleTools 8.49 on Database Server [17-Nov-08]
  3. Install PeopleTools 8.49 on Application Server [ok 11-Nov-08]
  4. Install Application (Financials) on Database Server [ok 17-Nov-08]
  5. Install Application (Financials) on Application Server [ok 11-Nov-08]
  6. Install Tuxedo (Application Server) [ok 11-Nov-08]
  7. Install PeopleTools 8.49.15 Product Patch on Database Server [ok 17-Nov-08]
  8. Install PeopleTools 8.49.15 Product Patch on Application Server [ok 12-Nov-08]
  9. Install IBM WebSphere (Web Server) [ok 11-Nov-08]
  10. Create Database Manually [ok 18-Nov-08]
  11. Install PIA for WebSphere (fsdmo) [ok 18-Nov-08]
  12. Create Application Domain [ok 18-Nov-08]
  13. Install PeopleTools PeopleBooks [ok 18-Nov-08]
  14. Install Application PeopleBooks [ok 18-Nov-08]
  15. Create Process Scheduler
  16. Install Crystal Reports (on Workstation)
  17. Install Change Assistant
  18. Apply Maintenance Pack 5 (Financials)

Precedence

The SQL Server software must be installed before the PeopleTools.

PeopleTools Product Patch must be installed before PIA.

Step 1: SQL Server Installation

The Microsoft SQL Server 2005 DVD was staged (that is, copied) to D:stagingSQLServer2005 on the GLDBASE machine. After staging, setup.exe from D:stagingSQLServer2005Servers was run.

By default, the following required components were installed prior to installing SQL Server:

  • .NET Framework 2.0
  • Microsoft SQL Native Client
  • Microsoft SQL Server 2005 Setup Support Files

These components were installed to C:Program FilesMicrosoft SQL Server by default.

The other SQL Server components were installed to D:Program FilesMicrosoft SQL Server. These components are:

  • Database Services
    • Data Files
    • Replication
    • Full-Text Search
    • Shared Tools
  • Client Components
    • Connectivity Components
    • Management Tools

The Microsoft SQL Native Client (SNaC) must also be installed on the GLWEBAPP machine in which PeopleTools is installed. To do so, share the D:staging directory on GLDBASE (10.18.14.31). From GLWEBAPP, navigate to \10.x.x.xstagingSQLServer2005Servers. Then run setup.exe.

Allow the required components to install (.NET Framework 2.0, Microsoft SQL Native Client and Microsoft SQL Server 2005 Setup Support Files). Continue the installation and install the Connectivity Components on GLWEBAPP.

Step 2: File Server (PeopleTools) Installation

It was necessary to install up the SQL Server Connectivity Components on the GLWEBAPP because the SQL Server Connectivity Program Directory must be specified as part of the installation.

The seven PeopleTools CDs were staged to the E:stagingCDImages

Note that you MUST install PeopleTools on both nodes.

The following values/options were set as part of the PeopleTools installation on the peoplesoft4hr node:

Variable Value
PeopleSoft (PeopleTools) License code z66smq-22c7mc-3w444e1-2is234-81p1f7
Type of Database Non-Unicode Database
Peoplesoft Application Server Checked
Peoplesoft Batch Server Checked
Peoplesoft Database Server Checked
Peoplesoft File Server Checked
Peoplesoft Web Server Checked
PS_HOME Drectory Name E:PSOFTHR900
ERP Connectors? No
Connectivity Program Directory C:Program FilesMicrosoft SQL Server80Toolsbinn
Install PeopleTools Icons? Yes
PeopleTools Program Group Folder PeopleTools 8.4
Environment Hub machine name Peoplesoft4hr
Environment Hub Port Number 8000
PeopleTools (Product Installation) Checked
PeopleTools System Database Checked
PeopleTools Language Pack Not checked
PeopleTools Language Development Kit Not checked

Step 3: Application Installation

To install the PeopleSoft Enterprise Human Resources Management System and Campus Solutions 9.0 (HR) application, the disk was obtained from the CD. It was unzipped (“exploded”) and staged to the F:stagingcd849-HR directory, in the disk1 directory.

To install the Financials application, navigate to F:stagingcd849-HRdisk1 directory and run setup.exe

The following values/options were entered

Variable Value
PeopleSoft (HRMS) License code
Type of Database Non-Unicode Database
PeopleSoft Application Server Checked
PeopleSoft Batch Server Checked
PeopleSoft Database Server Checked
PeopleSoft File Server Checked
PeopleSoft Web Server Checked
PS_HOME Directory Name E:PSOFTFS900

Step 4: Application Server (Tuxedo) Installation

The Tuxedo 9.1 CD (Windows version) was staged to E:stagingCDImagescd849-Tuxdisk1 on the GLWEBAPP server. To install Tuxedo, run pstuxinstall.exe. This brings up a console interface (as opposed to a GUI wizard).

The following prompts appeared when psstuxinstall.exe is run:

1 file(s) copied.

1 file(s) copied.

BEA Home being defaulted to C:\bea  (y/n)? [y]: n

Please provide a BEA Home: E:\bea

Tuxedo 9.1 will be installed to E:\beaTuxedo9.1  (y/n)? [y]: <Enter>

TListen port being defaulted to 3050  (y/n)? [y]: <Enter>

Accept default TListen password ‘password’  (y/n)? [y]: <Enter>

Are you happy with your selections (y/n)? [y]: <Enter>

Tuxedo 9.1 is being installed on your system….

Tuxedo 9.1 base install completed.

Stopping Tuxedo 9.1 Services…

The TListen 9.1 (Port: 3050) service is stopping..

The TListen 9.1 (Port: 3050) service was stopped successfully.

The BEA ProcMGR V9.1 service is stopping.

The BEA ProcMGR V9.1 service was stopped successfully.

Patch installation completed.

Please note that you must reboot your system before using any Tuxedo 9.1 or PeopleSoft applications.

Press any key to continue…

After installing Tuxedo, the GLWEBAPP server was rebooted remotely.

Step 5: Web Server (WebSphere) Installation

The two IBM WebSphere CDs (Windows version) were staged to the E:stagingCDImagescd849-WebSphere directories, in the disk1 and disk2 directories.

To install IBM WebSphere, navigate to disk1 and run installWAS.bat.

Install to E:IBMWebSphereAppServer

For Environments, choose None, then click Yes to accept the choice.

In the Summary screen, click Next.

Uncheck the Create a new WebSphere Application Server profile, and then click Finish.

Step 6: PeopleTools 8.49.15 Product Patch Installation

Check Customer Connection (now Metalink3 at http://metalink3.oracle.com) for the latest PeopleTools 8.49 Product Patch. As at this time, the latest PeopleTools Product Patch for version 8.49 is 8.49.15.

Download this patch 84915.exe from:

ftp://ftp.peoplesoft.com/outgoing/ptools/84915/84915.exe

(The password for 84915.exe is ‘MisterEd’)

Run 84915.exe and unzip the file to E:stagingCDImages. It automatically creates the cd84915 directory and unzips the file.

From E:stagingCDImagescd84915disk1, run setup.exe. It updates PS_HOME (E:PSOFTFS900) with the updated files.

Step 7: Pure Internet Architecture (PIA) Installation

To create the PIA, change directory to E:PSOFTFS900PsMpPIAInstall and run setup.exe

Install PIA to the IBM WebSphere web server, located in E:IBMWEBSPHEREAppServer.

Application name and web site name should be set to the name of the environment e.g. fsdmo. Create a Multi Server installation, not a Single Server installation.

Note that the port numbers for http and https must not be consecutive.

Web Profile Name, User ID and Password should remain the default.

The Report Repository should be set to E:psreports.

The installation process takes about ten minutes to complete.

PIA Installation on IBM WebSphere Hangs on 20%

Posted by on February 4, 2009 Comments Off on PIA Installation on IBM WebSphere Hangs on 20%

PIA Installation on IBM WebSphere Hangs on 20%

Problem:

When installing new PIA on IBM WebSphere, the installation hangs for several minutes at 20%

Solution:

Installation takes a long time to complete. If the timeout is not long enough, the installation may fail. (Applying MP5 appears to have resolved this). Else, manually increase the timeout.

Setting Up IBM WebSphere as a Service

Posted by on February 2, 2009 Comments Off on Setting Up IBM WebSphere as a Service

Problem:

If the user that starts the IBM WebSphere web server logs off the system, the web server is shut down. A Windows service must be created to ensure that the web service(s) remain running.

Solution:

At Command Prompt, issue the following commands:

E:
 cd E:IBMWebSphereAppServerbin
 WASService.exe -add fsdev -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservfsdev -logFile E:IBMWebSphereAppServerlogsstartNodefsdev.log -restart true -startType automatic
WASService.exe -add fsdmo -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservPIA_fsdmo -logFile E:IBMWebSphereAppServerlogsstartNodefsdmo.log -restart true -startType automatic
E:IBMWebSphereAppServerbin>cd E:IBMWebSphereAppServerbin
E:IBMWebSphereAppServerbin>WASService.exe -add fsdev -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservfsdev -logFile E:IBMWebSphereAppServerlogsstartNodefsdev.log -restart true –startType automatic
 Adding Service: fsdev
 Config Root: E:PSOFTFS900webservfsdevconfig
 Server Name: server1
 Profile Path: E:PSOFTFS900webservfsdev
 Was Home: E:IBMWebSphereAppServer
 Start Args:
 Restart: 1
 IBM WebSphere Application Server V6.1 - fsdev service successfully added.
 E:IBMWebSphereAppServerbin>
The “IBM WebSphere Application Server V6.1 – fsdev” service is created.
Note that the log file is E:IBMWebSphereAppServerlogsstartNodefsdev.log
E:>E:
 E:>cd E:IBMWebSphereAppServerbin
E:IBMWebSphereAppServerbin>WASService.exe -add tramdmo -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservPIA_tramdmo -logFile E:IBMWebSphereAppServerlogsstartNodetramdmo.log -restart true -startType automatic
 Adding Service: tramdmo
 Config Root: E:PSOFTFS900webservPIA_tramdmoconfig
 Server Name: server1
 Profile Path: E:PSOFTFS900webservPIA_tramdmo
 Was Home: E:IBMWebSphereAppServer
 Start Args:
 Restart: 1
 IBM WebSphere Application Server V6.1 - tramdmo service successfully added.
To remove the service:
 cd E:IBMWebSphereAppServerbin
 WASService.exe -remove tramdmo
E:>E:
 E:>cd E:IBMWebSphereAppServerbin
E:IBMWebSphereAppServerbin>WASService.exe -add peoplebooks -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservPSOL_fsdmo -logFile E:IBMWebSphereAppServerlogsstartNodepeoplebooks.log -restart true -startType automatic
Adding Service: peoplebooks
 Config Root: E:PSOFTFS900webservPSOL_fsdmoconfig
 Server Name: server1
 Profile Path: E:PSOFTFS900webservPSOL_fsdmo
 Was Home: E:IBMWebSphereAppServer
 Start Args:
 Restart: 1
 IBM WebSphere Application Server V6.1 - peoplebooks service successfully added.
 E:IBMWebSphereAppServerbin>
To remove the service:
 cd E:IBMWebSphereAppServerbin
 WASService.exe -remove peoplebooks

Reference:
http://handly.blogspot.com/2008/05/setting-up-websphere-61-cluster-to.html

Setting up the WebSphere Node Manager as a Windows service

First, you need to set up the Node Manager on each physical server to run as a service and restart after a reboot:

Open a Command Window and go to the ..IBMWebSphereAppServerbin directory
Type in the following command (adjusted for your install paths):

WASService -add “IBM WebSphere Node Agent” -servername nodeagent -profilePath D:IBMWebSphereAppServerprofilesAppSrv01 -wasHome D:IBMWebsphereAppserver -logFile D:IBMWebSphereAppServerprofilesAppSrv01logsnodeagentstartNode.log -logRoot D:IBMWebSphereAppServerprofilesAppSrv01logsnodeagent -restart true -startType automatic

Uninstalling PeopleSoft PIA for WebSphere

Posted by on January 19, 2009 No comments

1. In WebSphere Administration Console http://server:9060/ibm/console, log on as user admin

2. Applications > Enterprise Applications

3. Check fsdmo and then Stop

4. Check fsdmo and then Uninstall

5. Save configuration changes

6. Repeat for 9061 (PSEMHUB) and 9062 (PSOL)

7. Stop WebSphere using the command:

webserv\binstopServer.bat server1

e.g.
E:PSOFTFS900webservPIA_fsdmobinstopServer.bat server1
E:PSOFTFS900webservPSEMHUB_fsdmobinstopServer.bat server1
E:PSOFTFS900webservPSOL_fsdmobinstopServer.bat server1

8. Uninstall profiles using the commands:

manageprofiles.bat –delete -profileName

e.g.
cd /d E:PSOFTFS900webserv
PIA_fsdmobinmanageprofiles.bat -delete -profileName PIA_fsdmo
PSEMHUB_fsdmobinmanageprofiles.bat -delete -profileName PSEMHUB_fsdmo
PSOL_fsdmobinmanageprofiles.bat -delete -profileName PSOL_fsdmo

9. Delete the PIA_fsdmo, PSEMHUB_fsdmo and PSOL_fsdmo directories.

10. Reboot the server.

Reference:

Page 173-174, Enterprise PeopleTools 8.49 Installation for Microsoft SQL Server

IBM WebSphere 6.1.0.17 Download Location

Posted by on December 31, 2008 No comments

Problem:

Where is the IBM WebSphere 6.1.0.17 for PeopleSoft located?

Solution:

ftp://ftp.peoplesoft.com/outgoing/ptools/websphere/WAS61017

Starting PeopleSoft Services

Posted by on December 20, 2008 No comments

Starting Application Server
To start the application server, log on to the gl-web-app server (10.18.14.30) using Terminal Services Client. Open Command Prompt and enter the following commands (in bold red):

C:> E:
E:> cd PSOFTFS900appserv
E:PSOFTFS900appserv> psadmin.exe

Enter the following options:
1) Application Server
1) Administer a domain
1) FSDMO
1) Boot this domain
1) Boot (Serial Boot)

Starting Batch Server/Process Scheduler

To start the batch server, log on to the gl-web-app server (10.18.14.30) using Terminal Services Client. Open Command Prompt and enter the following commands:

E:
cd PSOFTFS900appserv
psadmin.exe

Enter the following options:
2) Process Scheduler
1) Start a Process Scheduler Server
1) FSDMO

Starting Web Server (BEA WebLogic)

To start the batch server, log on to the gl-web-app server (10.18.14.30) using Terminal Services Client. Open Command Prompt and enter the following commands:

E:
Cd PSOFTFS900webservfsdmobin
startWebLogicAdmin.cmd

The final line shows:

Open a second Command Prompt and enter the following commands:

E:
Cd PSOFTFS900webservfsdmobin
startManagedWebLogic.cmd PIA

The final line shows:

Starting Web Server (IBM WebSphere)

Single Node
cd /d E:PSOFTFS900webservfsdevbin
startserver.bat server1 -profileName fsdev

Multi Node
cd /d E:PSOFTFS900webservPIA_fsdmobin
startserver.bat server1 -profileName PIA_fsdmo

CopyUpdateProject fails

Posted by on December 8, 2008 No comments

Problem:

In Change Assistant, the CopyUpdateProject step fails:

Step Failed at: Copy Update Project

Contents of E:tempsoftwareupdateFSCM900_MP5{bb2f249c-b59c-11dd-aaa1-aa1d90f67f05}FSCM900_MP5.log:

PeopleSoft Project Command Line
Copy From File
Project Name: FSCM900_MP5
Tools Release: 8.49.15
2008-12-08 : 10.55.54

-CT Source Database Type = MICROSFT
-CS Source Database Server =
-CD Source Database Name = FSDMO
-CO Source Database Operator = VP1
-FP File Path = E:/staging/softwareupdateFSCM900_MP5{bb2f249c-b59c-11dd-aaa1-aa1d90f67f05}
-CL Commit Limit = 100
-AF Keep Target Audit Flags = 1
-DDL Keep Target DDL = 1
-CFD Keep Target Chartfield PageField Display Size = 1
-CFF Keep Target Chartfield DbField Format = 1
-PPL Keep Target Portal Structure Permission List = 1
-OBJ Object Types = All
-LNG Languages = ENG,COMMON

Project FSCM900_MP5 already exists, continuing processing, switch set to overwrite.
Transforming XML. Please be patient.
Processing Language : English
Processing Language : COMMON

Records Application Upgrade Copy started: 2008-12-08-10.58.38

Contents of E:tempsoftwareupdateFSCM900_MP5{bb2f249c-b59c-11dd-aaa1-aa1d90f67f05}FSCM900_MP5_CA.log

Command Line: E:PSOFTFS900binclientwinx86pside.exe -CT MICROSFT -CS -CD FSDMO -CO VP1 -CP * -PJFF FSCM900_MP5 -FP E:/staging/softwareupdateFSCM900_MP5{bb2f249c-b59c-11dd-aaa1-aa1d90f67f05} -LF E:tempsoftwareupdateFSCM900_MP5{bb2f249c-b59c-11dd-aaa1-aa1d90f67f05}FSCM900_MP5.log -CL 100 -AF 1 -DDL 1 -OBJ All -LNG ENG,COMMON -PPL 1 -CFD 1 -CFF 1 -HIDE -QUIET -SS NO -SN NO

Solution:

1. Batch server was running. Stopped batch server and restarted the CopyUpdateProject step.
2. Batch server started, and then restarted the CopyUpdateProject step.
3. Application server was running, stopped it and then restarted the CopyUpdateProject step.

(Advised by consultant) Skipped this step as it was previously deployed under IBM WebSphere.

psSharedLibrary classpath entry missing jar

Posted by on November 27, 2008 No comments

Problem:

After resolving the port issue (see above), the file E:PSOFTFS900webservPSEMHUB_fsdmologsserver1SystemOut.log shows:

[11/27/08 14:50:03:718 VET] 0000000a ModuleManifes E UTLS0002E: The shared library psSharedLibrary contains a classpath entry which does not resolve to a valid jar file, the library jar file is expected to be found at E:PSOFTFS900webservPSEMHUB_fsdmoinstalledAppsPSEMHUB_fsdmoNodeCellPSEMHUB.earPSIGW.warWEB-INFlibmail.jar.
[11/27/08 14:50:03:843 VET] 0000000a ModuleManifes E UTLS0002E: The shared library psSharedLibrary contains a classpath entry which does not resolve to a valid jar file, the library jar file is expected to be found at E:PSOFTFS900webservPSEMHUB_fsdmoinstalledAppsPSEMHUB_fsdmoNodeCellPSEMHUB.earPSIGW.warWEB-INFlibactivation.jar.

Solution:

Copied:

E:PSOFTFS900webservPIA_fsdmoinstalledAppsPIA_fsdmoNodeCellfsdmo.earPSIGW.war

To:

E:PSOFTFS900webservPSEMHUB_fsdmoinstalledAppsPSEMHUB_fsdmoNodeCellPSEMHUB.ear

After this, the file shows:

************ Start Display Current Environment ************
WebSphere Platform 6.1 [ND 6.1.0.3 cf30646.29] running with process name PSEMHUB_fsdmoNodeCellPSEMHUB_fsdmoNodeserver1 and process id 3576
Host Operating System is Windows Server 2003, version 5.2 build 3790 Service Pack 1
Java version = J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223-20061001 (JIT enabled)
J9VM – 20060915_08260_lHdSMR
JIT – 20060908_1811_r8
GC – 20060906_AA, Java Compiler = j9jit23, Java VM name = IBM J9 VM
was.install.root = E:IBMWebSphereAppServer
user.install.root = E:PSOFTFS900webservPSEMHUB_fsdmo
Java Home = E:IBMWebSphereAppServerjavajre
ws.ext.dirs = E:IBMWebSphereAppServer/java/lib;E:PSOFTFS900webservPSEMHUB_fsdmo/classes;E:IBMWebSphereAppServer/classes;E:IBMWebSphereAppServer/lib;E:IBMWebSphereAppServer/installedChannels;E:IBMWebSphereAppServer/lib/ext;E:IBMWebSphereAppServer/web/help;E:IBMWebSphereAppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime
Classpath = E:PSOFTFS900webservPSEMHUB_fsdmo/properties;E:IBMWebSphereAppServer/properties;E:IBMWebSphereAppServer/lib/startup.jar;E:IBMWebSphereAppServer/lib/bootstrap.jar;E:IBMWebSphereAppServer/lib/j2ee.jar;E:IBMWebSphereAppServer/lib/lmproxy.jar;E:IBMWebSphereAppServer/lib/urlprotocols.jar;E:IBMWebSphereAppServer/deploytool/itp/batchboot.jar;E:IBMWebSphereAppServer/deploytool/itp/batch2.jar;E:IBMWebSphereAppServer/java/lib/tools.jar
Java Library path = E:IBMWebSphereAppServerjavajrebin;.;E:IBMWebSphereAppServerbin;E:IBMWebSphereAppServerjavabin;E:IBMWebSphereAppServerjavajrebin;E:PSOFTFS900binclientwinx86;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;E:beaTuxedo9.1bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;C:PS_HOMEbinclientwinx86;C:Program FilesMicrosoft SQL Server80ToolsBinn;C:Program FilesMicrosoft SQL Server90Toolsbinn;C:Program FilesMicrosoft SQL Server90DTSBinn;C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDE;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin
************* End Display Current Environment *************

PSEM Agents Not Starting

Posted by on November 27, 2008 No comments

Problem:

When the StartAgent.bat command is executed, the following appears:

E:PSOFTFS900PSEMAgent>StartAgent.bat

ERROR main EMF_CATEGORY – Error while connecting to ‘http://glwebapp:8001/PSEMHUB/hub’.
ERROR main EMF_CATEGORY – Error: Internal Exception: – Error registering peer
ERROR main EMF_CATEGORY – Error while connecting to server – retrying attempt 1
ERROR main EMF_CATEGORY – Error while connecting to ‘http://glwebapp:8001/PSEMHUB/hub’.
ERROR main EMF_CATEGORY – Error: Internal Exception: – Error registering peer
ERROR main EMF_CATEGORY – Error while connecting to server – retrying attempt 2

Troubleshooting:

In Command Prompt, stopped the PSEMHUB profile with the following commands:

set PATH=%PATH%;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin

cd /d E:PSOFTFS900webserv

PSEMHUB_fsdmobinstopServer.bat server1 -profileName PSEMHUB_fsdmo

Moved all the files in E:PSOFTFS900webservPSEMHUB_fsdmologsserver1 to backup_20081127a.

Then restarted the PSEMHUB profile:

set PATH=%PATH%;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin

cd /d E:PSOFTFS900webserv

PSEMHUB_fsdmobinstartServer.bat server1 -profileName PSEMHUB_fsdmo

The E:PSOFTFS900webservPSEMHUB_fsdmologsserver1SystemOut.log contains the following error:

************ Start Display Current Environment ************
WebSphere Platform 6.1 [ND 6.1.0.3 cf30646.29] running with process name PSEMHUB_fsdmoNodeCellPSEMHUB_fsdmoNodeserver1 and process id 260
Host Operating System is Windows Server 2003, version 5.2 build 3790 Service Pack 1
Java version = J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223-20061001 (JIT enabled)
J9VM – 20060915_08260_lHdSMR
JIT – 20060908_1811_r8
GC – 20060906_AA, Java Compiler = j9jit23, Java VM name = IBM J9 VM
was.install.root = E:IBMWebSphereAppServer
user.install.root = E:PSOFTFS900webservPSEMHUB_fsdmo
Java Home = E:IBMWebSphereAppServerjavajre
ws.ext.dirs = E:IBMWebSphereAppServer/java/lib;E:PSOFTFS900webservPSEMHUB_fsdmo/classes;E:IBMWebSphereAppServer/classes;E:IBMWebSphereAppServer/lib;E:IBMWebSphereAppServer/installedChannels;E:IBMWebSphereAppServer/lib/ext;E:IBMWebSphereAppServer/web/help;E:IBMWebSphereAppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime
Classpath = E:PSOFTFS900webservPSEMHUB_fsdmo/properties;E:IBMWebSphereAppServer/properties;E:IBMWebSphereAppServer/lib/startup.jar;E:IBMWebSphereAppServer/lib/bootstrap.jar;E:IBMWebSphereAppServer/lib/j2ee.jar;E:IBMWebSphereAppServer/lib/lmproxy.jar;E:IBMWebSphereAppServer/lib/urlprotocols.jar;E:IBMWebSphereAppServer/deploytool/itp/batchboot.jar;E:IBMWebSphereAppServer/deploytool/itp/batch2.jar;E:IBMWebSphereAppServer/java/lib/tools.jar
Java Library path = E:IBMWebSphereAppServerjavajrebin;.;E:IBMWebSphereAppServerbin;E:IBMWebSphereAppServerjavabin;E:IBMWebSphereAppServerjavajrebin;E:PSOFTFS900binclientwinx86;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;E:beaTuxedo9.1bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;C:PS_HOMEbinclientwinx86;C:Program FilesMicrosoft SQL Server80ToolsBinn;C:Program FilesMicrosoft SQL Server90Toolsbinn;C:Program FilesMicrosoft SQL Server90DTSBinn;C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDE;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin
************* End Display Current Environment *************
[11/27/08 11:14:53:265 VET] 0000000a ModuleManifes E UTLS0002E: The shared library psSharedLibrary contains a classpath entry which does not resolve to a valid jar file, the library jar file is expected to be found at E:PSOFTFS900webservPSEMHUB_fsdmoinstalledAppsPSEMHUB_fsdmoNodeCellPSEMHUB.earPSIGW.warWEB-INFlibmail.jar.
[11/27/08 11:14:53:390 VET] 0000000a ModuleManifes E UTLS0002E: The shared library psSharedLibrary contains a classpath entry which does not resolve to a valid jar file, the library jar file is expected to be found at E:PSOFTFS900webservPSEMHUB_fsdmoinstalledAppsPSEMHUB_fsdmoNodeCellPSEMHUB.earPSIGW.warWEB-INFlibactivation.jar.
[11/27/08 11:16:00:546 VET] 0000000a TCPPort E TCPC0003E: TCP Channel TCP_4 initialization failed. The socket bind failed for host * and port 8500. The port may already be in use.
[11/27/08 11:16:00:546 VET] 0000000a WSChannelFram E CHFW0034W: The Transport Channel Service detected transport chain WCInboundDefaultSecure failed. The service will retry to start chain WCInboundDefaultSecure every 5000 milliseconds for up to 60 attempts.
[11/27/08 11:16:00:562 VET] 0000000a TCPPort E TCPC0003E: TCP Channel TCP_4 initialization failed. The socket bind failed for host * and port 8500. The port may already be in use.
[11/27/08 11:16:00:562 VET] 0000000a WSChannelFram E CHFW0034W: The Transport Channel Service detected transport chain SOAPAcceptorChain3 failed. The service will retry to start chain SOAPAcceptorChain3 every 5000 milliseconds for up to 60 attempts.

Netstat showed the following output:

E:PSOFTFS900webservPSEMHUB_fsdmo>netstat -na|more

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:86 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2809 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2810 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2811 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8000 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8002 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8500 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8502 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8880 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8881 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8882 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9043 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9044 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9045 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9060 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9061 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9062 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9100 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9101 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9102 0.0.0.0:0 LISTENING
TCP 10.18.14.30:139 0.0.0.0:0 LISTENING
Note that port 8501 is not used.

Check ports of PIA: pointed web browser to http://glwebapp:9060/ibm/console/. Logged on as admin. On the left pane, navigated to Servers > Application Servers. Click server1, and under Communications, click Ports.

Note that the WC_defaulthost_secure is 8500.

Check ports of PSEM: pointed web browser to http://glwebapp:9061/ibm/console/. Logged on as admin. On the left pane, navigated to Servers > Application Servers. Click server1, and under Communications, click Ports.

Note that the WC_defaulthost_secure is also 8500. It should be 8501(?)

Click WC_default_secure, and then change the port number from 8500 to 8501. The following message appears:

One or more virtual hosts match the previous host name and port combination of “*:8500” and do not match the new combination of “*:8501.” You might need to update the host aliases.
Changes have been made to your local configuration. You can:

• Save directly to the master configuration.
• Review changes before saving or discarding.

The server may need to be restarted for these changes to take effect.

The PSEM profile is stopped and started using the steps shown above.

After stopping PSEM web profile and restarting, the following error appears:

Recover prior changes

Your prior session timed out before the changes could be published to the master configuration. Would you like to recover the changes made in the prior session or work with the master configuration?

Work with the master configuration
Recover changes made in prior session View items with changes

Changed Items Status
cells / PSEMHUB_fsdmoNodeCell / nodes / PSEMHUB_fsdmoNode / serverindex.xml Updated

Also:

Enterprise Applications > Save
Save your workspace changes to the master configuration.

Click Save to update the master repository with your changes.
Click Discard to discard your changes and begin work again using the master repository configuration.
Click Cancel to continue working with your changes.

Total changed documents: 2

Changed Items Status
cells / PSEMHUB_fsdmoNodeCell / nodes / PSEMHUB_fsdmoNode / serverindex.xml Updated
cells / PSEMHUB_fsdmoNodeCell / applications / PSEMHUB.ear / deployments / PSEMHUB / deployment.xml

After saving the master configuration, PSEM was stopped and restarted. The file E:PSOFTFS900webservPSEMHUB_fsdmologsserver SystemOut.log showed:

************ Start Display Current Environment ************
WebSphere Platform 6.1 [ND 6.1.0.3 cf30646.29] running with process name PSEMHUB_fsdmoNodeCellPSEMHUB_fsdmoNodeserver1 and process id 2580
Host Operating System is Windows Server 2003, version 5.2 build 3790 Service Pack 1
Java version = J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223-20061001 (JIT enabled)
J9VM – 20060915_08260_lHdSMR
JIT – 20060908_1811_r8
GC – 20060906_AA, Java Compiler = j9jit23, Java VM name = IBM J9 VM
was.install.root = E:IBMWebSphereAppServer
user.install.root = E:PSOFTFS900webservPSEMHUB_fsdmo
Java Home = E:IBMWebSphereAppServerjavajre
ws.ext.dirs = E:IBMWebSphereAppServer/java/lib;E:PSOFTFS900webservPSEMHUB_fsdmo/classes;E:IBMWebSphereAppServer/classes;E:IBMWebSphereAppServer/lib;E:IBMWebSphereAppServer/installedChannels;E:IBMWebSphereAppServer/lib/ext;E:IBMWebSphereAppServer/web/help;E:IBMWebSphereAppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime
Classpath = E:PSOFTFS900webservPSEMHUB_fsdmo/properties;E:IBMWebSphereAppServer/properties;E:IBMWebSphereAppServer/lib/startup.jar;E:IBMWebSphereAppServer/lib/bootstrap.jar;E:IBMWebSphereAppServer/lib/j2ee.jar;E:IBMWebSphereAppServer/lib/lmproxy.jar;E:IBMWebSphereAppServer/lib/urlprotocols.jar;E:IBMWebSphereAppServer/deploytool/itp/batchboot.jar;E:IBMWebSphereAppServer/deploytool/itp/batch2.jar;E:IBMWebSphereAppServer/java/lib/tools.jar
Java Library path = E:IBMWebSphereAppServerjavajrebin;.;E:IBMWebSphereAppServerbin;E:IBMWebSphereAppServerjavabin;E:IBMWebSphereAppServerjavajrebin;E:PSOFTFS900binclientwinx86;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;E:beaTuxedo9.1bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;C:PS_HOMEbinclientwinx86;C:Program FilesMicrosoft SQL Server80ToolsBinn;C:Program FilesMicrosoft SQL Server90Toolsbinn;C:Program FilesMicrosoft SQL Server90DTSBinn;C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDE;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin
************* End Display Current Environment *************
[11/27/08 14:39:35:968 VET] 0000000a ModuleManifes E UTLS0002E: The shared library psSharedLibrary contains a classpath entry which does not resolve to a valid jar file, the library jar file is expected to be found at E:PSOFTFS900webservPSEMHUB_fsdmoinstalledAppsPSEMHUB_fsdmoNodeCellPSEMHUB.earPSIGW.warWEB-INFlibmail.jar.
[11/27/08 14:39:36:093 VET] 0000000a ModuleManifes E UTLS0002E: The shared library psSharedLibrary contains a classpath entry which does not resolve to a valid jar file, the library jar file is expected to be found at E:PSOFTFS900webservPSEMHUB_fsdmoinstalledAppsPSEMHUB_fsdmoNodeCellPSEMHUB.earPSIGW.warWEB-INFlibactivation.jar.

Note that there is no reference to the port number.

The file E:PSOFTFS900webservPSEMHUB_fsdmologsserverstartServer.log showed:

************ Start Display Current Environment ************
Host Operating System is Windows Server 2003, version 5.2 build 3790 Service Pack 1
Java version = J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi3223-20061001 (JIT enabled)
J9VM – 20060915_08260_lHdSMR
JIT – 20060908_1811_r8
GC – 20060906_AA, Java Compiler = j9jit23, Java VM name = IBM J9 VM
was.install.root = E:IBMWebSphereAppServer
user.install.root = E:PSOFTFS900webservPSEMHUB_fsdmo
Java Home = E:IBMWebSphereAppServerjavajre
ws.ext.dirs = E:\IBM\WebSphere\AppServer\java\lib;E:\IBM\WebSphere\AppServer\classes;E:\IBM\WebSphere\AppServer\lib;E:\IBM\WebSphere\AppServer\installedChannels;E:\IBM\WebSphere\AppServer\lib\ext;E:\IBM\WebSphere\AppServer\web\help;E:\IBM\WebSphere\AppServer\deploytool\itp\plugins\com.ibm.etools.ejbdeploy\runtime
Classpath = E:PSOFTFS900webservPSEMHUB_fsdmoproperties;E:IBMWebSphereAppServerproperties;E:IBMWebSphereAppServerlibstartup.jar;E:IBMWebSphereAppServerlibbootstrap.jar;E:IBMWebSphereAppServer/lib/j2ee.jar;E:IBMWebSphereAppServer/lib/lmproxy.jar;E:IBMWebSphereAppServer/lib/urlprotocols.jar;E:IBMWebSphereAppServerjavalibtools.jar
Java Library path = E:IBMWebSphereAppServerjavajrebin;.;E:IBMWebSphereAppServerbin;E:IBMWebSphereAppServerjavabin;E:IBMWebSphereAppServerjavajrebin;E:PSOFTFS900binclientwinx86;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;E:beaTuxedo9.1bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;C:PS_HOMEbinclientwinx86;C:Program FilesMicrosoft SQL Server80ToolsBinn;C:Program FilesMicrosoft SQL Server90Toolsbinn;C:Program FilesMicrosoft SQL Server90DTSBinn;C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDE;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin;E:PSOFTFS900webservPSOL_fsdmoinstalledAppsPSOL_fsdmoNodeCellPSOL.earPSOL.warWEB-INFlibwinx86;E:PSOFTFS900veritywinx86_nti40bin
Current trace specification = *=info:com.ibm.*=all
************* End Display Current Environment *************

[11/27/08 14:39:29:515 VET] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info:com.ibm.*=all.
[11/27/08 14:39:29:515 VET] 0000000a WsServerContr 1 Executing executeUtilityOnWindows with args: E:PSOFTFS900webservPSEMHUB_fsdmoconfig PSEMHUB_fsdmoNodeCell PSEMHUB_fsdmoNode server1
[11/27/08 14:39:29:515 VET] 0000000a WsServerContr 1 Getting WindowsService obj with: server1 and E:PSOFTFS900webservPSEMHUB_fsdmoconfig PSEMHUB_fsdmoNodeCell PSEMHUB_fsdmoNode server1
[11/27/08 14:39:29:515 VET] 0000000a WindowsServic > getWindowsServiceNameForServer() Entry
[11/27/08 14:39:29:515 VET] 0000000a WindowsServic 1 In executeCommand, args are: E:IBMWebSphereAppServerbinWASService.exe -getServiceName server1 -profilePath E:PSOFTFS900webservPSEMHUB_fsdmo
[11/27/08 14:39:29:531 VET] 0000000a WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@456a456a
[11/27/08 14:39:29:531 VET] 0000000a WindowsServic 1 retCode from childProcess.waitFor() is 0
[11/27/08 14:39:29:531 VET] 0000000a WindowsServic 3 exitCode = 0
[11/27/08 14:39:30:531 VET] 0000000a WindowsServic 1 Trying to new up WindowsService using serverName=server1, winServiceName=null
[11/27/08 14:39:30:531 VET] 0000000a ManagerAdmin I TRAS0018I: The trace state has changed. The new trace state is *=info.
[11/27/08 14:39:30:562 VET] 0000000a AdminTool A ADMU0128I: Starting tool with the PSEMHUB_fsdmo profile
[11/27/08 14:39:30:562 VET] 0000000a AdminTool A ADMU3100I: Reading configuration for server: server1
[11/27/08 14:39:32:828 VET] 0000000a AdminTool A ADMU3200I: Server launched. Waiting for initialization status.
[11/27/08 14:40:41:796 VET] 0000000a AdminTool A ADMU3000I: Server server1 open for e-business; process id is 2580

Solution:

Ensure that the web server is started

References:

http://www-128.ibm.com/developerworks/forums/thread.jspa?threadID=169775&start=15&tstart=0