IBM Platform Symphony 5.1 Fix 230653 Readme File

Abstract

SUP_BY_SYM#224001: When vemkd crashes, some uninitialized data loaders fail to recover until plc is restarted.

APAR#P100284: When a Symphony service instance has an infinite loop or other event listeners in the callback function onSessionEnter, after the user tries to abort the session, the slot occupied by the instance is wasted.

SUP_BY_SYM#225023: The user cannot save an imported resource plan on the GUI.

SUP_BY_SYM#227438: The borrow limit value is not correct when many times Borrow Details pages are opened to change its value, which results in an error message in the vemkd log.

Description

SUP_BY_SYM#224001:

· When vemkd is temporarily unavailable, the plc logs show that some uninitialized data loaders cannot recover.

APAR#P100284:

· If the callback function onSessionEnter does not return for a long time when the session is aborted, the slot occupied by the service instance is wasted.

· The service instance and the corresponding SIM hang indefinitely, and other applications cannot use the wasted slots.

SUP_BY_SYM#225023:

· When the user logs on to the GUI, goes to Consumers > Consumers&Plan > ResourcePlan and exports the resource plan. When the user imports the resource plan and clicks Apply, a pop-up message appears and the resource plan is not saved.

SUP_BY_SYM#227438:

The error occurs when the user does the following:

· Logs on to the GUI, and goes to Consumers > Consumers&Plan > ResourcePlan.

· On the Borrow Details page, adjusts the limit of one consumer borrowed from another consumer.

· Clicks Apply > OK > OK on the Consumers&Plan page to make the change take effect.

· Repeats the above steps.

· The error message appears in the vemkd logs.

This fix patch applies only to the following platform:

· Linux 64-bit

Readme file for: IBM® Platform Symphony

Product/Component Release: 5.1

Update Name: Fix 230653

Fix ID: sym-5.1-build230653

Publication date: 18 March 2014

Last modified date: 18 March 2014

Contents:

1. List of fixes

2. Download location

3. Products or components affected

4. Installation and configuration

5. List of files

6. Copyright and trademark information

1. List of fixes

SUP_BY_SYM#224001: For Symphony PERF 5.1, if a loader cannot be initialized correctly due to cluster instability, the loader cannot be recovered later on, although the loader shows as being enabled and the cluster becomes stable.

APAR#P100284: Aborting a session does not release slots when services are stuck in onSessionEnter.

SUP_BY_SYM#225023: The consumer administrator cannot import the previously exported resource plan.

SUP_BY_SYM#227438: The WEBGUI triggers a wrong request from the Borrow Details page to vemkd, which results in an error message in the vemkd log.

2. Download Location

Download Fix 230653 from the following location: http://www.ibm.com/eserver/support/fixes/

3. Products or components affected

Product/Component Name:

Platform Symphony/PERF,SSM,WEBGUI

4. Installation and configuration

4.1 Before installation

1. Stop the plc WEBGUI service and disable all applications.

Log on to the master host as the cluster administrator and run:

> source $EGO_TOP/cshrc.platform

> egosh user logon -u Admin -x Admin

> egosh service stop plc WEBGUI

> soamcontrol app disable all

2. Back up the files.

Log on to each management host and each compute host and back up the following file that will be replaced by this fix:

· $EGO_TOP/perf/ego/1.2.5/lib/perf_ego_loader.jar

· $EGO_TOP/perf/soam/5.1/lib/perf_soam_loader.jar

· $SOAM_HOME/5.1/linux2.6-glibc2.3-x86_64/etc/ssm

· $EGO_TOP/gui/ego/1.2.5/platform/WEB-INF/classes/com/platform/vem/gui/api/ConsumerResourcePlanUtil.class

· $EGO_TOP/gui/ego/1.2.5/platform/WEB-INF/classes/com/platform/vem/gui/web/ApplicationResources.properties

· $EGO_TOP/gui/ego/1.2.5/platform/js/ResourcePlanDetail.js

4.2 Installation steps

1. Low-Risk Method

These steps have the lowest risk to production environments. The cluster can be quickly rolled back if the management host fails.

a. For every existing management host in the cluster, add a new management host. At least one of the new management hosts must be a master candidate (that is, it must be listed in the cluster’s master list).

b. Update the new hosts with this patch and verify that they are functioning correctly.

c. Update or remove the original management hosts.

2. Installation Instructions

a. To update the cluster on Linux, use the RPM upgrade option on each host in the cluster to install EGO first, then the Symphony packages.

Note: While the same Symphony package is used for both management and compute hosts, the EGO installation is only used for management hosts.

b. For the RPM package:

· Use RPM version 4.2.1 or later.

· Use the same prefix that was used for the initial installation.

· Use the same dbpath that was used for the initial installation.

c. For example:

· If the dbpath and prefix were set as follows in the previous Symphony 5.1 installations:

> rpm -ivh --dbpath /tmp/rpm -prefix /opt/platform ego-linux2.6-glibc2.3-x86_64-1.2.5-nnnnnn.rpm

> rpm -ivh --dbpath /tmp/rpm -prefix /opt/platform symphony-linux2.6-glibc2.3-x86_64-5.1.0-nnnnnn.rpm

· Then the same dbpath and prefix must be used when installing current Symphony 5.1 Fix patch.

> rpm -Uvh --dbpath /tmp/rpm -prefix /opt/platform --nopreun --nopostun ego-linux2.6-glibc2.3-x86_64-1.2.5-230653.rpm

> rpm -Uvh --dbpath /tmp/rpm -prefix /opt/platform --nopreun --nopostun symphony-linux2.6-glibc2.3-x86_64-5.1.0-230653.rpm

4.3 After installation

1. Clean up the GUI work directory and the browser cache.

To clean up the GUI work directory, delete all subdirectories and files in this directory.

2. Start the plc WEBGUI service and enable all applications.

Log on to the master host as the cluster administrator and run:

> egosh user logon -u Admin -x Admin

> egosh service start plc WEBGUI

> soamcontrol app enable <appName>

4.4 Uninstallation

1. Stop the plc WEBGUI service and disable all applications.

Log on to the master host as the cluster administrator and run:

> egosh user logon -u Admin -x Admin

> egosh service stop plc WEBGUI

> soamcontrol app disable all

2. Uninstall.

Downgrade the Symphony product using the previous RPM package. For example, to roll back a Symphony management host:

> rpm -Uvh -dbpath /tmp/rpm -prefix /opt/platform --nopreun --nopostun --oldpackage symphony-linux2.6-glibc2.3-x86_64-5.1.0-nnnnnn.rpm

Note: symphony-linux2.6-glibc2.3-x86_64-5.1.0-nnnnnn.rpm refers to previous Symphony 5.1 fix patch

3. Clean up the GUI work directory and the browser cache.

To clean up the GUI work directory, delete all subdirectories and files in this directory.

4. Start the plc WEBGUI service and enable all applications.

Log on to the master host as the cluster administrator and run:

> egosh service start plc WEBGUI

> soamcontrol app enable <appName>

5. List of files

· perf_ego_loader.jar

· perf_soam_loader.jar

· ssm

· ConsumerResourcePlanUtil.class

· ApplicationResources.properties

· ResourcePlanDetail.js

6. Copyright and trademark information

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.