Installation Utility

8/10/2019 Installation Utility

1/130

Installation UtilityReference Manual

Supporting

Installation Utility 7.5.52

November 2006


2/130

Contacting BMC Software

You can access the BMC Software website at http://www.bmc.com . From this website, you can obtain informationabout the company, its products, corporate offices, special events, and career opportunities.

United States and Canada

Address BMC SOFTWARE INC2101 CITYWEST BLVDHOUSTON TX 77042-2827USA

Telephone 713 918 8800 or800 841 2031

Fax 713 918 8000

Outside United States and Canada

Telephone (01) 713 918 8800 Fax (01) 713 918 8000

Copyright 2006 BMC Software, Inc., as an unpublished work. All rights reserved.

BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarksor trademarks of BMC Software, Inc.

IBM is a registered trademark of International Business Machines Corporation.

All other trademarks belong to their respective companies.

BMC Software considers information included in this documentation to be proprietary and confidential. Your use of thisinformation is subject to the terms and conditions of the applicable End User License Agreement for the product and theproprietary and restricted rights notices included in this documentation.

Restricted rights legendU.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE

COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by theU.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer isBMC SOFTWARE INC, 2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent tothis address.
http://www.bmc.com/http://www.bmc.com/http://www.bmc.com/


3/130

3

Customer support

You can obtain technical support by using the BMC Software Customer Support website or by contacting CustomerSupport by telephone or e-mail. To expedite your inquiry, see Before contacting BMC.

Support website

You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support_home . From this website, you can

read overviews about support services and programs that BMC offersfind the most current information about BMC productssearch a database for issues similar to yours and possible solutionsorder or download product documentationreport an issue or ask a questionsubscribe to receive proactive e-mail alerts when new product notices are releasedfind worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, andtelephone numbers

Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 orsend an e-mail message to [email protected] . Outside the United States and Canada, contact your local support center forassistance.

Before contacting BMC

Have the following information available so that Customer Support can begin working on your issue immediately:

product information

product name product version (release number) license number and password (trial or permanent)

operating system and environment information

machine type operating system type, version, and service pack or other maintenance level such as PUT or PTF system hardware configuration serial numbers related software (database, application, and communication) including type, version, and service pack or

maintenance level

sequence of events leading to the issue

commands and options that you used

messages received (and the time and date that you received them)

product error messages messages from the operating system, such as f i l e syst em f ul l messages from related software
http://www.bmc.com/support_homehttp://www.bmc.com/support_homemailto:[email protected]:[email protected]://www.bmc.com/support_home


4/130

4 Installation Utility Reference Manual


5/130

Contents 5

ContentsChapter 1 Installation overview 9

About the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10The installation utility interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Options for installing products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Options for selecting products to install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Selecting products by using the default installation path . . . . . . . . . . . . . . . . . . . . 11

Selecting products by using the custom installation path. . . . . . . . . . . . . . . . . . . . 12Installing and configuring sudo to create a privileged account . . . . . . . . . . . . . . . . . . 13Performing a multiple CD installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Gathering product configuration information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 2 Installing and uninstalling products in a Windows environment 17

Checking installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Installing to a Windows Server 2003 computer from a network drive . . . . . . . . . 18Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Web browser requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Displaying installation utility online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Memory and disk space requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Network requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Before you begin installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Starting the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Creating, distributing, and installing installable images . . . . . . . . . . . . . . . . . . . . . . . . 42

Installable image files and directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Account requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Creating an installable image of products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Deploying the installable image to your environment . . . . . . . . . . . . . . . . . . . . . . 45Installing an installable image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Editing control files for installable images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Using the ctltool to edit control files for installable images . . . . . . . . . . . . . . . . . . 49

Locating log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Product installation directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Uninstalling BMC Software products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Performing an attended uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Performing an unattended uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Chapter 3 Installing and uninstalling products in a UNIX environment 59

Checking installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60


6/130


Web browser requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Displaying installation utility online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Memory and disk space requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Network requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Before you begin installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Starting the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Creating, distributing, and installing installable images . . . . . . . . . . . . . . . . . . . . . . . . 79

Installable image files and directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Creating an installable image of products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Deploying the installable image to your environment. . . . . . . . . . . . . . . . . . . . . . . 81Installing an installable image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Editing control files for installable images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Using the ctltool to edit control files for installable images. . . . . . . . . . . . . . . . . . . 86

Locating log files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Product installation directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Uninstalling BMC Software products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Performing an attended uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Performing an unattended uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Appendix A Troubleshooting a Windows environment 93

Common problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94The installation utility will not launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95The computer on which you want to install products does not have a web

browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Online help does not display properly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Installation fails with a failed to run script error . . . . . . . . . . . . . . . . . . . . . . . . . . 97Installable image installation fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Installation fails with unable to connect to remote host error. . . . . . . . . . . . . . . . 98Installation will not proceed past the specify installation directory page. . . . . . . 99Installation utility may stop responding if double quotes and angle brackets are

used in a directory path during a multiple CD installation . . . . . . . . . . . . . . . . 99After a product installation, Internet Explorer 5.0 stops responding and

consumes 99 percent CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99After a product installation, the installation utility cannot change a Windows

Server 2003 Itanium Terminal Server computer from install mode to executemode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

The installation utility is unable to perform directory-related functions onWindows platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Gathering diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Where to find diagnostic information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Generating debug information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Sending diagnostic information to BMC Software Support . . . . . . . . . . . . . . . . . 104

Appendix B Troubleshooting a UNIX environment 105

Common problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Typing errors cannot be corrected in an X-emulator . . . . . . . . . . . . . . . . . . . . . . . 107The display cannot be opened . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107


7/130

Contents 7

The installation utility will not launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Javascript error messages are displayed during installation . . . . . . . . . . . . . . . . 109Installation utility encounters problems during installation . . . . . . . . . . . . . . . . 109The computer on which you want to install products does not have a web

browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Online help does not display properly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Installation utility pages turn blank when resized. . . . . . . . . . . . . . . . . . . . . . . . . 111Perl error message is displayed when the -serveronly option is used . . . . . . . . 111Installation fails with unable to install perl error message . . . . . . . . . . . . . . . . . 112Installation fails or configuration scripts cannot be run after an installation. . . 112Installation fails with unable to connect to remote host error . . . . . . . . . . . . . . 113Installation will not proceed past the specify installation directory page . . . . . 113Unable to run root scripts error message is displayed on computers running Red

Hat Enterprise Linux AS 3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Mozilla browser renders installation utility pages with extra space . . . . . . . . . . 115Cannot extract a compressed installable image that is saved to a network share

on AIX platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Installation fails on computers running Red Hat and SuSE Linux . . . . . . . . . . . 115The installation utility is unable to run root scripts and reports an invalid root

password on computers running Red Hat Enterprise Linux AS 4.0. . . . . . . . 116Error messages are displayed when launching the installation utility on

computers running Red Hat Enterprise Linux AS 4.0 on Itanium . . . . . . . . . 116Gathering diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Where to find diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Generating debug information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Sending diagnostic information to BMC Software support . . . . . . . . . . . . . . . . . 119

Index 121


8/130



9/130

Chapter 1 Installation overview 9

C h a p t e r 11Installation overview

This chapter provides information about the installation utility. It presents thefollowing topics:

About the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10The installation utility interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Options for installing products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Options for selecting products to install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Selecting products by using the default installation path . . . . . . . . . . . . . . . . . . . . 11Selecting products by using the custom installation path. . . . . . . . . . . . . . . . . . . . 12

Installing and configuring sudo to create a privileged account . . . . . . . . . . . . . . . . . . 13Performing a multiple CD installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Gathering product configuration information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15


10/130

About the installation utility


About the installation utilityBy using the BMC Software installation utility, you can perform a local installation oruninstallation of BMC Software products on computers running Windows or UNIX

operating systems.

Alternatively, you can use the installation utility to create a product image that can betransferred to and installed locally on remote computers.

The installation utility interfaceThe installation utility interface consists of three panes:

a navigation pane that displays an indicator of where you are in the installationprocess

a data entry pane that displays each page that requires input during theinstallation

a footer pane that displays a Help button, Back and Next buttons, Exit button, andon certain pages, the following additional buttons:

Undo Changes - returns any values that you enter in the currently displayedpage to the default values.

Show/Hide Advanced - displays or hides optional advanced productconfiguration data entries. Consult the product documentation for the productsthat you are installing to determine the conditions under which you will need toenter any advanced configuration information.

Options for installing productsYou can install products on the computer on which you are running the installationutility, or you can create an installable image of products that can be installed at alater time. For detailed instructions on how to install products, see the getting startedor installation guides for the products that you are installing. For detailed instructionson how to create an installable image, see Creating, distributing, and installinginstallable images on page 42 for Windows platforms and Creating, distributing,and installing installable images on page 79 for UNIX platforms.


11/130

Options for selecting products to install


Options for selecting products to installThe list of products that you can select to install is based on the installation type and,optionally, on a system role that you select. Some products do not require different

installation types or system roles. If this is the case for the product that you areinstalling, the Select Type of Installation and the Select System Roles pages are notdisplayed in the installation utility. The following sections describe installing aproduct that uses two installation types.

Selecting products by using the default installation path

If you select the default installation path, you will see a product selection tree similarto the one shown in Figure 1 .

Figure 1 Example of a product selection tree view for PATROL productsdefaultinstallation path

The only selectable options shown are product solutions or groups, which arecomprehensive sets of products designed to work together. If you are installingproducts using the default installation path, you can select only these comprehensivesolutions or groups from the product selection tree. When you select a solution orgroup, all of the products included in that product set are automatically selected; youmay not be able to deselect individual products that you do not want to install if youuse the default path.

In addition, you are presented with subsequent pages to enter only mandatory product configuration information.

Use the default installation path if your installation scenario is similar to one of thefollowing examples:

You are installing products for the first time.You would like to use default values for most product configuration information.You are not familiar with the product set that you are installing.You want to select a prepackaged group of products with predefinedconfigurations.


12/130

Selecting products by using the custom installation path


Selecting products by using the custom installation path

If you select the custom installation path, you will see a product selection tree similarto the one shown in Figure 2 .

Figure 2 Example of a product selection tree view for PATROL productscustominstallation path

The selectable options shown are solutions or groups and individual products. Whenyou select a solution or group, all of the products that belong to that product set(including required and optional products) are automatically selected. However, byusing the custom installation path, you can deselect any of the optional products thatyou do not want to install.

In addition, you are presented with subsequent pages to enter both mandatory andoptional product configuration information about these products.

Use the Custom installation path if your installation scenario is similar to one of thefollowing examples:

You are upgrading a previous product installation (you can also use the Custompath if you are installing a product for the first time).

You would like to select and deselect products within product groups.

You want to more fully customize your product configuration.

You are familiar with the product set that you are installing.

and all products that belong to the specifiedsolution are automatically selected.

Click thischeck box...


13/130

Installing and configuring sudo to create a privileged account


Installing and configuring sudo to create aprivileged account

Some products that you install will require that you enter a root account andpassword to perform product configuration tasks. Instead of entering the rootaccount and password, you can install and configure sudo, then create a sudo-privileged account and enter the sudo account and password in place of the rootaccount and password. You must install and configure sudo before you begin theproduct installation.

To install and configure sudo

1 Download sudo version 1.6.7p5 or later from the following URL:www.courtesan.com/sudo .

2 Install sudo in the /usr/local/bin directory. If you install it in another location, createa link in /usr/local/bin directory to the location where sudo is installed.

3 Reconfigure sudo to turn off password caching by entering the followingcommand:

./configure --with-timeout=0

Password caching causes sudo sessions to be on a timer, meaning one sudo

operation could allow multiple operations without password authentication. Theinstallation utility code that is used to support sudo expects a password promptevery time sudo is invoked; therefore, password caching should be turned off forsudo to work correctly with the installation utility.

4 On the computer where you install sudo, enter the following lines for the Userprivilege specification in the sudoers file located in the local /etc directory:

install_accountname ALL=(ALL) PASSWD:ALL

Defaults: install_accountname shell_noargs, timestamp_timeout=0, !set_logname

The variable install_accountname is the name that you give to your sudo-privilegedaccount. These entries authenticate the user. The installation utility always expectsa password prompt, so sudo must be configured to supply the password. Noentries are required for the host alias, user alias, or command alias specifications.

Following is an example sudoers file:

#/etc/sudoers example file

#Host alias specification


14/130


15/130

Gathering product configuration information


directory. After the files have been copied from each of the required CDs, you will beasked to place the original CD back in the CD-ROM drive. The installation utilitycopies the required pieces from each CD to the temporary space that you designateand combines all the files for the installation.

