Creating a Remote Node
This article provides a procedure for creating a remote node. A remote node may be an Aspera FASP node (for example. a remote file watcher, remote file operation, or FASP transfer-controlled node), an SSH node (for example, an ffmpeg transcoding or remote execution), or an IP node (for example, Vantage transcoding from a SOAP API).
- Click Workflows in the top menu, then click Remote Nodes in the left navigation menu.
- Click the New Node button
-
In the Node Configuration dialog, enter the following information:
Field Details Required Name Name of node Must provide node name or node ID Node ID Must provide node ID or node name Comments No Address IP address of node Yes Secondary addresses Secondary IP addresses for node No Node type Allowable values: Aspera Fasp, SSH, IP, Aspera Orchestrator Yes Orch login Login for the orchestrator user. Yes, for Aspera Orchestrator only Orch API key Orchestrator user's API key. Yes, for Aspera Orchestrator only Orch web root Web root of Orchestrator node. If no value entered, default is aspera/orchestrator/ Yes, for Aspera Orchestrator only Node OS Node operating system No SSH Port SSH port of node Yes, if applicable TCP Port TCP port of node Yes, if applicable SSH/Fasp login Login string for SSH/Fasp No SSH/Fasp password Password for SSH/Fasp No Re-enter To confirm, re-enter the password above No Certificate location Directory path for certificate No Additional attributes Enter additional attributes No - Test the remote node settings by following the procedure in Testing a Remote Node.