Readme file for IBM® Spectrum Conductor 2.3.0 Interim Fix 526418  

Readme file for: IBM Spectrum Conductor
Product/Component Release: 2.3.0
Fix ID: sc-2.3-build526418

Publication date: August 2, 2019

This interim fix enables you to upgrade the IBM WebSphere Liberty Profile (WLP) in IBM Spectrum Conductor 2.3.0 to fix security vulnerabilities.

Contents

1.      List of fixes

2.      Download location

3.      Products or components affected

4.      Installation and configuration

5.      Uninstallation

6.      List of files

7.      Product notifications

8.      Copyright and trademark information

1.    List of fixes

N/A

2.    Download location

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

3.    Products or components affected

Component Name, Platform, Fix ID:

wlp, Linux x86_64 or Linux ppc64le, sc-2.3-build526418

4.    Installation and configuration

Follow the instructions in this section to download and install 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 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 to any valid operating user account, which then owns all installation files, for example:

> export CLUSTERADMIN=egoadmin

f.          Upgrade the WLP by using the RPM in this interim fix.

Note: RPM version 4.2.1 or later must be installed on the host.

Ensure that you replace dbpath_location in the following rpm commands with the path to your database, for example:

> mkdir -p /tmp/sc230build526418

> tar zxof conductor-2.3.0.0_build526418.tgz -C /tmp/sc230build526418

> rpm -Uvh --prefix $EGO_TOP --dbpath dbpath_location /tmp/sc230build526418/egowlp-19.0.0.6.noarch.rpm

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

This step updates the wlp/cshrc.wlp and wlp/profile.wlp files to the current WLP version. If you made copies of these files, ensure that you update the copied files with the new WLP version.

g.         From the master host, 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.

i.           Run the rpm –qa command to verify the installation, for example:

> rpm -qa --dbpath dbpath_location |grep egowlp

egowlp-19.0.0.6-526418.noarch

5.    Uninstallation

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 to any valid operating user account, which then owns all installation files, for example:

> export CLUSTERADMIN=egoadmin

f.       Uninstall the existing WLP and then install the old WLP.

Note: RPM version 4.2.1 or later must be installed on the host. 

Ensure that you replace dbpath_location in the following rpm commands with the path to your database, for example:

> rpm -e egowlp-19.0.0.6-526418.noarch --dbpath dbpath_location --nodeps

> rpm -qa --dbpath dbpath_location |grep egowlp

Then, install the old WLP:

> mkdir -p /tmp/extract230

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

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

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

g.      From the master host, 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.

6.    List of files

egowlp-19.0.0.6.noarch.rpm

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

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