After the installation is complete, the installation utility removes the copied files andthe temporary directory if it was created by the installation utility during thisinstallation. If you selected an existing directory as the temporary space to store theproduct files, then the installation utility removes only the copied files and the

bmc_install_temp_space directory.

Gathering product configuration informationTo install products, you will be asked to enter product configuration information inthe installation utility for the products that you are installing. The type and amount ofinformation depends on the products and the type of installation that you areperforming (Default or Custom). Consult the product getting started guides andrelease notes for details on the information that you must enter for each product.

NOTE On UNIX systems, you cannot eject removable media while the media is being accessed;therefore, if your installation requires multiple product images and you are using removablemedia, from a command line, cd to / then launch the installation utility by specifying theabsolute path; for example, /mnt/cdrom/setup.sh .

NOTE If the installation does not complete successfully, the installation utility will display the Multi-CD Temporary Area page after the Installation Results page and give you the option to savethe product files in the temporary directory or have the installation utility remove the filesand the directory. If you choose to save the files, you will not be asked to copy the productfiles again when you restart the installation.


16/130

Gathering product configuration information



17/130


C h a p t e r 22Installing and uninstalling productsin a Windows environment

This chapter describes requirements and options for installing and uninstallingproducts in Windows environments. It presents the following topics:

Checking installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Installing to a Windows Server 2003 computer from a network drive . . . . . . . . . 18Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Web browser requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Displaying installation utility online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Memory and disk space requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Network requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Before you begin installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Starting the installation utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Creating, distributing, and installing installable images . . . . . . . . . . . . . . . . . . . . . . . . 42

Installable image files and directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Account requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Creating an installable image of products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Deploying the installable image to your environment . . . . . . . . . . . . . . . . . . . . . . 45Installing an installable image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Editing control files for installable images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Using the ctltool to edit control files for installable images . . . . . . . . . . . . . . . . . . 49

Locating log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Product installation directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Uninstalling BMC Software products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Performing an attended uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Performing an unattended uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57


18/130

Checking installation requirements


Checking installation requirementsWhen you plan an installation of BMC Software products, you must considerwhether limitations or restrictions exist in your environment.

Before you launch the installation utility, ensure that your environment meets thehardware and software requirements described in the following sections. Also, beforeyou install any product to your environment, consult the product getting started orinstallation guides and release notes for the requirements for each product that youwant to install and for detailed installation information.

Installing to a Windows Server 2003 computer from a network

driveIf you are performing a local or -serveronly installation from a product image on ashared network drive to a Windows Server 2003 computer, the installation may timeout before the installation utility is launched. If this occurs, you must either:

use a product CD instead of a network image.

start the installation utility from a command line and use the -timeout commandline option. This option increases the amount of time that the installation utilitywaits to connect to the Perl HTTP server before it times out. The installation utilityuses the Perl HTTP server to install products.

For more details on the command line options, see Command line options onpage 24 .

Hardware requirements

The hardware requirements include

a CD-ROM drive (or network access to a CD-ROM product image)a FAT or NTFS file system (HPFS is not supported)a high color (16-bit) or true color (32-bit) display environment on any computerwhere you will be using a browser

NOTE For details and recommendations from Microsoft about installing and administering in aWindows Server 2003 environment, see the Microsoft website atwww.microsoft.com/technet .


19/130

Web browser requirements



A web browser is required to run the installation utility.

If you do not have a web browser on the computer on which you want to installproducts, you can:

create an installable image on a computer with a browser then install the image onthe computer that does not have a browser. For more details, see Creating,distributing, and installing installable images on page 42 .

use the -serveronly command line option to start the Perl HTTP server on thecomputer without the browser then connect to that server from a computer thathas a browser. For more details, see Command line options on page 24 .

Using proxy server definitions

If you have defined a proxy server for internet connections, your browser may beunable to connect to the Perl HTTP server that is used by the installation utility. Toresolve this issue, perform one of the following tasks for the browser that you areusing:

Remove the proxy server connection setting by selecting Tools => Internet Options=> Connections tab => LAN Settings and clearing the Use a proxy server check box.

NOTE If you use pop-up blocker software to prevent pop-up windows from being displayed in yourWeb browser, you must temporarily disable the software on the computer on which you wantto install products to run the installation utility. The procedures and requirements fordisabling pop-up blocker software vary depending on the software that you are using.Consult the documentation provided with the pop-up blocker software for instructions.

NOTE The installation utility will not run in Internet Explorer if any of the following conditions exist:

The computer on which you are running the installation utility is located in a Web contentzone that has a security setting of High. Security options are set in the Internet Optionsdialog box

The option Use HTTP 1.1 is deselected. This setting is located on the Advanced tab in theInternet Options dialog box

You used the -serveronly command line option to start the Perl HTTP server on anothercomputer, and you are connecting to that server from a Windows Server 2003 computerthat has the component Internet Explorer Enhanced Security Configuration installed andenabled. You can verify if this component is installed in the Add/Remove Programsdialog box.


20/130



Bypass the setting by selecting Tools => Internet Options => Connections tab => LANSettings => Bypass proxy server for local addresses .

Setting font size

If the font size in your browser is too large or too small, you can adjust the size byperforming the following task:

Choose View => Text Size and then one of the options that appears in the drop-downmenu, Largest , Larger , Medium , Smaller , or Smallest .


21/130

Displaying installation utility online help


Displaying installation utility online help

The installation utility includes a browser-based online Help system that can beaccessed from the Help button on each page in the installation utility. To properly

display the online Helpthe web browser that you are using to run the installation utility must be Java-enabled

you must have a Java Virtual Machine (JVM) or Java Plug-in version 1.1.2 or laterinstalled

If you are running the installation utility on a Windows computer that has InternetExplorer configured to use the Java Virtual Machine version 1.3.1, accessing the Helpsystem will cause the installation session to hang. To resolve this issue, perform one

of the following tasks:

upgrade to a newer version of the JVM

configure Internet Explorer to use a different JVM version if multiple versions areinstalled on your computer

use the -serveronly command line option to start the installation utility Perl HTTPserver on the computer that is running the JVM version 1.3.1, then connect to thatserver from a computer that has a different version of the JVM installed.

Memory and disk space requirements

Check the memory and disk space requirements listed in the getting started orinstallation guide for the products that you are installing to determine the amount ofdisk space and memory required to install each product. The installation utility alsoprovides an estimate of how much disk space is required for all products that youselect to install in one installation session.


22/130

Network requirements


Network requirements

You must have a properly installed TCP/IP local area network.

Before you begin installingComplete the following tasks before you install to computers running Windowsoperating systems.

Close all open applications on the computer where you are running the installationutility.

Map all drives that you will use during the installation.

If you are installing on a computer that is running Windows 2000 TerminalServices, Windows NT Terminal Server Edition, or Windows Server 2003 TerminalServices, make sure that the change.exe file exists in the Windows\System32 directory. The installation utility uses this file to change the installation mode oncomputers running these services.

If the file does not exist, you must either copy the file from another TerminalServices or Terminal Server computer, or launch the installation utility from theAdd/Remove Programs utility and use the -no_change_exe command line option. Formore details, see Command line options on page 24 .

If you are installing products on a backup domain controller, review the followingprocedure

WARNING The installation utility provides a command line option called -serveronly that you can use tostart the Perl HTTP server on one computer and connect to that server across a network froma browser running on another computer. The installation utility uses standard, unsecuredHTTP for network communications, which can create security risks for passwords and otherinformation that you may want to be secured across network traffic. Therefore, BMC Softwarerecommends that you install locally or create an installable image to distribute to remotesystems rather than use the-serveronly command line option in an unsecured network. For more information oncommand line options, see Command line options on page 24 .


23/130

Starting the installation utility


To install on a backup domain controller

If you are installing products on a backup domain controller (BDC) without firstinstalling to the primary domain controller (PDC) in a single domain, you mustperform the following procedure before you install the products.

1 From the User Manager for Domains, create a default account.

2 Assign the required advanced user rights to the default account.

3 Synchronize the entire domain. This process updates all the BDCs in the domainwith the updated user account database.

Once you have completed this procedure, you can install products on a BDC usingthe account that you created.

Starting the installation utilityTo start the installation utility, perform one of the following tasks:

Use Windows Explorer to open the CD directory and double-click setup.exe . (Dothis only if you do not want to specify any special command line options.)

Open a DOS command window and change to the CD-ROM drive where theproduct CD is located. At the prompt, type setup.exe and any other command lineoptions you would like to include (if any), then press Enter .

When you launch the installation utility from a command line, you can specify certaincommand line options to access additional functionality. For details on command lineoptions, see Command line options on page 24 .

NOTE Installing on a backup domain controller applies only to Windows NT 4.0 environments.

NOTE Only one installation session should be started at one time. If you need to perform multipleinstallations on the same computer, close out of each installation session and close allassociated browser windows before beginning a new session.


24/130

Command line options


Command line optionsTable 1 describes the options that you can use when you launch the installation utilityfrom a command line and references the page numbers where you can find detailed

information for each option.

Table 1 Command line options for Windows installation (part 1 of 2)

Option Definition For details

-h, -?, -help displays the list of command line options. see page 26-createcontrolfile lets you create a control file instead of perform

a product installation. The control file that youcreate shows the list of products that would beinstalled and the product configuration valuesthat the installation utility would use to

perform the product installation. Use thisoption to debug a failed installation, look forpotential problems with the installation beforeactually installing products, vary productconfiguration values to see the impact on theinstallation, or change the productconfiguration values associated with aninstallable image by creating a new control fileto use with the image. Also, you can use thisoption to create a control file that you can use toperform a silent uninstallation.

see page 27

-host_override hostname lets you override the default host name that theinstallation utility uses to connect to the PerlHTTP server. You can enter either a host nameor an IP address. This option can be usedstandalone or with the-serveronly option.

see page 28

-locale locale installs language-specific resource files for thelanguage that you specify

see page 29

-no_change_exe lets you install products on a computer runningWindows 2000 Terminal Services, Windows NTTerminal Server Edition, or Windows Server2003 Terminal Services if the change.exe file

does not exist on the computer. The installationutility uses the change.exe file to change theinstallation mode of a computer running theseservices. If the file is not found, the installationwill fail. To use this option, you must launchthe installation utility from the Add/RemovePrograms utility.

see page 30


25/130



-override_file location lets you install previously released BMCSoftware products onto new versions ofcompatible platforms. With this option, youspecify the location of a file that contains newplatform definitions that override the platforminformation stored in a product's installationfiles. The installation files are used tocommunicate installation information to theinstallation utility when the product isinstalled. You can also use the override file toupdate the platforms that you can select whenyou create an installable image.

see page 32

-port portnum lets you specify a port number to use to connectto the Perl HTTP server used by the installation

utility to perform product installations.

see page 33

-releaseversion version use this option to install a new KM into aprevious release of PATROL.

see page 34

-repository_designator role lets you select a system role from the commandline so that only those products designated forthat system role are displayed in the SelectProducts and Components to Install page.

see page 35

-serveronly use this option if you do not have a browser onthe computer on which you want to installproducts; lets you start the Perl HTTP server onone computer, then connect to that server using

a browser on another computer.

see page 36

-shutdownservice minutes lets you increase the number of minutes thatthe installation utility will wait for a service toshutdown before proceeding with aninstallation.

see page 37

-skipuserright tells the installation utility to not assign userrights to a default installation account during aproduct installation or to not unassign userrights from a default installation accountduring a product uninstallation. If you use thisoption, you must set the user rights manually.

see page 38

-timeout seconds lets you specify the number of seconds that theinstallation utility will wait to connect to thePerl HTTP server before timing out.

see page 39

-trace records detailed information about activities inthe installation utility interface duringinstallation.

see page 40

-v displays the version number for the installationutility.

see page 41

Table 1 Command line options for Windows installation (part 2 of 2)

Option Definition For details


26/130



-h, -?, -help

This option displays the list of command line options.

Command format

setup.exe -hsetup.exe -?setup.exe -help

Options

None.


27/130



-createcontrolfile

This option lets you create a control file instead of perform a product installation. Younavigate through the installation utility as you would if you were performing aproduct installation; however, at the end of the process, no products are actually

installed. Instead, a control file is created, and the installation utility displays a link tothe control file so that you can view it. The installation utility uses control files toperform product installations.

The control file that you create shows a list of the products that will be installed andthe product configuration values that the installation utility will use to install theproducts. Use this option to help you debug a failed installation, look for potentialproblems with an installation before actually installing products, vary the productconfiguration values to see the impact on the installation, or change the productconfiguration values associated with an installable image by creating a new controlfile to use with the image. The control file is located in the following directory

depending on your operating system:

For Windows 2000, Windows XP, and Windows Server 2003:

dr ive :\Documents and Settings\ username \Application Data\BMCinstall

For Windows NT:

dr ive :\winnt\Profiles\ username \Application Data\BMCinstall

