A system is a group of objects which together form a working set of software. This is used to make the task of specifying which objects belong at which locations both simple and flexible.
A system code has up to 30 alphanumeric characters.
When systems are used in Deltanji, each object must be defined as belonging to one or more systems. Each system is defined as being accepted at one or more locations.
Each variant of the object base may belong to a different set of systems. Note that the list of systems is held at the variant level, not the version level.
Each system has a list of locations that accept it. In order for an object to belong at a location, it must belong to at least one system which is accepted at that location. An object which is not associated with any system will only belong at locations which also have no systems.
Examples of how objects belong to systems:
|CORE||AA001/App, AA002/App ...|
|CUSTOMER||CUSTAAA/App, CUSTAAB/App ... LIB001/App, LIB002/App ...|
|SUPPLIER||SUPP001/App, SUPP002/App ... LIB001/App, LIB002/App ...|
Examples of how systems are assigned to locations:
|DEV||CORE, CUSTOMER, SUPPLIER|
In the example, the CORE system belongs at every location. The SUPPLIER and CUSTOMER systems each have their own live areas, but share the development area. Note that some objects, such as SUPP*, only belong to one system, whereas other objects, such as LIB*, belong to two systems, and can therefore be transferred to any location where either system belongs.
By linking each object to one or more systems and by associating each system with the location or locations where it will be installed, Deltanji is able to determine which objects belong in which locations.
Note: When a transfer function is used to transfer an object to a location or location list, Deltanji will only transfer the object to the location if it belongs to a system which is accepted by that location.