Readme File for IBM^® Spectrum Conductor 2.4.1 Interim Fix 600948

Readme File for: IBM Spectrum Conductor

Product Release: 2.4.1

Update Name: Interim Fix 600948

Fix ID: sc-2.4.1-build600948

Publication Date: January 21, 2022

 

This interim fix upgrades the nodejs package to version 16.12.0.0, and the explorer package to version 10.1.1.0, for IBM Spectrum Conductor 2.4.1.

Contents

1. List of fixes

2. Download location

3. Product and components affected

4. Installation and configuration

5. Uninstallation

6. List of files

7. Product notifications

8. Copyright and trademark information

 

1.    List of fixes

APAR: P104527

2.    Download location

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

3.    Product and components affected

Component name, Platform, Fix ID:

 Explorer, nodejs, WEBGUI, Linux x86_64, Linux ppc64le, sc-2.4.1-build600948

4.   Installation and configuration

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

System requirements

·       Linux x86_64 or Linux ppc64le

·       RPM version 4.2.1 or later must be installed on each host in the cluster

Installation

a.     Log on to the primary host in the cluster as the cluster administrator and stop the Explorer and WEBGUI services:

> egosh user logon -u Admin -x Admin

> egosh service stop Explorer WEBGUI

b.   On each management host, create a directory (for example, /scfixes) and download the nodejs, explorer, and egomgmt packages to this directory:

nodejs-16.12.0.0_OS_type _build600948.rpm

explorer-10.1.1.0_OS_type_build600948.rpm

egomgmt-3.8.0.1_noarch_build600948.tar.gz

where OS_type is either x86_64 or ppc64le.  

c.         On each management host, uninstall the old explorer and nodejs packages:

 > rpm -e --dbpath dbpath_location explorer-10.1.0.5-537883.OS_type -–nodeps

 > rpm -e --dbpath dbpath_location nodejs-8.16.0.0-537883.OS_type -–nodeps

where dbpath_location specifies the path to your rpm database, and OS_type is either x86_64 or ppc64le.

d.         Install the new nodejs package on each management host:

> rpm -ivh --replacefiles --prefix $EGO_TOP --dbpath dbpath_location nodejs-16.12.0.0_OS_type_build600948.rpm

where $EGO_TOP specifies the path to where the cluster is installed, dbpath_location specifies the path to your database, and OS_type is either x86_64 or ppc64le.

e.       Set the NODEJS_VERSION to 16.12.0.0: 

·       For csh: set setenv NODEJS_VERSION 16.12.0.0 in the cshrc.nodejs file.

·       For bash: set NODEJS_VERSION=16.12.0.0 in the profile.nodejs file.

f.     Install the new explorer package on each management host:

> rpm -ivh –replacefiles --prefix $EGO_TOP --dbpath dbpath_location explorer-10.1.1.0_OS_type_build600948.rpm

where $EGO_TOP specifies the path to where the cluster is installed, dbpath_location specifies the path to your database, and OS_type is either x86_64 or ppc64le.

g.     Update the explorer_service.xml file:

    > cp $EGO_ESRVDIR/activation/10.1.1/esc/conf/services/explorer_service.xml $EGO_ESRVDIR/esc/conf/services/

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

> rpm -qa --dbpath dbpath_location |grep nodejs

> rpm -qa --dbpath dbpath_location |grep explorer

nodejs-16.12.0.0-600948.OS_type

explorer-10.1.1.0-600948.OS_type

where dbpath_location specifies the path to your database, and OS_type is either x86_64 or ppc64le.

i.   On each management host, run the egoinstallfixes command to install the egomgmt package:

> egoinstallfixes /scfixes/egomgmt-3.8.0.1_noarch_build600948.tar.gz

Important: Running the egoinstallfixes command automatically backs up the current binary files to a fix backup directory. For recovery purposes of the original file, do not delete this backup directory. For more information on using this command, see the egoinstallfixes command reference.

j.   Run the pversions command to verify the installation:

   > pversions -b 600948

k.   Delete all subdirectories and files from the following directories:

> rm -rf $EGO_TOP/gui/work/*

> rm -rf $EGO_TOP/gui/workarea/*

(Optional) rm -rf $WLP_OUTPUT_DIR/webgui_hostname/gui/workarea/*

l.     Clear your browser cache.    

m. From the primary host, restart EGO, and start the Explorer service if it’s not:

> egosh ego restart -f

> egosh service start Explorer

5.   Uninstallation

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

a.  Log on to the primary host in the cluster as the cluster administrator and stop the Explorer and WEBGUI services:

> egosh user logon -u Admin -x Admin

> egosh service stop Explorer WEBGUI

b.  Uninstall the existing nodejs and explorer packages:

> rpm -e nodejs-16.12.0.0-600948.OS_type --dbpath dbpath_location -–nodeps

> rpm -e explorer-10.1.1.0-600948.OS_type --dbpath dbpath_location -–nodeps

where OS_type is either x86_64 or ppc64le and dbpath_location specifies the path to your database.

c.  Install the previous nodejs and explorer packages:

> mkdir -p /tmp/extract241

> conductor2.4.1.0_os_type.bin --extract /tmp/extract241

> rpm -ivh --prefix $EGO_TOP --dbpath dbpath_location /tmp/extract241/nodejs-8.16.0.0.OS_type.rpm

> rpm -ivh --prefix $EGO_TOP --dbpath dbpath_location /tmp/extract241/explorer-10.1.0.5.OS_type.rpm

where OS_type is either x86_64 or ppc64le, $EGO_TOP specifies the path to where the cluster is installed, and dbpath_location specifies the path to your database.

d.  Roll back the NODEJS_VERSION value to the previous nodejs version in the following files: 

·       For csh: set setenv NODEJS_VERSION 8.16.0.0 in the cshrc.nodejs file.

·       For bash: set NODEJS_VERSION=8.16.0.0 in the profile.nodejs file.

e.  Roll back the explorer_service.xml file:

   > cp $EGO_ESRVDIR/activation/10.1/esc/conf/services/explorer_service.xml $EGO_ESRVDIR/esc/conf/services/

f.   On each management host, roll back this interim fix:

      > egoinstallfixes -r 600948

g.     Delete all subdirectories and files from the following directories:

> rm -rf $EGO_TOP/gui/work/*

> rm -rf $EGO_TOP/gui/workarea/*

(Optional) rm -rf $WLP_OUTPUT_DIR/webgui_hostname/gui/workarea/*

h.     Clear your browser cache.

i.      Source the cluster profile and restart EGO, start the Explorer service if it’s not:

> egosh ego restart -f

> egosh ego start Explorer

6.   List of files 

egomgmt-3.8.0.1_noarch_build600948.tar.gz
explorer-10.1.1.0_ppc64le_build600948.rpm
explorer-10.1.1.0_x86_64_build600948.rpm
nodejs-16.12.0.0_ppc64le_build600948.rpm
nodejs-16.12.0.0_x86_64_build600948.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 2022

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.