Summary

Information that will help you design and plan the implementation of the 1E Service Catalog Connect app in your organization. This includes all the prerequisites and dependencies that are necessary to install the 1E Service Catalog Connect app.

This page is part of the design phase of implementation.

On this page:

Windows Servicing Suite requirements

CategoryRequirementMore Details
Windows Servicing Suite (WSS)
  • A complete Windows Servicing Suite infrastructure is required, including Nomad, Shopping, and its other key components.
Windows Servicing Suite 3.0 - Implementation
Windows Servicing Assistant (WSA)
  • The Windows Servicing Assistant component of WSS must be enabled.

Shopping 5.6 - WSA Deployment Applications

Microsoft System Center Configuration Manager (ConfigMgr)
  • ConfigMgr (also known as SCCM) is needed for WSS to provide its services. Therefore, ConfigMgr and its prerequisites must be installed and configured as per the ConfigMgr and WSS documentation.
Windows Servicing Suite 3.0 - Prerequisites
Shopping
  • 1E Shopping is part of WSS and is required for WSA. You must configure Shopping correctly as per the WSS, WSA, and Shopping documentation.
  • Shopping v.5.5.200 or later is required.
  • For Shopping 5.5.200 in particular, hotfix Q20575 or later is also required.

1E Support Portal - Shopping


Tachyon requirements

CategoryRequirementMore details
Tachyon system
  • A complete Tachyon v4.1 or later infrastructure is required either in local network or hosted over the internet.
  • 1E Client v4.1 must be deployed to all computers that could invoke the WSA wizard.
  • Two-factor authentication must be disabled for Tachyon.
  • The Basic Authentication feature must be installed on the Tachyon Server (Master Stack), and enabled in the Consumer web application.
  • For 1E Client v4.1 in particular, hotfix Q20507 or later is also required.

Tachyon 5.0 - Installing and upgrading

1E Core - Preparation: Disable Tachyon Two-factor Authentication

Preparation: Enable Basic Authentication

1E Support Portal - Shopping

Tachyon consumer
  • A Tachyon consumer with the name 1EServiceNowCore must be registered in the Tachyon Settings application, Configuration, Consumers page.
  • The Workflow column of the dbo.Consumer table in the Tachyon Master database for this consumer must have the value:

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

  • The workflow value is not set automatically, so be sure to see the link to the right to set the value.

  • After changing the value, the Tachyon Consumer service and IIS services must both be restarted.

1E Core - Preparation: Add the ServiceNow consumer to Tachyon

1E Core - Preparation: Editing the ServiceNow consumer workflow

Tachyon user

  • A Tachyon user with Actioners role on required instruction sets and management groups, used for the 1E Service Catalog Connect app user role in ServiceNow.

The users must be an AD domain account. This account does not belong to a specific person and can be regarded as service account, and does not require an email address.

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

Design Considerations: Tachyon Users and Roles

Preparation: Add the Service Catalog Connect app user to Tachyon

Post-Installation Tasks

Tachyon actioner

  • A Tachyon user with the Global Actioner role, or one or more users with the following roles:
    • Permissions Administrators role in order to create the above users and assign them to roles. Also create custom roles, and assign them to some instruction sets and management groups.
    • Consumer Administrators role in order to register the ServiceNow consumer.
  • Optionally a Tachyon user with the Global Administrator role, or the following roles:
    • Instruction Set Administrators role in order to upload instruction definitions and create instruction sets
    • Management Group Administrators role in order to create Management groups if desired

Users must be AD domain accounts. The above system roles can be substituted for equivalent custom roles.

Design Considerations: Users and roles

Preparation: Add the Service Catalog Connect app user to Tachyon

Tachyon license
  • Your Tachyon license should contain the ServiceNow-Integration feature tag.
Preparation: Check your Tachyon license

ServiceNow requirements

