Configuring Orchestration CLI

The extension for Orchestration CLI is bundled with the product. If required, you can download it as a stand-alone feature also.

Before you begin

You must have created an API key to authenticate the command line. For more information, see Enhancing authentication using API Keys.

About this task

After you downloaded the required files for HCL Workload Automation, you need to configure the config.yaml extension file by any source code editor. The config.yaml file contains mandatory and optional fields. To create the config.yaml file, you must run the Orchestration CLI file using the command prompt.

Procedure

  1. Navigate to the directory where you have downloaded the files for Orchestration CLI.
  2. Run Orchestration CLI from the command line.
    Note: For windows, you can also use powershell to run the file.
  3. Type ocli plan as command, and then press enter to create the config.yaml file.

    In Windows operating systems, the config.yaml file is created at c:\Users\<user_name>\.OCLI.

    In Unix operating systems, the config.yaml file is created at home/<user_name>/.OCLI.

  4. Open the config.yaml file by using any source code editor.
  5. Perform the following actions in the config.yaml file.

    You must enter valid details for the mandatory fields. If required, you can also specify the optional fields.

    Table 1. Mandatory fields
    Option Action
    connection
    host Enter the host name or IP address of the remote engine that you want to use.
    port Enter the port number of the remote engine that you want to connect.
    jwt Specify the JWT for authentication. For more information, see Authenticating the command line client using API Keys.
    Table 2. Optional fields
    Option Actions
    lang You can use this option to specify any one of the supported languages. The following languages are supported in Orchestration CLI:
    • Brazilian Portuguese (pt_BR)
    • English (EN, the default value)
    • French (FR)
    • German (DE)
    • Italian (IT)
    • Japanese (JA)
    • Korean (KO)
    • Simplified Chinese (zh_CN)
    • Spanish (ES)
    • Traditional Chinese (zh_TW)
    Important: You must ensure that the recent version of powershell is installed on Windows operating system to view the content in the selected language.
    dateformat You can ignore this option. The date format is specific to the commands you run on Orchestration CLI.
    current_folder Specify the path to any folder that will be taken as an absolute path, when you run the commands.
    Note: Use the base folder of the Orchestration CLI.

    Define the folder in the config.yaml in the "current_folder" parameter.

    Once this change has been made in all the paths of the commands that starts, the "current_folder" will be inserted in those that do not start with the "/" character.

    For more information, see Base folder of the Orchestration CLI
    default workstation The option is only applicable for model commands. You can ignore this option.
    local_timezone You can use this option to specify the timezone. The supported formats are:
    • The extended form "area/city". For example, "America/New_York” for EST.
    • The 3 character notation, for example ECT (European Central Time).
    logging
    level You can use this option to filter the log messages that are retrieved in the ocli.log file. When you set a value, all the messages equal to that severity and above are sorted. The default value is info. To view the file, navigate to C:\Users\<user_name>\.OCLI\logs. You can enter any one of the following message types. The message types are listed from lower to higher severity.
    • info:

      Any additional information which are not tied to the current task or action.

    • trace:

      Messages that provides information about the application flow.

    • debug:

      Informational messages that are useful to troubleshoot the application.

    • error:

      Messages related to errors or critical failures that may block the users to proceed further until the issue is resolved.

    • warning:

      Messages related to user actions that will have an unexpected or unwanted consequences.

    • fatal:

      Messages related to errors that will cause the Orchestration CLI to close without saving any data.

    • panic:

      Messages related to errors that will cause the Orchestration CLI to close without saving any data. The error is similar to a fatal error, except that the application is closed differently.
    redirect_to You can use this option to change the location of the log file.
    file_size You can specify the maximum size of the log file in Mega Bytes(MB).
    backup_files You can specify the number of log files that you want to save.
    connection
    contextroot You can specify the endpoint that connects to the server. The default value is /,/twsd/cli.
    protocol Enter the protocol of the remote engine that you use to connect.
    insecure Enter true, to ignore the host name error on SSL certificate. The default value is false.
    proxy Specify the proxy IP address, if you are using a proxy server.
    proxyport Specify the port of the proxy server.
    proxyuser Provide the user name of the proxy account, if authentication is required.
    proxypassword Provide the proxy account password.
    timeout You can use this option to specify the maximum time in milliseconds to display the timeout error message. The default value is 3600 milliseconds.
    show_warnings If you want receive any warnings when there is an internet connection failure, set the option to true.
    compatibility
    show_copyright_header If you want the copyright content to be displayed when you run a command, set the option to true.
  6. Save the config.yaml file.

Results

You have successfully configured Orchestration CLI.
Note: The config.yaml file is not encrypted. It may contain sensitive data such as the API Key of a specific user or a group of users. Ensure this file is protected in your OS.

What to do next

You can run the commands using Orchestration CLI to accomplish specific results. For more information, see Running commands from Orchestration CLI.