Update installation under Solaris systems

This section describes how you can update the proxy container and Management Console installation under Solaris systems. If you obtain new software, then start the master installation and install the new products (see Installing BeanConnect under Solaris systems).

Starting the update installation

The update installation is performed in the same way as a new installation.

Switch to the directory in which the component, you want to update, is located and start the installation procedure with the following command:

<BC_inst_dir/shsc/install.BeanConnect

As in a new installation, the procedure displays a menu listing the two components that can be installed. You select the components for which you want to install an update:

Configuration Options
1 BeanConnect Proxy Container
2 Management Console (Administration Tool)

The installation procedure recognizes when you are in the directory that already contains one of the components and checks whether the version is updatable. If it is, you are asked whether you want to perform an update installation or overwrite the existing version (new installation).

An update installation is performed for the selected BeanConnect components.

BeanConnect proxy container

1. The proxy container home directory is copied and saved in the directory <BC_home>/<proxy_cont_name>.save. This directory is not changed by the update installation. All the old configuration data is retained.

2. If required, the existing proxy container can be uninstalled. The following applies depending on whether or not the old and new directories are identical:

   • If the old and new directories are identical then the old proxy container is renamed, a new proxy container is installed and the data is transferred from the old proxy container.

   • If the old and new directories are different then a new proxy container is installed. The data is then transferred from the old proxy container.

3. The old configuration is moved to the new proxy container.

Under Solaris systems BeanConnect proxy container may only run in an 64-bit environment!

The update installation of a BeanConnect V3.0B proxy container 32-bit to a BeanConnect V6.5 proxy container 64-bit is only possible in two steps.

1. update installation BeanConnect V3.0B proxy container 32-bit -> BeanConnect V3.0B proxy container 64-bit and afterwards
2. update installation BeanConnect V3.0B proxy container 64-bit -> BeanConnect V6.5A proxy container 64-bit

Management Console

1. The Management Console home directory is copied and saved in the directory <BC_home>/<console_name>.save. This directory is not changed by the update installation. All the old configuration data is retained.

2. The following applies depending on whether or not the old and new directories are identical:

   • If the old and new directories are identical then the old Management Console is renamed, a new Management Console is installed and the data is transferred from the old Management Console.

   • If the old and new directories are different then a new Management Console is installed. The data is then transferred from the old Management Console.

3. The old configuration files are read from <console_name>.save and copied to the new Management Console home directory.