Defining Workload Automation AE Server 11.3.5 to WCC 11.3.5

Document ID : KB000048161
Last Modified Date : 14/02/2018
Show Technical Document Details

Step 1

Determine current Workload Automation AE configuration setting:

Review the file $AUTOUSER/config.$AUTOSERV

To review Workload Automation AE's security settings run "autosys_secure"
If option 1 reads:
Activate CA EEM instance security
that means Workload Automation AE is running in Native mode.
If option 1 reads:
Revert to NATIVE instance security
that means Workload Automation AE is using EEM.
Determine which EEM host is being used by selecting option 2 (Manage CA EEM server settings) then option 1 (Show current CA EEM server settings.)

Step 2

Login to Workload Control Center
Select the Configuration tab and then under the section Servers select Create.
Define the server based on the information/settings collected during Step 1.
Click Save

Step 3

Scroll down to the Deploy section, select the newly added server, click Deploy.
Acknowledge the Deploy Confirmation.

Step 4

Find the server you want to verify.
Select the check box to the left of that server in the Server Results section.
Select Validate from the Select and drop-down list, and click Go.

Note: If you cannot verify a server's status, verify the following items:

The server must be defined properly in Configuration, where the server names listed in the Application Server Host Address field must match the system agent names defined in CA Workload Automation AE exactly. Names are case-sensitive.

Credentials must be set up properly in Credentials if CA EEM is not enabled in the server definition or if the Workload Automation AE server is using a different EEM than WCC.

System agents must be configured properly for CA Workload Automation AE.

For CA Workload Automation AE on UNIX, PAM parameters must be configured properly for the CA Workload Automation AE agent.
For more information, see Credentials Help and the CA Workload Automation Agent for UNIX, Linux, or Windows Implementation Guide.

Also for additional troubleshooting see knowledge document TEC572195 on