QAD QXtend Release Notes > Release Notes for QXO > Release Notes for Version 1.8.2
Release Notes for Version 1.8.2
QXO Server Version: 1.8.2
Date: September 2012
QAD Enterprise Applications Compatibility: eB SP4 through current release
Supported Progress Releases: OpenEdge 10.2B
QAD QXtend Documentation: User Guide: QAD QXtend (70-3190-1.8.2) and Installation Guide: QAD QXtend (78-0952-1.8.2)
New and Changed Features
1 Oracle Support
QXtend now supports QAD EE running on an Oracle database. Both qxevents and qxodb can run on Oracle.
As a part of Oracle support, QXO now supports a QAD ERP source application whose logical name is not qaddb.
The installer has been enhanced to support QXtend installation against an Oracle environment.
2 The option of Require Acknowledgement has been added to the Subscriber Configuration Parameters. This option is available for the subscribers using File Directory Service, Web Service, or QAD BPM as the communication method and QDoc syntax as 1.1.
If this option is set to Yes, QXtend requires acknowledgement of message processing status from the subscriber. When a subscriber message is delivered successfully, the status of the message is set to WAITACK. When QXtend receives the acknowledgement, the status of the subscriber message is updated from WAITACK to DLV, APPERR, or WRN accordingly.
If this option is set to No, no acknowledgement is required by QXtend. The subscriber message status is indicated as DLV when the message is successfully delivered.
3 Enhanced BO/profile dump/load features:
QXO now allows reloading of business objects and profiles (that are not defined by QAD) from XML/XSD files. All links to existing transactions (for example, raw messages and subscriber messages) are retained after the reload.
The listened-to event type information of a business object is included in the dumped BO XML files. When the BO XML files are imported to other instances, the listened-to event type information is automatically loaded.
Fix Description
Internal ID
Issue Affected Versions
The Tomcat security role of QXO has been changed from “manager” to “qadadmin” to keep consistent with QXI.
In the previous version, the Message Monitor could not be reopened in the .NET UI until you logged in to QAD Enterprise Application again. Now this issue has been fixed.
The description of a BO profile can now be dumped and loaded correctly.
In the previous version, a large amount of event records could cause QXtend Event Service to halt. Now this issue has been fixed.
A carriage return can now be included in inner join, filter, and join fields of BO and profile definitions.
Scripts and sess-control.bat have been changed to allow them to be executed from other directories. Previously, they could not start Outbound services successfully if executed from other directories.
In the previous version, the performance of event service could drop when it was registered with specific event types instead of processing all events. Now the performance of event service has been improved.
In the previous version, there could be an error message saying that a duplicate table was found during BO validation. This issue is now fixed by filtering out SQL schema tables when getting the metaschema from the database.
In the previous version, if a Web service response was chunked, the response handler could not process fixed-length responses correctly, and the process timed out. Now this issue has been fixed.
Known Issues
1 Allow Superseded is not supported by BPM subscribers. Do not enable it for BPM subscribers.