Gate Installation Procedure

Library: Track & Trace Documentation Library
Document: Gate Installation Procedure
Document code: IMP_IP002
Version: 2
Effective date: June 1, 2022

Contents

• 1 Standard Description
• 2 Server Infrastructure
• 3 Prerequisites
  • 3.1 Application Server Recommendation
  • 3.2 Database Server Recommendation
  • 3.3 ALOHA Load Balancer
• 4 Server Configuration and Accessibility
  • 4.1 Prerequisites
    • 4.1.1 How to Check .NET Version with PowerShell
    • 4.1.2 SSL Certificate Installation on Application Server
    • 4.1.3 How to Import Certificate on Application Server
    • 4.1.4 HTTP Configuration Utility
  • 4.2 Service Account Creation
    • 4.2.1 Adding Service Account to Administrator Group
• 5 Installation Steps
  • 5.1 Database Installation
    • 5.1.1 Gate Database Requirements and Naming Convention
    • 5.1.2 DAC Package Installation
    • 5.1.3 Gate Database View Update
    • 5.1.4 GLA Database Configuration
  • 5.2 Application Installation
• 6 Application Configuration
  • 6.1 Application Settings
  • 6.2 Operation Drivers
  • 6.3 Layouts Configuration
• 7 Vault Connection
• 8 New Market Setup
  • 8.1 Prerequisites
  • 8.2 Configuration
  • 8.3 Description of the Configurable Settings
  • 8.4 Configure Manufacturing Market
• 9 Document Control
  • 9.1 Contact Person
  • 9.2 Revision History
• 10 References
• 11 Conversion and Preservation Notes

---

1 Standard Description

This document explains how to install Inextor Gate step by step.

2 Server Infrastructure

Gate requires the following server infrastructure:

• Two server instances for the Gate application, node one and node two, balanced by the load balancer
• Two database server instances configured as an Always On availability group
• Two server instances for the ALOHA load balancer

Depending on the Track and Trace requirements for the factory, server requirements should be clarified with the Business Technology Services team.

3 Prerequisites

3.1 Application Server Recommendation

Capacity	RAM	CPU
Maximum	8 GB	4
Minimum	4 GB	4

Additional requirements:

• Windows Server 2016 Standard or later
• 1 TB disk space minimum

Source preservation note: The source labels this table as RAM SQL Server and CPU SQL Server, although it appears under Application Server Recommendation. The values are retained without reinterpretation.

3.2 Database Server Recommendation

Capacity	RAM	CPU
Maximum	40 GB	12
Minimum	32 GB	8

Additional requirements:

• Windows Server 2012 R2 Standard or later
• 120 GB disk space minimum

Source preservation note: The source labels this table as RAM App Server and CPU App Server, although it appears under Database Server Recommendation. The values are retained without reinterpretation.

3.3 ALOHA Load Balancer

The Data Center Technical Architecture team recommends deploying a highly available pair of virtual load balancers consisting of two HAProxy ALOHA 12.5.2 virtual appliances.

Two Hyper-V virtual appliances are required, each with:

• Two virtual CPUs
• 1 GB RAM

The virtual appliances should be assigned:

• Static IP addresses from VLAN200
• Static MAC addresses from the System Center Virtual Machine Manager pool

4 Server Configuration and Accessibility

4.1 Prerequisites

Before installing the application, check the prerequisites on the Inexto website.

For each release, read the minimum required features from the Versions tab of the releases table. Installation files can be downloaded from the corresponding columns.

The Inextor Releases and Patches page provides access to:

• Official Inextor releases
• Patches
• Installation files
• Other materials required for installation or operation

Always review the release notes before installing a new version.

Inextor official releases shown in the source

