Initialising a New Location

AVEVA Global User Guide

Setting up a Global Project : Initialising a New Location

or select Project>Initialise Location from the main ADMIN menu bar.

To check that the location has been initialised successfully. At command level, give the commands:


/GLOC	Make the location (in this example, /GLOC) the current element.
GETWORK	Refresh view of System database. Give this command before seeing changes made to the Global database by the Global daemon.
Q ATT	Query the attributes of the location: LINIT will be TRUE if the location has been initialised.

or select Query > List > Locations from the main ADMIN menu.

Now exit from ADMIN and re-enter it.

Note:

The Hub Administrator will have to GETWORK to see the initialisation as complete, because the daemon (which is effectively another ADMIN user) will have written to the Global database.

When the Satellite is initialised:

•

The Satellite Administrator can start to create local Admin elements in the usual way.

•

The System database is propagated from its primary location to all other locations automatically. Subsequently, any changes that an Administrator makes to the System database will also be propagated to all other locations automatically. So if a Satellite’s System database is primary at a remote location (not at the Satellite itself), once any changes are completed by a remote Administrator, they will be propagated automatically from the remote location back to the Satellite, and to all other locations.

•

The Hub Administrator can now make databases primary at the Satellite. Refer to Changing the Primary Location.

•

An Administrator, either at the Hub or at the Satellite, needs to set up Update events, which control when the daemons look for databases that need updating. Refer to Creating Update Events.

If looking at the Admin Elements windows for the Satellite, notice that the buttons at the bottom of the Teams and Databases versions are inactive: these tasks cannot be carried out at a Satellite.