Using the admind command

The Global daemon is started by using the admindWCF command, for the admindWCF command to run correctly environment variables must be set either in a batch file or manually in a command line window.

Two sample batch files are supplied in the default install folder; singleds and multids. However these batch files must also be modified to work with your project.

The following environment variables must set in the supplied batch files or your own batch file before the daemon can be started using the admind command:

• Set AVEVA_DESIGN_EXE to the folder where Global is installed.

• Set AVEVA_DESIGN_WORK to point to c:\temp, or a valid empty folder. This is necessary for performing a remote Data integrity check.

• Set the project variables, for example:

  ABC000, ABCISO, ABCMAC, and ABCPIC for AVEVA Plant

  ABCDRG,ABCMAR,ABCMAC, ABCDIA, ABCSTE, ABCTPL for AVEVA Marine.

• Make sure that the AVEVA_DESIGN_EXE folder is included in the PATH variable setting.

• Set USERNAME to SYSTEM

  Note:
  The Global daemon is dependant on a valid AVEVA License. For more information relating to licensing refer to the AVEVA Licensing System (ALS) guide.

• If transfer of other data files is required (refer to Transfer of Other Data), then import (IMPORT) and export variables (EXP_XYZ for export to location XYZ) must also be set up.

  Note:
  If the project is using Areas, these will also need to be set along with the other project variables.
  This command must be run from a directory located on the local machine for the service to install. If it is executed from a mapped drive or UNC pathname then the service will not start when requested.

• Give the command to start the daemon.

  Example:
  set aveva_design_exe=C:\Program Files(x86)\AVEVA\GlobalServer3.3; set aveva_design_work=c:\temp set projects_dir=C:\Users\Public\Documents\AVEVA\Projects call %projects_dir%AvevaPlantSample\evarsAvevaPlantSample.bat "C:\Program Files (x86)\AVEVA\GlobalServer3.3\admindwcf" start APS

When the Ready message is visible, the daemon is running.

For more information about the Global daemon, and what to do about possible problems, refer to Global Daemon Messages.

Check whether the daemon is running by starting up the Task Manager and selecting the Processes tab. Look for the process named adminWCF.exe.

It is possible to set up tracing and login when the daemon is started, refer to Daemon Diagnostics for further information.

If required to stop the Global daemon manually, give the following command outside the base product:

base product install path\admindwcf stop prj

where prj is the project code. For example: C:\Program Files (x86)\AVEVA\Glo balServer3.3\admindwcf stop APS

Although the daemon can be started manually from the command line, there is a disadvantage that the daemon will stop when you log out.

The daemon can be run as a background service. This allows the program to persist after a user logs out; and to start automatically when a machine is restarted. This process is detailed in the following sections.

When the daemon is run as a service, it must be run on a file server.