WCC will not communicate with our primary Workload Automation AE application server yet it communicates fine with the shadow application server.
search cancel

WCC will not communicate with our primary Workload Automation AE application server yet it communicates fine with the shadow application server.

book

Article ID: 11896

calendar_today

Updated On:

Products

CA Workload Automation AE - Scheduler (AutoSys) Autosys Workload Automation

Issue/Introduction

Workload Automation AE (AutoSys)

Workload Control Center

 



When attempting to validate the Workload Automation AE instance from WCC we see the following: E190099 AST - Connection exception encountered. CAUAJM_E_10062 Failed to get initial configuration from CA WAAE Application Server(s).

If we change the Workload Automation AE instance definition in WCC to only use the shadow machine's application server, the server validates.

 

Environment

Workload Automation AE (AutoSys)Workload Control CenterPlatform - ANY

Resolution

The error is typically a result of an inconsistent configuration.

Usually a value for AutoServerPort or UseEncryption, the $AUTOUSER/config.$AUTOSERV file(s) do not match between the two AE hosts and/or WCC.

Additionally confirm consistent values are being used for the EnablePmux and EnableSSL settings in csampmux.

Run the following to review the csampmux settings (run this on all AE and WCC hosts as root) :

$CSAM_SOCKADAPTER/bin/csamconfigedit display 

$CSAM_SOCKADAPTER/bin/csamconfigedit port=<AutoServerPort> display

$CSAM_SOCKADAPTER/bin/csamconfigedit portrange=49152-50176 display

 

Example of how to change a value:

$CSAM_SOCKADAPTER/bin/csamconfigedit port=9000 EnablePMUX=True

NOTE: A restart of the application server would be needed to reflect any changes if they were made on the Workload Automation AE  application server(s).