Release Notes for Version 1.6.2
QXI Server Version: 1.6.2
Date: September 2009
QAD Enterprise Applications Compatibility: eB SP4 through current release
Supported Progress Releases: Progress 9.1E, OpenEdge 10.0B, 10.1A, 10.1B, 10.1C, 10.2A
QAD QXtend Documentation: Technical Reference: QAD QXtend (78-0691D) and Installation Guide: QAD QXtend (78-0692D)
1 Installer enhancements. Several significant enhancements have been made to the installer:
• The QAD Deployment Configuration Service (QDCS) must now be used for all installations and upgrades—QAD QXtend can no longer be installed manually.
• The installer now has two installation options: Typical and Advanced. Typical installation allows the product to be installed quickly using default parameter information from the QAD QXtend configuration that is provided with the product. Advanced installation allows a custom configuration to be defined; any default parameter information can be modified using the advanced installation option.
• It is now possible to specify whether to use client/server mode when connecting to the QXO database and/or the qxevents database.
2 WSDL generation. You can now create a WSDL on demand rather than store the WSDL on the server. In addition, each WSDL can contain more than one QDoc definition, allowing multiple APIs to be combined into one WSDL file for a selected receiver. All the request and response schemas are included and can be saved to a client. To generate a WSDL, select a receiver and then click the Generate WSDL button. The wsdl directory no longer exists in the QXtend Inbound web application since WSDL files can be generated using the Generate WSDL button.
3 API publishing. This feature improves the integration between QXI with QXO and Qgen. QXI enables QAD application APIs to be called via Web services. Every API that QXI exposes requires details about the request and response schemas, and these can now be added without having to enter them through the user interface.
4 Native API framework enhancements. The framework now supports customizations using either the .NET UI or the Integration Customization Toolkit (ICT). The framework supports features such as default values, disabled fields, custom validations, additional fields and frames, shadow tables, and custom programs.
5 In addition, the current version contains several general enhancements designed to improve usability.
• Receiver-level authentication. QAD QXtend now allows a receiver to be defined to always require QDocs to contain authentication information consisting of either a user name/password combination or a session ID. In previous versions, useQDocRequestor determined whether the QDoc needed to contain authentication information; this option has now been removed. To enable receiver-level authentication, select the Require Authentication check box in the Modify Receiver dialog box. If the QDoc does not contain authentication information, QAD QXtend will reject the QDoc. If the Receiver Authentication check box is not selected, by default the system uses the authentication information from the connection pool.
• QDoc authentication. In previous versions, QXI verified QDocs by using the credentials in the QDoc only if the system-wide useQDocRequestor setting was enabled; otherwise the credentials specified in the connection pool were used. In the current version, if the QDoc contains authentication information, QXtend always uses this information to authenticate the QDoc. This helps in situations where the application needs a detailed audit trail by user, but you do not want to require all QDocs to contain authentication information.
• Session context. For service interface APIs, the session context is now returned to the caller. This helps speed up processing since the session context now contains the session ID code, which can be extracted from the response and reused in subsequent requests.
1 The QXtend service interface adapter now validates blank dates and invalid months entered in QDocs. If an invalid date is entered, QXI now issues an exception instead of parsing it into a wrong date, as in previous versions. In the current version, it is now possible to send a blank date in a QDoc.
2 The support for pre/post-processing has been enhanced for the Windows platform. Previously, there were occasions when the pre-process and post-process communication would time-out, resulting in inconsistent data being captured in the response QDoc. This fix also ensures messages that extend beyond one message line are captured.
3 Previously, the date format in a QDoc was hardcoded to a month/day/year format. In the current version, the date and numeric format are taken from the active Progress session.
4 If there is an error—in a user name or password, for example—the system now returns messages correctly rather than exiting abnormally.
1 When scopetransaction is set to false and a QDoc contains multiple requests for native APIs, if an error occurs in one request, subsequent requests are not processed.
2 In an AIX environment, if a QDoc has many XML comment lines, the preprocessing program may return an error. You can avoid this situation by removing the XML comments from the QDoc.