The script execution process

The script execution process involves defining permissions, managing scripts, and executing scripts.

Defining permissions

In this phase, an SA Administrator assigns Folder permissions, Client feature permissions, and Customer constraints to define the security boundaries across various user groups. The permissions determines the actions the users in a user group can perform with the SA Client.

See the SA Administer section for more information about defining security permissions.

Managing scripts

In this phase, a policy setter or an advanced system administrator performs script management tasks such as creating or importing scripts, editing script properties, exporting scripts, and deleting scripts. See Manage scripts for more information.

Executing scripts

In this phase, a system administrator executes server scripts directly on servers or server groups and OGFS scripts in the Global Shell. A system administrator can also execute scripts by adding the scripts to a software policy and then remediating the servers against the software policy. See Execute scripts for more information.

Types of scripts

In the SA Client, the Script Execution feature supports two main types of scripts: server scripts and OGFS scripts.

• The Server script allows you to execute scripts on UNIX and Windows servers managed by SA. The SA Client supports the following types of Server scripts for UNIX and Windows operating systems: UNIX/Linux shell, Windows batch (.BAT), Windows Visual Basic (VBScript), Windows PowerShell and Python (.py). Python scripts can be executed on both Unix and Windows.
• The OGFS scripts allows you to execute scripts in the Global Shell from the SA Client. You can specify the directory path in the OGFS to execute the scripts.

The server scripts are further classified to Saved Scripts, and Ad-hoc Scripts.

• Saved scripts are accessible to all the users, if they have the appropriate permissions. You are required to have the appropriate permissions to create, view, edit, and execute saved scripts.
• Ad-Hoc scripts are created or uploaded for one-time use and are not stored in Server Automation. Ad- Hoc scripts are created or uploaded and then immediately executed by a user and during this process, only this user has access to the scripts.

After you create a script and save it as a specific type of script in Server Automation, you cannot convert the script to the other type of script.

In the SA Client, you can specify to run a Sever script as a Super User or as a specified user.

• A Super User script allows you to execute the script as root on UNIX or Local System on Windows servers without entering a password. This applies to any user who has permission to execute the script, including users that do not have "Run Ad hoc & Saved Scripts As Super User" permission.
• If the script is not designated as a Super User Script, then you need to enter a user name and password to run the script unless you have the "Run Ad hoc & Saved Scripts As Super User" permission. You also require the appropriate permissions to manage and run Super User Server Scripts.

See the SA Administer section for information on the permissions required to run the Super User Server Scripts. All the OGFS scripts can only be executed as an SA User.