Registration
Overview
This section describes the registration procedures required to connect and authorize the main Inextor components.
It covers:
- Registering a Gate on a Vault
- Creating a LinkUp setup
- Registering a Liz on a Vault
- Registering an MSK
The procedures are intersectional, meaning that some actions must be performed on the Gate, some on the Vault, and some on the Liz by the corresponding authorized users.
1 Register Gate
This procedure explains how to register a Gate on a Vault.
The registration requires actions on both sides:
- Gate side: create a connection request, import the license, configure the Vault connection, and test it
- Vault side: create or verify the owning entity and factory, import the certificate request, and generate the Gate license
| Step | Gate | Vault |
|---|---|---|
| 1 | Request a new connection. This generates a certificate request file named similar to cerReq_*.txt | |
| 2 | If the MAN / IMP entity owning the Gate is not yet created on the Vault, create an entity on the Vault website | |
| 3 | If the factory corresponding to the Gate is not yet created and assigned to the MAN / IMP entity, create the factory and assign it to the MAN / IMP entity | |
| 4 | Select the factory and click Manage Connections to import the certificate request, fill in the required information, and generate the license file (*.licx) | |
| 5 | Import the Gate license file | |
| 6 | Select the Vault connection and click Edit Connection to enter the Vault IP address and the correct connection credential type | |
| 7 | Click Test Connection to test the Vault connection |
After generating the license file on the Vault side, do not forget to click Save on the Manage Connections page.
Gate registration prerequisites
Before registering a Gate, ensure that:
- The MAN / IMP entity exists on the Vault
- The factory exists on the Vault
- The factory is assigned to the correct MAN / IMP entity
- The Gate can reach the Vault network address
- The certificate request file has been generated from the Gate Administration UI
- The user performing the Vault actions has the required rights to manage factories and connections
Gate registration outputs
At the end of this process:
- The Vault has a registered factory connection
- The Gate has imported the Vault license file
- The Gate has configured the Vault connection details
- The Gate connection test should be successful
2 Create LinkUp Setup
Once the installation of the Gate service and administration UI is completed, a LinkUp setup must be defined to configure the elements of a production line.
A LinkUp setup represents the production line topology and machine configuration used later by Liz.
2.1 Create a LinkUp setup from Gate Administration UI
To create a LinkUp setup:
- Start the Gate service
- Open the Gate Administration UI
- Go to Serializers → LinkUp Setups
- Click New
- Click Import
- Select the
.lusfile provided for the installation - Validate that the import is successful
- Click OK
The LinkUp setup should then appear in the list.
2.2 LinkUp setup example fields
A LinkUp setup can contain fields such as:
| Field | Description |
|---|---|
| Name | LinkUp setup name |
| Description | Description of the line or configuration |
| Manufacturing Center ID | Manufacturing center identifier |
| Machine ID | Machine identifier |
| LinkUp Type | Type of LinkUp topology |
| Liz ID | Identifier of the Liz assigned to the setup |
| Deleted | Indicates whether the setup is deleted |
2.3 Importing a .lus file
The .lus file contains the LinkUp setup configuration.
When imported successfully, the Gate Administration UI shows a successful validation result and the setup is added to the LinkUp setup list.
2.4 Default LinkUp setup configuration
If the user does not import a .lus file and clicks OK, a prompt appears asking whether to create the LinkUp setup with a default topology.
If accepted, the LinkUp is created with default topology.
A default LinkUp topology can be edited later from the Liz UI after the LinkUp is assigned to a Liz.
2.5 Editing LinkUp setups
Edition of LinkUp setups can be done either:
- Manually in the
.lusfile - Through the UI of the Liz to which the LinkUp setup was assigned
Modifications done on the Liz side update the LinkUp setup on the Gate.
2.6 LinkUp attributes
Some attributes may be inherited from other entities, such as the machine.
Other attributes are specific to the LinkUp setup and can define behavior such as printer handling or topology-related settings.
3 Liz Registration on the Vault
This procedure explains how to register a Liz on a Vault.
There are two scenarios:
- Registering a Liz on a Vault for the first time
- Registering a Liz on additional Vaults
3.1 Registering a Liz on a Vault for the first time
The first-time registration involves issuing a Liz license from the Vault side and using it during the Liz first-run configuration.
| Step | Liz | Vault |
|---|---|---|
| 1 | If the Vault Plugin Liz License Manager is active, use it to generate the Liz license file (.licx). Otherwise, use the Certificate Tool to generate the Liz license | |
| 2 | Transmit the .licx file to the Liz machine, for example by email or another approved transfer method | |
| 3 | Use the .licx file in the Liz first-run configuration procedure. In the Register Vault and Manage MSKs step, select the Vault that issued the license to register with it | |
| 4 | If automatic approval of pending requests is not activated, approve the Liz request from the Pending Requests section of the Dashboard on the Vault website |
First-time Liz registration result
At the end of this process:
- The Liz license has been generated on the Vault side
- The license has been transferred to the Liz machine
- The Liz has used the license during first-run configuration
- The Liz has requested registration on the issuing Vault
- The Vault has approved the Liz request, if manual approval is required
3.2 Registering a Liz on additional Vaults
A Liz can also be registered on additional Vaults.
The Gate should already be registered with the additional Vault before the Liz registration is performed.
| Step | Liz | Vault |
|---|---|---|
| 1 | In the Register Vault panel of Liz Configuration, choose the desired Vault and register with it | |
| 2 | If automatic approval of pending requests is not activated, approve the Liz request from the Pending Requests section of the Dashboard on the Vault website |
Additional Vault registration result
At the end of this process:
- The Liz has selected the desired Vault from the available Vaults
- The Liz has submitted a registration request
- The Vault has approved the request, if manual approval is required
4 Register MSK
This procedure explains how a Liz obtains an MSK from a registered Vault.
A Liz can only request an MSK from a Vault where the Liz is already registered.
| Step | Liz | Vault |
|---|---|---|
| 1 | Use the Manage MSK step of the Register Vault and Manage MSKs panel to request an MSK from the Vault and manage existing MSKs | |
| 2 | If automatic approval of pending requests is not activated, approve the MSK request from the Pending Requests section of the Dashboard on the Vault website |
4.1 MSK management notes
- The MSK request is initiated from the Liz Configuration UI
- The approval, when required, is performed from the Vault website
- The MSK is downloaded to the Liz through the Gate
- The MSK may take time to download because it is a large file
- The user can refresh the MSK status in Liz Configuration
4.2 MSK registration lifecycle
A typical MSK lifecycle is:
- Liz requests an MSK from a registered Vault
- The Vault receives the pending MSK request
- If manual approval is required, an authorized Vault user approves the request
- The MSK is downloaded to the production line through the Gate
- The MSK status changes from Pending to Not Registered
- The MSK is registered from the Liz Configuration UI
- If required, the Vault approves the MSK registration
4.3 MSK limitations
Only one MSK can be registered per Vault at any given time.
If an MSK is already registered for a Vault, it must first be unregistered before a new MSK can be registered.
5 Registration responsibilities summary
| Registration activity | Gate | Vault | Liz |
|---|---|---|---|
| Register Gate | Creates connection request, imports license, configures connection, tests connection | Creates or verifies entity/factory, imports certificate request, generates license | Not applicable |
| Create LinkUp setup | Creates or imports LinkUp setup | Not applicable | Can later edit assigned LinkUp topology |
| Register Liz first time | Must already be connected to Vault | Generates Liz license and approves request if required | Uses license and registers with Vault |
| Register Liz on additional Vault | Must already be registered with the Vault | Approves request if required | Selects Vault and registers |
| Register MSK | Transfers MSK through Gate | Approves MSK request if required | Requests, downloads, and registers MSK |
6 Recommended checks after registration
After completing registration, verify the following:
- Gate connection test to Vault is successful
- Factory is correctly linked to the MAN / IMP entity on Vault
- Gate license is imported successfully
- LinkUp setup appears in Gate Administration UI
- Liz is attached to the correct Gate
- Liz is assigned to the correct LinkUp setup
- Liz is registered with the required Vaults
- MSK is requested, downloaded, and registered
- Pending requests are approved on Vault if automatic approval is not enabled
7 Troubleshooting notes
Gate cannot connect to Vault
Check:
- Vault IP address or hostname
- Connection credential type
- Imported license file
- Network connectivity
- Firewall or proxy restrictions
- Whether the Vault-side connection was saved after license generation
Liz registration remains pending
Check:
- Whether automatic approval is enabled
- Whether a pending Liz request exists on the Vault Dashboard
- Whether an authorized Vault user has approved the request
- Whether the Gate is correctly registered with the same Vault
MSK remains pending or not registered
Check:
- Whether the Liz is already registered with the Vault
- Whether the MSK request was approved on the Vault, if required
- Whether the Gate can transfer the MSK to the Liz
- Whether another MSK is already registered for the same Vault
LinkUp setup does not match the physical line
Check:
- Whether the correct
.lusfile was imported - Whether the LinkUp setup was edited manually
- Whether modifications were made from the Liz UI
- Whether the LinkUp setup reflects the real production line topology