Installing VisiBroker on HP-UX(Itanium)

This document describes procedures for installing VisiBroker on HP-UX 11iV3 (Itanium) 64-bit operating systems.

For documentation updates, go to http://www.borland.com/techpubs.

Notes:

Preparing for installation

Before installing on HP-UX you should:

Platform and system requirements

Before installing VisiBroker on HP-UX check the platform, system, and JDK requirements. For the latest platform information and system requirements go to http://support.borland.com/kbshow.php?q=29385.

JDK requirements

The installation package for HP-UX does not ship any version of the Java Development Kit (JDK). For information on Java products for HP-UX go to http://www.hp.com/products1/unix/java/.

Important: Before installing on HP-UX, you must have an existing JDK (5.0, 6.0 is supported) installed. Make sure to put the JDK bin directory into the path variable.

To check the location of your JDK and the version, use the following syntax:

$which java
/opt/local/bin/java
$java -version
java version "5.0"

Installing VisiBroker on HP-UX

You can install VisiBroker from the CD or download the software from the Borland web site: http://www.borland.com/products/downloads/download_visibroker.html

Before you install VisiBroker, select the installation method:

  1. To install VisiBroker from a CD:

    1. Mount the CD-ROM.
    2. Enter the following command to launch the installer:
      Install_hp

      The installation wizard launches a separate window.

    3. Select the product you want to install.
    4. Go to step 2 and follow the installation wizard's onscreen instructions. For most options, defaults offered by the installation wizard are acceptable. You can use the Previous button to return to earlier screens and change any information that is incorrect.

    If installing from a downloaded file:

    1. Go to the directory where you downloaded the installer and change the permissions on the installer .bin file to all using the chmod 777 command.
    2. Invoke the appropriate command to launch the installer.
      vb8-<release number>-hp-ia64.bin

      For most options, defaults offered by the installation wizard are acceptable. You can use the Previous button to return to earlier screens and change any information that is incorrect.

  2. Introduction: Read the Introduction and click on Next.
  3. License agreement: Installation and use of VisiBroker requires acceptance of the license agreement.
  4. Choose Install Folder:

    This creates a new installation of Visibroker, or adds components to an existing installation.

    Important: You cannot install this version of VisiBroker on top of previous releases.

  5. Choose Product Components.

    Depending on the Borland Deployment Platform product you are installing, select from the following product components for each feature set:

    VisiBroker Console: GUI and tools for managing VisiBroker ORB and services.

    VisiBroker Core: VisiBroker for Java and C++ development tools and server components.

    Documentation: Suite of online documentation.

    Examples: Example applications for VisiBroker

    Select from the following product components:

  6. Choose VisiBroker Extended Services: If you chose the option to install the VisiBroker Extended Services you purchased, select from the following extended services:

    VisiNotify: An industrial strength, ORB-level implementation of the OMG Event/Notification Service.

    VisiSecure: A framework for establishing secure connections between clients and servers.

    VisiTime: A complete implementation of the OMG Time Service Specification, Version 1.1.

    VisiTransact: A complete implementation of the OMG transaction management solution for transactions with CORBA applications over the Internet or intranets.

    VisiTelcoLog: An OMG compliant implementation of the OMG Telecom Log Service specification version 1.1.2

  7. Choose Install Type: Typical/Custom panel:
    1. Typical - Express install - uses default settings.

      In addition, the typical installation includes the following defaults:

      • Smart Agent port. Also known as the osagent. This port is used by the ORB to communicate with the server. The default is 14000.
      • Agent name. Every agent using the same Smart Agent (osagent) port should have a unique name. The default is the host name.

        Note: The value(s) you enter for the port(s) must be valid for the installation to proceed.

      • Adding the VisiBroker bin directory to your PATH variable: The typical installation does not add the VisiBroker environment variables to your system environment. To add it, chosse the custom install type.

        Note: If you select the default, you may have to manually add certain components to your environment path.

      • Adding the VisiBroker environment variables - If you choose the Custom install type to add the VisiBroker environment variables, the installation sets the BES_LIC_DIR to <install_dir>/var and BES_LIC_DEFAULT_DIR to <install_dir>/license.
    2. Custom: In the custom installation, specifying Smart Agent port/Agent name. You can choose any value between 5000 and 65535. The default value is 14000.
  8. Pre-Installation Summary. Review the displayed information before proceeding with the installation. You can click the Previous button to revisit and change any selections you made except your choice for which product to install. To approve your choices and start installing, click the Install button.
  9. Registration:

    Important: You must register and activate your license in order to use the product. If you have a valid, node-locked license for previous versions of VisiBroker on the same machine where you installed VisiBroker, use the lmadm command-line tool to migrate your previous license for use with the newly-installed VisiBroker software. (see Migrating an existing 6.5 license).

    Note: If you want to register and activate your license later by running the lmadm executable found in the <install_dir>/bin directory. choose "No" and click Next.

  10. In the Make a Selection screen, click on any of the options:

    Have a serial Number: Enter the Serial number.

    Have Activation file: Enter the path for the activation file.

  11. When the installation completes, to dismiss the installer, click Done.

