# IBM_PROLOG_BEGIN_TAG # This is an automatically generated prolog. # # bos720 src/bos/usr/lpp/bos/README.ISMP.S 1.3 # # Licensed Materials - Property of IBM # # COPYRIGHT International Business Machines Corp. 2002,2004 # All Rights Reserved # # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # # IBM_PROLOG_END_TAG _____________________________________________________________________________ InstallShield Multi-Platform (ISMP) Packaged Installations for the AIX operating system This document describes how ISMP packaged products can be installed and uninstalled on the AIX version 5 operating system. For complete instructions for installing or uninstalling a specific product packaged and installed with ISMP, please consult the product documentation. CONTENTS: * INTRODUCTION * INVOKING AN ISMP INSTALLATION * INVOKING AN ISMP UNINSTALLATION * SILENT INSTALLATIONS AND USING RESPONSE FILES * USING RESPONSE FILES WITH NIM _____________________________________________________________________________ INTRODUCTION ------------ Some products that are distributed for installation on the AIX operating system are packaged and installed with InstallShield Multi-Platform (ISMP). Unlike installp or RPM installations which only provide non-prompted or silent installations of a product, ISMP packaged products provide both interactive and silent interfaces for installation and uninstallation of a product. Similar to products packaged and installed with installp, ISMP packaged products can be installed using the AIX System Management tools, including System Management Interface Tool (SMIT) and Web-based System Manager. These tools use the geninstall command to install or uninstall products that are packaged and installed with installp, RPM, or ISMP. As expected, the geninstall command can also be used directly to install, list, or uninstall ISMP packaged products. _____________________________________________________________________________ INVOKING AN ISMP INSTALLATION ----------------------------- There are several ways to invoke an ISMP installation of a product. 1. Using SMIT: You can use the SMIT application to easily install products without knowledge of the exact location of the product installation files. To do this, use the SMIT install application by typing: smitty install Follow the same steps as you would to install any optional software product. You can refer to Chapter 10 of the AIX Installation Guide for more information. If you use the F4 key on the SOFTWARE to install field to select the product you want to install, products packaged and installed with ISMP will show in the list just as the products packaged and installed with installp or RPM. After making all selections, press Enter to begin the installation. By default, all installations launched through SMIT will be silent or non-prompted installations. If you wish to launch an interactive installation, you should use Web-based System Manager or the geninstall command, or follow the instructions provided with the product documentation as described below. Although SMIT will list a preview option, there is no real way to preview an ISMP packaged installation. If you choose this option you will see a message instructing you to launch an interactive installation. This will allow you to view the preinstall summary panel before completing the product installation. 2. Using Web-based System Manager: You can use the Software Application in Web-based System Manager to launch ISMP packaged product installations. To do this, follow the same steps as you would to install any optional software product. You can refer to Chapter 10 of the AIX Installation Guide for more information. When you press the "Browse" button to see a list of installable products on the media, ISMP packaged products will display in the list. Important: There is no real way to preview an ISMP packaged installation. It is a limitation of ISMP packaging and installation. If you choose the preview option, but proceed through the entire installation wizard, the product will be installed. Most products will include a preinstall summary panel that will provide preview information about the installation, including the space required and indication if file system expansion will be required. If you do not wish to proceed with the installation after viewing this information, you can click the CANCEL button to exit the wizard. 3. Using the geninstall command: You can use the geninstall command to launch an installation for an ISMP packaged product. To launch the installation interactively, just specify the device or directory containing the product installation files with the -d flag, and specify the product name. The product name is the same as the subdirectory name containing the product installation files. For example, if we have a product called "MyProduct", and the product installer files are in the local directory: /usr/sys/inst.images/ismp/ppc/MyProduct/ You would use this command to launch the installation interactively: /usr/sbin/geninstall -d /usr/sys/inst.images J:MyProduct Using the "J:" prefix with the product name tells the geninstall command that you are requesting to install an ISMP packaged product. The geninstall command recognizes the "ismp/ppc" subdirectory, just as it recognizes "RPMS/ppc" for RPM packages and "installp/ppc" for installp packages, so you should specify only the base directory, "/usr/sys/inst.images". If you want to launch a silent or non-prompted installation with geninstall, you can include the -Z flag: /usr/sbin/geninstall -d /usr/sys/inst.images -Z J:MyProduct 4. Using the files provided by the product developer: In most cases, the product developer will provide a script or executable that can be used to launch an ISMP packaged product installation. You should see the documentation provided with the product for more information on this option. INVOKING AN ISMP UNINSTALLATION ------------------------------- Uninstallation of an ISMP packaged product can be invoked with the same four interfaces provided for installation. 1. Using SMIT: To can use SMIT to uninstall an ISMP packaged product just as you would to uninstall any optional software product. You can refer to Chapter 10 of the AIX Installation Guide for more information. If you use F4 to list the installed software for the SOFTWARE to remove field. You should see the ISMP packaged product that you wish to uninstall in the list. Alternately, you can type the name of the product directly in the field. By default, all uninstallations launched through SMIT will be silent or non-prompted. If you wish to launch an interactive uninstallation, you should use Web-based System Manager, the geninstall command, or the instructions provided with the product documentation as described below. You will be given the option to preview the uninstallation, but just as there is no real way to preview an ISMP installation, there is no way to preview an uninstallation either. If you attempt to preview the uninstallation, you will see a message instructing you to launch an interactive uninstallation using Web-based System Manager or the command line. This will allow you to view the pre-uninstall summary panel before completing the product uninstallation. 2. Using Web-based System Manager: You can use the Software Application in Web-based System Manager to launch ISMP packaged product uninstallations just as you can to uninstall any optional software product. You can refer to Chapter 10 of the AIX Installation Guide for more information. Important: Note that while there is a preview option, there is no real way to preview an ISMP packaged uninstallation. It is a limitation of ISMP packaging and installation. If you choose the preview option, but proceed through the entire uninstallation wizard, the product will be uninstalled. Most products will include a pre-uninstall summary panel that will provide preview information about the uninstallation. If you do not wish to proceed with the uninstallation after viewing this information, you can click the CANCEL button to exit the wizard. 3. Using the geninstall command: You can use the geninstall command to launch an uninstallation for an ISMP packaged product. To launch the uninstallation interactively, just specify the -u flag for uninstallation, and the product name. Note that this is exactly the same as the procedure to uninstall an RPM or installp package using the geninstall command. For example, if you want to uninstall the product MyProduct, you would use the command: /usr/sbin/geninstall -u MyProduct or /usr/sbin/geninstall -u J:MyProduct Using the "J:" prefix with the product name tells the geninstall command that you are requesting to uninstall an ISMP packaged product and speeds up processing, but it is not necessary. If you want to launch a silent or non-prompted uninstallation with geninstall, you can include the -Z flag: /usr/sbin/geninstall -Zu J:MyProduct You can read more about silent installations below in the section "Silent installations and using response files". 4. Using the files provided by the product developer: In most cases, the product developer will provide instructions for launching an ISMP packaged product uninstallation. You should see the documentation provided with the product for more information on this option. SILENT INSTALLATIONS AND USING RESPONSE FILES --------------------------------------------- This section will describe in more detail how to perform silent installations for ISMP packaged products using response files. A response file contains predetermined responses for an installation. A response file template can be generated from an installation and then used to create a response file with appropriate responses. By default, response files and templates are created in a default directory, which is the same as the product directory on the media. Likewise, when an appropriately-named response file exists on the product media in the same location as the product installer files, it will be used automatically. The response file should be named .response, where is the name of the product to be installed. This should match the name of the subdirectory in which the product installer files reside. You can specify an alternate location for response files with the -t flag. This alternate location can either be a file or a directory. If specifying a directory, it must already exist. If it doesn't exist, it is assumed that a file name is specified. There are three ways to use response files with ISMP: 1. Creating a response file template: To create a response file template, you can use the geninstall command with the -T option. Note that this option is only valid for ISMP packaged installations. For example, if we have a product called "MyProduct", and the product installer files are in the local directory: /usr/sys/inst.images/ismp/ppc/MyProduct/ You would use this command to create a response file template named MyProduct.template in the default location (/usr/sys/inst.images/ismp/ppc/MyProduct/): /usr/sbin/geninstall -d /usr/sys/inst.images -T J:MyProduct Similarly, you can create a response file template in an alternate location (/tmp/MyProduct/response.template) with the -t flag: /usr/sbin/geninstall -d /usr/sys/inst.images -T \ -t /tmp/MyProduct/response.template J:MyProduct The resulting file /tmp/MyProduct/response.template would contain something similar to the following: ################################################################################ # # InstallShield Options File Template # # Wizard name: Setup # Wizard source: setup.jar # Created on: Tue Jun 25 10:59:55 CDT 2002 # Created by: InstallShield Options File Generator # # This file can be used to create an options file (i.e., response file) for the # wizard "Setup". Options files are used with "-options" on the command line to # modify wizard settings. # # The settings that can be specified for the wizard are listed below. To use # this template, follow these steps: # # 1. Enable a setting below by removing leading '###' characters from the # line (search for '###' to find settings you can change). # # 2. Specify a value for a setting by replacing the characters ''. # Read each settings documentation for information on how to specify its # value. # # 3. Save the changes to the file. # # 4. To use the options file with the wizard, specify -options # as a command line argument to the wizard, where is the name # of this options file. # ################################################################################ ################################################################################ # # My Product Install Location # # The install location of the product. Specify a valid directory into which the # product should be installed. If the directory contains spaces, enclose it in # double-quotes. For example, to install the product to C:\Program Files\My # Product, use # # -P installLocation="C:\Program Files\My Product" # ### -P installLocation= This is a simple example. Often products have many user-configurable options that may be set in the response file. Each of these options will be presented in the template with an explanation of the expected value for that option. 2. Creating a response file recording: To create a response file recording, you can use the geninstall command with the -E option. Note that this option is only valid for ISMP packaged installations. For example, if we have a product called "MyProduct", and the product installer files are in the local directory: /usr/sys/inst.images/ismp/ppc/MyProduct/ You would use this command to record a response file named MyProduct.response in the default location (/usr/sys/inst.images/ismp/ppc/MyProduct/): /usr/sbin/geninstall -d /usr/sys/inst.images -E J:MyProduct This will install MyProduct and create a response file with the recorded responses at: /usr/sys/inst.images/ismp/ppc/MyProduct/MyProduct.response. Similarly, you can create a response file recording in the alternate directory /tmp/MyProduct/ (if the directory exists). This command will create /tmp/MyProduct/MyProduct.response: /usr/sbin/geninstall -d /usr/sys/inst.images -E \ -t /tmp/MyProduct/ J:MyProduct Both commands shown will launch the interactive installation wizard. It is necessary to run the wizard to completion to successfully create the response file recording. You will be notified of this with message like this one: Options record mode enabled - run the wizard to completion to create the options file response.file The response file generated by the commands above would look similar to the following: ################################################################################ # # InstallShield Options File # # Wizard name: Setup # Wizard source: setup.jar # Created on: Tue Jun 25 11:05:34 CDT 2002 # Created by: InstallShield Options File Generator # # This file contains values that were specified during a recent execution of # Setup. It can be used to configure Setup with the options specified below when # the wizard is run with the "-options" command line option. Read each setting's # documentation for information on how to change its value. # # A common use of an options file is to run the wizard in silent mode. This lets # the options file author specify wizard settings without having to run the # wizard in graphical or console mode. To use this options file for silent mode # execution, use the following command line arguments when running the wizard: # # -options "record.txt" -silent # ################################################################################ ################################################################################ # # My Product Install Location # # The install location of the product. Specify a valid directory into which the # product should be installed. If the directory contains spaces, enclose it in # double-quotes. For example, to install the product to C:\Program Files\My # Product, use # # -P installLocation="C:\Program Files\My Product" # -P installLocation="/opt/MyProduct" Note that the difference is that value of -P installLocation has been filled in according to the response given while running the wizard. In this case, /opt/MyProduct was specified as the install location in the wizard. The MyProduct.response generated by this action can be used directly to launch a silent installation with the chosen install location. 3. Using a response file for a silent installation: The geninstall command will automatically look for response files named .response in the product directory. For example, if we have a product called "MyProduct", and the product installer files are in the local directory: /usr/sys/inst.images/ismp/ppc/MyProduct/ And additionally, there is a response file named MyProduct.response in the same directory, the following command will automatically use the response file: /usr/sbin/geninstall -Zd /usr/sys/inst.images J:MyProduct Similarly, you can use a response file in an alternate location (for example, /tmp/MyProduct/response.file) by using the command: /usr/sbin/geninstall -Zd -t /tmp/MyProduct/response.file J:MyProduct USING RESPONSE FILES WITH NIM ----------------------------- When installing an ISMP packaged product on one or more NIM clients using NIM, it is possible to create and use a separate response file for each client. This is useful when there are properties of the install that must be configured differently for each client. In order to install multiple clients, you must name each response file CLIENT_NAME.response. These response files must exist in the default location (the same location as the product installer files). For example, if you plan to install two clients named CLIENT1 and CLIENT2 with the ISMP packaged product named MyProduct located in an lpp_source at: /export/lpp_source/lpp_source1/ismp/ppc/MyProduct You can create two response files named CLIENT1.response and CLIENT2.response and place them in the same location as the product shown above. You can put the correct responses for each client in the corresponding response file. Then, when you run the NIM cust operation to install MyProduct on CLIENT1 and CLIENT2, the response files will be used automatically and appropriately for each client. If you want to use the same response file for all clients, you should name the response file PRODUCT_NAME.response and place in the same default location (the product location in the lpp_source). In this example, you could create a response file called MyProduct.response in /export/lpp_source/lpp_source1/ismp/ppc/MyProduct/. When you perform the same nim cust operation, if there are no client response files, the MyProduct.response file will be used automatically.