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.com



  •     QAD Glossary

  • QXtend Inbound with QAD Q/LinQ
    This section provides information on using Q/LinQ with QXtend Inbound (QXI).
    Overview
    Gives an overview of Q/LinQ and its uses in QXI.
    Install and Configure Q/LinQ
    Explains how to install and configure Q/LinQ.
    Define QXI URL
    Explains how to use Q/LinQ Control.
    Define External Application Defaults
    Explains how to use Register External Application.
    Set Up Import Specifications for QDocs
    Explains how to use Import Specification Maintenance.
    Set Up for Acknowledgements
    Explains how to set up for acknowledgements.
    Overview
    Q/LinQ is a tool set for building integrations with third-party or in-house applications for complex data exchange. It also provides infrastructure for administering and managing the data exchange between QAD Enterprise Applications and these external applications. See External Interface Guide: QAD Q/LinQ for details about installing and using Q/LinQ.
    Q/LinQ and QXI provide overlapping features in terms of queuing messages to be processed as QAD Enterprise Applications transactions. However, the processing of data into QAD Enterprise Applications through QDocs is a more robust method than the more CIM-like user-interface-emulation approach generally used by earlier releases of Q/LinQ. If you have installed and configured Q/LinQ and now install QXI, you can use the services of QXtend to process messages received and managed by Q/LinQ through its processing API.
    There are a number of reasons why you might want to use Q/LinQ and QXI together:
    1
    Q/LinQ does outbound processing, while QXtend is currently only available for inbound documents.
    2
    Q/LinQ has APIs to perform data mapping.
    3
    Q/LinQ has middleware communications capability and the associated feature of generating and processing confirmations.
    4
    Q/LinQ stores in-process documents in a database rather than externally as files. This approach provides enhanced data security and scalability and reduces the overall number of pieces that must be managed in the integration.
    In addition, you can continue to process some Q/LinQ import documents using UI emulation, while redirecting processing responsibility to QXtend for others.
    To process QDocs, you need to follow some special steps when you set up and configure Q/LinQ:
    1
    Install Q/LinQ based on standard installation instructions, giving special consideration to the setting in the QqMomAdapter.ini file that affects processing of QDocs.
    2
    Specify the location of the QXI server in Q/LinQ Control (36.8.24).
    3
    Define appropriate defaults in Register External Application (36.8.1.1).
    4
    Define import specifications for QDocs using Import Specification Maintenance (36.8.1.3).
    5
    Define import and export specifications for the acknowledgement documents passed between QAD Enterprise Applications and QXI.