|
−
|
Configuration 2: Remote on the same host — Install the software on the host in which TIBCO Object Service Broker for Open Systems is present, but the components do not share configuration files. This configuration would be suitable for implementations in which the Service Gateway for Files will communicate with a Data Object Broker other than the one on the local host.
|
|
•
|
Local (Enablement) — Install the software as part of the TIBCO Object Service Broker system, which is locally installed in the machine.
|
When you run the installer, it detects the presence of TIBCO Object Service Broker for Open Systems if it is installed on the target host. At that time, you are given the choice to install the software with the base product (shared configuration files), or separately from the base product (components do not share configuration files).
|
•
|
GUI mode — in this mode, the installer presents panels that allow you to make choices about product selection, product location, and so on. When you invoke the installer by double-clicking on the icon, GUI mode is used.
|
|
•
|
Console mode — this mode allows you to run the installer from the command prompt or terminal window. This is used primarily for non-Windows environments.
|
|
•
|
Silent mode — installs without prompting you for information. To use this mode, you must first generate a response file (using GUI mode or Console mode) that contains the input values you want to use for the installation. For details, see Installation Modes — Using a Response File.
|
The package is extracted into a temp folder, typically SystemDrive:\Temp or
SystemDrive:\Documents and Settings\<user_name>\Local Settings\Temp.
When a regular (non-root) user installs a TIBCO product, the installation registry is maintained in the user's home directory. As more products are installed, entries are added. The user's home directory must at least have 500 KB of free disk space.
You must have administrator privileges for the machine on which the Service Gateway for Files is installed. If you do not have administrator privileges, the installer exits. You must then log out of the system and log in as a user with the required privileges, or request your system administrator to assign the privileges to your account.
When installing on Windows terminal server, there are two modes: Execute and
Install. By default all users are logged on in
Execute mode, which allows them to run the applications. When you want to install the Service Gateway for Files for use by everyone, the Administrator should change to
Install mode.
The best way to install the Service Gateway for Files is to use the Add/Remove Programs control panel applet, because this automatically sets the mode to
Install during the installation and then back to
Execute at the end.
If you install in the Execute mode, the installation registry is maintained in your user home directory. If you install in the
Install mode, the installation registry is maintained in the
%SystemRoot% folder.
You must invoke the installer from a TIBCO Object Service Broker-enabled CMD prompt or from a CMD shortcut created by the base installer, in which the TIBCO Object Service Broker environment has already been set.
The Service Gateway for Files can be installed by a regular (non-root) user and super-user (root). Different users can install the same product at different locations.
Before starting the installation procedure, ensure that your system meets the hardware and software requirements, and that you have reviewed the pre-installation steps.
After starting the installer and accepting the license agreement, you are prompted to specify the
TIBCO_HOME directory (if not detected by the installer). Typically, this is the top level installation directory for all TIBCO products; however, you can specify a different directory if desired.
This mode allows you to install the software in a non-Windows environment. The installer will prompt you for values. Type the following at the command prompt:
To use this mode, you must first generate a response file (using GUI mode or Console mode) that contains the input values you want to use for the installation.
where <installer> is the installer executable (or bin file on Solaris), and
<filename> is the name of the response file to be generated. For an example, see
Installing and Generating a Response File below.
You can generate a response file during installation which you can later use to invoke the installer with the selected values as default values (GUI mode) or as selected values (silent mode).
You can use a previously generated response file for installation. For non-silent modes, the response file determines the defaults that are presented. For silent mode, the response file determines what will be installed.
|
•
|
Enablement Installation To make the enablement choice available for installation, you must have installed a TIBCO Object Service Broker base system. Call the installer program from a TIBCO Object Service Broker-enabled CMD prompt or from a CMD shortcut created by the base installer, in which the HURON environment variable is already set.
|
|
•
|
Standalone Installation Standalone installation is the default in all other cases if no TIBCO Object Service Broker base system has been installed. This type of installation applies regardless of whether or not other standalone installations exist in the TIBCO_HOME folder.
|
After installing Service Gateway for Files, you must perform the tasks listed below. The directory names referred to in the following instructions are subdirectories of either OS_ROOT on Windows or ${OS_ROOT} on Solaris if you share configuration files with the base TIBCO Object Service Broker for Open Systems, or in the directory you specified during the install if you do not share configuration files.
|
|
You must modify the batch file launchFilesgw.bat, in the utils directory, to supply osMon with a NAME matching the NAME parameter value you choose for Service Gateway for Files in mon.prm.
|
|
|
You must modify the shell script launchFilesgw, in the utils directory, to supply osMon with a NAME matching the NAME parameter value you choose for Service Gateway for Files in mon.prm.
|
If another product is dependent on the product you wish to uninstall, you are informed that you must uninstall the other product first. The directory names referred to in the following instructions are subdirectories of either
OS_ROOT on Windows or
${OS_ROOT} on Solaris if you share configuration files with the base TIBCO Object Service Broker for Open Systems, or in the directory you specified during the install if you do not share configuration files.
