"unisrvcntr start all" does not work with CA-cci / CCI components

Products

• Autosys Workload Automation

Issue/Introduction

CCI was installed using Install-CCI but "unisrvcntr start all"  CCI components are not listed or started.

#unisrvcntr start all

WAAE Agent (WA_AGENT) Agent service is starting...
Agent service has been started
started.
Executed waae_agent-WA_AGENT start...............................OK
WAAE Application Server (C1D) started.
Executed waae_server.C1D start...................................OK
WAAE Scheduler (C1D) Scheduler started.
started.
Executed waae_sched.C1D start....................................OK
WAAE Web Server (C1D) started.
Executed waae_webserver.C1D start................................OK

unisrvcntr status command does show the status of CCi:

CA Services Status Report
Component Name Pid Status
------------------------------------ ------- --------------
WAAE Web Server (<InstandID>) 8039 running
WAAE Application Server (<InstandID>) 7651 running
WAAE Scheduler (<InstandID>) 7760 running
WAAE Agent (WA_AGENT) 7570 running
CA-CCI Server 2450 running
CA-CCI Remote Server 2464 running
CA-CCI Clean Up 2460 running
CA-CCI Legacy Proxy 2462 running

 

Registering CCI manually (unisrvcntr register --with CA-cci) did not make a difference 

 

Environment

Autosys

Cause

By default installing CCI does not register the product with unisrvcntr.

For the unisrvcntr start to work, Cross Platform scheduling needs to be enabled in $AUTOUSER/config.$AUTOSERV.  If this is not enabled, CCI startup will not work via unisrvcntr. Once it is enabled unisrvcntr controls the CCI component startup/shutdown as well.

The waae_sched.XXX script is written to check the config and see if cross-platform is enabled. If it is, it looks for the CA-cci script in /etc/init.d and runs it to start CA-cci if it exists...

sched_start() {
        set -- sched_pid
        test -n "$1" && return 0
        if grep '^CrossPlatformScheduling=[12]' $AUTOUSER/config.$AUTOSERV >/dev/null; then
                echo
                test -x /etc/init.d/CA-cci && /etc/init.d/CA-cci start
                test -f /etc/profile.CA && . /etc/profile.CA
        fi

Resolution

Enable Cross Platform Scheduling option in the Autosys configuration files and then restart everything using unisrvcntr.

Additional Information

If CCI needs to be started with unisrvcntr start all regardless of whether cross platform is enabled in AutoSys, add the needed changes to the main WAAE service's required start/stop list. 

 

• Edit /etc/init.d/CA-WAAE and look for the # Required-Start and # Required-Stop lists toward the top.
• In the Required-Start list, add CA-cci right after $remote_fs...

# Required-Start: $network $remote_fs CA-cci CA-wcc waae_webserversoap waae_agent-WA_AGENT CA-wcc-services waae_sched.PL2 waae_webserver.PL2 waae_server.PL2

• In the Required-Stop list, add CA-cci at the end of the list...

# Required-Stop: $network $remote_fs CA-wcc waae_webserversoap waae_agent-WA_AGENT CA-wcc-services waae_sched.PL2 waae_webserver.PL2 waae_server.PL2 CA-cci

 

• CCI should be started before the Scheduler starts, and shutdown after the Scheduler stops