ADMINISTER (Global Project Administration - Remote Administration)

Function:

Creates or opens a System Database (DB) to allow the administrator to administer a remote Location.

Description:

Before the administrator can use this command:

• The Location must have been created using the NEW LOC command, and its Location identifier must have been set.
  For example: Locid AAA

• The System DB of the new Location must be made Primary at the administering Location using the SYSTEMLOCATION command.
  For example: SYSTEMLOC /AAA PRIMARY AT /BBB

Here, /AAA is the identifier of the new Location, and /BBB is the identifier of the administering Location, the Location where the System DB for the Location will be Primary.

The NEWSYSTEM option is only available at the Hub. It creates a System DB for a new Location in the transfer area. (This is similar to the GENERATE LOCATION command.)

The System DB created is a copy of the Hub System DB without MDBs and with only a System User. The administrator at the Hub can then create Users and MDBs (as well as Teams and DBs) for the Location before it is set up.

The SYSTEM option is available at the administering Location, the Location where the System DB for the Location is Primary. This may be the Hub or another Satellite. This command will close the Local System DB and open the appropriate Satellite System DB. The DB will be opened with write access unless the READONLY keyword is used.

After the SYSTEM or NEWSYSTEM commands have been given, the administrator will be able to carry out administration tasks for the remote Location. To return to administering your own (current) Location, give the command ADMINISTER LOCAL. To return to administering the last System DB which was open, give the command ADMINISTER SAME.

Any Location may issue an ADMINISTER command for another other Location’s System DB. If the System DB is not Primary, then the System DB will be opened as read-only.

Once the administrator has selected a remote System DB, the administrator can give most AVEVA Administration commands, which will operate on the remote Location. In particular, the following commands can be used for housekeeping tasks on the remote System DB:
The Hub will not be allowed to REPLICATE the Project when it is administering a remote Location, since the wrong System DB will be replicated. However, REPLICATE SYSTEM commands (which generate macros to replicate the Project structure) will still be valid.

The administered Location will still be able to lock or isolate the Project locally. It will also be able to administer its Primary constructor DBs by using the REMOTE <loc> command, where <loc> is its own Location identifier, followed by one of the normal commands, listed below.
Reconfiguration will also be possible provided that suitable DBs are Primary at the Location.

Examples:

Command Syntax:

Querying: