Once the Path variable includes the folder, the user can run AVEVA Administration by typing Admin at a command prompt.
4.2 Set the License File Location
Before the user can use AVEVA Administration, the AVEVA Licensing System must be set up and connected, refer to the AVEVA Licensing System Guide. A license file should be requested from AVEVA Customer Services.
4.3 Environment Variables
AVEVA Administration uses Windows Environment variables to locate folders containing AVEVA Administration system files and users project data. This allows the user to locate these folders anywhere on the file system. The default location for AVEVA Administration system files is C:\Program Files (x86)\AVEVA\Administrationxxxx, unless the default location was changed during the installation.
AVEVA Administration is supplied with a file evars.bat which sets default values for the environment variables so that they point to the folder structure as installed. It also sets the PATH variable to include the AVEVA_DESIGN_EXE folder containing AVEVA Administration executables.
The user may need to modify this file to reflect the folder structure of their own installation.
The following is a list of the variables the user may need to reset, with a brief description of each one and the default setting.
Note: all environment variables must be entered in UPPERCASE.
Search Paths of Folders Containing Spaces
Search paths of folders can contain spaces, by using a semicolon as the separator between folders, for example:
set PMLUI=C:\Local AVEVA Administration\Appware;M:\Project AVEVA Administration\Appware; a:\Company AVEVA Administration\Appware Note: that in order to define an environment variable that contains just one item including
spaces, it must explicitly include a final semicolon. For example:
set PMLUI=C:\Local AVEVA Administration\Appware;
Length of Search Path Environment Variable
The lengths of AVEVA Administration search path environment variables can be up to a maximum of 5120 characters.
Recursive Expansion of Environment Variables
An environment variable defining a search path can itself contain references to other environment variables. For example:
set MPATH=%ROOT%\Standard Version;%ROOT%\Update Version set ROOT=C:\Program Files\AVEVA; (note final semicolon)
files.
User Environment Variables
The following environment variables refer to the location of users AVEVA Administration folders. Users must have write permission to these folders.
Project Environment Variables
For each AVEVA Administration project, the following environment variables must be set.
For example, for a project ABC:
AVEVA_DESIGN_EXE Executable folder
C:\Program Files (x86)\AVEVA\Administrationxxx PMLUI Application User Interface folder (PML 1)
C:\Program Files (x86)\AVEVA\Administrationxxxx\PMLUI PMLLIB Application User Interface folder (PML 2)
C:\Program Files (x86)\AVEVA\Administrationxxxx\PMLLIB AVEVA_DESIGN_DFLTS Applications defaults folder
C:\Users\Public\Documents\AVEVA\Administration\Data1.4.0\DFLTS\
AVEVA_DESIGN_WORK Temporary AVEVA Administration work file folder
AVEVA_DESIGN_USER Application Users save/restore setup area (or the users 'home' folder)
AVEVA_DESIGN_REP_DIR AVEVA Administration Applicationware Report Input and Output folder.
C:\Program Files(x86)\AVEVA\Administrationxx\PMLUI\reports AVEVA_DESIGN_DFLTS Applications defaults folder.
ABC000 Project database folder
ABCISO Project ISODRAFT options folder
Set Up the Windows Environment
4.4 Customise AVEVA Administration Start-Up
There is a batch (.bat) file supplied in C:\Program Files (x86)\AVEVA\Administrationxxxx called Admin.bat which allows entry into AVEVA Administration.
The user can run AVEVA Administration using this batch file in any of the following ways:
• Use the shortcut in the Windows Start menu, Start > All Programs > AVEVA >
Manage > AVEVA Administrationxxxx
• The user can create a shortcut on their desktop to run their batch file. With the cursor in the desktop area, right-click and select New > Shortcut. This shows a sequence of dialogs to help the user create the shortcut. Type in the location of Admin.bat, for example:
C:\Program Files (x86)\AVEVA\Administrationxxx\Admin.bat then click Next and give the shortcut a name.
click Finish.
The user should now be able to double-click on the shortcut icon to enter AVEVA Administration.
Note: Shortcuts can also be created during installation by checking the Create Start Menu Shortcuts check box on the Initial Configuration screen.
• If the user has C:\Program Files (x86)\AVEVA\Administrationxxx\ (the path name for the Admin.bat file) in their PATH environment variable, just type Admin in a command window to execute the batch file.
• Otherwise, navigate to the folder where the batch file is stored and type Admin or Admin.bat.
4.4.1 Create User Batch File to Run AVEVA Administration
The user can set up their own batch files to run AVEVA Administration. For example, the user may want to run design checking utilities every night, or update batches of drawings overnight.
Begin by creating a batch file, for example, runAVEVAAdministrationmacro.bat.
Type the following line into this file:
C:\Program Files
(x86)\AVEVA\Administrationxxxx\admin.bat TTY APS SYSTEM/XXXXXX /ALL
$M/mymacrofile Where:
• TTY tells AVEVA Administration not to start the AVEVA Administration GUI. This gives command line only operation.
• APS is the project name.
• SYSTEM/XXXXXX is the AVEVA Administration username/password to be used when running the command macro
• /ALL selects the required MDB
• mymacrofile is the pathname of an AVEVA Administration command macro, containing the commands that the user wants to execute in AVEVA Administration.
In this example, running runAVEVAAdministrationmacro.bat will enter AVEVA Administration in project APS, as user SYSTEM/XXXXXX, in MDB /ALL, and run the AVEVA Administration
and can be used to make an AVEVA Administration script wait for AVEVA Administration to complete before continuing.
PDMSWait uses Windows facilities to wait for an event triggered by PDMSConsole when AVEVA E3D™ finishes. Because the user can be running more than one AVEVA E3D™
session on any one computer, both PDMSWait and PDMSConsole look for an environment variable PDMS_CONSOLE_IDENTIFIER before doing this. The user can set PDMS_CONSOLE_IDENTIFIER to any unique string. In a .bat file the user can use the
%RANDOM% or %TIME% values provided by Windows; in a Perl script, the user can use the process number, accessible as $$.
This will start AVEVA Administration, then wait until it has finished before resuming the script.
Example: