Copyright © Cloud Software Group, Inc. All Rights Reserved

Installing on Microsoft Windows

Before starting the installation procedure, ensure that your system meets the hardware and software requirements, and that you have reviewed the pre-installation steps.

Installation Files

Installation file names for TIBCO Object Service Broker vary by version number and platform, using the following general format:

TIB_osb_version_platform

where version is the three-digit version number for this TIBCO Object Service Broker release andplatform is an abbreviated form of the hardware platform for which the executable is intended.

The installation files on Windows for this release are the following:

 

TIB_osb_6.0.0_win_x86_64.exe       (Base Product)

TIB_osbC_6.0.0_win_x86_64.exe   (SDK Clients)

 

Download the product from the TIBCO Software web site by following these steps:

1.	Contact TIBCO Software for a password, directory information, and so on.

2.	Connect to the TIBCO Software web site with the required information.

3.	Download the installation file appropriate for your platform.

Choosing an Installation Mode

Table 4 describes the modes for installing the product on Microsoft Windows.

 

Table 4 Installation Modes on Windows

Installation Mode	Description
GUI mode	Allows you to input values in panels. Use the following command: TIB_osb_6.0.0_win_x86_64.exe
Console mode	Allows you to install the software without using a GUI. The installer will prompt you for values. Use the following command: TIB_osb_6.0.0_win_x86_64.exe -console
Silent mode	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. You generate a response file using the following command: <installer> -options-record <responseFileName> where <installer> is the installer executable (or script file on Solaris), and responseFileName is the name of the response file to be generated. For an example, see “Install and Generate a Response File” below. Type the following at the command prompt to use this mode: TIB_osb_6.0.0_win_x86_64.exe -silent -options <responseFileName>
Install and Generate a Response File	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). Add the following statements at the top of the response file so that the silent process takes the proper responses: -G replaceExistingResponse=yesToAll -G replaceNewerResponse=yesToAll To install and generate a response file, use the following command: TIB_osb_6.0.0_win_x86_64.exe -options-record <responseFileName>
GUI or Console mode Install Using a Response File	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. To install using a response file, use the following command: TIB_osb_6.0.0_win_x86_64.exe -options <responseFileName> (GUI mode) TIB_osb_6.0.0_win_x86_64.exe -console                           -options <responseFileName> (Console mode)
Combining Options	You can combine the different available options. For example, to install using Console mode and generate a response file, use: TIB_osb_6.0.0_win_x86_64.exe -console                           -options-record <responseFileName>

Installing the Software

 

The following procedure is for a new installation. For instructions on upgrading from a previous release, see the section titled “Migration from Previous Releases on Open Systems” in TIBCO Object Service Broker Release Notes.

Before proceeding, you should have determined which components you will install as described in Base Components and SDK Clients. If you will install the SDK Clients, ensure that the SDK Clients installer file has been placed in the same folder as the base components installer, and that this folder is writable (before invoking the base product installer). Approximately 5 KB of available space is needed.

Base Components Installation (with or without SDK Clients installation)

To install TIBCO Object Service Broker, perform the following:

1.	Initiate installation by issuing the command of the desired installation mode.

2.	When prompted, accept the license agreement.

If this is the first time you install a TIBCO product, a prompt or panel requests the name of a directory for TIBCO_HOME, in which you could install all TIBCO products. However, you need not install OSB under the TIBCO_HOME umbrella.

3.	When prompted, select New installation. In GUI mode, the following panel displays for this choice:

 

Use the upgrade selection if you would like to bring up an OSB system at release 5.0 or 5.2 to the current 6.0 version level. The HURON enviroment variable should point to the target system to be upgraded.

4.	Specify the installation directory where the product will be installed. In GUI mode, the following panel displays:

On Microsoft Windows, the default installation directory is c:\tibco.

 

5.	Select the components to install. If you wish to install SDK Clients, specify that the SDK Clients installer should be launched. In GUI mode, the following panel displays for these selections:

