Q2 Architecture

In the above figure, the Application layer is typically referred to as HQ. This layer contains all of the business logic of the application. HQ also works as the gateway to other pieces of the product. In order to get data from the DB, an ExecuteStoredProc call from the HQ API is used.

The SDK fits into the architecture the same way as the Wedge does. Routes to the SDK extensions are set up in the DB, and read in by HQ. In a typical extension, a form for example, HQ will start the workflow of a extension by sending a request to the SDK. This request will include some online session information (login name, ssn, etc.), and the SDK can use available HQ methods to gather additional information. Once the workflow has finished, a return message is sent to HQ. In the example of a form workflow, HQ would then send the information returned from the SDK, to the end user via Online.