LogoCentral User Management
  • en-US
    • Contact
    • Legal Notice
    • General Terms & Conditions
    • Data Privacy Statement
    • Cookie Policy
    • 004-02062025
    • General
      • General
      • License Agreement
      • Software version
      • Safety Requirements
    • System requirements
      • System requirements – server
      • System requirements – operating system Docker
      • System requirements – Windows server operating system
      • System requirements – firewall and network
      • Recommended web browsers
    • Installing and activating CENTRUM Docker
      • Installing and starting the Docker engine
      • Starting the server
    • Installing and activating CENTRUM Windows
      • Installing and activating CENTRUM Windows
      • Web server settings
    • Initial Steps
      • Logging in for the first time
      • Changing the admin password
      • Adding an administrator
    • Connecting welding systems to the CENTRUM server
      • Before connecting to the CENTRUM server
      • Connecting welding systems to the CENTRUM server via SmartManager
      • Connecting welding systems to the Centrum server via the control panel
    • Connecting WeldCube Premium to the CENTRUM server
      • Connecting WeldCube Premium to the CENTRUM server
    • Creating a Docker backup
      • Overview of backup options
      • Creating a backup while the server is stopped
      • Creating a backup while the server is running
      • Loading the backup
      • Creating a Windows backup
      • Loading a Windows backup
    • Installing the Update
      • Performing a Docker update
      • Performing a Windows update
    • Using Specific Versions
      • Using specific versions

    Central User Management Installation instructions

    System requirements – server
    System requirements – firewall and network
    Spare parts

    General

    General

    CENTRUM = Fronius Central User Management

    CENTRUM is a server-based application that centrally manages the user settings of several connected welding systems in a database.
    The hardware or VM configuration required for this depends on the number of devices to be managed.
    The user is responsible for the operation of the hardware or VM, and for the configuration, licensing, and maintenance of the recommended operating system.

    It is not intended for CENTRUM to be installed and operated on a single desktop computer or system PC, for example in a production hall.

    To ensure smooth operation, the setup of the server (hardware or VM), the design of the network infrastructure, and administration should only be performed by the user's IT department.

    1. General

    General

    CENTRUM = Fronius Central User Management

    CENTRUM is a server-based application that centrally manages the user settings of several connected welding systems in a database.
    The hardware or VM configuration required for this depends on the number of devices to be managed.
    The user is responsible for the operation of the hardware or VM, and for the configuration, licensing, and maintenance of the recommended operating system.

    It is not intended for CENTRUM to be installed and operated on a single desktop computer or system PC, for example in a production hall.

    To ensure smooth operation, the setup of the server (hardware or VM), the design of the network infrastructure, and administration should only be performed by the user's IT department.

    1. General

    License Agreement

    The license agreement must always be observed.

    The license agreement can be found at:

    • https://www.fronius.com/en/welding-technology/terms-conditions/centrum
    1. General

    Software version

    These installation instructions relate to CENTRUM, version 1.5.

    1. General

    Safety Requirements

    The confidentiality and integrity of the data must be ensured at all times. To do this, proceed as follows:
    1Protect the host system and the data backups against unauthorized access
    2Use HTTPS

    System requirements

    System requirements – server

    Physical hardware:

    Processor (CPU)

    Quad Core 1.2 GHz

    Memory (RAM)

    At least 4 GB (depending on the operating system and the connected welding systems)

    Graphics

    Integrated graphics unit

    Network

    Gigabit Ethernet

    Storage

    At least 50 GB SSD

    Virtual Machine (VM)

    Processor (CPU)

    4 cores

    Memory (RAM)

    At least 4 GB (depending on the operating system and the connected welding systems)

    Graphics

    Standard graphics card

    Network

    Gigabit Ethernet

    Storage

    At least 100 GB SCSI (see table below)

    Storage:
    The required memory size depends on the number of connected welding systems and the number of users. The table shows the respective recommended memory size for standard installations.

    Welding systems used / users

    Memory size

    5 / 10

    50 GB

    50 / 50

    55 GB

    100 / 100

    60 GB

    300 / 300

    80 GB

    500 / 500

    100 GB

    1. System requirements

    System requirements – server

    Physical hardware:

    Processor (CPU)

    Quad Core 1.2 GHz

    Memory (RAM)

    At least 4 GB (depending on the operating system and the connected welding systems)

    Graphics

    Integrated graphics unit

    Network

    Gigabit Ethernet

    Storage

    At least 50 GB SSD

    Virtual Machine (VM)

    Processor (CPU)

    4 cores

    Memory (RAM)

    At least 4 GB (depending on the operating system and the connected welding systems)

    Graphics

    Standard graphics card

    Network

    Gigabit Ethernet

    Storage

    At least 100 GB SCSI (see table below)

    Storage:
    The required memory size depends on the number of connected welding systems and the number of users. The table shows the respective recommended memory size for standard installations.

    Welding systems used / users

    Memory size

    5 / 10

    50 GB

    50 / 50

    55 GB

    100 / 100

    60 GB

    300 / 300

    80 GB

    500 / 500

    100 GB

    1. System requirements

    System requirements – operating system Docker

    Supported operating systems:
    Central User Management is distributed as a Docker image. The Docker image can be used with one of the following operating systems.

    Linux servers
    Distributions like: Debian, Ubuntu, Alpine Linux, Container Linux, RancherOS, Atomic Host, Boot2Docker, Ubuntu Core

    In addition to the distributions listed above, other Linux distributions can be used if they meet the Docker requirements.

    Microsoft Windows Server 2019
    With Docker environment enabled to run the Docker container.

    For more information, see:
    https://docs.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=Windows-Server

    Microsoft Windows Server 2022
    With Docker environment enabled to run the Docker container.

    For more information, see:
    https://docs.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=Windows-Server

    1. System requirements

    System requirements – Windows server operating system

    From version 1.5, Central User Management is also distributed as ".msi" and can be installed on the following Windows operating systems without Docker:
    • Microsoft Windows Server 2022
    1. System requirements

    System requirements – firewall and network

    The following Ports and services are used by the respective welding systems for:
    • the connection to Central User Management
    • the configuration and management of the welding systems

    Ensure proper firewall and network configuration for incoming and outgoing data traffic.

    Connection from the welding systems to CENTRUM:

    Target server

    TCP

    Central User Management

    4711

    Connection from the user PC to CENTRUM:

    Service

    TCP

    HTTP

    80

    HTTPS (recommended)

    443

    1. System requirements

    Recommended web browsers

    Web browser

    Version

    Google Chrome

    80.0.3987.149

    Mozilla Firefox

    74.0

    Microsoft Edge

    101.0.1210.53

    IMPORTANT! For functional and security reasons, use the latest versions of the recommended browsers.

    Installing and activating CENTRUM Docker

    Installing and starting the Docker engine

    1Download and install the Docker engine

    Link to the Docker engine Installation Instructions:
    https://docs.docker.com/engine/install/

    The following instructions are recommended for installing the Docker engine on a Windows server:
    https://docs.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=Windows-Server
    1. Installing and activating CENTRUM Docker

    Installing and starting the Docker engine

    1Download and install the Docker engine

    Link to the Docker engine Installation Instructions:
    https://docs.docker.com/engine/install/

    The following instructions are recommended for installing the Docker engine on a Windows server:
    https://docs.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=Windows-Server
    1. Installing and activating CENTRUM Docker

    Starting the server

    To start the Central User Management server, you must first create a container for Central User Management.

    The container uses a defined Docker volume. The Docker volume is required in order to save the database independently of the container and thus enable server updates to be carried out without any loss of data.

    The container uses an HTTPS connection in order to ensure the highest possible level of security during communication between the server and user.

    In order to use HTTPS, copy the PFX or P12 certificate into the container as described below:

    Run all of the following commands in the shell of the operating system.

    1Run the following command to log in to the registry of Central User Management:
    docker login registry.pw.fronius.com --username 9432fea2-51d0-4450-a255-702bbe79d2be --password 6f7bda41-b0a2-48f3-b6a2-bbbb8ce754f4
    2Run the following command in order to create the container:
    docker create --name centrum -p <https-port>:443 -p 4711:4711 -v
    centrum-data:/<Container-Data-Folder-Path> -e ASPNETCORE
    _URLS="https://+;http://+" -e ASPNETCORE_HTTPS_PORT=
    <https-port> -e ASPNETCORE_Kestrel__Certificates__Default__
    Password=<Certificate-Password> -e ASPNETCORE_Kestrel__
    Certificates__Default__Path=<Certificate-Path-In-Container> --
    restart=always registry.pw.fronius.com/centrum

     

    Explanation of the command:

    <https-port>
    The port via which the website of Central User Management can be accessed—always select port 443, as this port is stored on the welding systems and cannot be changed from there

    -p 4711:4711
    Port mapping that is required for connecting to the welding systems

    -v centrum-data:<Container-Data-Folder-Path>
    The Docker volume where the data are stored.

    <Container-Data-Folder-Path> is the path for the storage data folder of the Central User Management server.

    Linux container: /data
    Windows container: C:\data

    In this example, the Docker volume is named "centrum-data".

    If a Windows container is used, in addition to the volume specification, the user must be specified as the ContainerAdministrator in the "create" command:
    --user ContainerAdministrator

    <Certificate-Password>
    The password for the PFX or P12 certificate

    <Certificate-Path-In-Container>
    The path for the certificate in the container.

    Windows does not store certificates in a folder, which is why the path can be freely selected in Windows. For example:
    C:\publish\Certificate.pfx

    For Linux the following path is recommended:
    /etc/ssl/private/Certificate.pfx

     

    3Run the following command to copy the certificate to the container:
    docker cp <Certificate-Path-On-Host> centrum:<Certificate-Path-In-Container>

    Example of the path on a Windows system:
    docker cp C:/Certificate.pfx centrum:/C:\publish\Certificate.pfx

    Example of the path on a Linux system:
    docker cp /Certificate.pfx centrum:/etc/ssl/private/Certificate.pfx

    4Run the following command in order to start the server:
    docker start centrum

    The browser can now be used to access Central User Management.

    Installing and activating CENTRUM Windows

    Installing and activating CENTRUM Windows

    An administrator user is required for the installation.

    1To start the installation, run "Central-User-Management-x.x.xxx.msi" and follow the process
    2Define the save location for the application files
    3Define the save location for the database

    Once the installation is complete, Central User Management can be accessed via the browser.

    1. Installing and activating CENTRUM Windows

    Installing and activating CENTRUM Windows

    An administrator user is required for the installation.

    1To start the installation, run "Central-User-Management-x.x.xxx.msi" and follow the process
    2Define the save location for the application files
    3Define the save location for the database

    Once the installation is complete, Central User Management can be accessed via the browser.

    1. Installing and activating CENTRUM Windows

    Web server settings

    By default, Central User Management is configured via http on port 80 and via https on port 443. To reconfigure or expand the web server, a config.json file is available in the directory "C:\ProgramData\Fronius\Central User Management\".

     

    • Urls: This setting can be used to configure which protocols (http, https) are to be supported. A port can be specified for each protocol.
      • Default value: https://0.0.0.0:443; http://0.0.0.0:80
    • Certificates: The https certificate is managed in this section. A self-signed certificate is stored and configured during installation. To use your own certificate, you can either store and load the certificate in the file system or load it from the Windows certificate store. Only one section can have "Default" in the file. To use the Windows certificate store, rename the following sections:
      • "Default" section with the path variable as "_Default"
      • "_Default" section as "Default"
      The variables for the storage location in the certificate store can then be filled out.
    • Location: Specifies the certificate store. Possible values:
      • CurrentUser
      • LocalMachine
    • Store: Describes the name of the certificate store. Possible values:

    AddressBook

    1

    The X.509 certificate store for other users

    AuthRoot

    2

    The X.509 certificate store for third-party certificate authorities (CAs)

    CertificateAuthority

    3

    The X.509 certificate store for intermediate certificate authorities (CAs)

    Disallowed

    4

    The X.509 certificate store for revoked certificates

    My

    5

    The X.509 certificate store for personal certificates

    Root

    6

    The X.509 certificate store for trusted root certificate authorities (CAs)

    TrustedPeople

    7

    The X.509 certificate store for directly trusted people and resources

    TrustedPublisher

    8

    The X.509 certificate store for directly trusted publishers

    After the configuration has been completed, the "Central User Management" Windows service must be restarted.

    Note: If the certificate is stored in the Windows store, the private key may need to be released for the "LOCAL_SERVICE" user.

    Initial Steps

    Logging in for the first time

    1Enter the IP address and the port of the Central User Management-Server into the browser:
    • Central User Management opens.
    2Log in using the default login details:
    • User: admin
    • Password: Admin123!!
    1. Initial Steps

    Logging in for the first time

    1Enter the IP address and the port of the Central User Management-Server into the browser:
    • Central User Management opens.
    2Log in using the default login details:
    • User: admin
    • Password: Admin123!!
    1. Initial Steps

    Changing the admin password

    For security reasons, a new password needs to be assigned for the "admin" user when logging in for the first time.

    1. Initial Steps

    Adding an administrator

    1Select the "Users" tab in Central User Management
    2Select the admin user (automatically created during installation)
    3Edit the admin user
    4In the "NFC Card" field, enter the number of the appropriate NFC key (NFC card, NFC key fob, etc.) and save this information

    IMPORTANT! Protect this NFC key against unauthorized access as this NFC key can be used to access all of the welding systems.
    5Save the settings

    Connecting welding systems to the CENTRUM server

    Before connecting to the CENTRUM server

    NOTE!

    Before connecting welding systems or WeldCube Premium to the CENTRUM server, first configure all users, user roles, client groups, and references to these client groups in CENTRUM!

    Otherwise, the systems are locked via the "admin user" until configuration in CENTRUM is completed.

    Correct sequence:

    Install CENTRUM

    Configure, set up users

    Connect system to CENTRUM

    1. Connecting welding systems to the CENTRUM server

    Before connecting to the CENTRUM server

    NOTE!

    Before connecting welding systems or WeldCube Premium to the CENTRUM server, first configure all users, user roles, client groups, and references to these client groups in CENTRUM!

    Otherwise, the systems are locked via the "admin user" until configuration in CENTRUM is completed.

    Correct sequence:

    Install CENTRUM

    Configure, set up users

    Connect system to CENTRUM

    1. Connecting welding systems to the CENTRUM server

    Connecting welding systems to the CENTRUM server via SmartManager

    Prerequisite:
    The welding system must be connected to a computer via network cable or integrated in a network.



    1Enter the IP address of the desired welding system into the browser, open SmartManager and log in
    2Select the User management tab
    3Select the CENTRUM server tab


    4In the input field highlighted, enter the domain name or the IP address of the server on which Central User Management has been installed (if using a domain name, a valid DNS server must be configured in the network settings of the welding system)


    5Check the box highlighted


    6Click on the highlighted button
    The availability of the specified server is checked.
    If the specified server is available, "Server verified" appears.
    7Save changes
    The welding system is displayed in Central User Management.
    8Integrate all subsequent welding systems into Central User Management in the same way
    1. Connecting welding systems to the CENTRUM server

    Connecting welding systems to the Centrum server via the control panel

    A welding system can also be connected to the CENTRUM server via the control panel.



    1 Select "Defaults"
    2Select "Administration"
    3Select CENTRUM Server
    4Enable CENTRUM Server
    5Enter the CENTRUM Server
    6Verify CENTRUM
    7Save

    Connecting WeldCube Premium to the CENTRUM server

    Connecting WeldCube Premium to the CENTRUM server



    1Open WeldCube Premium in the browser
    2Select the "Administration" tab


    3Expand the "User" menu and select CENTRUM


    4Enable Central User Management


    5Enter the URL of Central User Management


    6Open Central User Management in a separate browser window
    7Select the "Configuration" tab
    8Select "API"
    9Copy the API key from Central User Management


    10Reopen WeldCube Premium in the current browser window
    11Enter the API key from Central User Management
    12Save the entries
    WeldCube Premium is displayed in Central User Management.
    13Add all subsequent WeldCube Premium accounts to Central User Management in the same way
    1. Connecting WeldCube Premium to the CENTRUM server

    Connecting WeldCube Premium to the CENTRUM server



    1Open WeldCube Premium in the browser
    2Select the "Administration" tab


    3Expand the "User" menu and select CENTRUM


    4Enable Central User Management


    5Enter the URL of Central User Management


    6Open Central User Management in a separate browser window
    7Select the "Configuration" tab
    8Select "API"
    9Copy the API key from Central User Management


    10Reopen WeldCube Premium in the current browser window
    11Enter the API key from Central User Management
    12Save the entries
    WeldCube Premium is displayed in Central User Management.
    13Add all subsequent WeldCube Premium accounts to Central User Management in the same way

    Creating a Docker backup

    Overview of backup options

    There are two available options for creating a server backup
    • Option 1 = Stop the server and copy the data (available for Windows and Linux)
    • Option 2 = Copy data during operation (available for Linux)

    The precise procedure is described below.

    1. Creating a Docker backup

    Overview of backup options

    There are two available options for creating a server backup
    • Option 1 = Stop the server and copy the data (available for Windows and Linux)
    • Option 2 = Copy data during operation (available for Linux)

    The precise procedure is described below.

    1. Creating a Docker backup

    Creating a backup while the server is stopped

    The procedure described below applies to Windows and Linux.

    Run the following commands in the Shell of the server.
    1Stop the server:
    docker stop centrum
    2Copy data from the server to the host system:
    docker cp centrum:/<Container-Data-Folder-Path> <Destination-on-host-system>

    The <Destination-on-host-system> string leads to the storage location for the backup.
    For example, C:\backup\centrum\
    1. Creating a Docker backup

    Creating a backup while the server is running

    The procedure described below only applies to Linux.

    1Install SQLite CLI
    Run all of the following commands in the shell.
    2Get the path to the Docker volume:
    docker volume inspect centrum-data
    Upon entering Mountpoint, the path for the Docker volume is displayed, for example: /var/lib/docker/volumes/centrum-data/_data/
    3Copy the database (the command does not copy all of the data, just the database):
    sqlite3 <docker-volume-path>/centrum.db ".backup <Destination-on-host-system>/centrum.db"
    • Instead of <docker-volume-path>, enter the path for the Docker volume
    • The string <Destination-on-host-system> leads to the save location for the backup.
      For example, /var/backups/centrum/
    4List all of the data that appear in the same directory as the database:
    ls <docker-volume-path>
    • centrum.db is displayed
    • speednet.cert is displayed
    • ...
    5Copy the speednet.cert file:
    cp <docker-volume-pfad>/speednet.cert <path-of-backup>/speednet.cert
    • This command can be used to copy all of the data in the directory
    • In order to copy additional data, replace the file name (in this example, instead of speednet.cert, insert the new file name)
    1. Creating a Docker backup

    Loading the backup

    1Stop the server:
    docker stop centrum
    2Copy the backup data to the desired directory:
    docker cp <Destination-on-host-system> centrum:<Container-Data-Folder-Path>
    3Restart the server:
    docker start centrum
    1. Creating a Docker backup

    Creating a Windows backup

    1Stop the service "Central User Management Service" in the Windows services
    2Open Windows Explorer and navigate to the database path:
    • C:\ProgramData\Fronius\Central User Management\database
    3Copy the "centrum.db" file
    4Start the service
    1. Creating a Docker backup

    Loading a Windows backup

    1Stop the service "Central User Management Service" in the Windows services
    2Open Windows Explorer and navigate to the database path:
    • C:\ProgramData\Fronius\Central User Management\database
    3Replace the "centrum.db" file with the backup
    4Start the service

    Installing the Update

    Performing a Docker update

    1Create a Central User Management server backup—see Overview of backup options on page (→)
    2Using the shell of the operating system, run the following command in order to delete the existing container for Central User Management:
    docker rm -f <container-name>
    3Using the shell of the operating system, run the following command in order to update the existing CENTRUM Server Image:
    docker pull registry.pw.fronius.com/centrum
    4Restart the Central User Management Server—see Starting the server from page (→)

    Use the Docker volume to start the Central User Management Server.
    1. Installing the Update

    Performing a Docker update

    1Create a Central User Management server backup—see Overview of backup options on page (→)
    2Using the shell of the operating system, run the following command in order to delete the existing container for Central User Management:
    docker rm -f <container-name>
    3Using the shell of the operating system, run the following command in order to update the existing CENTRUM Server Image:
    docker pull registry.pw.fronius.com/centrum
    4Restart the Central User Management Server—see Starting the server from page (→)

    Use the Docker volume to start the Central User Management Server.
    1. Installing the Update

    Performing a Windows update

    1Start the installation file and follow the process

    Using Specific Versions

    Using specific versions

    Depending on the user's requirements, Central User Management can be started in any available version. In order to do this, adapt the command used to create the Central User Management container as described below.

    Command used to create the Central User Management container

    docker create --name centrum -p <https-port>:443 -p 4711:4711 -v
    centrum-data:/<Container-Data-Folder-Path> -e ASPNETCORE_
    URLS="https://+;http://+" -e ASPNETCORE_HTTPS_PORT=<https-
    port> -e ASPNETCORE_Kestrel__Certificates__Default__Password=
    <Certificate-Password> -e ASPNETCORE_Kestrel__Certificates__
    Default__Path=<Certificate-Path-In-Container> --restart=always
    registry.pw.fronius.com/centrum

    Adapt the command as follows in order to use a specific version:
    1Replace the registry.pw.fronius.com/centrum string with:
    registry.pw.fronius.com/centrum:<version-number>

    Instead of <version-number>, enter the desired Central User Management version (for example 1.0.0)
    1. Using Specific Versions

    Using specific versions

    Depending on the user's requirements, Central User Management can be started in any available version. In order to do this, adapt the command used to create the Central User Management container as described below.

    Command used to create the Central User Management container

    docker create --name centrum -p <https-port>:443 -p 4711:4711 -v
    centrum-data:/<Container-Data-Folder-Path> -e ASPNETCORE_
    URLS="https://+;http://+" -e ASPNETCORE_HTTPS_PORT=<https-
    port> -e ASPNETCORE_Kestrel__Certificates__Default__Password=
    <Certificate-Password> -e ASPNETCORE_Kestrel__Certificates__
    Default__Path=<Certificate-Path-In-Container> --restart=always
    registry.pw.fronius.com/centrum

    Adapt the command as follows in order to use a specific version:
    1Replace the registry.pw.fronius.com/centrum string with:
    registry.pw.fronius.com/centrum:<version-number>

    Instead of <version-number>, enter the desired Central User Management version (for example 1.0.0)