Automation Engine Script Guide > Ordered by Function > Script Structure and Processing > :BEGIN_EXT_INTERPRETER... :END_EXT_INTERPRETER

:BEGIN_EXT_INTERPRETER... :END_EXT_INTERPRETER

Script Statements: They are used to define the beginning and end of the external interpreter scriptA particular Automation Engine object type. in Job objects for Windows and UNIX and are dependent on the system variables UC_EXT_INTERPRETERS_WIN and UC_EXT_INTERPRETERS_UNIX respectively.

Syntax

:BEGIN_EXT_INT[ERPRETER ]
External Interpreter Script
:END_EXT_INT[EPRETER]

 

 

Value

Description/Format

External Interpreter Script

Contains the script to be used for the external interpreter. The script format is entirely dependent on the external interpreter called.

 

Comments

To be able to use the relevant script of an external interpreter in a Job objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task, you have to define the external interpreters using the system variables UC_EXT_INTERPRETERS_WINDOWS and UC_EXT_INTERPRETERS_UNIX respectively.

It is possible to use more than one external interpreter with this script statement. In that case, use them sequentially. Several external interpreter scripts (of the same or a different external interpreter type) may not cascade or overlap.

Scripts used in the Process Tab of a Job object (JOBS) will be overridden by the respective script entries in the parentThere are different ways of activating objects. The originator of an activation is referred to as the superordinate task (parent). See also: Child; Children Workflow object, in case the Job object is part of a workflowAn object of the Automation Engine that can include several executable objects and which runs them in a specified order. [Formerly called "ProcessFlow" and "JobPlan."].

Should you want to store return values or data in 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. defined variables, use the script statement :REGISTER_VARIABLE.

Examples

The following example shows a Perl script, which will not only print all file names, number of all files and number of all text files, but also store these values in the variables defined with :REGISTER_VARIABLE.

! Transfer resource file (perl library) from DB to agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host
:ATTACH_RES "STORE_LIB", "FUNC1", C


! Prepare resource file path string
:SET &cachepath# = STR_SUB("&$AGENT_RESOURCES_CLIENT#", "\", "\\")
:SET &funcfile# = STR_CAT(&cachepath#,"func.pl")


:BEGIN_EXT_INTERPRETER perl


# include transferred file
require "&funcfile#";


# Call functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… "myadd" of library file and print out result
my $val1 = 10;
my $val2 = myadd($val1);
print "calculated via lib function = $val2";


:END_EXT_INTERPRETER perl

 

See also:

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH