1. Rename the following directories (for example., _jvm.orig).
   • On AIX and Linux (including Linux on System z and PowerLinux BE):
     • $ES_INSTALL_ROOT/_jvm
       $ES_INSTALL_ROOT/_jvm64
   • On Windows:
     • %ES_INSTALL_ROOT%\_jvm
       %ES_INSTALL_ROOT%\_jvm64
2. Create empty directories, _jvm and _jvm64, at the same locations.
3. Copy the files that you extracted from the 32-bit (or 31-bit, if you use Linux on System z) and 64-bit JRE packages to the _jvm and _jvm64 directories, respectively.
4. On UNIX systems, enter the command "ls -la" to see whether the read/write/execute privileges and ownership settings for the new _jvm and _jvm64 files match the settings for the original directories. If they do not match, run the chown command to change the settings. In these examples, "esadmin" is the Content Analytics administrator ID and "staff" is the primary group assigned to the Content Analytics administrator ID:
   • chown -R esadmin:staff ES_INSTALL_DIR/_jvm
   • chown -R esadmin:staff ES_INSTALL_DIR/_jvm64
5. For a multiple server installation, run steps 3 - 7 on all servers.
6. Follow the steps below depending on your platform.
   • On AIX and Linux (including Linux on System z and PowerLinux BE):
     1. Stop all WEX processes on all servers.
     2. On all servers, log in as the Content Analytics administrator, open ES_INSTALL_ROOT/nodeinfo/esprofile file by using a text editor, and change the line as follows in one line:
        From:
        IBM_JAVA_OPTIONS="-Dcom.ibm.tools.attach.enable=no $IBM_JAVA_OPTIONS"
        To:
        IBM_JAVA_OPTIONS="-Dcom.ibm.tools.attach.enable=no  -XX:+HeapManagementMXBeanCompatibility $IBM_JAVA_OPTIONS"
   • On Windows:
     1. Stop all WEX processes including WEX Windows service.
     2. Open command prompt with "Run as Administrator" option and run the command "sc delete ICAService" to delete the WEX service.
     3. Confirm the WEX service has been deleted on Windows Service. If it still exists with "delete" mark, you might be still opening Services window.
     4. Open the %ES_INSTALL_ROOT%\bin\install_service.bat file by using a text editor and insert the following line in line 69 in one line:
        %UPDATE% ++Environment="IBM_JAVA_OPTIONS='-XX:+HeapManagementMXBeanCompatibility'"
     5. Run the install_service command to re-create WEX Windows service. For example, issue the command as follows:
        
        C:\PROGRA~1\IBM\es\bin\install_service.bat C:\PROGRA~1\IBM\es C:\PROGRA~1\IBM\es\esadmin ICAService "IBM Watson Explorer Content Analytics" .\esadmin PASSWORD
        Note: The actual arguments can be found in %ES_NODE_ROOT%\logs\install\<HOSTNAME>\v<VERSION>installLog.txt.
     6. Confirm a WEX service is visible and can be started on Windows Service.

Follow these steps after you download the required interim fix for your operating system from Fix Central.

You must have finished the procedure of "Updating IBM Java Runtime" above to proceed to this section.

1. Extract esctrl.jar file from the interim fix, and overwrite the old version of esctrl.jar with the fixed version in the $ES_INSTALL_ROOT/lib directory.
2. Extract cclclient.jar file from the interim fix, and overwrite the old version of cclclient.jar with the fixed version in the $ES_INSTALL_ROOT/lib directory.
3. Move or delete the $ES_INSTALL_ROOT/wlp directory. For example, move to $ES_INSTALL_ROOT/wlp.old directory.
4. Extract wlp-core-embeddable-version.zip file from the interim fix, and expand in the $ES_INSTALL_ROOT directory. The wlp directory is created. For example, unzip wlp-core-embeddable-XX.X.X.X.zip -d $ES_INSTALL_ROOT to extract to the $ES_INSTALL_ROOT directory.

