Tivoli Service Automation Manager 7.2.4 Fix Pack 5 - 7.2.4-TIV-TSAM-FP0005

Download Description

Table of Contents
=================================================================
1. Introduction
2. What's new in this Fix Pack
3. Contents
4. Installation Instructions
5. Errors Resolved
6. Checksum Information
7. Known Defects or Limitations, Special Notes
8. Notices and trademarks

1. Introduction
=================================================================

This Readme document describes fixes for IBM Tivoli Service Automation Manager. It provides information for you to use when installing the product.

After you install these fixes, Tivoli Service Automation Manager will be at level v7.2.4.5.

You can find out which specific components of Tivoli Service Automation Manager were updated by selecting 'System Information' from the product help menu.

The following updated items are displayed:

Service Automation Manager Configuration PMP 7.2.4.5 Build 20140515D DB Build V758-03.

Dependencies: None


Prerequisites:

You must have downloaded iFix 6 for Tivoli Provisioning Manager 7.2.1 to be available for installation. Refer to http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Provisioning+Manager&release=7.2.1.0&platform=All&function=all for a list of Tivoli Provisioning Manager 7.2.1 iFixes.
You must apply 7.2.1.0.6-TPM-0002LA available as part package at install/TPM location. Steps available in "Applying 7.2.1.0.6-TPM-0002LA" section of this readme.


================================================================
2. What's New in this Fix Pack
=================================================================

Tivoli® Service Automation Manager 7.2.4.5 is a quality fix pack that resolves a number of problems as listed in the "Errors Resolved" section.

In addition to the fixed issues, it contains the following new features:

1) Save/Restore for IBM Systems Director VMControl 2.4.2 and VMControl 2.4.3.1 (including multiple disks)

2) Root disk and additional disk via NPIV for P series IBM® Hardware Management Console (HMC)

3) Currency support: VMware ESXi 5.5 and VMware vSphere 5.5 with SUSE Linux Enterprise Server 11 SP3


=================================================================
3. Contents
=================================================================

The following items are included in this fix pack:

1) launchpad.sh
------------------------------
The root directory of the package contains the installation launchpad which
is used to install the fixpack.

2) licenses and install/license
-------------------------------
These directories contain the refreshed Tivoli Service Automation Manager licenses
which are installed using the installation launchpad.

3) install/PMP/tsam_pmp_7.2.4.5.zip
-----------------------------------
This zip package refreshes the product components that are installed with
the associated product.

4) install/tools and install/postinstall
----------------------------------------
These files contain helper tools to install the fix pack.

5) install/tcdriver
-------------------
This directory contains updates to the automation packages for Tivoli Service Automation Manager.

6) install/SRM
--------------
This directory contains the SRM LA0001, LA0007, LA0035 and LA0029 fixes and the Advanced Workflow (RBA) 7.3.0.4 fixpack.

7) install/TPM
--------------
This directory contains the TPM 7.2.1 IFIX6

8) install/files
----------------
This directory contains updates for administrative tools and configuration files
which can be used to define backends to be used by the cloud management subsystem.
For details on how to use these files consult the Tivoli Service Automation Manager Administration Guide.

=================================================================
4. Installation Instructions
=================================================================

This section guides you through the process of installing the files of this
fix pack. The steps must be followed in the order that is presented here.


Minimum disk space requirements:
-----------------------------------------------------------------

See Tivoli Service Automation Manager 7.2.4.5 Knowledge Center for disk space requirements - http://www-01.ibm.com/support/knowledgecenter/SSFG5E_7.2.4.5/com.ibm.tsam_7.2.4.5.doc/ic-homepage.html.

This fixpack must be extracted on the management server and administrative server (if on separate nodes) and occupies more than 1GB disk space when extracted. Reserve a minimum of 10 GB.



General Information and Notes:
-----------------------------------------------------------------

Installation Launchpad: This product upgrade package contains an installation launchpad. It is recommended to use the launchpad in order to install this Tivoli Service Automation Manager release or upgrade an existing Tivoli Service Automation Manager installation. The installation launchpad supports the full installation of 7.2.4.5 modes:

The installation of Tivoli Service Automation Manager 7.2.4.5 is available in the Knowledge Center (http://www-01.ibm.com/support/knowledgecenter/SSFG5E_7.2.4.5/com.ibm.tsam_7.2.4.5.doc/ic-homepage.html).

During the installation, create backups or snapshots. Note down the start/stop state of the middleware components and TPM components (that is, the deployment manager, node agent(s), MXServer,TPM engine) and make sure the system is in the same start/stop state when the backup has been completed. You can use the TPM tool $TIO_HOME/tools/tioStatus (.sh or .bat) to determine the start/stop state of the TPM components.



Before you begin the installation:
------------------------------------------------

Before you begin the installation, review the section on "Known Defects or Limitations, Special Notes" in this Readme file to learn about known unsupported scenarios and unresolved restrictions.


Preparing for Installation:
----------------------------

Updating IP address, host name, or password: When you install a fix pack or a new product, the installation program will use the host names and passwords stored in the database and the maximo.properties file. If they do not match your environment, the installation will fail. If you have changed the IP address, host name, or password of our database server or other servers, you must make the appropriate changes on the administrative server. Use the instructions in this technote to make the appropriate changes before installing - http://www-01.ibm.com/support/docview.wss?uid=swg21392272.

Unpack the file you downloaded, 7.2.4-TIV-TSAM-FP0005.zip or 7.2.4-TIV-TSAM-FP0005.tar, into a temporary directory on the administrative server and on the management server. For a Windows system, for example, C:\temp. For a Linux system, for example, /tmp. Use the checksum information in section 6 below to confirm that the download was not corrupted.

Updating from Tivoli Service Automation Manager version 7.2.2.1, 7.2.2.2, 7.2.3, 7.2.4,7.2.4.1, 7.2.4.2, 7.2.4.3, 7.2.4.4 to 7.2.4.5
-----------------------------------------------------------------

1) On the management server, start all the middleware.

a. Ensure that the middleware (including DB2, LDAP, IHS, and WAS) and base services are running.

b. Ensure that Tivoli Provisioning Manager deployment engine is stopped by running the following command as user tioadmin:
$TIO_HOME/tools/tio.sh stop -t

Verify that the script did not return any errors.

Note: This is the starting point for all subsequent steps of this upgrade scenario.
If you follow this scenario step by step, all processes are always in the correct state. In case you need to interrupt the scenario, for example, to reboot one of your systems, make sure you restart all processes exactly as described above.

2) Use the Installation Launchpad of the Tivoli Service Automation Manager Version 7.2.4.5 package along with the documented process in the online Knowledge Center (http://www-01.ibm.com/support/knowledgecenter/SSFG5E_7.2.4.5/com.ibm.tsam_7.2.4.5.doc/ic-homepage.html) to upgrade the products.


a. Start the Installation Launchpad on the administrative server and management server (if they run on different nodes). Select the language for the installation and click OK.

b. In the Installation Planning section, make sure to specify the Server Role and Installation Type (here,"Upgrade current 7.2.4 installation to 7.2.4.5") appropriately for each node.

Execute all launchpad actions as described in the Knowledge Center.


3) Migrate existing projects according to the steps described in "Migration from Tivoli Service Automation Manager 7.2.4 to 7.2.4.5" section of the Tivoli Service Automation Manager 7.2.4.5 Knowledge Center.


Performing a full installation of Tivoli Service Automation Manager Version 7.2.4.5
-----------------------------------------------------------------

In order to install Tivoli Service Automation Manager, the following packages must be available:
- Tivoli Process Automation Engine fix pack 7.1.1.9(included in TPM 7.2.1 package)
- Tivoli Service Request Manager 7.2 Service Provider Edition
- Tivoli Service Request Manager fix pack 7.2.0.1
- Tivoli Provisioning Manager 7.2.1
- Tivoli Provisioning Manager iFix 6 for 7.2.1 (7.2.1.0-IF0006).
These packages will be installed using the Installation Launchpad which comes with Tivoli Service Automation Manager Version 7.2.4.5.

To do a full installation of Tivoli Service Automation Manager 7.2.4.5, you need the Tivoli Service Automation Manager 7.2.4 package and the Tivoli Service Automation Manager 7.2.4.5 update package. If you don't want to copy the complete Tivoli Service Automation Manager 7.2.4 package to the installation machines then make sure that at least the following file is available on the machine where the installation launchpad has been started: tsam_key_7.2.4.zip.

Start the Installation Launchpad inside the Tivoli Service Automation Manager 7.2.4.5 installation set and perform the installation according to the documented process in Tivoli Service Automation Manager 7.2.4.5 Knowledge Center - http://www-01.ibm.com/support/knowledgecenter/SSFG5E_7.2.4.5/com.ibm.tsam_7.2.4.5.doc/ic-homepage.html.

Start the Installation Launchpad on the administrative server and management server (if they run on different nodes). Select the language for the installation on the main panel. In the Installation Planning section make sure to specify the Server Role and Installation Type (here: "Full Installation of 7.2.4.5") appropriate for each node. In the Installation Files section specify the paths as requested and click "Verify the locations specified above". Execute all launchpad actions as described in the Tivoli Service Automation Manager 7.2.4.5 knowledge center.


Applying 7.2.1.0.6-TPM-0002LA
-----------------------------------------------------------------
Limited Availability patch details:

This Limited Availability fixes issue regarding the following PMR(s): No PMR

Important Note: This Limited Availability patch is applicable only on top of:
------> IBM Tivoli Provisioning Manager(R), version: 7.2.1.0.6

Prerequisites:

Ensure your Tivoli Provisioning Manager(R) system is at required level specified in the previous point.

DO NOT apply this patch on any Tivoli Provisioning Manager(R) server that is lower or above than Tivoli Provisioning Manager(R) required level, results cannot be guaranteed.

Instructions:
1) On your non-production TPM server
Extract the provided tar file in
- Unix: $TIO_HOME/properties/version
- Windows: %TIO_HOME%\properties\version
2) Change the permission for all folders and files of 7.2.1.0.6-TPM-0002LA
- Unix: chmod -R 755 7.2.1.0.6-TPM-0002LA/
3) Change owner for all folder and files of 7.2.1.0.6-TPM-0002LA
- Unix: chown -R tioadmin:tioadmin 7.2.1.0.6-TPM-0002LA/
4.Follow the instructions given in the readme file to run the setup for 7.2.1.0.6-TPM-0002LA Limited Availability Patch


Post Installation Steps
--------------------------------

After successfully installing Tivoli Service Automation Manager Version 7.2.4.5, if “from=” directive parameter is present in the end point key, run the following commands :

cd /home/tioadmin
vi endpointkeys file
remove from=<hostname> entry


=================================================================
5. Errors Resolved
=================================================================

The list of APARs that are resolved in this release:

IV51409 - Issues with VMCONTROL provisioned LPARs and multiple NICs

IV52430 - VMware Storage Resiliency forces provisioning even when disk don't have the requested free space

IV53353 - Simple SRM create users failure when LDAP structure has OU=USER

IV54283 - Resource Consumption Tab showing incorrect values for resources CPU, memory and disk

IV54316 - Clone Server for Windows doesn't work

IV54329 - Cloud.overcommitfactor.disk for additional disks when setting "Place Disk on SingleStorage" option is fixed

IV54679 - Extension APIs to extend AdditionalDiskPanel for Create Project with VMware Servers, Add VMware Servers and Add Additional Disk on VMware Server

IV55181 - Modifying an additional disk that is attached to a Linux VM is fixed

IV55407 - Insufficient resources due to "vm-fs-" prefix in the ODSDS_vstXXXXX virtual server templates

IV55424 - The additional disk feature is restoring to wrong ESX datastore

IV55703 - Refresh server in SSUI under manage servers increases disk resources

IV55713 - Service Automation Request displays Project name instead of server name for Add/Modify/Remove additional disk issue is fixed

IV55722 - TSAM 7.2.4.1 with extension for IBM SYSTEMS DIRECTOR VMCONTROL, upgrade to TSAM 7.2.4.4 is not supported

IV55821 - Documentation for manual steps needed for ITM on a Cloned Server

IV55856 - Documentation on Drive Letter changes for additional Disk during Clone

IV55859 - Documentation update for Template Creation steps for provisioning with non-root Linux templates

IV55922 - AIX LPAR extend additional disk not working

IV56000 - VMware overcommit factor reset by template discovery

IV56160 - Branding the Self Service Interface login doesn't work

IV56215 - Add additional disk does not execute

IV58554 - VMWare connection reports invalid

IV58562 - Migrating Virtual Servers with additional disks using WMT fails during import


=================================================================
6. Checksum Information
=================================================================

Use this information to verify that you have successfully downloaded
and unpacked the files in this update package.

File name MD5 checksum
------------------------------------------------------------------
*7.2.4-TIV-TSAM-FP0005.tar
3c0623dfeec595601be3ba62db6ab784

*7.2.4-TIV-TSAM-FP0005.zip
6389ec3669a25846918ef3d64f48c70b

Note that these are sample checksum values. For the right values, see the online readme.

=================================================================
7. Known Defects or Limitations, Special Notes
=================================================================

Known Defects or Limitations
------------------------------------------

1)After the installation of Tivoli Service Automation Manager, if you do not find the tio key, update the credentials of Tivoli Provisioning Manager computer entry as follows:

1. Start Tivoli Provisioning Manager if necessary: tio.sh start
2. In the administrative user interface ( https://:9443/maximo/ui), enter the credentials (For example, maxadmin/maxadmin).
3. Edit the credentials (master) for the SSH server.
4. Click Go To > Deployment > Provisioning Computers, and press Enter to populate the table with a list of computers.
5. Select your Tivoli Provisioning Manager server from list.
6. Click the Credentials tab, and expand the SSH-Server to display the details.
7. In Password Credentials, expand the master search key to display the details.
8. If necessary, enter the credentials, user name, and password for your Tivoli Provisioning Manager administrative user (tioadmin).
9. Save the changes.
10. Edit the credentials (master) for the SSH client. Add "defaultPassword" as the SSH-Client password credential and "default" as the SSH-Client RSA credential.
11. Expand SSH-Client to display the details.
12. In Password Credentials, expand the master search key to display the details.
13. Enter the credentials, user name and password, for your Tivoli Provisioning Manager administrative user (tioadmin), and save the changes.
14. Expand SSH-Client to display the details.
15. Click New Password Credential, and enter the following details:
1. In Search Key, enter defaultPassword.
2. In User Name, enter root.
16. In Password, enter your root user's password for this Tivoli Provisioning Manager server, and reconfirm it.
17. Click New RSA Credential, and enter the following details:
1. Search Key, enter default.
2. User Name, type root.
3. Passphrase and Confirm Passphrase, enter the phrase you have defined in the task, Configuring the SSH key in the post-installation steps.
18. Save the changes.
19. Expand SSH-Client to display the details.
20. In the Password Credentials section, select the defaultPassword search key record in the table to set it as the default search key.
21. Save the changes.
22. Edit credential of SCP-Client and add "defaultPassword" as the SCP-Client Password Credential, and add "default" as the SCP-Client RSA Credential.
23. Expand SCP-Client.
24. Click New Password Credential, and enter the following details:
1. In Search Key, type defaultPassword.
2. In User Name, type root.
25. In Password, enter your root user's password for this Tivoli Provisioning Manager server, and reconfirm it.
26. Click New RSA Credential, and enter the following details:
1. In Search Key, enter default.
2. In User Name, enter root
3. In Passphrase and Confirm Passphrase, enter the phrase you defined in the task, Configuring the SSH key in the post-installation steps.
27. Save the changes.
28. In the Password Credentials section, select the defaultPassword search key record in the table to set it as the default search key.
29. Save the changes.
30. Set tiocredkey on the credentials of the Tivoli Provisioning Manager provisioning system.
31. Click Add Credentials > New Service Access Point.
32. In Service Access Point, enter tiocredkey.
33. Select Authentication.
34. In the RSA Credentials section, click New RSA Credential, and enter the following details:
1. In Search Key, enter default.
2. In User Name, type root.
3. In Passphrase and Confirm Passphrase, enter the phrase you defined in the task, Configuring the SSH key in the post-installation steps.
35. Save the changes.

2) When you install Tivoli Service Automation Manager for the first time, the tags are not available in Tools and System Health Check. However, tags are available in this path on the management server - /opt/IBM/tsam/properties/Version. As a work around, exit the launchpad and launch it again after the completion of the installation.

3) If you are installing Tivoli Service Automation Manager for the first time, installation of Cloud Management component fails with a SOAP exception. To resolve the exception, do the following:

1. Stop and restart middleware
2. Exit launchpad and relaunch it
3. Run the script from the point of failure.

4) When you install Tivoli Service Automation Manager for the first time, COPCOM608E error might occur in the configuration of cloud management component step. To resolve the error, do the following:

1. Stop and start WebSphere Application Server and Tivoli Provisioning Manager
2. Restart script and choose option 2.

5) ITMSyncCron is introduced for resource KPI performance issue and it is inactive by default. Enable/activate this cron task if you want to use the performance feature for IBM Tivoli Monitoring. In the Tivoli Service Automation Manager 7.2.4.5 knowledge center, see Configuring Tivoli Service Automation Manager > Integrating Tivoli Service Automation Manager with other Tivoli products > Integrating Tivoli Monitoring > Synchronizing data between Tivoli Monitoring and Tivoli Service Automation manager.

6)While defining an additional disk on the VSCSI enabled Resource Pool for VMControl hypervisor, a warning message may get displayed - "CTJZE1108W: The Virtual Server will be restarted while adding NPIV based Additional Disk."

7) If the warning Value limit set on the storage quota is reached, there are no warning messages displayed on the UI or the email notification sent to customer.

8) When the environment grows, the time to register a single new image in Simple SRM takes a lot of time to complete. If there are more images per cluster, then it affects the performance. To resolve the issue, do this procedure:

1.Create pmrdp.register.image.optimized global property
2.Set the value to True.
3.Save changes and do a live refresh.

9) An error occurs in Create Project with POWER LPAR Servers via IBM Systems Director VMControl, Add POWER LPAR Servers via IBM Systems Director VMControl, and Add Additional Disk on POWER LPAR Server via IBM Systems Director VMControl.

10) A VMControl NPIV project gets created successfully but additional disk request fails with "Auth Cancel" error. In addition, the management of virtual server (LPAR) from Tivoli Service Automation Manager Management Server might work. To resolve the issue, when you register an image or submit provisioning request, select a minimum amount of 2 GB memory for the Virtual Server (LPAR).

11) In case of Power LPAR via IBM Systems Director VMControl, the image restore is not available when you change server details, such as memory and processor.

12) Manual configuration steps to enable ITM correctly on Manual configuration steps to enable ITM cloned server. See Tivoli Service Automation Manager Installation and Administration Guide > Manually configuring the IBM Tivoli Monitoring agent set up for VMware clone section of Chapter 3 Configuring Tivoli Service Automation Manager. Also, see http://www-01.ibm.com/support/docview.wss?uid=swg21441836.

13) The restore of saved image function is not applicable for additional disks that were provisioned or added to servers during the earlier version releases of Tivoli Service Automation Manager.

14) Upgrade path to IBM Tivoli Service Automation manager and support for VMControl V2.4.2 extension.

15) If you have a project that has servers of the type VMware and LPARs, then on the modify resources screen of Simple SRM, you will notice that the disk is also modifiable for an LPAR. As this is not a supported operation, do not try to modify the disk for an LPAR.

16) The "Discover VMControl storage pools" does not run as expected from Tivoli Service Automation Manager Administrative UI > Cloud Storage pool.

17) If the configured SMTP mail server is down, the service requests do not progress and fail whenever you try any of the Tivoli Service Automation Manager offering.

18) When an ESX host is in maintenance mode on the Virtual Center that has more than one ESX hosts, the create project request fails with this error message - "The operation is not allowed in the current state of the host". The expected behavior is that the create project request must provision on any other available ESX host. To avoid this error, during provisioning, ensure that no ESX host on the Virtual Center is in maintenance mode.

19) As a Tivoli Service Automation Manager user, you might encounter issues when you deploy an image (Golden Master or Saved). The issue is related to collecting inventory in VMControl. According to VMControl documentation, the inventory collection is needed for “hosts/{hostOID}/virtualServers/customization” REST API only if HTTP status code is 425 (425 - NOT READY). For more information, see http://pic.dhe.ibm.com/infocenter/director/devsdk/topic/com.ibm.vmcontrol.ws.24.doc/html/resources/vmc2_2_api_hosts_oid_virtual_servers_customization.html. However, in some scenarios, the status code can also be 500 (500 - IBM Systems Director encountered an unexpected condition which prevented it from processing the request). The code 500 explanation signifies a VMControl error. Contact VMControl team about this 'customization' VMC API error.

20) After you upgrade from previous versions, the Backup directory name in NIM discovery for server pool is blank. As a work around to populate the Backup directory name value, reassign the NIM boot server name value using the redirection ">>".

21) In the back end, do not have 2 disks with same PVID. If there exists a duplicate PVID, this error occurs - "COPCOM123E A shell command error occurred: Exit code=1, Error stream="", Output stream="HSCL2970 The IOServer command has failed because of the following reason: 0 rc=4".

22) When you upgrade a version that is configured for system P to Tivoli Service Automation Manager 7.2.4.5, the server pool can be in disabled mode. To resolve the issue, do this procedure:

