IBM Platform Application Center 9.1.3 Fix 240577 Readme

Abstract

This fix resolves the issue that files larger than 2 GB cannot be uploaded with Web Services, and adds support for viewing job output in Terminal Services through Platform Application Center.

Description

Readme documentation for IBM Platform Application Center 9.1.3 Fix 240577 including installation-related instructions, prerequisites and co-requisites, and list of fixes.

This fix addresses the following issues:

    -  It was not possible to upload files that are larger than 2 GB with Web Services. This limitation is now removed and files can be uploaded with Web Services regardless of
       file size.

This fix adds support for:

    -  Submitting a Terminal Services job in Platform Application Center with the new template Remote_Windows_Desktop. Once the job starts running, users click the Visualize
       icon to download the generated .rdp file to their desktop and automatically display the Terminal Services session associated with the job with Windows Remote Desktop
       Connection.

Readme file for: IBM® Platform Application Center
Product/Component Release: 9.1.3.0
Update Name: Fix 240577
Fix ID: pac9.1.3_standard_linux-x64.tar.Z
Publication date: 18 Aug 2014
Last modified date:  21 Aug 2014

Contents:

• List of fixes
• Download location
• Products or components affected
• System requirements
• Known issues
• Installation and configuration
• Uninstallation 
• List of files
• Copyright and trademark information

• List of fixes

APAR#: P100579

• Download Location

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

• Products or components affected

 Affected components include: Job, Web services.

• System requirements

Windows OS on the Windows servers must be server edition, including:

      64 bit Microsoft Windows Server 2003

      64 bit Microsoft Windows Server 2008 R2 Enterprise SP1

      64 bit Microsoft Windows Server 2012

• Known issues

If Platform Application Center 9.1.3 is already installed, the following messages are displayed during installation of the fix. You can safely ignore these messages as no functionality is affected:
    - "ln: creating symbolic link '${PAC_TOP}/gui/3.0/wlp/etc/jvm.options': File exists".
    - The following message is missing the port number: "http://hostname:"

• Installation and configuration

6.1 Before installation

           Stop all IBM Platform Application Center services:

           If EGO is not enabled:

perfadmin stop all
               pmcadmin stop

If EGO is enabled:

           a.  Log on to EGO.

egosh user logon -u Admin -x Admin

           b.  Stop IBM Platform Application Center services.

egosh service stop mysql WEBGUI jobdt plc purger

c.  Check that services have stopped.

                egosh service list

6.2 Installation steps

The following steps assume IBM Platform Application Center is installed in /opt/pac.
             Replace with your actual installation directory.

             1.    Determine the location of your existing IBM Application Center installation.
#rpm -q --queryformat "%{INSTPREFIXES}\n" pcc-appcenter

             2.    As root, log on to your IBM Platform Application Center 9.1.3 host. Backup the exiting installation directory, for example:
#cp -rfp /opt/pac /opt/pac.bak

             3.    Backup database if you use local MySQL.
                    Export local IBM Platform Application Center mysql database use command:
#mysqldump -u pacuser -p pac --add-drop-table > /root/pacdata.sql

             4.    Download the fix file: pac9.1.3_standard_linux-x64.tar.Z.

             5.    Extract  pac9.1.3_standard_linux-x64.tar.Z.

             6.    As root, log on to your IBM Platform Application Center 9.1.3 host.

             7.    Set your IBM Platform Application Center environment:
                    For csh or tcsh:
% source /opt/pac/cshrc.platform
                    For sh, ksh, or bash:
$ . /opt/pac/profile.platform


             8.    Install the fix.
rpm -Uvh --prefix ${PAC_TOP} pcc-appcenter-9.1.3-240577.x86_64.rpm
Note: Replace ${PAC_TOP} with your actual installation directory.

6.3 After installation

             1.    Start IBM Platform Application Center services

                    If EGO is not enabled:

    perfadmin start all
                   pmcadmin start

        If EGO is enabled:

                   a.  Log on to EGO.

        egosh user logon -u Admin -x Admin

                   b.  Start IBM Platform Application Center services.

        egosh service start mysql WEBGUI jobdt plc purger

c.  Check that services have stopped.

                        egosh service list

             2.    Merge ${PAC_TOP}/gui/conf/pmc.conf.old into ${PAC_TOP}/gui/conf/pmc.conf according to your old configuration.

             3.    Clear your browser cache before logging into IBM Platform Application Center.
                    This is required on every browser that will access IBM Platform Application Center.
                    Otherwise, IBM Platform Application Center will not work properly.

