Knowledge Base > Automation Engine and Target Systems > UNIX > Shell and Shell Options

Shell and Shell Options

A shell under which a particular jobAn Automation Engine object type for a process that runs on a target system. should run can be specified in the Unix tab which is available for Unix jobs. Options can also be specified for calling this Shell. If no shell is defined, the default shell from the passwd file is used.

Shells selected in the Unix tab are maintained in the variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. UC_SHELL_UNIX of 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. The following shells are available by default:

You can add additional shells in the variable UC_SHELL_UNIX. Additionally, a shell-specific scriptA particular Automation Engine object type. line must be inserted in the Include "TRAILER.UNIX". The following format should be used:

##UC4[Shell]Shell specific command

Determining the Shell Path

  1. If a path string has been defined in the configuration file (section STARTCMD, parameter "shell_pfad"), this path is used.
    Format Path String: <Path name1>[:<Path name2>]...
    Format Path name: /<dir1>[/<dir2>]...

  2. If the parameter "shell_pfad" has not been specified, the environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications. variable PATH is read and used.

  3. If no PATH environment variable is available, the "/bin" directory is used.

The shell file name is composed of the retrieved shell path and the selected shell (Host Attributes tab) and checked for the availability of the right to execute. If this file must not be executed or cannot be found, an information message is output. The 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.'s default shell which has been defined in the passwd file is then used. If no shell has been specified in the passwd file, the bourne shell from "/bin/sh" is used.

Determining Shell Options

If shell options have been specified in the Host Attributes tab, these are used.

Shell options may be defined in the configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. file (section STARTCMD, variables "Bourne_Shell_Opt", "Korn_Shell_Opt" and "C_Shell_Opt")

As of version 11 the options will be left empty, if you do not select one of the shells mentioned above and also do not enter a value in the options field.

 


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

Copyright © 2016 Automic Software GmbH