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

  • Introduction
    The Queue Manager is an optional interface that allows you to accept QDoc request documents from external applications into a directory structure, to modify and manage requests and queues if necessary, and to return QDoc response documents to the external applications. The QXtend Inbound (QXI) transformation engine is a container for custom style sheet conversions for non-QDoc XML messages.
    The Queue Manager is accessed through the QXtend Manager interface, but is not a required or default component of QXI. QXI accepts API requests directly as HTTP post requests in SOAP-compliant XML format, or can accept the documents from a queuing application such as IBM MQSeries, or from the QXtend Queue Manager. You can also use QAD Q/LinQ for a more robust queuing and administrative application.
    Queuing applications provide queues for incoming and outgoing documents or messages, ensuring delivery and synchronous responses.
    In the case of the Queue Manager, requests arrive from external systems to a specified directory. The requests must be in XML format and be named with a .req extension. (The Queue Manager can add a SOAP envelope if necessary.)
    Note: The Queue Manager supports both the QDoc 1.1 and 1.0 syntax specifications, and the SOAP 1.1 standard.
    Non-standard XML requests can also be received by queues set up to allow them. These are XML documents added to the queue that do not have a .req extension. In this case, the document is passed to the transformation engine. The engine applies a custom XSLT style sheet based on the extension of the file and creates a standard QDoc request. It places this request in a standard queue directory where it is processed normally. For details, see QXtend Inbound Queue Manager.
    The Queue Manager polls the request directory, picks up new requests, renames them with a .req_wrk extension, and sends them to QXI where they are sent to the defined receiver. A response document container is created at the same time; messages, requested fields, errors, and so on are written to the response during QDoc processing.
    Once processing is complete, responses are placed in a response queue for the external application. Responses use the following extensions:
    ok
    The QDoc processed correctly.
    .wrn
    The QDoc processed but encountered warnings.
    .err
    The QDoc request failed.
    Once a response document is created in the \response directory, the .req_wrk request is moved to the response directory and renamed with a .req extension again.
    If the Queue Manager does not receive a response for some reason, the .req_wrk request is moved to the external application systems_failure directory.