Readme File for IBM® Spectrum Symphony 7.3.2 Fix 601711
Readme File for: IBM Spectrum Symphony
Product Release: 7.3.2
Update Name: IBM Spectrum Symphony 7.3.2 Fix 601711
Fix ID: sym-7.3.2-build601711
Publication Date: September 29, 2023
The IBM Spectrum Symphony 7.3.2 Fix 601711 offering is available for 64-bit Linux x86 and Windows. It is available for IBM Spectrum Symphony, IBM Spectrum Symphony Advanced Edition with the multicluster feature, and IBM Spectrum Symphony Developer Edition as a full product installation, and also available for the IBM Spectrum Symphony client as a full product installation. For what’s included in Fix 601711, 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
IBM
Spectrum Symphony 7.3.2 Fix 601711 is a mandatory fix that contains various fixes and enhancements, and
includes Fix 601349 released in November 2022. Apply this cumulative fix on top
of IBM Spectrum Symphony. You can apply Fix 601711
even if you do not have Fix 601349 in your environment. The Fix 601711
installation includes everything in Fix 601349.
Fix 601711 includes all the fixes provided in Fix 601349, plus these new fixes and features:
·
Support for additional operating systems and upgraded
software, including:
o Linux RHEL 8.8 and RHEL 9.2.
o Python 3.10 for Windows and Linux (RHEL 7.x and 8.x).
o
Java 17.
o
C++ 17 standard for G++
o OpenSSL 3.0.8
o Nodejs 19.8.1.0
o Elastic Stack 7.17.9
o IBM JRE 8.0.8.5
o IBM WebSphere Application Server Liberty Profile 23.0.0.6
o OpenJDK 17.0.6.10
· Enhancement to use the EGO_SERVICE_CREDENTIAL parameter to log onto the IBM Spectrum Symphony host factory
RESTful server for authentication.
· Enhancement to the IBM Spectrum Symphony
client API to resolve an issue where a multicluster
client is stuck on shutdown due to a connection object pointer held in C++
static memory.
· Enhancement to the EGO and SOAM audit logs
to capture cluster management console operations to corresponding audit logs in
an IBM Spectrum Symphony 7.3.2 cluster.
· Enhancement to support verifying a peer
hostname against the server certificate’s DNS (defined in the Subject
Alternative Name) or CN.
· Enhancement to update the IBM Spectrum
Symphony host factory symA requestor plug-in to support IBM Spectrum
Symphony hostnames using the cloud provider's instance ID and not the cloud
provider's assigned hostname when requesting hosts.
· Enhancement to the session director's
management of SSM network disconnections.
· Support
for a non-default API endpoint URL when requesting hosts through an Amazon Web
Services (AWS) provider.
·
Various fixes to all other client-reported
issues and customer feedback since the IBM Spectrum Symphony 7.3.2 release.
Software compatibility notes:
·
Fix 601711 includes upgraded software which can require related
files be upgraded together for compatibility reasons. You require Fix 601711
before you can apply any other future fixes.
· Fix 601711 upgrades OpenSSL to version 3.0.8, and maintains compatibility with old applications. Once you have installed Fix 601711, you do not require rebuilding your original IBM Spectrum Symphony applications.
For more details, see the Fix 601711 release notes within IBM
Documentation.
2. Download location
Download IBM Spectrum Symphony 7.3.2 Fix 601711 from IBM Fix Central: https://www.ibm.com/eserver/support/fixes/
3. Product and components affected
Component name, Platform, Fix ID:
IBM Spectrum Symphony, Linux x86_64, Windows x86_64, sym-7.3.2-build601711
4. Installation and configuration
Follow the instructions in this section to download and apply IBM Spectrum Symphony 7.3.2 Fix 601711.
Fix 601711 for IBM Spectrum Symphony is offered as a fix on top of your
existing version of 7.3.2.
Therefore, you
must first have the 7.3.2 version of IBM Spectrum Symphony installed before
you can apply Fix 601711.
System
requirements
Depending on your operating
system, you require Linux x86 64-bit or Windows x86 64-bit for IBM Spectrum Symphony, IBM Spectrum Symphony
with the multicluster feature, IBM Spectrum Symphony
Developer Edition, or the IBM Spectrum Symphony client. For details, see all supported system configurations.
Before installation
Before
installing Fix 601711, refer to these important notes for your IBM Spectrum
Symphony product offering. Refer to note for the appropriate product offering:
Before
installing on IBM Spectrum Symphony
Before
installing on IBM Spectrum Symphpony with the multicluster feature
Before
installing on IBM Spectrum Symphony Developer Edition
Before installing on an IBM Spectrum Symphony client
Before installing Fix 601711 on IBM Spectrum Symphony
7.3.2
Download the installation package for your
operating system,
to a directory on each of your management and compute hosts (for example, to a /sym732 directory on Linux, or to a C:\sym732 directory on Windows).
Tip: On Linux, if you
installed the IBM Spectrum Symphony package using the egoinstallfixes command,
to avoid the original files (which are backed up under the $EGO_TOP/patch/backup/ directory) from being
scanned by security management related tools, move the files to other hosts
that do not have IBM Spectrum Symphony installed.
Installation packages to download:
· Linux:
sym-7.3.2.0_x86_64_build601711.tar.gz
Note that you will install Fix 601711 using the egoinstallfixes command,
which requires that your Linux host include the ed Linux
line-oriented text editor.
· Windows:
sym-7.3.2.0_build601711.zip
Precondition: On Windows, download
the sym-7.3.2.0.exe file from IBM Passport Advantage, and
decompress it to get the base .msi files:
sym-7.3.2.0.exe --extract downloaded_path_to_installed_msp_files
where downloaded_path_to_installed_msp_files is the same path as where
you unzip the .msp files during installation.
Before
installing Fix 601711 on IBM Spectrum Symphony 7.3.2 with the multicluster feature
Fix 601711 for IBM Spectrum
Symphony Advanced Edition with the multicluster
feature is offered as a fix on top of your existing version of 7.3.2. Therefore, you must first have the 7.3.2
version of IBM
Spectrum Symphony Advanced Edition with the multicluster
feature installed before
you can apply Fix 601711.
The multicluster feature is available for IBM Spectrum Symphony Advanced Edition. Download the installation package for your operating system, to a directory on your IBM Spectrum Symphony multicluster primary cluster (for example, to a /smc732 directory on Linux, or to a C:\smc732 directory on Windows):
· Linux:
symmc-7.3.2.0_x86_64_build601711.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.
· Windows:
symmc-7.3.2.0_build601711.zip
Precondition: On Windows, download the symmc-7.3.2.0.exe file from IBM Passport Advantage, and
decompress it to get the base .msi files:
symmc-7.3.2.0.exe
--extract downloaded_path_to_installed_msp_files
where downloaded_path_to_installed_msp_files is the same path as where you unzip the .msp files during installation
Before
installing Fix 601711 on IBM Spectrum Symphony Developer Edition 7.3.2
Fix 601711 for IBM Spectrum
Symphony Developer Edition is offered as a full product installation(verses a fix
applied on top of a specific release). In this case, you do not require IBM
Spectrum Symphony 7.3.2. If you are upgrading to the Fix 601711 version from an existing version of IBM Spectrum
Symphony, treat it as a separate installation (not a package to apply on top of
your existing version), and install to a different location than your previous
installation.
Download the installation package for your operating system to a directory on your development host (for example, to a /symde732 directory on Linux, or to a C:\symde732 directory on Windows):
· Linux: symde-7.3.2.0_x86_64.bin
·
Windows: symde-7.3.2.0.msi
Before
installing Fix 601711 on an IBM Spectrum Symphony 7.3.2 client
Fix
601711 for the IBM Spectrum Symphony client is available as a full installation package (verses a fix applied on top of
a specific release). In this case, you do not require IBM Spectrum Symphony
7.3.2. If you are upgrading to the Fix 601711 version
from an existing version of IBM Spectrum Symphony, treat it as a separate
installation (not a package to apply on top of your existing version), and
install to a different location than your previous installation.
Download the installation package for your operating system to a directory on your client host (for example, to a /symclnt732 directory on Linux, or to a C:\symclnt732 directory on Windows):
· Linux:
o
To
install as root: symclnt-7.3.2.0.x86_64.rpm or symclnt-7.3.2.0.x86_64.tar.gz
o
To
install as non-root: symclnt-7.3.2.0.x86_64.tar.gz
·
Windows: symclnt-7.3.2.0.msi
Installation
steps
Use the following
installation steps for the installation package applicable to your operating
system (Linux or Windows) and IBM Spectrum Symphony product offering. Refer to
the appropriate installation type:
Installing on IBM Spectrum Symphony
Installing on IBM Spectrum Symphony with the multicluster
feature
Installing on IBM Spectrum Symphony Developer Edition
Installing on an IBM Spectrum Symphony client
Installing Fix
601711 on IBM Spectrum Symphony 7.3.2
Before applying Fix 601711, ensure
that you have IBM Spectrum Symphony 7.3.2 installed for our operating system.
Linux
. 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 $ soamcontrol app disable all$ egosh service stop all
$ egosh ego shutdown alla. 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: sym-7.3.2.0_x86_64_build601711.tar.gz
For example,
use tar command:
$ tar zxof sym-7.3.2.0_x86_64_build601711.tar.gz
-C /sym732
iii.
Change
to the directory where you extracted the files, and then install Fix 601711 by
running the sym-7.3.2.sh file.
For example:
$ cd
/sym732
$
./sym-7.3.2.sh -m -i
The installer installs all necessary packages for your management host, including:
o
egocore-4.0.0.0_x86_64_build601711.tar.gz
o
egomgmt-4.0.0.0_noarch_build601711.tar.gz
o
egorest-4.0.0.0_noarch_build601711.tar.gz
o
explorer-10.1.1.0_x86_64_build601711.tar.gz
o
hfcore-1.2.0.0_x86_64_build601711.tar.gz
o
hfmgmt-1.2.0.0_noarch_build601711.tar.gz
o
soamcore-7.3.2.0_x86_64_build601711.tar.gz
o
soammgmt-7.3.2.0_noarch_build601711.tar.gz
o
soammrcore-7.3.2.0_x86_64_build601711.tar.gz (This one will be installed only if you have
MapReduce installed previously on your host.)
iv.
Change to the directory where
you downloaded all installation packages, and then install Fix 601711 by running
the symrpm-7.3.2.sh script.
· If you installed IBM Spectrum Symphony
7.3.2 with a specified RPM database path, use the
same database path here：
sudo ./symrpm-7.3.2.sh
-m -i dbpath
· If you installed IBM Spectrum Symphony
7.3.2 with the default RPM database path:
sudo ./symrpm-7.3.2.sh -m -i
The installer installs all
necessary packages for your management host, including
o
egonodejs-19.8.1.0.x86_64.rpm
o
egoelastic-1.4.6.0.x86_64.rpm
o
egojre-8.0.8.5.x86_64.rpm
o
egowlp-23.0.0.6.noarch.rpm
o
openjdkjre-17.0.6.10.x86_64.rpm
v.
Verify the
installation using the pversions command.
For example:
$ pversions
-b 601711
b. 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: sym-7.3.2.0_x86_64_build601711.tar.gz
For example,
use tar command:
$ tar zxof sym-7.3.2.0_x86_64_build601711.tar.gz
-C /sym732
iii.
Change to the directory
where you extracted the files, and then install Fix 601711 by running the sym-7.3.2.sh file.
For example:
$ cd /sym732
$ ./sym-7.3.2.sh -c -i
The installer installs all necessary packages for your compute
host, including
o egocore-4.0.0.0_x86_64_build601711.tar.gz
o soamcore-7.3.2.0_x86_64_build601711.tar.gz
o soammrcore-7.3.2.0_x86_64_build601711.tar.gz (This one will be installed only if you have MapReduce installed previously on your host.)
iv. Change to the directory where you downloaded all installation packages, and then install Fix 601711 by running the symrpm-7.3.2.sh script.
· If you installed IBM Spectrum Symphony
7.3.2 with a specified RPM database path, use the
same database path here：
sudo ./symrpm-7.3.2.sh
-c -i
dbpath
· If you installed IBM Spectrum Symphony
7.3.2 with the default RPM database path:
sudo ./symrpm-7.3.2.sh -c -i
The installer installs the necessary package for your compute host: egojre-8.0.8.5.x86_64.rpm
v.
Verify the
installation using the pversions command.
For example:
$ pversions
-b 601711
c.
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.
d. Complete the remaining steps on your primary host:
(Optional:
not required if you already applied Fix 601349) Create the RESOURCE_GROUP_ALLOCATION database table. For example, if using
Oracle, copy the perf/ego/4.0/DBschema/Oracle/egodata.sql file to the
directory where you have installed your Oracle database and create table
according to the script in egodata.sql:
/*==============================================================*/
/* TABLE:
RESOURCE_GROUP_ALLOCATION */
/*==============================================================*/
CREATE
TABLE RESOURCE_GROUP_ALLOCATION
(
CLUSTER_NAME VARCHAR2(128) NOT NULL,
RESOURCE_GROUP VARCHAR2(256) NOT NULL,
HOSTS NUMBER(10),
SLOTS NUMBER(10),
FREE NUMBER(10),
ALLOCATED NUMBER(10),
TIME_STAMP TIMESTAMP NOT NULL,
TIME_STAMP_GMT NUMBER(13)
NOT NULL,
CONSTRAINT PK_RESOURCE_GROUP_ALLOCATION
PRIMARY KEY(TIME_STAMP,
RESOURCE_GROUP)
USING INDEX TABLESPACE &TSINDEX
)TABLESPACE
&TSDATA;
e. Log on as root or a cluster administrator user with root privileges, and source your environment:
(BASH) . $EGO_TOP/profile.platform
(CSH) source
$EGO_TOP/cshrc.platform
f. If you ran the egosetsudoers.sh command before you installed Fix 601711, then run it again now on the host and before restarting the cluster to grant administrator root privileges.
g.
Restart the cluster and enable applications:
$ egosh ego start
all
$ soamcontrol app enable application_name
Tip: After
installing Fix 601711 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 Symphony installed.
·
Remove
the old files by running:
$ sudo rpm -e old_rpm --dbpath database_path --nodeps
Windows
a.
Log on to your primary
host as the operating system cluster administrator, and stop the cluster:
> egosh user logon -u Admin -x Admin
> soamcontrol app disable all
> egosh
service stop all
> egosh ego shutdown all
b. Complete the following steps for each management and compute host in the cluster:
i.
Log on as the
cluster administrator with local administrator privileges and change to the
directory where you downloaded the installation file.
For example:
cd C:\sym732
ii.
Decompress the
following zip file:
sym-7.3.2.0_build601711.zip
iii.
Run the
installation file:
On management
hosts: > sym-7.3.2.bat -m -i
On compute hosts: > sym-7.3.2.bat -c -i
iv.
Install other Windows
packages on management host:
To install the .msi
packages directly by using the command prompt to
install each one silently:
a)
C:\>msiexec /i
C:\sym732\egojre-8.0.8.5.msi /l*v updateSym.log /qn MASTERHOST=host001.local
INSTALLDIR=”C:\\Program Files\\IBM\\SpectrumComputing”
b)
C:\>msiexec /i
C:\sym732\egowlp-23.0.0.6.msi /l*v updateSym.log /qn MASTERHOST=host001.local
INSTALLDIR=”C:\\Program Files\\IBM\\SpectrumComputing”
The
command syntax is as follows:
msiexec /i sym_package_name_path /l*v sym_install_log /qn MASTERHOST=host_name INSTALLDIR=installation_directory
where:
sym_package_name_path is the fully qualified path to the .msi packages; in this case, C:\sym732\egojre-8.0.8.5.msi and C:\sym732\egowlp-23.0.0.6.msi.
host_name is the primary host name in your cluster; in
this case, host001.local.
installation_directory is the installation path; in this case, C:\Program
Files\IBM\SpectrumComputing.
sym_install_log is the log file for the upgrade; in this case, updateSym.log.
To install the .msi
packages interactively:
a) Double-click the egojre-8.0.8.5.msi installation
package and follow the prompts.
b) Double-click the egowlp-23.0.0.6.msi
installation package and follow the prompts.
v.
Verify the installation
using the pversions command.
For example:
pversions
The command output should show the installed packages.
c. Complete the remaining steps on your primary host:
i.
Modify the wsm.conf file:
Open the %EGO_CONFDIR%\wsm.conf file, locate the line with the JVM_ARGS parameter, and add -Dlog4j2.disableJmx=true to the end:
JVM_ARGS="-Xmx4096m
-Dhttps.protocols=TLSv1.2 -Dssl_protocol=TLSv1.2
-Xshareclasses:name=sharedcc%EGOJRE_VERSION%,nonpersistent,nonfatal
-Dcom.ibm.ws.logging.message.file.name=messages_gui_server.log
-DGUI_LOGDIR=logs -DPERF_LOGDIR=../perf/logs -Dkc.log.dir=logs
-DGUI_TMPDIR=../gui/temp -Dlog4j2.disableJmx=true"
ii. (Optional: not required if you already applied Fix 601349) Create the RESOURCE_GROUP_ALLOCATION database table. For example, if using Oracle, copy the perf/ego/4.0/dBschema/Oracle/egodata.sql file to the directory where you have installed your Oracle database and create table according to the script in egodata.sql:
/*==============================================================*/
/* TABLE:
RESOURCE_GROUP_ALLOCATION */
/*==============================================================*/
CREATE
TABLE RESOURCE_GROUP_ALLOCATION
(
CLUSTER_NAME VARCHAR2(128) NOT NULL,
RESOURCE_GROUP VARCHAR2(256) NOT NULL,
HOSTS NUMBER(10),
SLOTS NUMBER(10),
FREE NUMBER(10),
ALLOCATED NUMBER(10),
TIME_STAMP TIMESTAMP NOT NULL,
TIME_STAMP_GMT NUMBER(13)
NOT NULL,
CONSTRAINT PK_RESOURCE_GROUP_ALLOCATION
PRIMARY KEY(TIME_STAMP,
RESOURCE_GROUP)
USING INDEX TABLESPACE &TSINDEX
)TABLESPACE
&TSDATA;
d. On each management host, delete all
subdirectories and files from the following directories:
> del %EGO_CONFDIR%\..\..\gui\work\*
> del %SOAM_HOME%\..\gui\workarea\*
> del %SOAM_HOME%\..\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. Start the cluster on your primary host by logging on as root or a cluster administrator user with root privileges, reopen a Symphony 7.3.2 command console, restarting the cluster, and enabling the applicable applications:
> egosh ego start all
> soamcontrol app enable application_name
Installing Fix 601711 on IBM Spectrum Symphony 7.3.2 with the multicluster feature
Log on as the operating system cluster administrator and install the Fix 601711 installation
package, which you previously downloaded, to the IBM Spectrum Symphony multicluster primary cluster:
Linux
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 allb. Complete these steps for each 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
Extract the .tar.gz file that you
previously downloaded: symmc-7.3.2.0_x86_64_build601711.tar.gz
For example,
use tar command:
$ tar zxof symmc-7.3.2.0_x86_64_build601711.tar.gz
-C /smc732
ii.
Change to the directory where
you extracted the file, and then install Fix 601711 by running the smc-7.3.2.sh and symrpm-7.3.2.sh files:
$ cd /smc732
$ ./smc-7.3.2.sh -i
The installer installs
all necessary packages for your host, including
o
symmccore-7.3.2.0_x86_64_build601711.tar.gz
o
symmcegorest-4.0.0.0_noarch_build601711.tar.gz
o
symmcmgmt-7.3.2.0_noarch_build601711.tar.gz
o
symmcegocore-4.0.0.0_x86_64_build601711.tar.gz
Next, run the smcrpm-7.3.2.sh script:
· If you installed IBM Spectrum Symphony 7.3.2 with a specified
RPM database path, use the same database path here：
sudo ./smcrpm-7.3.2.sh -i
dbpath
· If you installed IBM Spectrum Symphony 7.3.2 with the default
RPM database path:
sudo ./smcrpm-7.3.2.sh
-i
The installer installs all necessary packages for your management host, including symmcegojre-8.0.8.5.x86_64.rpm and symmcegowlp-23.0.0.6.noarch.rpm.
iii.
Verify the installation using the pversions command.
For example:
$ pversions -b 601711
c. 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.
d. Log
on as root or a cluster administrator user with root privileges, and source
your environment:
(BASH) . $EGO_TOP/profile.platform
(CSH) source
$EGO_TOP/cshrc.platform
e. If
you ran the egosetsudoers.sh
command before you installed Fix
601711, then run it again now on the host and before restarting the cluster to
grant administrator root privileges.
f. Restart
the cluster and enable applications:
$ egosh
ego start all
$ soamcontrol app enable application_name
Tip: After installing Fix 601711 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 Symphony multicluster installed.
·
Remove
the old files by running:
$ sudo rpm -e old_rpm --dbpath database_path --nodeps
Windows
. Log on to your 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
a. Complete the following steps for each host in the cluster:
i.
Log on as the
cluster administrator with local administrator privileges and change to the
directory where you downloaded the installation file.
For example:
cd C:\smc732
ii.
Run the
installation file:
> smc-7.3.2.bat -i
Installation_top
Installation_top is the directory where EGO is installed.
iii.
Install other Windows
packages:
To install the .msi
packages directly by using the command prompt to
install each one silently:
a)
C:\>msiexec /i C:\smc732\symmcegojre-8.0.8.5.msi /l*v
updateSym.log /qn MASTERHOST=host001.local
INSTALLDIR=”C:\\Program Files\\IBM\\SpectrumComputing”
b)
C:\>msiexec /i C:\smc732\symmcegowlp-23.0.0.6.msi /l*v
updateSym.log /qn MASTERHOST=host001.local
INSTALLDIR=”C:\\Program Files\\IBM\\SpectrumComputing”
The
command syntax is as follows:
msiexec /i symmc_package_name_path /l*v sym_install_log /qn MASTERHOST=host_name INSTALLDIR=installation_directory
where:
symmc_package_name_path is the fully qualified path to the .msi packages; in this case, C:\smc732\symmcegojre-8.0.8.5.msi and C:\smc732\symmcegowlp-23.0.0.6.msi.
host_name is the primary host name in your cluster; in this
case, host001.local.
installation_directory is the installation path; in this case, C:\Program
Files\IBM\SpectrumComputing.
sym_install_log is the log file for the upgrade; in this case, updateSym.log.
To install the .msi
packages interactively:
a)
Double-click the symmcegojre-8.0.8.5.msi installation package and follow the prompts.
b)
Double-click the symmcegowlp-23.0.0.6.msi
installation package and
follow the prompts.
iv.
Verify
the installation using the pversions command.
For example:
pversions
The command output should show the two .msi
packages installed.
b. On each host, delete all subdirectories and
files from the following directories:
> del %EGO_CONFDIR%\..\..\gui\work\*
> del %SOAM_HOME%\..\gui\workarea\*
> del %SOAM_HOME%\..\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.
c. Start the cluster on your primary host by logging on as root or as a cluster administrator user with root privileges, reopen a Symphony Multicluster 7.3.2 command console, and restarting the cluster:
> egosh ego start all
Installing
Fix 601711 on IBM
Spectrum Symphony Developer Edition 7.3.2
Log on as the operating system cluster
administrator, install Fix 601711, which you previously downloaded to your
development host:
· Linux: symde-7.3.2.0_x86_64.bin
· Windows: symde-7.3.2.0.msi
Linux
Follow Installing IBM Spectrum Symphony Developer Edition on one host.
Windows
Follow Installing IBM Spectrum Symphony Developer Edition on one host.
Installing Fix 601711 on an IBM Spectrum
Symphony 7.3.2 client
Log on as the operating system cluster administrator and
install the Fix 601711 installation package, which you previously downloaded,
to your client host:
· Linux:
o To install with root: symclnt-7.3.2.0.x86_64.rpm or symclnt-7.3.2.0.x86_64.tar.gz
o
To
install with non-root: symclnt-7.3.2.0.x86_64.tar.gz
Note: If you already have the IBM Spectrum Symphony client installed on Linux, install the Fix 601711 package to a different directory.
· Windows: symclnt-7.3.2.0.msi
To install on Windows, follow Installing the IBM Spectrum Symphony client on Windows.
Note: If you already
have the IBM Spectrum Symphony 7.3.2 client installed on Windows, first
uninstall version 7.3.2, and then install Fix 601711. If you have any other
previously installed versions, install the Fix 601711 package to a different
directory.
5. Uninstalling
If required, follow the instructions in this section
to uninstall Fix 601711 from your cluster. Refer to the appropriate product
offering:
Uninstalling from IBM
Spectrum Symphony
Uninstalling
from IBM Spectrum Symphony with the multicluster feature
Uninstalling
from IBM Spectrum Symphony Developer Edition
Uninstalling
from an IBM Spectrum Symphony client
Uninstalling Fix 601711 from IBM Spectrum Symphony 7.3.2
Linux
.
Log on to the
primary host as the operating system cluster administrator, and stop the
cluster:
$ egosh user logon -u Admin -x Admin
$ soamcontrol
app disable all
$ egosh service stop all
$ egosh ego
shutdown all
a.
Log on to each
Linux management host in the cluster and switch to the directory where you extract the package
(for example/sym732), and roll back the fix:
i. If you ran the egosetsudoers.sh command after you installed Fix 601711, change the owner back to clusteradmin now, before rolling back the fix. For example:
$ sudo chown
clusteradmin:clusteradmin
$EGO_TOP/4.0/linux-x86_64/bin/egosh
ii.
Roll back all .tar.gz files for Fix 601711 by running the sym-7.3.2.sh file:
$ sym-7.3.2.sh -m -r
iii.
Roll back all .rpm files for
Fix 601711 by running the symrpm-7.3.2.sh script:
$ sudo
./symrpm-7.3.2.sh -m -r
b. Log on to each Linux compute host in the cluster, switch to the directory where you extracted the package
(for example:/sym732), and roll back the fix:
i.
Roll back all .tar.gz files for Fix 601711 by running the sym-7.3.2.sh file
$
sym-7.3.2.sh -c
-r
ii.
Rollback all rpm files for Fix
601711 by running the symrpm-7.3.2.sh script.
$ sudo
./symrpm-7.3.2.sh -c -r
c. 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
d. Log on as root or a cluster administrator user with root privileges, and source your environment:
(BASH) . $EGO_TOP/profile.platform
(CSH) source $EGO_TOP/cshrc.platform
e. If
you ran the egosetsudoers.sh
command before you installed Fix 601711, then run
it again now on the host to grant administrator root privileges before starting
the cluster.
f.
Restart the cluster and enable
applications:
$ egosh ego start
all
$ soamcontrol app enable application_name
Tip: After rolling back, the new .rpm files from this fix are still in your file system and RPM database path. If you are certain that you no longer need these files, you can delete them by running:
$ sudo rpm -e new_rpm --dbpath database_path –nodeps
Windows
Note: The
following steps will uninstall all changes in Fix 601711 from your Windows
host. To recover Fix 601349 or IBM Spectrum Symphony 7.3.2, contact IBM
Support.
a.
Log on to the primary
host as the operating system cluster administrator, and stop the cluster:
> egosh user logon -u Admin -x Admin
> soamcontrol app disable all
> egosh
service stop all
> egosh
ego shutdown all
b.
Log on
each Windows management host and
roll back these .msi files:
· To uninstall
the .msi packages interactively:
i. From Windows Control Panel > Programs and Features, select IBM Spectrum Computing family: IBM JRE 8.0.8.5, and uninstall the program.
ii. From Windows Control Panel > Programs and Features, select IBM Spectrum Computing family: IBM WebSphere Application Server Liberty Profile 23.0.0.6, and uninstall the program.
·
To uninstall the egojre-8.0.8.5.msi and egowlp-23.0.0.6.msi files directly by using the command prompt to uninstall each one silently:
> msiexec /uninstall
{54DE60C9-FA4D-4A25-B765-EEB27CCE9611} /norestart /quiet
> msiexec /uninstall
{15FB5ED0-E121-4DEA-95BB-7A6B56DBB24E} /norestart
/quiet
c.
Roll back
the configuration: once the egojre-8.0.8.5.msi and egowlp-23.0.0.6.msi files
are uninstalled from your host, and you want to roll back to the old version of
these two packages (for example, to roll back to IBM JRE 8.0.6.36 and IBM
WebSphere Application Server Liberty Profile 21.0.0.9), ensure that the old
version is still on your host, and then follow these steps:
· Modify the EGOJRE_VERSION
parameter in the following configuration files to point to the old version of
IBM JRE:
%SOAM_HOME%\..\jre\setjre.bat
%SOAM_HOME%\..\jre\jre.conf
· Modify the WLP_VERSION
parameter in the following configuration files to point to the old version of
IBM WebSphere Application Server Liberty Profile:
%SOAM_HOME%\..\wlp\setwlp.bat
%SOAM_HOME%\..\wlp\wlp.conf
d.
Log on
each Windows host and uninstall the .msp file:
On management hosts: > sym-7.3.2.bat -m -r
On compute hosts: > sym-7.3.2.bat -c -r
e. Rollback the wsm.conf file, Open the %EGO_CONFDIR%\wsm.conf
file, locate the line with the JVM_ARGS parameter,
and delete -Dlog4j2.disableJmx=true at the end of the line.
f. On each management host, delete all
subdirectories and files from the following directories:
> del %EGO_CONFDIR%\..\..\gui\work\*
> del %SOAM_HOME%\..\gui\workarea\*
> del %SOAM_HOME%\..\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
g. Start
the cluster on your primary host by logging on as root or a cluster
administrator user with root privileges, reopen a Symphony 7.3.2 command
console, restarting the
cluster, and enabling the applicable applications:
> egosh
ego start all
> soamcontrol
app enable application_name
Uninstalling
Fix 601711 from IBM Spectrum
Symphony 7.3.2 with the multicluster feature
Linux
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
b.
Complete these steps for each 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.
Log on to each host in the cluster and switch to the
directory where you extract the package (for example /smc732), and roll back the fix:
iii.
If you ran the egosetsudoers.sh command after you
installed Fix 601711, change the owner back to clusteradmin
now, before rolling back the fix. For example:
$ sudo
chown clusteradmin:clusteradmin
$EGO_TOP/4.0/linux-x86_64/bin/egosh
iv.
Roll
back Fix 601711:
$ ./smc-7.3.2.sh -r
$ sudo ./smcrpm-7.3.2.sh -r
d. On each 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. Log on as root or a cluster administrator user with root privileges, and source your environment:
(BASH) . $EGO_TOP/profile.platform
(CSH) source $EGO_TOP/cshrc.platform
f.
If you ran the egosetsudoers.sh
command before you installed Fix 601711, then run
it again after now on the host to grant administrator root privileges before
starting the cluster.
g. Restart the cluster and enable applications:
$ egosh
ego start all
$ soamcontrol app enable application_name
Tip:
After rolling back, the new .rpm files from this fix are still in your file
system and RPM database path. If you are certain that you no longer need these files,
you can delete them by running:
$ sudo rpm
-e new_rpm --dbpath database_path –nodeps
Windows
a. Log on to your 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
b.
Log on
each Windows host and roll back the .msi files:
·
To uninstall the .msi
packages interactively:
i. From Windows Control Panel > Programs and Features, right-click IBM Spectrum Computing family: IBM JRE (Java runtime environment) package for IBM Spectrum Symphony Advanced Edition multicluster (Version 8.0.8.5) and select Uninstall
ii. From the Windows Control Panel >
Programs and Features, right-click IBM Spectrum Computing
family: IBM WebSphere Application Server Liberty Profile package
for IBM Spectrum Symphony Advanced Edition multicluster (Version
23.0.0.6) and select Uninstall.
·
To uninstall the
symmcegojre-8.0.8.5.msi and symmcegowlp-23.0.0.6.msi files
directly by using the command prompt to uninstall each one silently:
> msiexec /uninstall
{DD8FFDD8-735B-462E-9AF6-9ED68CD7000F} /norestart /quiet
> msiexec /uninstall
{1E08E0E3-28FA-457D-B299-AE72716E46C4} /norestart /quiet
c. Roll back the configuration: once the symmcegojre-8.0.8.5.msi and
symmcegowlp-23.0.0.6.msi files are uninstalled from your host, and you want to
roll back to the old version of these two packages (for example, to roll back
to IBM JRE 8.0.6.36 and IBM WebSphere Application Server Liberty Profile
21.0.0.9), ensure that the old version is still on your host, and then follow
these steps:
·
Modify the EGOJRE_VERSION parameter in the following
configuration files to point to the old version of IBM JRE:
%SOAM_HOME%\..\jre\setjre.bat
%SOAM_HOME%\..\jre\jre.conf
·
Modify the WLP_VERSION parameter in the following
configuration files to point to the old version of IBM WebSphere Application
Server Liberty Profile:
%SOAM_HOME%\..\wlp\setwlp.bat
%SOAM_HOME%\..\wlp\wlp.conf
d.
Log on each Windows host and roll back the .msp files:
> smc-7.3.2.bat -r
e. On each host, delete all subdirectories and
files from the following directories:
> del %EGO_CONFDIR%\..\..\gui\work\*
> del %SOAM_HOME%\..\gui\workarea\*
> del %SOAM_HOME%\..\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
f.
Start the cluster on your
primary host by logging on as root or a cluster administrator user with root
privileges, reopen a Symphony Multicluster 7.3.2
command console, and restarting
the cluster:
> egosh
ego start all
Uninstalling Fix 601711 from IBM Spectrum Symphony 7.3.2 Developer
Edition
Log on as the operating system cluster administrator, and
uninstall Fix 601711 from your development
host:
· Linux: symde-7.3.2.0_x86_64.bin
·
Windows: symde-7.3.2.0.msi
Linux
Follow Uninstalling IBM
Spectrum Symphony Developer Edition.
Windows
Follow Uninstalling IBM
Spectrum Symphony Developer Edition.
Uninstalling Fix 601711 from the IBM
Spectrum Symphony 7.3.2 client
Log on as the operating system cluster administrator, and
uninstall Fix 601711 from your client host:
· Linux:
To
uninstall:
symclnt-7.3.2.0.x86_64.rpm or symclnt-7.3.2.0.x86_64.tar.gz
·
Windows: symclnt-7.3.2.0.msi
Follow Uninstalling the IBM
Spectrum Symphony client.
6. List of files
sym-7.3.2.0_x86_64_build601711.tar.gz
- egocore-4.0.0.0_x86_64_build601711.tar.gz
- egomgmt-4.0.0.0_noarch_build601711.tar.gz
- egorest-4.0.0.0_noarch_build601711.tar.gz
- explorer-10.1.1.0_x86_64_build601711.tar.gz
- hfcore-1.2.0.0_x86_64_build601711.tar.gz
- hfmgmt-1.2.0.0_noarch_build601711.tar.gz
- soamcore-7.3.2.0_x86_64_build601711.tar.gz
- soammgmt-7.3.2.0_noarch_build601711.tar.gz
- soammrcore-7.3.2.0_x86_64_build601711.tar.gz
- egonodejs-19.8.1.0.x86_64.rpm
- egoelastic-1.4.6.0.x86_64.rpm
- egojre-8.0.8.5.x86_64.rpm
- egowlp-23.0.0.6.noarch.rpm
- openjdkjre-17.0.6.10.x86_64.rpm
-
sym-7.3.2.sh
- symrpm-7.3.2.sh
symmc-7.3.2.0_x86_64_build601711.tar.gz
-
symmccore-7.3.2.0_x86_64_build601711.tar.gz
-
symmcegorest-4.0.0.0_noarch_build601711.tar.gz
-
symmcmgmt-7.3.2.0_noarch_build601711.tar.gz
-
symmcegocore-4.0.0.0_x86_64_build601711.tar.gz
-
symmcegojre-8.0.8.5.x86_64.rpm
- symmcegowlp-23.0.0.6.noarch.rpm
-
smc-7.3.2.sh
- smcrpm-7.3.2.sh
sym-7.3.2.0_build601711.zip
- sym-7.3.2.0-soamcore-7.3.2.0_build601711.msp
- sym-7.3.2.0-soammgmt-7.3.2.0_build601711.msp
- sym-7.3.2.0-egocore-4.0.0.0_build601711.msp
- sym-7.3.2.0-egomgmt-4.0.0.0_build601711.msp
- sym-7.3.2.0-hfmgmt-1.2.0.0_build601711.msp
- sym-7.3.2.0-hfcore-1.2.0.0_build601711.msp
-
sym-7.3.2.0-egorest-4.0.0.0_build601711.msp
-
egojre-8.0.8.5.msi
-
egowlp-23.0.0.6.msi
-
sym-7.3.2.bat
symmc-7.3.2.0_build601711.zip
-
symmcegojre-8.0.8.5.msi
-
symmcegowlp-23.0.0.6.msi
- symmccore-7.3.2.0_build601711.msp
-
symmcmgmt-7.3.2.0_build601711.msp
-
symmcegorest-4.0.0.0_build601711.msp
- symmcegocore-4.0.0.0_build601711.msp
-
smc-7.3.2.bat
symclnt-7.3.2.0.msi
symclnt-7.3.2.0.x86_64.rpm
symclnt-7.3.2.0.x86_64.tar.gz
symde-7.3.2.0_x86_64.bin
symde-7.3.2.0.msi
7. Copyright and trademark information
© Copyright IBM Corporation 2023
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.