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  |   On Demand  |   Home  |   qad.com




Direct Data Publish
QAD EE uses the QAD Reference Architecture technology, which supports true business object functionality where the change in state of a business object can be detected—it is not necessary to poll the qxevents database for changes and extract the data. Instead the raw business object event data is saved in an XML file and passed directly to QXO via an event message API—the resulting QDoc is published without the need for further processing.
This ability is known as direct data publish (DDP), and enables data to be synchronized between one instance of the Financials module and another, or between the Financials module and an external application.
Since DDP source application types post event data directly to QXO, no event service is required. The QDoc is published using the standard message publisher functionality.
DDP employs a direct data publishing API to process event messages and schemas originating from a source application type that employs DDP. The direct data publishing API utilizes the service interface adapter API to input data into the target application.
Several configuration steps are required in order to implement DDP in QAD Enterprise Applications EE and QXtend. For details, see QXtend Interaction with Financials.
Note: DDP documents must be associated with a valid business event, otherwise the document will not be published. The business event is provided in the session context parameter. The system checks to verify that the business event is a valid event type for the source application. If the event is not valid, the system raises an exception. For details about session context parameters, see Parameter Data.