6.4 Configuration for terminal services jobs

             1.    Configure Windows Remote Desktop Services

                    Windows 'Remote Desktop Services' (or "Terminal Services" in some older versions of Windows) must be configured correctly with enough remote desktop
                    session host licenses on each Windows server. Follow the steps below to enable Windows Remote Desktop Services:

                    a). Open "Server Manager" in Windows server host.

                    b). Right click "Roles" and click "Add Roles".

                    c). Add the role "Remote Desktop Services" (or "Terminal Services") and select "Remote Desktop Session Host" (or "Terminal Server").

                    d). Following the instrument to set the license sever, allowed users and so forth.

                    e). Right click "computer" and click "Remote settings".

                    f). Ensure the "Allow connections from computers running any version Remote Desktop (less secure)" is selected.

             2.    Configure IBM Platform LSF to submit and execute terminal services jobs

                    LSF must be configured to submit and execute terminal service jobs. Follow the steps below to enable the terminal service job feature in LSF:

                    a). Define the msts static resource.
                         Edit $LSF_CONFDIR/lsf.shared and define the msts static resource. Note that the resource name must be msts and values for the resource must be
                         exactly as shown below:
                         Begin Resource
                         RESOURCENAME TYPE INTERVAL INCREASING DESCRIPTION
                         ...
                         msts Boolean () () (Windows Terminal Server)
                         ...
                         End Resource


                    b). Add the msts resource to hosts
                         Edit $LSF_CONFDIR/lsf.cluster.cluster_name and add the msts resource to each host on which Terminal Server is installed. For example:
                         Begin Host
                         HOSTNAME model type server r1m pg tmp RESOURCES
                         ...
                         hostA ! NTX86 1 - - - (msts)
                         ...
                         End Host

                    c). (Optional) Create job starters to preserve a user's environment settings
                         You may need to create a job starter script to preserve a user's environment settings on the execution host.

                    d). Make above configuration changes take effect
                         Execute the commands: lsadmin reconfig and badmin reconfig.

• Uninstallation

7.1 Before uninstallation

           Stop all IBM Platform Application Center services:

           If EGO is not enabled:

perfadmin stop all
               pmcadmin stop

If EGO is enabled:

           a.  Log on to EGO.

egosh user logon -u Admin -x Admin

           b.  Stop IBM Platform Application Center services.

egosh service stop mysql WEBGUI jobdt plc purger

c.  Check that services have stopped.

                egosh service list

 7.2 Roll back the fix

The following steps assume IBM Platform Application Center is installed in /opt/pac.
             Replace with your actual installation directory.

             1.    Determine the location of your existing IBM Application Center installation.
#rpm -q queryformat %{INSTPREFIXES}\n pcc-appcenter

             2.    Download the RPM package for a version previous to the Fix, for example, pcc-appcenter-9.1.3-123456.x86_64.rpm.

             3.    Set your IBM Platform Application Center environment:
                    For csh or tcsh:
% source /opt/pac/cshrc.platform
                    For sh, ksh, or bash:
$ . /opt/pac/profile.platform


             4.    Install the IBM Platform Application Center RPM package, for Example:
#rpm -Uvh --prefix ${PAC_TOP} --oldpackage --noscripts pcc-appcenter-9.1.3-123456.x86_64.rpm
Note: Replace ${PAC_TOP} with your actual installation directory.

             5.    If administrator has done some customization on code, copy back the changed code from backup directory.

             6.    Start IBM Platform Application Center services

                    If EGO is not enabled:

    perfadmin start all
                   pmcadmin start

        If EGO is enabled:

                   a.  Log on to EGO.

        egosh user logon -u Admin -x Admin

                   b.  Start IBM Platform Application Center services.

        egosh service start mysql WEBGUI jobdt plc purger

c.  Check that services have stopped.

                        egosh service list

             7.    Clear your browser cache before logging into IBM Platform Application Center.
                    This is required on every browser that will access IBM Platform Application Center.
                    Otherwise, IBM Platform Application Center will not work properly.

• List of files

${PAC_TOP}/gui/conf/application/draft/Windows_Remote_Desktop/Windows_Remote_Desktop.cmd
${PAC_TOP}/gui/conf/application/draft/Windows_Remote_Desktop/Windows_Remote_Desktop.xml
${PAC_TOP}/gui/3.0/tomcat/webapps/platform/pac/job/jobInfo/jobInfo_RV.jsp
${PAC_TOP}/gui/3.0/tomcat/webapps/platform/pac/job/jobDetail.jsp
${PAC_TOP}/gui/3.0/wlp/usr/servers/platform/apps/platform.war/pac/job/js/jobDetail.js
${PAC_TOP}/gui/3.0/wlp/usr/servers/platform/apps/platform.war/pac/job/js/jobDetailForList.js
${PAC_TOP}/gui/3.0/wlp/usr/servers/platform/apps/platform.war/pac/job/jobListDetail.jsp
${PAC_TOP}/gui/3.0/tomcat/webapps/platform/WEB-INF/classes/com/platform/gui/pac/job/package.properties
${PAC_TOP}/gui/3.0/tomcat/webapps/platform/WEB-INF/classes/com/platform/gui/pac/job/package_de_DE.properties
${PAC_TOP}/gui/3.0/tomcat/webapps/platform/WEB-INF/classes/com/platform/gui/pac/job/package_ja_JP.properties
${PAC_TOP}/gui/3.0/tomcat/webapps/platform/WEB-INF/classes/com/platform/gui/pac/job/package_zh_CN.properties
${PAC_TOP}/gui/3.0/tomcat/webapps/platform/WEB-INF/classes/com/platform/gui/pac/GuiConfigurationManager.class
${PAC_TOP}/gui/3.0/tomcat/webapps/platform/WEB-INF/classes/com/platform/gui/pac/job/action/JobDetailAction.class
${PAC_TOP}/gui/3.0/tomcat/webapps/platform/WEB-INF/classes/com/platform/gui/pac/job/api/JobHelper.class
${PAC_TOP}/gui/3.0/tomcat/webapps/platform/WEB-INF/classes/com/platform/gui/pac/vnc/action/VNCConsoleAction.class
${PAC_TOP}/gui/3.0/tomcat/webapps/platform/WEB-INF/classes/com/platform/gui/pac/application/manage/internal.properties


• Copyright and trademark information

© Copyright IBM Corporation 2014

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