Information that will help you design and plan the implementation of 1E Core 2.0 in your organization.

This page is part of the design phase of implementation.

The implementation of 1E Core is straightforward. Assuming you have already implemented the Tachyon infrastructure, the only significant choices required before installing 1E Core are described below.

For a full list of requirements, please refer to Requirements. Once you have made the implementation choices below, satisfied Requirements, completed Preparation steps, then you can continue with Installing 1E Core.

On this page:

MID Server

When ServiceNow is not able to access the Tachyon Server (Master Stack) over the internet then you require a MID Server. In this scenario both the Tachyon Server and the MID Server are installed on the local network and able to communicate, the MID Server can then access ServiceNow on the Internet, thereby acting as a bridge between the two.

A MID Server is a software application which gets installed on any local machine with internet connectivity, can access Tachyon Server on the local network and is configured to point to the desired ServiceNow instance on the Internet.

MID Servers are specific to the release version of ServiceNow and must be downloaded from the ServiceNow instance itself. For more information about MID Server set up, please refer to the ServiceNow MID Server installation documentation.

Multiple MID Servers can be installed on a single machine and be able to point to the same or different ServiceNow instances, however you will only be able to set the 1E ServiceNow app to use one of them.

Tachyon Users and Roles

1E Core provides ServiceNow with access to Tachyon instructions in order to provide functionality to 1E ServiceNow solutions (such as 1E ITSM Connect and 1E Service Catalog Connect). 1E Core has two roles - one for 1E Core administration and another that is inherited by the 1E solutions' accounts.

The following table describes the 1E Core app roles. 

Role nameAdditional ServiceNow roles requiredDescription

This role allows its users to configure and set up the 1E Core app.

ServiceNow admin users must change their application scope to 1E Core in order to configure the app, and retrieve instructions.


This role is inherited by the 1E ServiceNow solution roles.

Compatibility matrix for ServiceNow apps with 1E Core and Tachyon Platform

The following table contains details of all currently supported 1E ServiceNow integration apps. Use this table as a reference to ensure you are using the correct combination of apps for your needs. Each app is dependent on the 1E Core app and a Tachyon installation.

1E ServiceNow AppVersionSupported versions of 1E platformSupported versions of ServiceNowPurpose
1E ITSM Connect


5.2, 8.0, 8.1 Quebec, Rome, San Diego

Integrates ServiceNow ITSM with Tachyon, to provide real-time inventory and pre-approved automated fixes to first line teams from within the ServiceNow Incident page. 

Support for 1E Core (new in 2.0.0).

Tachyon Device View and Experience integration (new in v3.0).

Support for domain separation (multi-tenant) (new in v3.1).

Support for 1E CMDB Connect app (new in v3.2).

1E Service Catalog Connect


5.2, 8.0, 8.1 Quebec, Rome, San Diego

Integrates ServiceNow Service Catalog with Tachyon. Provides a UI like 1E Shopping – allows WSA to be invoked by ServiceNow and report WSA requests.

Guided Tour, and running any Tachyon instruction (new in v2.0.1).

1E Virtual Assistant


5.2, 8.0, 8.1 Quebec, Rome, San DiegoProvides a Virtual Agent for ServiceNow, supporting various topics, some of which use Tachyon instructions.
1E Core


5.2, 8.0, 8.1 Quebec, Rome, San Diego 

Platform enabler. Provides copy of Tachyon instructions.

Support for domain separation (multi-tenant) (new in v2.0).

Support for 1E CMDB Connect apps (new in v2.1) including Service Graph Connector for 1E Tachyon.

Service Graph Connector for 1E Tachyon


5.2, 8.0, 8.1 Quebec, Rome, San Diego

1E Tachyon CMDB Connect, and Service Graph Connector for 1E Tachyon, provide identical capabilities, your choice depends on your licensing.

Either one can be optionally used for the following, among other features:

  • populate device data in ServiceNow's CMDB through 1E Core and Tachyon
  • provide the device FQDN required by other 1E ServiceNow apps, so they can use Tachyon.

The latter requirement may also be met by any third party app capable of populating the device FQDN in the ServiceNow CMDB cmdb_ci_computer table.

Change target from cmdb_ci_pc_hardware to cmdb_ci_computer (new in SGC 1.2.2).

Populates installed software, disk usage and network attributes. Also provides custom table for uninstalled software (new in SGC 2.0.0). 


5.2, 8.0, 8.1 Paris, Quebec, Rome
1E Tachyon CMDB Connect


5.2, 8.0, 8.1 Paris, Quebec, Rome