Install log

The installer generates an install log that is written to the root of the installation directory if you installed VisiBroker from CD, or to the folder where the installer file resides if you used a downloaded file to install VisiBroker.

<install_dir>/Borland_VisiBroker_InstallLog.xml

The file is an XML formatted log with installation-specific information, such as errors.

Running the installer without a GUI

The installer is capable of running in a text only mode for UNIX systems. You can invoke the installer with a parameter which specifies the UI mode.

To run the installer in text-only mode:

  1. Change directories to the folder where the installation executable file is.
    <install_file>.bin -i console
  2. When the installer launches, follow the onscreen installation panels.

    The installer will write to stdout and read from stdin. This allows you to telnet from one system to another and run the installer remotely.

Required kernel configuration

HP-UX kernels are typically underconfigured for real world applications, and must be re-tuned.

HP-UX 11.0 is configured by default to allocate only 64 threads to any particular process. The typical symptom of this configuration problem is that the Management Agent and other processes emit errors regarding memory problems or errors regarding an inability to allocate additional threads. You may get the following errors/exceptions:

ias is throwing java.lang.OutOfMemory
or the error logs say:
Unable to allocate threads

This can be corrected by reconfiguring the kernel using the SAM utility. Borland recommends a minimum configuration of 512 threads per process. You should test your application under load to the verify this meets your requirements.

Change user/group privileges from nobody to a valid non-privileged user/group combination

If you are starting VisiBroker as root user/group, VisiBroker automatically switches root to "nobody". HP-UX does not support user/group=nobody. You must change nobody to another valid non-privileged user/group combination for your system. Note, you only need to do this if you are starting from a privileged (root) account.

To change this property directly in the agent.config file:

  1. Go to <install_dir>/var/domains/base/adm/properties/agent.config.
  2. Change agent.superuser.user=nobody to agent.superuser.user=xxx where xxx is the user name.
  3. Change agent.superuser.group=nobody to agent.superuser.group=xxx where xxx is the group name.

Configuring VisiBroker for C++ server, VisiTransact, or VisiNotify license variables

Before running VisiBroker C++ server, VisiTransact, or VisiNotify, you need to set two license environment variables (BES_LIC_DIR and BES_LIC_DEFAULT_DIR). During installation, a shell script is created for you to use for setting these environment variables.

To set the variables:

  1. Open a command window.
  2. Change directory to <install dir>/bin.
  3. Determine the appropriate script for your shell.

    If you are using the Korn or Bourne shell, use the following script to set environment variables:

    vbroker.sh

    If you are using the C shell, use the following script to set environment variables:

    vbroker.csh
  4. To run the script automatically when you log in, add a command to your .profile, .cshrc, or .login file.

Using silent installation

Before invoking the silent installation process, you must first create a text file that contains the properties for configuration settings, such as install directory, server name and JDK home. Each property must be listed on its own line, terminated by a carriage return, with no blank spaces at the end of each line and no blank lines at the end of the file. See the Properties file for silent installation section for more information.

After creating the text properties file, save it as <propertiesfile>.txt, where <propertiesfile> is the filename prefix for your properties file. Now you can invoke the silent installation process using the values specified in the properties file(s).

Note: All properties and values are case-sensitive. When specifying directory and file paths, always use a forward slash.

Properties file for silent installation

