Executing Nexus CM as a System Service | Utimaco Integration Guides

The <install_root>/bin/cmservices script can be used to install or remove the CF, CIS and CMSNMP services as system services. To install them as system services, run the following command: <install_root>/bin/cmservices install

<install_root>/bin/cmservices script can also be used to start, stop or check the status of all services (e.g. ./cmservices status).

Start the services:

service cmsnmp 
start service cis 
start service cf start

Check the log files in <install_root>/logs to see that the services started successfully. If not, see the following step for further troubleshooting.
The CM server components will use the first found Java executable file available on the $PATH. To use a specific Java version, or if the $PATH does not include a directory where Java can be found, you can explicitly specify which Java version should be used by setting a parameter like the following in <install_root>/bin/*_launch.conf: JAVA=/usr/jvm/jdk-default/bin/java

When installing the CM services on a system that uses a systemd, it is possible that the default $PATH, as seen by the systemd service wrappers, does not include the expected Java version. If this is the case, then calling the service cis start, for example, might not start the service. It will instead be reported as active (exited) by service cis status. To correct this, see the previous step of how to explicitly set the Java executable file to use.