Introduction

Data acquisition is available with plugin version 1.17.1 and later.

If the settings described below are absent, data on owners is taken from the PAYMENTSEXTRA table. If the setting is available and the data is loaded, it is taken from the aggregate via PDS/CRM — tables STAT_RK7_SHIFTS_PDSCARDS, STAT_RK7_SHIFTS_PDSFOLDERS. Moreover, if CRM DB communication is configured in the Extensions > Database reference, the report will attempt to connect directly to the CRM DB and retrieve owner names from there.

Getting Data from PDS Server

Data can be loaded either during the aggregates recalculation or during the recalculation of the corresponding cube — the payment cards cube. The validity of card data is verified in specified time intervals. Intervals are configured in IRReportsFSPrj.ini, section FS_AGREGATE, parameter Time_between_update_PDS. Time is specified in hours. If the data validity period has expired, and there are shifts, which have not been recalculated yet, FS attempts to connect to the PDS server and retrieve data.

For correct operation, the following is required:

  1. Ensure access to the PDS server
  2. In the r_keeper manager station, go to Service > Interfaces and configure the corresponding interface, if it has not been configured earlier.

Fig. 1. PDS interface configuration

  1. From FTP, copy the CscLink.dll, Rtcp.dll, RNETBIOS.dll, RNBOPEN.dll libraries into the FS folder (for IA reports) and into the folder containing the executable file of the directories server ftp://ftp.ucs.ru/r-keeper/versions/PERSCARD/CSCLINK/cscl127.7z
  2. For IA reports in IRReportsFSPrj.ini, section [FS_AGREGATE], set Time_between_update_PDS=1.
  3. Configure server connection in CscLink.ini.

CscLink.ini file template:

[Settings]

CSLinkDLL=RTcp

CSLinkGate=1


[Rtcp]

Client1=RK7CUBERTCP

Server1=127.0.0.1

Port1=3456


With

CSLinkDLL is the dll name used to connect to CardServ

CSLinkGate is the input number

Client1 is the client name

Server1 is the IP address of the PC with CardServ

Port1 is the CardServ port


Data acquisition from the CRM server

Data is loaded during the aggregates recalculation. The validity of card data is verified in specified time intervals. Intervals are configured in IRReportsFSPrj.ini, section FS_AGREGATE, parameter Time_between_update_PDS. Time is specified in hours. If the data validity period has expired, and there are shifts, which have not been recalculated yet, FS attempts to connect to the CRM server and retrieve data.

For correct operation, the following is required:

  1. Ensure access to the CRM server.
  2. In r-keeper, under Interfaces, configure the corresponding interface (if not configured earlier).

Fig. 1. CRM interface configuration

ini-file — the name of ini-file/library If you need to configure multiple CRM connections, name the files as follows: CscLink.dll, CscLink.ini, CscLink2.dll, CscLink2.ini, CscLink3.dll, CscLink3.ini, etc.
User — the user of the SQL server with CRM DB.
Password — the password of the SQL server with CRM DB.

Data is loaded via the aggregate service; as a consequence, the aggregate service should be enabled for this mechanism to function.

  1. Copy the CscLink.dll, CscLink.ini libraries from FTP to the FS folder. Dll is available at FTP: /installers/IR REPORTS VER/1_17/1_17_8/FS/CRMLink/.
    4. In CscLink.ini, specify the CRM DB connection string:

[CRM_CONNECTION]

CommandTimeOut=300

connection_string = Provider=SQLOLEDB.1;Persist Security Info=False;Initial Catalog=CRM_TEST;Data Source=127.0.0.1,1433


CommandTimeOut — the request execution timeout;

connection_string — CRM DB connection string.

PDS and CRM have different libraries; if you need to use both CRM and PDS, or multiple CRM instances at the same time, rename the libraries and ini-files into CscLink2.dll, CscLink2.ini, etc.

Note

The periodicity of new CRM/PDS data verification is specified in hours. If no setting is made, the default value is 3 hours. New data is verified, only if there are shifts, which have not been recalculated yet.

Data load features

1) Data is loaded from PDS only during the aggregates recalculation for a new shift, or during the recalculation of the corresponding cube (payment cards cube).

2) The load frequency is controlled by the Time_between_update_PDS parameter under [FS_AGREGATE], the value is specified in hours.

3) The load should result in filled tables STAT_RK7_SHIFTS_PDSCARDS and STAT_RK7_SHIFTS_PDSFOLDERS in the RK7 database.

It means that for a successful load from PDS, you should wait until the time interval, specified as Time_between_update_PDS, expires, close the shift, and wait at least for the time period specified in the Time_between_checking parameter (in minutes), until the feature server finds a new shift and recalculates the aggregates. A successful load is indicated by the log entries "[PDS] Load 999 cards", or something similar.