Integrator - HCM

The HCM Integrator can be used on exclusive or shared servers (which have other systems).

The minimum infrastructure necessary is:

• 1 virtual machine with 2 2.4 GHz processor cores;
• 4 GB of RAM 1600 MHz (if shared, it is necessary to have at least 4 GB free);
• 1 Gbps network;
• 500 GB HD 7000 RPM;
• Java 11 — OpenJDK 11 installation or upgrade;
• In system variables, it is mandatory to create the variableJAVA_HOME_HCM;
• By default, the environment variableJAVA_HOME_HCM must point to the Java 11 JDK.

• Have access to HTTPS calls (port 443) at the address below:
  

  
  

  hcm-api.senior.com.br
• Confirm that the certificate is valid (this can be indicated by the presence of the green padlock next to the address):
  
  
• Have equal access to a People Management station | HCM, including:
  • free acce
  • ss to Senior's installation directories;
  access granted for database server access.

Windows versions compatible with Integrator - HCM

Integrator - HCM can be installed on the following Windows platforms compatible with the application:

Platform	CPU architecture
Windows Server 2019	x64 (64-bit)
Windows Server 2016	x64 (64-bit)
Windows Server 2012 R2	x64 (64-bit)
Windows Server 2012	x64 (64-bit)
Windows 10	x64 (64-bit)
Windows 8.x	x64 (64-bit)
Windows 7	x64 (64-bit)

Windows versions compatible with Integrator - HCM

The browser homologated for the Integrator - HCM hcm-monitor operation is Google Chrome (version 70.0.3538 or higher).

People Management System Database | HCM (version 6 - on-premise)

The People Management database server | HCM needs to be one of theSenior approved versions.

Execution in versions other than those approved may cause instabilities or performance problems in the Integrator - HCM.

It is necessary to ensure that thesenior X platform is deployed and configured. If not, it is necessary to at least meet the same platform infrastructure requirements (the requirements are detailed in the documentation of theinstallation procedures).

If there is integration between G5/G6 systems (on-premise) and senior X Platform (cloud), it is also necessary to ensure theinstallation in hybrid environment.

URLs that need to be released to all users and on the Integrator server - HCM

• Integrator Server
  :
  • platform.senior.com.br (default port https44
  3
  • and https9433,8243
  • , 9991
  )
  • hcm-api.s
  enior.com.br
  • (default port htt
  ps
  443; typeCNAME: point tohcm-services-elb-613274854.sa-east-1.elb.amazonaws.com)https://hcm-api.senior.com.br/hcm-api/version (address used to test user access at: hcm-api.senior.com.br)awsstatic.com (domain)mail.senior.com.br:587 (Senior's email server; used by the HCM Integrator to send telemetry notifications to Senior about critical situations related to the Integrator's operation in the customers' environment)
• all users
  :
  • log
  • in.senior.com.br (default port https443)hcm.senior.com.br (default port https 443
  ; type
  • CNAME: point tod36y17dmgpn6g.cloudfront.net)
  • senior-hcm-storage.s3.amazonaws.com (default port https 443 )
  • br-com-senior-blob-service-shared-area.s3-sa-east-1.amazonaws.com
  (default port https
  • 443
  )
  https://hcm-api.senior.com.br/
  https://code.ionicframework.com
  https://maxcdn.bootstrapcdn.com
  https://cdn.senior.com.br
  https://oss.maxcdn.com
  https://npmjs.org
  https://fonts.googleapis.com
  https://cdnjs.com/ https://api.postmon.com.br/

Security

Communication is done only byTLS 1.2.

URL for automatic update

The URL below needs to be released for the automatic update of the Integrator - HCM to work correctly.

The installation of the Integrator - HCM requires the customer to have:

• a senior X platform access tenant
• the file (extension.pem), which contains the certificate keys to run the application

The following procedure explains how to obtain this information. This needs to be done by the system administrator at the client and must be completed before starting the Integrator - HCM installation.

Create onetenant access to senior platform X and get the file.pem

1. Access the Support SARA, which is the environment where the tenant creation request will be made (click here to access).
2. select the optionTENANTS and follow the instructions presented by SARA. If you want to know more about this step, seetenant creation documentation in the platform manual.
3. When the tenant request is complete, theadministrator you will receive an email with a unique identifier, calledtenant id. You will also receive an email with an attached file (extension.pem).
   
   Check this e-mail and save the information and the file, which will be used in the installation of the Integrator - HCM.

The web service of each acquired module must be installed to make the synchronization of information between senior X Platform and the contracted modules, and vice versa, happen.

Este é um requisito obrigatório para o funcionamento dos processos de atualização cadastral e de gestão de férias.

Além disso, também é necessário garantir que o servidor onde o Integrador está instalado tenha acesso as URLs dos web services instalados.

2. Install Integrator - HCM

The installer can be obtained in a .ZIP file, which is available at the following address:

The hcm-integration.zip file must be extracted in a server with access to the Human Capital Management | HCM database.

Installing Integrator - HCM as a Windows service

To install Integrator - HCM as a Windows service, you must run the installation using the file below, available in the root directory of the application:

• InstallService64.bat (install the service for servers with 64-bit Java installed).

Once the service is installed, it can be started either from the Windows service panel itself or from the fileSTART.BATTER.

When running the fileSTART.BATTER without parameters, it will try to execute the service and, if it does not exist, a message is issued indicating its absence. Even so, it is still possible to run the HCM Integrator in the form of an application, executing the fileSTART.BATTER with the parameter-nosvc.

Example of the warning message when the HCM Integrator service is not installed on the machine and an attempt is made to run the application using the fileSTART.BATTER:

Deleting the Windows service

To delete the Windows service it is necessary to run the fileRemoveService.bat, available in the root directory of the integrator.

Possible Java VM crash during HCM Integrator installation

If you notice that a Java VM crash occurred during the installation of the HCM Integrator, do the following:OpenJDK package download which is used by the application. Install the OpenJDK package and repeat the HCM Integrator installation.

The reason for the error can be seen when checking the log files named "global", located in the logs folder where the application was installed (example: C:\HCM-Integrador\log)

To access the Senior Settings Center, run the appSeniorConfigCenter.exe, located in the same directory where People Management | HCM (on-premise) was installed (example: c:\Senior\SeniorConfigCenter.exe).

In this app, make the following settings:

Contract data

In the Senior Settings Center, navigate to the HCM settings screen — located under Systems > People Management >HCM — and fill in the fields on the screen.

This information is only valid when:

• Do theconnection between the on-premise system environment and the senior X platform
• Use SAML authentication

You can obtain additional details on how to complete the fields on this screen atTechnology Manual.

Key

In the Senior Settings Center, navigate to the switch settings screen and add (or configure) the following record:

• Keycom.senior.vetorh.hcm.g7.auth:
• Valuetrue

Check if the key below was included — this inclusion should have occurred automatically when the connection data was configured in the previous step:

• Keycom.senior.vetoh.hcm.g7.location:
• Valuehttps://platform.senior.com.br/t/senior.com.br/bridge/1.0/rest
  

You can obtain additional details on how to complete the fields on this screen atTechnology Manual.

Proxy

If the company uses proxy:

Configure the proxy on Senior Config Center, at Network connections > Internet access.

To check whether the company uses proxy, you can consult the browser settings (example on Internet Explorer Internet: Internet Options > Connections tab > LAN Settings button > Proxy server).

If the company does not use proxy:

Caso não utilize proxy, a propriedade config.ignore.proxy deve estar configurada como true no arquivo integration.properties do Integrador - HCM (config.ignore.proxy=true).

The root folder where the HCM Integrator was installed will contain the fileintegration.properties (example: C:\HCM-Integrador\integration.properties).

Using Notepad or a similar text editor, open this file and edit the following properties as needed:

