Readme File for IBM® Spectrum Conductor 2.5.1 Fix 601861
Readme File for: IBM Spectrum Conductor
Product Release: 2.5.1
Update Name: IBM Spectrum Conductor 2.5.1 Fix 601861
Fix ID: sc-2.5.1-build601861
Publication Date: January 26, 2023
The
IBM Spectrum Conductor 2.5.1 Fix 601861 offering is available for 64-bit Linux
x86 and Linux on POWER. It is a security fix for IBM Spectrum Conductor, to be
applied on top of your version 2.5.1 Fix 601712 installation (including any fixes you may have already installed on top of version
2.5.1).
Fix 60861 is
not a mandatory fix; you can apply other fixes on top of IBM Spectrum Conductor
2.5.1 Fix 601712 without applying Fix 601861. Fix 601861 is, however, one that
provides optimal security.
The IBM Spectrum Conductor
installation includes various software, as listed in IBM Documentation. Some of the software packages have been identified with
common vulnerabilities exposures (CVEs). Fix 601861 provides upgraded versions
of the affected software, so that you can continue to use IBM Spectrum
Conductor 2.5.1 security. For improved security, apply Fix 601861.For a Linux environment with IBM Spectrum Symphony, always install IBM
Spectrum Symphony 7.3.2 Fix 601860 first, and then install IBM Spectrum
Conductor 2.5.1 Fix 601861.
For what’s included in Fix 601861, see the
following list of fixes in this readme file, and the release notes within IBM
Documentation for details.
Contents
1. List of fixes
2. Download location
3. Product and components affected
4. Installation and configuration
5. Uninstallation
6. List of files
7. Copyright and trademark information
1. List of fixes
Fix 601861 provides upgraded software packages to address known CVEs. The following list provides the software versions upgrade with Fix 601861:
· bcprov-jdk15on to 1.77
·
jquery-ui to 1.13.2
·
jquery.dataTables.min.js and jquery.dataTables.js to 1.11.3
· kotlin-stdlib to 1.9.20
·
libbind to 9.18.19
·
logback core to 1.2.13
·
netty-handler to 4.1.99
·
okio to 3.4.0
·
spring-security to 5.8.8
·
urllib3 to 1.26.18
For more details, see the Fix 601861 release
notes within IBM Documentation.
2. Download location
Download IBM Spectrum Conductor 2.5.1 Fix 601861 from IBM Fix Central: https://www.ibm.com/eserver/support/fixes/
3. Product and components affected
Component name, Platform, Fix ID:
IBM Spectrum Conductor, Linux x86_64, Linux on POWER 64-bit, sc-2.5.1-build601861
4. Installation and configuration
Follow the instructions in this
section to download and apply IBM Spectrum Conductor 2.5.1 Fix 601861.
Fix 601861 for IBM Spectrum Conductor is offered as a fix on top of your existing version of 2.5.1 Fix 601712. For an environment with IBM Spectrum
Symphony, always install IBM Spectrum Symphony 7.3.2 Fix 601860 first,
and then install IBM Spectrum Conductor 2.5.1 Fix 601861.
System requirements
Depending on your operating system, you require Linux x86 64-bit, or
Linux on POWER 64-bit. For details, see all supported
system configurations.
Before
installation
Download the installation package for your operating system, to a directory on each of your management and compute hosts (for example, to a /cws251 directory on Linux):
·
For Linux x86:
cws-2.5.1.0_x86_64_build601861.tar.gz
·
For Linux on POWER 64-bit:
cws-2.5.1.0_ppc64le_build601861.tar.gz
Note
that you will install using the egoinstallfixes command,
which requires that your Linux host include the ed Linux line-oriented
text editor.
Installation steps
Use the following
installation steps for the installation package applicable to your operating
system (Linux x86_84 or Linux on POWER).
Before
installing
Before applying the IBM Spectrum
Conductor 2.5.1 Fix 601861, take note of these items:
· Ensure that you have IBM Spectrum Conductor 2.5.1 installed for your operating
system.
· If any files
under the $EGO_TOP directory is not owned by the cluster
administrator, then run the egoinstallfixes command as root;
otherwise, file ownership cannot be set.
· Follow the installation steps for your environment:
o For a single product with only IBM Spectrum Conductor 2.5.1 installed, follow Installing Fix 601861 on an environment with only IBM Spectrum Conductor 2.5.1 installed.
o
For a multiple product
environment with both IBM Spectrum Conductor 2.5.1 and IBM Spectrum Symphony
7.3.2 installed, follow Installing Fix 601861 on an environment with IBM
Spectrum Symphony 7.3.2 with Fix 601860 and IBM Spectrum Conductor 2.5.1
installed.
Installing
Fix 601861 on an environment with only IBM Spectrum Conductor 2.5.1 installed
a.
Complete these steps on your primary host:
i.
Log on as the operating system
cluster administrator, and source the environment:
(BASH) . $EGO_TOP/profile.platform
(CSH) source $EGO_TOP/cshrc.platform
ii. Stop the cluster:
$ egosh user logon -u Admin -x Admin
$ egosh service stop all
$ egosh ego shutdown all
Tip: Ensure that there are no remaining IBM Spectrum Conductor processes running on the host, as they can affect the Fix 601861 installation or cluster startup after the installation. To check for processes, run ps -ef | grep $EGO_TOP and kill any remaining processes.
b. Complete these steps for each management host in the cluster:
i. Log on as the operating system cluster administrator and source your environment:
(BASH) . $EGO_TOP/profile.platform
(CSH) source $EGO_TOP/cshrc.platform
ii. Extract the .tar.gz file that you previously downloaded:
· For Linux x86: cws-2.5.1.0_x86_64_build601861.tar.gz
· For Linux on POWER 64-bit: cws-2.5.1.0_ppc64le_build601861.tar.gz
For example, use either of these tar commands:
· tar zxof cws-2.5.1.0_x86_64_build601861.tar.gz -C /cws251
· tar zxof cws-2.5.1.0_ppc64le_build601861.tar.gz -C /cws251
iii.
Change to the
directory where you extracted the downloaded file, and then install Fix 601861
by running the cws-2.5.1.sh script. For example:
$ cd /cws251
$ ./cws-2.5.1.sh -m -i
The installer installs all necessary packages for your management host, including:
o
egocore-4.0.0.0_{arch_type}_build601861.tar.gz
o
egomgmt-4.0.0.0_noarch_build601861.tar.gz
o
egorest-4.0.0.0_noarch_build601861.tar.gz
o
explorer-10.1.1.0_{arch_type}_build601861.tar.gz
o
ascd-2.5.1.0_noarch_build601861.tar.gz
o
conductorsparkcore-2.5.1.0_{arch_type}_build601861.tar.gz
o
conductorsparkmgmt-2.5.1.0_noarch_build601861.tar.gz
o
hfcore-1.2.0.0_{arch_type}_build601861.tar.gz
where
{arch_type} is x86_64 or ppc64le.
iv.
Verify the
installation using the pversions command:
For example:
$ pversions -b 601861
c. Complete these steps for each compute host in the cluster:
i. Log on as the operating system cluster administrator and source your environment:
(BASH) . $EGO_TOP/profile.platform
(CSH) source $EGO_TOP/cshrc.platform
ii. Extract the .tar.gz file that you previously downloaded:
· For Linux x86: cws-2.5.1.0_x86_64_build601861.tar.gz
· For Linux on POWER 64-bit: cws-2.5.1.0_ppc64le_build601861.tar.gz
For example, use either of these tar commands:
· tar zxof cws-2.5.1.0_x86_64_build601861.tar.gz -C /cws251
· tar zxof cws-2.5.1.0_ppc64le_build601861.tar.gz
-C /cws251
iii.
Change to the
directory where you extracted the downloaded file, and then install Fix 601861
by running the cws-2.5.1.sh script. For example:
$ cd /cws251
$ ./cws-2.5.1.sh -c -i
The
installer installs all necessary packages for your compute host, including:
o
egocore-4.0.0.0_{arch_type}_build601861.tar.gz
o
conductorsparkcore-2.5.1.0_{arch_type}_build601861.tar.gz
where
{arch_type} is x86_64 or ppc64le.
iv.
Verify the
installation using the pversions command:
For example:
$ pversions -b 601861
d.
On each
management host, delete all subdirectories and files from the following directories:
$ rm -rf $EGO_CONFDIR/../../gui/work/*
$ rm -rf $EGO_TOP/gui/workarea/*
$ rm -rf $EGO_TOP/kernel/rest/workarea/*
Note: If you configured the WLP_OUTPUT_DIR parameter and APPEND_HOSTNAME_TO_WLP_OUTPUT_DIR is set to true in the $EGO_CONFDIR/wlp.conf file, you must clean up the $WLP_OUTPUT_DIR/webgui_hostname/gui/workarea/ directory.
e.
(Optional) On
your management host, if you want to use EGO service ServiceDirector and
WebServiceGateway, configure environment variables LD_LIBRARY_PATH in $EGO_CONFDIR/../../eservice/esc/conf/services/named.xml:
Linux x86 64-bit:
<ego:EnvironmentVariable
name="LD_LIBRARY_PATH">${EGO_TOP}/4.0/linux-x86_64/lib/libbind</ego:EnvironmentVariable>
Linux on
POWER:
<ego:EnvironmentVariable
name="LD_LIBRARY_PATH">${EGO_TOP}/4.0/linux3.10-glibc2.17-ppc64le/lib/libbind</ego:EnvironmentVariable>
f. Start the cluster by logging on as root or a cluster administrator user with root privileges, sourcing your environment, and restarting the cluster:
(BASH)
. $EGO_TOP/profile.platform
(CSH)
source $EGO_TOP/cshrc.platform
$ egosh
ego start all
Tip: After installing
Fix 601861 and it works well in your environment, to avoid the original files
from being scanned by security management related tools, you can move the
original files out of the cluster. Move the backup files (under the $EGO_TOP/patch/backup/ directory) to other
hosts that do not have IBM Spectrum Conductor installed.
Installing
Fix 601861 on an environment with IBM Spectrum Symphony 7.3.2 with Fix 601860 and
IBM Spectrum Conductor 2.5.1 installed
a.
Complete these steps on your primary host:
i.
Log on as the
operating system cluster administrator, and source the environment:
(BASH) .
$EGO_TOP/profile.platform
(CSH) source
$EGO_TOP/cshrc.platform
ii. Stop the cluster:
$ egosh user logon -u Admin -x Admin
$ egosh service stop all
$ egosh ego shutdown all
Tip: Ensure that there are no remaining IBM Spectrum Conductor processes running on the host, as they can affect the Fix 601861 installation or cluster startup after the installation. To check for processes, run ps -ef | grep $EGO_TOP and kill any remaining processes.
b. Complete these steps for each management host in the cluster:
i.
Log on as the operating system cluster administrator and
source your environment:
(BASH) . $EGO_TOP/profile.platform
(CSH) source
$EGO_TOP/cshrc.platform
ii.
Extract the .tar.gz file that you previously downloaded:
·
For Linux x86: cws-2.5.1.0_x86_64_build601861.tar.gz
For example,
use either of these tar commands:
· tar zxof cws-2.5.1.0_x86_64_build601861.tar.gz
-C /cws251
iii. Change to the directory where you extracted the downloaded file, and then install Fix 601861 by running the cws-2.5.1.sh script. For example:
$ cd /cws251
$ ./cws-2.5.1.sh -m -i
The installer installs all necessary packages.
iv.
Verify the installation using the pversions command. For example:
$ pversions -b 601861
c. Complete these steps for each compute host in the cluster:
i.
Log on as the operating system cluster administrator and
source your environment:
(BASH) .
$EGO_TOP/profile.platform
(CSH) source
$EGO_TOP/cshrc.platform
ii.
Extract the .tar.gz file that you previously downloaded:
·
For Linux x86: cws-2.5.1.0_x86_64_build601861.tar.gz
For example,
use either of these tar commands:
$ tar zxof cws-2.5.1.0_x86_64_build601861.tar.gz
-C /cws251
The installer installs all necessary packages.
iii.
Change to the
directory where you extracted the downloaded file, and then install Fix 601861
by running the cws-2.5.1.sh script. For example:
$ cd /cws251
$ ./cws-2.5.1.sh -c -i
iv. Verify the installation
using the pversions command:
For example:
$ pversions -b 601861
d.
On each
management host, delete all subdirectories and files from the following directories:
$ rm -rf $EGO_CONFDIR/../../gui/work/*
$ rm -rf $EGO_TOP/gui/workarea/*
$ rm -rf $EGO_TOP/kernel/rest/workarea/*
Note: If you configured the WLP_OUTPUT_DIR parameter and APPEND_HOSTNAME_TO_WLP_OUTPUT_DIR is set to true in the $EGO_CONFDIR/wlp.conf file, you must clean up the $WLP_OUTPUT_DIR/webgui_hostname/gui/workarea/ directory.
e. (Optional) On your management host, if you want to use
EGO service ServiceDirector and WebServiceGateway, configure environment
variables LD_LIBRARY_PATH in $EGO_CONFDIR/../../eservice/esc/conf/services/named.xml:
<ego:EnvironmentVariable
name="LD_LIBRARY_PATH">${EGO_TOP}/4.0/linux-x86_64/lib/libbind</ego:EnvironmentVariable>
Linux on
POWER:
<ego:EnvironmentVariable
name="LD_LIBRARY_PATH">${EGO_TOP}/4.0/linux3.10-glibc2.17-ppc64le/lib/libbind</ego:EnvironmentVariable>
f. Start the cluster on the primary host by logging on as root or a cluster administrator user with root privileges, sourcing your environment, and restarting the cluster:
(BASH)
. $EGO_TOP/profile.platform
(CSH)
source $EGO_TOP/cshrc.platform
$ egosh
ego start all
Tip: After
installing Fix 601861 and it works well in your environment, to avoid the
original files from being scanned by security management related tools, you can
move the original files out of the cluster. Move the backup files (under the $EGO_TOP/patch/backup/ directory) to other hosts that do not have IBM
Spectrum Conductor installed.
5. Uninstalling
If required, follow the instructions in this section
to uninstall Fix 601861 from your cluster.
Important:
·
For
an environment with IBM Spectrum Symphony, always uninstall IBM Spectrum
Conductor 2.5.1 Fix 601861 first, and then uninstall IBM Spectrum Symphony
7.3.2 Fix 601860.
a. Log on as the operating system cluster administrator, and source the
environment:
(BASH) . $EGO_TOP/profile.platform
(CSH) source
$EGO_TOP/cshrc.platform
b. Log on to the primary host as the operating system cluster
administrator, and stop the cluster:
$ egosh user logon -u Admin
-x Admin
$ egosh service stop all
$ egosh ego shutdown all
c. Log on to each Linux management and compute host in the
cluster and roll back this fix:
For
an environment with only IBM Spectrum Conductor 2.5.1 installed
·
Roll back the
fix in each management host:
$
cws-2.5.1.sh -m -r
·
Roll back the
fix in each compute host:
$ cws-2.5.1.sh -c -r
The commands roll back the packages previously installed
for Fix 601861.
For
an environment with IBM Spectrum Symphony 7.3.2 with Fix 601860 and IBM
Spectrum Conductor 2.5.1 installed
·
Roll back the
fix in each management host:
$ cws-2.5.1.sh
-m -r
·
Roll back the
fix in each compute host:
$ cws-2.5.1.sh -c -r
The command rolls back the packages previously installed for IBM Spectrum Conductor Fix 601861.
d.
On each
management host, delete all subdirectories and files from the following directories:
$ rm -rf $EGO_CONFDIR/../../gui/work/*
$ rm -rf $EGO_TOP/gui/workarea/*
$ rm -rf $EGO_TOP/kernel/rest/workarea/*
Note: If you configured the WLP_OUTPUT_DIR parameter and APPEND_HOSTNAME_TO_WLP_OUTPUT_DIR is set to true in the $EGO_CONFDIR/wlp.conf file, you must clean up the $WLP_OUTPUT_DIR/webgui_hostname/gui/workarea/ directory.
e.
(Optional) On
your management host, if you want to use EGO service ServiceDirector and
WebServiceGateway in the cluster, remove environment variables LD_LIBRARY_PATH from $EGO_CONFDIR/../../eservice/esc/conf/services/named.xml:
Linux x86 64-bit:
<ego:EnvironmentVariable
name="LD_LIBRARY_PATH">${EGO_TOP}/4.0/linux-x86_64/lib/libbind</ego:EnvironmentVariable>
Linux on
POWER:
<ego:EnvironmentVariable
name="LD_LIBRARY_PATH">${EGO_TOP}/4.0/linux3.10-glibc2.17-ppc64le/lib/libbind</ego:EnvironmentVariable>
f.
Start the cluster
on your primary host by logging on as root or a
cluster administrator user with root privileges, sourcing your environment, and restarting the
cluster:
(BASH)
. $EGO_TOP/profile.platform
(CSH)
source $EGO_TOP/cshrc.platform
$ egosh
ego start all
6. List of files
cws-2.5.1.0_x86_64_build601861.tar.gz
- ascd-2.5.1.0_noarch_build601861.tar.gz
- conductorsparkcore-2.5.1.0_x86_64_build601861.tar.gz
- conductorsparkmgmt-2.5.1.0_noarch_build601861.tar.gz
- egocore-4.0.0.0_x86_64_build601861.tar.gz
- egomgmt-4.0.0.0_noarch_build601861.tar.gz
- egorest-4.0.0.0_noarch_build601861.tar.gz
- explorer-10.1.1.0_x86_64_build601861.tar.gz
- hfcore-1.2.0.0_x86_64_build601861.tar.gz
- cws-2.5.1.sh
cws-2.5.1.0_ppc64le_build601861.tar.gz
- ascd-2.5.1.0_noarch_build601861.tar.gz
- conductorsparkcore-2.5.1.0_ppc64le_build601861.tar.gz
- conductorsparkmgmt-2.5.1.0_noarch_build601861.tar.gz
- egocore-4.0.0.0_ppc64le_build601861.tar.gz
- egomgmt-4.0.0.0_noarch_build601861.tar.gz
- egorest-4.0.0.0_noarch_build601861.tar.gz
- explorer-10.1.1.0_ppc64le_build601861.tar.gz
- hfcore-1.2.0.0_ppc64le_build601861.tar.gz
- cws-2.5.1.sh
7. Copyright and trademark information
© Copyright IBM Corporation 2024
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.