IBM Tivoli Intelligent Orchestrator 5.1.1.2 readme file for UNIX or Linux

Copyright statement

© Copyright IBM® Corporation 2008. All rights reserved. May only be used pursuant to a Tivoli® Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyright notice.

No other rights under copyright are granted without prior written permission of IBM Corporation. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

About this fix pack

This fix pack only applies to a regular installation of Tivoli Intelligent Orchestrator (an installation with IBM WebSphere® Application Server as the application server). Tivoli Intelligent Orchestrator must be at version 5.1.1.1. A fix pack is not available for a Fast Start installation.

Enhancements/changes included in this fix pack

The enhancements and changes included in this fix pack are:

Red Hat Linux 5 TCA endpoint support

Included in this release is basic Red Hat Linux® 5 (RHEL 5) support for the Tivoli common agent on the endpoint. RHEL 5 is not supported on depots or the management console. This support does not include patch management or new security enhancements provided in Red Hat Linux 5.

Pause/resume distributions

You can now define maintenance windows. These are defined periods of time within which data downloads using Dynamic Content Delivery (DCD) will be enabled or paused. The maintenance windows are specified in a text file that follows the iCalendar syntax (RFC2445). The file containing the information about maintenance windows must be installed in the <agent installation directory>/runtime/agent/subagents directory, and must be named maintenance.ics. To install the schedule into the agent you can use the typical Software Package Block (SPB) distributions. Use the SPB processing to install the schedule file maintenance.ics into the previously mentioned directory. The SPB that contains the maintenance calendar is created using the Software Package Editor (SPE). To facilitate this process you can use the sample software package description (SPD) file found on the provisioning server after the fix pack is installed. The SPD can be found in $TIO_HOME/repository/tivoli/TCA/schedule.spd. The maintenance.ics file can be created using a text editor or any iCalendar-compliant calendar file creation tool.

The software module definition for the maintenance schedule SPB should have a software capability defined of type TIVOLI_COMMON_AGENT, name operational.schedule and value maintenance.window. When you install the software module, this capability is interpreted by Tivoli Intelligent Orchestrator to be a "system" task. As a result, the priority of the Scalable Distribution Infrastructure (SDI) job is decreased, downgraded to run - in the background so that maintenance windows are handled with a higher preference. After the SPB is installed, the new file is in the endpoint and is ready to be used by the agent. The agent includes a scheduler that reads and interprets the maintenance.ics file. This scheduler scans the maintenance.ics file every 20 seconds to check whether it has been updated. If it was updated then the scheduler loads the maintenance.ics file, then processes it. If there are any issues in processing the maintenance.ics file such as syntax errors, the scheduler defaults to having no service windows. Updating the last modified time stamp on the maintenance.ics file causes the scheduler to load and process the file, regardless of its contents. In this implementation of maintenance windows, only the DCD file transfers (downloads) are being managed, so only job steps related to file transfers from DCD will be paused and resumed by the scheduler as determined by the maintenance schedule.

The maintenance.ics file format is compliant with the syntax specified in the RFC 2445 document. Only a subset of the RFC is used. The following section demonstrates the supported tags.

maintenance.ics file format

BEGIN:VCALENDAR
DESCRIPTION:Sample 10pm to 5am maintenance window
PRODID:IBM
VERSION:1.0
BEGIN:VTIMEZONE
TZID:EST
END:VTIMEZONE

BEGIN:VEVENT
DESCRIPTION:Sample 10pm to midnight window
DTSTART:20080901T220000
DTEND:20080901T235959
RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR,SA,SU;
END:VEVENT

BEGIN:VEVENT
DESCRIPTION:midnight to 5am window
DTSTART:20080901T000000
DTEND:20080901T050000
RRULE:FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR,SA,SU;
END:VEVENT

END:VCALENDAR

Extension mechanism

Time Scheduling Services (TSS) uses the standard vCalendar extension mechanism. Custom properties have a standard prefix, X-; that are processed by specific applications and ignored by others.

Using this extension, some AvailabilityCalendar properties that are not standard in vCalendar can be set using X- properties.

In order to maintain compatibility with the vCalendar format, the X- properties are not required or mandatory. If they are not set, they will be automatically set by the AvailabilityCalendarFactory option to a default value.

Formal Definition

A TSS vCalendar definition consists of a header followed by a sequence of validity time intervals mapped into VEVENT components.

The following vCalendar properties are supported :

The VTIMEZONE is a vCalendar component. Only the TZID property is supported.

PRODID

VERSION

UID

DESCRIPTION

CALSCALE

METHOD

VTIMEZONE

X-CALVALIDFROM

X-CALVALIDTO

X-CALAVAILABILITYVALUE

X-CALFREESUNDAY

X-CALFREESATURDAY

X-CALTIMEINTERVAL

After the header, you must specify a sequence of validity time intervals. Note that you must specify a validity time interval.

The following validity time interval attributes are available:

UID

DESCRIPTION

DTSTART

DTEND

RRULE

RDATE

EXDATE

RRULE and RDATE are mutually exclusive.

TSS vCalendar only supports events that do not span across different days. In other words, DTSTART and DTEND must belong to the same day.

The following code is an example of a maintenance.ics file:

 	BEGIN:VCALENDAR
 	BEGIN:VEVENT
 	DTSTART:20080901T100000
 	DTEND:20080901T140000
 	RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=MO;FR; UNTIL=20200901T14000;
 	END:VEVENT
 	END:VCALENDAR

Custom inventory scans

Custom inventory extensions are used to extend the data model inventory schema with additional server attributes. The endpoint scanning system retrieves and processes these extended attributes generated by endpoint scripts, making them accessible for queries (for example, for dynamically grouping endpoints) and reports.

To create a custom inventory extension, first create custom tables with the columns needed to hold the collected data. The custom tables must conform to the following rules:

• A column named discovery_id is mandatory and a foreign key to discovery table must be set.
• A column named server_id is mandatory and a foreign key to server table must be set.

The following rules are suggested in the custom table creation:

• discovery_id column as not nullable.
• server_id column as not nullable.
• cascade delete constraints on server_id and discovery_id

For example:

CREATE TABLE IPCONFIG(
parameter VARCHAR(255),
endpoint VARCHAR(255),
network_interface VARCHAR(255),
value VARCHAR(255)
);
ALTER TABLE IPCONFIG ADD COLUMN SERVER_ID BIGINT NOT NULL;
ALTER TABLE IPCONFIG ADD COLUMN DISCOVERY_ID BIGINT NOT NULL;
ALTER TABLE IPCONFIG ADD FOREIGN KEY (discovery_id) REFERENCES DISCOVERY(discovery_id) on DELETE CASCADE;
ALTER TABLE IPCONFIG ADD FOREIGN KEY (server_id) REFERENCES SERVER(server_id)on DELETE CASCADE;
COMMIT;

The extensions are managed from a command line application found at:

$TIO_HOME/tools/inventoryExtension.[sh(unix) | cmd(windows)].

• inventoryExtension create -p properties_file [-r yes|no].
  • This command creates a discovery configuration that contains the extension and, an optional report. If you want a custom report, specify -r to create a custom report. The report created automatically selects all of the columns for all of the custom tables. This command creates the inventory extension information about the provisioning database and also checks if the user created a custom table according to the database schema. Specify the full path to the properties_file.
  The following code represents a sample properties file:

  ##name of the extension
  extName=IPCONFIG_Test
  #description of the extension
  extDescription=UNIT TEST
  
  #Custom Tables Names
  TABLE_1.NAME=ipconfig
  
  #files for the AIX platform
  AIX=yes
  pre_aix=/home/test/prescript.pl
  out_aix=/home/test/ipconfig1.mif
  post_aix=/home/test/postscript.pl
  
  #files for the HPUX platform
  HPUX=yes
  pre_hpux=/home/test/prescript.sh
  out_hpux=/home/test/ipconfig1.mif
  post_hpux=/home/test/postscript.sh
  
  #files for the Solaris platform
  SOLARIS=yes
  pre_solaris=/export/home/test/prescript.sh
  out_solaris=/export/home/test/ipconfig1.mif
  post_solaris=/export/home/test/postscript.sh
  
  #files for the Linux platform red hat 4 or 5
  LINUX=yes
  pre_linux=/home/test/prescript.sh
  out_linux=/home/test/ipconfig1.mif
  post_linux=/home/test/postscript.sh
  
  #files for the windows platform win xp
  WINDOWS=yes
  pre_windows=c:\\test\\prescript.windows.bat
  out_windows=c:\\test\\ipconfig1.windows1.mif
  post_windows=c:\\test\\postscript.windows.bat

  The extension name is a required parameter, if the extension description is not passed in, the extension is created with no description.

  The following restrictions apply to the table section

  • the numbering following the TABLE tag must start from 1 and must be sequential.

  The fully qualified path of the pre- and post-script files on the endpoints are specified in the properties file. The generated output file location is specified and can be an XML or MIF file.

• inventoryExtension list [-e extension name]
  • This command lists all of the extensions registered to Tivoli Intelligent Orchestrator, and if an extension is specified, gives information about all scripts for each platform. If you do not specify any options, all of the extensions will be listed using this command. Specifying the -e option will provide detailed information about the given extension and will display pre-script and post-script files for each platform. The extension name is specified in the properties file during the create command.
• inventoryExtension delete -n extension name
  • The delete command removes the inventory extension, the generated discovery configuration and report for that extension.
• inventoryExtension help
  • Displays the inventoryExtension command usage.

The pre- or post-script files can be used to gather custom data and are specified in the properties file that is run on the target endpoint. The pre-script file generates an output file in either the XML or MIF file format that describes the information used to complete the custom tables. Following are examples of pre-script and post-script files, and XML and MIF output files that can be generated.

Sample Pre-script:

#!/bin/bash
echo copying
cp  /tmp/ipconfig.mif.backup /tmp/ipconfig.mif
exit 0;

Sample Post-script:

#!/bin/bash
echo deleting backup
# rm /tmp/ipconfig.mif.backup
exit 0;

Sample XML output:

<custom-data>
   	<custom-table name="ipconfig">
				<string-column name="Parameter" length="255" value="parameter1" />
				<string-column name="endpoint" length="255" value="endpoint_test" /> 
				<string-column name="network_interface" length="255" value="eth0" /> 	
				<string-column name="value" length="255" value="9.168.100.80" />
 		</custom-table>
</custom-data>
  

Sample MIF output:

Start Component
     Name = "ipconfig.mif"
     Start Group
				id = 1                           
                Name = "ipconfig"
                Class = "test_class"
                
                Start Attribute
                        Name = "Parameter"
                        Id = 1
                        Type = String(255)
                        value = "parameter1"
                End Attribute
                
                Start Attribute
                        Name = "endpoint"
                        Id = 2
                        Type = String(255)
                        value = "endpoint_test"
                End Attribute
                
                Start Attribute
                        Name = "network_interface"
                        Id = 3
                        Type = String(255)
                        value = "eth0"
                End Attribute
                
                Start Attribute
                        Name = "value"
                        Id = 4
                        Type = String(255)
                        value = "9.168.100.80"
                End Attribute
    End Group
End Component

The inventory extension defined is also used in the discovery configuration. Custom inventory scans can be configured to run using the discovery configuration UI. Custom inventory extensions can be selected in the user interface. The deployment engine can also be used to run an agentless extended scan.

In order to create and run an inventory extension follow these steps :

1. Design and create custom tables.
2. Create the pre-script files that will generate an XML or MIF output file and the post-script files that will clean up at the end of the scan.
3. Deploy the scripts on the endpoints.
4. Run the generated discovery configuration against the targets.
5. Run the generated custom report associated with this scan to view the custom information.
   Note:
   The generated report can be copied or edited to make it work with the created discovery configuration. If more than one extension is active and sharing a common custom table or set of custom tables, the generated reports will show multiple rows, one for each server and discovery that executes. If it is desirable to eliminate these rows, each generated discovery report should filter rows not associated with that particular discovery.

To run multiple Custom Inventory Extensions that have been created from the command line under the same Discovery instance:

1. Go to Discovery Configurations >Discovery extension instance > Properties.
2. On the Second Page, Discovery Parameters > Inventory Extension add the value <Extension Name>.
3. Click Finish.

For the Report:

1. Copy the Original Reports.
2. On the last page of the cloned Reports 'Report Summary' change the discovery_last_scan.discovery_id to the updated Discovery instance ID the extension is running under.
3. Click Finish.

Multiple Network Interface Card (NIC)

Endpoints with multiple NICs can now be correctly managed from Tivoli Intelligent Orchestrator. Configure the appropriate host name for that NIC and the route to be used to the provisioning server. When the common agent is installed, Tivoli Intelligent Orchestrator will use the IP address used by the common agent to register itself as the management IP address, and use the defined host name as seen by the endpoint on the management IP as the computer name.

Network Address Translation support

This feature provides an option for agent discovery configurations (both 'IBM Tivoli Agent Manager Discovery' and 'IBM Tivoli Agent Manager Discovery Device' discovery configurations) that will use the observed IP address as the management IP for each endpoint. When this parameter is set the agent discovery will not attempt to verify that the observed management IP is in the list of supported IPs for that endpoint, as in the Network Address Translation (NAT) case that IP would not be present.

This will ensure that any operations initiated using the deployment engine will discover the endpoint correctly using the NAT addressing.

The basic flow of events is as follows:

1. Log on to the Web interface.
2. Select Inventory -> Manager Discovery -> Discovery Configurations
3. From the list of discovery configurations, select 'IBM Tivoli Agent Manager Discovery' and 'IBM Tivoli Agent Manager Discovery Device'
4. Enable the NAT support by setting the 'Use Observed IP as network management IP' property to true.
5. Run the agent manager discovery.
6. The endpoints will be created in the data model and the observed IP address that was used by the endpoint to contact the server will be set as the management IP address.

Now the user will be able to run the workflow using the deployment engine on the endpoints discovered using the NAT addressing.

Improvement to the common agent installation and upgrade process

The agent upgrade process now leverages the Software Infrastructure Distribution and the Software Installation Engine (SID/SIE) and therefore provides a more robust mechanism for agent upgrade and installation. The SPBHandler subagent is required on the endpoint.

Tivoli common agent (TCA) file permissions fix

The agent installer will now install all of its files as read-only.

TotalStorage Productivity Center (TPC) Integration

There are several components of this integration: Tivoli Intelligent Orchestrator, TotalStorage® Productivity Center Standard Edition and the IBMTPC automation package.

The features included in this release are :

1. Run TPC discovery repeatedly without destroying data model objects and relationships.
2. Improve the performance for discovery of storage information.
3. Run TPC discovery from multiple TPC management servers from which you want to retrieve storage information.

The IBMTPC automation package also provides workflows and Java™ helpers that enable Tivoli Intelligent Orchestrator to use the basic storage device functions provided by Total Storage Productivity Center.

Install IBMTPC automation package

To install the tcdriver, perform the following steps:

1. Shut down Tivoli Intelligent Orchestrator.
2. Place the tcdriver file in the %TIO_HOME%/ drivers directory.
3. For Windows®, run the following command:

   %TIO_HOME%/tools/tc-driver-manager.cmd forceInstallDriver IBMTPC

   For Unix, run the following command:

   $TIO_HOME/tools/tc-driver-manager.sh forceInstallDriver IBMTPC

4. Restart Tivoli Intelligent Orchestrator after the tcdriver is installed.

To configure and initialize your system, follow these steps:

1. Install the IBMTPC automation package before running the configuration steps provided below.
2. Run the TPC_DefineTPCServer workflow on each TPC server in your environment that you intend to manage using Tivoli Intelligent Orchestrator. To do this, on the Web interface:
   1. Click Automation -> Workflow. The TotalStorage Productivity Center workflows will be listed.
   2. Select TPC_DefineTPCServer.
   3. Select Execute -> Run to run the TPC_DefineTPCServer workflow.
   4. Enter the host, port, user name, and password of the computer where TotalStorage Productivity Center is installed. Note that the default port number for TPC and Tivoli Intelligent Orchestrator communications is 9500.
   5. Click Run.
3. Using the TotalStorage Productivity Center user interface, run the necessary device discoveries, scans, and probes to ensure that the TotalStorage Productivity Center is aware of all SAN elements.
4. Run TPC_Discovery to initialize the Tivoli Intelligent Orchestrator data model with SAN information. This process loads the SAN Fabric and Volume information into Tivoli Intelligent Orchestrator.
   1. In the Tivoli Intelligent Orchestrator Web interface, click Inventory -> Manage Discovery -> Discovery Configurations.
   2. From the Manage Discovery Configurations page, select TPC_Discovery and select Run
   3. Select one TPC management server (that you defined earlier using TPC_DefineTPCServer) to retrieve information from.
   4. Either schedule the discovery to take place immediately, or schedule it for a later time.
   5. Click Submit.
   For more information about the automation package and its workflows, refer to the IBMTPC automation package documentation.

Fixes related to Solaris UCE integration

• If the Sun UCE Profile discovery has no profile value or the value is set to unspecified, then the discovery will attempt to get a profile value from the groups the target belongs to. If the target is a member of more then one group (with profile values), one profile value is randomly chosen. The group property should have a key value of SUN_UCE_PROFILE_FOR_GROUP and the name of the profile as its value.
• Sun UCE can have PRE/POST action scripts as part of a profile.
• Tivoli Intelligent Orchestrator will now signal that Sun UCE will require a reboot as part of the patching process, by including a reboot object in the list of required patches.
• Tivoli Intelligent Orchestrator is now able to retrieve job logs for a Sun UCE action. The log ID is displayed in the Tivoli Intelligent Orchestrator workflow log. The Sun_UCE_Retrieve_Job_Log workflow can be used to bring the logs back to the provisioning server.
• Sun UCE Profiles are changed so that they are now easier to distinguish in the software catalog under Patches.

64–bit zLinux support

The provisioning server may now be installed and used on the 64–bit zSeries® Linux platform.

Fixes included in this fix pack

Version 5.1.1.2 (Fix Pack 2) includes fixes addressed in version 5.1.1.1 and customer Authorized Program Analysis Reports (APARs) from previous interim fixes.

1. Go to the IBM Support Web site at http://www.ibm.com/support.
2. In the Search all of support box, enter 5.1.1.1-TIV-TPM-FP0002 and click the search button.
3. Click 5.1.1.1-TIV-TPM-FP0002-DEFECTS (HTTP).

