Migrating from OSGD 5.x / VLX 3.x to VISULOX 4.x

Since VISULOX 3.3 environments Oracle Secure Gobal Desktop and its components are embedded. A VISULOX installation now consists of three major components: VISULOX, VISULOX PORTAL and VISULOX GATEWAY. VISULOX PORTAL cannot be installed upon existing Oracle Secure Global Desktop environments. This article shows the steps to migrate the SGD 5.40 (or later) datastore, password cache and user preferences and the VISULOX 3.x Database and Keys. In case of a redundant environment with more servers, that are updated in several steps, make sure not to have servers running in the cluster with different VISULOX versions at the same time,

Starting point

SGD 5.40 (or later) can be installed with several SGD Array members and SGD Gateways in front.

VISULOX 3.x is installed on the OSGD Nodes (such a node is called VISULOX Access Node). On pure VLX Nodes, follow the steps for VLX only.

Gateway on separate node

Gateway certificates

Make sure the Gateway certificates and keys are available, otherwise export the certificates from the existing Gateway installation. (See: How to export Gateway frontend certificate including key)

Remove the OSGD Gateway

yum erase oracle-sgd-gateway

Check and delete /opt/SUNWsgdg/ if it still exists after removing the Gateway.

Install VISULOX Gateway

yum install <visulox-gateway-4.x-<version>

Import Gateway certificates

visulox-gateway sslkey import --keyfile <filename> --certfile <filename> [--cacertfile <filename>]

VISULOX PORTAL with and without Gateway

In this case the VISULOX PORTAL Node has a previous version of Oracle Secure Global Desktop: 5.40 (or later).

A backup of the configuration also has to be made with the Oracle Secure Global Desktop Backup and Restore Tool.

Install and run OSGD Backup and Restore Tool

yum install oracle-sgd-backup-5.60.550-1.noarch.rpm

/opt/sgd-backup/bin/backup.sh (note the needed temporary password)

Always the latest version of the OSGD Backup and Restore Tool should be used.

This backup includes the Gateway configuration, if a local Gateway is installed on this server

Remember the password or run tool without encryption!

If there are customized files, e.g. expect scripts or customized OSGD applications under VISULOX Examples, a backup should be made as well.

Remove current OSGD fully (if new environment will be installed here)

Erase all OSGD related packages like oracle-sgd-server, oracle-sgd-gateway, oracle-sgd-webclient:

yum list installed | grep oracle-sgd | cut -f 1 -d " "

yum erase oracle-sgd-server
yum erase oracle-sgd-webclient
yum erase ...

Check and delete remaining folders in /opt after yum erase.

VISULOX 3.x

Copy VISULOX Database and Key

Copy the VISULOX Database and the VISULOX Key to a temporary folder:

mkdir /tmp/update 
./visulox database clean
cp /opt/visulox/data/database/* /tmp/update/
cp /opt/visulox/etc/key /tmp/update/

Check for other customized files, that should be saved before VISULOX will be uninstalled, eg event.sh, customized reports, filecheck.sh, etc

Configurations in pam.d must be saved as well and manually added in the new environmenmt after installation.

It is also necessary to make a copy of the files in the VISULOX Filestore. Have a look at the VISULOX Administration Guide: VISULOX Filestore

Remove VISULOX 3.x (if new environment will be installed here)

/opt/visulox/setup/uninstall.sh -a

Check and delete remaining folders in /opt after uninstall.

Check and delete SGD users (ttasys, ttaserv) and group (ttasys), if they are not removed during uninstall.

Install VISULOX Components on VISULOX Access Node

Install the VISULOX Components, also have a look at the Installation Guide for VISULOX 4.x:

yum install visulox-rte-1.2-<version>.rpm
yum install visulox-4.x-<version>.rpm 
yum install visulox-portal-4.x-<version>.rpm 

On pure VISULOX Nodes the visulox-portal package is not needed.

On VISULOX PORTAL with local Gateways, the visulox-gateway package has to be installed as well.

Restore previous SGD configuration to VISULOX PORTAL

The sgd-restore tool has to take care about the VISULOX PORTAL version. Therefore "VLX_EMBEDDED=true" is added in front of the command or in the shell.

export VLXEMBEDDED=true

Run the restore command:

/opt/sgd-backup/bin/restore.sh --serverfile /opt/sgd-backup/data/sgd-backup-encrypted-<date>.tar.gz --gatewayfile /opt/sgd-backup/data/sgdg-backup-encrypted-<date>.tar.gz

/opt/sgd-backup/bin/restore.sh --serverfile /opt/sgd-backup/data/sgd-backup-encrypted-<date>.tar.gz

visulox-gateway server add-array --name sgd --serverurl https://<sgd-hostname.domain>

In case of a new installtion of the Gateways with imported certificates, the old entries of the Gateways have to be removed on the VISULOX Portal Servers before the add-array command.

Restore previous VISULOX 3.x configuration

Restore VLX database:

chown vlx: /tmp/update/

/opt/visulox/setup/update/migrate.tcl all -source /tmp/update/
/opt/visulox/setup/update/migrate.tcl all -source /tmp/update/ -run

Check/ adjust previous saved customized files, eg event.sh, customized reports, filecheck.sh, pam.d etc

Copy the previous saved files from Filestore back into the related Filestore directory.

Starting / Attaching VISULOX PORTAL and VISULOX

Starting the VISULOX Components

visulox-gateway start
visulox-portal start
visulox start

Attaching VISULOX Service to VISULOX PORTAL

visulox portal attach

Attaching VISULOX Cluster

visulox attach <FQDN vlx node 2>
...
visulox attach <FQDN vlx node n>

If nodes are in different locations and/or zones, have a look at VISULOX Node hierarchy.

Depending on the VISULOX Setup, it can be necessary to adjust the layout of the VISULOX Nodes in the cluster and to start needed VISULOX Services, e.g. FTP, File Exchange, etc.

When finished a COMPLETE RESTART of all services on all nodes is recommended.

Finishing work

Check status

visulox-gateway status
visulox-portal status
visulox status

visulox integrity

VISULOX PORTAL Console

• Adjust the Workspace application icons
• Remove TransitWeb application from Workspace (Transfer from/to the client is now done in the File Transit Area in Workspace)

VISULOX Cockpit

• Assign a category to action scripts manually, where the category is missing and assign these scripts again to the according policies
• Check configured VISULOX Policies, Command Connetcs, Hosts, etc

Check configuration parameters

Check the changend configuration parameters, special sizes are now stored in a different format and have to be set again, even if the presentation is the same.
Use visulox config edit for all parameters with size, that have been changed (visulox config list -changed), e.g. transit.maxuploadsize, transit.quota, etc

Related articles