Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 1 Installing TIBCO Object Service Broker : Installing Multiple Instances

Installing Multiple Instances
You can install multiple instances of TIBCO Object Service Broker on the Windows or Solaris platforms by performing the following:
1.
Run the installer as described in Installing on Microsoft Windows or Installing on Solaris Systems. You must run the installer separately for each desired instance.
2.
/tibco/osb1 – Directory name for the first instance
/tibco/osb2 – Directory name for the second instance
For a Windows-only installation, make the above values unique by suffixing an instance identifier (IID), a numeric value that is incremented by one for each completed installation: DOB Nodename, DOB IPCKEY, MON NAME, and SHAREDMEMADDR. The IID also identifies the Start Menu shortcuts.
3.
For details, see Installation Parameters.
4.
Complete the installation for each instance, and perform any required post-installation tasks for each instance. For example, on Solaris, you must run the osbenv utility for setting up environment variables.
Administration
On both Solaris and Windows, there are different ways that you can administer multiple instances of TIBCO Object Service Broker on the same system. You must set the correct environment in order to administer each instance of TIBCO Object Service Broker. This section contains examples of a few simple approaches.
Solaris
This example uses a script to perform the following:
This example includes three instances: Production, Development, and Test.

 
#!/bin/ksh
echo "Please select OSB instance:"
echo
echo "Production 1"
echo "Development 2"
echo "Test 3"
read answer'?Selection:> '
if test $answer = "1"
then
echo "Starting Production OSB"
export HURON=/tibco/osb
export OS_ROOT=/tibco/osb
export HURONDIR=/tibco/osb/database/huron.dir
export PATH=/tibco/osb/bin:/tibco/osb/utils:$PATH
export LD_LIBRARY_PATH=/tibco/osb/sharedlib
hrncr
echo
echo "Starting Production osMon"
osMon >> /dev/null &
xterm -T "Production OSB" -n "PRD" -sb -bg white &
fi
if test $answer = "2"
then
echo "Starting Development OSB"
export HURON=/tibco/osb1
export OS_ROOT=/tibco/osb1
export HURONDIR=/tibco/osb1/database/huron.dir
export PATH=/tibco/osb1/bin:/tibco/osb2/utils:$PATH
export LD_LIBRARY_PATH=/tibco/osb1/sharedlib
hrncr
echo
echo "Starting Development osMon"
osMon >> /dev/null &
xterm -T "Development OSB" -n "DEV" -sb -bg white &
fi
if test $answer = "3"
then
echo "Starting Test OSB"
export HURON=/tibco/osb2
export OS_ROOT=/tibco/osb2
export HURONDIR=/tibco/osb2/database/huron.dir
export PATH=/tibco/osb2/bin:/tibco/osb2/utils:$PATH
export LD_LIBRARY_PATH=/tibco/osb2/sharedlib
hrncr
echo
echo "Starting Test osMon"
osMon >> /dev/null &
xterm -T "Test OSB" -n "TST" -sb -bg white &
fi
ksh .startosb

 
 
Windows
You can use individual batch files to control each instance of TIBCO Object Service Broker. Three samples are shown below. The first sets the correct environment and starts the Data Object Broker:

 
set HURON=c:\tibco\osb1
set OS_ROOT=c:\tibco\osb1
set HURONDIR=c:\tibco\osb1\database\huron.dir
set PATH=c:\tibco\osb1\bin;%PATH%
hrncr

 
This batch file starts the Execution Environment:

 
set HURON=c:\tibco\osb1
set OS_ROOT=c:\tibco\osb1
set HURONDIR=c:\tibco\osb1\database\huron.dir
set PATH=c:\tibco\osb1\bin;%PATH%
osmon

 
This batch file starts a command prompt with the correct environment set:

 
set HURON=c:\tibco\osb1
set OS_ROOT=c:\tibco\osb1
set HURONDIR=c:\tibco\osb1\database\huron.dir
set PATH=c:\tibco\osb1\bin;%PATH%
color OC
cmd

 
You can group batch files such as these together in a directory associated with an instance of TIBCO Object Service Broker or place them directly on the Windows Desktop.
The installer creates a menu shortcut OSB CMD for each instance of TIBCO Object Service Broker. That shortcut invokes a preconfigured batch file similar to the preceding example and enables you to enter and execute TIBCO Object Service Broker commands against that particular instance.
It is assumed that you execute the TIBCO Object Service Broker commands described in the following sections in either of these two ways:
From a Command Prompt window created by choosing the OSB CMD menu shortcut that corresponds to the instance.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved