Shell

Updated on 2022-02-22 GMT+08:00

View PDF

Functions

The Shell node is used to execute a shell script.

NOTE:

With EL expression #{Job.getNodeOutput()}, you can obtain the desired content (4000 characters at most and counted backwards) in the output of the shell script run by the Shell node.

Example:

To obtain <name>jack<name1> from a shell script (script name: shell_job1) output, enter the following EL expression:

#{StringUtil.substringBetween(Job.getNodeOutput("shell_job1"),"<name>","<name1>")}

Parameters

Table 1 and Table 2 describe the parameters of the Shell node.

**Table 1** Parameters of Shell nodes
Parameter	Mandatory	Description
SQL Statement or Script	Yes	You can select SQL statement or SQL script. SQL Statement In the SQL statement text box, enter the SQL statement to be executed. SQL Script Select a script to be executed. If the script is not created, create and develop the script by referring to Creating a Script and Developing a Shell Script. NOTE: If you select the SQL statement mode, the DLF cannot parse the parameters contained in the SQL statement.
Host Connection	Yes	Selects the host where a shell script is to be executed.
Script Parameter	No	Parameter transferred to the script when the shell script is executed. Parameters are separated by spaces. For example: a b c. The parameter must be referenced by the shell script. Otherwise, the parameter is invalid.
Interactive Input	No	Interactive information (passwords for example) provided during shell script execution. Interactive parameters are separated by carriage return characters. The shell script reads parameter values in sequence according to the interaction situation.
Node Name	Yes	Name of the node. Must consist of 1 to 128 characters and contain only letters, digits, underscores (_), hyphens (-), slashes (/), less-than signs (<), and greater-than signs (>).

**Table 2** Advanced parameters
Parameter	Mandatory	Description
Node Status Polling Interval (s)	Yes	Specifies how often the system check completeness of the node task. The value ranges from 1 to 60 seconds.
Max. Node Execution Duration	Yes	Execution timeout interval for the node. If retry is configured and the execution is not complete within the timeout interval, the node will not be retried and is set to the failed state.
Retry upon Failure	Yes	Indicates whether to re-execute a node task if its execution fails. Possible values: Yes: The node task will be re-executed, and the following parameters must be configured: Maximum Retries Retry Interval (seconds) No: The node task will not be re-executed. This is the default setting. NOTE: If Timeout Interval is configured for the node, the node will not be executed again after the execution times out. Instead, the node is set to the failure state.
Failure Policy	Yes	Operation that will be performed if the node task fails to be executed. Possible values: End the current job execution plan Go to the next job Suspend the current job execution plan Suspend execution plans of the current and subsequent nodes

Parent topic: Nodes

Previous topic: CSS

Next topic: RDS SQL

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot