The CallAPI can be used to process scripts in the AE system from your own C and C++ programs.
For this, you need to integrate the files uccall3.h and ucxbwi3c.lib. Note that your program requires access to the library ucxbwi3c.dll.
The delivery directory contains sample programs that provide a detailed description of how a script activation can be implemented.
The file uccall3.h gives information about structure and functions.
Scripts are always activated with the following steps:
You can log on to several AE systems at the same time and process various scripts. In this case, a Dialog license is used for each connection.
In your programs, you can use the functions listed below. These supply return code 0 if the action was successful or a message number if an error occurred.
Description |
Data type of return code |
Function |
---|---|---|
Logging on to the AE system |
long |
UCCALL3_Logon (structure, login data, connection) Data type of structure: UCCALL_PARAMS* Format for login data: Format for connection data for the communication process: |
Activating a script |
long |
UCCALL3_ActivateScript (structure, script) Data type of structure: UCCALL_PARAMS* |
Logging off the AE system |
long |
UCCALL3_Logoff (structure) Data type of structure: UCCALL_PARAMS* |
Universal function |
long |
UCCALL3 (structures) UCCALL3 can be called instead of the functions described above. In this case, indicate the opcode in the structure in order to have the required operation processed. Data type of structure: UCCALL_PARAMS* |
Information such as the system name or the script's returned RunID is stored in the structure UCCALL_PARAMS. It contains the following variables:
Data type |
Variable |
Description |
---|---|---|
char [4] |
cOpCode |
Operation code This variable must be set if the universal function should be used. Allowed values: |
char |
cErrorCode |
The error code in cErrorCode is automatically set and can contain one of the following values: " " - no error occurred |
char [3] |
cInterface |
The interface number must always contain the value 3. |
char [8] |
cSystemName |
Name of the AE system to which the connection should be established |
unsigned short |
sTimeout |
Period in seconds during which the CallAPI waits for an AE system response |
char |
cLanguage |
Language in which messages are output |
unsigned char |
cFlag1 |
Depending on the specified value, this flag results in one of the processing options listed below: "CALL_FLAG1_INI_SERVER" - connection to communication process is retrieved from INI file |
unsigned long [4] |
lUnused1 |
Not used |
unsigned long |
Output |
Not used |
unsigned long [4] |
lUnsued2 |
Not used |
unsigned long |
lScriptRunNr |
RunID of the script |
unsigned long |
lRetCode |
Return code of script execution |
char [256] |
cRetText |
Variable message part explaining the return code's value |
char* |
pIniFile |
Path and name of INI file |
unsigned long |
hZuLog |
For internal CallAPI processing only |
unsigned long |
hZuTrc |
For internal CallAPI processing only |
unsigned long |
hZuHlp |
For internal CallAPI processing only |
unsigned long [11] |
lUnused3 |
Not used |
void* |
pOwnPointer |
For internal CallAPI processing only |
See also:
About the CallAPI