ManageEngine Endpoint Central to JSM Assets

Ref: https://www.manageengine.com/products/desktop-central/api/

We support “Generating Authentication Key using API tool” (ref: https://www.manageengine.com/products/desktop-central/api/ )auth mechanism described above. You need username and password. Choose “All Other Asset Sources” and ManageEngine Endpoint to add this connection. URL should be the base URL of your Endpoint Central system. Base URL should be https://<Server URL>/api/{Version} e.g https://test.manageengine.com/api/1.4

Once connection is established, you can configure the api in your Asset mapping configuration:

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:

key:resource_id=id
map:os_version=OS Version
map:os_platform=OS Platform
map:status_label=Status

Here’s a breakdown of some of the mapping configuration items:

Key or Map	Description

Key or Map	Description
`key:resource_id=id`	The keyword “key” refers to using id as a unique identifier. This allows OnLink to update the record. “id” is a text attribute.
`map:os_version=OS Version`	Maps os_version to OS Version text attribute
`map:os_platform=OS Platform`	Maps os_platform to OS Platform text attribute
`config:api`	Set to api e.g. config:api=inventory/scancomputers
`config:installstatus=21`	Fetch only devices with install status of 21. Refer below for additional filter details.

Filter for Get Inventory Computers and Scan Details

Following are the filters supported by OnLink

installstatusfilter

21: Yet to install (agent has not been installed).
22: Installed (agent is currently installed).
23: Uninstalled (agent has been removed).
24: Yet to uninstall (marked for uninstallation but not yet removed).
29: Installation failure (an error occurred during installation).

config:installstatus=21

scanstatusfilter

-1: Not done scan has not started.
0: Failed scan failed.
1: In progress scan is ongoing.
2: Success scan completed successfully.

config:scanstatus=2

Once connection is established, you can use Fetch API Sample to get user data and complete the mapping.

OnLink processes data in two steps - Get Data and Import Data. To manually test, you can click on Get Data first and then wait until you see “No more pending records. Data will be imported on next Import run.” message in Job Logs. Then, click on Import. Production runs are fully automated based on the schedule you choose.