In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |

  •     QAD Glossary

  • Release Notes for Version 1.8
    QXI Server Version: 1.8
    Date: March 2012
    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, 10.2B
    QAD QXtend Documentation: User Guide: QAD QXtend (70-3190-1.8) and Installation Guide: QAD QXtend (78-0952-1.8)
    New and Changed Features
    QXI can now include multiple versions of the same API in one WSDL file, which was not supported in previous versions.
    During installation, QXtend installer now creates a version file version.adapter under the adapter directory showing the current QXtend version and the QAD Enterprise Applications version. Previously, there was no way to tell what adapters had been deployed.
    QXI now writes the following QDoc request/response information to a new log file qdocSummary.log:
    Request: Trx Id, Process ID, QDoc Type, Requesting System, Request Date, Request Time, QAD User ID, Trx Type
    Response: Trx Id, Process ID, QDoc Type, Requesting System, Request Date, Request Time, QAD User ID, Trx Type, Result, Error Message
    QXI now supports multiple e-mail recipients (delimitated by comma) for the “email” parameter in the QDoc session context.
    You can now configure the new SuppressResponseDetails envelope setting for a QDoc 1.1 queue in Queue Manager.
    System QDocs can now trigger e-mail alerts if the user chooses to receive e-mail alerts for all APIs.
    When Require Authentication is False for a receiver and username is blank in the request QDoc, QXI now uses the username/password from the connection pool for authentication rather than give an error as it did previously.
    QXtend is a key component required to implement the integration between QAD Business Process Management (BPM) and QAD Enterprise Applications. The following enhancements have been made to this release of QXtend to fully support the QAD BPM product.
    Processing of QDoc Requests without SOAP Headers
    Previous versions of QXI could only process QDoc requests from external applications with appropriate information contained in the SOAP header. However, since QAD BPM does not natively support web services that leverage SOAP headers, QXI has been modified to accept QDoc (1.1) requests without SOAP headers as well.
    You can now choose whether to include the SOAP header in QDoc requests from external applications to QXI. If you choose not to, you can move the values in the original SOAP header to the session context (dsSessionContext) part in the SOAP body.
    New WSDL Generation Options
    When generating WSDL files, you have two new options:
    Separate Schema File: lets you choose whether to embed selected schemas into WSDL files or create separate schema files
    Use SOAP Headers: lets you choose whether to include the SOAP header in the WSDL file
    In previous versions of QXI, WSDL files could only be opened or downloaded immediately after generation and saved to local.
    Now, for each supported API of a receiver, QXI provides a URL through which you can directly access its corresponding WSDL file on the fly, also with the option to include or exclude the SOAP header.
    The WSDL URL without SOAP header can be directly exposed to QAD BPM and other applications for integration purposes. It provides the most efficient way for QAD BPM to access and consume WSDL documents that define the services it will use as part of the business process being developed in its development environment.
    WSDL Access Screens
    QXI provides you with modules, receivers, and APIs screens that let you easily browse, locate, and access all available WSDL URLs. A bread crumb trail is displayed on each screen to tell you where you are in the hierarchy and let you navigate to a higher-level screen.
    Fix Description
    Internal ID
    Issue Affected Versions
    When you select a standard QDoc and a custom QDoc with identical name during WSDL generation, QXI now generates a WSDL file and a sample QDoc from the custom QDoc, and writes an error message in an exclusion file explaining the situation. Previously, QXI only created a sample QDoc from the standard QDoc in such situations and did not create any error message.
    When processing a QDoc, if ODBC security is activated for qaddb and the record being accessed is locked, QXI now correctly returns a message containing the user name of the user who is locking the record. Previously, the system sometimes provided a wrong user name in the message.
    Queue Manager has been modified to prevent queues from being removed when they are stopped during QDoc processing and meanwhile move unprocessed QDocs from req_wrk to .req. Previously, QDocs that were in the Processing (req_wrk) state were moved to the System Failure directory.
    QXtend can now be successfully installed to deep directories. Previously, the installer would report error “File input too long” when compiling the adapter and QXO server code if the installation path was too deep.
    Multi-threaded queues now wait for 0.1 second (previously 2 seconds) to check whether there is an idle SOAPCaller object to start another request. This improves QDoc processing performance of multi-threaded queues.
    When a receiver is set to require authentication, QXI now always retrieves the username and password from the request. Previously, if QDoc contained a wrong session ID and no username and password were supplied, QXI would incorrectly use the username and password defined in connection pool.
    QXI now returns primary fields in the response QDoc when suppressResponseDetail is false in the request QDoc and the first element in ttContext is version. Previously, no primary field was returned in this situation.
    Connection pool agents would no longer be stuck in the connection pool with a status of Force Disconnect. Previously, when QXI processed a QDoc that had a different user ID than the one defined in the connection pool, if the QDoc threw an internal exception, the agent would go to the Force Disconnect status and could only be manually removed from the connection pool. This could jam up the connection pool and leave no idle sessions to process QDocs.
    QXI now returns all error and warning messages received during QDoc processing. Previously, when warning messages were returned for each line (iteration) from QAD Enterprise Applications, only the warning messages for the first line (iteration) were included in the response QDoc.
    When installing QAD Alerts, the system now returns correct error messages if the default configuration fails. Previously, the configuration service might return an error “invalid subscriber profile” when the real issue could be authentication failure, no active maintenance license, or invalid QXI receiver.
    Previously, QXI could not process more than eight elements in a row. Now this issue has been fixed.
    Previously, QDocs could not be properly created for Quality Order Maintenance (19.7) and Quality Order Results Entry (19.11). Now, this issue has been fixed.
    Native API processing performance against QAD 2011 EE has been improved through the correct use of authorization cache. Previously, there was a logical error in the code that prevented using the authorization cache correctly.
    QDoc maintainBank for QAD SE has been remapped to allow deletion.
    Known Issues
    In some situations, generating UIAPI QDocs in QGen gets the following error:
    Title message is too long for the window (character(s) lost). (4149).
    The workaround is to output the QDocs to files and manually load them to QXI.
    If QXtend is installed on Windows, query for large amount of data—for example, response XML > 10M—may cause Tomcat to run out of memory.