Fix Readme
Abstract
Follow the procedures in this document to update the version of IBM Runtime Environment Java Technology Edition that is provided with IBM Watson Explorer oneWEX.
Content
Update IBM Java Runtime in oneWEX for single container deployment:
Note: In order to updating IBM Java Runtime, you must install / upgrade to the base version of Watson Explorer oneWEX first. For example, you need to install / upgrade to version 12.0.3.5 first to attach IBM Java Runtime update for version 12.0.3.5.
- Download the required version of IBM Java Runtime and patch file to the machine where oneWEX for single container deployment is deployed.
- Unpack the patch file.
- Copy the downloaded IBM Java Runtime archive file to the directory where the patch is unpacked. As shown in the example:
cp ibm-java-jre-8.0-6.25-linux-x86_64.tgz <path-to-patch>/ibm-wex-fix-12.0.3.5-java-8.0.6.25/patches-linux-amd64/
- Go to the patch directory and execute the install script. The install script will create a new patched image that includes the fixes.
As shown in the example:
An existing image ibm-wex-ee:12.0.3.2268 will be patched with the fix, then the new image is created and tagged asibm-wex-ee:12.0.3.2268-java-8.0.6.25.- On Linux:
cd <path-to-patch>/ibm-wex-fix-12.0.3.5-java-8.0.6.25
./install.sh - On Windows:
cd <path-to-patch>\ibm-wex-fix-12.0.3.5-java-8.0.6.25
./install.ps1 - On Windows, use PowerShell to run the install script. In case of disabled script execution policy, use Set-ExecutionPolicy -ExecutionPolicy RemoteSigned to enable. See Execution-Policy for more information.
- You can ignore the following message on the screen, as an example:
Docker image mycluster.icp:8500/default/ibm-wex-ee:12.0.3.2268-linux-amd64 not found. skip patching
Docker image ibm-wex-ee:12.0.3.2268-linux-amd64 not found, skip patching
Docker image ibm-wex-hdp:12.0.3.2268-linux-amd64 not found, skip patching
Docker image ibm-wex-hdp:12.0.3.2268 not found, skip patching
Docker image mycluster.icp:8500/wex/ibm-wex-hdp:12.0.3.2268-linux-amd64 not found, skip patching
Docker image ibm-wex-wksml:12.0.3.2268-linux-amd64 not found, skip patching
Docker image mycluster.icp:8500/wex/ibm-wex-wksml:12.0.3.2268-linux-amd64 not found, skip patching
- On Linux:
- Update dockerImage property in wex.json file to point to the patched image created in step 4. The new image tag should be in format like
<onewex-base-version-tag>-java-<java-version>. As shown in the example:
From:
To:"dockerImage" : "ibm-wex-ee:12.0.3.2268", "wksmlImage" : "ibm-wex-wksml:12.0.3.2268","dockerImage" : "ibm-wex-ee:12.0.3.2268-java-8.0.6.25", "wksmlImage" : "ibm-wex-wksml:12.0.3.2268-java-8.0.6.25",Note: The file location such as /root/ibm/wex or C:\IBM\wex varies depending on the environment.- On Linux: /root/ibm/wex/config/wex.json
- On Windows: C:\IBM\wex\config\wex.json
- Restart oneWEX and confirm the patched image is up and running.
Note: The file location such as /root/ibm/wex or C:\IBM\wex varies depending on the environment.- On Linux:
/root/ibm/wex/bin/wexdocker.sh restart - On Windows:
C:\IBM\wex\bin\wexdocker.bat restart
- On Linux:
Update IBM Java Runtime in oneWEX for IBM Cloud Private (ICP) and oneWEX for IBM Cloud Private (ICP) with OpenShift:
Note: In order to updating IBM Java Runtime, you must install / upgrade to the base version of Watson Explorer oneWEX first. For example, you need to install / upgrade to version 12.0.3.5 before attach IBM Java Runtime update for version 12.0.3.5.
- Download the required version of IBM Java Runtime and patch file to the machine where oneWEX for ICP is deployed.
- Unpack the patch file.
- Copy the downloaded IBM Java Runtime archive file to the directory where the patch is unpacked. As shown in the example:
cp ibm-java-jre-8.0-6.25-linux-x86_64.tgz <path-to-patch>/ibm-wex-fix-12.0.3.5-java-8.0.6.25/patches-linux-amd64/
- Check if local file system has all docker images ibm-wex-ee, ibm-wex-wksml, ibm-wex-hdp of oneWEX base version. If not, pull images from your private image registry to your local file system. See Pushing and pulling images instructions for more information.
- Go to the patch directory. As shown in the example:
cd <path-to-patch>/ibm-wex-fix-12.0.3.5-java-8.0.6.25
- Edit the ./install.sh to match your private image registry and the namespace for oneWEX.
Default namespace iswexand the default private image registry is mycluster.icp:8500.- Edit the line WEX_LOADED_NAMESPACE=wex to match the namespace you created for oneWEX deployment.
- Edit the line ICP_REGISTRY=mycluster.icp:8500 to match the private image registry.
For example, set ICP_REGISTRY=docker-registry.default.svc:5000 for ICP with OpenShift.
- Execute the install script.
- ./install.sh
The install script will create a new patched image that includes the Java runtime update. For example:
An existing image ibm-wex-ee:12.0.3.2268-linux-amd64 will be patched with the fix, then the new image is created and tagged asibm-wex-ee:12.0.3.2268-java-8.0.6.25-linux-amd64. If the ICP image mycluster.icp:8500/default/ibm-wex-ee:12.0.3.2268-linux-amd64 exists, the patched image will also be created and tagged asmycluster.icp:8500/default/ibm-wex-ee:12.0.3.2268-java-8.0.6.25-linux-amd64and pushed to your private image registry.
- ./install.sh
- Re-deploy the helm chart with the patched image with following steps.
- Delete the current oneWEX deployment in the release. See Step 1 to Step 4 in Uninstalling Watson Explorer oneWEX on IBM Cloud Private instructions for more information. If you perform Step 5 in Uninstalling Watson Explorer oneWEX on IBM Cloud Private , all data to migrate will be deleted.
- In order to migrate data from oneWEX deployment deleted above, create Persistent Volumes that use the extracted directories of the deleted deployment.
- Specify the patched image in Core Image, HDP Image and WKSML image parameters in General section in the helm chart and re-deploy oneWEX.See Installing Watson Explorer oneWEX on IBM Cloud Private and Installing Watson Explorer oneWEX on IBM Cloud Private with OpenShift instructions for more information.
- Restart oneWEX and confirm the patched image is up and running.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS8NLW","label":"IBM Watson Explorer"},"ARM Category":[{"code":"a8m0z000000cvvoAAA","label":"Documentation"}],"Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"12.0.3"}]
Was this topic helpful?
Document Information
Modified date:
25 March 2022
UID
ibm16441277