5. Edit classpath entry in the $ES_INSTALL_ROOT/configurations/interfaces/indexservice__interface.ini file as follows:

   1. Find "wlp/dev/api/spec/com.ibm.websphere.javaee.servlet.3.0_1.0.*.jar" or "wlp/dev/api/spec/com.ibm.ws.javaee.servlet.3.0_1.0.*.jar" in the classpath and replace it with "wlp/dev/api/spec/com.ibm.websphere.javaee.servlet.3.0_1.0.41.jar".
      For example,

      From:
      classpath=es.indexservice.jar,antlr-2.7.2.jar,cloudscape/lib/derbyclient.jar,cloudscape/lib/derby.jar,an_icm.jar,es.dock.jar,oze_search.jar,wlp/dev/api/spec/com.ibm.websphere.javaee.servlet.3.0_1.0.22.jar,es.rdf.jar,pdfbox-2.0.3.jar,fontbox-2.0.3.jar,bcprov-jdk15-1.44.jar,/opt/ibm/sire/lib/noarch/json.org.jar

      To:
      classpath=es.indexservice.jar,antlr-2.7.2.jar,cloudscape/lib/derbyclient.jar,cloudscape/lib/derby.jar,an_icm.jar,es.dock.jar,oze_search.jar,wlp/dev/api/spec/com.ibm.websphere.javaee.servlet.3.0_1.0.41.jar,es.rdf.jar,pdfbox-2.0.3.jar,fontbox-2.0.3.jar,bcprov-jdk15-1.44.jar,/opt/ibm/sire/lib/noarch/json.org.jar

   2. Save the change.

6. Replace at most 5 JAR files.

   1. Rename or remove the following *.jar files to *.jar.bak in the $ES_INSTALL_ROOT/wlpapps/servers/admin/apps/ESAdmin.ear/ESAdmin.war/WEB-INF/lib directory. Some of these files might not exist.
      
      com.ibm.ws.crypto.passwordutil_1.0.*.jar
com.ibm.ws.kernel.service_1.3.*.jar
com.ibm.ws.logging_1.0.*.jar
com.ibm.ws.kernel.boot_1.0.*.jar
com.ibm.ws.security.common_1.0.*.jar

   2. Copy the following *.jar files into the $ES_INSTALL_ROOT/wlpapps/servers/admin/apps/ESAdmin.ear/ESAdmin.war/WEB-INF/lib directory from the $ES_INSTALL_ROOT/wlp/lib directory:
      
      com.ibm.ws.crypto.passwordutil_1.0.41.jar
com.ibm.ws.kernel.service_1.3.41.jar
com.ibm.ws.logging_1.0.41.jar
com.ibm.ws.kernel.boot_1.0.41.jar
com.ibm.ws.security.common_1.0.41.jar

   3. Rename or remove the following es.security.jar to es.security.jar.bak:
      
      $ES_INSTALL_ROOT/lib/es.security.jar
$ES_INSTALL_ROOT/wlpapps/servers/admin/apps/ESAdmin.ear/ESAdmin.war/WEB-INF/lib/es.security.jar
$ES_INSTALL_ROOT/wlpapps/servers/admin/apps/ESAdminRestServer.ear/ESAdminRestServer.war/WEB-INF/lib/es.security.jar
$ES_INSTALL_ROOT/wlpapps/servers/admin/apps/ESAdminRestServer20.ear/ESAdminRestServer20.war/WEB-INF/lib/es.security.jar
$ES_INSTALL_ROOT/wlpapps/servers/searchapp/apps/ESRestServer.ear/ESRestServer.war/WEB-INF/lib/es.security.jar
$ES_INSTALL_ROOT/wlpapps/servers/searchapp/apps/analytics.ear/analytics.war/WEB-INF/lib/es.security.jar
$ES_INSTALL_ROOT/wlpapps/servers/searchapp/apps/commonui.ear/commonui.war/WEB-INF/lib/es.security.jar
$ES_INSTALL_ROOT/wlpapps/servers/searchapp/apps/search.ear/search.war/WEB-INF/lib/es.security.jar

   4. Extract es.security.jar file from the interim fix, and copy it into all of the above directories

Notes:

• This operation is applicable for the master server (where admin session is running) and search server (where searchapp.nodeN session is running). Repeat the steps if Analytical Components is installed on distributed servers.

Start the service

1. On the master server, enter the command "esadmin system startall" to start the Watson Explorer Content Analytics system and CCL.