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 for starting Smart ID Certificate Manager (CM) server components on Windows. Use this instruction if you want to start the CM server components manually. Normally, the server components are configured to start automatically. For Linux, see Start Certificate Manager server components on Linux.

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 there is only one service - CF. In this case, CF also handles the CIS functionality.

  1. Power on the CF host machine and log on to the operating system.
  2. To check that the CF service is started:
    1. Go to the Windows Start menu > Control Panel and in Administrative tools, click the Services icon.
    2. If the service named Nexus CF has the status Started, the CF is running.
  3. Certificate Manager is now operational.

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. The CIS service starts automatically.
    • 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.
    • If at least one device requires a PIN that is not configured and not using a PIN pad, the CIS service will start a temporary web server and wait until the required PIN codes are entered in a web browser, see Start and configure password server in Certificate Manager.

    • Should an error occur while the service attempts to start, an error code and a short description are printed to the log file. Use a text editor to read the log file.

  3. To check that the CIS service is started:
    1. Go to the Windows Start menu > Control Panel and in Administrative tools, click the Services icon.
    2. If the service named Nexus CIS has the status Started, the CIS is running.
  4. Power on the CF host machine and log on to the operating system.
  5. Check if the service Nexus CF has been started.
  6. Certificate Manager is now operational.

Stop or restart the services

  1. Go to the Windows Start menu > Control Panel and in Administrative tools, click the Services icon.
  2. Select a service in the list.
  3. Click the Stop Service icon to stop the service.
  4. Click the Restart Service icon to restart the service.

    Restart the services in the order shown in "Start-up sequence" above.