Product compatibility

There is no refresh installation included as part of this fix pack. Only an existing version 5.1.1.1 on any interim fix level can be upgraded to version 5.1.1.2. Migration from version 5.1 and version 5.1.1 to version 5.1.1.2 is not supported.

Fix pack applies to regular installations only

You can only apply the fix pack to a regular installation of Tivoli Intelligent Orchestrator (an installation with WebSphere Application Server as the application server). A fix pack is not available for a Fast Start installation.

Software Package Editor compatibility

Software Package Editor and the Tivoli Intelligent Orchestrator installation must be both updated to version 5.1.1.2 to work together properly.

Topology

If you have Tivoli Intelligent Orchestrator components distributed in a multi-node installation, the fix pack must be applied to the application server node where Tivoli Intelligent Orchestrator is installed and not on the IBM DB2 Universal Database server, LDAP server, or the directory server node.

Agent manager and common agent version

• The agent manager is updated when you install the fix pack.
• You must also upgrade the common agent on all depot servers after you have applied the fix pack.
• V1.3.2.29 agents will work with a Tivoli Intelligent Orchestrator 5.1.1.2 server and are not supported with earlier versions of Tivoli Intelligent Orchestrator.
• A Tivoli Intelligent Orchestrator 5.1.1.2 server supports V1.3.2.25 agents (the agent version provided with Tivoli Intelligent Orchestrator version 5.1.1 and version 5.1.1.1) and V1.3.2.29 agents.
• New Tivoli Intelligent Orchestrator 5.1.1.2 functions (for example, RHEL5 endpoint support, pause/resume distributions, custom inventory scans, multiple NIC support, NAT support, new TCA installation/upgrade, TCA file permissions fix, TPC integration improvements, Solaris UCE integration fixes, LDAP mixed attributes support, 64-bit zLinux server support) will only be supported with a Tivoli Intelligent Orchestrator version 5.1.1.2 server and a V1.3.2.29 agent.
• Fixes to problems found on V1.3.2.14 will be provided on V1.3.2.29 and will require the endpoint to be upgraded to that level.
• Fixes to problems found on V1.3.2.25 may be provided on V1.3.2.25 and not require an endpoint upgrade to V1.3.2.29.
• Tivoli Intelligent Orchestrator 5.1.1.2 officially provides agent migration from V1.3.2.25 to V1.3.2.29. If you have an agent with a version earlier than 1.3.2.25, migrate to 1.3.2.25 first before using Tivoli Intelligent Orchestrator 5.1.1.2. It is recommended that you migrate to version 1.3.2.25 before upgrading the server.
• All depots must be upgraded to version 1.3.2.25 before installing Tivoli Intelligent Orchestrator 5.1.1.2. After installing Tivoli Intelligent Orchestrator 5.1.1.2, all depots must be upgraded to version 1.3.2.29 before resuming regular operations.
• For Tivoli Intelligent Orchestrator 5.1.1.2, we recommend moving to V1.3.2.29 endpoints as soon as possible to make use of its new features. It is always recommended that you use the latest endpoint level supported by the provisioning server.

.

Platform support

HP is not supported as a provisioning server.

Preinstallation tasks

You must install and configure all components of Tivoli Intelligent Orchestrator version 5.1.1.1 before attempting the installation of 5.1.1.2. Thoroughly review the following list of installation prerequisites before you proceed with the installation.

Installation requirements

1. Identify your current installation situation. Consider the following scenarios:

   New Tivoli Intelligent Orchestrator installation

   Before you install this fix pack, you must first install Tivoli Intelligent Orchestrator version 5.1.1.1. For a regular installation, refer to the Tivoli Intelligent Orchestrator Installation Guide.

   For Linux on IBM iSeries®, IBM pSeries®, or IBM zSeries and Linux on AMD, you must perform the installation manually. Refer to the Tivoli Intelligent Orchestrator Installation Guide for additional platforms for your operating system.

   Tivoli Intelligent Orchestrator is currently installed

   If Tivoli Intelligent Orchestrator is already installed, you will upgrade from version 5.1.1.1 to 5.1.1.2.

   The fix pack can be applied to an existing regular installation of Tivoli Intelligent Orchestrator. After verifying all the prerequisites described in this section, you can install the fix pack. A fix pack is not available for a Fast Start installation.

2. Verify disk space requirements:

   Table 3. Disk space requirements for the Tivoli Intelligent Orchestrator node

   Location	Disk space requirements
   Disk space for installation images	2 GB
   Disk space to extract files from installation images	2.5 GB
   /	250 MB
   Temporary files: /tmp	600 MB
   /usr	50 MB
   /var	1 MB
   /home	100 MB
   Tivoli Intelligent Orchestrator installation directory The default location is: /opt/IBM/tivoli/tio	IBM AIX® 5 GB Solaris 3.5 GB Linux 3.6 GB
   Agent manager installation directory: usr/IBM/AgentManager	50 MB

3. Ensure that the zip and unzip utilities are installed on the provisioning server, and that the zip executable file is in the system PATH. This is required so that the fix pack files can be extracted. If not already installed, download the RPM zip and unzip packages from the following locations:
   • For AIX, go to http://www-03.ibm.com/systems/p/os/aix/linux/toolbox/download.html.
   • For Linux, the packages are provided on the Linux CDs, and are usually installed by default.
   • For Solaris, go to www.sunfreeware.com.
4. If the provisioning server is installed on AIX, ensure that the GNU tar utility is installed and is also in the system PATH. This is required so that the fix pack files can be extracted. If not already installed, download the GNU tar package from http://www-03.ibm.com/systems/p/os/aix/linux/toolbox/download.html.
5. If you have Web Replay installed, you must uninstall it before installing version 5.1.1.2. To uninstall Web Replay:
   1. Open a Web browser and type the Web address of the WebSphere administrative console for your provisioning server, for example, https://<host_name>:9044/ibm/console/logon.jsp. The default user and password are wasadmin.
   2. In the WebSphere administrative console menu, click Applications>Enterprise Applications.
   3. Click TCEAR.
   4. On the right-hand side, click Web module.
   5. Select the WebReplay.war check box and click Remove, then click OK.
   6. Click Save.
   7. Click Save to Master Configuration and click Save.
6. Log on to the provisioning server as administrator. If Tivoli Intelligent Orchestrator is LDAP based, log on as user tioappadmin
7. Verify that Tivoli Intelligent Orchestrator is operational.

   Ensure that you can run the workflow named no_operation. For instructions on how to run a workflow, refer to the Running workflows from the Web interface topic in the Tivoli Intelligent Orchestrator version 5.1.1.1 information center.

   • If the workflow was successful, the deployment engine is working properly and you can continue to the next step in this checklist.
   • If the workflow does not run successfully, check the workflow log and refer to the Tivoli Intelligent Orchestrator Problem Determination Guide to resolve the error before you proceed with the fix pack installation.
8. Verify the currently installed version of Tivoli Intelligent Orchestrator. The fix pack is compatible with version 5.1.1.1.

   To determine the Tivoli Intelligent Orchestrator version, in the Web interface, click the About link at the top right corner of the Welcome page.

9. Verify data model requirements:

   Verify that the sample:all-objects access domain exists. If you removed this access domain after installing Tivoli Intelligent Orchestrator, you must recreate it before installing the fix pack.

   1. Connect to the database:

      For DB2 Universal Database™

      db2 connect to database_name user database_user using password

      where:

      database_name

      The name of the Tivoli Intelligent Orchestrator database. The default database name is tc.

      database_user

      The database user name. If you installed version 5.1.1.1 with the default installation path, the DB2 Universal Database user is tioadmin.

      password

      The password for database_user.

      For example:

      db2 connect to tc user tioadmin using pa55w0rd

      For Oracle database

      sqlplus database_user/password@database_name

      database_user

      The database user name. If you installed version 5.1.1.1 with the default installation path, the Oracle database user is tiodb.

      database_name

      The name of the Tivoli Intelligent Orchestrator database. The default database name is tc.

      password

      The password for database_user.

      For example:

      sqlplus tiodb/pa55w0rd@tc

   2. Run the following command.

      For DB2 Universal Database

      db2 "select * from access_domain where name = 'sample:all-objects'"

      For Oracle database

      In SQL*Plus, enter:

      select * from access_domain where name = 'sample:all-objects'

      • If the command returns one record, then the access domain exists and no further action is necessary for this requirement.
      • If the command does not return any records, you must recreate the access domain. Proceed to the next steps.
   3. Create a new file called sampleAccessDomain.xml with the following lines:

      <?xml version="1.0" encoding="ISO-8859-1"?>
      <!DOCTYPE datacenter PUBLIC " -//Think Dynamics//DTD XML Import//EN" "xml import.dtd">
      <datacenter>
         <access-domain name="sample:all-objects">
         </access-domain>
      </datacenter>

   4. Import the file you created with the following command:

      $TIO_HOME/tools/xmlimport.sh file:path/sampleAccessDomain.xml

      1. If you imported the sample data in venice.xml, you must remove the sample boot server called Rembo. If this boot server is in the data model during fix pack installation, the automation package migration will fail. In the Web interface, click Inventory > Infrastructure Management > Boot Servers. Find the sample Rembo boot server and delete it.
      2. During installation of the fix pack, automation packages provided with Tivoli Intelligent Orchestrator are updated. If you removed some of the automation packages provided with previous versions of Tivoli Intelligent Orchestrator 5.1.1.1, but did not remove the data model objects associated with those automation packages, the update process will fail.

         For each automation package that you have removed, ensure that the data model objects that were created by the automation package are also removed. For example, if you removed an automation package for a piece of software, any software catalog entries created by the automation package must also be removed. Information about the objects created by an automation package is in the xml subfolder of the automation package.

         Alternatively, you can reinstall all provided automation packages that you removed before you begin the fix pack installation.

   5. During the installation of the fix pack, the TCA-1.3.2.25 Upgrade software module is deleted as part of a clean-up action. If there are data model objects associated with this software module, the migration will fail. One example of such an association is when the installable belonging to the TCA-1.3.2.25 Upgrade software module is published to one or multiple depots.
      Important:
      Unpublish the TCA-1.3.2.25 Upgrade Installable (upgrade_200712201840.jar) and manually delete the TCA-1.3.2.25 Upgrade software module.
