When AppRCadm is not used, if you want to have your application to automatically start during system boot up, and auto stop when system shutdown, your application developer has to develop application start/stop scripts, and hand them over to root account owner, and ask him/her to help to put the scripts under system's RC directories.
There are a few issues with this way of work.
||The application start/stop scripts are different from what application administrator would use if he logs on to the system using application admin account to start or stop the application.
||The system administrator may not understand what your scripts will do.
||When the scripts get run during system boot or shutdown, they are run under root privilege, but the application does not need that privilege to run, a clear violation of the principle of least privilege.
Because system administrator may not understand the scripts logic properly, if something in the script goes wrong, it affects the whole system.
Moreover, due to each UNIX flavor has its own way of doing the RC processing, it's quite complicated when your application is able to run on multiple types of UNIX/Linux platforms.
Our AppRCadm is the software which can help to solve all these problems.
With AppRCadm, the application administrator takes full responsibility to install the application start/stop scripts, and our software will automatically detect the scripts' owner, and use that owner account to run the scripts, so no violation to the least privilege principle. And the setup is much easier: you don't need to worry about which K number you should choose if you know what number you will choose for your application's start up script, they are SAME! And our software will do the job for running the start/stop scripts using the proper account and sequence.