Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Installation   |   Topic List   |   Previous   |   Next   |   Contents

   Installing the BEA Tuxedo System

To install the BEA Tuxedo system and BEA Jolt on multiple machines with the same configuration, create a setup.iss file. This file contains the settings, such as destination directories for software components, required by the BEA Tuxedo system for a successful installation. You can then use the setup.iss file with Microsoft BackOffice tools to install the BEA Tuxedo system on multiple machines with the same configuration.

There are two ways to create the setup.iss file for unattended installation:

• Create a new setup.iss file using the choices you select during the standard installation process, or

• Edit one of the template setup.iss files provided with your software.

  Note: We recommend you create a new setup.iss file rather than edit a template file.

Using the Unattended Installation Process

To install the BEA Tuxedo or BEA Jolt software using the unattended installation process, complete the following 9-step procedure.

1. Ensure that there are no previous versions of the BEA Tuxedo or BEA Jolt software installed on the system. If previous versions are installed, you must remove them and reboot the system before proceeding to the next step.

2. Hold down the Shift key and insert the BEA Tuxedo CD into the CD-ROM drive. (By holding down the Shift key, you bypass the Windows autorun feature.)

3. Copy the following directories from the BEA Tuxedo CD-ROM to a directory on your hard drive:

   • cdrom_drive\Tuxedo\winnt (for BEA Tuxedo system installation)

   • cdrom_drive\Jolt\inwnt40 (for BEA Jolt installation)

   • cdrom_drive\unattended_install\templates

     Note: For the remainder of this procedure, we refer to the directory on your hard drive to which you copied the software directories as SETUPDIR and the full path name to that directory as SETUPDIR_PATH.

4. Create a new setup.iss file or edit one of the template files.

   For details on creating a new setup.iss file, see Creating a New setup.iss File. For instructions on editing a setup.iss template file, see Editing the setup.iss Template Files.

5. Verify that a new or edited setup.iss file has been copied to the directory in which the BEA Tuxedo or BEA Jolt Setup.exe file resides (SETUPDIR).

6. Start the installation process, using either of two methods. If you want to use the Windows NT menus, go to step 7. If you want to use a DOS command, skip to step 8.

7. Execute Setup.exe -s from the SETUPDIR directory as follows:

   1. From the task bar select Start-->Run.

   2. Enter the following command in the Open box:

      SETUPDIR_PATH\Setup.exe -s

      Alternatively, you can locate the Setup.exe file by selecting Browse. Be sure to add the -s option after the Setup.exe filename. The -s option indicates there is a setup.iss file to be used during this installation.

      Note: Installing the software using unattended installation takes the same amount of time as a standard installation. During unattended installation, no windows or prompts are displayed indicating the installation is in progress or has completed successfully. You can verify the successful completion of the installation process by confirming the existence of the setup.log file, as described in step 9.

      Note: You cannot run setup.exe -s directly from the CD-ROM for the following two reasons. First, for setup.exe -s to execute properly, both the setup.iss and the setup.exe files must be located in the same directory. There is no setup.iss file in the directory in which the BEA Tuxedo or BEA Jolt setup.exe file resides on the CD-ROM. Second, the setup.log will not be created since you cannot write to the CD-ROM.

   3. Click OK and go to step 9.

8. At the DOS command-line prompt, enter

   SETUPDIR_PATH\setup -s

   The -s option indicates there is a setup.iss file to be used during this installation.

   Note: Installing the software using unattended installation takes the same amount of time as a standard installation. During unattended installation, no windows or prompts are displayed indicating the installation is in progress or has completed successfully. You can verify the successful completion of the installation process by confirming the existence of the setup.log file, as described in the next step.

9. Verify that the installation completed successfully by viewing the setup.log file in the SETUPDIR directory. To do so:

   1. In a Windows Explorer window, double-click on the setup.log file in the SETUPDIR directory.

   2. Check the ResultCode in the last line of the file. If ResultCode=0, the installation was successful. Other possible result codes are listed in the following table.

      This Code. . .	Indicates. . .
      0	The installation completed successfully.
      -3	Setup information (such as directory names) is missing or not defined in the setup.iss file. This situation occurs most often when the setup file being used is an edited template file; it is unlikely to occur if the setup file being used is one that was created during the standard installation process.
      -4	There is insufficient memory to complete the installation process.
      -5	The setup.iss file could not be found.
      -12	The order of information in the setup.iss file differs from the sequence of the installation script.

To create a new setup.iss file, complete the following 7-step procedure.

1. Invoke the standard installation program through either of two methods. If you want to use Windows menus, go to step 2. If you want to use a DOS command, skip to step 3.

2. Invoke the standard installation program as follows:

   1. From the task bar select Start-->Run.

   2. Enter the following in the Open box:

      SETUPDIR_PATH\Setup.exe -r

      where SETUPDIR_PATH is the directory to which you copied the BEA Tuxedo or BEA Jolt files in step 3 in the procedure provided in Using the Unattended Installation Process.

      Alternatively, you can locate the Setup.exe file by selecting Browse. Be sure to add the -r option after the Setup.exe filename.

      Note: The -r (record) option is used to generate the setup.iss file.

   3. Click OK and go to step 4.

3. At the DOS command-line prompt, enter

   SETUPDIR_PATH\setup -r

4. The Setup screen is displayed, followed by the Welcome screen for the product you are installing. Step through the installation program by responding to each prompt. Detailed instructions for using the installation programs can be found in Installing the BEA Tuxedo Release 7.1 Software on a Windows NT System and Installing the BEA Jolt Software.

   Caution: The setup.iss file is a record of the choices you enter in response to the prompts from the installation program. To create a reliable setup.iss file, it is important that you correctly respond to each prompt. If, for example, you select the Back key to correct an entry or to verify your selections, you will create an extra entry in the setup.iss file. This extra entry is not valid for unattended installation. As a result, subsequent unattended installations using this setup.iss file will not complete successfully. Therefore, if you make a mistake or you accidentally hit the Back key when responding to the prompts, you must select Cancel, delete the setup.iss file, and restart the installation.

5. After you have completed the installation, find the setup.iss file in one of the following directories:

   • C:\WINNT on a Windows NT system

   • C:\WINDOWS on a Windows 9x system

6. Copy the setup.iss file to the directory in which the BEA Tuxedo or BEA Jolt Setup.exe file resides (SETUPDIR).

7. Go to step 7 in the procedure provided in Using the Unattended Installation Process.

BEA provides five setup.iss template files for unattended installation.

This Template . . .	Can Be Edited for Use While Installing the . . .
setup.iss_core_w_lic	BEA Tuxedo Core System with a license file
setup.iss_core_wo_lic	BEA Tuxedo Core System without a license file
setup.iss_ws	BEA Tuxedo Workstation Only
setup.iss_win9x	BEA Tuxedo Workstation on Windows 9x systems
setup.iss_jolt	BEA Jolt

To edit a template file, complete the following 4-step procedure.

1. Locate the setup.iss_xxx template files in the templates directory that you created on your hard drive.

   Note: The template files are provided on the BEA Tuxedo software CD. You copied the template files to your hard drive in step 3 in the procedure provided in Using the Unattended Installation Process.

2. Copy the appropriate setup.iss_xxx file to one of the following directories:

   • SETUPDIR\winnt (BEA Tuxedo system)

   • SETUPDIR\inwnt40 (BEA Jolt)

     Rename the copy as setup.iss.

     Note: The setup.iss file must be located in the same directory as the setup.exe file.

3. In the setup.iss file replace the strings shown in angle brackets with values appropriate for your installation. You can use any text editor to edit the files. The bracketed items you need to change in each template file are listed in the tables shown after step 4.

4. After you finish editing your setup.iss file, go to step 7 in the procedure provided in Using the Unattended Installation Process.

   Editing the setup.iss_core_w_lic File

   Replace this bracketed value . . .	With . . .
   szName=<User Name>	The name of the user to whom the product is registered. For example: szName=John Smith
   szCompany=<User's Company Name>	The name of the company to which the product is registered.
   szDir=<Destination Directory for Tuxedo>	The name of the directory in which the core BEA Tuxedo system will be installed. The use of white space in directory names is allowed but not recommended.
   szPath=<Destination Directory for Tuxedo>\udataobj\webgui\	The path name of the directory in which the HTML files for the BEA Administration Console will be installed. This directory does not need to be the directory in which the BEA Tuxedo core system is installed. See Selecting Directories for BEA Tuxedo System Files for details.
   szPath=<Destination Directory for Tuxedo>\udataobj\webgui\java\	The path name of the directory in which the Java applets for the BEA Administration Console will be installed.
   szPath=<Destination Directory for Tuxedo>\udataobj\webgui\cgi-bin\	The path name of the directory in which the CGI programs for the BEA Administration Console will be installed.
   szEdit1=<Tlisten Password>	A tlisten password of your choice.
   szPath=<Directory of license File>	The location of the BEA Tuxedo lic.txt file. For example: szPath=A:\ The setup program must be able to find the license file.

   Editing the setup.iss_core_wo_lic File

   Replace this bracketed value . . .	With . . .
   szName=<User Name>	The name of the user to whom the product is registered. For example: szName=John Smith
   szCompany=<User's Company Name>	The name of the company to which the product is registered.
   szDir=<Destination Directory for Tuxedo>	The name of the directory in which the core BEA Tuxedo system will be installed. The use of white space in directory names is allowed but not recommended.
   szPath=<Destination Directory for Tuxedo>\udataobj\webgui\	The path name of the directory in which the HTML files for the BEA Administration Console will be installed. This directory does not need to be the directory in which the BEA Tuxedo core system is installed. See Selecting Directories for BEA Tuxedo System Files for details.
   szPath=<Destination Directory for Tuxedo>\udataobj\webgui\java\	The path name of the directory in which the Java applets for the BEA Administration Console will be installed.
   szPath=<Destination Directory for Tuxedo>\udataobj\webgui\cgi-bin\	The path name of the directory in which the CGI programs for the BEA Administration Console will be installed.
   szEdit1=<Tlisten Password>	A tlisten password of your choice.

   Editing the setup.iss_ws File

   Replace this bracketed value . . .	With . . .
   szName=<User Name>	The name of the user to whom the product is registered. For example: szName=John Smith
   szCompany=<User's Company Name>	The name of the company to which the product is registered.
   szDir=<Destination Directory for Tuxedo>	The name of the directory in which the BEA Tuxedo client will be installed. The use of white space in directory names is allowed but not recommended.

   Editing the setup.iss_win9x File

   Replace this bracketed value . . .	With . . .
   szName=<User Name>	The name of the user to whom the product is registered. For example: szName=John Smith
   szCompany=<User's Company Name>	The name of the company to which the product is registered.
   szDir=<Destination Directory for Tuxedo>	The name of the directory in which the BEA Tuxedo client will be installed. The use of white space in directory names is allowed but not recommended.

   Editing the setup.iss_jolt File

   Replace this bracketed value. . .	With . . .
   szDir=<Destination Directory for Jolt>	The name of the directory in which BEA Jolt will be installed. The use of white space in directory names is allowed but not recommended.
   szPath=<Destination Directory for Jolt>	The path name of the directory in which the Jolt Server component will be installed.The use of white space in directory names is allowed but not recommended.
   szPath=<Destination Directory for Jolt>\udataobj\jolt\relay	The path name of the directory in which the Jolt Relay Front-end components will be installed.The use of white space in directory names is allowed but not recommended.
   szPath=<Destination Directory for Jolt>\bin	The path name of the directory in which the Jolt Relay Back-end components will be installed. The use of white space in directory names is allowed but not recommended.
   szPath=<Destination Directory for Jolt>\udataobj\jolt	The path name of the directory in which the Jolt Client components will be installed. The use of white space in directory names is allowed but not recommended.
   szText=<Destination directory for Jolt>\udataobj\jolt\relay\jrly.config	The full path name of the configuration file to be used if you are using Jolt Relay as a service.