1. In the NIM discovery tab, click >> for NIM boot server Name.
2. Reassign the boot server.
3. Enable the server pool.

23) The enable PMRDPCLSWS_MONITORING for Create Project with VMware servers gets revoked after you upgrade the Tivoli Service Automation Manager to a higher version. You must manually enable PMRDPCLSWS_MONITORING for Create Project with VMware servers again. See Tivoli Service Automation Manager 7.2.4.5 knowledge center, see Tivoli Service Automation Manager 7.2.4.5 knowledge center > Configuring Tivoli Service Automation Manager > Integrating Tivoli Service Automation Manager with other Tivoli products > Integrating Tivoli Monitoring > Enabling the PMRDPCLSWS_MONITORING for Create Project with VMware servers.

24) For VMControl, whenever you create a saved image for LPARs, remember that the support is not extended for NIM based images.

25)The SSH and SCP credentials are added to VMControl server computer entry after you run VMControl discovery. Check that the SSH and SCP credentials are created post VMControl discovery. If not created, then add them manually:

1. In Tivoli Service Automation Manager administrative UI, click Go To > Provisioning Computers > Select VMControl Server Entry
2. Open Credentials tab
3. Click Add Credentials and select SSH and SCP option.
4. Select Create Password Credential.
5. Enter “master” in search key.
6. Enter user credentials (user Name, Password, and Confirm Password).
7. Click OK and save the changes.

26) General limitations in Save/Restore for VMControl:

1. NIM based images cannot be captured.
2. No capacity check for SCS repository.
3. No disk, CPU, or memory slice check during provisioning of LPAR.
4. Toggle of NPIV flag on Server Pool is not recommended.
5. Create\Capture\Restore of LPAR with root disk as vSCSI, and data disk as NPIV is not supported.
6. Register images rounds off disk size and Create Server Image does not. Hence, discrepancy can be seen on disk size.

27) For VMControl hypervisor, when you create a project using a saved image and later decommission it by saving its image, a saved image failed error message and inbox assignment is created - "COPDEX172E The /server[@id=$virtualServerId]/sap[@defaultcredentialsid != "<null>" and @appprotocolid=$AppProtocolId and @host="Y"]/credentials variable is a single value variable. An array value cannot be assigned to a single valuable variable."

As a work around, do this procedure:

1. Navigate to Provision Computers > Select virtual sever that was selected for decommissioning from its project.
2. Navigate to Credentials tab.
3. Expand the SSH Service Access Point details.
4. Delete additional entry created for master search key and save the changes.
5. Navigate to Start Center and then Go To > Deployment > OS Management > Images.
6. Select the image name for which the save image operation failed.
7. Use the Delete Image option to remove the selected image
8. To action the inbox assignment, select "Continue Management Plan by re-exeuting failed workflow" option.

Special Notes:
--------------------

1) Note to customers using IBM Systems Director VMControl as virtualization technology: We strongly suggest to run IBM Systems Director VMControl in an english-only environment. When you create a project with IBM Systems Director VMControl, images with multiple disks are not supported.

2) In server pool configuration, the import of VMControl hypervisor SSL certificate into the WebSphere certificate store is automated.

3) Whenever you use NPIV enabled resource pool for VMControl 2.4.3.1 Hypervisor, ensure that you have installed VMControl 2.4.3.1 with LA 64.

4) Whenever you change the server specifications, save the image of the server such that it can be restored in the future. The server specifications include CPU, RAM, Disk Size, and Additional Disk Size.

Deficiencies:
-------------

1) If you encounter the following error during the installation of Tivoli Provisioning Manager refresh pack: "./tpm_core/unixCoreCompUpgrade.sh: line 1240: /tmp/CAS_Update/setuplinux390.bin: No such file or directory. Error while installing Agent Manager Upgrade. See logs in /opt/IBM/AgentManager/logs for details.". Refer to the following technote for a solution: http://www-01.ibm.com/support/docview.wss?uid=swg21638222.
On AIX on the 'Install software' panel additional software is not displayed for selection even the requirements and capabilities are correct when it should be installed on a provisioned AIX server. The software module (the operating system) in the software stack of the master image has to be assigned to the customer who should be able to install additional software on the provisioned server.

