![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The installers require a JRE/JDK. When prompted by the installer, specify the location of the JRE/JDK.For Microsoft Windows, the SDK Clients installer requires that you install the supported Microsoft .NET Framework package, and the Microsoft Visual J# Redistributable Package.
• Microsoft Windows The entire package is extracted into a temp folder, typically SystemDrive:\Temp or SystemDrive:\Documents and Settings\<user_name>\Local Settings\Temp. The installer requires 165MB of free space in the temp directory.
• Solaris Platforms When a regular (nonroot) user installs a TIBCO Software 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 100 MB of free disk space.
• Directory for Installers Ensure that the downloaded installer files for both the Base and the SDK Clients are located in a user-writable directory and that at least 165 MB of space is available.You can install TIBCO Object Service Broker on either Microsoft Windows or Solaris. However, you must have administrator privileges for the machine on which to install the product. Otherwise, the installer exits. In that case, 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.To enable TIBCO Object Service Broker programs to run properly in a Windows 2008 system, the setting for User Account Control (UAC) must be off.To install the product on a network drive, ensure that the installation account has permission to access that drive.Windows Terminal Server contains two modes: Execute and Install. By default, all users are logged in in Execute mode, which enables them to run the applications. To install TIBCO Object Service Broker for all users, change to Install mode.The best way to install TIBCO Object Service Broker is through the Add/Remove Programs Control Panel applet, which automatically sets the mode to Install during installation and then back to Execute on completion.Alternatively, do the following:
1. Manually change the mode to Install. Type:
2. Change back to Execute mode. Type:Depending on whether you install in Execute mode or Install mode, the installation registry is in your user home directory or in the folder %SystemRoot%\WINDOWS, respectively.You can install TIBCO Object Service Broker as a regular (nonroot) user or superuser (root). Different users can install the same product at different locations.When you install the software (regardless of the installation mode used), you must specify the installation parameters listed below. Determine values appropriate for your site for these parameters before initiating the installation.
Name of the TIBCO Object Service Broker database engine. This uniquely identifies the TIBCO Object Service Broker system. If the name of the database engine is greater than 8 characters, provide the alias name. Use a unique name that is no more than 8 characters. Listening port for the database engine. Use a unique number between 1024 and 65535. DOB IPCKEY
(Solaris only) IPC key value for the database engine. Use a unique hexadecimal value between 0 and 0x7FFF. Listening port for the Execution Environment. Use a unique number between 1024 and 65535. Listening port for the customer-supplied 3270 emulator. Use a unique number between 1024 and 65535. osMon IPCKEY
(Solaris only) IPC key value for the Execution Environment. Use a unique hexadecimal value between 0 and 0x7FFF.
Path to Server Folder in JDK's JRE Used in Open Access Administration Configuration. Defaults to 19985. The installation of the TIBCO Object Service Broker SDK Clients includes an optional Installation Verification Procedure (IVP); to make use of it, the following parameters are required:
The host where the SQL services are running, which will be used by the JDBC and ODBC 64-bit Adapter installation. The port used by the SQL services required for the JDBC and ODBC 64-bit Adapter installation.
If the IVP is invoked as part of a TIBCO Object Service Broker base component installation, all the parameters will be populated with the proper information, with the exception of the Password field, which must be typed in. If the IVP is invoked from an SDK only installation, the parameters may be filled in, but will require reviewing
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |