Release Notes for Version 1.4
QXI Server Version: 1.4
Date: September 2007
MFG/PRO Compatibility: eB SP4 through current release
QAD QXtend Documentation: Technical Reference: QAD QXtend (78-0691A) and Installation Guide: QAD QXtend (78-0692A)
1 You can now configure QXI to generate and distribute e-mail alerts that are raised by QXI for events relating to specific receivers, domains, and APIs. Similar e-mail alert functionality—providing alerts for subscribers and profiles—is available in QXO.
2 You can now synchronize data between instances of QAD applications or with external systems using QXtend. QAD QXtend version 1.4 introduces several enhancements that will support interoperability with the QAD Enterprise Applications 2008 (QAD 2008) Financials module when available.
• A service interface layer has been developed to permit QDocs to be routed through a new service interface adapter. To support this routing, a receiver must be associated with an API that uses the SIAPI adapter route and the AppServer ubroker.properties setup file must be modified to include the service interface.
QXO can now accept (and publish) raw business object event data from modules such as the QAD 2008 Financials module. See Release Notes for Version 1.4
• A new QDoc standard has been introduced. See point 3 below.
3 To make QDocs compliant with the industry standards for message identification used by the service interface layer, the QDoc syntax has been extensively modified. In addition, Progress also has adopted XML notation that required modifications to the existing QDoc standard. QAD QXtend release 1.4 supports both QDoc 1.1 and 1.0 syntax versions.
The new QDoc 1.1 syntax specification introduces numerous modifications, including the following:
• The SOAP header has been modified in several ways.
• For both QDoc standards the namespace for the SOAP envelope has changed from http://www.w3.org/2002/06/soap-envelope/ to http://schemas.xmlsoap.org/soap/envelope/. The original namespace has been obsoleted. The SOAP encoding namespace also has been removed from both SOAP envelopes.
• The receiver was previously passed as a parameter in the URL in the receiverId node. It is now the third entry in the URN of the To node.
• The suppressResponseDetail parameter in the 1.0 syntax was an attribute of the root node for the QDoc body. In the 1.1 syntax, this attribute is now a node in the SOAP header ReferenceParameters section.
• The value of SOAP header attribute mustUnderstand has changed from true to 0.
• Arrays in the QDoc 1.0 syntax were represented like this:
In the QDoc 1.1 syntax, array structures are represented in QDocs by having multiple entries of the node. Indexing is achieved by the order in which the node appears in the XML. For example, the above array is represented in the 1.1 syntax like this:
For details about the QDoc 1.1 syntax specification, see Chapter 20, “QDoc Structure Reference,” and Chapter 23, “QDoc Specifications and Standards” in Technical Reference: QAD QXtend.
4 QXI has a new GUI-based installation program designed to simplify the installation and deployment of the QAD QXtend components. The installation supports single-tier and multi-tier mode installation. The installation has a Parameter Service that allows an administrator to enter parameter information that describes their existing environment. The settings stored in the Parameter Service are used to guide the QXtend installation and deployment behavior. For details see Installation Guide: QAD QXtend.
5 The number and type of exception codes has been enhanced. There are now codes for transformation, internationalization, and reflection exceptions. New codes have been added for event, connection, queue, transaction, adapter, QDoc, configuration, and failure exceptions.
6 QXI now supports Secure Sockets Layer (SSL), both self-trusted and true-trusted certificate.
7 Operation tags are now validated in the request QDoc. This means that QXI validates that the operation tag is A, R or S.
1 If you intend to use the service interface layer, first obtain a patch for Progress from QAD Support. This patch is only available for Progress OE10.1B02.
2 If you use suppressResponseDetails, only the error message is returned—not any associated traceability details, such as sales order numbers for sales order transactions, for example. There are two solutions:
• Use the Message Monitor to trace into the affected record.
• Call QAD Support for a hotfix.
This known issue only affects integration into third-party applications, not QAD-to-QAD applications.
3 If you use scopeTransaction and an error occurs during processing, the transaction is not backed out correctly. If this happens, call QAD Support for a hotfix.