Date	Version	Vault files	Gate files	Liz files	Prerequisite
July 30, 2021	v10.1.0.3163	Vault Server 10.1.0.3163; Vault Administration 10.1.0.3163	Gate 10.1.0.3163; Gate Database 10.1.0.3163	Liz 10.1.0.3163	.NET 4.8
July 2, 2021	v10.1.0.3101	Vault Server 10.1.0.3101; Vault Administration 10.1.0.3101	Gate 10.1.0.3101; Gate Database 10.1.0.3101	Liz 10.1.0.3101	.NET 4.6.2
June 4, 2021	v10.1.0.3035	Vault Server 10.1.0.3035; Vault Administration 10.1.0.3035	Gate 10.1.0.3035; Gate Database 10.1.0.3035	Liz 10.1.0.3035	.NET 4.6.2
May 7, 2021	v10.1.0.2981	Vault Server 10.1.0.2981; Vault Administration 10.1.0.2981	Gate 10.1.0.2981; Gate Database 10.1.0.2981	Liz 10.1.0.2981	.NET 4.6.2
April 15, 2021	v10.1.0.2918	Vault Server 10.1.0.2918; Vault Administration 10.1.0.2918	Not specified	Not specified	.NET 4.6.2
April 9, 2021	v10.1.0.2917	Vault Server 10.1.0.2917; Vault Administration 10.1.0.2917	Gate 10.1.0.2917; Gate Database 10.1.0.2917	Liz 10.1.0.2917	.NET 4.6.2
March 12, 2021	v10.1.0.2835	Vault Server 10.1.0.2835; Vault Administration 10.1.0.2835	Gate 10.1.0.2835; Gate Database 10.1.0.2835	Liz 10.1.0.2835	.NET 4.6

Image placeholder: Inextor Releases and Patches webpage showing release versions, installation packages and .NET prerequisites. The original screenshot was intentionally omitted.

4.1.1 How to Check .NET Version with PowerShell

1. Open the Windows Start menu
2. Search for PowerShell
3. Right-click Windows PowerShell
4. Select Run as administrator

Image placeholder: Windows search results showing Windows PowerShell and the Run as administrator action. The original screenshot was intentionally omitted.

Run the following command:

Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP' -Recurse |
  Get-ItemProperty -Name version -EA 0 |
  Where-Object { $_.PSChildName -Match '^(?!S)\p{L}' } |
  Select-Object PSChildName, version

Example output shown in the source:

PSChildName                         Version
-----------                         -------
v2.0.50727                          2.0.50727.4927
v3.0                                3.0.30729.4926
Windows Communication Foundation    3.0.4506.4926
Windows Presentation Foundation     3.0.6920.4902
v3.5                                3.5.30729.4926
Client                              4.8.04084
Full                                4.8.04084
Client                              4.0.0.0

The command returns information for both the client and full versions of .NET installed on the server.

Image placeholder: Elevated PowerShell console showing the .NET registry-query command and the returned framework versions. The original screenshot was intentionally omitted.

4.1.2 SSL Certificate Installation on Application Server

An SSL certificate should be requested and installed on the application server.

The source references the following example certificate request:

RITM1398836

The certificate-request service is described as fully automated and delivered within 24 hours after approval.

If an IT employee is required to handle the request, use the Additional requirements field.

For a non-standard certificate signed with a different template, raise a separate Operational Change Request for Infrastructure and Cloud Services Infrastructure.

The request form provides these request-type options:

• I already have request file
• I will populate all fields manually

It also includes a required Certificate Template field.

Image placeholder: Certificate Request form for a web server, monitoring client or other application. The original screenshot was intentionally omitted.

4.1.3 How to Import Certificate on Application Server

After completing the request, the owner receives the certificate file and password by email.

Copy the certificate file to the application server and install it using the supplied password.

1. Open the certificate file to start the Certificate Import Wizard
2. Select the appropriate store location
3. Click Next

Image placeholder: Certificate Import Wizard welcome page showing Current User and Local Machine store-location options. The original screenshot was intentionally omitted.

4. Select the certificate file to import

Supported formats shown by the wizard include:

• Personal Information Exchange—PKCS #12: .PFX, .P12
• Cryptographic Message Syntax Standard—PKCS #7 Certificates: .P7B
• Microsoft Serialized Certificate Store: .SST

5. Click Next

Image placeholder: Certificate Import Wizard file-selection page showing an example .pfx file path. The original screenshot was intentionally omitted.

6. Enter the password supplied with the certificate
7. Complete the installation

The source shows these private-key import options:

