Cross-tenant collaboration nodes are used to associate nodes from different tenants. Cross-tenant collaboration nodes are classified into sender nodes and receiver nodes.
A sender node and its receiver node must use the same CRON expression. You can find the CRON expression in the Schedule section after you click Properties on the right of the node editing page.
Create a cross-tenant collaboration node
- Log on to the DataWorks console. In the left-side navigation pane, click Workspaces. On the Workspaces page, find the target workspace and click Data Analytics in the Actions column.
- Move the pointer over the icon and choose
You can also click a workflow, right-click General, and then choose .
- In the Create Node dialog box, configure Node Name and Location and click Commit.
Note The node name must be 1 to 128 characters in length.
- On the Cross-Tenant Collaboration page, set the relevant parameters.
Parameter Description Type The type of the cross-tenant collaboration node. Two node types are available, which are Sender and Receiver. Location The path of the cross-tenant collaboration node. The node path cannot be modified. Collaborative Workspaces The workspace name and Alibaba Cloud account of the peer node. This example sets the node type to Sender. Therefore, you need to enter the workspace name and Alibaba Cloud account of the receiver node.
- After the sender node is created, follow the same procedure to create the receiver
node under the Alibaba Cloud account and workspace to which the receiver node belongs.
Set the node type to Receiver. Afterward, the information about available sender nodes appears. You must also set Timeout. This parameter indicates the timeout period of the receiver node after it starts running.
The sender node first sends a message to the message center. After the message is delivered, the status of the sender node is set to successful. The receiver node continuously pulls messages from the message center. If a message is received within the timeout period, the status of the receiver node is set to successful.
If the receiver node does not receive any messages within the timeout period, the receiver node fails. The lifecycle of a message is 24 hours.
Assume that an auto triggered instance was run on October 8, 2018. A message indicating the completion of the instance was then sent to the message center. If you create a retroactive instance for the receiver node with the data timestamp set to October 7, 2018, the status of the generated receiver node instance is set to successful.
- After the configuration is completed, save and commit the node.