IBM Watson Explorer oneWEX, Version 12.0.1 HotFix 1 Readme

Content

IBM Watson Explorer oneWEX, Version 12.0.1 HotFix 1 includes the fixes for Watson Explorer Version 12.0.1 oneWEX. See Release Notes - IBM Watson Explorer oneWEX, Version 12.0 for the information about oneWEX Version 12.0.1. 

List of fixes

Version 12.0.1 HotFix 1 provides fixes for the following enhancements and problems:

• Respect collection language configuration in Realtime NLP API
• Configure multiple collection languages (REST API only)
• Deploying pear file from Content Analytics Studio to oneWEX fails.

Installing Version 12.0.1 HotFix 1 oneWEX for IBM Cloud Private (ICP)

To apply oneWEX Version 12.0.1 HotFix 1, you must install / upgrade to Watson Explorer oneWEX Version 12.0.1 first.

1. Download and unpack the HotFix 1 to the machine where oneWEX for ICP is deployed.

2. Execute the install script. 
./install.sh

The install script will create a new patched image that includes the fixes. An existing image ibm-wex-ee:12.0.1.237-linux-amd64 will be patched with the fix, then the new image is created and tagged as ibm-wex-ee:12.0.1.237-20180730-linux-amd64 . If the ICP image mycluster.icp:8500/default/ibm-wex-ee:12.0.1.237-linux-amd64 exists, the patched image will also be created and tagged as mycluster.icp:8500/default/ibm-wex-ee:12.0.1.237-20180730-linux-amd64 . 

3. Re-deploy the helm chart with the patched image with following steps.

i. 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. 

Notes: If you perform Step 5 in Uninstalling Watson Explorer oneWEX on IBM Cloud Private , all data to migrate will be deleted. 

ii. Specify the patched image in General.image.core in General section in the helm chart and re-deploy oneWEX. See Installing Watson Explorer oneWEX on IBM Cloud Private instructions for more information. 

4. Restart oneWEX and confirm the patched image is up and running. 

Installing Version 12.0.1 HotFix 1 oneWEX for single container deployment

To apply oneWEX Version 12.0.1 HotFix 1, you must install / upgrade to Watson Explorer oneWEX Version 12.0.1 first.

Note: The file location such as /root/ibm/wex or C:\IBM\wex varies depending on the environment.

1. Download and unpack the HotFix 1 to the machine where oneWEX for single container deployment is deployed.

2. Execute the install script. The install script will create a new patched image that includes the fixes. An existing image ibm-wex-ee:12.0.1.237 will be patched with the fix, then the new image is created and tagged as ibm-wex-ee:12.0.1.237-20180730 .

On Linux:
./install.sh
On Windows:
./install.ps1

Notes:

• 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:
  mycluster.icp:8500/default/ibm-wex-ee:12.0.1.237-linux-amd64 not found. skip patching ...
ibm-wex-ee:12.0.1.237-linux-amd64 not found, skip patching ...

3. Update  dockerImage property in wex.json file to point to the patched image. 

On Linux: /root/ibm/wex/config/wex.json
On Windows: C:\IBM\wex\config\wex.json
From: "dockerImage" : "ibm-wex-ee:12.0.1.237"
To: "dockerImage" : "ibm-wex-ee:12.0.1.237-20180730"

4. Restart oneWEX and confirm the patched image is up and running.

On Linux:
/root/ibm/wex/bin/wexdocker.sh
On Windows:
C:\IBM\wex\bin\wexdocker.bat

Configuring multiple collection languages

Configuring multiple collection languages with REST API is supported in this HotFix 1.

Note: The configuration cannot be changed in Watson Explorer Admin Console. Use the REST API.

1. Get a collection ID that you want to configure, either in Admin Console or with the REST API. For example, you can confirm the collection ID with following REST APIs.

https://ONEWEX_SERVER/admin/main/#/admin/collections/COLLECTION_ID

https://ONEWEX_SERVER/miner/main/COLLECTION_ID

2. Get the collection configuration with the REST API and save it as a file. For example, save the output to test_col.json file.

curl -v -k -u userId:password -H 'accept: application/json' "https://ONEWEX_SERVER/api/v1/collections/COLLECTION_ID" -o test_col.json 

3. Edit the language of the collection property in the saved json file. For example, specify English as "en" and Spanish as "es". See Language Identification section for the languages that you can use.

  {
  ...
   "enrichFieldGroups": [
      {
  ...
        "languages": [
          "en", "es"
        ]
      }

4. Update the collection configuration with the REST API using updated configuration json file.

curl -v -k -u userId:password -H 'Content-type: application/json' -X PUT "https://ONEWEX_SERVER/api/v1/collections/COLLECTION_ID" -d @test_col.json 

Notes: 

• The value in the example varies depending on the environment.
  • COLLECTION_ID is the collection id that you want to configure.
  • userId:password is the administrative user for oneWEX .
  • ONEWEX_SERVER is the server where oneWEX is deployed .