• Enable strong private-key protection
• Mark this key as exportable
• Protect the private key using virtualization-based security, non-exportable
• Include all extended properties

Image placeholder: Certificate Import Wizard private-key protection page with a password field and import options. The original screenshot was intentionally omitted.

4.1.4 HTTP Configuration Utility

Download the HTTP Configuration Utility from the location referenced by the controlled source document.

Copy the tool to the application server. After importing the certificate, add the SSL configuration using the tool.

1. Open the HTTP Configuration Utility
2. Select the SSL tab
3. Click Add

Image placeholder: HTTP Configuration Utility with the SSL tab selected and the Add button highlighted. The original screenshot was intentionally omitted.

Configure the following values:

Field	Value
IP Address	0.0.0.0
Port	8743
GUID	Click New to generate
Revocation freshness time	0
URL retrieval timeout	0

Select the imported certificate in the certificate section, then save the configuration.

Image placeholder: SSL Configuration dialog showing application, certificate and client-certificate settings. The original screenshot was intentionally omitted.

4.2 Service Account Creation

Request a site-level service account using the service catalog. The account name and password are sent to the requester by email.

The source references this example request:

RITM1693508

The service is described as being delivered within 24 hours after approval.

Review JTI Standard 10.149 to remain aligned with High-Privileged Account Management principles.

Image placeholder: Site-level service-account request form showing the location fields. The original screenshot was intentionally omitted.

4.2.1 Adding Service Account to Administrator Group

The service account must be added to the local Administrators group on the application server.

1. Open Start
2. Enter the following command:

lusrmgr.msc

3. Open Groups
4. Double-click Administrators
5. Click Add
6. Select CORP.JTI.COM from Locations
7. Enter the service-account name
8. Click Check Names
9. Confirm that the account is resolved in the proper format
10. Click OK

Image placeholder: Local Users and Groups console showing the Administrators group and its properties. The original screenshot was intentionally omitted.

Image placeholder: Select Users, Computers, Service Accounts, or Groups dialog showing the corporate domain and an example resolved service account. The original screenshot was intentionally omitted.

5 Installation Steps

5.1 Database Installation

Download the database installation file from the Inexto website.

Create an Operational Change Request for the Data Center Operations Database team to install the database.

The source references this example change:

CHG203586

The Operational Change form is used for changes not included in the Data Center Standard Change Catalogue.

Image placeholder: Operational Change Request form showing infrastructure, configuration-item, geographical-impact and processing fields. The original screenshot was intentionally omitted.

After database installation, add the service account and the required Active Directory groups to the database with the following permissions.

Login name	Access roles and permissions
Global-IT-TT-DevOps-Admins and SWIGVA01-TAT-INEXTO-SYSTEM Admins	db_datareader, db_datawriter, db_ddladmin, db_backupoperator, execute, view server state, view definition
Global-IT-TT-DevOps-Deployment	db_datareader, db_datawriter, db_ddladmin, db_backupoperator, db_securityadmin, execute, view server state
SWIGVA01-TAT-Support	db_datareader, view server state, view definition
SWIGVA01-TAT-Inexto-SYSTEM DataReader	db_datareader, view definition
SWIGVA01-TAT-VAULT-SYSTEM ADMINS, Global-GSC-CP-Support and SWIGVA01-TaT-System Admins	db_datareader
Z_XXX_GATESVC or Z_XXX_MCGSVC	db_owner

Request SQL Server access using the Access to Data Centre Database service.

The source references this example request:

RITM1603033

The request form includes these account choices:

• User Domain Account
• Service Account
• SQL account

It also includes the following permission choices:

• DB Reader
• DB Writer
• DB DDLAdmin
• DB Owner

Image placeholder: Access to Data Centre Database request form showing database, account and permission options. The original screenshot was intentionally omitted.

5.1.1 Gate Database Requirements and Naming Convention

The Gate database DAC package uses the following collation:

SQL_Latin1_General_CP1_CI_AS

This is the only supported collation for the Gate database and must not be changed.

The SQL Server hosting the Gate database should use one of these collations:

SQL_Latin1_General_CP1_CI_AS
Latin1_General_CI_AS

