Readme for IBM® Spectrum Conductor 2.3.0 Interim Fix 504324

Readme file for: IBM Spectrum Conductor
Product/Component Release: 2.3.0
Update Name: Interim Fix 504324
Fix ID: sc-2.3-build504324
Publication date: November 5, 2018

Abstract

Security vulnerability exists in IBM Java SDK.

Description

This interim fix enables you to upgrade the IBM Java Runtime Environment (JRE) in IBM Spectrum Conductor 2.3.0 to fix the following security vulnerabilities in IBM Java SDK: CVE-2016-0705, CVE-2017-3732, CVE-2017-3736, CVE-2018-1517, CVE-2018-1656, CVE-2018-2940, CVE-2018-2952, CVE-2018-2964, CVE-2018-2973, CVE-2018-12539.

Contents:

1.       List of fixes

2.       Download location

3.       System requirements

4.       Packages

5.       Installation and configuration

6.       Uninstallation

7.       List of files

8.       Copyright and trademark information

1.            List of fixes

APAR: P102770

2.            Download location

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

3.            System requirements

Linux x86_64

4.            Packages

Platform

Package to download

Description

x86_64

conductor2.3.0.0_x86_64_build504324.tgz

JRE 8 SR5 FP22 package for IBM Spectrum Conductor 2.3.0

5.            Installation and configuration

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: RPM version 4.2.1 or later must be installed on the host.

For example, on Linux x86_64 hosts, enter:

> mkdir -p /tmp/sc230build504324

> tar zxof conductor2.3.0.0_x86_64_build504324.tgz -C /tmp/sc230build504324

> rpm -ivh --replacefiles --prefix $EGO_TOP --dbpath dbpath_location /tmp/sc230build504324/egojre-8.0.5.22.x86_64.rpm

where dbpath_location specifies the path to your database.

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

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

i.         Run the rpm –qa command to verify the installation. For example, on Linux x86_64 hosts, enter:

> rpm -qa --dbpath dbpath_location |grep egojre

egojre-8.0.5.22-504324.x86_64

6.            Uninstallation

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: RPM version 4.2.1 or later must be installed on the host. 

For example, on Linux x86_64 hosts, enter:

> rpm -e egojre-8.0.5.22-504324.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/extract230

> conductor2.3.0.0_x86_64.bin --extract /tmp/extract230

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

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

> egosh ego start all

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

7.            List of files

egojre-8.0.5.22.x86_64.rpm

8.            Copyright and trademark information

© Copyright IBM Corporation 2018

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