This time around I was attempting to create a new clustered WAS 7.0.0.13 environment with separate nodes running IHS and Plugin (7.0.0.13 as well). The installs ran fine until it came time to patch up the plugin to 7.0.0.13 / JDK SR8, at which point things went bad.
At first it looked like the patch names were wrong, so I reviewed the patches directory under the RAFW Media tree and made some adjustments to my install.properties files for each of the two IHS nodes I was attempting to install and patch the Plugin to. Then I ran the steps again, but came up with different errors. A few more tweaks and I managed to get the right values, but the project still failed on the Install Plugin Nodes steps!
In case anyone is struggling with the patch lines, here are the valid X_PATCHES values from the IHS Node's install.properties file:
# Patches to apply for each product.The error, once the patch lines were sorted out, was:
IHS_PATCHES=ihs70_fp13,ihs70_jdk_sr8
PLUGIN_PATCHES=plugin70_fp13,plugin70_jdk_sr8
D:\IBM\BuildForge\rafw\product\actions\install\ihs\common\install_update_ihs_common.xml:176: D:\IBM\BuildForge\rafw\media\linux\X64\ihs\70\patches\@PATCHNAME@ not found.This looked very odd to me, so I dug into the install_update_ihs_common.xml file and back-traced the call to the install_ihs70.xml file, where I found the offending @PATCHNAME@ in an ANT for loop ... what would we call it? A typo? I'm not sure how it got there.
(our BF/RAFW stack is on a Windows server)
Anyway, on to the fix. It was easy - just replace "@PATCHNAME@" with a properly formatted ANT variable (as was done in other places in the script): "@{PATCHNAME}".
ORIG: <param name="PATCH_NAME" value="@PATCHNAME@" />
FIXED: <param name="PATCH_NAME" value="@{PATCHNAME}" />
That's it... if it helps anyone, great!
-Kreebog
No comments:
Post a Comment