Release Notes for Version 1.1.0
QXI Server Version: 1.1
Date: February 1, 2004
MFG/PRO Compatibility: eB through eB2.1
QAD QXtend Documentation: Technical Reference: QXtend Inbound (78-0602B)
Enable Requestor Licensing and Validations
QAD QXtend now licenses requestor applications. This feature allows administrators to ensure incoming data is from a known and trusted source. At least one requestor license is required to run QAD QXtend; the implementation of the validation in the QDoc request SOAP envelope is optional.
In addition to the validation of the requestor type in the SOAP envelope, QAD QXtend also validates the requestor applications user ID and password. On receipt, if the ID and password are validated, the password is encrypted.
The connection pool manager now accepts an encrypted password, which is stored in the QAD QXtend startup scripts as a variable.
In addition, QAD QXtend now operates over Tomcat with Secure Socket Layer (SSL) on HTTPS.
Suspend/Resume of the QAD QXtend Environment
Administrators can now suspend QAD QXtend processing from within the application interface in order to make configuration changes. This prevents partial or corrupted QDoc cycles, and substantially reduces the time and communication required to make changes.
Improved QDoc Response Documents
Error states, data values, and unused schema components are all valuable information for assessing effectiveness and debugging problems in an interoperable environment. QAD QXtend 1.1 allows users to include all these types of information, some of it configurable based on need, in the QDoc response. Four specific enhancements provide this capability:
Return MFG/PRO Data
Returning MFG/PRO data in the response documents is configurable. The feature can be turned on and off with a simple modification of a configuration attribute. The administrator can also determine the exact field list for each MFG/PRO calling program by modifying the appropriate QDoc response schema. By default, the included fields are primary key values.
Warnings for Unused Fields and Iterations
The notification of unused fields and iterations is now always returned in the response document. This informs an administrator when primary key fields or data iterations have not been updated in MFG/PRO. Typically these are empty fields or iterations, and should be unused. That information may be used to improve performance of future schema builds. In other cases, this notification isolates important data problems that could be misdirecting a QDoc during processing.
Enable Java Trace
Java information is helpful in debugging connection and processing problems. You can now modify a configuration attribute to include the Java trace data for a QDoc cycle in the QDoc response document.
Return Data Length Errors
Another notification that is always included in QAD QXtend 1.1 response QDocs is over-length field values. This assists administrators in isolating and solving one of the most common data errors in an interoperable environment.
Multiple Events Files Per Run Program Supported
In order to support multiple processing paths and incremental performance improvements, QAD QXtend now allows users to maintain and run QDoc schemas with different events files for a given MFG/PRO calling program. Events files control the navigation of a QDoc through an MFG/PRO calling program. Maintaining multiple versions allows administrators to provide navigation paths for different data entry tasks within a single calling program, as for confirmed and unconfirmed sales orders, since in the latter, tax and other trailer frames may not appear.
Pre- and Postprocessing Enhancements
The QAD QXtend preprocessor can call custom programs to validate or, as of version 1.1, modify inbound QDocs prior to writing data to MFG/PRO. The preprocessor programs can eliminate MFG/PRO errors, filter required records, eliminate records based on unique sets of criteria, and add or remove data as required.
The new postprocessor capability is similar but is used to validate and modify the response document contents. One example is obtaining updated data from MFG/PRO, such as line item prices that changed after the initial data update from the QDoc request.
Schema Merges Completed in a Web Service
Request and response QDocs are made up of two schemas and an events file. To allow administrators to merge the two schemas for testing and review, a new Web service method has been added.
Installation of Standard APIs from QAD QXtend Web Site
All API installations from the Web in the past were seen as custom schemas in QAD QXtend. The standard APIs from the QAD Web site are now installed as standard schemas by default.
1 Patched myQdocWebService.wsdl file to remove undefined and recursive types generated by AXIS Java2WSDL utility.
2 Added ability to add custom schema without raising an error when a custom schema by the same name already exists.
3 Updated security to force log-in on all files accessed within QXI.
4 Added fix to format .xml files correctly when writing to disk.
5 Fixed a problem with Supplier Schedule event mapping that required a key to be sent to MFG/PRO in order to enter an iteration.
6 Replaced use of pxrun.i with gprunp.i for context fix code to support compatibility with MFG/PRO eB.
7 Corrected the Cancel function to function without raising an error.
8 Modified Yes/No values in events files to the translatable values of True/False.
9 Improved error reporting when server or MFG/PRO connections fail.
10 Fixed installation so Queue Request/Response/System Failures directories and log directory are created on installation of QAD QXtend.
11 Updated the delete event functionality to unload an events file that is currently in memory when it is being deleted. Updated the add event functionality to remove any currently loaded event file from memory.