Using systemd instead of init.d to start CMOD in RHEL

[JeanineJ]

My Unix guys are bugging me to use systemd instead of init.d to start and stop CMOD on my new RHEL8 server. I don't know what exactly I'm supposed to do and I figured I'd start here with the user group to see if anyone was successful in using systemd.
We currently have a script that starts the DB instance, then arssockd, then arsjesd, wait 60 seconds then start arsload as a daemon.
The stop part stops arssockd and end the DB instance.

If anybody has successfully done it, let me know and point me in the direction of resources.

[jsquizz]

I actually tried doing this on a redhat system about 2-3 years ago and for whatever reason I couldnt get it to work, but- It was a POC.

I essentially backdoored it with a cronjob that would run every 5 minutes and also act as a monitoring script

Db2 Running? Good.. No? Start!..sleep
ARSSOCKD Running? Good.. No? check DB2-> Start
ARSLOAD(s)/ARSJESD Running? Good.. No? Check arssockd-> Start!

That was the best purpose because I also added logic to where if it failed a second time in X minutes, to send out an email/page. So within 5 min of a server being booted, it would come up.