Readme File for IBM® Platform Symphony 6.1.1 Interim Fix 448920

Readme File for: IBM Platform Symphony

Product Release: 6.1.1

Update Name: Interim Fix 448920

Fix ID: sym-6.1.1-build448920-citi

Publication Date: April 13, 2017

This interim fix enables the session manager (SSM) to log details of all hosts on which the SIM failed, along with the PID of the SIM, when binding fails for a session.

Contents

1. List of fixes

2. Download location

3. Product and components affected

4. Installation and configuration

5. List of files

6. Copyright and trademark information

1.     List of fixes

APAR: P102181

2.     Download location

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

3.     Product and components affected

Component name, Platform, Fix ID:

SOAM, Linux x86_64, sym-6.1.1-build448920-citi

4.     Installation and configuration

System requirements

Linux x86_64

Before installation

a.      Log on to the master host as the cluster administrator, disable all applications, and shut down the cluster:

> soamcontrol app disable all

> egosh service stop all

> egosh ego shutdown all

b.      Log on to each management host in the cluster and back up the following files, which will be replaced by this interim fix:

$EGO_TOP/soam/6.1.1/linux2.6-glibc2.3-x86_64/etc/sd

$EGO_TOP/soam/6.1.1/linux2.6-glibc2.3-x86_64/etc/ssm

Installation

a.      Log on to each management host in the cluster and decompress the sym6.1.1_lnx26-lib23-x64_build448920.tar.gz package:

> tar zxfo sym6.1.1_lnx26-lib23-x64_build448920.tar.gz -C $EGO_TOP

b.      Edit the $EGO_CONFDIR/../../eservice/esc/conf/services/sd.xml file to add the SSM_LOG_HOST_INFO_ON_BINDING_FAILURE environment variable with a value of “TRUE”. For example:

<sc:ActivityDescription>

    <ego:Attribute name="hostType" type="xsd:string">X86_64</ego:Attribute>

    <ego:ActivitySpecification>

     ....

    <ego:EnvironmentVariable name="SSM_LOG_HOST_INFO_ON_BINDING_FAILURE">TRUE</ego:EnvironmentVariable>

     ....

 </ego:ActivitySpecification>

</sc:ActivityDescription>

After installation

a.      Verify the installation:

·        Run the sd -V command. The following is sample output of successfully running this command:

> sd -V

IBM Platform Symphony 6.1.1.0 build 448920, Apr 11 2017

Copyright International Business Machines Corp, 1992-2013.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

·        Run the ssm -V command. The following is sample output of successfully running this command:

> ssm -V

IBM Platform Symphony 6.1.1.0 build 448920, Apr 23 2017

Copyright International Business Machines Corp, 1992-2013.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

b.      Start the cluster and enable your applications:

> egosh ego start all

> soamcontrol app enable <appName>

Uninstallation (if required)

a.      Log on to the master host as the cluster administrator, disable all applications, and shut down the cluster:

> soamcontrol app disable all

> egosh service stop all

> egosh ego shutdown all

b.      Log on to each management host in the cluster and restore the following files from your backup:

$EGO_TOP/soam/6.1.1/linux2.6-glibc2.3-x86_64/etc/sd

$EGO_TOP/soam/6.1.1/linux2.6-glibc2.3-x86_64/etc/ssm

c.      Edit the $EGO_CONFDIR/../../eservice/esc/conf/services/sd.xml file to remove the SSM_LOG_HOST_INFO_ON_BINDING_FAILURE environment variable.

d.      Start the cluster and enable your applications:

> egosh ego start all

> soamcontrol app enable <appName>

5.     List of files

sd ssm

6.     Copyright and trademark information

© Copyright IBM Corporation 2017

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.