Install WebSphere Fix Packs


Download Fix Packs

NOTE: You will need your passport advantage credentials

Application Server Fix Pack

Customization Toolbox Fix Pack

WAS Supplements fix pack

Unzip WAS parts 1 & 2 into one directory

Unzip WCT parts 1 & 2 into one directory

Unzip WAS Supp parts 1 & 2 into one directory

Install Fix Pack

Stop WebSphere Services

Open IBM Installation Manager as administrator

Set the repository in File > Preferences (select the location where you saved the fix pack files)

Click ok

Click update

Select all, click next

Accept the license agreements

Click update

Click Finish

Start WebSphere services

Propagate Plug-Ins

WebSphere Console > Servers > Server Types > Web servers

Select web server

Generate Plug-in

Propagate Plug-in

Restart Application Server

Installing CTPs in Lawson

Here is a quick reference to Install CTPs in Lawson.

  1. Download and save CTP to LSF Server
  2. Extract .tar (unzip) on LSF server to folder (d:\patch\CTPXXXX)
  3. Log on LID as Lawson
  4. Change directory to extracted CTP location:
    cd d:\patch\CTPXXXXX)
  5. Run command: perl %gendir%/bin/lawappinstall preview <PRODLINE> (make sure it completes successfully)
  6. Rename/Save Preview.log
  7. Run command: perl %gendir%/bin/lawappinstall update <PRODLINE> (make sure it completes successfully)
  8. Run command: perl %gendir%/bin/lawappinstall activate <PRODLINE> (make sure it completes successfully)
  9. Go to the Lawson application and perform general testing to make sure everything is up and running.


During the ACTIVATE mode if it stops at dbreorg, this is likely do to activity in DB (“database in use”) or “No such file or directory” Perform the following:

On the LSF Server

Window Services:  Stop the IBMWASXXService – LSFAPP – This prevents users from accessing Portal

Window Services:  Stop Lawson.insightEnvironment “PRODLINE” –  stops LID to disconnect LID users

Task Manager:  End all java processes

Windows Services:  Start Lawson.insightEnvironment “PRODLINE” – starts LID

In LID, run the reorg manually:  dbreorg PRODLINE

Run the ACTIVATE step again


Troubleshooting BSI Database Connection during Install

Your install is successful, but when you log on to the BSI Interface (Screen Print #1) you receive an error (Error Message. Exception is: org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Login failed for user ‘tf10’. ClientConnectionId:f0509232-la4c-4d22-b118-785e9ba8eee5). See Screen Print #2

You will receive this error if your SQL database is configured with a Named Instance. The Named Instance should be configured with a static port. You should not use the default port (1433) when installing the BSI Client even though your ODBC will connect successfully with the default port. Please see article on assigning a static port for SQL Server named instance: (

Screen Print #1

Troubleshooting BSI Database Connection during Install-1


Screen Print #2

Troubleshooting BSI Database Connection during Install-2