10. Verify passwords required to perform the fix pack installation.
    • The password for the WebSphere Application Server administrator. The default ID for this user is tioadmin for OS authentication, and wasadmin for LDAP.
    • The password for database instance owner.
      • For DB2 Universal Database, the default user ID is db2inst1. If you installed 5.1.1.0 with the Default install path, the DB2 Universal Database user is tioadmin.
      • For Oracle database, the default user ID is sys.
11. To ensure successful installation of the language pack, ensure that the user tioadmin has read, write, and execute permissions for all directories under $TIO_HOME/tioprofile.
12. Cancel all running workflows and clear failed, deleted, and canceled workflows. Ensure that Tivoli Intelligent Orchestrator is stopped. For more information, refer to the Administering Tivoli Intelligent Orchestrator section in the Installation Guide.
    1. Open a command window.
    2. Go to the $TIO_HOME/tools directory.
    3. Run the following commands:

       ./cancel-all-in-progress.sh
       ./clean-up-deployment-requests.sh

13. The command marks all the in-progress deployment requests as abandoned (failed). The log files cancel-all-in-progress.log and clean-up-deployment-requests.log are created with the results of the commands.
14. Check for /bin as an entry in the PATH environment variable for the shell that you are using. If /bin is defined towards the beginning of the list in the PATH environment variable and the java command resolves with a path of /bin/java, installation of the dynamic content delivery service will fail.
    1. To confirm the location of Java, run the command:

       which java

       If this command is not available on your system, run the following command instead:

       type java

    2. If the returned value is /bin/java, run the following command to display the contents of the PATH variable:

       echo $PATH

    3. If the first part of the path is /bin, update the PATH variable so that /bin does not resolve the java command. There are several options for making this change:
       • Move /bin to the end of the list of paths in the PATH variable. Normally the java command will resolve to /usr/bin/java.
       • Create a symbolic link for /bin/java under another directory and add that path to the front of the PATH variable. For example, if you have a link in /usr/bin to the java command, ensure that /usr/bin is at the front of the PATH variable or place /usr/bin before /bin in the list of paths.
15. During installation, the installer runs the command df -Mk. On AIX, the GNU version of the df command does not support the -Mk option. Set the default df command to the native AIX version instead of the GNU version or change any existing symbolic link to point to the native AIX version for the fix pack installation.
16. If you have a Linux on zSeries installation of Tivoli Intelligent Orchestrator and you disabled the Java Just-In-Time (JIT) compiler after installation, you must enable the JIT compiler again and apply IBM Java SDK Version 1.4.2, Service Release 8. This Java SDK update fixes an issue with the reinit script that required you to disable the JIT compiler. The Java SDK update must be installed to successfully install the fix pack.
    1. Open the file $TIO_HOME/tools/setupCmdLine.sh and comment out the following line:

       export JITC_COMPILEOPT=NALL{org/eclipse/osgi/framework/internal/core/PackageAdminImpl}{doResolveBundles}

    2. Open the file $TIO_HOME/.tools/dcm/getdb.sh and comment out the following line:

       export JAVA_COMPILER=nojit

    3. Download the 31-bit zSeries (IBM S/390®) version of the Java SDK Version 1.4.2, Service Release 8 from http://www.ibm.com/developerworks/java/jdk/linux/download.html. This version of the download should be used for both 31-bit and (s390) and 64-bit (s390x) installations.
    4. Install the Java SDK according to the Java SDK documentation. If an older service release is already installed, force installation of Service Release 8.
    5. Open the file $TIO_HOME/tools/setupCmdLine.sh and change the value of JAVA_HOME to the directory where you installed the Java SDK.
17. Back up your installation:
    Important:
    The fix pack installation makes changes to the database, directory server, and files in the Tivoli Intelligent Orchestrator installation directory. These changes cannot be rolled back. If installation of the fix pack fails, you must restore a backup of the product before you applied the fix pack or reinstall the product, and then retry the fix pack installation.
    1. Back up your current installation. Use your own backup tools to perform a full system backup or refer to the Tivoli Intelligent Orchestrator Installation Guide for instructions on how to back up Tivoli Intelligent Orchestrator data.
    2. If the directory server or database is on a separate computer, also ensure that you back up that data.
    3. Save workflows that you created in the Web interface that you want to keep. If you create a new workflow in the Web interface, the workflow is saved in the data model and is associated with the automation package called default_automation_package by default. A copy of the workflow is not saved in the automation package file default_automation_package.tcdriver.

       The default_automation_package automation package can cause problems during the fix pack installation and is therefore deleted during the installation. If you want to save a workflow that you created in the Web interface, perform the following steps:

       Click Automation > Workflows

       1. Search for the workflow name.
       2. In the search results, click the workflow that you want to save.
       3. Click Edit > Export. The file is saved as a .wkf file.

       After the fix pack installation, you can add the workflow back into Tivoli Intelligent Orchestrator by opening it in the workflow composer and compiling the workflow. If you have multiple workflows to import, you can add them to an automation package and install the automation package.

18. Ensure that you have downloaded all the installation files required for the fix pack:

    Table 4. Tivoli Intelligent Orchestrator downloads available from the fix pack Web page.

    Operating System	Tivoli Intelligent Orchestrator	Components
    Windows Upgrading from 5.1.1.1	5.1.1.1-TIV-TIO-Win32-FP0002.zip	5.1.1.1-TIV-Components-Win32-FP0002.zip, which includes:   - CAS\AM_V13_WIN.zip   - CDS\Win32\setup.exe   - DMS\DMS_patch.zip   - DMS\ProductUpdateInstaller61.zip
    AIX Upgrading from 5.1.1.1	5.1.1.1-TIV-TIO-AIXPPC32-FP0002.zip	5.1.1.1-TIV-Components-AIXPPC32-FP0002.zip, which includes:   - CAS/AM_V13_AIX.tar   - CDS/AIXPPC32/setup.bin   - DMS/DMS_patch.zip   - DMS/ProductUpdateInstaller61.zip
    Solaris Upgrading from 5.1.1.1	5.1.1.1-TIV-TIO-SolarisSparc-FP0002.zip	5.1.1.1-TIV-Components-SolarisSparc-FP0002.zip, which includes:   - CAS/AM_V13_SUN.tar   - CDS/SolarisSparc/setup.bin   - DMS/DMS_patch.zip   - DMS/ProductUpdateInstaller61.zip
    Linux Upgrading from 5.1.1.1	5.1.1.1-TIV-TIO-Linux-FP0002.zip	5.1.1.1-TIV-Components-Linux-FP0002.zip, which includes:   - CAS/AM_V13_LIN.tar   - CAS/AM_V13_LIN_PPC.tar   - CAS/AM_V13_LIN_zSeries.tar   - CDS/LinuxIA32/setup.bin   - CDS/LinuxPPC64/setup.bin   - CDS/LinuxS390/setup.bin   - DMS/DMS_patch.zip   - DMS/ProductUpdateInstaller61.zip
    HP-UX Upgrading from 5.1.1.1	5.1.1.1-TIV-TPMFSW-HPUXIA64-FP0002.zip	5.1.1.1-TIV-Components-HPUXIA64-FP0002.zip, which includes:   - CAS/AM_V13_HPUX_IA64.tar   - CDS/HPUXIA64/setup.bin   - DMS/DMS_patch.zip   - DMS/ProductUpdateInstaller61.zip

19. Verify your downloads by validating their checksum values.
    1. Ensure that you have downloaded the .md5 file that corresponds to each .zip file from the fix pack download page.
    2. For each download, run the following command:
       Linux or Solaris: md5sum -c filename.md5
       AIX: csum -i filename.md5
       

       where filename.md5 is the name of the file that contains the md5 sum and the name of the filename.zip file. The md5 file must include only the .zip file name and not its full path.

       The command calculates the md5 sum for the filename.zip file, automatically compares it with the value listed in the .md5 file, and returns OK if the values are the same. For this to work, the .zip and .md5 files should be in the same directory when the md5sum check is run.

       For example, to validate the file 5.1.0.2-TIV-TIO-Linux-FP0002.zip, run the command:

       Linux or Solaris: md5sum -c 5.1.0.2-TIV-TIO-Linux-FP0002.md5
       AIX: csum -i 5.1.0.2-TIV-TIO-Linux-FP0002.md5
       
