Device42 (D42) is a comprehensive IT infrastructure management platform that helps organizations discover, track, and manage their hardware, software, and network assets. By integrating Freshservice with D42, organizations can bridge the gap between their ITSM and asset management.


TABLE OF CONTENTS


Requirements
  • Device42 version 16.12.00+
  • Freshservice agent account with access to the Freshservice Marketplace.
  • Freshservice API token


Setting up the Integration with Device 42


Integrating Freshservice with Device 42 requires a few straightforward steps. Here's a step-by-step guide to help you get started:


Step 1: Obtain the API key from Freshservice 


Generate the API key in Freshservice to establish a secure connection between the two systems. Freshservice API key will serve as authentication credentials to import D42 devices and software items into Freshservice and also create relational mappings between them.


  1. Login to your Freshservice dashboard with an agent profile.

  2. Select the logged-in user profile in the top right corner of the page and navigate to profile settings.




  3. API token will be displayed on the right side of the page. Copy this code to use later to set up your integration in Device42.


Step 2: Configure the Freshservice API token in Device42.


  1. Access the Device42 menu bar and select "Secrets."

            

  1. On the "Select Password to view" page, click on "Add Password" located at the top right corner.

               

  1. In the "Username" field, enter a name for the API token. This can be of any value, but remember to use it when creating the integration later.

  2. In the "Password" field, enter the Freshservice API token. Make sure there are no white spaces or newline characters before or after the API token.

  3. Finally, save the API token by clicking on "Save" at the bottom right corner of the page.


Step 3: Setup Freshservice Integration in D42


  1. Access the menu bar and navigate to Tools > Integrations > External Integrations.

  2. Click on "Add External Integration," located at the top right of the page.

           
            

  1. On the integration configuration page, fill in the required fields, starting with your Freshservice URL (e.g., https://demo-instance.freshservice.com/).

  2. From the drop-down field labeled "Type," select the option for Freshservice.

  3. To populate the "Token" field, click on the magnifying glass icon and select the secret that contains your Freshservice API token.

  4. Once you have entered all the required fields, copy the displayed Verification Token. This token will be used later during the installation of the Device42 Freshservice App.

  5. Finally, click on "Save" at the bottom right corner of the page to save your integration settings.


Step 4: Install the D42 Integration app in Freshservice 


  1. Access the Freshservice dashboard and navigate to the Settings page.

  2. From the Settings page, go to the Agent Productivity section and select "Apps." Kindly ensure that you are logged in using an administrative account.

           

           

  1. On the Apps page, click the left arrow across Manage apps.

           
 
           

  1. Search for "Device42." You should find an application titled "Device42 For Freshservice." If multiple applications are listed for Device42, make sure to choose the one with this specific name and the option to install the application. If the install button says "Visit the site to install," close the window and select the other Device42 application.


  1. After selecting the Install button, you will be directed to a settings page where you need to provide certain information to proceed with the installation.

  2. Enter your Freshservice Domain Name, which is part of your Freshservice URL between "https://" and ".freshservice.com."

  3. In addition, provide a Cloud Connector. This can be either "connect.device42.net" or "connect-eu.device42.net." To determine the correct Cloud Connector, navigate to Tools > Settings > Global Settings and refer to the External Integration Settings section.

The Cloud Connector listed there will determine which option you should choose. If you are uncertain, feel free to contact Device42 Support for assistance in setting up your Device42 integration.


  1. With the latest version of Freshservice, a default approver is a new required field and should now be selected and set in the new section of the D42 Freshservice Application.


  1. Once you have entered the required fields, click the " Save " button located at the bottom right of the window.



How to set up Schedule syncs and run manual syncs?


Setting up and running syncs between Device42 and Freshservice is a seamless process that allows you to transfer discovered data efficiently. The integration eliminates the need for external environments and manual scripts, making the entire syncing process hassle-free.


Scheduled Sync:

  1. Access the Freshservice Dashboard and navigate to Settings > Apps.

  2. Locate the Device42 application among your installed applications and click on the settings icon associated with it.

  3. On the Device42 application settings page, you will find additional configuration options.

  4. To set up a scheduled sync, select the checkbox for the "Scheduled Sync" option.

  5. Choose the desired time for the scheduled sync to run. This allows you to specify when the sync will occur automatically on a daily basis.

  6. Once you have selected the checkbox and set the time, click "Save" to apply the scheduled sync settings.


Manual sync 


If you prefer to initiate syncs on-demand instead of setting up a scheduled sync job, you can easily run manual syncs between Device42 and Freshservice.


  1. Access the Freshservice Dashboard and navigate to Settings > Apps.

  2. Locate the Device42 application among your installed applications and click on the settings icon associated with it.

  3. On the Device42 application settings page, you will find the option to run a manual sync.

  4. Look for the "Manual Sync" button displayed on the page and click on it. This will expand a panel with additional options.

  5. In the expanded panel, you will have two sync options available:

    1. Full Sync: This option synchronizes all items from Device42 to Freshservice, regardless of when those items were added or updated in Device42.

    2. Partial Sync: This option only syncs items that have changed in Device42 (added or updated) since the last successful sync between the two systems.

  6. Select the appropriate sync type based on your requirements.

  7. If a sync is currently running, you will also have the option to stop the ongoing sync process using the provided button.

  8. Once you have made your selection, the manual sync process will be initiated, and the data transfer will take place between Device42 and Freshservice.

  9. Wait for the sync to complete, and you will see the updated data reflected in your Freshservice instance.


Full Sync Forced Upon Certain Upgrades


During certain upgrades, a full sync is forced to capture all new data from Device42 (D42). In the synchronization history, this forced full sync will be labeled as a "Full Upgrade." It occurs when there is a scheduled synchronization or a Partial Sync. This forced full sync happens once until a successful sync is completed.


How to view the sync history?


Viewing the synchronization history provides valuable insights for troubleshooting issues and monitoring the number of devices synced into Freshservice. Follow these steps to access the sync history:

  1. Access the Freshservice Dashboard and navigate to Settings > Apps.

  2. Among the installed applications, locate the Device42 application and click on the settings icon associated with it.

  3. From the options displayed, select "Sync History." This will take you to the sync history page, where you can view past synchronizations and ongoing ones.

  4. On the sync history page, you will find a table displaying the history of syncs. Each row represents a specific sync process.

  5. To view detailed logs associated with a particular sync, select the respective row in the table. This allows you to review any logs or additional information related to that sync.

Note: Keep in mind that the displayed text is limited to approximately 4000 characters.

  1. If you need to download the full logs for further analysis, you can use the "Download Full Log" button located at the lower-left corner of the text area. Clicking this button will initiate the download of the complete log file.


List of data types transferred from D42 to Freshservice



              D42 Data Type

 Freshservice Type      (General)

   Type (Specific)

Device with physical type and Laptop subtype

Assets/Inventory

Laptop

Device with physical type and WorkStation subtype

Assets/Inventory

Desktop

Device with physical type and Network Printer subtype

Assets/Inventory

Printer

Device with physical type and Router subtype (this is not a built-in subtype and would need to be created by the user)

Assets/Inventory

Router

Device with physical type and Firewall subtype (this is not a built-in subtype and would need to be created by the user)

Assets/Inventory

Firewall

Device with OS of F5 or NetScaler

Assets/Inventory

Load Balancer

Device with Network Device flag set

Assets/Inventory

Switch

Device with physical type and Windows Server OS

Assets/Inventory

Windows Server

Device with physical type and Unix or Linux OS

Assets/Inventory

Unix Server

Device with physical type and AIX OS

Assets/Inventory

AIX Server

Device with physical type and SunOS or Solaris OS

Assets/Inventory

Solaris Server

Device with Virtual/Container Host flag set and ESXi OS

Assets/Inventory

VMware VCenter Host

Device with Virtual/Container Host flag set

Assets/Inventory

Host

Device with virtual type and VMWare subtype

Assets/Inventory

VMware VCenter VM

Device with virtual type and Amazon EC2 Instance subtype

Assets/Inventory

AWS VM

Device with virtual type and Azure Virtual Machine subtype

Assets/Inventory

Azure VM

Device with physical type and does not match one of the more specific asset types above.

Assets/Inventory

Server

Device with virtual type and does not match one of the more specific asset types above.

Assets/Inventory

Virtual Machine

Device that doesn’t match one of the more specific asset types above

Assets/Inventory

Computer

Business Applications

Assets/Inventory

Business Service

Software

Assets/Software

Desktop

PO Line Item/Contract Type: Warranty

Assets/Contracts

Warranty

PO Line Item/Contract Type: BASE

Assets/Contracts

Warranty

(IBM & Lenovo vendors)

 

 

PO Line Item/Contract Type: UPGRADE(IBM & Lenovo vendors)

Assets/Contracts

Warranty

PO Line Item/Contract Type: Lease

Assets/Contracts

Lease

PO Line Item/Contract Type: Service and all others

Assets/Contracts

Maintenance

Software Licensing (only for managed software and can come from software or the PO line item)

Assets/Contracts

Software License

Business Applications Device-to-Device Relationship

Relationships between assets

Sends Data To / Receives Data From

Business Application to Device Relationships

Relationships between assets

Hosted On / Hosts

Affinity Group Device-to-Device Relationships

Relationships between assets

Depends On / Used By

VM to Host Relationships

Relationships between assets

Virtualized by / Virtualizes


Freshservice - Device 42 data mapping 

  1. Data Mapping UI


With the updated Data Mapping UI, users can now view additional mapping types available on the Data Mapping Chart screen. This enhancement expands the types of information that can be mapped, including warranties, licenses, business apps, and more. Previously, users were limited to mapping devices and software types only.




  1. Access Current Data Mappings


To view the current data mappings between Device42 and Freshservice, follow these simple steps:


  • Navigate to the Freshservice Dashboard and click on "Settings" followed by "Apps" in the sidebar menu.

  • Among the installed applications, locate the Device42 application and click on the settings icon associated with it.

  • From the options displayed, select the "Data Mapping" button. This will take you to the Data Mapping page.

  • On the Data Mapping page, you can easily view the fields from Device42 that are currently mapped to Freshservice for both device and software items.






  1. View Mapped and Unmapped Data for Specific Assets


To easily access and view mapped and unmapped data for a device within Freshservice, follow these steps:


  • From the Freshservice Dashboard, navigate to "Assets" and select "Inventory."




  • On the inventory screen, locate and select the asset that has been imported from Device42. This is the asset for which you want to view the mapped and unmapped data.

  • On the right panel of the page, you will find the Device42 application. Click on it to expand the application details.

  • Once the Device42 application window is expanded, click on the "View Device42 Data" button.




  • A new window will open, displaying the mapped and unmapped data for the selected device. This allows you to conveniently view all the required fields from one location, eliminating the need to navigate between applications.




  • Additionally, if you choose to close this window and select the "View Asset in Device42" option, you will be redirected to the corresponding asset within the Device42 application.