AutoSys 24.1: WCC and EEM Startup Order and Systemd Migration

Products

• Autosys Workload Automation

Issue/Introduction

There is confusion regarding the proper startup order and the presence of legacy init.d scripts (such as S99igateway) in AutoSys 24.1 environments running on RHEL 8 or 9.
Users may see old scripts in /etc/init.d/ and need clarity on how to manage these services using systemd.

Environment

• Product: AutoSys Workload Automation 24.1 (and 12.x)
• Operating System: Red Hat Enterprise Linux (RHEL) 8 or 9
• Components: WCC (Web UI), EEM (Embedded Entitlements Manager), DXServer (CA Directory), iGateway

Cause

In clean installations of AutoSys 24.1 on modern Linux distributions, systemd is the standard for service management. Legacy init.d scripts may remain after upgrades or in environments where they were manually retained.
Furthermore, if EEM is not installed on the local WCC server, the iGateway service is not required, leading to confusion when legacy scripts are present.

Resolution

1. Service Startup Order

In environments where EEM and WCC are installed on the same machine, the services must be started in the following sequence:

1. DXServer / CA Directory
2. iGateway Service
3. CA-wcc-services
4. CA-wcc

Note: CA-CCS (Common Components) does not require a dedicated startup script as it is initiated by other components as needed.

2. iGateway Necessity

If EEM is hosted on a remote server and is not installed locally on the WCC host, the S99igateway script is not required and can be removed from /etc/init.d/.

3. Systemd Service Examples

Official documentation currently lacks specific examples for dxserver and igateway systemd files. Use the following examples to migrate from init.d to systemd on RHEL 8/9.

A. DXServer Service File (/etc/systemd/system/dxserver.service)

[Unit]
Description=Broadcom DXserver Service
After=network.target network-online.target

[Service]
Type=forking
User=dsa
Group=etrdir
# Remove limits just like iGateway
TasksMax=infinity
LimitNOFILE=131072
LimitNPROC=infinity
# Note: Adjust the paths below if your dxserver start script is located elsewhere
ExecStart=/bin/bash -c 'source /opt/CA/SharedComponents/CADirectory/dxserver/install/.dxprofile; /opt/CA/SharedComponents/CADirectory/dxserver/bin/dxserver start all'
ExecStop=/bin/bash -c 'source /opt/CA/SharedComponents/CADirectory/dxserver/install/.dxprofile; /opt/CA/SharedComponents/CADirectory/dxserver/bin/dxserver stop all'
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

B. iGateway Service File (/etc/systemd/system/igatewayd.service)

[Unit]
Description=Autosys iGateway Service
After=network.target network-online.target

[Service]
Type=forking
# Remove systemd resource limits that choke the Broadcom JVM
TasksMax=infinity
LimitNOFILE=131072
LimitNPROC=infinity
LimitCORE=infinity
ExecStart=/bin/bash -c 'source /etc/profile; /opt/CA/SharedComponents/iTechnology/S99igateway start'
ExecStop=/bin/bash -c 'source /etc/profile; /opt/CA/SharedComponents/iTechnology/S99igateway stop'
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

4. Deployment

1. Create the files above with 755 permissions.
2. Enable the services:
    

   systemctl daemon-reload
systemctl enable dxserver.service
systemctl enable igatewayd.service

    

Additional Information

iGateway (EEM) and CA Directory (dxserver) systemd startup scripts