KB482894: How to register MicroStrategy processes as services on Linux when installation is performed by a non-root user

BACKGROUND:
When installing the Strategy platform on Linux operating systems, an option is provided to register the processes as services so that they may be started automatically on machine startup and controlled via the operating system's service control functions.  Registering services on Linux requires root-level privileges as the service startup scripts will be placed in the /etc/init.d/ folder, so the Strategy installer can only perform the registration when being run as the root user.  However, it is possible to manually register the processes as services if the installation is performed as a non-root user following the steps below.
ACTION:
1. Install Strategy products as a non-root user
2. After the installation has completed, copy the desired service scripts from <MSTR_INSTALL>/initd_scripts into the system directory /etc/init.d/. This step will require root-level privileges.
3. Open the script file named Strategy and search for "SVCPREFIX" as shown below:
4. Copy the value of SVCPREFIX and add it to the name of the Strategy service scripts (except for the Strategy script), for example:

mv kafka-zookeeper mstr-amunukun@2018-12-03T11:21:6-kafka-zookeeper

5. Register the scripts as services using chkconfig (except for the Strategy script)

chkconfig --add mstr-amunukun@2018-12-03T11:21:6-kafka-zookeeper

 
6. After registering verify the services individually

• service xxxx status|stop|start

service mstr-amunukun@2018-12-03T11:21:6-kafka-zookeeper status

7. Verify the Strategy script

service Strategy status

 
Now, the status of each Strategy service can be checked using the format:

service service-name status

To start a service:

service service-name start

To stop a service:

service service-name stop

To restart a service:

service service-name restart

NOTE:  Due to a limitation in SUSE Linux 12, the "service" command cannot detect changes in the service status that were not initiated using the "service" command. For example, when a service is running, if the process was killed or terminated, the "service service-name status" command would still show the service status as running, and consequently "service service-name start" command would fail because it thinks the service is already running.

 

KB482894