6.	Specify the database engine parameters (described in Installation Parameters). In GUI mode, the following panel displays:

7.	Specify the system parameters (described in Installation Parameters). In GUI mode, the following panel displays:

8.	When a summary of your installation selections displays, click the Install button.

9.	When the base component installation finishes, the SDK Clients installer is automatically launched. In GUI mode, the panel below displays. If you did not choose to install SDK Clients, go to Step 13.

Otherwise, click the Install button to proceed with the installation of the SDK Clients.

10.	If the following dialog displays, click Yes.

11.	The TIBCO Object Service Broker SDK Clients screen appears. The SDK Client installer installs the JDBC SQL Service Adapter, which requires the parameters shown here. For more information about these parameters, see JDBC Deployment Parameters.

12.	When the SDK Clients installation finishes, the following panel displays:

To run the IVP, specify the field values (described in Installation Verification Procedure Parameters), select the checkbox to launch the IVP, and click the Next button.

If this a base installation, a black MS-DOS window for osMon will display and stay active throughout the IVP processing. An hourglass cursor is shown during this process, which can take approximately one minute.

13.	When the SDK Clients/IVP installation is complete, click the Finish button to exit the installers for those processes.

14.	Click the Finish button again to exit the installation wizard.

SDK Client Installation Only

If you are only installing the SDK Clients, note the following:

•	Use the following installation file:

 

TIB_osbC_6.0.0_win_x86_64.exe

The installer requests an installation folder. This folder can be any folder except that in which a pre-Release 6.0 instance of the TIBCO Object Service Broker base components is installed.

•	IVP  A clients-only SDK installation IVP requires that a separate, independent TIBCO Object Service Broker be running to provide the ‘host connectivity’ that is exercised by the verification process.

Post Installation

After installing TIBCO Object Service Broker, you should perform the following tasks:

Verify Permission Requirements for Data Object Broker Users

As a result of improvements in security in Windows 7 and Windows 2008 Server, the user that starts the Data Object Broker must have the user right "Create Global Objects". By default, only Windows system administrators have this user right. If you choose not to use a system administrator account to start the Data Object Broker, you must use the Security Configuration Manager to modify this local security policy to grant the "Create Global Objects" right to the user that starts the Data Object Broker.

Configure the System

Configure the Data Object Broker and user sessions. If you use distributed data access, set up your communications environment. These procedures are described in subsequent chapters.

Configure an ODBC Data Source (optional)

For Windows installations that include the TIBCO Object Service Broker Adapter for JDBC-ODBC, configure an ODBC data source. For details, see TIBCO Object Service Broker for Open Systems External Environments.

Test the Installation

To verify that TIBCO Object Service Broker is correctly installed, even after the IVP has completed successfully, you should start a session:

•	To establish a background process for your database, start the Data Object Broker. For details, see Starting the Data Object Broker.

•	To establish a background process for your application development, start an Execution Environment. For details, see Starting osMon.

•	To start a development session, start ostty. For details, see Starting ostty. The TIBCO Object Service Broker workbench starts with a user of SYSADMIN.

Uninstalling TIBCO Object Service Broker

If another product is dependent on the product you wish to uninstall, you are informed that you must uninstall the other product first.

Use one of the following to uninstall TIBCO Object Service Broker:

•	Click Start > Programs > TIBCO > TIBCO Object Service Broker x.x > OSB >Uninstall

•	Use Add/Remove Programs from the Control Panel.

•	Navigate to the _uninst directory located in the TIBCO Object Service Broker home directory and invoke the uninstall.exe program.

The uninstallation process will explicitly exclude from removal the DATABASE directories and some binary files that are shared between an independent SDK Client and a base installation.

The installation process creates two subdirectories, _uninst and _uninstc, for the uninstallation components of the OSB Base and SDK Clients. You might be able to start the uninstallation process by invoking the corresponding uninstaller.exe program.

Copyright © Cloud Software Group, Inc. All Rights Reserved