Integrator

1. On senior X Platform, go to Access Control and Security Management > Downloads;
2. click inTo go down the Ronda senior X Integrator and extract the folder on the desired server;
3. Run the create-service.bat file. With this, the SAM-Integrator service is created.

Note

If the client's Rabbit is shared, that is, if it uses VIRTUAL_HOST, it is necessary to configure its create-service.bat file, changing the VIRTUAL_HOST property, as in the following example:

set VIRTUAL_HOST=senior

When the Rabbitno uses VIRTUAL_HOST, it should look like this: set VIRTUAL_HOST=/

4. In Windows Services, start the SAM-Integrador service.

After installing the Integrator:

1. In Senior Round, go to Miscellaneous > Assignments > Miscellaneous (FR000ASS) > Senior Round X tab and:
   1. Set the optionIntegrates with Ronda senior X asYes;
   2. Mark all the information you want to integrate as Yes.

Note

If you have People Management | HCM, go to Miscellaneous > Assignments (FR000ASS) > Senior Round X tab and set the optionIntegrates with Ronda senior X asYes. Additionally, in the Integration panel, setYes for each type of Record you wish to integrate via Pending;

1. In the directory where the Integrator was installed, open the fileconfig.prop
   erties
   1. in edit mode sync.company.idfilterand:If you want to define specific companies to be included in the initial load of Employees, Employee Credentials/Badges, Senior Round X Users and Role Suspensions/Leave Leaves, define their codes in the parameter, separating each company with a comma. Example:sync.company.idfilter=1,2,5
   2. card.company.branch.filterIf you want to define specific filters to be integrated in the initial load and in the handling of pending companies and branches for Senior Ronda Employee Credentials/Badges, you can use the parameter, leaving the company codes separated by semicolons and the branch codes within the brackets, separated by a comma. Example:card.company.branch.filter=1[1,2,3,6];2[];3[2];4
   3. • server.portIf necessary, change the values of the following parameters (they already come with suggested
      • sync.accessevents.batchsize values): - identifies the server port; - defines the number of access and point markings processed at a time, from Ronda senior X (Senior cloud) to Ronda Senior (on-premise database). The highest possible value is 50, as this is the maximum number of events to be collected per batch;
      • sync.pendencies.batchsize - defines the number of pending issues handled at a time;
      • sync.accessevents.frequency - defines the search frequency for appointments from Ronda senior X (Senior cloud) to Ronda Senior (on-premise database);
      • card.technology – defines the default credential technology to be associated with the badges assigned in the Senior Ronda, for those who do not have technology assigned on the badge screenBadge Pre-Registration. Possible values are: 1 – bars; 2 – proximity; 3 – Smart Card;
      • devices.status.sync.timeout - defines the time to process pending device statuses. The minimum value is 30 and the defa
      • devices.status.sync.pendencies.batchsizeult is 60; - defines the device status backlog batch size.
   ImportantThe other parameters must not be changed in the config.properties file; they must be configured in the Integrator Settings tab, as described in step 5.

• By means ofUser It isPassword for connection to the system. In this case, the user must be an Administrator on Ronda senior X and have permissions on all senior X Platform resources. It is recommended that the user is specific to the use of the Integrator;
• By means ofAccess key and theAccess Secret, if you use ADFS login. In this case, you can configure the Ronda senior X integrator so that it does not use a senior X Platform Administrator role:
  1. Create a new senior X Platform role in the Technology > Administration > Authorization > Role Management menu, with permission on all resourceslobby, application and third. This role will be used by the authentication key;
  2. Create a new senior X Platform user, in the Technology > Administration > User Management menu, and associate it with the role created in the previous step. This user will be used in the Ronda senior X integrator;
  3. Create a person in Ronda senior X in the Access and Security Management > General Records > People menu, and associate it with the login generated in the previous step. It is important that this user in Ronda senior X is placed as Administrator, as shown in the following image:

  

  5. 

  Create a new authentication key on the senior X Platform in the Technology > Administration > Application management menu, associating the role created in st
  ep a;Access the Ronda senior X integrator settings and fill in as shown in the following image (items in red need to be filled in):

Access the documentationVirtual concierge for all information.

When records of contracts and third-party companies are integrated with Ronda Senior, only information that belongs only to Third-Party Management (that is, that does not exist in the Ronda Senior system) can be changed.

Furthermore, in the third-party company, it is only allowed to change the approval flow process, register and attach documents.

Companies without identification documents will not be integrated into Third Party Management. The CNPJ, CEI or CPF must be included in the third-party company's registration for it to be integrated. This is done in the Ronda Senior system, in the Other Companies register, by filling in the fieldsRegistration Type It isRegistration Number.

Finger Print biometrics will be integrated. For more information, see the documentation forOrdinance Management Integrator.

Integrate all items from Ronda Senior Ordinance Control to Ronda senior X Ordinance Management. For more information, see the documentation forOrdinance Management Integrator.

Integrate information from Ronda Senior Third Party Control into Ronda senior X Third Party Management. Find out more in the documentationThird Party Management Integrator.

1. In the Integrator, click on the Pendencies tab;
2. In the Consultation panel, use the date filters and define the Routine you want to verify, then click on Apply filter;
3. The Pendency errors list panel might show that no pendency with errors was found, or otherwise display the ones that have errors. In that case:
   1. Click on the pending issue listed and see the error description;
   2. Treat the problem highlighted in the Senior Round;
   3. Select the column check boxResend in the pending issue(s) addressed;
   4. click in Resend and wait for the successful resend notice.