Tuesday, 15 June 2010

WebSphere Portal 6.1.5.1 on WebSphere Application Server 7.0.0.9

This is the first of a work-in-progress series of articles as I move towards using WebSphere Portal on WebSphere Application Server (WAS) 7.0, rather than the default WAS 6.1.

*CAVEAT* THIS WORKS FOR ME - THAT DOESN'T MEAN IT'LL WORK FOR YOU - PLEASE PLEASE PLEASE FOLLOW THE IBM DOCUMENTATION LINKED BELOW *CAVEAT*

On my trusty Ubuntu 10.04 box ( now 32 rather than 64-bit, but with the PAE kernel ), I installed ( this morning ): -

WebSphere Application Server Network Deployment 7.0.0.0

into /opt/IBM/WebSphere/AppServer and then installed the WAS 7.0.0.9 Update Installer into /opt/IBM/WebSphere/UpdateInstaller.

Using the Update Installer, I upgraded WAS to the fix pack ( 7.0.0.9 ) required for WebSphere Portal 6.1.5.1.

I had already downloaded WebSphere Portal Server 6.1.5.0, and unpacked into /tmp using the following script: -

unzip CZ8G7ML.zip    -d /tmp/IL-Setup
mkdir                   /tmp/IL-1
tar xvzf CZ8H5ML.tgz -C /tmp/IL-1
unzip CZ8HDML.zi p   -d /tmp/IL-2
unzip CZ8I4ML.zip    -d /tmp/IL-3
unzip CZ8I5ML.zip    -d /tmp/IL-4
unzip CZ8I6ML.zip    -d /tmp/IL-5
unzip CZ8I7ML.zip    -d /tmp/IL-5A

Having done this, I installed WebSphere Portal Server 6.1.5.0 into /opt/IBM/WebSphere which automatically places the PortalServer code into /opt/IBM/WebSphere/PortalServer and the WAS profile into /opt/IBM/WebSphere/wp_profile.

I then downloaded the most recent Portal Update Installer and extracted it into a specially created directory - /opt/IBM/WebSphere/PortalServer/update.

I then downloaded the fixpack (  WP_PTF_6104.jar) from Fix Central, along with a co-requisite fix, PM15558.jar, and placed both fixes in /opt/IBM/WebSphere/PortalServer/update/fixpacks.

Having  updated /opt/IBM/WebSphere/wp_profile/ConfigEngine/properties/wkplc.properties, and set the WasPassword and PortalAdminPwd properties, I then installed the two pixies as follows: -

cd /opt/IBM/WebSphere/PortalServer/update

source /opt/IBM/WebSphere/wp_profile/bin/setupCmdLine.sh

./updatePortal.sh -install -installDir /opt/IBM/WebSphere/PortalServer/ -fixpack -fixpackDir /opt/IBM/WebSphere/PortalServer/update/fixpacks/ -fixpackID WP_PTF_6104

./updatePortal.sh -install -installDir /opt/IBM/WebSphere/PortalServer/ -fix -fixDir /opt/IBM/WebSphere/PortalServer/update/fixpacks/ -fixJars PM15558.jar

After a wee while, the job is done.

I checked the versions using the following two scripts: -

/opt/IBM/WebSphere/AppServer/bin/versionInfo.sh

which returns: -

<snip>
Installed Product
--------------------------------------------------------------------------------
Name                     IBM WebSphere Application Server - ND
Version                  7.0.0.9
ID                       ND
Build Level              cf091011.19
Build Date               3/17/10
Architecture             Intel (32 bit)
</snip>

and: -

/opt/IBM/WebSphere/PortalServer/bin/WPVersionInfo.sh

which returns: -

<snip>
Installed Product
--------------------------------------------------------------------------------
Name           IBM WebSphere Portal MultiPlatform
Version        6.1.0.4
ID             MP
Build Level    wp6104_031_01
Build Date     05/21/2010

Installed Product
--------------------------------------------------------------------------------
Name           IBM WebSphere Portal FeaturePack
Version        6.1.5.1
ID             FEAT615
Build Level    wp6104_031_01 2010-05-21
Build Date     05/21/2010
</snip>

and: -

/opt/IBM/WebSphere/PortalServer/update# /opt/IBM/WebSphere/PortalServer/bin/WPVersionInfo.sh -fixes

which returns: -

<snip>
Installed Fix
--------------------------------------------------------------------------------
ID             PM15558
Description    Fix for Performance degradation in sametime awareness code
Build Date     05/28/2010
Build Version  201005282300
</snip>

*CAVEAT* THIS WORKS FOR ME - THAT DOESN'T MEAN IT'LL WORK FOR YOU - PLEASE PLEASE PLEASE FOLLOW THE IBM DOCUMENTATION LINKED BELOW *CAVEAT*

No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...