20. Create a temporary directory for the fix pack. In these instructions, the directory is called fp_temp. The temporary directory must meet these requirements:
    • It exists outside the Tivoli Intelligent Orchestrator installation directory.
    • It includes at least 2.5 GB of free space to contain the fix pack after it is unzipped.
    • The root and tioadmin user must have read and write permission to this directory.
    • There are no spaces in the name of the directory or the names of the parent directories.
21. Extract the contents of both fix pack downloads (Tivoli Intelligent Orchestrator and components) to the temporary directory. After you unpack the files, you can delete the zipped fix pack downloads to free space in the directory if necessary.
22. Run the following command: chmod -Rf 755 fp_temp, where fp_temp is the temporary directory that you created.
23. Ensure that Tivoli Intelligent Orchestrator is stopped. For instructions, see the Tivoli Intelligent Orchestrator Installation Guide, Common tasks for Tivoli Intelligent Orchestrator installation, in the Tivoli Intelligent Orchestrator Version 5.1.1.1 information center.
24. Ensure that WebSphere Application Server is stopped. For instructions, see the Tivoli Intelligent Orchestrator Installation Guide, Common tasks for Tivoli Intelligent Orchestrator installation, in the Tivoli Intelligent Orchestrator Version 5.1.1.1 information center.

25. Ensure that the Tivoli Intelligent Orchestrator database server and directory server are still running. The database and directory server must be running during the fix pack installation process to complete the installation successfully.

    Tivoli Directory Server

    To verify ITDS on Windows:

    1. Open the Services control panel.
    2. Find the entry for the IBM Tivoli Directory Server instance.
    3. If the server instance is not started, right-click the server instance name and click Start.

    AIX or Linux

    ibmdirctl -D cn=root -w password status

    Solaris

    ibmdirctl -D cn=root -w password -h hostname status

    DB2 Universal Database

    To verify that DB2 Universal Database is running:

    1. Switch to the DB2 Universal Database instance owner. For example, if you are using the default instance owner db2inst1, run the command:

       su - db2inst1

    2. To start DB2 Universal Database, run the command:

       db2start

       DB2 Universal Database is started if it is not running already. If the database is already running, the following message is displayed:

       SQL1026N  The database manager is already active

    Oracle database

    To check the status of the Oracle database and start the database, if necessary:

    1. To log in as the oracle user, enter su - oracle.
    2. To check if the Oracle database listener is running, enter lsnrctl status. If the listener is running, detailed information about the listener is displayed. If the listener is not running, the following message is displayed:

       TNS-12541: TNS:no listener

    3. If the listener is not running, enter lsnrctl start to start the listener.
    4. To check if the Oracle database is running, enter sqlplus / as sysdba. If the database is running, a message similar to the following is displayed:

       Connected to: Oracle Database 10g Enterprise Edition Release

       If the database is stopped, the following message is displayed:

       Connected to an idle instance.

    5. If the database is stopped, enter startup in SQL*Plus to start it.

Common directory paths

This readme file uses the following variables to represent directory paths.

/opt/IBM/ldap/V6.0

/opt/IBM/tivoli/tio

/var/ibm/tivoli/common/COP/logs

Installation tasks

Installing the fix pack

1. Ensure that you meet all the requirements as described in Preinstallation tasks.
2. Ensure that the directory server and database are running. For instructions on checking the status of applications, see the Tivoli Intelligent Orchestrator Installation Guide, Common tasks for Tivoli Intelligent Orchestrator installation, in the Tivoli Intelligent Orchestrator Version 5.1.1.1 information center.
3. Ensure that Tivoli Intelligent Orchestrator and WebSphere Application Server are stopped. For instructions, see the Tivoli Intelligent Orchestrator Installation Guide, Common tasks for Tivoli Intelligent Orchestrator installation, in the Tivoli Intelligent Orchestrator Version 5.1.1.1 information center.
4. Log in to the Tivoli Intelligent Orchestrator computer as root.
5. Run the following command, depending on what is supported on your operating system:

   export TERM=ansi

   or

   export TERM=xterm

   or

   export TERM=vt100

6. Change to the fp_temp directory.
7. Run the following command to install the fix pack. Note that the installation options are case-sensitive.

   For DB2 Universal Database

   unixUpgrade.sh -WASadmin was_adminID -WASadminPWD was_admin_pwd -DBAdmin db_adminID -DBAdminPWD db_admin_pwd

   For Oracle database

   unixUpgrade.sh -WASadmin was_adminID -WASadminPWD was_admin_pwd -DBAdmin db_adminID -DBAdminPWD db_admin_pwd -CDSOraclePWD cds_schema_pwd

   where
   • was_adminID is the WebSphere Application Server administrator ID. If you are using operating system authentication, the default user ID is tioadmin. If you are using read-only LDAP authentication, the default user ID is wasadmin.
   • was_admin_pwd is the password for the WebSphere Application Server administrator. If you are using operating system authentication, enter the password for the tioadmin user. If you are using read-only LDAP authentication, enter the password for the wasadmin user.
   • db_adminID is the database instance owner that was used to install Tivoli Intelligent Orchestrator.
   • db_admin_pwd is the password of the database instance owner that was specified during Tivoli Intelligent Orchestrator installation.
   • cds_schema_pwd. If upgrading from Version 5.1.1.0, enter the password for the CDSSCHEMA Oracle user, which was specified during Tivoli Intelligent Orchestrator installation. If upgrading from Version 5.1.0.2, enter tivoli, if you have not changed the password since installing Version 5.1.0.2, otherwise enter the correct password.
8. If Tivoli Intelligent Orchestrator is installed on Solaris, you must precompile all JavaServer Pages™ to ensure that the Web interface loads properly. This step is needed as a result of a Java problem on Solaris operating systems. To precompile all JavaServer Pages, run the following command:

   $TIO_HOME/.tools/tpmJspCompiler.sh

9. If Tivoli Intelligent Orchestrator is installed on Linux on zSeries and you are upgrading from version 5.1.0.2, you must update the run-deploymentengine.sh file for Tivoli Intelligent Orchestrator to start properly. To update this file, open $TIO_HOME/tools/run-deploymentengine.sh and replace the following line:

   $JAVA_HOME/bin/java -Xms256m -Xmx1024m

   with

   $JAVA_HOME/bin/java -Xms512M -Xmx512M 

   then save and close the file.
10. Start Tivoli Intelligent Orchestrator. For instructions, see the Tivoli Intelligent Orchestrator Installation Guide, Common tasks for Tivoli Intelligent Orchestrator installation, in the Tivoli Intelligent Orchestrator Version 5.1.1.1 information center.

    The first time that you start the product after installing the fix pack, the automation package migration process runs and updates the automation packages provided with Tivoli Intelligent Orchestrator:

11. Verify that you can log on to the dynamic content delivery service console. If the message The specified username or password is incorrect is displayed, this might indicate that SOAP services were not started. Check the log file $TIO_LOGS/soap/desoap_start.log. For information on how to fix the SOAP services, refer to the Tivoli Intelligent Orchestrator Installation Guide for your operating system.

Recovering from installation errors

The following main steps occur during the installation of the fix pack:

1. Installation of fix pack files.
2. Post-installation configuration such as migration of directory server data and migration of automation packages.
3. Upgrade of the agent manager.
4. Upgrade the dynamic content delivery service.
5. Database schema updates to tables and views in the database.

To recover from an installation error:

1. Record any error messages that you received and address the errors.
2. Check the log files for information about the error and possible recovery actions.

   Writable to read-only LDAP migration

   $TIO_LOGS/fixpack

   Fix pack installer

   $TIO_HOME/logs/update

   Data and LDAP migration

   $TIO_LOGS\migration

   The agent manager

   AM_installdir/logs

   The dynamic content delivery service

   /opt/ibm/tivoli/common/ctgde/logs

   The device manager service

   $DMS_HOME/log 

   Automation package installation

   $TIO_LOGS/tcdrivermanager.log

   Automation package data migration

   $TIO_LOGS/deploymentengine/console.log

3. Refer to the Known problems topic for possible installation errors and recovery actions.
4. An uninstaller is not available for the fix pack. Restore your backup of the product before you started the fix pack installation.
5. When you have fixed the source of the installation error, attempt the fix pack installation again.

Post-installation tasks

Upgrading the common agent

After you have completed the installation of the fix pack, you must upgrade older versions of the common agent. The common agent upgrade is from version 1.3.2.25, provided with Tivoli Intelligent Orchestrator 5.1.1.1 (any interim fix), to version 1.3.2.29, provided with Tivoli Intelligent Orchestrator 5.1.1.2. The common agent must be upgraded on both the depot servers and the endpoints that are participating in the software distribution process.

You can upgrade the agents using the Software Distribution Infrastructure (SDI) or the deployment engine. The steps to upgrade using SDI are:

1. Publish the TCA-1.3.2.29 Upgrade installable for the specific platform as shown in the following table. Make sure it is published to a preferred upload server depot.

   Name	Version	Installation Files
   TCA-1.3.2.29 Upgrade	1.3.2.29	TCA-1.3.2.29 AIX Upgrade Installable
   TCA-1.3.2.29 Upgrade	1.3.2.29	TCA-1.3.2.29 HP-UX on Itanium® Upgrade Installable
   TCA-1.3.2.29 Upgrade	1.3.2.29	TCA-1.3.2.29 HP-UX Upgrade Installable
   TCA-1.3.2.29 Upgrade	1.3.2.29	TCA-1.3.2.29 Linux390 Upgrade Installable
   TCA-1.3.2.29 Upgrade	1.3.2.29	TCA-1.3.2.29 Linux86 Upgrade Installable
   TCA-1.3.2.29 Upgrade	1.3.2.29	TCA-1.3.2.29 LinuxPPC Upgrade Installable
   TCA-1.3.2.29 Upgrade	1.3.2.29	TCA-1.3.2.29 Solaris Upgrade Installable
   TCA-1.3.2.29 Upgrade	1.3.2.29	TCA-1.3.2.29 Solaris x86 Upgrade Installable
   TCA-1.3.2.29 Upgrade	1.3.2.29	TCA-1.3.2.29 Windows Upgrade Installable

2. Go to Software Management > Upgrade > Software Product to upgrade the targets.
3. After the agent is upgraded either through the provisioning server or standalone, run the JES_Parameter_Set workflow using the parameters in the order below:
   • DeviceID
   • ParameterName The value for this parameter must be DiscoveryUploadUrl
   • ParameterValue The value for this parameter must be https://TPM_SERVER_IP:9046/poBox

You can run the workflow as a Favorite Task for multiple computers or a group.

Component versions

The agent upgrade uses the following versions of the scalable distribution infrastructure components:

Table 6. Scalable distribution infrastructure components

Component name	Component version
Tivoli Common Agent Services	1.3.2.29
Common Inventory Technology (CIT)	2.5.1026
Dynamic Content Delivery Client	1.3.2102
Dynamic Content Delivery Depot	1.3.2102
Dynamic Content Delivery Axis Export	1.3.2102
Tivoli Provisioning Manager OMA/DM OSGi Agent Extension	1.8.2
IBM Tivoli Provisioning Manager Job Execution Service	5.1.2000
Event Administration Service	5.1.1000
IBM Tivoli Intelligent Orchestrator CIT Scanner	5.1.5
SPBHandler	5.1.1000
IBM Tivoli Provisioning Manager Subagent	5.1.2000

Upgrading the Automation Package Developer Environment and Software Package Editor

If the Automation Package Developer Environment is installed in Eclipse on a separate computer, perform the following steps to upgrade it.

1. Ensure that Eclipse is not running.
2. Copy the archive file $TIO_HOME/apde/apde.zip to the remote computer.
3. Extract the contents of the archive file to the directory where the Automation Package Developer Environment is installed. For example /opt/apde. The contents of the archive file are placed in the eclipse/plugins subdirectory.
4. Start Eclipse with the -clean option so that the plug-in changes are applied:

   ./eclipse -clean

5. Exit Eclipse.

Downloads and updates

Web Replay updates

Additional Web Replay scenarios are available for you to use in Tivoli Intelligent Orchestrator. To download these Web Replay scenarios, go to the IBM Open Process Automation Library at http://catalog.lotus.com/tpm?NavCode=1TW10105F.

After downloading the packages, see the Web Replay online help for instructions on how to import and use the Web Replay scenarios in your environment. The Web Replay online help is available from the Tivoli Intelligent Orchestrator Web interface.

Patch management updates

Patch management for the HP-UX operating system is not supported

AIX patch discovery updates

If non-root user SAP is being used for AIX patch discovery, then the permissions of the following files need to be updated as shown below at the satellite server:

	chmod 505 /usr/suma/bin/suma
	chmod 404 /usr/suma/lib/SUMA/DBMStanzaDir.pm
	chmod 404 /usr/suma/lib/SUMA/Download.pm
	chmod 404 /usr/suma/lib/SUMA/Policy.pm
	chmod 404 /usr/suma/lib/SUMA/PolicyFactory.pm
	chmod 404 /usr/suma/lib/SUMA/StanzaDB.pm
	chmod 666 /var/adm/ras/suma.log
	chmod 707 /var/suma/data/policy.suma/
	chmod 606 /var/suma/data/policy.suma/default.SDBM_File.pag
	chmod 606 /var/suma/data/policy.suma/default.SDBM_File.dir
	chmod 604 /var/suma/data/config.suma 

Documentation updates

If you are applying the fix pack to a Tivoli Intelligent Orchestrator version 5.1.1.1 installation, refer to the following sources of documentation:

• The Tivoli Intelligent Orchestrator version 5.1.1 information center.
• This readme file.

Information center updates

Problems logging onto the dynamic content delivery console

In the Tivoli Provisioning Manager version 5.1.1 information center , disregard the document at http://publib.boulder.ibm.com/infocenter/tivihelp/v20r1/index.jsp?topic=/com.ibm.support.tpm.doc/agent/trdcds_authentic.html. This is not the supported resolution for resolving publishing problems because of issues logging onto the dynamic content delivery console. Contact IBM Software Support for assistance if you are experiencing this problem.

Overriding the default common agent installation path

The default installation path for the common agent is C:\Program Files\Tivoli\ep (Windows®), /opt/tivoli/ep (Solaris or Linux®), and /usr/tivoli/ep (AIX® or HP-UX). The default installation path can be customized as required.

The installation path variable that is defined in the configuration template associated with the common agent software module specifies the default common agent installation path. The following installation path variables can be used to override the default common agent installation path:

• AIX_Install_Path_Override
• HPUX_Install_Path_Override
• Solaris_Install_Path_Override
• Linux86_Install_Path_Override
• Linux390_Install_Path_Override
• LinuxPPC_Install_Path_Override
• Windows_Install_Path_Override
• Cygwin_Install_Path_Override

To override the default common agent installation path :

1. Click on Software Management > Manage Software Catalog > Software Stacks. The Manage Software Stacks page is displayed.
2. In the list, click the name of the common agent software stack. For example, Tivoli Common Agent Stack.
3. Expand Configuration Templates and default. Next to default, click > Edit
4. Next to default, click > Add Parameter. The New Template Parameter dialog is displayed.
   Note:
   The parameters must be added at the very top of the stack.
5. Specify the following values for the new parameter. For example :
   • In the Name field, type the parameter name, for example, Windows_Install_Path_Override
   • In the Parameter Type list, select String.
   • In the Predefined Value field, type the new installation path for common agent, for example, C:\Programme\tivoli\ep.
   • Click Add.
6. Click Save.
7. In the Configuration Templates table, click Save.

The default common agent installation path for the selected software definition has now changed to the specified new location.

Updating Oracle jdbc driver from 10.2.0.1.0 to 10.2.0.2.0

There are two ways to manually update the Oracle driver from 10.2.0.1.0 to 10.2.0.2.0 :

Method 1:

1. In the <Oracle installation folder>/jdbc directory, backup ojdbc14.jar as ojdbc14_10201.jar
2. Copy the new ojdbc14_10202.jar to the <Oracle installation folder>/jdbc directory and rename it to ojdbc14.jar.
3. Restart the server ./tio.sh
4. Restart Oracle.

Using this method, all components that were using driver 10.2.0.1.0 will use driver 10.2.0.2.0.

Method 2:

1. Copy ojdbc14_10202.jar to the <Oracle installation folder>/jdbc directory.
2. Open the Websphere Administrative Console from http://localhost:9061/ibm/console
3. Expand the Environment section.
4. In Environment click on the WebSphere variables link.
5. In the variables table click on the DMS_ORA_JDBCPATH variable.
6. In the Value field specify a path to the ojdbc14_10202.jar
7. Click Apply and to save the changes, click the Save button.
8. Restart the server ./tio.sh
9. Restart Oracle.

Using this method, only DMS will use driver 10.2.0.2.0. All other components will use driver 10.2.0.1.0.

Jdbc driver 10.2.0.2.0 can be downloaded from Oracle site: http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.htm

Discovery fails when there is no password

Discovery works when no password is specified. However, it is the policy defined on the endpoint being discovered which restricts the login. TPM cannot discover the endpoint when there is no password because the local security policy on the system by default does not allow a connection with no password when using SMB. To allow a connection with no password, disable the policy to allow the machine to be discovered.

Steps to configure local security policy on the endpoint:

1. Go to Start>Control Panel>Administrative Tools->Local Security Policy.
2. Go to Local Policies> Security Options.
3. Look under Policy for Accounts: Limit the local account use of blank passwords to console logon only. Disable the policy if it's enabled.

Logs do not get created for SUSE Linux Enterprise Server 8 (SLES8) and Red Hat Enterprise Linux 4

When using SDI, the job is submitted to the device manager service (DMS) federator agent running on the provisioning server and DMS publishes this job. The endpoint polls the DMS server until it sees the job available for execution. It fetches all the required files, and executes the job. The detailed logs about the task are available on the endpoint rather than the server.

How to change the SSL security certificate

Below are the steps to change the SSL security certificate:

Step 1: Generate the keystore for the provisioning server user interface (log on as root or administrator).

1. Start iKeyman on your workstation. The ikeymancommand is located under <WAS_HOME>/bin.
   • Click Key Database File and select New.
   • Specify settings:

     Key database type: JKS

     File Name: tpmKeyStore.jks

     Location: <TIO_HOME>/cert

   • Click OK.
   • Enter a password (twice for confirmation) and click OK.
2. Delete all of the signer certificates.
3. Click the pull down menu to select the personal certificate to add a new self-signed certificate.
   • Click New Self-Signed to add a self-signed certificate.
   • Specify the settings:

     Key Label: tpmUICert

     Common Name: your system hostname

     Organization: your organization name

   • Click OK.
4. Extract the certificate from this self-signed certificate.
   • Click Extract Certificate.
   • Specify the settings:

     Data Type: Base64-encoded ASCII data

     Certificate file name: tpmuicert.arm

     Location: <TIO_HOME>/cert

   • Click OK.
5. On the Unix platform, change the ownership of <TIO_HOME>/cert to tioadmin
   • chown -R tioadmin:tioadmin <TIO_HOME>/cert

Step 2: Create a new virtual host TPMUIVH and add 9049 to this virtual host (if 9049 is used for another application, you can use another available port)

1. Login to the WebSphere Administrative Console with your WebSphere administrator user name and password.

   http://<your hostname>:9061/admin

2. From Environment
   • Click Virtual Hosts >New
   • Enter TPM_UI_VH as name.
   • Click OK and Save.
3. From Environment
   • Click Virtual Hosts> TPM_UI_VH> Host Aliases > New
   • Enter 9049 as the port.
   • Click OK and Save.

Step 3: Create new SSL configuration repertoires for the provisioning server

1. From the WebSphere Administrative Console, click Security> SSL> New JSSE repertoire
   • Alias: TPMUISSL
   • Protocol: SSLv3
   • Key file name: <TIO_HOME/cert/tpmKeyStore.jks
   • Key file password: <your tpmKeyStore password>
   • Trust file name: <TIO_HOME>/cert/tpmKeyStore.jks
   • Trust file password: <your tpmKeyStore password>
2. Click OK and Save.

Step 4: Create 9049 transport chain

1. From the WebSphere Administrative Console:
   • Click Servers> Application servers> server1> expanding Web Container Settings under Container Settings> Web container transport chains> New.
   • Transport chain name: TPMUISSLChain
   • Transport chain template: select Webcontainer-secure
   • Click Next
   • Port name: TPMUIPort
   • Host:*
   • Port: 9049
   • Click Next> Finish> Save.
2. From the WebSphere Administrative Console:
   • Click Servers> Application servers>server1 > expanding Web Container Settings under Container Settings> Web container transport chains> TPMUISSLChain> SSL Inbound Channel
   • Modify SSL repertoire to use TPMUISSL
   • Click OK, then Save.

Step 5: Map AlphaloxPlatform and TCEAR web modules to TPM_UI_VH (9049)

1. From the WebSphere Administrative Console:
   • Click on Applications> Enterprise Applications> AlphabloxPlatform
   • Click Map virtual hosts for Web modules under Additional Properties
   • Modify IBM DB2 Alphablox and IBM DB2 Alphablox Administration Application virtual host to TPM_UI_VH
   • Click OK and Save.
2. From WebSphere Administrative Console:
   • Click on Applications> Enterprise Applications> TCEAR.
   • Click on Map virtual hosts for Web modules under Additional Properties
   • Modify tcWebUI, WebReplay, SPEWebApplication and SPEWebStart virtual host to TPM_UI_VH.
   • Keep DiscoveryUpload's virtual host as TPMVirtualHost.
   • Click OK, then Save.

Step 6. Restart the provisioning server

• https://<your hostname>:9049/tcWebUI for the provisioning server user interface.
• https://<your hostname>:9045/admin for the Dynamic Content Delivery administration console.

Publishing patches to the Tivoli Management Framework depot is not supported

Publishing patches to a Tivoli Management Framework (TMF) depot is not supported. Only software package block (SPB) packages can be published on a TMF depot.

When an endpoint with multiple network interface cards has its agent upgraded, its hostname is not updated in the data center model

Multiple network interface cards (NICs) were not supported in version 5.1.1.1 (Tivoli Common Agent 1.3.2.25). The computer representation found by discovery in version 5.1.1.1 will not change after an agent upgrade to version 5.1.1.2 (TCA 1.3.2.29). Only the interface name will be updated and this is by design. To change the computer name in the data center model (DCM), delete the DCM object representing the computer and rediscover the computer using Tivoli common agent discovery.

Information center report documentation

In Managing computers, inventory, and compliance > Reporting> Creating a new report the statement in step 10: "Review the summary of your selections for the report." should be updated with the following information:

The fields selected on the Constraints and Layout page of the wizard are used for the generated report and are different from the fields displayed on the Summary page of the wizard.

Endpoint interface name

On the Hardware page, all interfaces are shown with an endpoint host name rather than the actual name of each interface. .

Changing the user password in the Lightweight Directory Access Protocol

There are two steps to change a password for an user in the Lightweight Directory Access Protocol (LDAP) :

1. Update the user password for the provisioning server using the changePassword command.
2. Update the user password on the directory server (LDAP).

Known problems

At time of publication, the following problems and limitations were known.

As limitations and problems are discovered and resolved, the IBM Support team updates the online knowledge base. You can search the online support knowledge base to quickly find workarounds or solutions to problems that you experience.

Agent upgrade using the software distribution infrastructure fails with a Dynamic Content Delivery exception

Symptoms

Occasionally a workflow might end unexpectedly with java.rmi.MarshalException: org.xml.sax.SAXParseException.

Causes

This is caused by a problem with error handling for the common agent version 1.3.2.25.

Resolving the problem

See the endpoint log ep/logs/rcp.log.0 to determine the cause of the error.

Agent installation on Windows 2008 fails

Symptoms

COPDEX123E The workflow threw a AgentInstallException exception. The message is Agent installation failure. Agent install return code log file contents InstallStatus=0.

Causes

The possible causes of this error are:

1. Firewall
2. Network Failure
3. Agent incorrectly installed

Resolving the problem

On the endpoint, check the installation log for error details at <agent_install_dir>/ep/runtime/agent/logs. If the target computer has a firewall enabled, ensure that the provisioning server can ping the common agent. Check that the provisioning server can access the endpoint. Install the common agent again.

Cannot install the common agent on a target that has a double quotation mark in the password

Symptoms

The Tivoli common agent installation fails with a Jython error in the TCA_Installable_Install workflow.

Causes

The password of the user installing the common agent has an invalid character for Jython. The double quotation mark (") is an invalid character.

Resolving the problem

The user password for the default credential must not include a double quotation mark.

Columns are overlapping in PDF reports

Symptoms

Columns are overlapping in PDF reports when the data length of the column is long.

Causes

This is a known problem in Alphablox version 8.4, which has been fixed in Alphablox version 9.5.

Resolving the problem

Export the PDF into a spreadsheet to allow adjustment to the columns.

Error while upgrading the common agent

Symptoms

The common agent upgrade fails.

Causes

The # character in the password generates a corrupted URL, because the Dynamic Content Delivery component does not validate the URL.

Resolving the problem

Do not use the # character in the password for the administrator user of the provisioning server.

Automation packages are missing

Symptoms

After the installation of version 5.1.1.2, the custom automation packages (created by customers) are missing from the %TIO_HOME%\drivers folder.

Causes

During the fix pack installation, the old automation packages are backed up in %TIO_HOME%\drivers_5.1.1.1 and the 5.1.1.2 automation packages are copied to %TIO_HOME%\drivers.

Resolving the problem

Copy the custom automation packages (.tcdriver files) from %TIO_HOME%\drivers_5.1.1.1 to %TIO_HOME%\drivers after the upgrade is completed.

Install the Interim Fix 5 on version 5.1.1.1 to work with Windows Vista and Windows 2008

Symptoms

The discovery and common agent installation did not succeed.

Causes

Support for Windows Vista and Windows 2008 were added after version 5.1.1.1.

Resolving the problem

Install the Interim Fix 5 on version 5.1.1.1.

Installing the common agent on Red Hat Enterprise Linux 5 endpoints

Symptoms

The provisioning server is unable to ping the endpoints and the operation fails after 15 attempts with InstallStatus=0.

Causes

SELinux or a firewall might be enabled on the endpoints.

Resolving the problem

Perform the following steps to verify and disable SELinux on Red Hat Linux 5 and install the common agent again:

1. Run the command getenforce to find out if SELinux is enabled. If Enforcing, go to step 2, otherwise, go to step 3.
2. Run setenforce 0 to turn it off, then after you install the agent run setenforce 1 to enable again.
3. Ensure that no other firewall is enabled.
4. Reimage the endpoint or manually uninstall the agent from "tivoli/ep/_uninst/uninstall -console", remove TIVguid package and remove "/opt/tivoli* ,"/etc/cit" and "/etc/ibm" folder from endpoint.
5. Install the common agent again.

Initial discovery (on a computer behind a device using network address translation) sets the management IP of the endpoints to unknown

Symptoms

Running initial discovery on endpoints using network address translation (NAT) sets the management IP to unknown.

Causes

TADDMDiscovery, TPMNetworkDiscovery, MSADDiscovery do not support NAT. Therefore, after running initial discovery on endpoints using NAT, the management IP is set to unknown.

Resolving the problem

1. If initial discovery is run, then IBM Tivoli common agent discovery needs to run to set back the management IP to NAT IP.
2. After running IBM Tivoli common agent discovery, it is recommended not to run initial discovery. If a new SAP needs to be set for the computer (with NAT configured), which was discovered by IBM Tivoli common agent discovery, then the SAP should be manually created from the Inventory >Manage Inventory>Computers >Credentials tab.

Installation command exits with a return code: 237

Symptoms

Agent installation fails with error code 237.

Causes

This generally occurs when a common agent is already running on the same endpoint.

Resolving the problem

Ensure the old agent is correctly uninstalled from the endpoint.

Windows 2008 64-bit stand-alone common agent installation fails

Symptoms

Stand-alone Tivoli common agent installation fails on Windows 2008 64-bit platforms if the default installation location is used.

Causes

c:\Program files (x86) folder is emulated as a standard folder by 32-bit mode emulation. Even though the default installation is c:\Program Files as the destination folder, Windows redirects all the files and installs them to c:\Program files (x86), but the installation script verifies if installation is completed in c:\Program Files and fails.

Resolving the problem

Update the response file caInstall.rsp and specify an installation location. The installation location must to be different from C:\Program Files.

For example:

-P installLocation="C:\Program Files (x86)\tivoli\ep" 

or

-P installLocation="C:\tivoli\ep"

COPDEX123E The workflow threw a DownloadFailure exception

Symptoms

While performing Windows patch remediation and/or download, the following error message is generated:

COPDEX123E The workflow threw a Download Failure exception.
The message is "Download of Microsoft .NET Framework 2.0 Service Pack 1
(KB110806) ar zh-cn zh-tw cs da nl en fi fr de el hu it ko no pl pt-br
pt ru tr es sv has failed! Verify the WSUS server or proxy is reachable".

Causes

This is a problem with the selected patch. There is no issue with the code used to download the patch but with the .Net SP1 which has downloading issues.

Resolving the problem

Refer to the Microsoft® Web site at http://support.microsoft.com/kb/923100.

Microsoft Windows Update Agent (WUA) scan fails to execute on a Tivoli Management Agent (TMA)

Symptoms

1. Check C:\Program Files\ibm\tivoli\common\COP\logs\deploymentengine\Console.log.
2. The log has one of the following errors :

   COPCOM123E A shell command error occurred: Exit code=253, Error stream="** ERR:A problem occurred while attempting to download the UPDATE file: A connection with the server can not be established

   or

   2008-11-14 16:08:54,578 INFO  [Deployment Request 12802] (InvCfgHelper.java:69) inv.InvCfgHelper: A profile with this name does not exists, create it

   2008-11-14 16:08:54,703 ERROR [Deployment Request 12802] (TmfInventoryService.java:124) inv.TmfInventoryService: COPTMF001E Object: TPM_Windows_Patch_Scan not found.

Causes

The provisioning server is not able to login to Tivoli Management Framework (TMF).

Resolving the problem

1. Log on to the provisioning server user interface:
2. Click Inventory> Infrastructure Management > Tivoli Management Framework.
3. Check the user name and password in node type Region. It must be the same as the one used to log on to the TMF server (case-sensitive).

On a Solaris Operating System with Oracle configuration, an OutOfMemoryError occurs and the Web interface pages fail to load

Symptoms

On Solaris, Web pages do not load and an Out of Memory error is seen in the j2ee/console.log file.

Causes

This is caused by an issue with the Sun Java Virtual Machine. For more information, see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5077277

Resolving the problem

Open the Web Sphere Administrative Console and click Servers > Application servers > server1 > Process Definition > Java Virtual Machine. Change the Maximum Heap Size to 1024 and save the configuration change. Then restart the provisioning server.

The Sun_Update_Connection_Register workflow fails, when it is run again on the same Solaris Operating System 10 endpoint

Symptoms

The registration fails when attempting to register the same Solaris Operating System (Solaris) endpoint again by running the Sun_Update_Connection_Register workflow.

Causes

If a Solaris endpoint is already registered with the Sun Solve account, then it is not possible to register the same Solaris endpoint again with the Sun Solve account.

Resolving the problem

If an endpoint is already registered with Sun Solve, unregister the endpoint and wait for at least 24 hours for the unregistration to take effect, before attempting to register an endpoint again.

The new access group is not displayed in the group list

Symptoms

When you add a new access group in a one-node Microsoft Active Directory (MSAD) setup, the group is not displayed immediately.

Causes

The refresh interval for the MSAD server is one minute, therefore it can take up to one minute to refresh the page.

Resolving the problem

To see the new access group immediately, refresh the page manually.

Unable to login to the Web interface after upgrading to version 5.1.1.1

Symptoms

Cannot login to the Web interface after upgrading to version 5.1.1.1.

Causes

There is a space between the comma and the dc in the DN in user-factory.xml.

Resolving the problem

In the user-factory.xml file, remove any spaces in the DN. Ensure that the base DN in user-factory.xml exactly matches the real base DN. For example, the value should be dc=co,dc=in without additional spaces between the comma and dc.

Unable to add the Alphablox administrator role to the new WebSphere Application Server user (other than the default WebSphere Application Server user)

Symptoms

Cannot use the new WebSphere Application Server (WAS) user (unless it is the default WAS user) in the WAS Administrative console on UNIX® platforms.

Causes

Logging in using a non-default WAS user is not allowed.

Resolving the problem

Only the default WAS user login is supported on UNIX platforms.

Installing a software stack fails

Symptoms

Installing a software stack fails if more than one status update is in the status update window.

Causes

This is a problem in the Oracle jdbc driver 10.2.0.1.0 on the Solaris Operating System.

Resolving the problem

Update the Oracle jdbc driver to version 10.2.0.2.0. Instructions are provided in the Information center updates section of this readme file.

The port displayed when creating a Remote Execution and Access (RXA) service access point (SAP) for Server Message Block (SMB) is not valid

Symptoms

When creating an RXA SAP for SMB, the port shown is 0 where it should be 445 or 139.

Causes

The provisioning server does not reference the assigned port, instead it uses port 455 or 139.

Resolving the problem

No action is required.

Incorrect agent level is displayed during Tivoli common agent uninstallation

Symptoms

During the manual uninstallation of Tivoli common agent, the displayed agent version is incorrect.

Causes

When Tivoli common agent is upgraded, the uninstaller is not being upgraded from a previous version.

Resolving the problem

Ignore the agent level displayed during a manual uninstallation.

Patch installation fails on SUSE 10 with dependency failure error

Symptoms

• Run a patch scan and verify that suse_computers scan is successful.
• Approve one missing patch.

COPDEX123E A PatchInstallError exception occurred. The exception was caused by the following problem: Error installing patches. Please refer /tmp/temp11428.log file for more details. RETURNCODE:1 ERROR:ERROR: Dependency resolution failed:
Resolvable id 116289 does not exist.

Causes

This problem is related to the Novell rug issue. If the ZENworks daemon service is idle for a long time, the first time when rug install calls ZEN to retrieve Suse catalog database data, the error

Resolved id can not be retrieved.

Resolving the problem

1. Log in to the target computer.
2. Stop the ZMD process, run ps -ef |grep zmd to find all the ZMD related processes. Run kill -9 to stop all the ZMD processes.
3. Run rczmd stop to stop the ZENworks daemon.
4. Run rczmd start to start the ZENworks daemon.
5. Enter rug sl to ensure that the service is in active state.
6. Run the patch installation again.

Error loading libawt in the rcp.log.0 on the target endpoint

Symptoms

A Software Distribution Infrastructure (SDI) job stays in a submitted state for a long time and there is an error in the rcp.log.0 regarding loading libawt.

Causes

The Java XMLEncoder/Decoder classes depend on libawt. There might be situations when the operating system environment does not have the particular package that includes all of the libraries needed by libawt.

Resolving the problem

Verify that you have the packages documented in the following link and install any as needed: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.itpmdcd.doc/install_guide/cdcd_prereqs_jvmdependencies.html

Contacting customer support

If you have any questions about this fix pack, call the IBM Support Center for your country. For example, in the USA call 1-800-IBM-SERV. For specific contact numbers for all countries, refer to the following Web site:

http://techsupport.services.ibm.com/guides/contacts.html

If you find a problem or have a suggestion about the APDE (Automation Package Development Environment) features or the documentation in general, contact IBM through the Tivoli Provisioning Manager and Intelligent Orchestrator Automation Package Development Environment forum. The forum is a technical discussion focused on installing, configuring and using the APDE (Automation Package Development Environment) for writing workflows and creating automation packages for the Tivoli Intelligent Orchestrator products.

To access the forum:

1. Go to http://www-128.ibm.com/developerworks/forums/tivoli_forums.jsp.
2. Click on the Tivoli Provisioning Manager and Intelligent Orchestrator Automation Package Development Environment link on the Web site.

Additional license information

The notices file in the license subdirectory has been updated for this release.

Notices and trademarks

The following section includes important information about this document and its use.

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 about 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 property 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:

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

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 might not apply to you.

This information might 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 or changes in the product(s) or in 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 want 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:

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.

Trademarks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml

Intel® and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States, other countries, or both.

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

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

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. 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, and service names may be trademarks or service marks of others.