Other collations have not been sufficiently tested and are not supported.

The database name depends on the factory location.

Naming pattern:

Gate<IATA-or-approved-location-code>

The location code normally uses a three-character International Air Transport Association airport code. Custom codes are possible as exceptions but must not duplicate an official code.

Example:

Server name: SWEVAR01-SQL-01
Database name: GateVAR

5.1.2 DAC Package Installation

1. Open SQL Server Management Studio
2. Connect to the required SQL Server instance
3. Create a Data-tier Application on the SQL Server
4. Select the Gate database .dacpac package from the installation media
5. Complete the deployment

5.1.3 Gate Database View Update

The GLA and Gate databases are installed on the same database server.

Configure these views so they read data from the GLA database:

ProductCatalogIntegration
ProductCatalogUnitIntegration

The view definitions can be taken from a known operating factory.

5.1.4 GLA Database Configuration

Add the service account to the GLA database with the following permission:

db_datareader

Use the Access to Data Centre Database request. The source references RITM1603033 as an example.

5.2 Application Installation

Download the installer from the Inexto website.

1. Double-click the setup file
2. On the welcome page, click Next

Image placeholder: Inextor Gate 10.1.0 Setup welcome page. The original screenshot was intentionally omitted.

3. On the Product Features page, retain the default settings
4. Ensure both components are selected:
   • Gate Administration
   • Gate Service
5. Click Next

Image placeholder: Product Features page showing Complete, Gate Administration and Gate Service selected. The original screenshot was intentionally omitted.

6. Retain the default installation directory:

C:\Program Files (x86)\Inextor\

7. Click Next

Image placeholder: Destination Folder page showing the default Inextor installation directory. The original screenshot was intentionally omitted.

8. Configure the system using the source values:

Field	Value
Manufacturing Center Gateway	localhost
Manufacturing Center ID	QA
Gate is a primary node	Yes
Communicate with Liz on TCP	8088
Communicate with Gate on TCP	8089

Image placeholder: System Configuration page showing the Manufacturing Center and TCP-port settings. The original screenshot was intentionally omitted.

9. On the Service Log On Credentials page, select Run service as
10. Click Browse
11. Enter the service-account name
12. Select CORP.JTI.COM as the location
13. Click Check Names
14. Click OK after the account is resolved

Image placeholder: Service Log On Credentials page with the account and password fields. The original screenshot was intentionally omitted.

Image placeholder: Select User dialog showing a resolved corporate service account. The original screenshot was intentionally omitted.

15. Enter the service-account password
16. Click Test Credentials
17. Confirm that successful validation is shown

Image placeholder: Service Log On Credentials page showing successful credential validation. The original screenshot was intentionally omitted.

18. Enter the required database instance and database name
19. Click Next

The source screenshot contains example values, which must not be treated as universal configuration values.

Image placeholder: Database Configuration page showing example database-instance and database-name fields. The original screenshot was intentionally omitted.

20. Select Windows Authentication
21. Click Test Connection
22. Confirm that the connection succeeds
23. Click Next

Image placeholder: Database Run Time Credentials page showing Windows Authentication and a successful connection test. The original screenshot was intentionally omitted.

24. Click Install

Image placeholder: Ready to Install Software page with the Install button highlighted. The original screenshot was intentionally omitted.

25. When installation completes, click Finish

Image placeholder: Setup completion page with the Finish button. The original screenshot was intentionally omitted.

26. Open Windows Services
27. Locate the Inextor Gate service
28. Start the service
29. Confirm that its status is Running and startup type is Automatic

Image placeholder: Windows Services console showing the Inextor Gate service running under its service account. The original screenshot was intentionally omitted.

6 Application Configuration

6.1 Application Settings

Start the Gate application and open Configuration > Application Settings.

Configure the following values:

Category	Key	Value
DefaultVaultCredentialProvider	ForceHttps	True
CodesManager	SideBySideGateEnabled	False
ExternalCodesManager	ReserveOnlyMaterializedChunks	False
SatCodesHandler	ProductionCodePropertyName	SHIFTCODE
VaultProxy	Vaults4WithMessaging	JTIPRD

6.2 Operation Drivers

Enable the Basic HTTP operation driver.

In its configuration, set the Windows Communication Foundation base address using this pattern:

https://<HOST_NAME>.corp.jti.com:8743

Select the following option:

Update layouts on update products

The source also shows these example settings:

Setting	Value
Mini Log Size	1000
Mini Log Duration	0d0H5M0s0ms
Default Requested Quantity	10000
Work Order Quantity Property	WOQuantity
Message validity time	0d2H0M0s0ms

Image placeholder: Basic HTTP operation-driver configuration showing the secure WCF base address, XML configuration and data settings. The original screenshot was intentionally omitted.

External service drivers cannot be enabled unless the service account has been added to the local Administrators group on the application server.

Set the Product Integration Driver Periodicity to at least:

0d0H10M0s0ms

The source shows these Product Integration Driver settings:

Setting	Value
Mini Log Size	1000
Mini Log Duration	0d0H5M0s0ms
Periodicity	0d0H10M0s0ms
Page Size	500
Send mail after synchronization	Enabled
Severity and higher	Info
Subject prefix	[CodentifyProductSynchronization]

Image placeholder: Product Integration Driver configuration showing behavior, logging, periodicity, page size and email settings. The original screenshot was intentionally omitted.

6.3 Layouts Configuration

The content under Layouts contains SHIFTCODE criteria.

1. Open Layouts > Contents
2. Select SHIFTCODE
3. Click Edit Content
4. Click Edit Arguments
5. Review the declarations

The declarations should be taken from a known operating factory.

The source shows SHIFTCODE with these characteristics:

Field	Value
Code	SHIFTCODE
Description	SHIFTCODE
Content type	Dynamic
Minimum length	1
Maximum length	30
Code issuer	Scripted
Code mask	Not set

Image placeholder: Gate Layouts and Contents page showing SHIFTCODE selected and its scripted content configuration. The original screenshot was intentionally omitted.

7 Vault Connection

The Vault connection should be established by Inexto.

Submit a ticket through the Inexto Support website.

8 New Market Setup

8.1 Prerequisites

Identify and contact the relevant authorities to register and obtain access to order codes.

Manufacturers must obtain the following credentials and identifiers:

• OMS Authorization Token: Used by some Order Management Systems to communicate with CRPT using dynamic tokens
• OMS URL: IP address or URL of the Order Management System used to order codes and send production reports to the identifier issuers
• OMS ID: Unique Order Management System identifier required to connect to the OMS server
• Participant ID (INN): Manufacturer identifier assigned in Russia by the Russian Tax Authority
• Factory ID (GateID): Request and obtain this identifier from Inexto

Factory registration is the process of creating and assigning a unique identity to a factory.

8.2 Configuration

Enable the CRPT codes driver under:

Gate > Configuration > Op. Drivers

The source identifies the driver using the following pattern:

CRPT codes driver (10.1.0.xxxx)

Image placeholder: Gate Operation Drivers page showing the CRPT codes driver enabled among the available drivers. The original screenshot was intentionally omitted.

Click Configure to continue.

Add a connection to the relevant identifier issuer:

• Click Add V2 or Add V1, depending on the backend
• Click Edit to modify an existing connection

Image placeholder: Gate operation-driver configuration page showing enabled driver components and the Configure action. The original screenshot was intentionally omitted.

The CRPT Codes Configuration dialog contains these tabs:

• General
• OMS
• INEXPRESSV1
• INEXPRESS V2

It provides these actions:

• Add V2
• Add V1
• Edit
• Delete

Image placeholder: CRPT Codes Configuration dialog listing configured OMS schemes and reported units. The original screenshot was intentionally omitted.

The following settings are mandatory:

• GLN
• Factory Name
• Country
• Production Type
• Participant ID
• Authentication section
• OMS Servers section

OMS scheme configuration

The production orders using an OMS scheme must contain an attribute named:

OMS_SCHEME

Its value must match the configured scheme name. The attribute is normally placed on the manufacturing market.

Configure the following factory information:

