PIM: RHEL: How to start endpoint automatically on boot

book

Article ID: 106242

calendar_today

Updated On:

Products

CA Privileged Access Manager - Server Control (PAMSC) CA Privileged Identity Management Endpoint (PIM) CA Virtual Privilege Manager CA Privileged Access Manager (PAM)

Issue/Introduction



How can I configuer Privileged Identity Manager (PIM) endpoint to start automatically when the server boots?

Environment

Release:
Component: SEOSU

Resolution

For Red Hat 6.x and below which use sysvinit please do the following:
 
cp /opt/CA/AccessControl/samples/system.init/LINUX/S95seos /opt/CA/AccessControl/bin 
chmod +x /opt/CA/AccessControl/bin/S95seos 
ln -s /opt/CA/AccessControl/bin/S95seos /etc/rc5.d/S95seos

The above assumes that PIM has been installed to the default location of /opt/CA/AccessControl. If it has been installed to a different location, please adjust the paths as necessary.

For Red Hat 7.x which uses systemd, please request fix T6C7004 from CA Technical Support. This contains the file seos.service. Copy this to /etc/systemd/system.

If you have not installed PIM to the default location of /opt/CA/AccessControl, you will need to edit seos.service and modify the line below to reflect the location you have installed it to:
 
ExecStart=/opt/CA/AccessControl/bin/seload

Execute the following to ensure that the PIM agent is started at boot:
systemctl enable seos.service

If you are unable to request T6C7004 from CA Technical Support, you can use the following for seos.service:
 
[Unit]
Description=Service to start CA Privileged Identity Manager
After=network.service NetworkManager.service NetworkManager-wait-online.service

[Service]
ExecStart=/opt/CA/AccessControl/bin/seload
Type=forking

[Install]
WantedBy=default.target

Note that the above are also applicable to other supported linux distributions/versions, not just Red Hat.