Nexus' software components have new names:

Nexus PRIME -> Smart ID Identity Manager
Nexus Certificate Manager -> Smart ID Certificate Manager
Nexus Hybrid Access Gateway -> Smart ID Digital Access component
Nexus Personal -> Smart ID clients

Go to Nexus homepage for overviews of Nexus' solutions, customer cases, news and more.


This article describes the start order when starting the Smart ID Certificate Manager (CM) server components on Linux. Use this instruction if you want to start the CM server components manually. Normally, the server components are configured to start automatically. For Windows, see Start Certificate Manager server components on Windows.

The CM server components are installed and run as services. They will be started automatically when the CM operator starts the relevant server.

This is the recommended server component start-up sequence:

  • Start SQL database server
  • Start CIS
  • Start CF
  • Start remaining servers

Expand/Collapse All

Prerequisites

If a Hardware Security Module (HSM) is used with the CIS server, it must be powered on and have been configured. Refer to the manufacturer's documentation for the necessary instructions.

The SQL database server must have been configured to be automatically started.

Step-by-step instruction

This instruction describes the case where CIS is used separately from CF.

  1. Power on the CIS host machine and log on to the operating system.
  2. Power on the CF host service and log on to the operating system.
  3. To start the CM services in Linux, type the following commands at the command prompt:
    1. ./cis start
    2. ./cf start
  4. To avoid manual intervention during the start of the CIS service, set the pin parameter for each cryptographic device installed and configured in cis.conf.
  5. As an alternative, use the <install_root>/bin/cmservices script to install or remove the CF, CIS and SNMP services in the Services Manager. For example, use this command to install the services:

    Example: Install CF, CIS and SNMP services
    ./cmservices install
  6. Use this script to start, stop or check the status of all services, for example:

    Example: Check the status of all services
    ./cmservices status

In a cluster installation with SNMP installed at a separate location, you must use the cmservices command in the SNMP installation to install cmsnmp as a service.