Tivoli Intelligent ThinkDynamic Orchestrator and Tivoli Provisioning Manager Interim Fix, IF0001 Readme

August 2004

Contents

Copyright statement

About this interim fix

  • New in Interim Fix V 2.1.0.0
  • New feature: Adding an available server to a cluster
  • Product compatibility

    • Installation notes

  • Before you install the interim fix
  • Viewing the license agreement
  • Creating a temporary directory
  • Unzipping the interim fix
  • Installing the fix on a Windows system
  • Installing the fix on AIX, Linux or Solaris
  • Post-installation steps
  • Before you begin
  • Post-installation on Windows
  • Post-installation on AIX, Linux, or Solaris

    • Uninstallation information

  • Before you begin
  • Uninstalling the fix on a Windows system
  • Redeploying the expanded archive files
  • Reinstalling the automation packages
  • Uninstalling the fix on AIX, Linux, or Solaris machine
  • Redeploying the expanded archive files
  • Reinstalling the automation packages
  • Restoring the database

    • Documentation updates

  • SOAP commands for running workflows
  • Creating deployment requests from the command line
  • Creating deployment requests in a Java program

    • Contacting customer support

    Notices and trademarks

  • Notices
  • Trademarks

    • Copyright statement

    First Edition, August 2004

    (C) Copyright IBM(R) Corporation 2004. All rights reserved. May only be used pursuant to a Tivoli(R) 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 interim fix

    This readme file contains the latest information about installing Tivoli Intelligent ThinkDynamic Orchestrator Interim Fix, Version 2.1.0.0 and Tivoli Provisioning Manager Interim Fix, Version 2.1.0.0. For more information on how to install the products, Tivoli Intelligent ThinkDynamic Orchestrator V 2.1.0 and Tivoli Provisioning Manager V 2.1.0, refer to the installation guide that is supplied with each product.

    New in Interim Fix V 2.1.0.0

    Interim Fix V 2.1.0.0 includes new fixes and customer Authorized Program Analysis Reports (APARs). For a detailed list of fixes and customer APARs included in this interim fix, refer to the file 2.1.0.0-TIV-TIO-IF0001.DEFECTS.html. To download the defects list:

    1. Go to the IBM Support Web site: http://www.ibm.com/support
    2. In the Downloads list, click Downloads and Drivers.
    3. In the search box, enter the interim fix number: 2.1.0.0-TIV-TIO-IF0001 and click Submit.
      Note:
      Interim Fix 2.1.0.0-TIV-TIO-IF0001 applies to Tivoli Intelligent ThinkDynamic Orchestrator and Tivoli Provisioning Manager.
    4. On the Download Results page, click the Tivoli Intelligent ThinkDynamic Orchestrator & Provisioning Mgr 2.1.0.0-TIV-TIO-IF0001 link.
    5. On the Tivoli Intelligent ThinkDynamic Orchestrator & Provisioning Mgr 2.1.0.0-TIV-TIO-IF0001 page, click 2.1.0.0-TIV-TIO-IF0001-DEFECTS (HTTP)

    New feature: Adding an available server to a cluster

    To add an available server to a cluster:

    1. Click the Data center assets and resources tab.
    2. Click Inventory -> Servers.
    3. Navigate to the list of servers that contains an available server. You can generate a list of servers in any of the three following ways:
    4. On the list of servers, select more server options for the available server and click Assign Server to Cluster.
    5. On the Clusters list, click the cluster that you want to assign the server to, and click Save.

    Product compatibility

    Interim fix V 2.1.0.0 supports all the hardware and software that is supported by Tivoli Intelligent ThinkDynamic Orchestrator V 2.1.0 and Tivoli Provisioning Manager V 2.1.0. Refer to the Installation Guide that is provided with your product to verify that your system meets the hardware and disk space and operating system requirements, as well as the required kernel parameter settings, and other requirements).

    Installation notes

    Complete the following instructions to install the interim fix.

    Before you install the interim fix

    Complete the following instructions before you install the interim fix.

    Viewing the license agreement

    Before you install Interim Fix V 2.1.0.0 you must read and agree to the terms of the product license agreement by viewing the contents of the license_oem.txt license file located in the following directory:

    Creating a temporary directory

    On the Tivoli Intelligent ThinkDynamic Orchestrator server or Tivoli Provisioning Manager server, create a temporary directory into which you will place the interim fix ZIP file.

    To create the temporary directory, run the following command:

    The directory must meet the following criteria:

    Unzipping the interim fix

    Complete the following instructions to unzip Interim Fix V 2.1.0.0. These instructions are applicable to all the operating systems supported by IBM for Interim Fix V 2.1.0.0.

    1. Log on to the server as Administrator in Windows, or as root in Solaris or Linux or AIX.
    2. Download the interim fix package to update_installer_dir directory where update_installer_dir is the directory in which you will unzip the interim fix ZIP file.
    3. Unzip the interim fix ZIP file. Unzipping the file will create a new directory within the current directory to store the package contents.
      Note:
      After you unpack the ZIP file, you can delete the ZIP file to free space in the directory if necessary.
    4. If you unzip the file from Cygwin, ensure that the files under the update_installer_dir/installer directory have read and write permissions.

    Installing the fix on a Windows system

    To install Interim Fix V 2.1.0.0 on Windows:

    1. From a command prompt, log in to the Tivoli Intelligent ThinkDynamic Orchestrator server or Tivoli Provisioning Manager server as Administrator
    2. Ensure that the database server and the directory server are both running.
    3. On the Tivoli Intelligent ThinkDynamic Orchestrator server or the Tivoli Provisioning Manager server, set the JAVA_HOME environment variable to WAS_HOME\java where WAS_HOME is the location of the WebSphere Application Server.
    4. Change directory to update_installer_dir\installer where update_installer_dir is the directory in which you unzipped the interim fix ZIP file.
    5. From update_installer_dir\installer, run the updatewizard.bat command to launch the installation wizard directory.
    6. Select the correct language and click OK.
    7. On the Welcome screen, click Next.
    8. On the next screen, specify the installation root directory.
      Note:
      The installation directory might not be specified here because, on some platforms, the graphical update installer program does not recognize the existing Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager installation. To work around this limitation:
      1. In the Installation Directory box, if the installation directory is not specified, select the Specify product information check box.
      2. Click Browse and select the appropriate installation root directory. For example: 
        C:\IBM\tivoli\thinkcontrol
    9. Click Next until you are prompted to select an option.
    10. Select Install fix packs and click Next.
    11. The interim fix directory screen displays the default directory in which the interim fix package is installed. Verify that the interim fix package is in this directory and click Next.
    12. On the interim fix selection screen, select the correct interim fix, and click Next.
    13. On the review screen, in the Name box click Next.
    14. On the summary screen, click Finish. The system completes the installation.

    Installing the fix on AIX, Linux or Solaris

    To install Interim Fix V 2.1.0.0 on AIX , Linux, or Solaris:

    1. Log in to the Tivoli Intelligent ThinkDynamic Orchestrator server or Tivoli Provisioning Manager server as root.
    2. Ensure that the database server and the directory server are both running.
    3. Export the JAVA_HOME environment variable to WAS_HOME/java where WAS_HOME is the location of the WebSphere Application Server.
    4. Ensure that the DISPLAY variable is set and confirm that the hostname of the server is correct.
    5. Change directory to update_installer_dir/installer where update_installer_dir is the directory in which you unzipped the interim fix ZIP file.
    6. From /update_installer_dir/installer, run updateWizard.sh to launch the installation wizard.
    7. Select the correct language and click OK.
    8. On the next screen, specify the installation root directory.
      Note:
      The installation directory might not be specified here because, on some platforms, the graphical update installer program does not recognize the existing Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager installation. To work around this limitation:
      1. In the Installation Directory box, if the installation directory is not specified, select the Specify product information check box.
      2. Click Browse and select the appropriate installation root directory. For example: 
        /opt/IBM/tivoli/thinkcontrol
    9. Click Next until you are prompted to select an option.
    10. Select Install fix packs and click Next.
    11. The interim fix directory screen displays the default directory in which the interim fix package is installed. Verify that the interim fix package is in this directory and click Next.
    12. On the interim fix selection screen, select the correct interim fix, and click Next.
    13. On the review screen, in the Name box click Next.
    14. On the summary screen, click Finish. The system completes the installation.

    Post-installation steps

    Complete the following instructions after you install the interim fix.

    Before you begin

    Before you complete the post-installation steps:

    Post-installation on Windows

    To complete the post installation procedure on Windows:

    1. Log in as user tiodamin.
    2. Ensure that WebSphere Application Server is stopped.
    3. Change directory to update_installer_dir\installer where update_installer_dir is the directory in which you unzipped the interim fix ZIP file.
    4. From update_installer_dir\installer\utils, run the postinstall.bat was_user was_pwd command, where was_user is your WebSphere Application Server user name, and was_pwd is your WebSphere Application Server password.
      Note:
      The postinstallation operation will print the output to the console. You can also redirect the output to a log file by running the following command: 
      postinstall.bat was_user was_pwd > log.txt

      where was_user is your WebSphere Application Server user name, and was_pwd is your WebSphere Application Server password.

    Post-installation on AIX, Linux, or Solaris

    To complete the post installation procedure on AIX , Linux, or Solaris:

    1. Log in as user tiodamin.
    2. Ensure that the WebSphere Application Server is stopped.
    3. Change directory to update_installer_dir/installer where update_installer_dir is the directory in which you unzipped the interim fix ZIP file.
    4. From /update_installer_dir/installer/utils, run postinstall.sh was_user was_pwd to deploy the EAR (expanded archive) files and the database schema change, where was_user is your WebSphere Application Server user name, and was_pwd is your WebSphere Application Server password.
      Note:
      The post-installation operation will print the output to the console. You can also redirect the output to a log file by running the following command: 
      postinstall.sh was_user was_pwd > log.txt

      where was_user is your WebSphere Application Server user name, and was_pwd is your WebSphere Application Server password.

    Uninstallation information

    Complete the following instructions to uninstall the interim fix.

    Before you begin

    Before you uninstall the interim fix:

    Uninstalling the fix on a Windows system

    To uninstall Interim Fix V 2.1.0.0 on Windows:

    1. From a command prompt, log in to the Tivoli Intelligent ThinkDynamic Orchestrator server or Tivoli Provisioning Manager server as Administrator
    2. Ensure that the database server and the directory server are both running.
    3. On the Tivoli Intelligent ThinkDynamic Orchestrator server or the Tivoli Provisioning Manager server, set the JAVA_HOME environment variable to WAS_HOME\java where WAS_HOME is the location of the WebSphere Application Server.
    4. Change directory to update_installer_dir\installer where update_installer_dir is the directory in which you unzipped the interim fix ZIP file.
    5. From update_installer_dir\installer, run the updatewizard.bat command to launch the installation wizard.
    6. Select the correct language and click OK.
    7. On the Welcome screen, click Next.
    8. On the next screen, specify the installation root directory.
      Note:
      The installation directory might not be specified here because, on some platforms, the graphical update installer program does not recognize the existing Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager installation. To work around this limitation:
      1. In the Installation Directory box, if the installation directory is not specified, select the Specify product information check box.
      2. Click Browse and select the appropriate installation root directory. For example: 
        C:\IBM\tivoli\thinkcontrol
    9. Click Next until you are prompted to select an option.
    10. Select Uninstall fix packs and click Next.
    11. The name of the installed interim fix package is displayed. Verify that the specified interim fix package is the one that you want to uninstall, and click Next.
    12. On the interim fix selection screen, select the correct interim fix, and click Next.
    13. On the review screen, in the Name box click Next.
    14. On the summary screen, click Finish. The system completes the uninstallation.

    Redeploying the expanded archive files

    After you have completed the uninstallation procedure using the graphical interface, you must redeploy the EAR (expanded archive) files on the WebSphere Application Server. To redeploy the EAR files:

    1. Log in to the Tivoli Intelligent ThinkDynamic Orchestrator server or the Tivoli Provisioning Manager server as user tioadmin.
    2. Start the WebSphere Application Server.
    3. From a command prompt, run the following command: 
      %TC_ROOT%\bin\bash --login -c "$TIO_HOME/tools/was_deploy.sh username password"

      The default value for username and password is wasadmin.

    4. Stop the WebSphere Application Server.

    Reinstalling the automation packages

    After you redeploy the expanded archive files, you must reinstall the automation packages.

    Run %TIO_HOME%\tools\post-install.cmd. This script installs all automation packages into the %TIO_HOME%\drivers directory. If you added any automation packages to this directory, they will be installed when you run the script.

    Note:
    Consider removing any automation packages that you added to the %TIO_HOME%\drivers directory to prevent "not installed" error messages from appearing when you run this script. The script will process for approximately one hour, as the system loads the automation packages.

    Uninstalling the fix on AIX, Linux, or Solaris machine

    To uninstall Interim Fix V 2.1.0.0 on AIX , Linux or Solaris:

    1. Log in to the Tivoli Intelligent ThinkDynamic Orchestrator server or Tivoli Provisioning Manager server as root.
    2. Ensure that the database server and the directory server are both running.
    3. Export the JAVA_HOME environment variable to WAS_HOME/java where WAS_HOME is the location of the WebSphere Application Server.
    4. Ensure that the DISPLAY variable is set and confirm that the hostname of the server is correct.
    5. Change directory to update_installer_dir/installer where update_installer_dir is the directory in which you unzipped the interim fix ZIP file.
    6. From /update_installer_dir/installer, run updateWizard.sh to launch the installation wizard.
    7. Select the correct language and click OK.
    8. On the Welcome screen, click Next.
    9. On the next screen, specify the installation root directory.
      Note:
      The installation directory might not be specified here because, on some platforms, the graphical update installer program does not recognize the existing Tivoli Intelligent ThinkDynamic Orchestrator or Tivoli Provisioning Manager installation. To work around this limitation:
      1. In the Installation Directory box, if the installation directory is not specified, select the Specify product information check box.
      2. Click Browse and select the appropriate installation root directory. For example: 
        /opt/IBM/tivoli/thinkcontrol
    10. Click Next until you are requested to select an option.
    11. Select Uninstall fix packs and click Next.
    12. The name of the installed interim fix package is displayed. Verify that the specified interim fix package is the one that you want to uninstall, and click Next.
    13. On the interim fix selection screen, select the correct interim fix, and click Next.
    14. On the review screen, in the Name box click Next.
    15. On the summary screen, click Finish. The system completes the uninstallation.

    Redeploying the expanded archive files

    After you have completed the uninstallation procedure using the graphical interface, you must redeploy the EAR (expanded archive) files on the WebSphere Application Server. To redeploy the EAR files:

    1. Log in to the Tivoli Intelligent ThinkDynamic Orchestrator server or the Tivoli Provisioning Manager server as user tioadmin.
    2. Start the WebSphere Application Server.
    3. At a command prompt, run the following script: 
      $TIO_HOME/tools/was_deploy.sh username password 

      The default value for username and password is wasadmin.

    4. Stop the WebSphere Application Server.

    Reinstalling the automation packages

    After you redeploy the expanded archive files, you must reinstall the automation packages. To reinstall the automation packages:

    1. Run $TIO_HOME/tools/deinitdb.sh
    2. Run $TIO_HOME/tools/post-install.sh start. This script installs all automation packages into the $TIO_HOME/drivers directory. If you added any automation packages to this directory, they will be installed when you run the script.
      Note:
      Consider removing any automation packages that you added to the $TIO_HOME/drivers directory to prevent "not installed" error messages from appearing when you run this script. The script will process for approximately one hour, as the system loads the automation packages.

    Restoring the database

    Tivoli Intelligent ThinkDynamic Orchestrator and Tivoli Provisioning Manager cannot determine or predict whether the database should be restored after you uninstall the interim fix.

    If you restore the database to the information that existed before the interim fix was installed, the information that was recorded when you installed the interim fix will be deleted.

    The decision to restore the database is, therefore, largely affected by the business needs of the enterprise. The database administrator and the appropriate corporate representatives should discuss whether or not the enterprise needs to keep the information that was recorded when you installed the interim fix. If you need that information, do not restore the database. If you do not need the information, it might be appropriate to restore the database.

    Documentation updates

    This section includes updates to the existing documentation.

    SOAP commands for running workflows

    The SOAP commands for running workflows have been updated.

    You can use MessageTranslator.wsdl to run a workflow. These commands are useful when you want to test workflows in a test application environment. You can run a workflow from the command line or from XML code. The XML format is useful for creating deployment requests from a Java program. These commands are available to all users.

    Creating deployment requests from the command line

    Syntax 
    soapcli username password wsdl_location createDeploymentRequest 
request_type_id workflow_name request_parameters 

    Options
    This command uses the following parameters:

    request_type_id
    The numeric identifier for the type of request.

    workflow_name
    The workflow name

    request_parameters
    Parameters for the specified workflow.

    Example
    The following examples show a createDeploymentRequest operation without request parameters and with request parameters. 
    soapcli username password http://localhost:9080/tcSoap/wsdl/com/ibm/tc/soap/ 
MessageTranslatorService.wsdl createDeploymentRequest 0 myworkflow 
 
soapcli username password http://localhost:9080/tcSoap/wsdl/com/ibm/tc/soap/ 
MessageTranslatorService.wsdl createDeploymentRequest 0 myworkflow "param1=value1,param2=value2,param3=value3" 

    Returned value
    The identifier of the new deployment request.

    Creating deployment requests in a Java program

    Syntax
    To incorporate request parameters for a deployment request, use the following XML format: 
    <?xml version="1.0" encoding="UTF-8"?>
<requestParameters>
<param name="param1" value="value1"/>
<param name="param2" value="value2"/>
<param name="param3" value="value3"/>
</requestParameters>

    Example
    The following example integrates a SOAP call from a Java client program by using the requestParameters in an XML string: 
    public class MyTest
public MyTest() throws Exception {
String wsdl= "http://localhost:9080/tcSoap/wsdl/com/ibm/tc/soap/
Message-TranslatorService.wsdl";
String opname= "createDeploymentRequest";
List params= new ArrayList();
params.add("0");
params.add("myworkflow");
String requestParams =
"<?xml version=\"1.0\" encoding=\"UTF-8\"?>" +
"<requestParameters>" +
"<param name=\"param1\" value=\"value1\"/>" +
"<param name=\"param2\" value=\"value2\"/>" +
"<param name=\"param3\" value=\"value3\"/>" +
"<param name=\"param4\" value=\"value4\"/>" +
"</requestParameters>";
params.add(requestParams);
System.out.println("result: " + Invoker.invoke(wsdl, opname, params, "userid",
"password"));
}

    Returned value
    The ID of the new deployment request.

    Contacting customer support

    If you have any questions about this interim fix, 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

    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 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 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:
    IBM Director of Licensing
    IBM Corporation
    North Castle Drive
    Armonk, NY 10504-1785
    U.S.A.

    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 Canada Ltd.
    Office of the Lab Director
    8200 Warden Avenue
    Markham, Ontario
    L6G 1C7
    Canada

    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

    The IBM logo and the following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States or other countries or both:

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

    UNIX(R) is a registered trademark of The Open Group in the United States, other countries, or both.

    Pentium(R) and Intel(TM) are registered trademarks of Intel Corporation in the United States, other countries, or both.

    Java(TM) and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

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

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