The properties file is a plain text file, with each property listed on its own line, terminated by a carriage return, with no blank spaces at the end of each line and no blank lines at the end of the file. The properties can appear in any order in the file.

Properties File Contents for Silent Installation

Variable Value
INSTALLER_UI silent (required). The mode of installation.
USER_INSTALL_DIR <install_dir> (required). The full path name for the VisiBroker. For Red Hat Linux, the default installation directory is /opt/Borland/BDP.
OSAGENT_PORT (optional). Default is 14000.
SERVER_NAME <server_name> (optional). A server name of your choice. Default is host name.
MANAGEMENT_PORT (optional). Sets the Management Port. Default is 42424.
USER_SHORTCUTS The required value is /dev/null.
INSTALL_DOCS Installs the suite of online documentation. Default is YES.
INSTALL_EXAMPLES Installs the example applications for VisiBroker. Default is YES.
INSTALL_TYPE Installs VisiBroker
JVM_JDK_HOME (optional). Sets the JDK path for BES components that host user application code. The default is set to the location where the JDK included with BES is installed.
INSTALL_VBCONSOLE Installs the GUI and tools for managing VisiBroker ORB and services. Default is YES.
INSTALL_VISICORE Installs the VisiBroker for Java and C++ development tools and server components. Default is YES.
VISI_SERVICES When INSTALL_TYPE is VisiBroker, installs any optional VisiBroker Extended Services you purchased. The value is a comma-delimited list that contains one or more of the following entries:
  • VisiNotify
  • VisiSecure
  • VisiTime
  • VisiTransact
  • VisiTelcoLog

For example, if you purchased VisiBroker Edition with VisiNotify and VisiTransact, include the following line in your silent installation <properties> file to install those additional services: VISI_SERVICES=VisiNotify,VisiTransact

For a description of each optional Extended Service, see the Choose VisiBroker Extended Services section in VisiBroker Installation Guide.

CONFIGURATION_SETUP Installs the VisiBroker example configuration. Default is YES.
VBROKER_SETUP (optional)Windows only. The system variable BES_LIC_DIR is set to <install_dir>/var and BES_LIC_DEFAULT_DIR is set to <install_dir>/license. The default is NO.
VISICORE_FEATURES {Java|.NET} This will determine whether you get Visi for Java/C++, Visi for .NET, or both Default is Visi for Java/C++. This is ignored if you specified INSTALL_VISICORE=NO
VB_NET_MODE {Development|Client|Server} which license mode you want for Visi for .NET Default is Development. This is ignored if you did not include .NET in VISICORE_FEATURES
VB_NET_FEATURES {Tools|Add-In}whether you install the tools and/or addin features Default is neither tools nor add-in will be installed. If you specify Add-In, you'll get Tools as well. This is ignored if you did not include .NET in VISICORE_FEATURES

Sample silent installation properties for VisiBroker

This example installs VisiBroker Edition on non-default management and agent ports, and installs several VisiBroker Extended Services.

 INSTALLER_UI=silent
 USER_INSTALL_DIR=/opt/Borland/BDP
 USER_SHORTCUTS=/dev/null
 OSAGENT_PORT=14925
 INSTALL_TYPE=VisiBroker
 VISI_SERVICES=VisiNotify,VisiSecure,VisiTime,VisiTransact,VisiTelcoLog
 MANAGEMENT_PORT=42925

Invoking silent installation

To invoke the silent installation process using the values specified in the properties file:

  1. Open a command-line shell.
  2. Download VisiBroker for HP-UX from the Borland web site.
  3. Extract the installer executable from the tar file you downloaded.
  4. Go to the directory where you extracted the installer and obtain all permissions, or chmod all, where 777 indicates all, to run the installer.
  5. Invoke the silent installation process by entering the following command. Make sure to specify the full path name of the <propertiesfile> file:
    Install_hp-ia64.bin -f <path to properties file>
    where <path to properties file> is the full path of the propertiesfile file.

Note: After silent installation is completed, you need to register and activate the license you received for your product. The license may be in the form of an email from Borland listing one or more serial numbers and license keys, or it may be a license key file sent to you in an email from Borland. If you want to register and activate your license by running the lmadmw executable found in the <install_dir>/bin directory or by launching the wizard from the Tools menu in the Management Console (see the Management Console User's Guide).

Licensing and Registration

Before using VisiBroker, you need to register and activate the license you received for your product. The license may be in the form of an email from Borland listing one or more serial numbers and license keys, or it may be a license key file sent to you in an email from Borland.

Important: For information on how to license your product, go to http://info.borland.com/devsupport/bdpcommon/faq/6.5/licensing/index.html.

If you have a valid, node-locked license for VisiBroker 6.0 installed on the same machine as the newly-installed VisiBroker 6.5, use the lmadm command-line tool to migrate your 6.0 license for use with the newly-installed VisiBroker 6.5 software (see Migrating an existing 6.0 license).

If you have already received a key file in an email from Borland for a product you purchased online or downloaded for evaluation, or if you downloaded a free version of the product, you can use the registration wizard to apply the key file, or you can copy it to the <install_dir>/license directory and it will be applied automatically when you restart your product.

If you have a serial number and key, you can register and activate your VisiBroker product using one of the following registration methods:

Depending on which method you choose, you may be asked to indicate whether you have a Borland Developer Network (BDN) account. If you do not have an account, you will be prompted to create one in the product registration wizard.

If you do not choose the Direct registration method, you will receive an activation file. Simply copy this file into the <install_dir>/license directory and it will be applied automatically when you start your product.

Migrating an existing 6.0 license

To migrate an existing 6.0 node-locked license after installing 6.5:

For information on how to migrate your existing 6.0 license after installing 6.5, go to the Borland website, http://info.borland.com/devsupport/bdpcommon/faq/6.5/licensing/index.html.

Direct registration

To use the Borland product registration wizard for Direct registration:

  1. Select the Direct registration method in the first wizard screen, and click Next.
  2. Indicate whether you have a BDN account, and click Next. If you do not have an account you are prompted to create one in this wizard.
  3. If applicable, enter proxy settings for your internet connection.
  4. Review the summarized information before clicking Next. The wizard monitors and displays the progress of your registration.
  5. When registration is successfully completed, click Next. Then click Finish to close the Wizard.

Email registration

To use the Borland product registration wizard for Email registration:

  1. In the first wizard screen, select the Email registration method and click Next.
  2. Indicate whether you have a BDN account, and click Next. If you do not have an account you are prompted to create one in this wizard.
  3. Review the summarized information before clicking Next.
  4. Copy the content of the Email Registration content pane into an email message addressed to reg@borland.com, and click Next.
  5. To close the Wizard, click Finish. You will receive a product activation file by email.
  6. Copy the activation file into the <install_dir>/license directory, and it will be applied automatically when you start your product.

Web page registration

To use the Borland product registration wizard for Web page registration:

  1. In the first wizard screen, select the Web page registration method and click Next.
  2. Copy the registration key from the Web Registration step of the wizard, then click Finish to close the Wizard.
  3. Start a web browser and open the http://reg.borland.com URL.
  4. In the registration web page, enter your BDN account information and click Login. If you do not have an account, click the Create account link (http://reg.borland.com/srs5/new_user.jsp).
  5. In the Product Registration web page, enter the Serial Number and the Registration Key (from the registration wizard) and click Continue.
  6. Verify the email address to which the activation file will be sent, and click Register. You will receive a product activation file by email.
  7. Copy the activation file into the <install_dir>/license directory, and it will be applied automatically when you start your product.

Telephone registration

To use the Borland product registration wizard for Telephone registration:

  1. In the first wizard screen, select the Telephone registration method and click Next.
  2. From the drop-down list, select the location that is nearest you.
  3. Click Next, then click Finish to close the Wizard.
  4. Dial the number for assistance by telephone and keep the information in the Phone Registration wizard screen on hand.
  5. When you receive your activation file, copy it into the <install_dir>/license directory, and it will be applied automatically when you start your product.

Uninstalling VisiBroker

To uninstall VisiBroker:

  1. Make sure there are no background processes (such as osagent) running during the uninstall.
  2. Change directories to <install_root>/UninstallerData directory.
  3. Enter the uninstall command:
    uninstall
    

    Note: This does not remove files and folders that were created after the installation.

  4. After you run the uninstall command, check the installation directory and remove any unnecessary files and subdirectories.