QAD QXtend Release Notes > Release Notes for QXO > Release Notes for Version 1.6.3
Release Notes for Version 1.6.3
QXO Server Version: 1.6.3
Date: March 2010
QAD Enterprise Applications Compatibility: eB SP4 through current release
Supported Progress Releases: OpenEdge 10.1C, 10.2A
Note: If QAD QXtend is installed on an HP-UX IA64 machine with Progress OE10.2A01 or OE10.2A02, a Progress hotfix needs to be applied to avoid issues with QXO services. Please check the Platform Guide and make sure that the hotfix is applied.
QAD QXtend Documentation: User Guide: QAD QXtend (78-0691E) and Installation Guide: QAD QXtend (78-0692E)
New Features
1 Installer enhancements. Several significant enhancements have been made to the installer:
The installer allows the loading of an initial default configuration at install time. This provides an easy out-of-the-box solution to common interoperability scenarios.
The installer allows the user to perform an in-place upgrade without the need for a first successful installation.
The installer allows the user to pause, stop, restart and re-run steps within the installation. This feature provides better control on installation.
QXtend Message Monitor is automatically installed as a .NET UI plug-in.
2 Qxtend Licensing. A new QXtend installation now defaults to a QAD & Approved QAD Partner Free Use license, under which QXtend Outbound can send any QDocs to QXtend Inbound without any license restrictions. Previously, the default license was called Data Synchronization.
3 Configurable Event Services. You can now configure event services to only process specific event types so as to create dedicated event service instances for high-priority events, allowing them to be processed as soon as they arise.
Previously, an event service processed all events for a source application but not selected event types, making it impossible to prioritize important events.
Event service configurability is achieved through the new event type registration feature that lets you register specific event types of a source application with an event service for processing. A new Event Registration page is available for each registered source application under each event service instance in the QXO administrative UI.
This enhancement also entails the following changes and impacts:
If an active event type is not registered with any event service, it still generates events in the qxevents database but they will never be processed. To prevent unwanted events from accumulating in the qxevents database, the system stops any event service that has a registered source application with active event types not registered with any event service. When you start an event service, the system checks whether all the active event types within each of its registered source applications are registered with an event service. If not, the system shuts down the just-started event service and displays a warning message.
Business object groups used to ensure that designated groups of business objects are published in chronological sequence. Now with the new configurable event services enhancement, this is only true when all active event types within the business object group are registered with the same event service.
In the Event Types overview screen, a warning icon is displayed next to any active event type that is not registered with any event service.
The Validate Configuration utility displays warning messages for:
Every active event type that is not registered with any event service
Every business object group in which active event types are not all registered with the same event service
In the business object subscribers report, a warning icon is displayed next to any event name that is not registered with any event service.
4 Encode password before sending out message. QXO can now encode the password for a subscriber.
5 Changes to data sync profiles. Data sync profile names have been changed to the same as QDoc names. Also, through changing the QDoc version, the same profile can be used for data sync through UIAPI or SIAPI (if corresponding SIAPI exists). Because of this, QXtend Outbound now only keeps one default data sync profile for a BO even if the data can be synchronized using both UIAPI and SIAPI.
Fix Description
Internal ID
Issue Affected Versions
QXtend Outbound now does not cause unspecified locks between client sessions. Previously, this could happen and no message was displayed on the client. The user would just have to wait until the other user completed the transaction.
QXtend Outbound can now connect to a source application database in shared memory mode under Windows. Raw messages can be extracted as expected.
Memory leak issue in Event Service and Message Publisher has been solved.
Message Monitor can now display correctly when a profile is assigned to multiple subscribers with tokens.
The QXO Session control query option can now show DEAD sessions. Previously, it did not show DEAD sessions unless the QXO dashboard had first been accessed.
Email alerts now works well for messages with Detect Operation turned off on profile.
A correct Qdoc can be generated for a 1.0 Qdoc syntax when the Qdoc Name and top level node name are the same.
Previously, events related to multiple business objects did not always result in raw messages and some events were left unprocessed. Now this has been solved and no events are left pending forever.
Previously, fixed value expressions referencing a field with an unknown value always returned errors. Now the system always changes the unknown value to string “?”
Performance of archive has been improved by performing a full table scan on the published message table.
Previously, when Detect Operations was turned off, in some situations, not all rows were published. Now this has been solved.
Message Sender takes a relatively short time to stop when subscriber web service is not responding.
Known Issues
1 To avoid potential issues, QXO triggers for the sct_det and spt_det tables are not deployed for QAD EE.
2 In the Windows environment, the subscriber response page may not be displayed correctly if the subscriber is using HTTP version 1.1. The workaround is to change Subscriber HTTP from 1.1 to 1.0.