You can run the EP 6.1 upgrade script to save certain files in the current installation and unpack the latest infoedition.zip file on top of the 6.0 installation. Everything is replaced, including ASA, Tomcat and JRE.
Before performing the upgrade:
Create a system backup of the machines on which EP 6.0 is installed.
Verify that ASA and Tomcat are running.
Verify that a temporary directory exists on the machine where you are performing the upgrade. If one does not exist, create it; for example, C:\tmp or D:\tmp.
Verify that the %SYBASE% environment variable is set to the Sybase installation directory where ASA and Tomcat are installed.
To verify this variable, open a DOS command window, and enter:
echo %variable%
where %variable% is the name of the variable you want to verify.
Verify that the %TEMP% and %TMP% environment variables are set correctly; for example:
echo %TEMP% D:\temp echo %TMP% D:\temp
Upgrading EP 6.0 to 6.1
The script for performing the upgrade is located in the IE610-UPDT-win.zip file in the root directory of the EP 6.1 CD. Using a zip utility, expand the file to a temporary directory.
Change to the update directory, and open a Command prompt window. Enter:
update-ie6_1
You see “Welcome to the Enterprise Portal Info Edition 6.1 upgrade” and an overview of the upgrade procedure.
Respond to the prompts that display. Each prompt appears on a command line followed by a value in square brackets [ ]. The value in brackets is the default, based on the values set for %SYBASE%.
Press Enter to accept the default value, or enter a new value and press Enter.
Upgrade script prompt |
Default entry or example |
---|---|
Tomcat host name |
The name of the machine where Tomcat is installed; for example:
WARNING! Do not enter “localhost.” You must enter or accept the machine name. |
Tomcat port number |
The port number used to connect to Tomcat.
|
ASA host name |
The name of the machine where Adaptive Server Anywhere is installed. The script displays the machine name you entered for the Tomcat host name as the default; for example:
|
ASA port number |
The port number used to connect to Adaptive Server Anywhere.
|
ASA admin user name |
The administrator user name used to log in to Adaptive Server Anywhere.
|
ASA admin password |
The password the administrator uses to log in to Adaptive Server Anywhere.
|
The input parameters are validated. You see:
Validating host mysysname:4747....Validating database server mysysname:4747 dba/SQL....Validating host mysysname:4040....
Any errors resulting from the validation display, as well as a summary of your input. You are then given a final opportunity to accept the input and proceed with the update.
Current environment is:
APASSWORD = SQL
APORT = 4747
AUSER = dba
TPORT = 4040
AHOST = mysysname
THOST = mysysname
Use this (yes|no) [yes]:
Press Enter if the entries are correct and you want to proceed.
If any of the entries are incorrect, enter no
and
press Enter. The script prompts you again for the upgrade information.
You can correct any of the entries you made.
When you answer yes to the final prompt, the upgrade proceeds. When the upgrade process starts the new Tomcat server, a new Command Prompt window is created.
You see the following output:
....Verify that database is running ....Check current version ....Stopping servers ....Wait for Tomcat to stop ....Wait some more .............................. ....Check disk space ....Back up the current installation ....Checksum the current installation ....Removing old tomcat and jdk ....Deploy update ....Determine changes ....Determine user only changes ....Update global.properties.xml ....Restore some things ....Update oem.xml ....Restore user apps ....Starting ASA Adaptive Server Anywhere Server Ping Utility Version 8.0.0.2065 Ping server failed -- Database server not found. Adaptive Server Anywhere Server Ping Utility Version 8.0.0.2065 Ping server failed -- Database server not found. Adaptive Server Anywhere Server Ping Utility Version 8.0.0.2065 Ping server failed -- Database server not found. Adaptive Server Anywhere Server Ping Utility Version 8.0.0.2065 Ping server failed -- Database server not found. Adaptive Server Anywhere Server Ping Utility Version 8.0.0.2065 Ping server failed -- Database server not found. Adaptive Server Anywhere Server Ping Utility Version 8.0.0.2065 Ping server failed -- Database server not found. Adaptive Server Anywhere Server Ping Utility Version 8.0.0.2065 Ping server failed -- Database server not found. Adaptive Server Anywhere Server Ping Utility Version 8.0.0.2065 Ping server failed -- Database server not found Failed to start Portal Database ....Give ASA time to start ................... ....Update database data ....Update database stored procs ....Restore user added files ....Execute unjar script ....Starting Tomcat ....Give it time to get going .................... ....Verify that Tomcat is running Upgrade complete
When the process finishes, you may see a message listing files that were modified by both you and Sybase. If you see the message, you must manually merge these files to update your installation, as described in “Merging changed files”.
If you encounter problems during the upgrade process, check the update-ie6_1.log in the %SYBASE% directory.
Close the Command Prompt window that was used to start Tomcat during the upgrade process (not the Command Prompt window in which Tomcat is running).
Copyright © 2004. Sybase Inc. All rights reserved. |
![]() |