CSS

Node Name

Yes

Name of a node. The name must contain 1 to 128 characters, including only letters, numbers, underscores (_), hyphens (-), slashes (/), less-than signs (<), and greater-than signs (>).

Cluster or Data Connection

Yes

Select Cluster or Connection.

If you want to enable the security mode for CSS clusters, select Connection.

CloudSearch Cluster

Yes

This parameter is required when you select Cluster for Cluster or Data Connection.

Connection to CloudSearch. A CloudSearch cluster has been created in CloudService. Currently, only clusters of version 5.5.1 is supported.

CDM Cluster Name

Yes

This parameter is required when you select Cluster for Cluster or Data Connection.

Name of the selected CDM cluster. The CDM cluster functions as a proxy to forward requests.

If there are no CDM clusters available in the drop-down list, create one on the CDM console.

Data Connection

Yes

This parameter is required when you select Connection for Cluster or Data Connection.

Select a data connection.

Request Type

Yes

Possible values:

• GET
• POST
• PUT
• HEAD
• DELETE

Request Parameter

No

Parameter of the request.

For example, to query the dlfdata mapping type in the dlf_search index, set this parameter to:

/dlf_search/dlfdata/_search

Request Body

No

The request body is in JSON format.

This parameter is mandatory when Request Type is POST, PUT, or HEAD.

CloudSearch Output Path

No

Path where output data is to be stored.

Node Status Polling Interval (s)

Yes

How often the system check completeness of the node. 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 be executed again.

Retry upon Failure

Yes

Whether to re-execute a node if it fails to be executed. Possible values:

• Yes: The node will be re-executed, and the following parameters must be configured:
  • Retry upon Timeout
  • Maximum Retries
  • Retry Interval (seconds)
• No: The node will not be re-executed. This is the default setting.
  NOTE:

  If retry is configured for a job node and the timeout duration is configured, the system allows you to retry a node when the node execution times out.

  If a node is not re-executed when it fails upon timeout, you can go to the Default Configuration page to modify this policy.

  Retry upon Timeout is displayed only when Retry upon Failure is set to Yes.

Policy for Handling Subsequent Nodes If the Current Node Fails

Yes

Operation that will be performed if the node fails to be executed. Possible values:

• Suspend execution plans of the subsequent nodes: stops running subsequent nodes. The job instance status is Failed.
• End the current job execution plan: stops running the current job. The job instance status is Failed.
• Go to the next node: ignores the execution failure of the current node. The job instance status is Failure ignored.
• Suspend the current job execution plan: If the current job instance is in abnormal state, the subsequent nodes of this node and the subsequent job instances that depend on the current job are in waiting state.

Enable Dry Run

No

If you select this option, the node will not be executed, and a success message will be returned.

Task Groups

No

Select a task group. If you select a task group, you can control the maximum number of concurrent nodes in the task group in a fine-grained manner in scenarios where a job contains multiple nodes, a data patching task is ongoing, or a job is rerunning.