1. Goto > IT infrastructure > Image library > Master images
2. Select the AIX master image which should get additional software
3. Select the software stack of the master image > goto software stacks
4. Select the software module (e.g. AIX 6.1)
5. Select Variables tab
6. Click new row and enter variable exposetotivsam with value 1
7. Click new row and enter variable swType with value OS
8. Click save
9. Goto > Service Automation > Customization > Cloud Customer Administration
10. Select the customer who should be able to install the additional software on a server which was provisioned from this masterimage
11. Select Software Modules tab
12. Click select software product
13. Select the software module which got the additional properties in the steps above and click assign software module

2) During installation of DB2 on windows, the following error message is created during DB2 installation: COPDEX137E There is no provisioning workflow that implements the "OperatingSystem.AddUser" logical management operation associated with object "VMware Template -- win2008r2x64bit."

3) During DB2 installation the TPM tc-driver requires to have a LDO implementation for OperatingSystem.AddUser and OperatingSystem.AddUserToGroup. The devicemodel 'Cloud Windows Operating System' used by Tivoli Service Automation Manager doesn't have this LDO implementations. Therefore the two implementations Windows_LocalUser_AddUserToGroup and Windows_LocalUser_Add for these LDOs have to be assigned manually to the software stack of the windows master image. Steps to execute:

1. Goto > IT infrastructure > Image Library > Master Images.
2. Select the windows master image.
3. Select the software stack of the master image > goto software stacks.
4. Select Workflow tab.
5. Press 'assign provisioning workflow'.
6. Enter 'Windows_LocalUser' in the workflow name field.
7. Select Windows_LocalUser_AddUserToGroup and Windows_LocalUser_Add.
8. Click OK.
9. Click Save.

4) Some data elements of the Cloud Server Pool Administration and Cloud Storage Pool Administration applications are not translated.
LPAR(s) Provisioned to a processor pool do not support the modify server resources offering. Execution of this offering will fail with error message "CTJZH0100E - The Service Request is not consistent. Processing of the Service Request is cancelled".
Although Windows XP is not supported by TSAM, some functionality might still work. Anyway, there is a known issue with non-Administrator use with Windows XP, which might not work.

5) The following deficiencies have been observed on selected non-English systems:
Problems have been reported with the Process Solution Installer (PSI)on administrative servers running Windows Vista. Installation of this fix pack may be affected. Use of Windows Vista in this case is discouraged.
First and last names should be reversed for Asian countries (PHYP1541TPY). For Asian countries, the customary order is last name, first name. The SimpleSRM UI uses separate input fields, but the input field for "first name" is always displayed before the input field for "last name".
In order to provision Russian, Spanish, Italian, or French Windows 2008 R2 or Windows 7 virtual images, do the following (PT721605WSF):
If the built-in "Administrator" user and "Administrators" Group in non-English Windows image templates is localized, then rename them to English "Administrator" user and "Administrators" (languages affected: Russian, French, Italian, Spanish and a couple of others). Add the localized "Administrator" user and "Administrators " group back to the template and make this localized user also a part of English Administrator group. Copy the endpoint_keys file from Tivoli Service Automation Manager management server (that is, present in /home/tioadmin/endpoint_keys) to the c:/temp folder created on the template. Add a new template parameter "endpoint-keys-present" and give it value "true" in the discovered software stack of the image template:

1. Click Go To > IT Infrastructure > Software Catalog > Software Stacks
2. Select the VMware template from the list, for example, MyVMwareTemplate
3. Select this default template definition to display the details.
4. In the Template Parameters section, add a new parameter named endpoint-keys-present.
5. Assign the value "true" in the Value field.

=================================================================
8. Notices and Trademarks
=================================================================
Notices

This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document
in other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that
IBM product, program, or service may be used. Any functionally equivalent
product, program, or service that does not infringe any IBM intellectual
vproperty right may be used instead. However, it is the user's responsibility to
evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing,
to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express
or implied warranties in certain transactions, therefore, this statement may not
apply to you.

This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those
Web sites. The materials at those Web sites are not part of the materials for
this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.

The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer
Agreement, IBM International Program License Agreement or any equivalent
agreement between us.

Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available
sources. IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change
or withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include
the names of individuals, companies, brands, and products. All of these names
are fictitious and any similarity to the names and addresses used by an actual
business enterprise is entirely coincidental.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.

Trademarks

The following terms are trademarks of International Business Machines
Corporation in the United States, other countries, or both:

AIX, DB2, IBM, Maximo, Service Request Manager, System p, Tivoli, WebSphere

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.
Download package