command format

setup.exe -createcontrolfile

Options

None.

NOTE You can use this option to create a control file to perform a product uninstallation. For moredetails, see Performing an unattended uninstallation on page 57 .


28/130



-host_override hostname

This option lets you override the default host name that the installation utility uses toconnect to the Perl HTTP server. By default, the installation utility connects tolocalhost for a local product installation. If you launch the installation utility by using

the - serveronly command line option, the installation utility uses the primary IPaddress of the computer where the Perl HTTP server is launched as the default host.This option lets you override this default so that you can specify the host name or IPaddress that you want the installation utility to use on computers with multiple IPaddresses. This option can be used standalone or with the - serveronly option.

Command format

setup.exe -host_override hostname setup.exe -serveronly -host_override IPaddress

Options

None.


29/130



-locale locale

This option lets you select and install only those products that are compatible withthe locale (language) that you specify. You can specify only one locale. Theinstallation utility will filter the list of products that will be displayed in the Select

Products and Components to Install page to display only those products that areeither specific to the locale that you specify or that do not have a locale designation.

If you do not specify an option, then the locale from the system on which you arerunning the installation utility is used. If the system locale is not supported by theinstallation utility, then the English locale, en_US, is used. This option does notchange the language of the text displayed in the installation utility. The installationutility will run in English regardless of the system locale or the -locale option that youenter except as noted. In addition, you will be able to input only English characters.

Command format

setup.exe -locale en_US

Options

NOTE If you set the -locale option to be the same as the system locale, you will install theappropriate products and language resource files, but the installation utility will run in eitherEnglish or the system locale language and will accept input in either English or the systemlocale language.

Language Option

English en_USTraditional Chinese zh_TWSimplified Chinese zh_CNKorean ko_KR Japanese ja_JP


30/130



-no_change_exe

This option lets you install products on a computer running Windows 2000 TerminalServices, Windows NT Terminal Server Edition, or Windows Server 2003 TerminalServices if the change.exe file does not exist on the computer. The installation utility

uses the change.exe file to change a computer running one of these services to installmode if it is not already in install mode. If the file does not exist, the installation failswith an error message that the installation terminated abnormally. To bypass thechange.exe requirement, launch the installation utility from the Add/Remove Programs utility to put the computer in install mode and specify this option so that theinstallation utility will not look for the change.exe file.

Command format

setup.exe -no_change_exe

Enter this command in the Add/Remove Programs utility as follows depending onyour operating system:


1 Click Start => Settings => Control Panel => Add/Remove Programs .

2 In the Add/Remove Programs dialog box, click Add New Programs .

3 Click the CD or Floppy button.

4 In the Install Program From Floppy Disk or CD-ROM dialog box, click Next .

5 In the Run Installation Program dialog box, browse to the location of the productimage and select setup.exe or if you are installing products from an installableimage, select install.exe .

6 In the Open text box, enter -no_change_exe after setup.exe or install.exe and clickFinish .


31/130



For Windows NT:

1 Click Start => Settings => Control Panel => Add/Remove Programs .

2 In the Add/Remove Programs Properties dialog box, click Install .

3 In the Install Program From Floppy Disk or CD-ROM dialog box, click Next .

4 In the Run Installation Program dialog box, browse to the location of the productimage and select setup.exe or if you are installing products from an installableimage, select install.exe .

5 In the Command line for installation program text box, enter -no_change_exe aftersetup.exe or install.exe and click Finish .

Options

None.


32/130



-override_file location

This option lets you specify a file ( override.dat ) that will override platform definitionsin product installation files so that you can:

install previously released products onto new versions of compatible platforms.update the platforms that you can select when you create an installable image ofproducts.

The product installation files contain product-specific installation instructions, suchas supported platforms, that communicate to the installation utility how to install theproduct.

When BMC Software authorizes support for new platforms, Customer Support willprovide a valid override.dat file with new platform definitions that you will be able todownload from an ftp site located at the following URL:

ftp://ftp.bmc.com/pub/patrol/patches/COMMON_INSTALL_override.dat

After you have downloaded an updated override.dat file , when you install products,launch the installation utility from a command line and use this option to specify thelocation where you downloaded the file.

Command format

setup.exe -override_file c:\temp\override.dat

Options

None.

WARNING Do not edit the contents of the override.dat file. The installation utility may be unable to readthe edited file.

NOTE Although this functionality is being provided in this version of the installation utility, itcannot be used at this time because a valid override.dat file does not currently exist on the ftpsite.


33/130



-port portnum

This option lets you specify a port number to use to connect to the Perl HTTP server.Use this option if the default port number to the server is locked and you want tospecify another open port, or if you are using the -serveronly command line option

and you need to open a port through a firewall. If not specified, the installation utilityuses a default of 50001. If the default port number is in use, the installation utilityincreases the number by one and tries again to connect to the server.

Command format

setup.exe -port 3184setup.exe -serveronly -port 3184

Options

Any number from 1025 to 65534.


34/130



-releaseversion version

In a PATROL environment, this option lets you install a new KM into an existingPATROL environment.

Command format

setup.exe -releaseversion 3.4

Options

Option Description

3.2 for 3.2.x platforms and components3.3 for 3.3.x platforms and components3.4 for 3.4.x platforms and components

3.5,7.1 for 3.5.x and 7.1. x platforms and components. These optionsshould always be specified together.7.2 for 7.2 platforms and components.7.4 or 7.4 platforms and components. This is the default for this

version of the installation utility.


35/130



-repository_designator role

This option lets you select a system role from a command line so that only thoseproducts specified for a particular system role will be displayed in the Select Productsand Components to Install page. Each role has a specific code associated with it. The

roles (codes) that you can enter vary from product to product. Valid options can befound in the sysrole.xml file in the \ Index directory of the product image that you areinstalling from . If you specify this option, the Select System Roles page will not bedisplayed in the installation utility.

Command format

setup.exe -repository_designator PAT,PAA

Options

Depends on the products that you are installing. See the sysrole.xml file for validoptions.


36/130



-serveronly

This option lets you start the Perl HTTP server on one computer, then connect to thatserver using a browser on another computer. Use this option if you do not have a browser on the computer where you want to install products. When you launch the

installation utility with this command line option, the Perl HTTP server is started,and a message box is displayed that shows a URL. Leave this message box open. Onthe computer with the browser, start the browser and enter the URL displayed in themessage box to connect to the Perl HTTP server.

By default, this option uses port number 50001 to connect to the Perl HTTP server. Ifthat port is busy, the installation utility automatically increases the number by oneand tries again to connect. You can specify the port that you want to use by using the-port command line option with this option.

Command format

setup.exe -serveronly

setup.exe -serveronly -port 3184

Options

None.

WARNING The -serveronly command line option is not secure over a network and using it in an

unsecured network environment could result in security violations. If this is an issue for yourenvironment, you may want to consider either performing only local installations or creatingan installable product image that can be sent to a remote computer and installed on it locally,rather than installing over an unsecured network. For details on creating an installable image,see Creating, distributing, and installing installable images on page 42 .


37/130



-shutdownservice minutes

This option lets you increase the number of minutes that the installation utility waitsfor a service to shutdown before proceeding with an installation. The installationutility typically waits two minutes for a service to shut down. This option lets you

increase that number up to five minutes.

Command format

setup.exe -shutdownservice 3

Options



38/130



-skipuserright

This option keeps the installation utility from assigning user rights to a defaultinstallation account, if one is required, during a product installation. If you use thisoption, you must set the user rights for the installation account manually. Use this

option if the computer on which you are running the installation utility is notconnected to a network or if you are getting error messages when the installationutility attempts to assign the user rights.

Command format

setup.exe -skipuserright

Options

None.

NOTE You can also use this option to keep the installation utility from unassigning user rights from

the installation account during a product uninstallation. Change to the BM C productinstall ati on direct ory \Uninstall directory and enter:

uninstall.exe -skipuserright


39/130



-timeout seconds

This option lets you specify the number of seconds that the installation utility willwait to connect to the Perl HTTP server before timing out.

Command format

setup.exe -timeout 120

Options



40/130



-trace

This option lets you record detailed information about what is happening in theinstallation utility interface during a product installation. The installation utility addsthis information to the beginning of the standard log file. You can view the standard

log file from the installation utility when the installation is complete. This option alsosaves the control file that the installation utility uses to install products. Normally, theinstallation utility deletes the control file after the installation is complete. You canuse the saved control file and the information generated by this option for debugging

For information on the installation log files created and where to find the log files, seeLocating log files on page 51 .

Command format

setup.exe -trace

Options

None.

WARNING Using this option causes the installation utility to record passwords unencrypted in theinstallation log files.


41/130



-v

This option displays a dialog box that shows the version number for the installationutility.

Command format

setup.exe -v

Options

None.


42/130


43/130

Account requirements


Install this directory contains two subdirectories, instbin , which stores theinstallation engine binaries and installation tools such as ctltool, and instdata ,which stores the default text files that control the order in which the products areinstalled and that list the operating systems that are recognized by the installationutility.

If you selected the option to compress and save the image to a .zip file, you will seethe following files:

inst_ t imestamp .zip this file contains the compressed installable image directoriesand files.

cizip.exe run this executable from a command line to extract the installable imagefiles.

Account requirements

To create an installable image on Windows platforms, you must be a member of thelocal Administrator group on the computer on which you are creating the image. Toinstall the image, the person performing the installation must be a member of thelocal Administrator group on the computer on which the image is installed.

Creating an installable image of productsThis procedure describes how to create an installable image on a local computer forlocal installation on other computers.

To create an installable image of products

1 Start the installation utility.

2 On the Welcome page, click Next .

3 Review the license agreement and select Accept . Click Next .

4 On the Select Installation Option page, select Create an image to be installed later.

5 Enter the name of a directory on your computer where you want the image storedafter it has been created.

6 Optionally, select to have the image compressed and saved to a .zip file. Click Next .


44/130

Creating an installable image of products


7 Select the target operating systems on which you want to install the image. ClickNext .

You can select multiple Windows or UNIX platforms for each image that youcreate. Alternatively, you can select the Local System option, which lets you create

an image that can be installed only on computers with the same platform andconfiguration as the computer on which you are creating the image. This includesservice pack level.

8 Select the products that you want to include in the image. Click Next .

9 Proceed through the installation as you would if you were installing productslocally, entering all required product configuration information.

10 On the Review Selections and Create Image page, click Create Image .

11 When the status indicator reaches 100 percent, click Next on the Export Status page.

12 Verify that the process was successful and optionally view the log file. Click Next .

13 Review or enter any postinstallation product configuration information.

14 Click Finish to exit the installation utility.

When you create an installable image, the product configuration information that youenter, such as product installation directory, account names, passwords, and so forth,must be the same for all computers on which the image is installed. If you want tospecify different product configuration values for different computers, you can

create a separate image for each set of values that you want to implement.

launch the installation utility from a command line and use the -createcontrolfile command line option to create a new control file to use with the image. For moredetails, see Command line options on page 24 .

use the ctltool to change the variables stored in the image's control file after theimage is generated. For more details, see Editing control files for installableimages on page 49 .

NOTE You cannot create an installable image that can be installed on both Windows and UNIXcomputers. You must create one image for all Windows operating systems and one image forall UNIX operating systems; however, you can create the images from either a Windows orUNIX computer.


45/130

Deploying the installable image to your environment


Deploying the installable image to your environment

Once you have created an installable product image, you can deploy it to yourenvironment in several ways:

Tar the image and use ftp or secure ftp to send it to a remote computer.

Use a third-party distribution system such as Microsoft Systems ManagementServer (SMS).

Burn the image to a CD and distribute the CD.

Place the image on a shared network drive.

Selecting the Compress Installable Image option in the installation utility to create

a .zip file that you can then send to other computers.

Once the image is copied to the computer, it can be installed as described inInstalling an installable image on page 46 .

NOTE If you created an installable image on a Windows computer to be installed on UNIXcomputers, you must make sure that the method that you use to transfer the image (forexample, tarring the image) maintains execute permissions on the installable image files whenyou unpack the files on the UNIX computer. If the permissions are not maintained, you mayreceive an error message similar to the following when you try to install the image: " Er r or :Execut abl e not f ound ' . / t hor i nst . s25' . To correct the file permissions, before youinstall the image, perform one of the following tasks depending on where the installableimage directory resides:

If you exported the image to a directory that is at the root level, for example, /image , change tothe root directory and enter

chmod -R 755 /image

If you exported the image to a directory that is not at the root level, for example, /image/myimage , change to the directory in which the image directory is located ( /image ),and enter

chmod -R 755 /image/myimage


46/130

Installing an installable image



This procedure describes installing an installable product image locally in a Windowsenvironment.

To install an installable image on a Windows computer

1 Open a command prompt.

2 Change to the directory that contains the image files.

