Cherwell Integration with Device42

Bring the power of Device42 autodiscovery to Cherwell for better ITSM

Using the Device42-Cherwell sync integration,users can synchronize data from Device42 to Cherwell. The integration script brings Device42’s enhanced asset management and tracking capabilities to Cherwell.

Device42's comprehensive agentless autodiscovery, optional agents, and remote collectors automatically maintain an up-to-date inventory of your physical, virtual, and cloud servers, containers, network components, software, services, and applications - and their critical interrelationships and interdependencies.

Sync your CIs between Device42 and Cherwell

Once you sync your Device42 CMDB with Cherwell, any CIs that were configured to sync will be available in both systems. If you are transitioning from Cherwell to Device42, this integration makes the move a breeze!

If both systems are to remain in concurrent use, the CI data can be kept up-to-date by scheduling automatic syncs, and can be refreshed manually at any time!

Cherwell Integration

Associate imported CIs with Cherwell requests!

When a creating a new request in Cherwell, users can choose to associate configuration items synced from Device42. They can then be managed natively within Cherwell, utilizing the task management workflow you’re already used to. Assign teams and create task checklists related to CI’s imported from Device42.

Cherwell Integration

Sync hardware, software and services, vendor information and more from Device42

Leverage the CI details you already have in Device42 to sync anything from software and services, to service levels and customers (and much more) into your Cherwell instance. Use this imported information to create custom service request workflows, and tailor them to your unique needs!

Hardware and software, networks and servers, and any other details from a wide range of CI information can be synced from Device42 to your Cherwell instance [simply map Device42 fields (“resource” values) to Cherwell fields (“target” values) within the mapping.xml file, and associate each with a business object ID in Cherwell - see readme.md]. Synced software information can include all relevant licensing information along with supplementary information such as tags, category, vendor, a description, and any aliases that might be in use. Synced Service information includes service name, description, category, tags, and the associated vendor as well.

Vendor information can also be synced from Device42. The default configuration includes the Vendor’s name and the vendor’s home page. Notes, contact information, and escalation information for troubleshooting and support contacts can also be synced if those target fields are created in Cherwell.