Readme for IBM® Spectrum Conductor 2.3.0 Interim Fix 519043
Readme file for: IBM Spectrum Conductor
Product/Component Release: 2.3.0
Update Name: Interim Fix 519043
Fix ID: sc-2.3-build519043
Publication date: May 10, 2019
This interim fix enables you to upgrade the IBM Java Runtime Environment
(JRE) in IBM Spectrum Conductor 2.3.0 to JRE
8 SR5 FP31 in order to fix the following security vulnerabilities in IBM Java
SDK: CVE-2019-2540,
CVE-2018-11212, CVE-2019-2426, CVE-2019-2449, CVE-2019-2422, CVE-2018-12547,
CVE-2018-12549, and CVE-2018-1890.
Contents
1.
List of fixes
2.
Download location
3.
Installation and configuration
4.
Uninstallation
5.
List of files
6.
Product notifications
7.
Copyright and trademark information
1.
List of fixes
N/A
2.
Download location
Download interim fix 519043 from the following location: http://www.ibm.com/eserver/support/fixes/
3.
Installation and configuration
Follow the instructions in this
section to download and install this interim fix in your cluster.
System requirements
Linux x86_64 or Linux
ppc64le
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/sc230build519043
> tar zxof conductor2.3.0.0_os_type_build519043.tgz -C /tmp/sc230build519043
> rpm -ivh --replacefiles --prefix $EGO_TOP --dbpath dbpath_location
/tmp/sc230build519043/egojre-8.0.5.31.os_type.rpm
where $EGO_TOP specifies the path to
where the cluster is installed, os_type is either x86_64 or pcc64le, and 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:
> rpm -qa --dbpath dbpath_location |grep egojre
egojre-8.0.5.31-519043.os_type
where os_type is either x86_64 or pcc64le.
4.
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.31-519043.os_type --dbpath dbpath_location --nodeps
where os_type is either x86_64 or pcc64le and 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_os_type.bin --extract /tmp/extract230
> rpm -ivh --prefix
$EGO_TOP --dbpath dbpath_location /tmp/extract230/egojre-*.rpm
where $EGO_TOP specifies the path to
where the cluster is installed, os_type is either x86_64 or pcc64le, and dbpath_location
specifies the path to your database.
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.
5.
List of files
egojre-8.0.5.31.x86_64.rpm
egojre-8.0.5.31.ppc64le.rpm
6.
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.
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