Problem:

Currently there are no documented instructions for upgrading Enterprise Link from version 3.1 to 5.0 on Unix. The customer would like instructions on how to upgrade their system.

Resolution:

There are several Solaris EnterpriseLink customers that have successfully upgraded to EnterpriseLink 5.0.  The process is seamless and fully-compatible.  This means it is possible to continue to use an EnterpriseLink 3.1 repository with EnterpriseLink 5.0.  Database conversion is not required.  However, to use some of the new features of EnterpriseLink 5.0 it is recommended that customers migrate their EnterpriseLink projects to a 5.0 formatted Repository.

   Some of the new features of EnterpriseLink 5.0:

  - compatible with free Apache 1.3.x HTTP Web Server (use in place of iPlanet Web Server)

  - compatible with free MySQL database management system (use in place of Oracle or text file repositories)

  - authoring tool "EnterpriseLink Builder" runs on Sun Solaris

  - all components fully tested with Solaris 8

  To upgrade from version 3.1 to 5.0 (while maintaining the EnterpriseLink configuration settings) perform the following steps:

  1) backup the existing EnterpriseLink 3.1 install directory and the EnterpriseLink start-up script /etc/rc2.d/S92enterpriselink

  2) [optional] download Apache 1.3 from www.apache.org and install it

  3) [optional] download MySQL 3.x or 4.0 from www.mysql.com and install it

  4) install EnterpriseLink 5.0.4 from CD-ROM.  When prompted, indicate a new installation directory (such as /opt/el50).  If you choose to use a different database or web server, change those settings when prompted

  5) download the latest HotFix for Solaris from www.enterpriselink.com -> administering -> downloads -> EnterpriseLink 5.0 -> HotFixes and install it.

  6) manually merge configurations settings.  the new EnterpriseLink configuration file /opt/el50/config/EnterpriseLink.cfg has some new keys in

it.  However, you can merge the EnterpriseLink 3.1 settings into it.   The

easiest way of doing this is edit the new EnterpriseLink.cfg file while looking at a printed version of the old EnterpriseLink.cfg file.  All settings valid in EnterpriseLink 3.1 are valid in EnterpriseLink 5.0

  7) restart the system or issue "/etc/rc2.d/S92enterpriselink start" to start the EnterpriseLink 5.0

  8) ensure that the ODBC DSN ELRepository indicates the EnterpriseLink 3.1 system

  9) test the old project under EnterpriseLink 5.0 using a browser to access "Customized Applications" from the /stdocs web page

  7) [optional] create two Data Source Names, el31repo that indicates the old EnterpriseLink 3.1 repository and el50repo that indicates the new database.  If you are not changing database types (Oracle to MySQL), you should create a new database within the same server.

  8) [optional] initialize the schema on the el50repo database

  9) [optional] using the command line migrate utility migrate the EnterpriseLink project from the 3.1 to 5.0 repositories:

                migrate project1 el31repo el50repo

10) [optional] change the ODBC data source name "el50repo" to "ELRepository"

and test the project as in (9).