3 If you selected the option to compress the image, unzip the file by entering thefollowing command:

cizip.exe -u filename directory

The option filename is the name of the .zip file that contains the installable imagedirectories and files, and the option directory is the path to the directory where thefiles will be placed after they are extracted from the .zip file. If you specify adirectory that does not exist, the directory will be created. If you do not specify adrive with the directory name, the directory will be created in the same directorywhere the .zip file is located.

4 Change to the directory where the unzipped files are located.

5 Launch the installation utility by entering the following command:

install.exe options

For options, enter any command line options that you want to specify as listed inTable 2 on page 47 .

6 You can optionally unzip the file and automatically start the installation byentering the following command:

cizip.exe -u -x filename directory

The -x option launches the installation utility after the file is unzipped. If youchoose this option, you cannot specify any of the command line options listed inTable 2 .


47/130



Table 2 Installable image command line options for Windows (part 1 of 2)

Option Definition

-v displays the installation utility version on the command linethen returns to the command line prompt

-h displays the available command line options-path directory lets you specify the path name to the installable image if you

are not in the same directory-log location filename lets you specify the location where you want to store the

comprehensive log file and the name of the log file to bestored in that location. You can specify a complete path andfilename or just the file name. If you specify just the filename, the log file is stored in the same directory where theinstallable image files are located. The location and filenaming convention that you use for this option will also beused for the product log, user log, and standard output log

unless you use the additional command line options tospecify the location and file names for these log files. Forexample, if you name the comprehensive log file testing.log and store the log file in a directory called c:\install\logfiles ,the product log file will be named testing-product.log , theuser log file will be named testing-user.log , and the standardoutput log will be named testing-output.log and these logfiles will also be stored in the c:\install\logfiles directory.

-productlog location filename lets you specify the location where you want to store theproduct log file and the name of the product log file to bestored in that location. You can specify a complete path andfilename or just the file name. If you specify just the filename, the log file is stored in the same directory where theinstallable image files are located.

-userlog location filename lets you specify the location where you want to store the userlog file and the name of the user log file to be stored in thatlocation. You can specify a complete path and filename or

just the file name. If you specify just the file name, the log fileis stored in the same directory where the installable imagefiles are located.

-install location filename installs the products listed in a control file stored in thelocation that you specify. If the location is not specified, theinstallation utility looks for the control file in the directory

where the image was created.-no_change_exe lets you install the image on a computer running Windows

2000 Terminal Services, Windows NT Terminal ServerEdition, or Windows Server 2003 Terminal Services if thechange.exe file does not exist on the computer. Theinstallation utility uses the change.exe file to change theinstallation mode of a computer running these services. If thefile is not found, the installation will fail. To use this option,you must launch the installation utility from theAdd/Remove Programs utility. For details on using thisoption, see Command line options on page 24 .


48/130



The installation utility executes and installs the products associated with the image tothe installation directory that you specified when you created the image. When theprocess is complete, one of the following status messages is displayed on thecommand line:

The i nst al l at i on compl et ed successf ul l y The user l og cont ai ns t he f ol l owi ng f at al mess ages and a list of themessages

The pr oduct l og cont ai ns t he f ol l owi ng non- f at al messages anda list of the messages.

No status messages are displayed until the installation is complete.

Log files are created and stored in the user's profile directory under ApplicationData\BMCinstall unless you use one of the command line options listed in Table 2 onpage 47 to redirect them to another location. If you use the -log command line optiononly, all log files will be stored to the same location and with the same file namingconvention that you specify for the -log option.

For Windows NT environments, the default directory is:

C:\Winnt\Profiles\ username \Application Data\BMCinstall

For Windows 2000, Windows XP, and Windows Server 2003 environments, thedefault directory is:

-output location filename lets you specify the location where you want to store thestandard output log file and the name of the log file to bestored in that location. You can specify a complete path andfilename or just the file name. If you specify just the filename, the log file is stored in the same directory where theinstallable image files are located.

-nooutput lets you send output messages to standard output instead ofto a log file.

-skipuserright keeps the installation utility from assigning user rights to adefault installation account, if such an account is required fora product installation; this option also keeps the installationutility from unassigning user rights during a productuninstallation. If you use this option, you must set the userrights manually. For details on using this option, seeCommand line options on page 24 .

-shutdownservice min lets you increase the number of minutes that the installationutility waits for a service to shutdown before proceedingwith an installation. For details on using this option, seeCommand line options on page 24 .

Table 2 Installable image command line options for Windows (part 2 of 2)

Option Definition


49/130

Editing control files for installable images


C:\Documents and Settings\ username \Application Data\BMCinstall

In previous releases of the installation utility, log files were stored in the samedirectory as the installable image files.

Editing control files for installable images

Each computer on which you want to install an image must have the same productconfiguration values as those stored in the images control file.

To change the product configuration values, you can either create a new image, oredit the control file associated with the existing image. Ctltool is a utility that you canuse to change the product configuration values in an existing control file to create anew control file. Then, you can use the new control file to install the same image oncomputers that require the different values.

Using the ctltool to edit control files for installable images

This procedure describes how to edit the variables stored in an installable imagescontrol file.

To use the ctltool to edit control files in Windows environments

1 Open a command prompt.,

2 Change to the \Install\instbin directory in the directory where the installableimage is stored.

3 Enter the following command:

ctltool.exe drive:\ path\ inputf i l e.ct l drive:\ path\ outputf i l e.ct l

The option drive:\path\inputfile.ctl represents the path to and name of the controlfile that you want to edit (the control file that was created with the installableimage), and the option drive:\path\outputfile.ctl represents the path to and name ofthe new control file that you want to create.


50/130

Using the ctltool to edit control files for installable images


For example, you create an installable image and store the image in a directory onyour D: drive called installable image . When you create the image, the installationutility creates a .ctl file named install.ctl and stores that file in that directory alongwith the image files. To edit this control file and create a new one in the samedirectory, at the command prompt, you would change to D:\installable

image\Install\instbin , and enterctltool.exe D:\installable image\install.ctl D:\installable image\newfile.ctl .

The installation utility displays the first value stored in the control file.

4 Type a new value and press Enter to save your entry and display the next variable.To keep the existing value, press Enter . If you are changing a password variable,the value is encrypted in the new control file.

When the ctltool has finished displaying all the variables in the control file, thecommand prompt is displayed.

5 Rename the new control file to install.ctl so that when you install the image, theinstallation utility uses the new control file. The installation utility looks for acontrol file named install.ctl to perform the installation.