property name	Property Description	property completion
hcm.location	Address of the HCM services.	Required
integration.fromFile.dir	Directory which stores the files with report-generated data. This key needs to point to the folder where the files are saved.hcm-employee-salary-premiums.txt It is hcm-employee-vacation-schedule.txt (refer toManagement Panel prerequisite documentation), in addition to other files that are cited later on this page. Example: integration.fromFile.dir=C:\\temp\\data_files	Required
rh.company.id	Companies to be considered in the integration.	Required
config.rootdir	Installation folder of the Senior - Human Capital Management - HCM system.	Required
config.environment	Name of the ".CFG" file without the extension. For example, if the file is named "senior.cfg", simply u "senior".	Required
config.ignore.proxy	If true, the proxy defined in SeniorConfigCenter is ignored.	Required
hcm.tenant.id	It must be filled withTenant ID (tenant) that appears in the HCM database. This information can be obtained from the email that is received by the tenant administrator, in which the key file is sent.pem. In the e-mail, the information will be described inTenant ID, for example: Tenant name Tenant ID:xxx_ltda	Required
sync.interval	Synchrony verification time. If not defined, the default value is 30 seconds.	Optional
integration.administrator	Identification of the user who will be established as the first admin user of the Management Panel. It must be completed in the formatNumEmp/TipCol/NumCad, where: numemp = company code TipCol = employee type code NumCad = employee registration code Example: integration.administrator=1/1/19028	Optional
hcm.admin.email	email address ofadministrator of the Integrator - HCM. When it is informed, the administrator will receive a daily e-mail with a summary of occurrences of errors and failures of the Integrator - HCM. If the Integrator does not present errors, the e-mail will not be sent.	Optional
integration.log.level	Log level. Possible values: ALL: Complete logs, considers all variations of application logs. It is the recommended option as it facilitates maintenance. FIN E: Log that considers error situations, important warnings, informative warnings and tracking warnings (records traversed in a flow, details of an entity, etc.). Example: Searching parent item with position: %s; INF O: Log that considers error situations, important and informative warnings (notice of start and end of process execution, request parameters, etc.). Example: Rerunning integration network errors...; WARNIN G: Log that considers error situations and important warnings (ignored record, momentary unavailability, circumventable error, etc.). Example: Timeout occurred while trying to download remote version file with timeout, we will try again soon.; SEVER E: Log that only considers error situations. Example: Failed to create the meta migration cache table.; OFF: Logs disabled. This option is not recommended as it can be difficult to maintain. If not defined, the default value is WARNING. Se nada for definido, o valor padrão será WARNING.	Optional
integration.hierarchy.interval​	Hierarchy integration interval in minutes This property sets how often the hierarchy will be resubmitted to HCM. Standard value:180 minutes​ Note Values less than or equal to 60 minutes will be disregarded.	Optional
sync.enabledOnStart	Enables/disables the automatic start of synchronization when starting the HCM Integrator. Standard value:false Observation The default value of the propertysync.enabledOnStart It is false, however, this value can be changed totrue. When the value is likefalse, in turn, the system checks whether loads of at least 80% of the flows have already been executed. If you have already executed at least this percentage, the value automatically changes totrue.	Optional
movimentation.task.enabled	Indicates whether the sequences related to workers' movements and job positions will be executed daily to adjust the database and prevent divergences. Default value: true.	Optional
updater.disable	Indicates whether the automatic update is disabled. The default value is false.	Optional
sync.request.maxRows	Maximum number of pending issues to be handled in each synchronization run. Standard value:300 pendencies Maximum value:500 pendencies	Optional
sync.request.batch.size	Size of the sending batch. Default value: Maximum goal value	Optional
sync.request.batch.timeout	Batch synchrony timeout (in minutes). Default value:	Optional
updater.openjdk11.download.path	Indicates the location (folder) in which the OpenJDK11 download will be done.	Optional
updater.openjdk11.zip	Define which Java 11 version will be downloaded by Integrator - HCM.	Optional
updater.integration.healthcheck.port	Port to verify whether the Integrator - HCM service on Windows is being executed properly. By default, port is used.9082. Port 9082 is used by default, if it is already being used by another Windows process, another port must be used in this property.	Optional
integration.inbound.port	HCM Integrator Port. The port value must have exactly 4 (four) digits. If not defined, the default value is 8082.	Required
integration.inbound.host	HCM Integrator computer name. If not defined, the default value is localhost.	Optional
integration.batch.size	Size of the sending batch. The default and maximum value is 150.	Optional
old_files_cleaner.deadline_days	Number of days that old files (logs, for example) are available before they are eliminated. Standard value:45 (days) Minimum value:7 (days) Maximum goal value	Optional
use.index.rtcpendencies.enabled	By default, the G5 database does not use the RTC_PENDENCIESINDICE_1 index in the query, which returns the number of synchronization pendencies per table. If the query presents performance problems in the SQLServer database, it is recommended to enable its use by informingtrue on this property.	Optional
useraccount.module.control.disabled	When configured astrue, the Integrator will start to replicate the information of users who are linked to collaborators and who have no indication of modules in People Management | HCM (G6/on-premise). This parameter is typically used in deployments where the customer has other Senior products in addition to HCM. The default value is false. How the HCM Integrator verifies the indication of modules Validation varies according to the modules indicated in the client's tenant, being possible to consult them in the graphic interface of the HCM Integrator, in the active modules section. I.e: If theManagement Panel is included in the tenant, the routine will consider the indication of the module Management Panelin G6 (codmod = 17). If theeSocial Cloud is included in the tenant, the routine will consider the indication of the moduleSST integratoron G6 (codmod = 18). If thePayroll is included in the tenant, the routine will consider: the module indicationPersonnel Administrationin G6 (codmod = 9); It is Otype of collaborator configured in the propertygdp.tipcol.filter. If there is more than one indication — a tenant with three active modules, for example — these validations are done with the "OR" logical operator. Therefore, any of the employee's indications in G6 works so that the HCM Integrator knows that the information in this record needs to be uploaded to the senior version X. To avoid problems, it is recommended that the control in G6 be done through the "Management Panel" module (codmod=17).	Optional
useraccount.syntax.error	When configured astrue, disables the generation of errors caused by problems in the syntax of usernames, considering that the authentication service of the senior X platform does not accept usernames with certain types of special characters. When enabling this parameter, users who present a syntax error in the name will still not be integrated into the HCM, but instead of acknowledging the error, the situation will only be displayed in the Integrator's log. The default value is false.	Optional
integration.jvm.params	Parameter for property initializationXmxsize (Maximum Heap Size) of the Java Virtual Machine (JVM). Defines the maximum amount of memory that the HCM Integrator can allocate while processing pending issues. Standard value:-Xmx4096m Recommended minimum value:-Xmx2048m	Optional
integration.g5.service.module	Indicates through which G5 module the integrations with the senior X Platform will be carried out. Possible values:ruby, round orcs Standard value:ruby	Optional
platform.roles.replication.enabled	Enables integration of SGU user groups (on-premise version/Version 6 of People Management | HCM for senior X Platform) Possible values:true	Optional
hcm.email.notification.enabled	Initialize option settingsReceive email notification Possible values:true,false	Optional
platform.multidomain.enabled	Enables support for the use ofalternate domains (multidomain). When this parameter is set totrue, indicates that the tenant has more than one domain. Possible values:true,false Note In addition to enabling the propertyplatform.multidomain.enabled in the HCM Integrator, you need to do some additional configuration. refer toHCM alternate domains documentation to know all the necessary settings.	Optional

The deployment ofHCM integratoris enough to synchronize thegeneral HCM data in hybrid environments.

In some scenarios it is common to use theETL integratorto integrateuser groups It isusers (SGU), but there are situations where this is not recommended.

The following documentation demonstrates the possible scenarios and how they occur.

HCM+ETL asERP:

When theETLand the ERP from Senior are in use, it is recommendeddon't use ETL to sync user pools It isusers, as there is a risk of duplicating users and groups in the base.

Therefore, in this scenario, you need to make the settings below todisable user group sync it's fromusers:

1. Disable replication tables:
   1. Access the senior X platform with a usertenant admin.
   2. Access the menu: Technology > Administration > Integration > Replication.
   3. disable
      • the following ETL user replication tables:
      • R900CPL
      • R9
      • 00GRP
      R900PDT R999USU
2. Configure Unified Logon:
   • Go to the Senior Settings Central app (SeniorConfigCenter) and configure Unified Database Logon. For details on how to do this procedure, seecomplete documentation in the Technology Manual.

Through the HCM Integrator, it is possible to load the users' data to use the Timekeeping 2.0 | HCM - therefore, there is no need to enable the Management Panel module. See the instructions below:

1. Access Sara from Support, through the addresshttps://suporte.sara.senior.com.br/;
2. Click on the optionTenant and then inI would like to Request the Creation of a Tenant;
3. Enter your username and password;

Attention

To request the creation of a Tenant, your user must have permission to do so.

4. On Sara's screen, request the Tenant from the APP - Marking Time 2.0. To do so, simply check the optionAPP - Point Marking 2.0, present in the itemNumber of employees per module;
5. click inRequest creation;
6. Once answered, this request will go up to the HCM Integrator.

In the HCM Integrator, theAPP - Point Marking 2.0 will be displayed in:

• on the tabdashborad, will display theAPP - Point Marking 2.0 on the card ofactive modules;
• on the tabIntegration, will display theAPP - Point Marking 2.0 on the card ofFlow , containing three streams. Being them:
  HCM users;
  Use
  r groups;Group users.

After carrying out this process, the user data will be loaded, and employees will now be able to use the Ponto de Ponto 2.0 | HCM.

It's possiblecustomize flows by modifying the SQL commands. Flowcharts may be customized by modifying SQL commands, executed on the database of the on-premises Human Capital Management | HCM system, changing the data that will be integrated.

How to customize

1. Access the folderQueries, which is located in the same directory as the Integrator - HCM installation.
2. Inside the folderQueries, make a copy of the query file (.sql) that you want to customize andadd the extension
   
   .usu at the end. Example:
   • original file: g5-accounting-query.sql

   file copied

   : g5-accounting-query.sql.usuImportantOencoding of the file.usu needs to beUTF-8 (No BOM) so that Integrator - HCM can interpret it. Workers of the Partner type are not supported.

3. Make sure the worker had his or her admission closed.
   
   Example:
   

The existence of the file.usu during integration and synchronization it indicates to the Integrator - HCM that it should consider this query, instead of using the original file (.sql).

If you directly modify the original query file (.sql), it will be overwritten during the Integrator - HCM update and your changes will be reverted.

It is not necessary to restart the Integrator - HCM for the customized query to be used, as the update takes place in real time.

How to check HCM Integrator version

On the home screen of the HCM Integrator dashboard, in the fieldintegrator version, the current running version is displayed.

How to Tell if HCM Integrator Is Updating Automatically

Since the propertyupdater.disable ofintegration.properties file be likefalse, when there is a new version, the integrator will be updated automatically when its respective service is restarted.

While running, the HCM Integrator also has a scheduled task that every eight hours checks for a newer version available for download. If a new version is found, an automatic restart process is triggered for the update to take place.

How HCM Integrator checks if there is a new version to update

A new version is found when the version recorded in the fileversion.properties have a date lower than the version available for download.

How to monitor the HCM Integrator update process and check if any errors occur in this process

The progress of the update can be followed by the fileupdater.log, present in the log folder of the HCM Integrator. This file records the entire update process and possible failures, such as failure to access the server where the new version is hosted.

The integration dashboard allows you to view information through the cards and perform actions related to the HCM Integrator.

The dashboard (hcm-monitor) is located inside the application installation ( hcm-integration.zip).

View camera images

No cardactive modules it is possible to view the contracted modules, with their respective activation status.

The newly contracted modules can be activated by the card itself, an action that causes the HCM Integrator to restart and record the flows and synchronies necessary for the module to work. All monitoring triggers are also recreated in the Personnel Management | HCM on-premises, leaving the flows available for carrying out the initial load.

