Managing Code on Other Machines

Deltanji offers several ways of managing code which is on machines other than the Deltanji server.

Native Networking

The Deltanji server accesses the remotely-hosted code using the networking capabilities of its host Caché or M environment or host operating system. For example, a physical address using M-format storage would specify a namespace whose database is remote and accessed using Caché's Enterprise Cache Protocol (ECP). Or bin-format storage would address a UNC path on a remote server, accessed using the Windows host's SMB networking. Note that if Deltanji works directly into namespaces that map to remote databases then all nodes typically need be running the same Caché version.

Proxying via the Deltanji Task Server

The Task Server is used to perform operations which for any reason cannot be done by the system which the user is connected to. Example uses of the task server include:

  • Users connect to Deltanji on a Unix system and need to move files on a Windows system.
  • Users manage code which needs to be compiled under a different Caché version from the one they are connected to. For example, Deltanji and the development locations could be hosted on Caché 2012.1 and transfer code to a 2013.2 test environment.

See here for information about installing Deltanji to operate in this way.

Non-Networked Locations: Deltanji Deploy

Deltanji Deploy is a stand-alone edition of Deltanji which is used for installing software on a machine which has no network connection to the Deltanji server. It is typically used for transferring code onto a production server which is at another site or which is firewalled from the development environment.