To ensure that the integration runs successfully, test the integration and complete a dry run.
When you select Test Run, the integration data will not be imported into Oomnitza.
To test the integration, click Test Run.
Copy the response payload to the clipboard for reference.
When you want to import the data, click RUN Now.
The information that is collected about assets is shown on the All Assets page under the Hardware menu. For user integrations, the option for user selection that was selected determines where the information is shown. If you selected users, the user records are shown on the People page. If you selected user and SaaS user, the records are shown on the People page and on the Software > SaaS page.
To review your results you can click the Errors number in the upper right of the screen, or click Sync sessions. When the integration runs, records are processed.
While results come in in real-time, completion is only checked every 30 minutes, so the "loading" icon may continue spinning for some time after all results have been processed.
You can see individual results by clicking on a session that is running. Check the Status in the Information tab to determine if the integration is Complete or Complete with errors.
A successful integration should indicate the number of updated records. To view the updated records, navigate to the People, Software or Assets module, depending on the type of integration you selected. Click History in the sidebar to view when the record was created.
Complete with errors
A failed integration displays the response error in the Response Code field.
The Error Logs tab can also provide additional information relating to the API error. The example below shows a successful integration that failed for one object or user. In this instance, the Error Log displays additional information relating to the failed integration.
Add related integration
The Add Related Integration feature enables you to add child integrations to your integration. When you select this feature all settings are inherited from the current integration. This feature may be particularly useful if you want to create a duplicate integration with an almost identical configuration, such as an AWS user load, where only the AWS region in the Integration details needs to be changed.