Auxiliary Listening Port

The Auxiliary Listening Port parameter defines the port number the scheduler or the application server uses to listen for inbound Automation Framework Message (AFM) protocol data using non-SSA communication. Network data between the scheduler and the agent or the scheduler and the CA Workload Automation EE manager is prepared using the proprietary AFM protocol. The scheduler or application server auxiliary listening port is used primarily to receive inbound messages from agents running on non-SSA ports.

The following field on the Application Server - CA Workload Automation AE Administrator window lets you define this parameter:

Auxiliary Listening Port

Defines the port number the application server uses to listen for inbound AFM protocol data using non-SSA communication.

Default: 7500

Note: On UNIX, the equivalent configuration parameter is AppSrvAuxiliaryListeningPort.

The following field on the Scheduler - CA Workload Automation AE Administrator window lets you define this parameter:

Auxiliary Listening Port

Defines the port number the scheduler uses to listen for inbound AFM protocol data using non-SSA communication.

Default: 7507

Notes:

On UNIX, the equivalent configuration parameter is SchedAuxiliaryListeningPort.
The scheduler auxiliary listening port is also used to receive job dependencies and statuses from the mainframe scheduling managers. For example, the scheduler uses this port to receive messages from the CA Workload Automation EE manager or CA WA Agent for z/OS (a mainframe manager with minimal agent capabilities).

Notes:

By default, CA Workload Automation AE does not enable SSL communication for any of its ports (physical or virtual). When you configure the SSA port settings of the scheduler or application server auxiliary listening port, ensure that you do not enable SSL communication.
The scheduler auxiliary listening port must be different from the application server auxiliary listening port. The scheduler and application server auxiliary listening ports must be physical ports. So, we recommend that you configure the SSA port setting to disable port multiplexing (EnablePmux=False), otherwise CA Workload Automation AE uses the virtual ports provided by SSA. If EnablePmux is set to True or the scheduler or application server auxiliary listening port is not defined, CA Workload Automation AE does not initiate communication with agents that are configured to run on physical ports. For more information about configuring CA Workload Automation AE to work with SSA, see the Windows Implementation Guide.
During the CA Workload Automation AE installation, the scheduler auxiliary listening port is set to 7507 by default. If you are performing a custom installation, you can specify a different scheduler auxiliary listening port using the Scheduler Properties page. CA Workload Automation AE uses both the virtual ports and the auxiliary ports at the same time. The scheduler log displays the ports used by CA Workload Automation AE as follows:
```
CAUAJM_I_20366 CA WAAE Scheduler operational on agent listener port 49161.
CAUAJM_I_20367 CA WAAE Scheduler operational on auxiliary agent listener port 7507.
```
During the CA Workload Automation AE installation, the application server auxiliary listening port is set to 7500 by default. If you are performing a custom installation, you can specify a different application server auxiliary listening port using the Application Server Properties page. CA Workload Automation AE uses both the virtual ports and the auxiliary ports at the same time. The application server log displays the ports used by CA Workload Automation AE as follows:
```
CAUAJM_I_20366 CA WAAE Application Server operational on agent listener port 49169.
CAUAJM_I_20367 CA WAAE Application Server operational on auxiliary agent listener port 7500.
```

More Information:

Define Communication Ports for the Scheduler