The UC_EXT_INTERPRETERS_WINDOWS and UC_EXT_INTERPRETERS_UNIX system variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. objects are used to define external interpreters for use with the respective 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, they are available for Windows and UNIX agents respectively.
These rules apply to Windows and UNIX respectively.
Key | Description |
---|---|
Key |
Interpreter identifier, unique within the Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. system. This key is used to specify an external interpreter section. |
Value1 | Desired file extension of the scriptA particular Automation Engine object type. file passed to the external interpreter |
Value2 |
Variant 1 - single line: Use this Variant to call the external interpreter stating only parameters. Variant 2 - multi-line: The static Variable objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task may contain several lines and can be edited in two ways: In the Variable Tab you may edit the cell in the value column directly or use the cell editor of the static Variable object The value column cells should only contain commands that are processed each time this interpreter is called. In all other cases you should place the commands in the jobAn Automation Engine object type for a process that runs on a target system.'s script. |
The UC_EXT_INTERPRETERS_WINDOWS and UC_EXT_INTERPRETERS_UNIX variable objects should be used in the system 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. Thus the external interpreters will be available to all users in all clients of the Automation Engine system.
The system variable object UC_SHELL_UNIX lists all registeredThis is the status of a task that runs within a group and is waiting for its start. shells of an operating system. It should not be used for registering external interpreters. UC_SHELL_UNIX is delivered together with the Automation Engine software and maintained by the system administrator in the system client 0000.
In Job (JOBS) objects for Windows and UNIX you may use an external interpreter script in the Process tab. To be able to use such scripts, the external interpreters have to be registered first by using these variables.
The Storage object is another object directly affected by this variable. As the files contained in the Storage object may be used in Windows and UNIX agents, you have to register the external interpreters using UC_EXT_INTERPRETERS_WINDOWS / UC_EXT_INTERPRETERS_UNIX.
Key | Value 1 | Value 2 | Value 3 | Value 4 |
---|---|---|---|---|
PERL1 |
.pl |
perl.exe <FILE> -k | ||
PERL2 | .pl | perl.exe <FILE> | ||
GROOVY | .groovy | groovy.exe <FILE> |
The term "<FILE>" will be replaced by the generated script file. This term is fixed and has to be upper case.
For PERL1 the following call would be the result of using the example values above:
perl myprog.pl -k
See Also
Variable Tab (Cell configuration)
Configure Include Objects for External Interpreter Calls
How to use an External Interpreter
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |