The classes and methods of the AE ApplicationInterface can be used as soon as the library has been integrated in your program.
Data between the program and the AE system is exchanged via "Requests". Keep in mind that you should establish a connection to the AE system and log on to a clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type., as otherwise requests cannot be sent or received.
The following steps are always required, regardless of how your program is used:
Requests are used for retrieving information from or executing an actionActions are predefined building blocks for recurring activities. They are commonly used for managing third party systems or in deployment scenarios. in the AE system. The supplied packageA Package is an instance (a version, a revision, a tag, …) of your application and defines the content which you want to deploy. Here you decide, if you want to deploy the entire application or just a few specified components. includes several examples which describe how the AE.ApplicationInterface is best used. Additionally, the documents shown below provide information about the most important classes.
See also:
Classes for Objects
Classes for Workflows and Schedules
Classes for Activities
Classes for Statistics and Reports
Classes for the System Overview
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |