Release Notes for Version 1.5
QXI Server Version: 1.5
Date: May 2008
QAD Enterprise Applications Compatibility: eB SP4 through current release
QAD QXtend Documentation: Technical Reference: QAD QXtend (78-0691B) and Installation Guide: QAD QXtend (78-0692B)
1 Version 1.5 of QXtend includes a Query Service, which provides a data interface between QAD products, and between QAD products and external systems, without the need to connect to an application database.
The Query Service is a Service Interface API, and can be called using a native Progress call, a Progress appserver call, or using an XML Web service (QXtend Inbound) call. When called, the Query Service connects to the source application database, extracts the required data, packages the data, and returns it to the calling application. The data can be returned as either XML or as a ProDataSet.
You can use the Query Service to:
• Access data in other QAD applications for lookups and validation.
This facility removes the need to replicate data into the product module.
• Allow an external application to access data stored in a QAD application.
This facility could be used to validate data from an external application before it is sent to the QAD application, reducing potential errors when interfacing between products.
2 QXtend can now accept and publish raw business object event data from the QAD 2008 Enterprise Edition Financials module, eliminating the need to extract data from the Financials database. Financials can use QXtend to:
• Replicate financial data, including configuration and transactional data, between separate instances of Financials.
• Replicate financial data between Financials and a third-party financial application.
Financials business objects employ direct data publishing and are passed directly from the source to the QXODB database in QXO. From the QXODB database, they are processed by the message publisher.
The Financials raw business object event data is saved in an XML file and passed directly to QXO using an event message API; the resulting QDoc is published without the need for any further processing.
3 Subscriber configuration in QXO contains a number of new fields that facilitate QXtend’s interaction with Financials. These fields are:
• Source Entity
• A new communication method: QXtend Web Service. In this method, users can connect to QXtend without needing to know the full URL of the Web service. The QXtend Web Service method also denotes communication that is carried free of charge. Any message sent using the File Directory or Web Service communication methods requires a license. If you select the QXtend Web Service, there are a number of new fields for the Tomcat hostname and port, Web service, and for SSL.
4 The QXO Profiles tab includes a new button for generating WSDL files.
5 The Profiles screen includes new fields for specifying the entity you want to create a QDoc for. If you leave the field blank, the profile will create the QDoc for all entities. There is also a field for Default Operations, where you can indicate whether you want to include an Operation node in the QDoc.
6 In the QXtend Message Monitor, data can now be filtered by target domain and subscriber.