You may want to have the same set of actions / commands performed in the jobs of a given type. For instance, "all Unix jobs should use 'BASH' as the default shell".
In Client 0 it's possible to create include objects that will subsequently affect all jobs used in every Automation Engine (AE) client.
These 3 types of includes affect their related job types:
- HEADER: is executed at the beginning of every job, before the actions listed in the Process tab.
- RESTART: content is executed every time a job is restarted
- TRAILER: is executed at the end of each execution, after the commands / scripts listed in the job's process tab
As these objects are part of the initial data, it's not recommended that they be modified directly because they will be overwritten during the next AE upgrade. You can still do so, but you will need to export them before upgrading your Automation Engine's database and import them in again afterward.
A safer approach is to create other include objects of your own. This is supported by default in the HEADER/RESTART/TRAILER includes, as they contain a reference to other include objects, with predefined names.
'HEADER.UNIX.USER.START' and 'HEADER.UNIX.USER.HEAD', 'HEADER.UNIX.USER.PRE, you will see that there are some placeholders for 'HEADER.UNIX: if you edit Example
These objects are not delivered by default with the Automation Engine, but if you create them, their content will automatically be taken into account in all the jobs of the given type - Unix in this case.There are HEADER / RESTART / TRAILER objects for pretty much every job types, so this is a very easy way to add actions / modifications to all jobs from a given type.