That is, the flows, synchronies and triggers of newly hired modules do not start working until the module is activated. The process of activating a business module can take a few minutes, and whenever it occurs, their respective flows will be marked as pending loading, since certain flows need a new execution to load new specific fields of the newly activated module.

Select and run flows for the initial load

Integration flows are grouped by module on the cardflows from the guideIntegration. In this way, when deploying a module, it is possible to select only the specific ones to execute the initial load, since all flows necessary for the operation are already included in it. Through this card it is also possible to identify which flows still need to be executed to finalize the module deployment.

When selecting a module, its initial load flows are displayed in execution order. The flows presented in colorgreen have already had their initial charge executed, and those presented in colorblack are still pending execution. It is possible to run only the flows whose execution is pending, or also to rerun those that have already had the initial load.

The buttonRun load from selected stream is only enabled when only one flow is selected, and performs the initial load starting with the selected flow and following the sequence. already the buttonRun full load can be used to perform the full initial load of all flows from theactive modules.

View flows already executed or pending initial load

It is possible to view the flows that have already had the initial load performed or those that are still pending through the cardsFlows with initial loads already performed It is Initial load pending flows.

Through these cards, it is possible to visualize which flows have already had their respective initial loads completely executed (regardless of the occurrence or not of errors) and which flows are still pending loading. through the buttonsTo add and/or Add All it is possible to include the pending load flows in the execution queue.

List of flows by module or routine

The table below shows the name of the initial load sequences and the .sql file which contains the query. The files can be consulted in the queries folder of the integrator.

What is a sync hang

The pending sync is a record in the People Management | HCM (version 6) that has a change and needs it to be replicated to the HCM senior X database.

All operations performed on one of the tables monitored by the HCM Integrator are considered to generate a pending item. The operations areINSERT:UPDATE (inclusion of a new record),DELETE (change of a record) and (deletion of a record).

How issues are generated

These pendencies are generated via existing triggers in each of the tables monitored by the HCM Integrator. The generation and maintenance of these triggers are carried out at the time of base consistency that the HCM Integrator performs when initializing.

Examples of naming the generated triggers:

• RTC_R034FUN_I
• RTC_R034FUN_U
• RTC_R034FUN_D

scheduled pendencies

AtSync tab ofdashboard, you can find the grouperG5 → Open HCM (Scheduled).

This grouper displays the number of open pending issues that are scheduled for thenight run.

The integration of the tables that are waiting for the nightly execution takes place daily, in the periodbetween 18:30 on one day and 08:00 on the following day.

The columnExecution Time indicates if the issues of the respective tables are already queued for processing or if the issues were scheduled for processing at night time.

Where sync pending issues are stored

The generated pendencies are stored in the tableRTC_PENDENCIES, from the People Management database | HCM (version 6).

How to identify if a sync pending has already been processed

The pendencies that have already been processed by the HCM Integrator continue with a record in the tableRTC_PENDENCIES, but receive a record in the tableHCM_PENDENCIES (also from the People Management | HCM database - version 6). Thus, the HCM Integrator considers that the pending issue has already been properly processed.

Therefore, one way to identify which pending issues were not processed is to run the following query on the People Management | HCM:

Execution of synchronization tasks

The time interval for executing synchronizations related to requests in the HCM > G5 context will be 1 (one) minute for customers who have the Payroll module enabled in the HCM Integrator; and 3 (three) minutes for customers who do not have the module enabled.

The HCM Integrator has a routine that allows the administrator to configure which synchronization issuesshould not be processed.

How the Ignore Issues routine works

This routine is based on the properties file configurationsync-ignorefields.properties (found in the root folder of the HCM Integrator installation).

If a table's sync pendency is likechanged fields, only those defined in the property (one or more) will have the pendency ignored, thus inserting a record in the tableHCM_PENDENCIES of the People Management base | HCM (version 6). This indicates to the HCM Integrator that the issue in question should be considered as "successfully processed".

How to configure the filesync-ignorefields.properties

In this file, it is necessary to put the name of the Personnel Management table as a key. HCM (version 6) and, as key value, the fields that should be ignored.

Thus, if the HCM Integrator receives a pending synchronization by changing just one of these fields, the pending will be ignored.

It is also possible to configure with the termALL, thenall the sync issues for that table will be ignored, regardless of which fields were changed.

File configuration example:

Batch synchronization allows routines to process their pending issues independently, grouping them by context and sending them to the application server.

Due to the synchrony routines that are executed in large numbers per day, the batch concept was adopted for the routines to process their pendencies independently, grouping them by context and sending them to the application server.

No additional configuration is required to use the batch sync routine. It is enabled by default for all clients.

Synchronies that handle your issues in batch

1. Employee vacation periods
2. Employee points
3. Payrolls
4. Payroll events
5. Users (SGU)

Batch sync customization

The HCM Integrator has three file propertiesintegration.properties that allow you to change some settings of the batch sync:

• sync.request.maxRows: maximum number of pendencies to be treated in each synchronization run.
• sync.request.batch.size: size of the sending batch.
• sync.request.batch.timeout: Batch sync timeout in minutes.

To know the default, minimum and maximum values accepted by these properties, see thefile configuration sectionintegration.properties.

Due to the Government decree that suspended daylight saving time indefinitely, it may be necessary to adjust the Integrator - HCM so that the application log times are correct.

Procedure to adapt the schedules of the Integrator - HCM:

1. The Integrator setup is available at https://s3-sa-east-1.amazonaws.com/senior-hcm-integration/.
2. Unzip the downloaded file and place the filetzdb.dat unzipped in the folder
   lib
   • of the following JDK:
   • Integrator JDK 11 - HCM (folder
   jdk-11.0
   .2
   in the

   Integrator directory)

   JDK 8 used for the installation of the Integrator - HCM (usually it can be found by the environment variable%JAVA_HOME_HCM%)ImportantIf the on-premise solution database isoracle, put the file tzdb.dat also in the folder lib of Java from Oracle. If this is not done, the Java used by Oracle will not have the same date and time settings, causing errors in queries involving fields of typegives you It is d

   ate
   time.
3. Restart the Integrator - HCM service for the change to take effect.

The HCM Integrator allows integrating SGU user groups (on-premise version/version 6 of People Management | HCM for the senior X Platform).

How to enable this feature

1. Access the root folder where the HCM Integrator was installed (example: C:\HCM-Integrador\integration.properties);
2. Access the fileintegration.properties;
3. inside the fileintegration.properties, enable (put astrue) the keyplatform.roles.replication.enabled;
4. Restart the HCM Integrator.

By restarting the HCM Integrator, the integration of user groups from the SGU to the senior X Platform will now be available.

After restarting the HCM Integrator, the flowsuser groups It isGroup Users will be marked asPending on the tabIntegration. Therefore, it becomes necessary to run both groups to initialize the routine. With that, we again stress the importance of checking/carrying out the items highlighted in the check box.Attention above.

How to use this feature

With the functionality enabled, it is enough to create, modify and/or delete a group (as well as the users of a group) in the SGU. When making any type of change in the SGU, the information will be synchronized with the senior X Platform.

The table below clarifies what is modified in the SGU and what/where is the impact on the senior X Platform:

in the SGU	On Senior X Platform
User group (fields:Name,Description It isgroup origin) On-premise/version 6 version table where data is saved: Users - People Data (R900PDT)	Paper (fields:paper name,Description It isType)
members On-premise/version 6 version table where data is saved: Users - Group Members (R900GRP)	Users

frequently asked questions

The system makes it possible to make the sending of notifications by e-mail to the company's users standard, this is done through the flowSettings (send email notifications). For this, you must follow the step by step below to enable this functionality.

1. On the Integration tab, browse and select the flowSettings (send email notifications) for individual execution.;
2. After selecting above, click onRun selected flow;

3. Access the root folder where the HCM Integrator was installed (example: C:\HCM-Integrador\integration.properties);
4. Access the fileintegration.properties;
5. inside the fileintegration.properties, enter the keyhcm.email.notification.enabled =true;
6. Restart the HCM Integrator so that this new key can be read;
7. run the flowSettings (send email notifications);