Upgrade Guide to Websydian Version 3.1

• Websydian 3.1b
  • TransacXML
• Websydian 3.1
  • General
  • iSeries
  • DWA
  • Regenerate and Build Websydian Functions
     

This upgrade guide is aimed at development sites that have already built CA Plex models based on Websydian 3.0 and want to move them to Websydian version 3.1. If the CA Plex model is based on a Websydian version prior to 3.0, the upgrade guides for these versions should be read and the guidelines in all the upgrade guides applied.

Websydian 3.1b

TransacXML

As a result of supporting Java in the TransacXML patterns a number of changes have been made to the functions in TransacXML.

Parameter interface changed

• A new parameter, ObjectStoreReference, have been added to all functions in TransacXML. ObjectStoreReference is returned by DomServices.CreateDocument and is a reference to the object store holding the DOM objects for the newly created XML document.
• Before using the LoadDocument function it is required that the DomServices.CreateDocument function is called in order to create an XML document in memory to load content into.
• The parameters encoding, and version have been added to SaveDocument.
• The parameters encoding, and version have been removed from InitializeDom.

Required panel only needed for Windows implementations

Using the Windows variant of WSYDOM requires that there is a panel function in the call stack when a DOM function is called. Usually this is implemented by adding a panel to the top-level function.

Using the Java variant of WSYDOM a panel is NOT required when calling a DOM function.

Websydian 3.1

General

URL encoding (Windows only)

The function EncodeUrl made use of a Windows API to encode URL's. This API did not work correctly in all cases, so the function now traverses the character string and encodes unsafe characters without using any Windows API's.

If you have not used the option WSYD URL Encode Marked Data in the PageGenerator function then you can ignore this.

Option to disable trim spaces (Windows only)

When a character field is read from an ODBC data source, some data base engines will pad the field with spaces up to the length of the field. To compensate for this Plex (and Websydian) removes trailing spaces before displaying the field value.

If the database engine used does not pad character strings or if the trailing spaces should be sent to the HTML page, a new option (Trim trailing blanks) has been introduced that disables the removal of trailing spaces.

The default behavior is to trim trailing spaces.

Use of new HTTP client in script variant

The script variant now uses the HTTP client in the model WsyHttp rather than using the functions in WsyBase.

The functionality has not changed but the library WsyHttp.lib must be included in the generate and build settings.

Changed source codes scoped under SendHtmlPage

The source codes scoped under SendHtmlPage has been changed so they are capable of sending binary output. The parameter interface is unchanged.

iSeries

Translation tables obsolete

Websydian no longer uses translation tables to translate the HTML templates and incoming requests. Instead information about the code pages to use should be specified in a data area.

Please refer to Set up Character Conversion for further details.

WSYDPATH dataarea has been extended to a length of 200 characters

As a result of the support for placing the documenttemplates in the IFS the dataarea WSYDPATH has been changed to support a longer path.

It is required to replace current WSYDPATH with the one supplied with Websydian 3.1, can be found in the library of the Websydian run-time objects.

DWA

Run-time files renamed

The run-time files for the DWA variants have been renamed.

The new files should be used instead of the old ones when deploying DWA applications generated and built with Websydian 3.1.

Websydian Server

New parameters have been added to the Websydian Server. Please refer to Configure and Start Websydian Server for more details.

Relay Service

All parameters to the Servlet Relay Service must now be specified in a file rather than being configured as servlet parameters. More information can be found here.

Added new and changed existing packets

New packets have been added to the DWA protocol. Therefore it is necessary to re-gen and build the entire application when upgrading and also use the new run-time files.

External libraries

The functions DecodeUrl and HostNameToIp used in the DWA - Windows variant requires that the libraries wininet.lib and ws2_32.lib are added to the Gen & Build section. Please refer to Setting up Your CA Plex Environment.

Objects renamed

Since the acronym DWA is used instead of PKA for the Websydian TCP/IP architecture some Websydian objects have been renamed.

iSeries commands renamed

The following commands on the iSeries platform have been renamed.

Regenerate and Build Websydian Functions

When upgrading to Websydian version 3.1, all Websydian Packages and application functions (Dispatchers, Page Generators, Event Handlers) should be regenerated and built.  This is due to changed internal field lengths and parameter lists as well as changed run-time objects.