|
|
This document describes changes made to the Websydian product that might affect Websydian applications prior to Websydian v6.1 and may require changes to the models or runtime environment.
When upgrading from versions prior to v6.1 the upgrade guides for these versions should be applied before this document is applied.
For more information on what is changed and new features in Websydian v6.1 please read Websydian Version v6.1 - What Is New?.
The issue and the workaround is described here.
If you upgrade an application where you have implemented one or more SoapProcessors, you MUST read the description and implement one of the described workarounds.
The Websydian v6.1 library models can be used with Plex v5.5, v6.0 and v6.1.
Websydian v6.1 is required for running CA Plex v6.1.
All supplied java runtime provided by Websydian now requires java v1.5 or later. Make sure that you upgrade both your development and production environments.
Make sure that you attach the Websydian v6.1 pattern libraries to your group model and that you refer the correct lib and header files supplied with Websydian v6.1
You will be needing new Websydian license keys when upgrading to Websydian v6.1
A complete generate and build of your application is required when upgrading to Websydian v6.1. Please consider upgrading your CA Plex version as well.
New Websydian runtime objects for have been supplied with Websydian v6.1 make sure that you include these objects when deploying your upgraded applications.
The object used for reading templates have been changed for supporting UTF-8 this requires that the CCSID stored on the file holding the template have to be set correctly.
For standard ISO-8859-1 countries use CCSID 01252.
Changing the CCSID of a file can be achieved by using the command CHGATR OBJ('/path/to/myfile.txt') ATR(*CCSID) VALUE(01252)
The IdentifyInputFields scoped to the EventHandler have been made obsolete in Websydian v6.1 you may remove the object that is left behind in your model but it is not required. The IdentifyInpufFields object left behind in your model is set to implement no and will not affect your generate and build.
Changes have been made to the session pattern that requires you to generate and build your session entity and will also require a database upgrade of the session table.
The changes involve IPAddress field length extended to 128 and an additional field SessionTimeout added to the SessionControl.Data.Session entity.
If you are using or inheriting from the field WSYSESS/IPAddress you should note that it has been increased to the length of 128.
We have decided to start the deprecation of the library model SDSTRING why new and improved string functions are now provided in the library model WSYBASE scoped to the function StringFunctions. We recommend that you start moving to the new string functions.
Online
documentation - Websydian v6.5