For this example of a distributed environment setup, machine 1 (M1) is the machine where Adaptive Server Enterprise and EAServer for Enterprise Portal 5.x are installed.
Machine 2 (M2) is the machine where EAServer for Enterprise Portal 6.0 is installed.
Machine 3 (M3) is the machine where Adaptive Server Enterprise for Enterprise Portal 6.0 is installed.
Backing up and restoring the databases
Before upgrading the portal and security databases, you must back up the databases from your Enterprise Portal 5.x installation and restore them on your Enterprise Portal 6.0 installation. For information about backing up and restoring databases, see chapter 27 “Backing and Restoring User Databases” of the Adaptive Server Enterprise 12.5 Administrative Guide, Vol 2.
Dump the portal database (portaldatabase) from your Enterprise Portal 5.x installation on machine 1.
Dump the security database (entldb) from your Enterprise Portal 5.x installation on machine 1.
Create the portal database devices portalData with a size of 300MB and portalLog with a size of 100MB on machine 3.
Create the new portaldatabase on the database devices created in the previous step.
Load the databases from the dump created in step 1.
Create the entldb database devices securitydata with a size of 300MB and securitylog with a size of 100MB on machine 3.
Create the new entldb database on the database devices created in the previous step.
Load the entldb database created from the dump created in step 2.
Upgrading the security database
Copy the .enk file located in $SYBASE/Security-2_5 from your Enterprise Portal 5.x installation on machine 1 to $SYBASE/Security in your Enterprise Portal 6.0 installation on machine 2.
Create a tmp directory under $SYBASE/Security under your Enterprise Portal 6.0 installation on machine 2.
Copy the security.properties file located in $SYBASE/EAServer/java/classes/com/Sybase/ep/security from your Enterprise Portal 5.x installation on machine 1 to the tmp directory you created in the previous step on machine 2 and point it to the location in the response file.
Create a upgrade.res file to match your environment and place it in the Enterprise Portal 6.0 setup under $SYBASE/Security/bin. See “Sample response file (upgrade.res)”.
Go to $SYBASE/Security/bin, and remove the existing acdb database if it exists by entering:
securetool.sh removedb @upgrade.res
After running this command verify that the acdb database and associated device files are gone.
Securetool cannot remove the device files when running
over a network.
Create a new acdb by entering:
securetool.sh createschema @upgrade.res
This creates a new acdb without any data in it for upgrading into.
Upgrade the acdb database by entering:
Securetool.sh upgradedb @upgrade.res
If you have not upgraded the EAServer to Enterprise Portal 6.0, you must perform this step. At the command line, enter:
Securetool.sh deploymw @upgrade.res
Then, enter:
Securetool.sh deploysm @upgrade.res
Upgrading the portal database
Execute the scripts located in $SYBASE/PortalStudio/database/ASE in your Enterprise Portal 6.0 installation against the new databases created in the procedure above. The scripts are:
Catalina_upgrade-to_5.1.1.sql
Catalina_upgrade5.1_to_6.0.sql
Catalina_stored_procs.sql
Running InstallStudioSecurity
Before running the installStudioSecurity.sh, set JAVA_HOME and verify the connection cache is pointing to the newly upgraded Security database.
Start Jaguar Manager and log in as “jagadmin.”
Click Connection Cache, then click on secDboCache.
The cache properties window opens. Verify the connection cache is pointing to the security database you just upgraded.
From the machine where Enterprise Portal 6.0 is installed, go to $SYBASE/EAServer/Repository/WebApplication/onepage/bin/InstallStudio.sh and execute:
InstallStudioSecurity (iiop://<host>:<port> <username> <password>)
Where <host> is the name of the machine where EAServer is installed, <port> is the port number for EAServer (the default is 9000), <username> is the security admin user (the default is “pso”), and <password> is the password for the security admin user (the default is “123qwe”).
