Multi-App Query Tool (MQT) by Greenlight
Overview
Integration with PC 2.5
Control testing and monitoring based on queries
Control Testing and Monitoring Based on Queries
The query is used for control testing and monitoring. This is achieved by creating a script based on the query.
The query is developed and stored in the target application. Users can use a tool of their choice to build the query.
Once the query is developed and tested it needs to be registered in the MQT query tool. During the registrations all the metadata related to the query are captured such as, schema, table, column and other information necessary to execute the query in a secured way. All these steps happen outside of the PC 2.5 application.
Rule Script
The user creates a rule script based on a query defined in MQT. The rule script will be of type “Query”. The user can search for all the queries in the MQT by selecting the appropriate Connector. When a rule script is created, the entire “where” conditions that are part of the query are created as rule criteria automatically. If a rule script is already defined then the rule criteria need not be duplicated, but is automatically associated to the rule script. The rule criteria are displayed in the Rule Criteria tab.
Rule
Once a rule script is created the user creates a rule based on the rule script. The rule creation for the script based on MQT is identical to a rule created based on an SAP query. The user experience remains the same. The user can search on scripts based on MQT during the rule creation. User can also define a Connector.
Control Rule Assignment
The rule parameters will have the rule criteria values for the query execution. Once a rule is created the user can associate the rule to a control. The flow for testing and monitoring will be similar to that of any other automated control.
Scheduler
Once the rules are assigned to a control, the user can schedule the rule execution part of the scheduler. The scheduling for execution happens within PC 2.5. The scheduler will invoke a service in MQT. This is asynchronous and the results are returned to PC 2.5 in an XML format. The results are then stored in DMS.
