Upgrading WebsydianExpress for Java to version 3.5

Before upgrading

Before you perform the upgrade as described in this document, ensure that you have read the what's new document and the general upgrade guide for version 3.5 and have investigated all issues that are relevant for your installation.

Note that this document only describes upgrading from version 3.0.x to version 3.5. If you are at an earlier version, you must start by upgrading to version 3.0.

Your current version can be found by opening the WebsydianExpress administration interface and looking at the Welcome page. At the top and at the bottom you will find the current version of your WebsydianExpress installation.

Download

Go to the WebsydianExpress download page and download the zip-file: Upgrade WebsydianExpress for Java to version 3.5.

Unzip this file to your disk. This creates a folder structure:

The database folder holds two subdirectories iSeries and SQL these directories holds programs for updating the database objects of either iSeries or Microsoft SQL.

The html folder holds update html templates for the WebsydianExpress administration interface.

The folder webcontainer holds updated files for the Java servlet to be used to update your deployed application. 

The Upgrade folder contains files that is used to upgrade the administration sites.

Stop WebsydianExpress and perform a complete backup

Before starting the upgrade stop WebsydianExpress and do a backup of the entire WebsydianExpress installation folder. It is also recommended to do a backup of the database.

Upgrade the WebsydianExpress database

Depending on the database platform you are using follow the description below on how to upgrade your WebsydianExpress database 

Upgrade your iSeries database using the install program supplied

The easiest way to upgrade your iSeries WebsydianExpress database is to run the WXPJ35UPG.EXE program found in the database\iSeries folder.

1. Press "Next" on the first page shown.
2. Select "Standard", Press "Next".
3. Select "Use TCP/IP", specify the name of the iSeries and the iSeries user and password. Press "Next".
4. Press "Next" to start the installation.
   The installation will create a library named WXPJ35UPG. If this library already exist on the iSeries, you will be asked to either overwrite the existing library or to specify another name for the library to install.
5. Press "Finish" to exit the tool.

Run the upgrade command

Add the library you have restored to to the library list of your interactive session.

Run the command WXPUPGRADE, press F4 to specify the following parameters:

DBLIB

Specify the database library of the current WebsydianExpress installation. This is the library that contains the WebsydianExpress database files. One of the files it contains is a physical file called WSBSCRP.

The upgrade command will create new physical and logical files in this library.

Upgrade your Microsoft SQL database using the install program supplied 

Run the install program UpgradeDB.exe program found in the database\SQL folder.

1. Press "Next" on the first page shown.
2. Specify database server where your WebsydianExpress database is located, a user with authorization to create tables and views, and the name of the database catalog where the database is located.
3. Press "Next"
4. Press "Install"   

Upgrade WebsydianExpress administration HTML templates

Locate your html templates used by WebsydianExpress and copy all files located in the upgrade folder html to your html folder, overwriting any existing files.

Upgrade and redeploy the WebsydianExpress servlet

WebsydianExpress for Java is deployed as a servlet and the upgrade requires you to update a number of files within the servlet all ready deployed.

Updating your WebsydianExpress servlet depends on your scenario of deployment, below is a number of scenarios that should help you decided how to update.

WebsydianExpress running on Tomcat

Manually copy the new and updated files located in the upgrade folder webcontainer to your Tomcat webapps folder where the WebsydianExpress is deployed. By default the target folder of these files are C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\express30 but this might vary.

If you deployed the WebsydianExpress servlet as a WAR file you will need to update the WAR file as described below.

Special care is needed as you copy the new jar files to the WEB-INF/lib folder. Please make sure that there is no duplicate jar files with different version numbers; make sure that you delete the jar files with the lowest version number.

WebsydianExpress deployed using WAR file on WebSphere, Servlet Exec or Tomcat

Start by obtaining your current version of your deployed WAR file. Normally the WAR file will be available on the server where you deployed the WAR file in the first place.

1. Rename the WAR file to file suffix ZIP
2. Unpack the ZIP file to a folder of your choice using the standard Windows tool to do so. (Right click the file and select extract to)
3. Copy the files located in the upgrade webcontainer to the unpacked structured into the root of the folder structure.
4. Pack the ZIP file using the standard Windows tool. (Right click the file and select send to and then compressed (zipped) folder
5. Rename the ZIP file to file suffix WAR
6. Your WAR file is now ready to be redeployed to your WebSphere, Servlet Exec or Tomcat

Upgrade the administration interface

As version 3.5 introduces a new administration menu item, you need to upgrade the administration interface using the "Update Admin" menu item for each of your sites.

1. Start WebsydianExpress and open the administration interface of any available sites. Go to Utilities→Update Admin.
   If you get a warning about a digital signature, just accept it.
2. Press the "Open import file" button.
   This opens a file selector, select the file Administration Interface Upgrade - v3.5.txt in the Upgrade folder (in the structure that was created when you unzipped the downloaded file). Press "Open" to select the file.
3. Press the "Import" button to perform the import - this import can take some time.
   After the import has finished, refresh the administration menu (press F5 or Ctrl-F5) and check whether the section Site Structure contains the "Authorized Events" menu item.
4. Access the "Authorized Events" menu item to ensure that the new html templates for this menu item have been installed in the html-folder.