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. The install function is designed to be as automated as possible so that the risk of mistakes is minimized.

Deltanji Deploy is a single-user version with limited functionality. There are no systems and no change requests.

Using Deltanji Deploy

To start Deltanji Deploy:

do ^%vcl

Software is transferred from the Deltanji server to the Deltanji Deploy machine. The procedure has 3 steps:

  1. The main Deltanji server transfers the objects destined for the Deltanji Deploy machine to a local sequential file location.

    The transfer on the main Deltanji server creates a series of files with the same name but different extensions. One of the files has an extension of $. This is the control file and it contains all the information which Deltanji Deploy requires about the objects and the locations which they belong in. There is also one file for each type of component which is to be installed. The extensions for these are the component type code.

  2. The user manually copies the files to a sequential file location on the Deltanji Deploy machine using any available transfer protocol.
  3. Deltanji Deploy reads the sequential files and installs the objects from this sequential file location into the installation location.

Installation Mode

A Deltanji Deploy machine can be configured to install the objects in one of three different modes.

  1. An operator can use the interactive 'Install' option from the menu.
  2. A non-interactive batch job can be run at an appointed time. This could be run, for example, when a system re-starts after a nightly shutdown for backup.
  3. A background install daemon can be set up which is running all the time and will install the objects non-interactively when they are placed in the sequential file location.

Hot Backups and Rollback

The install function includes an option for a hot backup of the objects which are being replaced. This means that, when a new version of an object is installed, the displaced version will be transferred from the 'to location' into the designated backup location. If the new version turns out to have a problem, the old version of the object can be quickly re-instated from the hot backup location, using the 'Rollback' option. This is particularly useful for a live system.


To run the terminal-mode application which allows you to configure Deltanji Deploy for a particulare namespace:

do ^%vcsetup