PeopleSoft HCM connector

Last modified 13 May 2021 09:13 +02:00

Identity connector for Oracle PeopleSoft Human Capital Management (HCM).

Development statusdormant (not developed actively, but still somehow maintained)
Support statussupportable
Support provided byEvolveum
Target systemsOracle PeopleSoft Human Capital Management (HCM)
ProtocolLocal file I/O
Source code

A connector which is meant to provide identity information by reading the XML files exported from the Oracle PeopleSoft Human Capital Management (HCM) software. These files are viewed as individual resources which are connected to midpoint.

Capabilities and Features



Live Synchronization






Paging support


Native attribute names





Version Origin Binary Sources Build Date ConnId Framework Description


download jar


April 2017

Official release


The connector itself is available under the terms of Apache License 2.0. To our best knowledge there is no extra license needed to use this connector. (Additional licensing terms and conditions may apply with services on which the connector is used).


The basic parameters which are present in the configuration dialogue window are the following:

  • File path: The path to a XML resource file from the HCM resource. (e.g. ../hcm.xml)

  • Parser iterations: The number of employee records the parser iterates trough. This action is needed to generate the resource schema. The higher the number of iterations the higher the possibility that the schema will be complete.

  • Unique identifier name: The UID name of the user account attribute. Please select an identifier which is unique for each employee.

  • Name attribute: The secondary identifier attribute.

Setting up tests

A predefined set of test resources is present in the source bundle which can be found at our git repository. Additionally the tests can be modified via the file which contains the basic test properties which are the following:

  • filepath_xmlconsistent: Contains the path to a (valid) consistent xml resource which simulates the provided xml containing no flaws.

  • uid: The name of the unique identificator attribute.

  • secondaryid: The name of the Name attribute.

  • iterationcount: Number of iterations which the parser is permitted to execute for successful schema generation. If the number is higher than the actual number of identities present in the xml file than the number of iteration will be equal to the number of identities.

  • secondaryid_missing: Name of a secondary attribute which can be potentially non mandatory in the source system but which will be marked mandatory in midpoint. This will end up in an exception.

  • filepath_xmlinconsistent: A path to an XML resource file containing indentities but which is (non valid) inconsistent.

  • filepath_filenotfound: A non valid path to an XML resource file.

  • filter_equals_attr: Name of the attribute which will be used for an equals filter test.

  • filter_equals_value: The value used in the equals filter test.

  • filter_contains_attr: Name of the attribute which will be used for an contains filter test.

  • filter_contains_value: The value used in the equals filter test.

  • query_options_option: Name of the query option which will be used in a query.

  • query_options_value: Value which will be used in the query option.

Was this page helpful?
Thanks for your feedback