Requirements

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.

Windows Servicing Suite requirements

Category	Requirement	More 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 6.1 - 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

Category	Requirement	More details
Tachyon system	A complete Tachyon v5.1 or later infrastructure is required either in local network or hosted over the internet. 1E Client v5.1 or l;ater 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 ensure all hotfixes have been applied.	Tachyon 8.1 - 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

Note

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 name

Additional ServiceNow roles required

Description

x_1e_service_catal.shopping_admin

n/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_user

n/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