|
|
Users Guide | Patterns Reference | WebsydianExpress | Search |
|
|
Users Guide | Patterns Reference | WebsydianExpress | Search |
This document describes the upgrade process for upgrading Websydian applications from version 3.1 to 4.0/4.01.
When upgrading from versions prior to 3.1 the upgrade guides for these versions should be applied before this document is read.
The implementation of DOM have been tested with the latest versions of Xerces2, and Xalan which are supplied with this Websydian release. It is recommended to use the supplied versions of Xerces2 and Xalan.
The implementation of DOM now requires MSXML 4.0. Can be downloaded from the Microsoft site.
The required panels which were required in previous versions of TransacXML are now obsolete and have to be removed. If the panels are not removed it can cause memory leaks in the Windows DWA variant and the Java variant will not work properly.
The output parameter ErrorType has been removed from the function DomServices/ErrorPop.
Please make sure to include new library files in the model for generate and build, read more about setting up your AllFusion Plex model.
A new lib file have been supplied for the WsyHttp library model (WsyHttpxxx.lib). Please remember to replace the old file with the new version.
To be sure that the latest lib files are included please read the document setting up your AllFusion Plex model.
When upgrading from Websydian 4.0 it is only necessary to regenerate and build the Websydian application if any of the TransacXML patterns are used.
In Websydian 4.0 a bug has been fixed in the MD2 message digest routine used by the Integrity module. For a discussion on the severity of this issue please refer to Technical Bulletin #2.
When upgrading a Websydian application to 4.0 from a prior version of Websydian care must be taken if the UserManagement pattern has been used. As the MD2 implementation in Websydian has changed, passwords in the user table signed by earlier versions of Websydian will not match passwords signed by Websydian 4.0.
Please refer to Update Passwords in UserManagement Pattern for details on the password issue.
No other actions are required regarding the MD2 update.
The field AuditEventID in the entity WsyAudit/AuditControl.Data.EventType has been assigned length 32 (the old length was 10), and it is thus necessary to transform the database in order to retain the old data, if a Websydian model that uses the Audit pattern is migrated to the latest version of Websydian.
The dispatcher now allows parameters in the first request. The way the dispatcher now determines if the request is the initial request is by detecting the presence of the EventHandler parameter - if it is present, the event handler is called, otherwise the call is redirected to the CallFirstPage function.
The signature check is unchanged, and models using the Websydian Integrity module of course still have the same high level of security as before.
Setting the session timeout value to zero (0) now actually means a zero timeout value, and not infinite. An infinite value is no longer available, but instead set the timeout to a very large value.
For security reasons infinite or extremely large timeout values are not recommended.
In DWA Basic and Pro the smallest allowed value is one (1) minute.
The default session timeout value has been changed from 30 minutes to 10 minutes.
Now the session timeout function SessionControl.Data.Session.Update.ValidateAndUpdateSession.SetTimeOutInterval returns the timeout value in minutes. Before the timeout value was a combination of hours, minutes, and seconds.
It is no longer possible to specify the timeout value in seconds. In the edit point 0 Set own time out interval specify hours and minutes - the function will convert the specified period of time to minutes.
The undocumented function ServiceFunctions.DeleteFile has been deprecated, and instead the function DeleteFile is being used.
Due to an improved memory structure all functions in WsyDom and most in WsyXML have had their input parameter list appended with the field ObjectStoreReference.
This means that it is necessary to ensure the correct mapping when migrating an existing Websydian model that includes TransacXML functionality.
The new parameter ObjectStoreReference should be mapped with the ObjectStoreReference returned by the CreateDocument function.
When initialising the XML environment and documents, the sequence of calls to the functions Initialize, Create, Load, and UnInitialize has been specified precisely. Please refer to the TransacXML section for more details.
The parameters that specify the encoding and version of XML documents have been moved from the InitializeDomRep function to the SaveDocumentToFile function.
This means that the parameters previously specified in the InitializeDomRep function must be specified in the call to the SaveDocumentToFile function.
The commands to start a Token Server no longer exist as the Token Server is replaced by the Websydian Server. Use the commands STRWS and RUNWS to start a Websydian Server. Please refer to the DWA Websydian Server section for more information.
The licensing model of DWA has been changed to include three levels of licenses: Websydian Server Basic, Websydian Server Pro, and Websydian Server Enterprise. Please refer to the DWA licensing section for further information on the licensing model.
Customers with a valid PKA license can upgrade to the Websydian Server Enterprise license free of charge.
Further inheritance must be specified for the Application Service Listener function when upgrading existing DWA/PKA applications. Please refer to the Application Service Listener implementing section for further information.
The session pattern now also scopes the abstract function Abstract.ApplicationServiceListener. If the session pattern is used the implemented listener function should be updated to inherit from the Abstract.ApplicationServiceListener function.
A number of functions in WsyBase have been renamed to have their names better reflect their actual functionality. The functionality of the functions is unchanged.
| Old name | New name |
|---|---|
| EncodeUrl | URLEncode |
| DecodeUrl | TokenizeURL |
| UnencodeUrl | ParseParameterString |
The Token Server has been replaced by the Websydian Server.
Please refer to the DWA section for information on how to start the Websydian Server.
New parameters have been added to the Relay Service, and old parameters have changed. Please refer to Configure and Start Relay Service for more details.
The Log Pattern has been upgraded from Log4J version 1.1.3 to Log4J version 1.2.6. The two versions are not compatible, and it is thus necessary to use the newest version distributed with Websydian.
When upgrading to Websydian version 4.0, all Websydian functions and application functions (Dispatchers, Page Generators, Event Handlers) should be regenerated and built. This is due to changed internal field lengths and parameter lists, changed run-time objects, and changes in the DWA packet protocol.
To ease the process of generating and building the correct functions for a specific model, the objects to generate and build in WsyBase have been moved from package objects into variant specific subject areas, e.g. DWA_iSeries_ObjectsToGenAndBuild and DWA_Win_ObjectsToGenAndBuild. Please refer to the Generate And Build section for more details.
Online documentation - Websydian v6.0