QAD QXtend Release Notes > Release Notes for QXI > Release Notes for Version
Release Notes for Version
QXI Server Version:
Date: May 12, 2006
MFG/PRO Compatibility: eB through eB2.1
QAD QXtend Documentation: Technical Reference: QAD QXtend Inbound (78-0602F)
New Features
1 You can now specify for each QXI queue whether it should operate in single or multi-threaded mode. Using a combination of single and multi-threaded queues lets you maximize throughput while guaranteeing that a QDoc that depends on a previous QDoc is not processed before the previous QDoc completes.
To support this feature, you can now specify Thread Settings when you set up a queue in the Queue Manager, including the initial size, maximum size, Web service time-out, and retry time.
2 QXI now provides a view that system administrators can use to investigate QDocs that have not returned a response, but remain in a processing state.
If an issue such as a record lock or other error is preventing a QDoc from completing an update, the QDoc waits in the processing state until it times out. It then returns a response with details about the failure. In some critical situations, users need to know immediately that a problem exists, without waiting for the time-out.
An administrator can now use the Connection Manager to view the telnet screen of a session in the processing state to determine the source of the issue. This is done by clicking the View link that displays in the Connection Manager screen under the Close column.
Note: The View link displays only for a QDoc in the processing state.
3 You can now set up receivers and schemas explicitly for MFG/PRO eB2.1. Previously, users with eB2.1 environments used the eB2 schemas and receivers, which could cause confusion.
4 This release of QXI provides support for users who have installed Advanced Inventory Management (AIM) 2.3c. To enable this support, install a patch required by the AIM installation. Copy the include file in the following directory on the CD to your AIM installation directory and compile the code using the AIM compile tools.
Note: This patch will be included in the AIM 3.0 release.