CategoryRequirementMore details
ServiceNow
  • A working ServiceNow instance must be set up. This can be a demo instance or a production/vendor instance.
  • The following versions of ServiceNow are supported:
    • Orlando
    • New York
    • Madrid

Installing 1E Service Catalog Connect

1E CoreInstall the latest version of 1E Core application into your ServiceNow instance. Request the latest version of 1E Core from the ServiceNow Store. Minimum supported version is 1.0.8.
MID Server
  • If the Tachyon instance is not hosted over the internet then a MID Server must be installed on the same network domain where the Tachyon server is installed.

Please refer to your ServiceNow documentation for details on installing a MID server.

Design Considerations: MID Server

ServiceNow users
  • At least one ServiceNow user for each of the roles in the following table:
    Role nameAdditional ServiceNow roles requiredDescription
    x_1e_service_catal.shopping_adminn/a

    This role allows its users to configure the 1E Service Catalog Connect app, in addition to having the same rights as the x_1e_service_catal.shopping_user role.

    ServiceNow admin users must change their application scope to 1E Service Catalog Connect in order to configure the app.

    x_1e_service_catal.shopping_usern/a

    This role grants its users access to invoke WSA and select catalog items tied with tachyon instructions.

Design Considerations: Users and roles

Post-Installation Tasks

User Management

ServiceNow admin
  • This role allows its users to install and configure the 1E Service Catalog Connect app.

Installing 1E Service Catalog Connect

Compatibility matrix for ServiceNow apps and the 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.

IntegrationVersion1E on-premises1E SaaSServiceNowPurpose
1E ITSM Connect4.2.08.0, 8.18.2, 8.4Rome, San Diego, Tokyo

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. 

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 (new in v3.2).

ROI Dashboard; Device views (Hardware, network, s/w installations etc.); Flexible Quick fixes menu; Guided Setup; Prioritized Recommended actions; Device History; Configurable retrieval of device stats (Online status, Last reboot, Last seen etc.); Scheduled retrieval of 1E Tachyon instructions; Improved error handling logic; (new in 4.0.0).

Agent Workspace features not available in San Diego release (new in 4.1.0).

CI selector based on Caller name. Instruction segmentation based on user role (new in 4.2.0).

Support for OAuth2 required by 1E SaaS. Requires 1E Core 3.0 (new in 4.2.0).

4.1.08.0, 8.1
4.0.08.0, 8.1
Rome

3.2.1

8.0, 8.1
Rome
1E Service Catalog Connect3.1.08.0, 8.18.2, 8.4Rome, San Diego, Tokyo

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

Installation of software applications via 1E Shopping (new in 3.0.0).

Support for OAuth2 required by 1E SaaS. Requires 1E Core 3.0 (new in 3.1.0) 

3.0.08.0, 8.1
San Diego Patch 5, Tokyo

2.0.1

8.08.1
RomeWithdrawn.
1E Virtual Assistant3.0.18.0, 8.18.2, 8.4Rome, San Diego, Tokyo

Provides a Virtual Agent for ServiceNow, supporting various topics, some of which use Tachyon instructions.

Support for OAuth2 required by 1E SaaS. Requires 1E Core 3.0 (new in 3.0.1).

2.0.1

8.0, 8.1
1E Core

3.0.0

8.0, 8.18.2, 8.4Rome, San Diego, Tokyo

Platform enabler. Provides a 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.

Support for OAuth2 required by 1E SaaS (new in 3.0.1).

Service Graph Connector for 1E TachyonTBD 8.0, 8.18.2, 8.4TBD

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

2.0.0

 8.0, 8.1
Rome, San Diego, Tokyo
1E CMDB Connect1.1.0 8.0, 8.18.2, 8.4Rome, San Diego, Tokyo

See above, details as Service Graph Connector for 1E Tachyon.

1.0.0

 8.0, 8.1
Rome, San Diego, Tokyo

See above, details as Service Graph Connector for 1E Tachyon.

Support for platform 5.2 ceased in December 2022.