Import configuration for Jamf Importer
- Pio
1-Build Objects/Attributes
Once you completed Source and Destination configurations, now it is time to create Object Types and their relations according to the Jamf Pro data model.
You may also choose to enable or disable Object Schema sharing.
Pro Tip: Commonly, our customers create references from other Object Schemas and are in need of accessing the Jamf data. We recommend enabling the Object Schema sharing.
Click the Build Data Model button.
This needs to be done only one time. When this build is completed successfully you don't need to do it again. You will get a message if you already completed this step.
You may check your new Object Schema now and make sure the Object Types and Attributes are successfully created.
The Object Schema Graph will be as follows:
 |
2- Test Run
You can test the configuration by clicking the Test Run button. This will import the first 100 Computers to your Object Schema. After the test run wait for a few minutes for the process to finish and check your Object Schema.
You may click the Check Test Import Status button to check the import execution status.
3- Import Run / Schedule
If you are happy with the results of the test run, please choose an option for a final run from below. The maximum number of records you can import is 1000 by default. You can update this value from the Admin tab.
You have 3 options.
Option 1: Import Run
Use this option to execute a full Jamf import manually.
Pro Tip: Please note that if you have a large number of records, this import will take time. We suggest testing it outside of the busy hours when JSM is not used heavily.
Option 2: Enable Daily Import Scheduling
When enabled, the import will run once a day.
Pro Tip: This is the most common import schedule among JSM customers.
Option 3: Enable Hourly Import Scheduling
When enabled, the import will run once an hour.
Pro Tip: We recommend importing manually first and measuring the import duration. In case a full import takes long time (i.e. an hour), or if there are multiple imports schedduled at the same time at your JSM Site, then hourly scheduling may not be the best option. Then use Daily scheduling.
Due to the nature of Atlassian’s Forge platform, the scheduling repeatedly invokes a function on a scheduled interval. Each trigger is scheduled to start shortly after it is created, about 5 minutes after app deployment. For that reason, it is not possible to set at which minute the scheduled import will run. Refer to Atlassian’s Documentation.