For configuring provisioning , you will need access to Platform configuration console.

1. Open the Administration area (a gear symbol).
2. Open Connectors view.
3. Choose "New connector" 

4. Select Data Source type to be Generic REST API

5. Give name for the connector and add connection settings:

• Connector name - give your connector a friendly name (name can be changed afterwards)
• Host url - base url for REST API. https://<YOUR_RAYNET_URL>.raynetone.com/v1/resultDatabase (for example: https://matrix42-demo-datahub.raynetone.com/v1/resultDatabase)This can be used as prefix for final url to be called. 
• REST Connector type - select Generic
• Authentication method - Auth Header
• Authentication Header Name - ApiKey
• Authentication Header Value - value of your apikey
• Pagination Type - Page Increment
• Pagination Page Attribute - page
• Pagination Page Start - 1
• Pagination Page Size Attribute - page_size
• Pagination Page Size - 500 (if you want to use bigger page size, confirm from Raynet documentation that they support that page size)

6. Fulfill WebAPI user information

• WebAPI user - select correct WebAPI user which is used when writing data from external system to Matrix42 Core, Pro and IGA solutions
• WebAPI password - password for the WebAPI user

8. Save connector information

9. Add Raynet root https certificate to be trusted by Connector management (EPE). This can be done only by Matrix42 following this guidance Add certificate.  Raynet uses usually “ISRG Root X1” root certificate, which you can download using "base 64 encoded single certificate pem"-format from here: https://letsencrypt.org/certificates/

10. Matrix42 Core, Pro and IGA solution is now able to connect to Raynet

• Next step is to configure scheduled task for data read or event task for data writing and actions towards Raynet. 

In this chapter we add scheduled task to read data from Raynet. 

1. Add Scheduled task under correct Connector, by clicking “New Task”

2. Set Task attributes

Scheduling - Set scheduling if needed

Task name - Set informative name

Task usage - Scheduled

Mapping type - Generic Template

Query - Query depends on what data you want to fetch. 
In this example we fetch users using: resultTable/paged?tableName=DataTransformation-result_devices which basically will fetch all data from Raynet DataTransformation-result_devices -table.

Sub Queries - You can add subqueries if you want to read more data related to resultset returned by actual Query. In this example we are not using subqueries.

Query headers - for Raynet we need to add these headers:
Accept / application/json
Content-Type / application/json

Value Marker - records

Error Marker - leave this empty

Safety threshold for API calls - suggested to be set twice as big as how many pages this API will return. If you leave it empty there is no safety threshold and then Connector can go to infinite loop if there is error in configuration.

Unique Attribute - Unique attribute on API resultset. In this case import_id

3. Fill in failure information

Optional settings for failure handling, if scheduled task fails it can create data card to ESM that displays the error. If failure settings are defined, the administrator does not need to manually check the status of scheduled tasks.

• Failure template - Select a Template of datacard which will be created in case of any errors during provisioning (connection to data sources, timeouts, etc.)
• Failure folder - Select folder where failure data card is stored.
• Failure attribute - Select an attribute where in the Failure Template should the error information be stored in. Select text type attribute.

4. Fill in Generic mappings information

In mappings section you configure which attribute from JSON message is read to which attribute on Matrix42 Core, Pro and IGA datacard.

• Target template - Select a template to define attribute mappings (in this example Device as we are fetching devices)
• Target folder - Select a folder from a list of folders. The list is narrowed down to match compatibility with selected Template. (in this example Asset/Servers)
• Data Source Type mapping - optional. If it is set, it writes connectors type to that attribute.
• Task Id mapping - Task id number is written to this attribute. Correct attribute to choose depends on how your Template is configured.
• Set value to datacard fo object deleted from source system - This functionality is activated by setting checkbox on. When some object that was previously read from 3rd party system to solution is deleted from 3rd party system. This scheduled task notices that is was deleted and marks that datacard selected attribute with value you want. This can be for example used to set Status attribute to Deleted. This Attribute name and Attribute value needs to be set based on how your Template is configured. 
• See supported mapping syntaxes: https://docs.efecte.com/configure-connectors/jsonpath-mappings-for-generic-rest-api-connector 

• Attribute mappings
  1. External attribute - which attribute from the Raynet API is read from JSON body
  2. Local attribute - to which attribute in Matrix42 Core, Pro and IGA attribute is mapped to
• It is possible to set additional attributes to attribute mappings, by choosing New attribute
• You need to add mapping also to Unique Attribute, in this example it is import_id. That needs to be mapped to unique attribute on template, in this example Name.
• first mapping uses subquery to map users group memberships to multiValueField attribute. Other mappings are for main query user attribute mappings. 

5. Save provisioning task from the Save button. 

If some required attributes are missing the save button is displayed as grey and it will display what is missing from the settings.

6. You have now configured scheduled-based connector task

• You can now wait until task is started based on scheduling or
• Run task manually - by clicking the “Run Task” button on top of task edit window, task is configured to be scheduled to start immediately. Usually for test runs or if you don't want to change the schedule settings, but want to run the task now.   

Example of manual task run starting message:

If task is executed manually (run task) or it is run according to scheduling, task status can be reviewed from Scheduled tasks list manage column, by clicking “View history” button.

Raynet API contains filtering capabilities, which can be used from Native Connectors. 
Raynet API documentation related to filter functionality Raynet 2025.3 release notes 

To use filter in query attribute of task, you need to url encode filter value manually or using some website (for example https://www.urlencoder.org) to do the encoding.

Filter example without url encoding(does not work): resultTable/paged?tableName=DataTransformation-result_devices&filter=["device_manufacturer","=","HP"]
Same example url encoded(works): resultTable/paged?tableName=DataTransformation-result_devices&filter=%5B%22device_manufacturer%22%2C%22%3D%22%2C%22HP%22%5D

If your Raynet environment has both of these tables: DataTransformation-result_devices and Catalog_v2_SoftwareOnDeviceMatching you can fetch Devices with Query and installed softwares with Sub Query.

Query: resultTable/paged?tableName=DataTransformation-result_devices 

Subquery: resultTable/paged?tableName=Catalog_v2_SoftwareOnDeviceMatching&filter=["ComputerId","=","{import_id}"]

One example mapping for device attributes, using query:

Mapping for devices installed softwares, using subquery:

resultTable/paged?tableName=Catalog_v2_SoftwareOnDeviceMatching&filter=["ComputerId","=","{import_id}"].SoftwareId

Restrictions in 2025.3

More than 1 level of subqueries for scheduled tasks are not supported, for performance reasons.