Our current version of PS is r12.52 SP1 running on RHEL 6. For SiteMinder policy server auto-start on server reboot, we simply created a file "siteminder" in: /etc/init.d/
Below is the content of this file:
# this script starts and stops the siteminder policy server# at boot time# start
case "$1" in
su - smuser -c /usr/pservices/ca/siteminder/start-all &touch /var/lock/subsys/siteminder
su - smuser -c /usr/pservices/ca/siteminder/stop-all &rm -f /var/lock/subsys/siteminder
For the new r12.8.02 running on RHEL 7, I came across this document from CA which instructs us to setup the policy server auto-start using service daemon: https://docops.ca.com/ca-single-sign-on/12-8/en/installing/install-a-policy-server/install-policy-server-on-unix/configure-auto-startup
Perform the following steps only when configuring auto startup for RHEL 7.
Follow these steps:
Add the following content in the file /etc/systemd/system/S98sm.service and replace nete_ps_root with an explicit path to the CA Single Sign-on installation directory.
[Unit]Description=S98sm ServiceRequires=network.target [Service]Type=forkingUser=smuserExecStart=-"nete_ps_root"/start-all ExecStop=-"nete_ps_root"/stop-allRestart=on-abort [Install]WantedBy=multi-user.target
My question here is, could I still implement the policy server auto-start for the r12.8 on RHEL 7 the same way as I currently do for our r12.52 on RHEL 6 or do I really need to follow the instruction from the CA doc that is specifically for r12.8 on RHEL 7 for proper policy server auto-start on server reboot?
I haven't tried using the /etc/init.d approach with RHEL 7. I converted to systemctl and haven't looked back. You might want to review this thread, posted a year ago, which I think is more detailed and helpful than what you found in docops:
SSO systemctl service files