Readme for IBM® Spectrum Conductor with Spark 2.2.1 Interim Fix 509249

Readme file for: IBM Spectrum Conductor with Spark
Product/Component Release: 2.2.1
Update Name: Interim Fix 509249
Fix ID: cws-2.2.1-build509249
Publication date: January 29, 2019

This interim fix enables you to upgrade the IBM Java Runtime Environment (JRE) in IBM Spectrum Conductor with Spark 2.2.1 to JRE 8 SR5 FP25 in order to fix the following security vulnerabilities in IBM Java SDK: CVE-2018-3183, CVE-2018-3169, CVE-2018-3149, CVE-2018-3180, CVE-2018-3214, CVE-2018-13785, CVE-2018-3136, and CVE-2018-3139.

Contents

1.         List of fixes

2.         Download location

3.         Product notifications

4.         Installation and configuration

5.         Uninstallation

6.         List of files

7.         Copyright and trademark information

1.              List of fixes

APAR: P102842

2.              Download location

Download interim fix 509249 from the following location: http://www.ibm.com/eserver/support/fixes/

3.              Product notifications

To receive information about product solution and patch updates automatically, subscribe to product notifications on the My Notifications page http://www.ibm.com/support/mynotifications/ on the IBM Support website (http://support.ibm.com). You can edit your subscription settings to choose the types of information you want to get notification about, for example, security bulletins, fixes, troubleshooting, and product enhancements or documentation changes.

4.              Installation and configuration

Follow the instructions in this section to download and install this interim fix in your cluster.

System requirements

Linux x86_64

Installation

a.         Log in to the cluster management console as the cluster administrator and stop all Spark instance groups.

b.         Log on to the master host as the cluster administrator:

> egosh user logon -u Admin -x Admin

c.         Stop all services and shut down the cluster:

> egosh service stop all

> egosh ego shutdown all

d.         Log on to each host in your cluster (root or sudo-to-root permission).

e.         Define the CLUSTERADMIN environment variable and set it to any valid operating user account, which then owns all installation files, for example:

> export CLUSTERADMIN=egoadmin

f.          Upgrade the JRE by using the RPM in this interim fix (note that RPM version 4.2.1 or later must be installed on the host):

> mkdir -p /tmp/cws221build509249

> tar zxof cws-2.2.1.0_x86_64_build509249.tgz -C /tmp/cws221build509249

> rpm -ivh --replacefiles --prefix $EGO_TOP --dbpath dbpath_location /tmp/cws221build509249/egojre-8.0.5.25.x86_64.rpm

where $EGO_TOP specifies the path to where the cluster is installed and dbpath_location specifies the path to your database.

g.         In the $EGO_TOP/integration/elk/1.4/scripts/common.inc file, change JAVA_HOME to the location of the new JRE, for example:

JAVA_HOME=$EGO_TOP/jre/8.0.5.25/linux-x86_64

h.         Source the cluster profile again and start the cluster:

> egosh ego start all

The cshrc.jre and profile.jre files are updated to the current JRE version. If you made copies of these files, ensure that you update the copied files with the new JRE version.

i.           Log in to the cluster management console as the cluster administrator and start the required Spark instance groups.

j.           Run the rpm –qa command to verify the installation:

> rpm -qa --dbpath dbpath_location |grep egojre

egojre-8.0.5.25-509249.x86_64

5.              Uninstallation

If required, follow the instructions in this section to uninstall this interim fix in your cluster.

a.      Log in to the cluster management console as the cluster administrator and stop all Spark instance groups.

b.      Log on to the master host as the cluster administrator:

> egosh user logon -u Admin -x Admin

c.      Stop services and shut down the cluster:

> egosh service stop all

> egosh ego shutdown all

d.      Log on to each host in your cluster (root or sudo-to-root permission).

e.      Define the CLUSTERADMIN environment variable and set it to any valid operating user account, which then owns all installation files, for example:

> export CLUSTERADMIN=egoadmin

f.       Uninstall the existing JRE and install the old JRE (note that RPM version 4.2.1 or later must be installed on the host):

> rpm -e egojre-8.0.5.25-509249.x86_64 --dbpath dbpath_location --nodeps

where dbpath_location specifies the path to your database.

> rpm -qa --dbpath dbpath_location |grep egojre

For each previous egojre rpm, run:

> rpm -e egojre_name --dbpath dbpath_location --nodeps

Then, install the old JRE:

> mkdir -p /tmp/extract221

> cws-2.2.1.0_x86_64.bin --extract /tmp/extract221

> rpm -ivh --prefix $EGO_TOP --dbpath dbpath_location /tmp/extract221/egojre-*.rpm

where $EGO_TOP specifies the path to where the cluster is installed and dbpath_location specifies the path to your database.

g.      In the $EGO_TOP/integration/elk/1.4/scripts/common.inc file, change JAVA_HOME to the location of the previous JRE, for example:

JAVA_HOME=$EGO_TOP/jre/8.0.5.0/linux-x86_64

h.      Source the cluster profile again and start the cluster:

> egosh ego start all

i.        Log in to the cluster management console as the cluster administrator and start the required Spark instance groups.

6.              List of files

egojre-8.0.5.25.x86_64.rpm

7.              Copyright and trademark information

© Copyright IBM Corporation 2019

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM®, the IBM logo and ibm.com® are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml