Friday 24 February 2017

IBM Installation Manager - Tinkering with iFixes

I've posted about this in the past: -



This is merely an update, as my memory is fading ….

So I have some iFixes for IBM BPM 8.5.7: -

ls -al /mnt/BPM/Fixes/

total 119883
drwxr-xr-x 1 501 games      170 Feb 24 19:39 .
drwxr-xr-x 1 501 games      170 Feb 24 19:39 ..
-rw-r--r-- 1 501 games 24474208 Feb 24 19:39 8.5.7.201609-WS-BPM-IFJR56722.zip
-rw-r--r-- 1 501 games   232160 Feb 24 19:39 8.5.7.201609-WS-BPM-IFJR56860.zip
-rw-r--r-- 1 501 games 98051787 Feb 24 19:39 8.5.7.201609-WS-BPMPCPD-IFJR56884.zip


and I want to install them.

Well, here's how ….

for i in /mnt/BPM/Fixes/*.zip; do /opt/ibm/InstallationManager/eclipse/tools/imcl listAvailableFixes com.ibm.bpm.ADV.v85_8.5.700201609 -repositories $i; done

8.5.7.201609-WS-BPM-IFJR56722_8.5.700201609.20161028_0129
8.5.7.201609-WS-BPM-IFJR56860_8.5.700201609.20161101_2257
8.5.7.201609-WS-BPMPCPD-IFJR56884_8.5.700201609.20161130_1425


Add this to seeing what binaries we have: -

/opt/ibm/InstallationManager/eclipse/tools/imcl listAvailablePackages -repositories /mnt/BPM/Product/repository/repos_64bit/,/mnt/WAS/Product/Supp/,/mnt/WAS/Fixes/Base,/mnt/WAS/Fixes/Supp/,/mnt/BPM/Fixpack

com.ibm.bpm.ADV.v85_8.5.7000.20160301_1551
com.ibm.websphere.IBMJAVA.v70_7.0.9010.20151112_0100
com.ibm.websphere.ND.v85_8.5.5008.20151112_0939
com.ibm.ws.DB2EXP.linuxia64_10.5.0.20160301_1400
com.ibm.websphere.APPCLIENT.v85_8.5.0.20120501_1108
com.ibm.websphere.IHS.v85_8.5.0.20120501_1108
com.ibm.websphere.PLG.v85_8.5.0.20120501_1108
com.ibm.websphere.PLUGCLIENT.v85_8.5.0.20120501_1108
com.ibm.websphere.WCT.v85_8.5.0.20120501_1108
com.ibm.websphere.BASE.v85_8.5.5011.20161206_1434
com.ibm.websphere.BASETRIAL.v85_8.5.5011.20161206_1434
com.ibm.websphere.DEVELOPERS.v85_8.5.5011.20161206_1434
com.ibm.websphere.DEVELOPERSILAN.v85_8.5.5011.20161206_1434
com.ibm.websphere.EXPRESS.v85_8.5.5011.20161206_1434
com.ibm.websphere.EXPRESSTRIAL.v85_8.5.5011.20161206_1434
com.ibm.websphere.ND.v85_8.5.5011.20161206_1434
com.ibm.websphere.NDDMZ.v85_8.5.5011.20161206_1434
com.ibm.websphere.NDDMZTRIAL.v85_8.5.5011.20161206_1434
com.ibm.websphere.NDTRIAL.v85_8.5.5011.20161206_1434
com.ibm.websphere.APPCLIENT.v85_8.5.5011.20161206_1434
com.ibm.websphere.APPCLIENTILAN.v85_8.5.5011.20161206_1434
com.ibm.websphere.IHS.v85_8.5.5011.20161206_1434
com.ibm.websphere.IHSILAN.v85_8.5.5011.20161206_1434
com.ibm.websphere.PLG.v85_8.5.5011.20161206_1434
com.ibm.websphere.PLGILAN.v85_8.5.5011.20161206_1434
com.ibm.websphere.PLUGCLIENT.v85_8.5.5011.20161206_1434
com.ibm.websphere.PLUGCLIENTILAN.v85_8.5.5011.20161206_1434
com.ibm.bpm.ADV.v85_8.5.700201612.20161214_1824
com.ibm.bpm.EXP.v85_8.5.700201612.20161214_1824
com.ibm.bpm.PS.v85_8.5.700201612.20161214_1824
com.ibm.bpm.STD.v85_8.5.700201612.20161214_1824


and we're good to go :-)

For the record, I used IBM Fix Central to provide a listing of the available fixes for BPM 8.5.7, to take me from the September 2016 Cumulative Fix: -



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="{...