Administer Operator Categories and Custom Operator Groups › Configuring Operator Categories › Configure Command Execution: Default Windows Command Execution Properties

Configure Command Execution: Default Windows Command Execution Properties

You can configure default run properties for the Windows commands.

Follow these steps:

1. Click the Configuration tab, select Domain, and click Lock.
2. Click the Modules tab, right-click Command Execution, and select Edit.
3. Select the Default Windows Command Execution Properties tab.
4. Enter the default shell command interpreter to use for the profile and for shell commands. For example:

   cmd.exe
   

   Note: Do not enter Command.exe.

5. Enter the name of the default shell script file to interpret before starting a user process for which no profile is specified.

   The command interpreter that the Shell program specifies interprets the profile file. The profile can contain any noninteractive command that the shell interpreter understands.

6. Specify the user credential defaults.
   1. Select one of the following values to specify that the Process operators use the selected option when user credentials are not specified:
      • (Default) Defaults to the user under which touchpoint is run.

        The Process operators use the user credentials under which the agent or Orchestrator process is running.

      • Defaults to the specified Default user.

        The Process operators use the user credentials that are configured as the Default user and Default password.

      • No default.

        The Process operators use the user credentials that are supplied at run time.

   2. Consider the implications of specifying defaults for user ID and password:
      • To prevent users from defining and starting processes through CA Process Automation to which they otherwise have no access, specify a user ID with only necessary permissions.
      • Leave the user ID and password blank to force users to enter those values when they start processes through CA Process Automation.
   3. If appropriate, enter the default shell account to use when starting user processes that lack a user name and a password.
   4. If appropriate, enter the password for the Shell user account.

      Note: Passwords that are part of the Command Execution configurations are protected and cannot be modified through a program, referenced, or passed to external methods.

   5. Reenter the Default password to confirm it.
7. Consider the implications of specifying defaults for user ID and password:
   • To prevent users from defining and starting processes through CA Process Automation to which they otherwise have no access, specify a user ID with only necessary permissions.
   • Leave the user ID and password blank to force users to enter those values when they start processes through CA Process Automation.
8. If appropriate, enter the default shell account to use when starting user processes that lack a user name and a password.
9. If appropriate, enter the password for the Shell user account.

   Note: Passwords that are part of the Command Execution configurations are protected and cannot be modified through a program, referenced, or passed to external methods.

10. Reenter the Default password to confirm it.
11. Indicate whether to load the user profile that is associated with the specified default user and password.
12. Click Save and Close.
13. Click Save.
14. Select Domain and click Unlock.

More information:

About Command Execution

Override Settings Inherited by a Category of Operators

Category Configuration and Operator Inheritance

Configuring Operator Categories