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

WebSphere Update Error

When updating a WebSphere fix pack, the following error can be seen from the IBM Installation Manager.

The update in this example is from WebSphere to Fix Pack 10 –

Looking at the error details shows that a dll file was unable to be deleted –

D:\IBM\WebSphere\AppServer\bin\WASServiceMsg.dll. This file can be locked by the Cell Manager when the server is started.

To resolve the issue, stop the WebSphere service in Computer Management and set it to manual start (not to start automatically).

Then find the file that was locked (WASServiceMsg.dll) and rename it to something like WASServiceMsg8550orig.dll.

Permissions may need to be added to the IBM directory to ensure Full Control is Allowed for your user id. Then restart the server and run the IBM Installation Manager again to apply the update.

Afterwards, you can see an updated version of the dll is available along with the original file that was renamed.

Be sure to change the service back to start automatically after the update is complete.

Configure WebSphere profile to use a different version of Java

There may be a time where you need to update your WebSphere profile to use a later version of Java.  One indication of this would be if you are installing an app in WebSphere, and you come across the error “The major.minor version ‘51.0’ is too recent for this tool to understand.”  This means that your application expects a newer Java SDK.

To determine which SDK your application is currently using,

  1. Open <WAS_HOME>/profiles/<profile>/logs/startServer.log
  2. Find the last server start entry
  3. Make not of the Java version

To update the SDK used by your WebSphere profile,

  1. Open a command prompt as administrator
  2. Navigate to <WAS_HOME>/profiles/<profile>/bin
  3. Type bat –listAvailable ( for Unix) to list the Java SDKs that are available for this profile (note the name of the SDK that you want to use)
  4. Type bat –enableProfileAll –sdkname <the name you noted earlier> -enableServers
  5. Syncrhonize the WebSphere nodes
  6. Restart the WebSphere application server
  7. Check the startServer.log to see that the java version has changed

For example:

WebSphere Application Server, update java sdk version, The major.minor version ‘51.0’ is too recent for this tool to understand

How to Setup Dependencies for Lawson Services

After dust from the upgrade settles, it’s usually time to automate any and everything that can be automated. When it comes to Lawson (LSF) related services though things can get a big tricky.

There’s a precise order bringing up the services on windows and one way to ensure this happens correctly is to setup service dependencies on your windows applications server.

Let’s first review what depends on what and why.

The services that need to come up are in order:

  1. ADLDS
  2. Lawson Environment
  3. IBM Webshphere Cell Manager (Optional)
  4. IBM Websphere Node Agent
  5. IBM Websphere Application Server
  6. Web server (IIS)

Obviously, since all the authentication work happens through ADLDS, it makes sense that it would be the services to come up first. And since ADLDS has it’s own set of dependencies, we don’t need to create new ones there.

Next we setup a dependencies for the Lawson Environment Service to depend on ADLDS.

To do this, bring up the services window (Start-> Run-> services.msc).

Right click on your ADLDS service and note the service name.

Right Click on your Lawson Environment Service and note the service name.

Now bring up a cmd prompt as administrator and type in the following command:

sc config [service name] depend= <Dependencies(separated by / (forward slash))>

Note: There is a space after the equals sign, and there is not one before it.

Warning: depend= parameter will overwrite existing dependencies list, not append. So for example, if ServiceA already depends on ServiceB and ServiceC, if you run depend= ServiceD, ServiceA will now depend only on ServiceD.


sc config laserv-prod depend= ADAM_ProdInfor10ADLDS

In the above example, my Lawson environment service is called “laserv-prod” and my ADLDS service is called: “ADAM_ProdInfor10ADLDS”.

Once you hit enter, a message should appear that says: “[SC] ChangeServiceConfig SUCCESS”

You have now setup a dependency for the Lawson Environment service to depend on ADLDS. You can confirm this by checking the service properties:

How to setup dependencies for Lawson services_1

Now you can continue with the rest of the services and setup dependencies as you go. Keep in mind that the Cell manager is really an optional service and you may not want it running all the time, so you can avoid that dependency if you like.

Next, you’ll want to change all the services named above to be automatic. We usually don’t setup any recovery options as they can lead to some unintended results.

In the end, your Web Server’s dependencies should look similar to this:

How to setup dependencies for Lawson services_2