NOTE If the path that you enter for the input control file or the output control file has a space in it,you must enclose the path in quotes.

NOTE Optionally, you can use the -install command line option when you install the image tospecify the location and name of the new control file that you want to use. For more detailson the -install command line option, see Installing an installable image on page 46 .


51/130

Locating log files


Locating log filesThe installation utility creates the following log files:

concatenated logContains information from all other log files created during aproduct installation.

user logLists error messages about fatal errors that caused an installation to fail.The information in this log file is the first section in the concatenated log file.

product logLists nonfatal error messages and post-installation informationmessages, such as if a reboot is required after the installation is complete. Theinformation in this log file is the second section in the concatenated log file.

standard output log Lists messages that are usually sent to standard output. Theinformation in this log file is the third section in the concatenated log file.

comprehensive or main logLists all actions performed by the installation utilityduring a product installation such as the products that were installed or added toan image, files that were copied or removed, registry entries made, and anyversion checking that was performed. The information in this log file is the fourthsection in the concatenated log file.

front end trace logShows detailed information about activities in the installationutility interface during installation. This file is created if you launch the installationutility from a command line and use the -trace command line option. Theinformation in this log file is the fifth section in the concatenated log file. For moredetails on using the -trace command line option, see Command line options onpage 24

When the installation utility finishes installing products or creating an installableimage, a page is displayed in the installation utility that shows a status messageindicating the success or failure of the process. This page also contains a link, ViewLog , to the concatenated log file and displays the log files location and name. The logfiles name is determined at runtime and contains the name of the computer on whichthe installation utility was run and an incremental time stamp.

All log files are deleted after the installation is complete except for the concatenatedlog file unless:

you started the installation utility and used the -trace command line option or the-createcontrolfile command line option

the installation failed with an out-of-space error


52/130

Product installation directory structure


The installation utility stores the log files in the following directories:

For Windows NT:

C:\winnt\Profiles\ username \Application Data\BMCinstall


C:\Documents and Settings\ username \Application Data\BMCinstall

By default, the Application Data directory on Windows operating systems is hidden.To view this directory so that you can locate the installation log files, open WindowsExplorer and for Windows NT, choose View => Options => Show all files . ForWindows 2000, Windows XP, and Windows Server 2003, choose Tools => FolderOptions => View => Show hidden files and folders .

Product installation directory structureWhen you install products or create an installable image, you will need to provide thename of a directory into which the products that you select will be installed. Theinstallation utility provides a default directory that you can use, or you can enter anew directory.

By default, the installation utility uses c:\Program Files\BMC Software as the productinstallation directory. When you install products, the installation utility creates asubdirectory in the product installation directory for each product that you installand the following additional subdirectories that store information required by theinstallation utility:

WARNING You cannot enter a root directory as the product installation directory for BMC Software

products, because if you uninstall products from that directory, you may unintentionallyuninstall products other than BMC Software products. If you need to install into a rootdirectory to install a product upgrade, you can create an installable image and specify the rootdirectory as the installation directory for the products in the image; however, if you need touninstall the products from the root directory, do not use the uninstall-all.ctl file to performthe uninstall.

WARNING Product installation directories are stored in installation utility history files as full path names;therefore, do not rename the product installation directory after you install products, becausethe installation utility will be unable to find the renamed directory if you uninstall products.


53/130

Uninstalling BMC Software products


Install\insthist stores files that contain installation utility history information,such as which products you installed during a particular installation session

itools stores utilities that may be used by the products that you install

Uninstall\Install\instbase stores the Perl binaries and the Perl HTTP server code;Perl is used by installation utility to install products

Uninstall\Install\instbin stores the installation engine binaries and installationtools such as ctltool

Uninstall\Install\instcommon stores the xml files that are used to format anddisplay the standard installation utility pages

Uninstall\Install\instdata stores default text files that control the order of the listof products that you can select to install and the order in which the products areinstalled, and that list the operating systems that are recognized by the installationutility

Uninstalling BMC Software productsYou can use the installation utility in uninstall mode to select and uninstall only thoseproducts that were installed with version 7.2 or later of the installation utility.Products installed with a previous version of the installation program must use that

versions uninstallation utility.

WARNING Performing the tasks described in this section might remove files needed by a previousversion of the installation program to uninstall products installed with that version. Likewise,if you use a previous version of the installation program to uninstall products, you mightremove files needed by this version of the installation utility to perform the uninstallationtasks.

In addition, FTP and Telnet are not required for the uninstallation process on Windows.


54/130

Performing an attended uninstallation



Use the installation utility to select and uninstall individual products. Allcomponents associated with those products will also be uninstalled unless they are

required by another installed product.If the installation utility detects hidden, or orphaned, components on your computer,an additional page is displayed during the uninstallation that gives you the option toremove all of these components. Orphaned components are product components thatwere originally installed as non-selectable required product components during aprevious product installation but are no longer required by any of the productsinstalled on your computer.

If you select to uninstall all products and any orphaned components, an additionalpage is displayed that gives you the option to uninstall the uninstallation utility.

To uninstall products, orphaned components, and the uninstallation utility

1 From the Uninstall directory in your BMC Software product installation directory,double-click uninstall.exe to launch the uninstallation utility.

The Welcome page is displayed. Click Next .

2 Select the installation directory from which you want to remove a product. ClickNext .

3 Enter pre-uninstallation product information.

The pages displayed during this phase of the uninstallation may present onlyinformation that you should know prior to uninstalling the products or mayrequire you to enter information that the uninstallation utility will use to performvalidation checking before the uninstallation process begins.

The pages displayed will vary depending on the products installed on yourcomputer. For some groups of products, no pre-uninstallation pages will bedisplayed.

4 Select the product or products that you want to uninstall. Click Next .

NOTE You can optionally launch the uninstallation utility by choosing Start => Settings =>Control Panel => Add/Remove Programs and in the Add/Remove Programs Properties dialog box, in Windows NT environments, double-clicking on BMC Software Tools , andin Windows 2000 environments, selecting BMC Software Tools and clickingChange/Remove .


55/130



5 (optional) If the uninstallation utility detects any orphaned components, select toremove these components from your computer.

6 Enter any additional requested information in the displayed pages.

The information that you are required to enter depends on the products that youare uninstalling; for example, you may be required to enter account information,such as a user name and password, to uninstall the selected products. These pagesmay also display only information that you need to know once the products areuninstalled, such as if a reboot

Installation Utility

Documents

Transcript of Installation Utility