Output Pages

The External Output Files page allows you to register files that are stored on the Agent. After a Job has been executed, you can access those files directly from the Reports window. On the Output-Scan page you set the filters to be used to search the report of a task or an external output file. You also define the reaction to your search results.

This page includes the following:

External Output Files

This page is active for Jobs (JOBS) that run on Windows, UNIX, SAP, R3, RA, JMX. SQL, VMS and OA Agents.

Overview

When executing objects, comprehensive output files and reports are generated both in the Automation Engine and, in the case of Job objects, in the target systems. When defining the general object settings you also specify if the reports should be stored in the Automation Engine database or as a file in the target system. From an Automation Engine perspective, reports stored on the agent are external reports and are transferred from the agent to the Automation Engine via File Transfer.

To have those files available and accessible from the User Interface later on, you register them on the External Output Files page indicating their path. The files you enter here are then accessible as Directory reports from the Reports window.

Important!

Standard Job outputs (Reports, JCL, scripts, etc.) are automatically registered as such and displayed on is page after execution. You can add other outputs as well. Once the Job has been executed, the files registered here are available for display from the Reports dialog.

Tip: Specify files that are expected through the execution of Jobs, such as the text file that the JCL generated, on the Process page.

To Register Output Files

  1. In the Fully Qualified Name column enter the path and name of the file to be registered. You must specify the full path.

    Notes:

    • Wildcard characters are not allowed.
    • The file extension is irrelevant.

  2. When the Agent accesses the output file through the Automic Web Interface, it logs on to the computer and transfers the file. If you activate the checkbox in the Requires User's Login column, the Login object that has been assigned to that particular user is applied. Otherwise, the login information of the job Login object is used.

    Notes:

    • If you activate this option, do not forget to define a default login to log on to the Agent in the User object. Otherwise an error occurs when you open the output file.
    • This option is only relevant for operating system Jobs and has no impact on other Jobs (for example, Rapid Automation, SAP and so on).

Another Way to Register Files for Windows and UNIX Jobs

In addition to entering the files here, you can also register files as external output using the :REGISTER_OUTPUTFILE script element. The difference between both methods lies in the registration time:

Output-Scan Page

This page is available and active for the following object types:

Overview

When executing objects, reports and output files are written and stored and, if so specified on the Output Pages, they are registered as external output files by the Automation Engine. They are then transferred to the Agent and can be accessed through the Automic Web Interface.

Sometimes you need to search for specific strings in those files and, depending on the search result, you might want to specify follow-up actions. They are then executed before the defined post process actions, regardless of the task end status.

On this page you define the settings that scan the files and specify the actions that should take place depending on the search outcome.

Prerequisites

You must have defined the following:

Important! The output scan always requires login information, even if the Windows or UNIX Agent's password check is disabled (UC_HOSTCHAR - ANONYMOUS_FT/JOB).

To Define the Filter Parameters and Follow Up Options

  1. In the Filter Object columns enter or select the Filter object that contains the criteria you want to apply to scan the reports and/or external files for specific strings.

    If you add more than one filter, the criteria of all selected filters are combined.

  2. In the Filter Criteria Apply columns activate the checkbox to indicate that the search criteria must be met. Leave it deactivated if they should not be met. Basically, this is a true/false setting.

  3. In the Set Return Code column enter the return code you want the task to specify for the result of the search.

    This option is set to 0 by default, where 0 means OK. Other values indicate an error.

    The first entry that meets the conditions determines the return code that will be assigned to the task. Successive conditions that apply do not change the return code anymore.

  4. In the Status Text columns enter any user-friendly text that helps users understand the return code.

    This text will be visible in the Status column of the Tasks table.

  5. Optionally, in the Execution of column enter or select here the executable object that should be processed as a reaction to the search result. This object is executed for each line in which the condition applies.

Filter definitions are checked at runtime. For example, a task has the FAULT_POST_PROCESSING status if the Filter object you specify here tries to search for a string in a report that does not exist in the task.

To Use a Different Agent and/or Login Object for File Scan

By default, the Agent and Login object assigned to a task are used to access an external file that has been defined in a Filter object. In the case of File transfers, the destination Agent is the default.

You can change both the Agent and the Login object here.

Example

Two Filter objects are assigned to the Unix job:

Screesnshot showing the configuration of the Filter objects

The list is processed bottom up, so the report is searched for first. These are the possible outcomes:

See also: