When the Deltanji task server is used to perform operations by proxy on a connected node, it is a Remote Address that directs the work to the target node.
M-format Remote Addresses
When the target node is running Caché or Ensemble a remote address is a string with four comma-separated pieces:
- The path that the remote node uses to access its local database where the M-format data is stored. Typically this is the path of the default global database of the namespace specified in piece 3 below. Make sure you specify this in the canonical form used by the remote node. For example, if the remote node runs on Windows then the path should be entirely lowercase.
- The name of the ECP connection across which Deltanji can reach the node responsible for the storage being addressed.
- The namespace (on the remote node) that is being addressed. Note that the node hosting Deltanji should not have a local namespace of this name defined to access that first-piece database as a remote database. If it does, task requests will be executed locally on the Deltanji node by the task server's "fast-track" mechanism. This defeats the original purpose of defining the address as a remote one.
- The path that the remote node uses to access its DELTANJI-LOCAL database, which is the default database for the DELTANJI-LOCAL namespace in which the task server process (%vczn) runs. Make sure you specify this in the canonical form used by the remote node. For example, if the remote node runs on Windows then the path should be entirely lowercase.
bin-format and text-format Remote Addresses
If the directory to which bin- or text-format storage is mapped is not directly reachable from the Deltanji node (e.g. it is not available using OS-level networking) then Deltanji can proxy its access via the task server of another node.
To do this, specify an address in the format protocol://@remoteNodePSA:localAddress where the three named elements have the following meanings:
- The string "remote" or "REMOTE"
- The physical location code assigned to an M-format remote address that access the node from where proxy access to the files is to occur. This physical location code can be obtained from the Physical Address property dialog. It typically has the format xyz$M
- The path to the target filsystem directory that the remote node is to access when proxying bin- or text-format access to files there.