The following document includes information and notes required for using the CallAPIA programming interface that processes a script in the Automation Engine system. It can be called directly from within the program itself or from a different program. for SAP.
The RFC Server transfers the scriptA particular Automation Engine object type. to the AE system. It includes a functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… module called AE which can be called in your ABAP programs.
The folderTop level entities such as Environment, Deployment Target, Activity, … are stored in folders. The permissions a user has on an entity depend on the permissions that are set on the folder for the entities. "sample" of the delivery directory includes example programs which show how it is best used.
Sound knowledge of ABAP/4 is required in order to understand the following descriptions:
|
Parameter |
Description |
---|---|---|
Import Parameter |
AE client |
|
|
trcflg(1) type c |
Trace flag |
|
userabtl(200) type c |
|
|
username(200) type c |
Name of the AE user |
|
userpass(32) type c |
Password of the AE user |
Export Parameter |
msg(255) type c |
Message |
|
run(10) type c |
Run number of the scripts |
Tables |
script |
Script table (a total of 255 characters per line) |
Exceptions |
logon-failed |
Logging on to AE was not successful |
|
others |
Other error |
call function 'UC4' destination 'UC4'
exporting
client = p_clint
trcflg = '0'
userabtl = p_usera
username = p_usern
userpass = p_userp
importing
msg = omessg
run = orunnr
tables
script = uscript
exceptions
logon_failed = 1
others = 99.
See also:
About the CallAPI
Using the CallAPI
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |