For Windows, specifies the extension that indicates the type of script. Select an option from the drop-down list or type an extension.
Specifies a subscript for the script to run. Click the (...) button to open the editor to enter the script to run.
The script must be a script that can run according to UNIX protocols. The first line of the script must indicate the full path of the shell that is used to interpret the script (for example, #!/bin/sh).
The script must be a script that can run according to the Windows extension specified in the Script extension field.
Note: See the Content Designer Guide for more information about using the CA Process Automation Code Editor.
Specifies a host system profile to use as the source to define parts of the processing context for the script (for example, /home/username/appli_1_profile).
If you do not specify a profile, the product uses the profile specified in the Command Execution category property settings. The product uses the user file that runs the process when the Command Execution category property settings do not specify a profile.
Specifies the path to a batch (.bat) file in Windows that sets environment variables for the process to run. The environment variable definitions in the batch file are in the following format:
SET SOME_ENV_VAR=/tmp/PAM.exe SET ANOTHER_ENV_VAR=/tmp/aaaa
The variable settings that the specified batch file defines are in addition to settings that are defined for the user profile that runs the process. If this option does not specify a file, the operator uses the settings that the Command Execution category Shell profile parameter value defines.
Specifies the working directory for the operator (for example, /home/user1). Typically, the working directory is the folder that contains the program file or related files that the program requires. The product looks in this directory for files that are specified without explicit paths.
If you do not specify a working directory, the default value is the home directory of the user account running the script.
Specifies the working directory for the operator. Typically, the working directory is the folder that contains the script file or related files that the script requires.
If you do not specify a working directory, the value defaults to the working directory of the user account that runs the script.
Specifies the user name under which to run the script. The expression must have run permissions on the file (for example, Process.Appli_1.User). If you leave the User ID field blank, the value defaults to the user that the Command Execution category configuration specifies.
User names (and their associated passwords) are typically stored in named dataset variables so users can update them centrally without changing process values.
Specifies the current password that is associated with the specified user ID. For example, the following input sets the password to the value of the Process variable Password:
Process.Password
The product typically evaluates the password against system information. However, where nonstandard security mechanisms are defined on the target host, administrators can deactivate this checking.
Because you specify the password as an expression, the text you enter must be visible. Avoid using literal strings and refer instead to password dataset variables.
Specifies parameters as in the following example to pass to the program:
/tmp/input_file /tmp/output_file
The product passes parameters to the process in the order that they are listed.
Program parameters are passed individually to the program on startup (that is, they are not concatenated with spaces between them). For example, entering the following expression on one line returns the single parameter “P1P2”:
P1 + P2
Entering the following expressions on two lines returns the two parameters “P1” and “P2”:
"P1" "P2"
Specifies the standard output file for the script. If you do not specify the full path, the Working directory parameter value defines the root directory for the path (for example, /tmp/trace.log).
The Command Execution category directs the stdout stream from the process to the specified file. You can specify the same file for both the standard error and standard out files. However, the product does not maintain a relative order for the different output types.
Specifies the standard error file for the script. If you do not specify the full path, the Working directory parameter value defines the root directory for the path (for example, /tmp/trace.err).
The Command Execution category directs the stderr stream from the process to the specified file. You can specify the same file for both the standard error and standard out files. However, the product does not maintain a relative order for the different output types.
Logs process output to the global log files.
Copies output of an operation (stdout and stderr) to an operator dataset variable (for example, scriptOutput).
Select this check box to have the product replace an existing log file that has the same name when it writes new output.
With the check box selected, the product replaces an existing file even when the following items are true:
If the check box is cleared, the product appends output to an existing error log file with the same name.
Select this check box to have the product replace an existing error file that has the same name when it writes new output.
With the check box selected, the product replaces an existing file even when the following items are true:
If the check box is cleared, the product appends output to an existing error file with the same name.
Loads the operating system profile (typically Windows) that is associated with the following items:
The OS user profile is typically used only to establish associations and similar Windows registry-based constructs for a specific user. Downloading user information from a Domain server carries a performance penalty.
If you select this option, the product ends the process when the process flow finishes.
|
Copyright © 2014 CA.
All rights reserved.
|
|