search cancel

The password in the CallAPI is not taken into account

book

Article ID: 189632

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Question of behavior: CallAPI for Windows
Ref: https://docs.automic.com/documentation/webhelp/english/AA/12.3/DOCU/12.3/Automic%20Automation%20Guides/help.htm#AWA/Integration/CallAPI_Overview.htm?Highlight=ucxbxxxc

EXAMPLE FOR WINDOWS is not correctly describing the default behavior:
UCXBXXXC SCRIPT=C:\AUTOMIC\CallAPI\script.txt LOGON=98,SMITH INI=C:\AUTOMIC\CallAPI\WINDOWS\ucxbxxxc.ini

Actual behavior
- If LOGON name (and dept as optional) is defined without password (as example) --> U00003210 Logon error: Access denied
- If LOGON parameter is not defined, credential written in ini file is used --> logon successful, script is triggered.

Cause

Wrong example.

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

Correct behavior:
- If LOGON is not used in CallAPI command, credential specified in INI config file is used.
- If LOGON is used, you must specify password because credential in INI file is not used.

Online documentation will be fixed.