Configuring Deltanji Deploy
Configuring the Deltanji Server
1. Set up a single-version sequential file location for the objects which are to be transferred to the non-networked machine where Deltanji Deploy will be used to install them. All components (i.e. '*') must be mapped to one physical location with a storage format of 'F'. There should be no additional mappings for binary and text files. Typically this location holds Deltanji's record of what has 'gone live' (see transfer route activation in the next step), so you should set the 'Browse fileset contents?' option to 'No' on the location definition. If you don't do this a user-initiated browse of an outbound fileset will clear the location's list of objects and repopulate it with only the objects in the browsed fileset.
Note: In order for Deltanji Deploy to function, it is essential that the outbound sequential file location on the main Deltanji server has the same location name as the target installation location on the Deltanji Deploy instance. For example, if the Deltanji Deploy target M-format location is named LIVE then the outbound F-format location on Deltanji must also be named LIVE.
2. Define a route to transfer the objects to this location. If the location is to act as Deltanji's record of every object that has ever gone live, give the route a '+%TO' activation. Generally this route would not set a master location.
If there is more than one Deltanji Deploy installation location or more than one Deltanji Deploy machine, a separate location is required for each one. However, one physical address (i.e. directory) can be used for files destined for more than one location. By default Deltanji Deploy's install function will not allow a transfer file to be installed into a location for which it is not intended.
Configuring the Deltanji Deploy Machine
1. Define a multi-version sequential location for the objects which are awaiting installation. This is where files arrive from the Deltanji server, so you might call it 'Inbox'. This location must map all components (i.e. '*') to one physical address (the inbox folder) with a storage format of 'F'.
2. Define a location managing the place where the objects are to be installed, for example the LIVE namespace. This location must have the same location name as the corresponding sequential file location on the main Deltanji server. If there is more than one target destination, a separate location is required for each one.
3. Define a route to transfer the objects from the sequential file location (e.g. 'Inbox') to the installation location (e.g. 'LIVE'). This route must have a function code of 'XFER'. It should activate '-%FROM,+%TO' but should not set master.
4. If the automated hot backups and rollback functions are to be used, create a multi-version sequential location for the backup copy of the objects which are being replaced. You might call this location 'Backups'. It should map all components to F-format storage in a filesystem directory that will store the backups. Two transfer routes are required, both with a function code of 'XFER'. The first is a route from the installation location (e.g. 'LIVE') to the backup location (e.g. 'Backups'), performing no activations and not setting master. This route enables creation of a backup copy of each existing object (earlier version) during installation. The second route is from the backup location (e.g. 'Backups') to the installation location (e.g. 'LIVE'). It should activate '-%FROM,+%TO' but leave master unchanged. This route enables the backed-up copies to be restored using Deltanji Deploy's Rollback option in its terminal mode interface. If you also want to permit rollback using this route in Deltanji Deploy's browser UI, go to the 'Advanced' tab of the route definition dialog and clear the checkbox captioned 'Enforce normal version sequencing rules?'.
5. Set up the installation parameters using the 'Install' option in the terminal-mode
Setup utility (
do ^%vcsetup). This option must be run in the namespace of the location where the objects are
to be installed. If there is more than one location, switch to each one's namespace
in turn and run the option. If you are using hot backups, also enter the name of the
backup location in the appropriate field.