Scribd
Upload
992 views15 pages

Aveva E3D Migration Training Manual - Administrators-1

Aveva E3D Migration Training Manual

Uploaded by

Gangatharen Nackeeran
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
992 views15 pages

Aveva E3D Migration Training Manual - Administrators-1

Aveva E3D Migration Training Manual

Uploaded by

Gangatharen Nackeeran
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 15
Peer CHAPTER 1 This chapter will explain the new configuration for E3D 4.4 Astandard installation When AVEVA Everything3D™™ (E3D"™) is installed using the default options, there will be a single shortcut available on the desktop. This will start E3D, displaying the new login screen (after displaying the new animated splash screen), AVN Sco Ta © Copyright 2012 to current year. 7 www.aveva.com AVEVA Solutions Limited and its subsidiaries. Al rights reserved. AVEVA EverythingaD (1.1) For Administrators ~ TM-XXXX There are supporting products shortcuts installed into the start menu: Bi Aveva i Manage [al AVEVA Administration 1.1.0 [di] AVEVA Catalogue1.0 [dl Project Creation Wizard 1.1.0 AVEVA Administration provides access to Admin and Lexicon. AVEVA Catalogue provides access to Paragon and Propcon. NW TTS © Copyright 2012 to current year. 8 www.aveva.com AVEVA Solutions Limited and its subsidiaries, Al rights reserved. FARRAR RAR RRA RRR AAR RAR AR AR ARR AAR AAA. AVEVA Everything3D (1.1) For Administrators TM-1811 The shortcut starts C:\Program Files (x86)AVEVA\Plant\E3D1.1.0\mon.exe, supplying it with a number of arguments. ‘The target of the shortcut is: “C:\Program Files (x86)\AVEVA\PIant\E3D1.1.0\mon.exe" PROD 3I (x86)\AVEVA\Plant\E3D1.1.0\launch. init” :\Program Files Where the PROD 30 is the product to be started and init “filename” is the initialisation file. 7 G2 short stats mon exe, but supe diferent produc argument ¢ elas Deuces AVEVA Everything3D PROD 3D AVEVA PROD ADMIN Administration AVEVA Catalogue PROD CATALOGUE Sian ene: AVEVA Everything3D —%SystemRoot%\Installer(8E1A0ED1-E376-4DB6-94CA- 924D5AF2F40B)\avevae3d ico AVEVA %SystemRoot%\installer\(8E1AQED 1-£376-4DB6-04CA- Administration 924D5AF2F40B)\avevamanage.ico ‘AVEVA Catalogue %SystemRoot%\installer\(8E 1ADED 1-£376-4DB6-94CA- 924D5AF2F40B)\avevamanage ico ‘These shortcuts can be updated to: ‘* A different installation location (ie. the installation directory of mon.exe). ‘© Start a different product. + Start a different initialisation fle to set a different environment. © Copyright 2012 to current year. 9 www.aveva.com AVEVA Solutions Limited and its subsidiaries, All rights reserved, AVEVA Everything3D (1.1) For Administrators — TM-XXXX. isation files as ee Init 7 - The alsa le upped to mon.exe as an argument to define the envionment for 2D ‘The default initialisation file is: cAProgram File (86)AVEVA'Plant301.1.0aunch.nit Itis equivalent to pdms.bat for AVEVA PDMS, or marine.bat for AVEVA Marine. There is also a launch.bat available for compatibility. The logic of the file is as follows: © Set the environment variable “aveva_design_installed_dir” Ls, ‘peyes f + Call "%aveva_design_installed_dirtbevars.ini cus tori oon * Define the supported AutoCAD versions: i aay ‘+ Set the compatibility environment variables eae ‘© Set the environment variable “aveva_design_exe” ‘* Set the environment variable “aveva_design_installed_dir” iables 4.3 Environment The file Defined within the file evars.init, the following locations are the defaults: Sener AVEVA_ECHOFILE Location’ Satemp%\everything3d_init.log aveva_design installed ‘Dummy argument — indictated by %0; will be the location of mon.exe aveva_design_exe ‘%aveva_design_installed_dir% pmillib ‘%aveva_design_exe%pmilib\ pmiui *haveva_design_exe%pmlul aveva_design_plots C:\Program Files (x86)\AVEVA\PIantiE3D'. 1. \PMLUMpiots\ ‘AVEVA_APPLICATION_DATA C:\Users\Public\Documents\AVEVA\PlanfiE3D\Datat.1.0\ AVEVA_DESIGN_DFLTS (C:\Users\Public\Documents\AVEVA\PlanfiE3D\Datat.1.010FLTS\ aveva_design_work Setemp%l aveva_design_user C\Users\Public\Documenis\AVEVA\PianfiEaD\Datat.1.01USERDAT A\ aveva_design_rep_dir ‘opmiuivereports\ aveva_design_help_dir %aveva_design_exe%Documentation\ plotcade ‘C:AProgram Files (x66)\Common Files\Aveva Shared Plotiplot exe cade_plot_dir Yploicade% projects_dir C:\Users\PubliciDocuments\AVEVA\PlantiE3D\Projects1.1.0\ Customer projects are now stored in C:\User\Public\Documents. A call from the standard evars int file runs Soprojects_dirYecustom_evars.bat. Updating this fle can be used to install new projects, Note: For compatibility, PDMS environment variables are also set by set_aveva_design.bat © Copyright 2012 to current year. 10 AVEVA Solutions Limited and its subsidiaries. All rights reserved, www.aveva.com FARRAR ARRPRARPARARAAANHAAAAAAHAAAANAANAOAN. As Starting E3D in Non-graphics mode : AVEVA E3D supports non-graphics (TTY) mode. This is a useful mode for administrators running batch Scripts, overnight processes or large data updates. For example, the following could be executed in a windows batch file: ‘Program Files (x86)\AVEVA\Plant\E3D1.1.0\mon.exe" TTY PROD 30 init "C:\Program Files («86)\AVEVA\Plant\E3D1.1.0llaunch.init* APS SYSTEM/XXXXXX /ALL C:\macro.pmimac Where the arguments are: + TTY tells E3D to enter non-graphics mode + PROD 3D is the required product. This will dictate which modules are available. is the standard init file call to set the environemtn + APS is the required project, + SYSTEMIXXXXXX is the required username and password + IALLis the required MDB = CAlmacro.pmimac is the macro to be run at startup (full path) Note: File paths would need to be updated to reflect actual file locations ef ecioue pe vet whe! Bap Rege 9 ireme dD, © Copyright 2012 to current year. " AVEVA Solutions Limited and its subsidiaries, All rights reserved, wWww.aveva.com AVEVA Everything3D (1.1) For Administrators ~ TM-XXXX © Copyright 2012 to current year. 12 www.aveva.com AVEVA Solutions Limited and its subsidiaries. All rights reserved. NRAAAARAARAARARARPAAAAAAAAAAAAAAAA see ere This chapter gives an overview of the Microsoft fluent interface used by AVEVA Everything3D™ 24 Interface 5D 24 Gsm ba Pome Se A aerition =, | eeltcey [ taettaeiares Itfeatures Tabs, Tab Groups and Controls. Existing PDMS PML developments may have included toolbars. Before deploying the PML in E3D, their existing PDMS menu bar needs to be converted to work with the new interface. Consider the following PDMS toolbar: Peo By Loaded j» No PML Forms Found Itis a typical example of a toolbar with a mixture of buttons and menus. All the buttons run a PML function and depending on the supplied argument, different activities are completed. If the user selects from the drop down menus, they can load the available PML files in session. This is possible because the PML function can both read values from and write values to the toolbar. It can also control the active state of some of the buttons. Within PDMS, itis the variable !!appDesMain which provides the access. In E3D, PML cannot directly access the fluent interface as was possible in AVEVA PDMS, but there is a mechanism available, This document will demonstrate how this POMS toolbar can be migrated to E3D. © Copyright 1974 to current year. 3 AVEVA Solutions Limited and its subsidiaries, All rights reserved, Www.aveva.com AVEVA Everything3D (1.1) For Administrators ~ TM-XXXX ey Setting up the environment : To customise the E3D interface, changes are going to be made to a number of files. The following lines shouldbe added to the launch fe: set customization_folder=C: \AVEVA\Customisation set pmllib=%customization_folder%\pmllib;%pml1ib% set pnlui=%eustomization folder%\pnlui ;%pmluix . svt Giauteparwavtniatin fade DS os gail 280 eqrorn BO This will ensure that any modified files are kept separate from the or indtallaion oe 7 Itis possible to create another E3D launch shortcut to call this customised launch.init file. The target can be updated to the following (with the full fle paths used instead of dots) \.e\es\e-\mon.exe" PROD 3D init "C:\..\..\launch.init” Updating DesignCustomization.xml The content of the interface is controlled by a series of .uic files. These are loaded as E3D starts up and define the available controls, tab groups and tabs. Each module loads the”.uic files listed in a module specific xml file. For example, the module Model uses an xml file calles nCustomization.xml. Locate the file in the E30 installation directory and copy into %customisation_folder%. ‘Open and add red line from below: AvevaSharedIcons: 1D_WARNING

You might also like