Until now the recommended configuration of namespaces, remote databases and local databases on a task-served node has been as follows:

• Local database DELTANJI-LOCAL or VCM-LOCAL.
• Namespace DELTANJI-LOCAL or VCM-LOCAL that uses the above database as its default database for globals and routines.
• Remote database DELTANJI or VCM that accesses the central DELTANJI or VCM database on the Deltanji server over an ECP connection.
• Namespace DELTANJI or VCM that uses the above central database as its default database for globals and routines.
• Mappings directing all Deltanji-managed namespaces to access most ^%vc* globals over ECP in the DELTANJI or VCM central database, and to access the %vc* routines and VCmStudio.* classes from the DELTANJI-LOCAL or VCM-LOCAL local database.

In Portal, the configuration table of namespaces typically looks like this:



If this node is upgraded to a later version of its InterSystems product than the version hosting the central Deltanji server, and the later version requires an upgrade to its class dictionaries, then the InterSystems utilities may upgrade the dictionary in the remotely-hosted DELTANJI or VCM database and render it unusable by its local host, the Deltanji server.

For historical reasons the task-served nodes at some sites use different naming conventions for their Deltanji-related namespaces and databases. However all task-served nodes will be running a background process that idles (hangs) in the routine named %vczn in the DELTANJI-LOCAL namespace or equivalent.