Example of how to add Workload Automation AE server 11.3.5 within UWCC 11.3.5 and validate the monitor ID/credential user

Products

• CA Directory
• CA IT Asset Manager
• CA Software Asset Manager (CA SAM)
• ASSET PORTFOLIO MGMT- SERVER
• CA Service Management - Service Desk Manager
• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• Workload Automation Agent
• CA Process Automation Base

Issue/Introduction

Example of how to add Workload Automation AE server 11.3.5 within UWCC 11.3.5 and validate the monitor ID/credential user .

Environment

Release: ATSYHA99000-11.3.5-Workload Automation AE-High Availability Option
Component:

Resolution

Here's the steps for adding a server, and monitor user when AutoSys is using native security.
This assumes all other info is correct in UWCC, and that EEM is unchecked
(EEM is checked by default)

1. Identify the appserver, note <Hostname>(short or long hostname)
   <Hostname>
   
   
2. Insert machine via jil
   #insert_machine: <Hostname>
   
   
3. autosys_secure
   add "<User>@<Hostname>" as edit/exec user AND <User>@<Hostname>(Options 2 and 5)
   
   
4. UWCC: add "<User>@<Hostname>" for cred <User> and monitor <User> w/ password
   
   
5. Validate
   Example of how to add Workload Automation AE server 11.3.5 within UWCC 11.3.5 and validate the monitor ID/credential <User>.
   
   Here's the steps for adding a server, and monitor <User> when AutoSys is using native security.
   This assumes all other info is correct in UWCC, and that EEM is unchecked
   (EEM is checked by default)
   
   1. Identify the appserver, note <Hostname>(short or long hostname)
   <Hostname>
   2. Insert machine via jil
   #insert_machine: <Hostname>
   3. autosys_secure
   add "<User>@<Hostname>" as edit/exec <User>AND <User>@<Hostname> (Options 2 and 5)
   4. UWCC: add "<User>@<Hostname>" for cred user and monitor <User> w/ password
   5. Validate
   -------------------
   Here's the steps for adding a server, and monitor <User>when AutoSys is using the same EEM as WCC for security.
   This assumes all other info is correct in UWCC, and that EEM is checked
   (EEM is checked by default)
   
   1. Identify the appserver, note <Hostname>(short or long hostname)
   <Hostname>
   2. Insert machine via jil
   #insert_machine: <Hostname>
   3. autosys_secure
   add "<EEMuser>" as edit/exec user AND "<EEMuser>" (Options 2 and 5)
   4. UWCC: add "<EEMuser>" for the monitor user w/ password
   5. UWCC: add "<EEMuser>@<Hostname>" in the Credentials tab with a password for ECLI to work.
   6. Validate

Here's the steps for adding a server, and monitor user when AutoSys is using the same EEM as WCC for security.
This assumes all other info is correct in UWCC, and that EEM is checked
(EEM is checked by default)

1. Identify the appserver, note <Hostname>(short or long hostname)
   <Hostname>
   
   
2. Insert machine via jil
   #insert_machine: <Hostname>
   
   
3. autosys_secure
   add "<EEMuser>" as edit/exec user AND "<EEMuser>" (Options 2 and 5)
   
   
4. UWCC: add "<EEMuser>" for the monitor user w/ password
   
   
5. UWCC: add "<EEMuser>@<Hostname>" in the Credentials tab with a password for ECLI to work.
   
   
6. Validate