Field	Description
GLN	Global Location Number of the factory using Gate
Factory Name	Manufacturer display name
Country	Manufacturer country
Participant ID	Manufacturer identifier
Address	Manufacturer address
Production Type	Product type used to select the OMS API

Image placeholder: Edit OMS Scheme dialog showing factory information, production type and authentication settings. Any visible token was intentionally omitted. The original screenshot was intentionally omitted.

Authentication and order settings

The configuration can include:

• Access Token
• OMS ID
• Close Orders
• Release Method
• Machine Prefix
• Aggregation Reports
• Aggregated Items Count
• Approve on Error
• OMS Servers

Security note: Authentication tokens, credentials and secret identifiers visible in source screenshots are intentionally not reproduced in this Markdown file.

The source explains the following controls:

• Close Orders: Controls whether Gate asks the OMS to close each order after downloading all codes
• Aggregation Reports: Controls whether Gate waits for related usage reports to be approved before sending aggregation reports
• Aggregated Items Count: Controls whether reports contain the actual aggregated-item count or fixed bundle and case values
• Approve on Error: Defines how long Gate waits before marking reports approved when the OMS returns an error

Image placeholder: Edit OMS Scheme dialog showing authentication, order and report controls. Sensitive values were intentionally omitted. The original screenshot was intentionally omitted.

OMS servers

Configure one or more OMS server addresses.

The CRPT codes driver checks all addresses for availability before each request but uses the available address with the lowest priority value.

Set priority to 0 to disable an address.

Field	Description
Address	IP address and port of the OMS server
Priority	Priority among configured OMS addresses; 0 means inactive

Image placeholder: Edit OMS Scheme dialog showing OMS server priority, address and status. Internal addresses were intentionally omitted. The original screenshot was intentionally omitted.

Reported units

Configure reported units such as:

• Packs
• Bundles

The values should be obtained from the market team.

The source shows a reported-unit configuration containing these fields:

Field	Example or description
Name	Must match the SerializationLevelReference value used by products for this OMS
Unit	Unit type, such as Packs or Bundles
Generation Mode	Code-generation mode
Identification	Identification method
Marking	Marking type
Ordering Quantity	Quantity of codes ordered
Code State	State that triggers usage reporting; None disables usage reports
GTIN	Global Trade Item Number expression
Has MRP	Whether Maximum Retail Price is sent in code orders
MRP	Maximum Retail Price content and validation expression

The source states that Has MRP should be selected for Russian OMS configurations and cleared for Kazakhstan and Kyrgyzstan.

Image placeholder: Reported Units tab showing Packs and Bundles configuration, generation mode, quantity, GTIN and MRP fields. The original screenshot was intentionally omitted.

8.3 Description of the Configurable Settings

OMS Scheme

Name

The unique identifier of the OMS scheme.

The CRPT codes driver recognizes production orders for CRPT-operated markets by the presence of an attribute named OMS_SCHEME.

The attribute value must equal one of the configured OMS scheme names.

The OMS_SCHEME attribute is normally added to the Manufacturing Market, but it can also be added to the Manufactured Product or Production Order.

Factory Information

Setting	Description
GLN	Global Location Number of the factory using Gate
Factory Name	Manufacturer display name
Country	Manufacturer country
Participant ID	Manufacturer identifier
Address	Manufacturer address

Production

Production Type defines the type of product to produce.

Available values shown in the source include:

• Tobacco: Product type is tobacco
• NCP: Nicotine-containing products
• Water: Packaged water products, such as water bottles
• Beer: Product type is beer
• OTP: Other tobacco products

The value affects which OMS application programming interface is used.

For example:

• Tobacco production uses the tobacco OMS API for code orders and usage and aggregation reports
• NCP production uses the NCP OMS API

Authentication

OMS ID

Identifier of the OMS, obtained from the OMS administration console.

Use Dynamic Tokens

Select when the OMS uses dynamic tokens. Otherwise, leave it cleared.

The source states that the Russian cloud OMS has required dynamic tokens since October 1, 2021. Static tokens remained standard for on-premises OMS servers and countries other than Russia at the time of publication.

Static Token

Visible only when Use Dynamic Tokens is cleared. It contains the token string used to establish a connection with the OMS server.

Dynamic Token Provider URL

Visible only when Use Dynamic Tokens is selected. It contains the address of the dynamic-token-provider web service.

Dynamic Token Provider

Specifies the provider type:

• OMS Authenticator—developed by Inexto and uses the manufacturer’s private signing certificate to obtain and cache tokens
• Sputnik—third-party software

OMS Connection

Visible when Use Dynamic Tokens is selected. It contains the unique ID of the OMS device.

Register a different device for each application communicating with the OMS, such as Gate and Inexpress.

Sputnik API Key

Visible only when the Dynamic Token Provider is Sputnik.

Orders

Close Orders

Controls whether the CRPT codes driver asks the OMS to close a code order after downloading the codes.

The source states:

• For Russian production, leave the option cleared because the Russian OMS closes orders automatically
• For Kazakhstan code orders, select the option

Sign Orders

Controls whether the CRPT codes driver sends the X-Signature HTTP header with each code order.

For some production types, such as other tobacco products, water and beer, orders without this header must be signed manually on the OMS website.

This feature works with OMS Authenticator or another application capable of generating detached signatures.

Release Method

Specifies when the manufacturer should release payment for ordered codes.

Possible values shown in the source include:

• PRODUCTION—manufactured in the Russian Federation
• IMPORT—imported into the Russian Federation
• REMAINS—residue marking
• CROSSBORDER—cross-border scenarios for eligible Eurasian Economic Union commodity groups
• REMARK—relabeling for eligible commodity groups
• COMMISSION—accepted for commission from a natural person for eligible commodity groups

The source states that this value is required for NCP production and may be left empty for tobacco production.

Expiration Scheme

Specifies how ordered code chunks expire.

Available behaviors:

• Chunks expire after a fixed number of days
• Chunks expire at the end of the current month or when the configured expiration period ends, whichever comes first

Expiration Time Zone

When the Expiration Scheme is End Of Month, this setting specifies the time zone used to calculate the end of the month.

No Ordering Window

Specifies a period before month-end during which no code orders are placed, preventing Gate from ordering codes that would expire immediately.

Reports

Machine Prefix

A text prefix added to the Machine ID when sending reports to the OMS.

Aggregation Reports

Controls whether the driver waits for related usage reports to be approved before sending aggregation reports.

The source recommends selecting this option.

Aggregated Items Count

Controls the aggregatedItemsCount field in OMS aggregation reports.

• When selected, the field contains the actual number of aggregated items received in the Inexpress file or message
• When cleared, the field always contains 10 for bundles and 50 for cases

Approve on Error

Specifies how long the driver waits for OMS report approval. After the period passes, the driver automatically approves reports if the OMS returns an error.

The driver continues checking the status when the OMS does not return an error.

OMS Servers

The OMS Servers list contains the addresses used for code orders and usage or aggregation reports.

Before each request, the driver checks all configured addresses for availability and uses the available address with the lowest priority.

Set priority to 0 to disable an address.

Gate Application Settings

The source includes a Gate Application Settings view filtered for OMS. Non-default values are identified visually in the original screenshot.

Image placeholder: Gate Application Settings page filtered for OMS configuration. The original screenshot was intentionally omitted.

8.4 Configure Manufacturing Market

Before production, create the Manufacturing Market under:

Gate > Products > Manufacturing Markets

The Attributes field in the Manufacturing Market window accepts key-value settings unique to the product’s market.

Add the following attribute:

Name	Value
OMS_SCHEME	Name of the connection to the relevant identifier issuer configured in CRPT Codes Configuration

Example:

Name: OMS_SCHEME
Value: DefaultV2.0
Type: String
Source: MC

Image placeholder: Manufacturing Markets page and Manufacturing Market Edit dialog showing an OMS_SCHEME attribute. The original screenshot was intentionally omitted.

9 Document Control

9.1 Contact Person

As of July 2025, questions and feedback regarding this standard should be submitted to Andrei Grideanu.

9.2 Revision History

Version	Effective date	Purpose of change	Author
2	June 1, 2022	New market setup section has been added	Mattias Linden
1	October 1, 2021	First version of the document	Pavel Evdokimov