When a jobAn Automation Engine object type for a process that runs on a target system. is processed, Includes are read and used to generate the executable job for the target system. Depending on the job definition, activation data is retrieved, variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. settings evaluated, the attribute dialog facilitated, messages for the target system prepared, the log on/off in the target system facilitated, the job reportA report provides more detailed information about a task's execution or a component. requested, etc.
AE supplies platform-specific Includes in 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. 0000. Within header and trailer includes, userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. Includes are called using the parameter "NOFOUND=IGNORE" in order to avoid errors if these Includes do not exist.
In doing so, individual Includes can be created which are responsible for special tasks during the various stages of job execution. These tasks are then included in AE processing.
For running jobs, you require the rightto run job includes when you use job includes.Note when you use job includes (access method "X" for JOBI objects).
Job |
Header Include |
Trailer Include |
User Includes |
---|---|---|---|
BS2000 |
HEADER.BS2000 |
TRAILER.BS2000 |
HEADER.BS2000.USER.PRE |
GCOS8 |
HEADER.GCOS8 |
TRAILER.GCOS8 |
HEADER.GCOS8.USER.PRE |
JMX |
HEADER.JMX |
TRAILER.JMX |
HEADER.JMX.USER.PRE |
MPE |
HEADER.MPE |
TRAILER.MPE |
HEADER.MPE.USER.PRE |
NSK |
HEADER.NSK |
TRAILER.NSK |
HEADER.NSK.USER.PRE |
Oracle Applications |
HEADER.OA |
TRAILER.OA |
HEADER.OA.USER.PRE |
z/OS |
HEADER.MVS |
TRAILER.MVS |
HEADER.MVS.USER.PRE |
OS/400 |
HEADER.OS400 |
TRAILER.OS400 |
HEADER.OS400.USER.PRE |
PeopleSoft |
HEADER.PS |
TRAILER.PS |
HEADER.PS.USER.PRE |
RA | HEADER.CIT | TRAILER.CIT | HEADER.CIT.USER.PRE HEADER.CIT.USER.HEAD HEADER.CIT.USER.START TRAILER.CIT.USER.END |
SAP |
HEADER.SAP |
TRAILER.SAP |
HEADER.SAP.USER.PRE |
SAP BW |
HEADER.SAPBW |
TRAILER.SAPBW |
HEADER.SAPBW.USER.PRE |
Siebel |
HEADER.SIEBEL |
TRAILER.SIEBEL |
HEADER.SIEBEL.USER.PRE |
SQL |
HEADER.SQL |
TRAILER.SQL |
HEADER.SQL.USER.PRE |
UNIX |
HEADER.UNIX |
TRAILER.UNIX |
HEADER.UNIX.USER.PRE |
VMS |
HEADER.VMS |
TRAILER.VMS |
HEADER.VMS.USER.PRE |
Windows |
HEADER.WINDOWS |
TRAILER.WINDOWS |
HEADER.WINDOWS.USER.PRE |
Due to the program logic, the Include objectAn Automation Engine object type for a script that is frequently used in more than one object. of the own client is used even if an objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task of the same name is available in client 0000.
Automic recommends using user includes for special tasks. You can also modify the supplied header and trailer includes in client 0000 and store them in your own client. This only increases maintenance work when the supplied includes were changed with an updated version due to programming reasons.
There are interdependencies between the individual includes. Keep this in mind when modifying Include objects.
Resources attached to the Storage object may be transferred using external interpreters, where the scriptA particular Automation Engine object type. is entered in the Process Tab of a Job object (JOBS). Jobs containing external interpreter scripts use the header/trailer of existing Include objects. The existing Includes should not be changed.
If you do not intend to work with user-defined Include objects in general or on particular platforms, the administrator can deactivate this functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… in the AE variable UC_SYSTEM_SETTINGS using the key "DISABLE_USER_HEADER". In this case, Include objects are not called and this increases performance.
See also:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |