Configure the connection to Oracle HCM JAMF by going to OnLink (Manage your apps) - Connections. Then click on Add System and select “HR Idm/Device Assets Sources”. Refer to this link for information on getting API credentials: https://learn.jamf.com/en-US/bundle/jamf-pro-documentation-current/page/API_Roles_and_Clients.html
Once connection is established, please review instructions here to get started with setting up an Assets import configuration. You can then access OnLink app from the “Manage your apps” menu to further configure and set the field level mapping.
Here’s an example mapping configuration when pulling in computer data. Any field available in this Oracle API can be used to map to the asset attribute.
key:PersonNumber=WorkerIDmobile_device.id=Device ID
map:WorkEmail=Usermobile_device.serial_number=Serial Number
map:FirstName=First mobile_device.device_name=Device Name
map:LastNamemobile_device.name=Last Name
map:assignments.0.ManagerId=ManagerUserIdmobile_device.model=Model
Here’s a breakdown of some of the mapping configuration items:
Key or Map | Description |
---|---|
| The keyword “key” refers to using Worker ID as a unique identifier. This allows OnLink to update the record. |
| Maps device name to attribute |
| Can be set to any other API from Oracle as well - https://docs.oracle.com/en/cloud/saas/human-resources/24c/farws/op-emps-get.html JAMF as well. Update the mapping based on the API response to import data from any Oracle JAMF API to JSM Assets |
Any other field returned by the API can be used in the mapping.
...