Requirements

1E system

• For Basic Authentication

  A complete infrastructure of 1E (on-premises) is required, either in a local network or hosted over the internet. This includes the 1E Client, deployed to all devices that you need to manage.

  The Basic Authentication feature must be installed on the 1E Server (Master Stack), and enabled in the following 1E web applications: Consumer and Experience

• For Modern Authentication

  A complete infrastructure of 1E (Saas) is required, either in a local network or hosted over the internet. This includes the 1E Client, deployed to all devices that you need to manage.

  The Modern Authentication is to be setup either using Microsoft Entra ID or Okta for external IdP.

1E license

• Your 1E license should contain the ServiceNow-Integration entitlement

• The 1E license should contain the following consumer in the ServiceNow Integration feature tag:

  Copy

  <Feature name="ServiceNow-Integration">
  <Consumer name="1EServiceNowCore" enable="on">
  </Consumer>
  </Feature>

1E consumer

• A 1E consumer with the name 1EServiceNowCore must be registered in the 1E Settings application, Configuration, Consumers page.

• The Workflow column of the dbo.Consumer table in the 1E Master database for this consumer must have the following value:

  Copy

  [{"ReferenceType":0,"InstructionWorkflow":[{"InstructionType":1,"Workflow":{"StateMachine":"State"}}]}]

1E proxy user

• A 1E user with Full Administrator role on any required instruction sets and management groups.

• The 1E user must be an AD domain account. This account does not belong to a specific person, and can be regarded as a service account, it does not need an email address.

• 1E roles can be predefined system (Global) roles or custom roles. Global roles have permissions on all instructions sets and all devices. Custom roles can be optionally configured for all instruction sets or limited instruction sets, and all devices or management groups.

• The following are 1E instructions that the 1E user must have permissions to execute:1E ITSM Connect Actioner

SQL Server

• A SQL Server database instance is required to retrieve Software related data and CI specifications for the following databases:

  • SLA-Data

  • SLA-Shared 

  • TachyonMaster

  • TachyonResponses.

1E Core

• The latest version of the 1E Core needs to be installed and configured on your ServiceNow Instance.

ServiceNow

• A working ServiceNow instance must be set up, this can be a demo instance or a production/vendor instance.

• The application supports the latest ServiceNow releases. For more details on the supported releases, refer to Compatibility matrix for 1E and ServiceNow integration applications.

• Install the plugin Service Graph Connector Dependencies, this will install data Stream Action Template, ITOM licensing, and a few other plugins that are needed to use a SGC.

• Activate the Software Asset Management Professional (com.snc.samp) plugin to insert the software related data into cmdb_sam_sw_install table, else the data is placed into cmdb_ci_spkg_list.do table by default.

• In ServiceNow discovery source list, add an entry for SG-1ETachyon.

MID Server (Basic Authentication)

• You require a MID Server when your 1E Platform instance is installed on-premises (that is, does not have a direct connection to your ServiceNow instance in the Cloud).

• The MID Server must be installed on the same network domain as the 1E Platform server. It must be able to connect to the 1E Platform server (specifically the Master server hosting the Coordinator service).

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 here.

ServiceNow users

• ServiceNow's users are needed as defined in the 1E Core documentation.

• To administer the SGC for 1E application, you require a user with the x_1e_cmdb_connect.admin role.

• To use 1 Information Services module, you need a user with the x_1e_cmdb_connect.config_manager role.

• To view CI information fetched from 1E and the related lists, you require a user with the x_1e_cmdb_connect.user role.

ServiceNow admin

• This role allows its users to install and configure SGC for 1E.