Online documentation - Websydian v6.0

Users Guide | Patterns Reference | WebsydianExpress | Search
 

Upgrade Guide to Websydian Version 5.6

Contents

Introduction

This document describes changes made to the Websydian product that might affect Websydian applications prior to Websydian 5.6 and may require changes to the models or runtime environment.

When upgrading from versions prior to 5.5SP1 the upgrade guides for these versions should be applied before this document is read.

Pattern changes in Websydian 5.6

Session management pattern changed

The function CallFirstPagegenerator scoped to the EventDispatcher function has a new input field named SessionIdSpecified. The value of this field specifies whether or not a session already exists. So if the value of SessionIdSpecified is *No, then CallFirstPageGenerator will create a new session record in the session table, and if the value is *Yes, no new session record will be created.

In both cases the CallFirstPageGenerator function will make the call to the first PageGenerator function inserted in the edit point 'Call to first page'.

The change has been introduced because of Websydian Express and it should not have any effect on existing applications as the EventDispatcher never calls CallFirstPageGenerator with SessionIdSpecified set to *Yes.

Changes to Distributed Websydian Architecture (DWA)

New Websydian Server licensing system

With Websydian 5.6 the licensing system of the Websydian Server has been changed. This requires that customers request new license files for the Websydian Server.

Make sure to take this into account when planning an upgrade to a production environment.

Changed behavior of mails being sent from Websydian Server and Relay Service

The Websydian Server and the Relay Service servlet can be configured to send e-mails when an error occurs. With Websydian 5.6 only error messages with severity FATAL will be forwarded to the mail recipient.

It is recommended configuring a mail recipient for the Websydian Server, in order to receive information about expiring licenses or any other fatal errors.

Changed behavior of custom error page in Relay Service

In Websydian 5.6 the Relay Service property servlet.errorpage.extension has been changed enabling the administrator to supply a full path for the custom error page.

The error page have to be placed within the scope of the WAR-file where / (slash) indicates the root of the WAR-file. E.g.

servlet.errorpage.extension=/errorpage.jsp

Grace period for Websydian Server Basic and Pro

Now the Websydian Server Basic and Pro automatically enters a grace period of 30 days if the maximum concurrent users limit is exceeded. During the grace period the Websydian Server accepts all user requests and reports that the grace period has been activated in the Websydian Server log file as well as forwards an e-mail to the mail recipient.

Grace period enables the customer to start out by using Pro (or licensed Basic) and when the number of concurrent users exceeds the limit of Pro the customer will be notified to upgrade to Enterprise.

Basic server available in a licensed version

With the introduction of grace period a new Websydian Server type has been introduced. The licensed Basic Websydian Server enables the support for grace period.

Make sure to request a license if deploying the Websydian Server Basic in a production environment. The license will enable the support for a grace period.

The unlicensed Basic server is called Unregistered Basic and does not require a license file.

Parameter for specifying license key has changed for Websydian Server

In previous versions of the Websydian Server the parameter websydianserver.licensefilepath specified the path to the license file.

This has now been changed so the parameter specifies the path AND the file name of the license file.