Caveat
This represents my own experiences with this fixpack - your experiences may vary. Please use caution, especially when working in a production environment.
Please see: -
6.0.0.1: WebSphere Portal version 6.0 fix pack 1
http://www-1.ibm.com/support/docview.wss?uid=swg24014281
and: -
WebSphere Portal Version 6.0.0.1
http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/topic/com.ibm.wp.ent.doc/wpf/pui_intro.html
for the formal IBM documentation.
Caveat
Right, here goes.
Firstly, download the fixes from here: -
https://www14.software.ibm.com/webapp/iwm/web/reg/download.do?source=swgwp-fixpacks&S_PKG=6001&lang=en_US&cp=UTF-8&dlmethod=http
In my environment ( a clean installation of WebSphere Portal 6.0.0 installed on WebSphere Application Server ND 6.0.2.9 and WebSphere Process Server 6.0.1.1 ), I only needed to download: -
WebSphere Portal version 6.0 fix pack 1 (6.0.0.1 ZIP archive)
6.0.0-WP-Multi-FP001.zip (418MB)
PK31711 - Full production-capable support of composite application workflow.
6.0.0.1-WP-Multi-IFPK31711.zip (4.1MB)
PK35227 - Creation or edit of composite application/template fails using DB2 on z/OS.
6.0.0.1-WP-Multi-IFPK35227.zip (9.9KB)
PK35520 - My Tasks portlet is unavailable.
6.0.0.1-WP-Multi-IFPK35520.zip (3.7KB)
plus: -
Required WebSphere Application Server V6.0.2.13 fixes
6.0.0.1-WP-WSASv6.0.2.13-IFPackage.zip (7MB)
However, your mileage may vary.
There are other fixes for various versions of WebSphere Application Server and WebSphere Process Server.
Check your versions and choose as appropriate
Ialso downloaded the latest version of the Portal Update Installer: -
WebSphere Portal Update Installer for version 6
PortalUpdateInstaller.zip (9.6MB)
In my testing, I found that I had to use a version of this later than October 24, 2006.
I then performed the installation as follows: -
a) Install 6.0.2-WS-WAS-IFPK29636.pak by simply double-clicking on .PAK file; the association with WebSphere is already set up
b) Using WinZIP, expand the Portal Update Installer to \WP6\WebSphere\PortalServer\updates
c) Using WinZIP, expand the three other PKxxxxx fixes to \WP6\WebSphere\PortalServer\updates\fixes ( note that you will need to create this subdirectory )
d) Using WinZIP, expand 6.0.0-WP-Multi-FP001.zip to \WP6\WebSphere\PortalServer\updates\fixes
e) Edit \WP6\WebSphere\PortalServer\config\wpconfig.properties and set a value for the property PortalAdminPwd
f) Open a command prompt
g) Change directory to \WP6\WebSphere\PortalServer\updates
h) Run \WP6\WebSphere\AppServer\bin\setupCmdLine.bat
i) Run \WP6\WebSphere\PortalServer\updates\updatePortalWizard.bat
j) Choose "Install Fixpacks
k) Select WP_PTF_6001 from \WP6\WebSphere\PortalServer\updates\fixes as the source
l) Choose to install the fix pack - and wait
m) Assuming that installation is successful, shut down servers - ***OTHERWISE YOU CANNOT INSTALL THE REMAINING FIXES***
n) Re-run updatePortalWizard.bat and choose "Install fixes"
o) Select \WP6\WebSphere\PortalServer\updates\fixes as the source
p) Select PK31711.jar, PK35227.jar and PK35520.jar
q) Choose to install the fixes - and wait
r) Assuming that installation is successful, you're good to go :)
On completion of this process, \WP6\WebSphere\AppServer\bin\versionInfo.bat should return: -
IBM WebSphere Application Server - ND 6.0.2.9
IBM WebSphere Process Server 6.0.1.1
and \WP6\WebSphere\PortalServer\bin\WPVersionInfo.bat should return: -
IBM WebSphere Portal MultiPlatform 6.0.0.1
I've now done this three times; with success in each case :-)
Geeking in technology since 1985, with IBM Development, focused upon Docker and Kubernetes on the IBM Z LinuxONE platform In the words of Dr Cathy Ryan, "If you don't write it down, it never happened". To paraphrase one of my clients, "Every day is a school day". I do, I learn, I share. The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions. Remember, YMMV https://infosec.exchange/@davehay
Subscribe to:
Post Comments (Atom)
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="{...
-
Why oh why do I forget this ? Running this command : - ldapsearch -h ad2012.uk.ibm.com -p 389 -D CN=bpmbind,CN=Users,DC=uk,DC=ibm,DC=com -w...
-
Error "ldap_sasl_interactive_bind_s: Unknown authentication method (-6)" on a LDAPSearch command ...Whilst building my mega Connections / Domino / Portal / Quickr / Sametime / WCM environment recently, I was using the LDAPSearch command tha...
-
Whilst building a new "vanilla" Kubernetes 1.25.4 cluster, I'd started the kubelet service via: - systemctl start kubelet.se...
No comments:
Post a Comment