![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
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 file names for TIBCO Object Service Broker vary by version number and platform, using the following general format: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.Table 5 describes the modes for installing the product on Solaris.
Table 5 Installation Modes on Solaris Allows you to install the software without using a GUI. The installer will prompt you for values. Use the following in a terminal window: 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. See Install and Generate a Response File below for details.The silent installation ivocation varies based on whether you are performing an OSB and clients combined installation, or are installing clients only.
• Perform these steps if the JDBC Deployment parameters to be used in the OSB and SDK Clients combined silent installation have non-default values:
1. Create a text file, JDBC-DetailsFileName, containing the JDBC values to be used for the silent JDBC Deployment. The text file must use the format:where name-of-host is the name of the machine where the service will run and path is the location of the JDK as shown here:JDK_HOME is the full root path to the Java Development Kit installation../TIB_osb_6.0.0_solaris.bin -silent -options responseFileName -V V_JDBC_DETAILS=JDBC-DetailsFileName
• Perform these steps if you are installing SDK Clients only and the response file and JDBC Deployment parameters were generated using console mode:
2. 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). 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 determine the defaults that are presented. For silent mode, the response file determines what will be installed. You can combine the different available options. For example, to install using Console mode and generate a response file, use:
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.
When using GUI mode, the Windows and Solaris installers use similar steps and panels. For examples of these panels for a Windows installation, see Installing the Software.
4. Specify the installation directory where the product will be installed. The default installation directory depends on who performs the installation:
−
− For non-root users, the default installation directory is /<myhome>/tibco, where <myhome> is the home directory of the user.
5. Select the components to install. If you wish to install SDK Clients, specify that the SDK Clients installer should be launched.
8.
9. When the base component installation finishes, the SDK Clients installer is automatically launched. 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.
11. When the SDK Clients installation finishes, the IVP installer is automatically launched. 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 window for osMon will display and stay active throughout the IVP processing.
12. When the SDK Clients/IVP installation is complete, click the Finish button to exit the installers for those processes.
13. Click the Finish button again to exit the installation wizard.The installer will request an installation folder. This folder can be any folder except those where the TIBCO Object Service Broker base components have already been installed.GUI mode – TIB_osbC_6.0.0_solaris.binConsole mode – TIB_osbC_6.0.0_solaris.bin -consoleAfter installing TIBCO Object Service Broker, you must run a utility (osbenv) for setting up environment variables.installdir/utils/osbenvThe utility must be run with “. ” (period, blank) preceding the command (you can also add this to your .profile file).After installing TIBCO Object Service Broker, you should perform the tasks described in this section.Solaris system parameters are in the /etc/system file. Consider adjusting the following parameters in this file to allow for a very large number of TIBCO Object Service Broker users on one system, to provide the semaphores required for each user:
• SEMMNS — the maximum number of semaphores on the system — should be set to its default value plus the value of the MAXUSERS Data Object Broker parameter.
• SEMMSL — the maximum number of semaphores per set — should be set to the larger of its default value or the value of the MAXUSERS parameter.
• RLIM_FD_MAX — the maximum number of file descriptors for the system — must be increased to allow for the required number of users plus a contingency amount, because a file handle is used for each user logging in.See TIBCO Object Service Broker Parameters for information about the MAXUSERS Data Object Broker parameter.Use of the SCHEDULE statement for asynchronous processing results in at-jobs being submitted for immediate execution to queue b under the control of cron. You might need to update the characteristics for cron queue b in the /etc/cron.d/queuedefs file to increase the number of at-jobs that might run simultaneously. Set the maximum number of simultaneous jobs for queue b to its default value and the anticipated system-wide number of at-jobs submitted with the SCHEDULE statement that must execute concurrently.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.
• 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.If another product is dependent on the product you wish to uninstall, you are informed that you must uninstall the other product first.Navigate to the _uninst directory located in the TIBCO Object Service Broker home directory and invoke the uninstaller.bin program.The installation process creates two subdirectories, _uninst and _uninstc, for the uninstallation components of the OSB Base and SDK Clients. If you install SDK Clients along with the OSB Base, first run uninstaller.bin from the _uninstc subdirectory. Uninstallation for the OSB Base does not proceed if you do not adhere to that sequence.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |