Web-services integration module
The Web-services integration module is used for interaction between the QORT server and external program applications. It allows adding, editing, deleting records in the QORT database, invoking procedures for upload of trading positions to the front-office system QUIK and PIT calculation, and integrating with the broker’s personal account.
Connection of External Applications
An external application sends requests to export/import information to the QORT server via the Internet or a local network by using web-services. The data are transmitted via the HTTPS protocol.
The list of applications allowed for connection is set in the backQORT terminal. The authentication is performed by login and password. Only one external application can simultaneously operate with the service. After the connection, a request ID (token) is assigned to the application which is further used to call web-service operations.
Features of Module Operation
Examples of Module Usage
Upload of trading positions to QUIK through a special call.
The broker can decide on when the client’s onboarding is finished and it is time to provide the client with trading access. At that point, a request is sent and backQORT uploads trading positions to QUIK enabling the client to perform trading operations.
Integration with the broker’s client personal account on the website without compromising the system security. In the personal account, the client can view and fill in personal details, request and view client reports, PIT calculation. Reports are generated and sent to clients by their request.
During the integration with the broker’s personal account or any other external application, both QORT and the external application must have access to the QORT database. And on the one hand, the database must be located outside of the broker’s internal infrastructure in order to meet the information security requirements. On the other hand, in terms of the network infrastructure, it is better if the database is located near the QUIK server. For this reason, if the IDB is used as an integration mechanism, there are additional difficulties related to the system security, whereas the Web-services integration module meets this challenge in full.
Transfer of a data packet in which the information was collected from different sources and places.
When the module is used, it is possible to receive various information in one data packet, for example, the information on a business partner collected from different tables. When the IDB is used, the user has to collect the information from different tables and then make a single the data packet.
Optionally use of the Data model extension module which allows adding new data in the system. In this case, the Web-services integration module will be able to use these data in requests to export/import the information.