PDMS and Associated Products Installation Guide
Short Description
PDMS and Associated Products Installation Guide...
Description
PDMS & Associated Products Installation Guide
AVEVA Solutions Limited
Disclaimer 1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from viruses. 1.2 AVEVA AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any special, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be suffered by the user, including any loss suffered by the user resulting from the inaccuracy or invalidity of any data created by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or arise in contract, tort (including negligence) or otherwise. 1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the performance of the AVEVA AVEVA software shall be limited to 100% of the licence fees paid in the year in which the user's claim is brought. 1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law. 1.5 In the event of any conflict between the above clauses and the a nalogous clauses in the software licence under which the AVEVA software was purchased, the clauses in the software licence shall take precedence.
Copyright Copyright and all other intellectual property rights in this manual and the associated software, and every part of it (including source code, object code, any data contained in it, the manual and any other documentation supplied with it) belongs to, or is validly licensed by, A AVEV VEVA A Solutions Limited or its subsidiaries. All rights are reserved reserved to AVEV AVEVA A Solutions Limited Limited and its subsidiaries. subsidiaries. The information contained in this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without the prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires that this copyright notice, and the above disclaimer, disclaimer, is prominently displayed at the beginning of every copy that is made. The manual and associated documentation may not be adapted, reproduced, or copied, in any material or electronic form, without the prior written permission of AVEVA Solutions Limited. The user may not reverse engineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in this publication may be incorporated into any third-party software, product, machine, or system without the prior written permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal prosecution. The AVEVA software described in this guide is to be installed and operated strictly in accordance with the terms and conditions of the respective software licences, and in accordance with the relevant User Documentation. Unauthorised or unlicensed use of the software is strictly prohibited. Copyright 1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA shall not be liable for any breach or infringement of a third party's intellectual property rights where such breach results from a user's modification of the AVEVA software or associated documentation. AVEV AVEVA A Solutions Limited, High Cross, Cross, Madingley Road, Road, Cambridge, CB3 0HB, 0HB, United Kingdom.
Trademark AVEV AVEVA A and Tribon are registered trademarks of AVEVA AVEVA Solutions Limited or its subsidiaries. Unauthorised use of the AVEVA or Tribon trademarks is strictly forbidden. AVEV AVEVA A product/software names are trademarks or registered trademarks of AVEVA VEVA Solutions Limited or its subsidiaries, registered in the UK, Europe and other countries (worldwide). The copyright, trademark rights, or other intellectual property rights in any other product or software, its name or logo belongs to its respective owner.
PDMS & Associated Products Installation Guide
Revision Sheet
Date
Version
Comments / Remarks
September 2011
12.1.1
Issued
January 2012 June 2013
Copyright added to all pages. Screens updated from 12.1.1 to 12.1.SP2 12.1.SP4
Updated for SP4
PDMS & Associated Products Installation Guide
PDMS & Associated Products Installation Guide
Installation Installation Guide
Contents
Page
PDMS & Associated Products Introduction Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 Assumptions Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 Guide Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1 Associated Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Hardware Hardware and Softwar Software e Requirements Requirements . . . . . . . . . . . . . . . . . . . . . . . 2:1 AVEVA PDMS 12.1 Software Installation Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1 AVEVA License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1 .NET Framework Installation Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1
Enable Microsoft Excel Interop Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1 Font Size Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4 True Type Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6
AVEVA PDMS and and Associated Associated Product Products s Installation Installation . . . . . . . . . . . 3:1 Log File File
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:14 3:14
Uninstall Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:15 3:15 Modifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:15 Repairing Repairing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:16 Healin Healing g
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17 3:17
Modified New and Removed Removed Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17 User Modified Appware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17
Models, Sample Data and Example Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . 3:17
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
i
12 Series
PDMS & Associated Products Installation Guide
Changing Default File Replacement Replacement Behaviour . . . . . . . . . . . . . . . . . . . . . . . . 3:18 Post Deployed .bat files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:18 Pre-Deployed Pre-Deployed .bat files. files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:18 .bat file Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:19
Network (Admin) Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:19 Create an Administrative Administrative Installation Installation Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:19
Issues with Administrative Installation Points . . . . . . . . . . . . . . . . . . . . . . . . . 3:21 .NET Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:21 Signin Signing g
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22 3:22
Using Files within within the Source Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:22 Network Throughput. Throughput. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:23 Advantages of a Network Installation Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:23
Run PDMS and Associated Products from Network Locations. Locations. . . . . . . . . . . . 3:23 Administrative Installation Installation Points Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:24 Patch Administrative Administrative Installations. Installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:24
Copy a Local Deployment to a File Server Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:24 Feature Id Reference List List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:25 Feature Tree Hierarchy Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:25
SelectionTree Selection & De-selection Rules . . . . . . . . . . . . . . . . . . . . . . . . . 3:26 Selecting Features from the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . 3:26 Command Line Definable Directories Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:27 Sample Command Command Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:27
Set Up the Windows Windows Environme Environment. nt. . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1 Windows Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1 Graphics Card Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1 Set the License File Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2 PDMS Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2 Run PDMS PDMS from a Comman Command d Window Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4 Customise PDMS Start-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:4 Create User Batch Batch File to Run PDMS PDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5
Run PDMS in Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:5 Plot Plot
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:6
Language Language Support. Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:1 Setting PDMS Default Text Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:2
© Copyright 1974 to current year. year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
ii
12 Series
PDMS & Associated Products Installation Guide
Prepare PDMS For Legacy Legacy Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5:3
Run PDMS PDMS Under Under Windows Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1 Spaces in Windows Windows Pathnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1 Link to Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1 Windows Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6:1
PDMS Projects. Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1 Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1 Copy Project SAM to User Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1 Users and Teams Teams in the Sample Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:1 MDBs in the Sample Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:2 Sample Project Project and User Projects Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7:3
Troubleshoot Troubleshooting ing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1 Genera Generall
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1 8:1
Enter PDMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:1 Problems with Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8:2
Structure Structure of PDMS PDMS on .NET .NET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1 Overview Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1 9:1 PDMSEXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1 GUI Module Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:1 .NET Loading Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2 Native DLLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2
Components Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9:2
Troubleshoot Troubleshooting ing the .NET .NET Installation Installation . . . . . . . . . . . . . . . . . . . . . . 10:1 Version Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1 Interface or a Dependency Missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:1 Interface Incompatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2 No Add-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2 Window Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2 Serialisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10:2
Install AutoDRA AutoDRAFT. FT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1 Compatibility Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
iii
12 Series
PDMS & Associated Products Installation Guide
AutoDRAFT Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1 Configure AutoDRAFT with AutoCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:1 Install and Configure AutoCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:2 AutoCAD R2006. R2006. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:2 AutoCAD R2007. R2007. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:2
AutoCAD AutoCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:3 Application Macros for use with DRAFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11:3
Configure Configure Area Area Based ADP ADP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12:1 MDS Installed Installed Configura Configuration tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:1 Manual Configuration of the Product and Product Environment Environment Variables . . 13:1 Set Environment Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:1 Modification of Evars.bat for MDS . MDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:2 Environment Variables Variables for Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:2 For Projects Used with MDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:2
Projec Projects ts
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:3 13:3
Projects Released Released with this Product. Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13:3
© Copyright 1974 to current year. year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
iv
12 Series
PDMS & Associated Products Installation Guide Introduction
1
Introduction The PDMS & Associated Products Installation Guide explains how to install and set up PDMS & Associated Products on a workstation running Microsoft Windows. For completely up-to-date information, refer to the AVEVA Website at http://www.aveva.com/products/ support/support.html and support/support.html and the Customer Support Hardware pages. The Web pages also give hints on ways of setting up and running PDMS on different computers in order to achieve the most efficient performance.
1.1
Assumptions The PDMS & Associated Products Installation Guide assumes that: •
Users are familiar familiar with the the concepts concepts of folder/fi folder/file le hierarchie hierarchies s for storing storing data data on disks disks and with basic Windows terminology and commands. If not, the user can also refer to the operating system documentation while carrying out the installation.
•
Users have already already gained gained access access to the PDMS PDMS install installation ation files files via a disk, disk, from from the AVEVA AVEVA Web site, or by some other route.
•
1.2
User Users s have have Local Local Adm Admin inis istr trat ator or righ rights ts..
Guide Structure The PDMS & Associated Products Installation Guide is divided into the following sections: Hardware and Software Requirements
lists the hardware and software requirements.
AVEVA PDMS and Associated Products Installation
describes how to install and license the software.
Set Up the Windows Environment
explains how to configure the Windows operating system before running PDMS.
Language Support
describes how to set up the Windows Environment to use PDMS with different Language options.
Run PDMS Under Windows
gives some advice on using PDMS in a Windows environment.
PDMS Projects
describes the sample project that is supplied as part of PDMS, and how the user can set up projects.
Troubleshooting
describes solutions for some of the errors that could be encountered when running PDMS.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and its subsidiaries. subsidiaries. All rights reserved. reserved.
1:1
12 Series
PDMS & Associated Products Installation Guide Introduction
Structure of PDMS on .NET
outlines the way in which PDMS in installed and configured in a Microsoft .NET environment.
Troubleshooting the .NET Installation
describes solutions to some of the .NET related issues that might be encountered.
Install AutoDRAFT
1.3
explains the procedure needed to install and configure AutoDRAFT.
Configure Area Based ADP
describes how to configure Area Based ADP.
MDS Installed Configuration
describes how to configure folder structure and naming configurations.
Pipe Stress Interface Configuration
describes which standard settings need modifying to complete the installed version.
Associated Products The following are available as additional installation options when installing PDMS. •
Global and Global Global WCF Client Client - for synchronisati synchronisation on of projects projects between between world-wide world-wide sites
•
Schematic Schematic 3D 3D Integrator Integrator - Integratio Integration n applicati application on to to make make sure sure there there is data consistency between P&ID and the 3D model
•
Area Based Based ADP ADP - Automates Automates the producti production on of volumetric volumetric drawings drawings using using specifi specified ed templates, thus simplifying their update after a change to the model
•
Multi-Discip Multi-Discipline line Support Supports s - For the design, design, drawing drawing and MTO MTO of all all kinds kinds of supports supports
•
ExPl ExPlan antt-A A - DXF DXF exp expor ortt dri drive ver r
•
ExPl ExPlan antt-II - DGN DGN expo export rt dri drive ver r
•
Pipe Stres Stress s Interfa Interface ce - for exchan exchangin ging g informat information ion betwe between en the PDMS PDMS and the CEASAR II pipe stress system
•
Building Building Applicatio Applications ns - Specialis Specialised ed applicat applications ions for for the design and managing managing of power power plants
There are various AVEVA products that can be used in conjunction with PDMS. The user can consider installing these at the same time. Those closely associated with PDMS include the following DESIGN products: •
AVEVA VEVA Global Global Server Server - For synchroni synchronisatio sation n of PDMS PDMS products products between between world world wide sites
•
AVEVA VEVA SQL Direct Direct - Access Access the DESIGN DESIGN Database Database directly directly from within within software software products that support Microsoft Universal Data Access interfaces
•
AVEVA VEVA ImPlant-I ImPlant-I - Transla Translator tor for for exporting exporting Intergraph’s Intergraph’s 3D graphics graphics to PDMS PDMS
•
AVEVA VEVA ImPlant-STL ImPlant-STL - For translat translating ing stereol stereolithogr ithography aphy (STL) (STL) files files that that have have been generated from non-AVEVA mechanical CAD systems into macro files that can be input to PDMS
•
AVEVA VEVA OpenSt OpenSteel eel - Trans Transfer fer steel steel detai detailin ling g data data via SDNF SDNF
•
AVEVA VEVA PML Publish Publisher er - Programma Programmable ble Macro Macro Language Language functions, functions, object object forms forms and and macros can be encrypted using the tools available
•
Model Management Management - for change change & status status control control of engineer engineering ing object objects s (e.g. (e.g. pipes, pipes, welds, …) from system DESIGN through detailing and into deliverable production
•
AVEVA VEVA P&ID - AutoCad AutoCad based based application application that enables enables the creation creation of intellige intelligent nt P&IDs P&IDs
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
1:2
12 Series
PDMS & Associated Products Installation Guide Introduction
•
AVEVA VEVA Licensing Licensing System - License License file required required to run the the software. software.
For details of the installation of these ‘add-on’ products, refer to the relevant installation guide. If they are required, it may be advisable to read these before installing PDMS.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
1:3
12 Series
PDMS & Associated Products Installation Guide Introduction
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
1:4
12 Series
PDMS & Associated Products Installation Guide Hardware and Software Requirements
2
Hardware and Software Requirements The user should refer to the Systems Requirements guide Requirements guide and make sure that the system and network meets all of the requirements before attempting to install the software.
2.1 2.1
AVEV EVA A PDMS PDMS 12.1 12.1 So Sofftwar tware e Inst Instal alla lati tion on AVEVA AVEVA PDMS software is supplied on a disk. The disk contains •
Release No Notes
•
AVEV VEVA Plan Plantt Suit Suite e 12. 12.1 1 Hel Help p
•
an inst install allabl able e versio version n of Micro Microsof soft’ t’s s .NET .NET Framew Framework ork
•
AVEV VEVA Lic Licen ense se Serv Server er
Insert the disk in the Workstation disk drive, and then follow the instructions. If the disk does not start, click Start > Run and then browse for the Start.htm.
2.1.1
AVEVA License File To operate, AVEVA software must be able to access the correct license file, which should be installed on either the Server, on the users workstation, or on a networked workstation. Refer to the AVEVA Licensing System guide. News and update information is also available on the AVEVA support web-site.
Note: Although the disk contains several AVEVA AVEVA products, the user will only be able to use the items that are licensed to them. The user will get an on-screen notification to warn them when the license is due for renewal.
2.1.2
.NET Fr Framework In Installation The graphical user interface requires that Microsoft’s .NET Framework be installed. The .NET Framework is supplied on the disk and if it has not been previously installed the installation will install it automatically when the installation is ru n from the disk.
2.2 2.2
Enable ble Mi Micro crosoft Exc Exce el In Intero erop Ass Asse embly Several of AVEVA applications use a facility in the AVEVA GridControl to import an Excel file, for example, Equipment Import, Cable Import, and Diagrams. To make sure that the Excel import facility will work the user must make sure that the Microsoft Excel Interop Assembly is enabled on each machine where it will be used.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and its subsidiaries. subsidiaries. All rights reserved. reserved.
2:1
12 Series
PDMS & Associated Products Installation Guide Hardware and Software Requirements
Open the Add or Remove Programs utility from the Control Panel , and select the version of Microsoft Office being used, the one shown here is Microsoft Office Professional Edition 2003.
Click Change to display the Maintenance Mode Options .
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
2:2
12 Series
PDMS & Associated Products Installation Guide Hardware and Software Requirements
Make sure Add or Remove Features is checked and click Next:
Check the option for Choose advanced customisation of applications , and click Next.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
2:3
12 Series
PDMS & Associated Products Installation Guide Hardware and Software Requirements
Under the Microsoft Office Excel application make sure that .NET Programmability Support is enabled. If .NET Programmability Support is not enabled then select the option Run from My Computer , and click Update.
2.3
Font Size During the installation of Windows 7, the install process decides what it believes to be the best setting for the font size and sets this as the Default. AVEVA only supports the setting Smaller and suggests that the user changes their setup to make Smaller the default setting. To change the default setting, set ting, right-click on the desktop.
Select Personalize from the menu to display the control panel.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
2:4
12 Series
PDMS & Associated Products Installation Guide Hardware and Software Requirements
Click Display to display the screen for setting the Font size.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
2:5
12 Series
PDMS & Associated Products Installation Guide Hardware and Software Requirements
Select Smaller and click Apply. The user will have to restart the system to save the settings.
2.4
True Type Fonts TrueType fonts used in Draft need to be added in the Admin module. Any font needed for this process should be toggled to Show rather than Hide in the Windows 7 Control Panel Fonts display. This may not be the default for Arial Unicode MS, which is likely to be needed for some character sets.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
2:6
12 Series
PDMS & Associated Products Installation Guide Hardware and Software Requirements
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
2:7
12 Series
PDMS & Associated Products Installation Guide Hardware and Software Requirements
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
2:8
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
3
AVEVA PDMS and Associated Products Installation The AVEVA PDMS and Associated Products Installation is supplied on a disk in an installation called Plant. The disk contains an installable version of Microsoft’s .NET Framework. Also on the disk is a folder containing the Installation instructions and user documentation, and it is recommended that the user carefully read all of the Installation instructions before installing the software. It is recommended that the default settings are used for folder paths etc., unless the user has good reasons for doing otherwise.
Important: AVEVA does not recommend the use of spaces in installation folder path names. However, the system will work, with some limitations. Refer to section 1.3 of the User Bulletin for further information. Using the DVD to install AVEVA PDMS and Associated products, insert the disk and on the Welcome screen click Click for contents . Alternatively the user can click the setup.exe file to install the software manually. Using the setup.exe option bypasses the first three windows and displays the Plant Setup Wizard window. Manual installations can be easier if run from the Setup.exe program, which ships with each .msi installation supplied on disk. Each Setup.exe checks and installs the dependencies of its primary installation (like the .NET framework), before running its primary (MSI) installation. Users should never see missing dependency errors if installations are started from the Setup.exe program. Setup.exe also tells the primary installation to target the C:\ drive/volume, which is the preferred default in most manual installations. However, if a more customised installation is required then running the primary MSI directly becomes the better approach. In such cases, run time dependencies (Like the .NET framework) must be deployed beforehand. Using Setup.exe displays the Plant Setup Wizard window.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and its subsidiaries. subsidiaries. All rights reserved. reserved.
3:1
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
A screen showing the available products is displayed.
Click AVEVA PDMS to display the Release Documents screen.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:2
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
Click INSTALL to display the AVEVA Plant Setup Wizard.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:3
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
Click Next to display the End-User License Agreement window.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:4
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
The user must read the End-User License Agreement and then select the I accept the terms in the License Agreement check box to activate Next.
Note: If the user does not select the check box, Next will not activate and the installation cannot continue. After clicking Next the Custom Setup screen is displayed.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:5
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
The Custom Setup window displays every configurable aspect of the installation. Configurable Features are displayed on the left hand side of the window, in a control called the SelectionTree SelectionTree.. Each feature is depicted as a box with a description of the feature displayed in the right hand pane. The boxes representing each feature are depicted as follows: - Feature will be installed (Locally) - Feature will be installed (Locally), but not all sub-Features will. - Feature will be unavailable (Not Installed), as will all descendants. Clicking a box displays a drop-down menu.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:6
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
Will be installed on local hard drive
Selecting this option will install the feature locally.
Entire feature will be installed on local hard drive
Selecting this option will install the feature and all its sub-features locally. locally.
Entire feature will be unavailable
Selecting this option prevents the current feature and all its sub-features from installing.
Clicking Reset will de-select all currently selected features. If the the Feat Featur ure e is not not Unav Unavail ailab able le ( ), a Locat Locatio ion n Path Path sho showi wing ng whe where re the the pro progr gram am is is to be installed may be displayed, if so Browse becomes active. If a Location Path is not displayed and Browse is inactive when a specific Feature is highlighted and scheduled to be installed, then that Feature contains something which embeds itself inside another program (whose path is separately configurable). Clicking Browse, when active, displays the Change Destination Folder window window which allows the user to select a different folder name and location path.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:7
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
Addins and Ad dons are examples of this sort of thing, as they have no folders of their own, and they reside inside other programs. It may appear confusing that some Features do/do not have configurable folder paths. The following list is hoped to clarify this:
Feature
Configurable
Default Path
PDMS
Yes
C:\AVEVA\Plant\PDMS12.1.SP4\
PDMS Models
Yes
C:\AVEVA\Plant\Project12.1.SP4\
Global Client
No
C:\AVEVA\Plant\PDMS12.1.SP4\
Schematic 3D 3D In Integrator
No
C:\AVEVA\Plant\PDMS12.1.SP4\
No
C:\AVEVA\Plant\PDMS12.1.SP4\ C:\AVEVA\Plant\PDMS12.1.SP4\
Multi-Discipline Supports No
C:\AVEVA\Plant\PDMS12.1.SP4\
ExPlant-A
No
C:\AVEVA\Plant\PDMS12.1.SP4\
ExPlant-I
No
C:\AVEVA\Plant\PDMS12.1.SP4\
Plant Suite Help
No
C:\AVEVA\Plant\PDMS12.1SP4\Documentati on\
Area Based ADP
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:8
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
Changing the Folder Path of the Feature "AVEVA Plant Suite" will affect all applications residing in subfolders. For example: if "AVEVA Plant Suite" = J:\Test\ Then "PDMS" = J:\Test\PDMS12.1.SP4\ "PDMS Models" = J:\Test\Project12.1.SP4\ J:\Test\Project12.1.SP4\ … "Manuals" = J:\Test\PDMS12.1.SP4\Documentation\ J:\Test\PDMS12.1.SP4\Documentation\ However, if any of the other folders were to be directly changed, they would remain in that state regardless of changes to the "AVEVA Plant Suite" folder or other underlying folders. To check if enough disk space is available click Disk Usage to display the Disk Space Requirement screen. Highlighted volumes indicates that there is not enough disk space available for the selected features. The user can remove some of the files from the highlighted volumes, install fewer features or select a different destination volume. Click OK to return to the Custom Setup form. Click Back to step back a stage, Cancel to terminate the Setup Wizard or Next to display the existing projects and Infrastructures Configuration screen and continue the installation.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:9
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
The Configuration screen allows the user with existing projects and infrastructures to customise the installation. The Projects Folder path path can only be changed if the user has chosen to install the Plant or the MDS models. To change the path click Browse to display the Change Destination Folder window window which allows the user to select a different folder name and location path. Unchecking the Install bat files and: checkbox deactivates the StartMenu Shortcuts and the Desktop Shortcuts options. Both options are dependant on the bat files being installed. Unchecking the StartMenu Shortcuts checkbox deactivates the Desktop Shortcuts option. The option is dependant on the StartMenu Shortcuts being installed. Click Back to step back a stage, Cancel to terminate the Setup Wizard or Next to display the folder path Configuration screen.
Clicking Browse displays the Change Destination Folder window window which allows the user to select a different folder name and location path. Click Back to step back a stage, Cancel to terminate the Setup Wizard or Next to display the Ready to Install AVEVA Plant screen.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:10
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
The Selection Review pane displays the installations options selected by the user. The user can now click Back to step back a stage and change their installation option, Cancel to terminate the Setup Wizard or Install to display the Installing AVEVA Plant screen.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:11
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
The Installing AVEVA Plant screen displays a taskbar showing the status of the installation. During the installation process the screen displays Cancel , which can be clicked to stop the installation. When selected a window is displayed asking for confirmation that the AVEVA Plant installation is to be cancelled.
Selecting Yes displays a screen showing the AVEVA AVEVA Plant Setup W izard was interrupted.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:12
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
Click Finish to exit the screen and installation. Selecting No on the confirm screen returns the user back to the Installing AVEVA Plant screen and continues the installation.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:13
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
When the installation has been completed, click Finish to exit the Setup Wizard.
3.1
Log File During the installation, setup.exe creates a log file of the installation in the users TEMP directory named Plant12.1.4.log. To locate the log file, select Start > Run and type %TEMP% in the text field.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:14
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
Click OK to display the users TEMP directory.
3.2
Uninstall Complete removal of an installation can be accomplished by several methods. •
Removing it fro from Start > Settings > Control Panel > Add/Remove Programs applet
•
Right clicking clicking on the MSI MSI file file that that installe installed d it, and selecti selecting ng Uninst Uninstall all
•
Runnin Running g the the comma command nd MSIE MSIEXEC XEC /X [Path [Path to Orig Origina inall MSI] MSI]
•
Runn Runnin ing g the the comm comman and d MSIE MSIEXE XEC C /X {ProductCode ProductCode of of MSI}
Removal of individual Features is also possible from the command Line, using the REMOVE property or by changing the installation state via the Add/Remove Programs applet.
Note: Uninstalling the PDMS and associated Products installation will not uninstall Microsoft's .NET Framework or downgrade the Windows Installer Service. The .NET Framework must be removed separately if required.
3.3
Modifying There are several ways to modify an installed installation. For example: •
Changing it from rom Start > Settings > Control Panel > Add/Remove Programs applet
•
Right clicking clicking on the MSI MSI file that insta installed lled it, it, and selecting selecting Install Install,, then selecting selecting Change at the subsequent window.
•
Running Running the command command MSIEXEC MSIEXEC /I /I [Path [Path to Original Original MSI], MSI], then then selectin selecting g Change Change at at the subsequent window.
•
Runn Runnin ing g the the comm command and MSIEX MSIEXEC EC /I {ProductCode ProductCode of of MSI}, then selecting Change at the subsequent window.
Once the Change option is selected the Custom Setup window is displayed allowing the user to change which features are installed.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:15
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
The Change option can not be used to change the Location Path. If the user wants to change the Location Path, the current installation must be removed and then re-installed using the new Location Path.
Note: Never move files by other means, as this may trigger healing, however Copying files to other locations will not cause problems.
3.4
Repairing If any programs stop working, or the installation has knowingly been damaged, then Repair may fix the problem. There are several ways to repair an installation. For example: •
Changing it from rom Start > Settings > Control Panel > Add/Remove Programs applet
•
Right clickin clicking g on the MSI file that install installed ed it, and and selecting selecting Instal Install, l, then selecti selecting ng Repair Repair at the subsequent window.
•
Running Running the command MSIEXEC /F [Path [Path to Original Original MSI], MSI], then selecting selecting Repair Repair at the subsequent window.
•
Runn Runnin ing g the the comm comman and d MSIE MSIEXE XEC C /F {ProductCode ProductCode of MSI}, then selecting Repair at the subsequent window.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:16
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
Repairing installations causes them to heal themselves. For more information refer to Healing.
3.5
Healing MSI technology has inbuilt self repairing mechanisms. As such it is generally unwise to alter file and folder names, shortcuts or registry manually, as this may trigger the MSI which deployed the files to redeploy them. However, it is expected that some users will want to alter Appware, "Sample Data" Shortcuts and .bat file variables. As such, AVEVA installations have been designed to minimise the ability of the MSI to heal itself in such cases. Sample Data, Models, example projects and shortcuts, should not trigger healing if they are deleted or altered. The consequence of making shortcuts editable/deletable is that MSI Advertising will not function.
3.6
Modified Ne New an and Re Removed Fi Files Irrespective of whether an MSI is installing, changing state, or repairing, files are removed/ deployed/overwritten based upon certain file version rules. rules . As such, the changes caused by a repair or an installation depend upon the initial state of th e computer.
3.6.1
User Modified Appware In MSI/Deployment terms, Modified appware files constitute un-versioned, language neutral files, whose "Created Date" and "Modified Date" differ. However, if appware files have been moved or handled in certain ways, then it is possible that the "Created Date" and "Modified Date" will not differ, in which case the file replacement behaviour replacement behaviour of the installation will be different. In the case where an appware files "Created Date" and "Modified Date" is different, no MSI will ever overwrite such a file. So Modified appware will never be upgraded (by default), changed or bug fixed by an AVEVA AVEVA MSI or P atch. In the case where a modified appware files "Created Date" and "Modified Date does not differ, the appware file with the newest date will prevail (by default). This scenario is most likely to happen when installing a Patch or an MSI which is not classed as a "Service Pack" or a "Full Release", since releases with more minor designations are not side-by-side deployable, as they are intended as upgrades to pre-existing releases. Once appware has been modified, it must fall to the author/owner to maintain the changes, since there is no reliable way to reconcile code differences. In extreme cases this may mean that AVEVA installations cannot be used to deploy appware, and those clients must make their own code merges.
3.7 3.7
Models els, Sa Sample Dat Data a an and Ex Example Pr Projec ojectts It is in the nature of Models, Samples and Examples, that: •
The const constitu ituent ent part parts s are ofte often n interde interdepen penden dentt in some some way. way.
•
Interdependen Interdependencies cies will will vary vary between between releases releases and can can be difficu difficult lt and risky to migrate migrate automatically.
•
Their Their file file foot footpri print nt is is apt to chan change ge drast drastica ically lly..
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:17
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
•
They They wil willl not not alwa always ys be requi require red. d.
•
They They may may be move moved, d, cop copie ied d and and share shared. d.
•
File paths paths and folder folder names names may change change in time. time.
•
Parts Parts of them may be re-u re-used sed in othe otherr scena scenario rios. s.
•
They can can be suppor supported ted or migrat migrated ed across across many many versio versions ns of an appli applicati cation. on.
•
Many diffe different rent programs programs may work work with with them them and with data derived derived from them.
Hence, it is felt that Models, Samples and Examples: •
Should Should be regarde regarded d as sepa separate rate entiti entities es in thei theirr own right. right.
•
Have a lifecycle lifecycle which which is is likely likely to differ differ from the applicat applications ions which which they they service. service.
•
May be released released with installati installations ons which which instal installl applications applications,, but should be as easy as as possible to divorce from such installations.
•
Are unsu unsuite ited d to Repa Repair ir or or Patch Patching ing by inst install allatio ations. ns.
•
Are risky risky to to de-inst de-install all/re /remov move e when when applica applicatio tions ns are are removed removed..
•
Shoul Should d be be rel relea ease sed d holi holist stic ical ally ly..
•
Should be availabl available e separately separately from application application installatio installations ns in special special cases. cases.
•
May suit suit release release in in a simple simple compressed compressed archives archives (.zip file or or self extracting extracting executa executable ble say).
Current AVEVA MSI installations attempt to address these requirements by completely removing an installations ability to heal its Models, Samples and Examples. If a new copy is required, the installation must be completely removed, and then reinstalled. Repairing will not restore Models, Samples or Examples. Uninstalls, are achieved by deleting the root folders where the Models, Samples and Examples where deployed to. It is important to remove them if they are to be retained.
3.8 3.8
Chan Changi ging ng Defa Defaul ultt File File Repl Replac acem emen entt Beha Behavi viou our r It is possible to alter default file replacement behaviour in circumstances where an MSI installation or Patch is launched from a command line. This is achieved with the REINSTALLMODE property or the /f command line switch. REINSTALLMODE switch . Otherwise default file replacement rules will apply. apply. Default file replacement rules should suit most users. It is desirable to change file replacement behaviour, in situations where the Date/Time stamps of files might not support the required replacement of files.
3.8.1
Post De Deployed .b .bat fi files The .bat files which AVEVA installations deploy and edit are regarded as necessary for the applications to work, and so could be repaired by the installation if they are removed. However, they can be edited or replaced post deployment without risk, as long as the files "Created Date" and "Modified Date" is different (this stops an MSI from overwriting the file).
3.8.2
Pre-Deployed .b .bat fi files It is feasible to replace .bat files before deployment, in the case where deployments are staged from Admin Installations. However the details and issues concerning Admin Installations are beyond the scope of this manual.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:18
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
It is also possible to add additional files to an MSI installation, but an MSI table editor of some sort would be required. This is not a trivial option, and may well require the services of a professional re-packager. However it can be accomplished without compromising an installations ability to be patched.
3.8.3
.bat file Shortcuts All the shortcuts pointing to the .bat files are of the non-advertised or normal type. As such they can be deleted and edited, without triggering healing.
3.9
Network (Admin) Installations Administrative Installation Mode Mode is a type of .msi installation, which only causes an uncompressed copy of the original installation to be generated to a specified location (TARGETDIR TARGETDIR). ). It does not install applications, it creates another installation. The installations media (deployable files) is unpacked into a subfolder beneath the regenerated .msi file, rather than stored in external .cab files or in .cab files embedded within the .msi file itself. The resultant folder structure created resembles that, which a (Typical) local deployment would create by default. Administrative installations do not become installed onto the computer which spawned it. They only transform the source installation into an uncompressed variant of itself during this process.
3.9. 3.9.1 1
Crea Create te an Admi Admini nist stra rati tive ve Inst Instal alla lati tion on Po Poin intt To create an admin installation from an installation, start the installation from the Command Line as follows to display the AVEVA Plant Administration Point Setup screen: MSIEXEC /A [Path to MSI File]
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:19
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
Click Next to display the AVEVA Plant Administration Point Distribution screen.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:20
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
Enter the location where the Admin Installation is to be created. Clicking Browse displays a window allowing the user to navigate to the required location. Click Install to start the installation. Conversely, Conversely, the following Command Line will achieve the same result quietly: MSIEXEC /A [Path to MSI File] /QN TARGETDIR=[Path to Admin Installation]
3.10 3.10
Issue Issues s with with Adm Admin inis istra trati tive ve Ins Insttalla allatio tion n Poi Point nts s
3.10.1
.NET Security .NET security defaults to not allowing .NET program code to execute if it resides in a network location. There are several ways to “Trust” such locations, but Trusted it must be, if programs are to run across a network. .NET security can cause issues when running PDMS across the network where the add-in assemblies reside on a different machine to the .NET runtime. The default security level for the local intranet is not set to Full Trust, which means that programs may not be able to access resources on the local machine. To overcome this, the intranet security may be set to Full Trust, though this means that any .NET assembly may run. Alternatively, Full Trust may be given to a specified group of strongly named assemblies.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:21
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
Full Trust is configured using the code access security policy tool caspol. First of all the assemblies must be strongly named. Then caspol is run on each client machine to add all the assemblies on a given server directory to a group and give Full Trust to this group as follows: To trust all assemblies in a given folder:
caspol -m -ag LocalIntranet_Zone -url \\\\* FullTrust -n "" -d "" OR to trust all assemblies with the same strong name:
CasPol.exe -m -ag LocalIntranet_Zone -strong –file \\\\ -noname -noversion FullTrust -n "Aveva" -d "Full trust for Aveva products" where is the UNC (Uniform Naming Convention) The format of a UNC path is:
\\\\ where:
The Network name
The name of the share
Any ad additional onal directorie ries be below the sha sharred di directory.
caspol can be found in c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ or is part of the .NET Framework 2.0 SDK which can be downloaded from: http://www.microsoft.com/downloads/details.aspx?FamilyID=fe6f2099-b7b4-4f47-a244c96d69c35dec&displaylang=en
3.10.2
Signing Newer windows operating systems have code signing embedded into their security. As such, AVEVA have begun signing .msi files and .cab files for installations which are not restricted to Windows XP or older operating systems. Unfortunately, the Administrative Installation process recreates and/or alters the source .msi file and removes .cab files altogether, thus removing any file signatures. Changes to signed file always invalidates its signature. In this release AVEVA AVEVA have signed all dll's and exe's that are supplied. However in order to cater for installations where internet access is not permitted/available we provide an .exe.config files for each exe file that tells the operating system not to validate the digital signature. By default the installation installation is set to deploy the .exe.config to disable the digital signature validation. To enable digital signature validation the command line option CERTIFICATECHECK=1 CERTIFICATECHECK=1 should be set.
3.10 3.10.3 .3
Usin Using g File Files s with within in the the Sour Source ce Ins Insttalla allati tion on MSI databases can be authored to allow Features to be installed in the "Will be installed to run from network" state. AVEVA Installations do not currently support this mode; however it may be made available if requested. The "Will be installed to run from network" option is otherwise known as run-from-network. In this mode, files are not copied onto the target computer, but registry, shortcuts and file
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:22
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
edits do occur on the target computer, and they address the programs which reside inside the source installation.
3.10 3.10.4 .4
Netw Networ ork k Thr Through ughput put Admin installations can be very suitable for staging large deployments, because uncompressed installations usually travel better over networks because they are even more fragmented. The overall size is typically much larger; however this is still tends to be easier on Packet Switching Networks.
3.10 3.10.5 .5
Adva Advant ntag ages es of a Net Netwo work rk Inst Instal alla lati tion on Once computers address files across a network, it becomes crucial that the files are accessible whenever required. This then begs questions regarding: •
Netw Networ ork k Rel Reliabi iabili lity ty
•
Netw Networ ork k Perf Perfor orma manc nce e
•
File File Serv Server er Reli Reliab abil ilit ity y
•
File File Serv Server er Perf Perfor orma manc nce e
•
Chan Change ge Sync Synchr hron onis isat atio ion n
•
Chan Change ge Gran Granul ular arit ity y
Common reasons for storing programs on file Servers are: •
To avoid avoid the networ network k loading loading of large large and and un-stag un-stagger gered ed rollou rollouts. ts.
•
To guarant guarantee ee the the user user base base is workin working g with with the the same same files. files.
•
To preven preventt tamper tampering ing with with progra programs ms and and sett setting ings. s.
•
To mai maint ntai ain n a trad tradit itio ion. n.
All of these issues are of course resolvable with locally deployed applications
Note: Direct editing of .msi's is discouraged in favour of Transforms (.mst files).
3.1 3.11
Run PDMS PDMS and Assoc Associa iated ted Pr Prod oduct ucts s fro from m Netw Network ork Locations Running programs directly from network locations is discouraged because: •
AVEVA VEVA installati installations ons have have been been redesign redesigned ed to deploy well across networks. networks.
•
Networ Network k reliab reliabili ility ty and and perform performanc ance e is less less of of a factor factor..
•
Patch Patch rollbac rollback k functio functional nality ity only only works works with with local local install installati ations ons..
However, it is recognised that network based programs suit circumstances where: •
Multip Multiple le inst instanc ances es of of the same program program are required required..
•
An embe embedde dded d tradi traditio tion n of workin working g this this way way exis exists. ts.
•
Chan Change ge impa impact cts s Quali Quality ty Cont Control rol sys system tems. s.
So this information is provided to facilitate successful over network operation. Definitive instructions on how to run AVEVA programs from network file servers are impractical, given the many ways in which AVEVA programs can interact with each other and with Project data. Not to mention other possible permutations. So the following information is deliberately general and lacking in detail and it is aimed at assisting a highly skilled readership.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:23
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
The following things must happen if programs are to be run directly from a file server:
3.1 3.11.1 1.1
•
The progr programs ams and and the projec projects ts enviro environme nment nt must must be correctl correctly y defined defined..
•
Appropr Appropriat iate e .NET Trust Trust shoul should d be granted granted to the program programs s network network locat location ion..
•
Visual Visual Studi Studio o 2008 2008 C++ Runt Runtime imes s should should be be pre-ins pre-instal talled led..
•
.NETFram .NETFramewo ework rk Redist Redistrib ributa utable ble shou should ld be pre-i pre-inst nstall alled. ed.
•
The appro appropri priate ate short shortcut cuts s and drive drive mappi mappings ngs shoul should d be provisi provisione oned. d.
Admi Admini nist stra rativ tive e Ins Insta tall llat atio ion n Poi Point nts s The Files and Folders extracted to an "Administrative Installation Point" are laid out in a fundamentally identical way to a local installation. Additionally, files which are normally deployed to operating system folders will also be visible, but will play no functional part unless deployed locally. locally. Some Configuration files will be incomplete, or have incorrect data in them, as they are not edited until they are deployed (Locally). These files may require manual editing and concern which Modules, Addins, Addons and "User Interface Modifications" are loaded.
3.1 3.11.2 1.2
Patc Patch h Adm Admin inis istr trat ativ ive e Ins Insta talla llatio tions ns A slightly different Patch is required for an administrative installation than for a local installation, and standard AVEVA AVEVA patches target local installations. If such a Patch is applied to an Administrative Installation Point, the patch will succeed. However, any local installations which have previously been deployed from it will cease to recognise it as their source installation. So as long as local deployments have not occurred, an Administrative installation is patchable with an AVEVA patch. Similarly, if programs within the installation are addressed by a clients own means, then the Administrative Installation can be patched at any time with impunity. Since in this event the Installation has not been deployed (Locally) and so only the media state has any effect. AVEVA AVEVA patches are supplied inside an executable wrapper. To apply them to an administrative image, the patch must be extracted and the appropriated command line used. The appropriate command switch is /C which extracts the contents to the current folder.
Note: Patches cannot be rolled back from Administrative Installation Points. A copy must be made before the patch is applied, in order to rollback. Note: Patches cause changes to the .msi file, which invalidates any security certificates applied to the installation.
3.12 3.12
Copy Copy a Loc Local al Depl Deploy oyme ment nt to a Fil File e Ser Serve ver r Installing normally to a local computer and then copying the programs to a network location, as a way to create a network based installation has several advantages over an "Administrative Installation Point": •
The fund fundame amenta ntall config configurat uration ion file file edit editing ing has has happe happened ned..
•
The Local Local insta installa llatio tion n need only only includ include e the requir required ed applic applicati ations ons..
Note: Running a normal (Local) installation, and choosing a network drive as a target for the programs will fail to install. This is because file editing is performed with the local System Accounts Accounts credentials, which are not normally recognised by other computers.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:24
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
3.13
3.13 3.13.1 .1
Feat eature Id Id Re Refer ference List Feature Id
Title
Description
ABA
Area Based ADP
Area-based Automatic Drawing Production (ABA) Add-on to PDMS that automates the production of volumetric drawings of using specified templates, thus simplifying their update after a change to the PDMS model.
EXPLANTA
ExPLANT-A
DXF export driver
EXPLANTI
ExPLANT-I
DGN export driver.
GLOB GLOBAL ALUS USER ER
Glob Global al Clie Client nt
Upgr Upgrad ades es thi this s inst instal alla lati tion on to to incl includ ude e the the Remo Remote te Procedure Call (RPC) Global Client. This is required to allow PDMS Users to invoke Global commands.
MDS
Multi-Discipline Supports
Multi-Discipline Supports (MDS) Add-on to PDMS for the design, drawing and MTO of all kinds of supports, from a complicated framework encompassing integral hangers to a simple U-bolt.
MDSMOD
Plant Compatible Sample data, including catalogues, for PDMS and Models associated products.
MODELS
PDMS Models
Sample da data, in including ca catalogues, fo for PD PDMS an and associated products.
PDMS
PDMS
PDMS, including applications. Includes separately licensed add-ons: Diagrams, Cable Design, Laser Model Interface, Query, SQL-Direct.
PIDINT
Schematic 3D 3D Integrator
Integration application to ensure data consistency between P&IDs and the PDMS 3D model.
PLANT
AVEVA Pl Plant Suite
AVEVA AVEVA PDMS and associated Products 12.1.SP4
Feat Featur ure e Tree ree Hier Hierar arch chy y The following diagram shows the Plant installations SelectionTree by Feature Id's. Ancestor (Parent) Features to the Left, Descendant (Child) Features to the Right. PDMS PDMS -- MODELS PDMS -- GLOBALUSER PDMS -- GLOBALUSER -- GLOBALWCF PDMS -- PIDINT PDMS -- ABA PDMS -- ABA -- MDS PDMS -- ABA -- MDS -- MDSMOD
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:25
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
PDMS -- EXPLA NTA NTA PDMS -- EXPLANTI PDMS -- MAN
3.14 3.14
Select Selectio ionT nTre ree e Sel Select ectio ion n & De-sel De-select ectio ion n Rul Rules es Successful Inclusion of a descendant Feature implies that all ancestor Features are also included. For example, suppose the MDS Feature is required. This implies that PLANT, PDMS and ABA must also be included, since they are ancestors of the MDS Feature (see above). De-selection of a Feature overrides any commands or defaults which may have otherwise included it. For example, suppose MDS is included, and ABA is excluded. The result will be that PLANT and PDMS are installed, since they default to being installed. Removing ABA causes MDS to be removed, since ABA is its Parent (Ancestor), (see SelectionTree Hierarchy diagram).
3.15 3.15
Sele Select ctin ing g Fea Featu ture res s fro from m the the Comm Comman and d Lin Line e Features can be in the following states: •
Run Locally
•
Run from Source
•
Not Present
•
Advertised
There are several ways of controlling Feature states, but for the sake of clarity this discussion will be limited to the ADDLOCAL ADDLOCAL and and REMOVE Properties. Properties. The ADDSOURCE The ADDSOURCE Property is considered less relevant, as the "Will be installed to run from network" Feature option, is not available to Features within this installation. The ADDLOCAL ADDLOCAL and REMOVE Properties Properties are comma separated lists of an installations' Feature Id's. Any Features intended to be "Run Locally", will be listed in the ADDLOCAL Property, whilst any Features intended not to be installed will be listed in the REMOVE Property. As previously stated, de-selection commands override in clusion commands. The reason for this is because the REMOVE REMOVE Property is evaluated after the ADDLOCAL property. The partial list below shows the order in which FeatureState Properties Properties are are evaluated by the MSI Service: 1. ADD ADDLOCAL 2. REMOVE 3. ADDS ADDSO OURCE URCE 4. ADDD ADDDEF EFAU AUL LT 5. REIN REINST STAL ALL L 6. ADVE ADVER RTISE TISE
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:26
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
3.16 3.16
Comm Comman and d Line Line Defi Defina nabl ble e Dire Direct ctor orie ies s The following directories can be set on the Command Line, in the same way that Properties are assigned. Directory Id
Explanation
PDMSUSER
Specifies the pdmsuser directory location
PDMSWK
Specifies the pdmswk directory location
DFLTS
Specifies the PDMSUI\DFLTS directory location
PROJECT
Specifies the directory to extract the models to
PRODUCTDIR
Specifies the root product directory location
TARGETDIR
Target location for an Administrative Installation
ROOTDRIVE
The Partition where All Applications will be targeted (unless application directories are set).
As with Properties, Directories for which the Id's are all uppercase, can be re-defined on a Command Line. They must also be addressed in uppercase on the Command Line, because Id's are case sensitive. e.g. PRODUCTDIR="C:\Some Path with Spaces in it\" Will make PDMS install to: "C:\Some Path with Spaces in it" Rather than to: C:\AVEVA\Plant\PDMS12.1.SP4
Note: There is no space around the equals (=) sign. Note: The quotes surround the value, and would be unn ecessary is the value had no space within it.
3.1 3.16.1 6.1
Samp Sample le Comm ommand and Line Lines s A most definitive reference to MSI Command Line arguments can be found here here.. The following examples have been tested, but are only intended to demonstrate general Command Line principles. In Windows 7 and Windows Server 2008 make sure that the command line has been opened using the option Run as administrator so so that the silent install application has the correct User Access Control (UAC).
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:27
12 Series
PDMS & Associated Products Installation Guide AVEVA PDMS and Associated Associated Products Installation
Example 1 Installing Everything with Exceptions Installs all Features except "Area Based ADP" to the "E:\" drive Unattended Installation showing a progress bar with no cancel button, no finished dialog and standard logging. Never attempt to Reboot Create a basic log MSIEXEC /I [Path to MSI] ADDLOCAL=ALL REMOVE=ABA ROOTDRIVE=E:\ REBOOT=ReallySupress/l [Path to log file] /qb!-
Example 2 Installing projects to a different location locati on and setting users writeable areas to a separate drive. Installs all Features to the C:\ MSIEXEC /I [Path to MSI] ADDLOCAL=ALL ROOTDRIVE=C:\ PDMSUSER=D:\AVEVA\Data12.1.SP4\PDMSUSER PDMSWK=D:\AVEVA\Data12.1.SP4\PDMSWK DFLTS=D:\AVEVA\Data12.1.SP4\PDMSUI\DFLTS PROJECT=Q:\PDMS\12.1.SP4/l [Path to log file] /qb!-
Example 3 Removing an Installation MSIEXEC /X [Path to MSI] /QB!
Example 4 Removing a Feature Remove "ExPLANT-I" MSIEXEC /I [Path to MSI] REMOVE=EXPLANTI /qb!-
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
3:28
12 Series
PDMS & Associated Products Installation Guide Set Up the Windows Environment
4
Set Up the Windows Environment Setting up the Windows Environment section describes how to configure the Windows operating system before running PDMS. Following the installation of PDMS, the user should perform the following steps: •
Check Check the setting settings s for for the the graphi graphics cs board: board: See Graphics Card Settings. Settings .
•
Make sure sure the the AVEV AVEVA A Licensi Licensing ng Syste System m is runnin running. g. Refer Refer to Set the License File Location.. Location
•
Config Configure ure Windows Windows parame parameter ters s for for PDMS: PDMS: Refer Refer to to PDMS Environment Variables. Variables.
•
The user user can then run PDMS PDMS by clicking clicking on the PDMS PDMS shortcut shortcut or icon, icon, which which will will set set up the remaining environment variables required.
Note: In the following instructions it is assumed that AVEVA PDMS has been installed in folder C:\AVEVA\Plant. If it has been installed elsewhere, substitute C:\AVEVA\Plant with the name of the installation folder.
4.1
Windows Control Panel The Windows Control Panel contains tools that are used to change the way Windows looks and behaves. This Installation Guide describes how to use Control Panel tools to configure Windows to run PDMS. Open the Control Panel as follows:
•
4.2
Windows XP If the users computer is set up with the Classic Start menu, click Start, point to Settings, and then click Control Panel. If the users computer is set up with the standard Start menu, click Start and then click Control Panel.
Graphics Ca Card Se Settings The user should set the display to a resolution of at least 1024 x 768 ( 1920 x 1200 recommended) and the colour depth to True colour or 16.7 million colours. To set the display settin gs, open the Control Panel. Select Display and select the Settings tab. Make the appropriate selections on the form for the graphics card. Due to the rapidly changing list of hardware accelerated OpenGL graphics cards commercially available, an up-to-date list of supported graphics cards, graphics device drivers and recommended device driver configuration cannot be included in this document. However, the AVEVA AVEVA Support Web pages (http://www.aveva.com/support (http://www.aveva.com/support)) contain a current list of both tested and supported graphics cards, along with advice on configuration of graphics device drivers.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and its subsidiaries. subsidiaries. All rights reserved. reserved.
4:1
12 Series
PDMS & Associated Products Installation Guide Set Up the Windows Environment
4.3
Set the License File Location Before the user can use PDMS, the AVEVA Licensing System must be set up. Refer to the AVEVA AVEVA Licencing System guide for further information. A license file should be requested from AVEVA Customer Services.
4.4
PDMS En Environment Va Variables PDMS uses Windows Environment variables to locate folders containing PDMS system files and users project data. This allows the user to locate these folders anywhere on the file system. The default location for PDMS system files is C:\AVEVA\plant\PDMS12.1.SP4\, unless the default location was changed during the installation. PDMS is supplied with a file evars.bat in the PDMS executables folder 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 PDMSEXE folder containing PDMS 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 PDMSUI=C:\Local PDMS\Appware;M:\Project PDMS\Appware; a:\Company PDMS\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 PDMSUI=C:\Local PDMS\Appware;
Length of Search Path Environment Variable The lengths of PDMS 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) Then on PDMS:
*$m%MYPATH%\mac Will check in turn for:
C:\Program Files\AVEVA\Standard Version\mac C:\Program Files\AVEVA\Update Version\mac
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
4:2
12 Series
PDMS & Associated Products Installation Guide Set Up the Windows Environment
PDMS System Environment Variables The following environment variables refer to the location of PDMS system files. PDMSEXE
Executable folder C:\AVEVA\Plant\PDMS12.0.xxx
PDMSEXEMAIN
Copy of PDMSEXE, but can be a search path C:\AVEVA\Plant\PDMS12.0.xxx
PDMSUI
Application User Interface folder (PML 1) C:\AVEVA\Plant\PDMS12.1.SP4\PDMSUI
PMLLIB
Application User Interface folder (PML 2) C:\AVEVA\Plant\PDMS12.1.SP4\PMLLIB
PDMSDFLTS
Applications defaults folder C:\AVEVA\Data12.1.SP4\PDMSUI\dflts
PDMSPLOTS
Applications PLOTS folder C:\AVEVA\Plant\PDMS12.1.SP4\PDMSUI\plots
PLOTCADC
Pointer to the PLOT executable. C:\AVEVA\Plant\PDMS12.1.SP4\plot\plot.exe
PDMSHELPDIR
Online help data files. C:\AVEVA\Plant\PDMS12.1.SP4\Documentation
PDMS User Environment Variables The following environment variables refer to th e location of users PDMS folders. Users must have write permission to these folders. PDMSWK
Temporary PDMS work file folder C:\AVEVA\Data12.1.SP4\PDMSWK
PDMSUSER
Application Users save/restore setup area (or the users 'home' folder) C:\AVEVA\Data12.1.SP4\PDMSUSER\
PDMSREPDIR
PDMS Applicationware Report Input and Output folder. C:\AVEVA\Plant\PDMS12.1.SP4\PDMSUI\reports
PDMSDFLTS
Applications defaults folder. Note that individual users may not have permission to change PDMS System defaults in C:\AVEVA\Data12.1.SP4\PDMSUI\dflts, but they should have their own local defaults area. This is achieved by setting a PDMSDFLTS search path, e.g. ‘C:\USERDFLTS C:\AVEVA\Data12.1.SP4\PDMSUI\dflts.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
4:3
12 Series
PDMS & Associated Products Installation Guide Set Up the Windows Environment
Project Environment Variables For each PDMS project, the following environment variables must be set. For example, for a project ABC: ABC000
Project database folder
ABCISO
Project ISODRAFT options folder
ABCMAC
Project Inter-DB connection macro folder
ABCPIC
Project DRAFT picture file folder
ABCDFLTS
Project configuration settings
PDMS is installed with sample project data (Refer to PDMS Projects). Projects). PDMS Project Environment variables for these projects are set in evars.bat.
4.5
Run PDMS from a Command Window The user can run PDMS from a Command window rather than using the Start/Programs menu. To do this the user must set the PATH variable to include the folder where PDMS is installed.
Windows XP •
Open the Control Panel .
•
Select System, and pick the Advanced tab.
•
Click on the Environment Variables .
•
Edit Edit the the sys syste tem m vari variab able le Path to add the PDMS folder (for C:\AVEVA\Plant\PDMS12.1.SP4\) to the list of folders in the Path variable.
example,
Once the Path variable includes the AVEVA AVEVA PDMS folder, the user can run PDMS by t yping pdms at a command prompt.
4.6
Customise PDMS Start-Up There is a batch (.bat) file supplied in C:\AVEVA\Plant\PDMS12.1.SP4\ called pdms.bat which allows entry into PDMS. The user can run PDMS using this batch file in any of the following ways: •
Use Use the sho short rtcu cutt in the the Windo Windows ws Sta Start rt menu menu,, Start > All Programs > AVEVA Plant > Design > PDMS 12.SP4 > Design
•
The user user can create a shortcut shortcut on on their their desktop desktop to run their their batch batch file. file. With 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 pdms.bat, for example: C:\AVEVA\Plant\PDMS12.1.SP4\pdms.bat then press Next and give the shortcut a name. Press Finish. The user should now be able to double-click on the shortcut icon to enter PDMS.
•
If the user has has C:\AVEV C:\AVEVA\Plant A\Plant\PDMS12 \PDMS12.1.SP4\ .1.SP4\ (the path path name name for the pdms.bat pdms.bat file) in their PATH environment variable, just type pdms in a command window to execute the batch file.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
4:4
12 Series
PDMS & Associated Products Installation Guide Set Up the Windows Environment
•
4.6 4.6.1
Otherwi Otherwise, se, navig navigate ate to the the folder folder where where the the batch batch file file is store stored d and type type pdms or pdms.bat .
Crea Create te User User Batc Batch h File File to Run Run PDMS PDMS The user can set up their own batch files to run PDMS. 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, runpdmsmacro.bat . Type the following line into this file:
C:\A C:\AVE VEVA VA\P \Pla lant nt\P \PDM DMS1 S12. 2.1. 1.SP SP4\ 4\pd pdms ms.b .bat at TTY TTY SAM SAM SYST SYSTEM EM/X /XXX XXXX XXX X / STRUC $M/mymacrofile Where: •
TTY tells PDMS not to start the PDMS GUI. This gives command line only operation.
•
SAM is the project name.
•
SYST SYSTEM EM/X /XXX XXXX XXX X is the the PDMS PDMS username/password to be used when running the command macro
•
/STR /STRUC UC sele select cts s the the requ requir ired ed MDB
• m y m a c r o f i l e is is the pathname of a PDMS command macro, containing the commands that the user wants to execute in PDMS. PDMS . In this example, running runpdmsmacro.bat will enter PDMS in project SAM, as user SYSTEM/XXXXXX, in MDB /STRUC, and run the PDMS command macro mymacrofile. mymacrofile.
4.7
Run PDMS in Batch PDMS creates a separate PDMSConsole process to manage the command-line input/ output for all modules. When PDMS is invoked from a .bat file, processing of this file resumes as soon as the user leaves MONITOR - even though the user is still using PDMS. To help manage this situation, PDMSWait.exe is distributed as part of PDMS and can be used to make a PDMS script wait for PDMS to complete before continuing. PDMSWait uses Windows facilities to wait for an event triggered by PDMSConsole when PDMS finishes. Because the user can be running more than one PDMS 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 $$.
Example:
set PDMS_CONSOLE PDMS_CONSOLE_IDEN _IDENTIFIER TIFIER=%RAND =%RANDOM% OM% call call %PDM %PDMSE SEXE XE%\ %\pd pdms ms call call %PDMSE %PDMSEXE% XE%\pd \pdmsw mswait ait echo Returned to .bat at %TIME% This will start PDMS, then wait until it has finished before resuming the script. The MONITOR Reference MONITOR Reference Manual provides provides more details on running PDMS batch programs.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
4:5
12 Series
PDMS & Associated Products Installation Guide Set Up the Windows Environment
4.8
Plot To plot in a Windows environment, AVEVA AVEVA recommend that the user uses the plotcadc.bat file supplied in the AVEVA AVEVA PDMS folder.
Note: The user may have to modify the plotcadc.bat file to suit their local printer installation. The Network Plotter must be mapped using the NET USE command. Refer to the network documentation for more information. To run the plotcadc.bat file, give a command in the format:
C:\AVEVA\Plant\PDMS12.1.SP4\plotcadc.bat plotfile format printer options Where options are the AVEVA PLOT utility options, and may be omitted. See the PLOT User Guide for more information.
Note: The options must be enclosed in quotes. Example:
plotcadc.bat c:\pdms\plot1 ps \\ntserver\NTPostScript plotcadc.bat c:\pdms\plot1 hpgl \\ntserver\NThpgl 'CE=Y'
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
4:6
12 Series
PDMS & Associated Products Installation Guide Language Support
5
Language Support PDMS 12.1.SP2 introduced the use of Unicode for character storage throughout, with the exception of data migrated from previous versions or deliberately created in this 'legacy' format. This simplifies its installation so that, in general, no special settings are required, other than making sure that the appropriate language support is installed in Windows. This will enable the support of many more languages in the future. There are aspects of the Unicode standard that are not yet implemented. PDMS currently handles the following correctly: •
Left Left to to Right Right lang langua uage ges; s; and and the there refor fore e not, for example, Arabic and Hebrew
•
Pre-com Pre-compose posed d charac characters ters;; for examp example, le, the the singl single e charac character ter á but not the combiners a + ' => á
•
Upper and lower lower casing casing of characte characters, rs, where where both both cases cases have have the the same same number number of bytes
Previous versions of PDMS have been supported only with certain language groups; the same groups have been used to test PDMS 12.1.SP4 and are fully supported. No PDMS font files are available for any other language; this means that TrueType fonts must be used on drawings and that therefore it is not possible to produce plotfile output. These groups are: •
Latin-1
•
Latin-2
•
Latin-Cyrillic
•
Far Eastern
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and its subsidiaries. subsidiaries. All rights reserved. reserved.
5:1
12 Series
PDMS & Associated Products Installation Guide Language Support
Supported Languages Name
Description
Languages covered
Latin 1
ISO 8859-1 Lat Latin alphabet 1
Danish, Du Dutch, Eng English, Faroese, Fi Finnish, French, German, Icelandic, Irish, Italian, Norwegian, Portuguese, Spanish, Swedish,
Latin 2
ISO 88 8859-2 Latin al alphabet 2
Albanian, Cz Czech, En English, Ge German, Hungarian, Polish, Rumanian, SerboCroat, Slovak, Slovene
Lati Latinn-Cy Cyri rill llic ic
ISO 88598859-5 5 alphabet
Latin Latin/C /Cyr yril illi lic c Bulgarian, Byelorussian, English, Macedonian, Serbo-Croatian, Ukrainian, Russian
Far Eastern
5.1
Japanese, Korean, Simplified Chinese, Traditional Chinese
Setting PD PDMS Default Te Text Fo Format By default all sequential text files read by PDMS will be expected to be in UTF-8 format with a Byte Order Mark (BOM) present to identify them. This includes PML files, Datal files etc. Similarly by default all sequential text files written by PDMS will be in Unicode UTF-8 format with a BOM present. A simple command line 'transcoder' 'tr anscoder' is also supplied; this may be used in some applications to convert files to a different encoding. This is installed with PDMS and is called transc.exe; further details can be found using its -h command line option. In order to change these defaults, environment variables are available for users to modify the way PDMS handles sequential text files: CADC CADC_L _LAN ANG G
Speci pecifi fies es the the file file enco encodi ding ng for for read readin ing g exte extern rnal al file files s whic which h do not not have a Unicode BOM present. If the variable is unset, this defaults to LATIN-1. Files with the following Unicode BOMs will be translated to UTF-8 on reading: UTF-16 little-endian, UTF-16 big-endian, UTF-32 little-endian, UTF-32 big-endian.
CADC_L CADC_LANG ANG_NEW _NEW
Specifie pecifies s the file file encodi encoding ng for new new files files writte written. n. If the the variabl variable e is unset, the default is Unicode UTF-8 format with a BOM present.
These variables may be set to a variety of values: UTF8
Unicode UTF-8 (the default)
UTF16LE
UTF-16 little-endian
UTF16BE
UTF-16 big-endian
UTF32LE
UTF-32 little-endian
UTF32BE
UTF-32 big-endian
LATIN1
ISO8859-1
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
5:2
12 Series
PDMS & Associated Products Installation Guide Language Support
5.2
LATIN2
ISO8859-2
LATIN3
ISO8859-5 Cyrillic
JAPANESE
Japanese Shift-JIS
CHINESE
Simplified Chinese (EUC)
KOREAN
Korean (EUC)
TCHINESE
Traditional Chinese (used in Taiwan for example) (EUC)
CP932
Japanese Shift-JIS
CP936
Simplified Chinese GBK
CP949
Korean
CP950
Traditional Chinese Big5
CP1250
Central European
CP1251
Cyrillic
CP1252
LATIN-1 + some extras (beware)
Prepare PDMS For Legacy Database These settings should not be required for new projects but must be set correctly in order to use 'legacy' databases. This is particularly important if they are to be reconfigured to Unicode as the transcoding will be based on these settings.
Command
Languages covered
PROJECT CHARSET LATIN 1 (default)
Danish, Dutch, English, Faroese, Finnish, French, German, Icelandic, Irish, Italian, Norwegian, Portuguese, Spanish, Swedish,
PROJECT PROJECT CHARSET CHARSET LATIN LATIN 2
Albanian, Albanian, Czech, English, English, German, German, Hungarian, Hungarian, Polish, Polish, Rumanian, Serbo-Croat, Slovak, Slovene
PROJECT CHARSET LATIN CYRILLIC
Bulgarian, Byelorussian, English, Macedonian, SerboCroatian, Ukrainian, Russian
PROJ PROJEC ECT T MBCH MBCHAR ARSE SET T JAP JAP
Jap Japanes anese e
PROJECT MBCHARSET KOR Korean FILE / PROJ PROJEC ECT T MBCH MBCHAR ARSE SET T CHI CHI
Simp Simpli lifi fied ed Chi Chine nese se
PROJECT MBCHARSET Traditional Chinese TCHIN FILE / The corresponding font family must be selected for DRAFT and ISODRAFT drawings. Use Project > Font Families and select the Font Type appropriate for the chosen language. For details, see the Administrator User Guide Guide and Administrator Command Reference Manual .
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
5:3
12 Series
PDMS & Associated Products Installation Guide Language Support
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
5:4
12 Series
PDMS & Associated Products Installation Guide Run PDMS Under Windows
6
Run PDMS Under Windows
6.1
Spaces in Windows Pathnames To run macros with spaces in the filenames, the user must enclose the filename in quotes, without a leading slash. For example:
$m'c $m'c:\ :\Pr Prog ogra ram m File Files\ s\Ma Macr cros os\s \spac pace. e.ma mac' c' arg1 arg1 arg2 arg2 Due to the way in which PDMS parses its command lines, this format is also recommended for use with filenames containing Asian characters.
6.2
Link to Microsoft Excel The user can make reports load directly into a Microsoft Excel spreadsheet, as commaseparated files: •
Select Utilities > Standard Reporting > Reports > Modify from the PDMS main menu bar.
•
Pick Pick a rep repor ortt tem templ plat ate. e.
•
Click Open to display the Modify Report Template window.
•
Select Options > Other Formats from the Modify Report Template window menu bar to display the Report Format window. From the Report Format window: •
Choose the CSV option from the Format drop-down list.
•
Click OK to return to the Modify Report Template window.
•
Select the Overwrite radio button.
•
For the the filename filename enter %PDMSUSER%/fnam %PDMSUSER%/fname.csv e.csv (the .csv extension extension is importa important). nt).
•
In the the Sys System tem comm comman and d text text box box ent enter er..
•
'cmd/c 'cmd/c “C:\\exc excel. el.exe exe”” %PDMSUS %PDMSUSER%\ ER%\fna fname.c me.csv'. sv'. where C:\ Version > Assembly Version, and check that all version numbers are the same.
Inte Interf rfac ace e or or a Dep Depen ende denc ncy y Mi Missin ssing g
Error:
An exception mon.exe.
‘System.IO.FileNotFoundException’
has
occurred
in
Additional information: File or assembly name Aveva.Pdms.Database. Implementation, or one of its dependencies, was not found.
Solution:
All the .NET assemblies are Private assemblies and are installed under %PDMSEXE% (Assembly Base directory) or a subdirectory below. .NET loads private assemblies from the base directory of the application. If it can’t find the private assembly here, it uses the application’s configuration file called .exe.config to see whether it contains any path hints. Path hints are stored in the element. Normally all assemblies should be located in the %PDMSEXE% directory
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and its subsidiaries. subsidiaries. All rights reserved. reserved.
10:1
12 Series
PDMS & Associated Products Installation Guide Troubleshooting the .NET Installation
10.3 10.3
Inte Interf rfac ace e Inco Incomp mpat atib ibil iliity
Error:
An exception mon.exe, or
‘System.MissingMethodException’
has
occurred
in
An exception mon.exe
‘System.IO.FileNotFoundException’
has
occurred
in
Additional informa tion: A procedure impor ted by 'Aveva.Pdms.Database. Implementation' could not be loaded
Solution:
10.4
The interfaces between components are not compatible. Check that File > Properties > Version Assembly Version on all assemblies is consistent. Also check that pdms.dll is being loaded from the same %PDMSEXE% directory as the .NET interface implementation assembly. This will be determined by the %PATH% %PATH% environment variable.
No Add-ins
Problem:
Add-ins missing from module
Solution:
Add-ins loaded by each module are defined in the following xml files: •
DesignAddi ddins.x s.xml
•
DraftAdd Addins.xml
•
Isod Isodra rafftAdd tAddin ins. s.xm xmll
•
Spool pooler erAd Add dins. ins.xm xmll
If Add-ins are missing, check that these files exist in %PDMSEXE%
10.5
Window Layout
Problem:
Window layout is not restored e.g. Add-ins position and/or docked state,
… Solution:
10.6
The file WindowLayout.xml in the %PDMSUSER% directory stores this information for the each GUI module. If this file is deleted then the window layout will return to its default.
Serialisation Serialisation is the process used to store the window layout - e.g. history stacks, toolbar state, docked window position - for the GUI in a .NET environment. For each module this
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
10:2
12 Series
PDMS & Associated Products Installation Guide Troubleshooting the .NET Installation
data is stored in C:\Documents and Settings\\Local Settings\Application Data\Aveva\PDMS. This directory may contain other serialisation data for example saved searches.
Problem:
Window layout is not restored correctly for given module.
Solution:
Delete serialisation data for given module.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
10:3
12 Series
PDMS & Associated Products Installation Guide Troubleshooting the .NET Installation
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
10:4
12 Series
PDMS & Associated Products Installation Guide Install AutoDRAFT
11
Install Au AutoDRAFT The Installing AutoDRAFT section explains the procedure needed to install and configure AutoDRAFT. AutoDRAFT may be run in stand-alone mode or it may be run from DRAFT or ISODRAFT. The user can use the adraftde, adraftbe and adraftse scripts as described in AutoDRAFT User Guide. The DRAFT and ISODRAFT applicationware generates interface files for AutoCAD, which are then used by the scripts. AutoDRAFT generates interface files for DRAFT, which can be imported using their applicationware.
11.1
Compatibility The version of AutoDRAFT released with AVEVA PDMS 12.1.SP4 is compatible with AutoCAD Releases 2006 and 2007 within the limitations described in more details in AutoDRAFT User Guide.
11.2
AutoDRAFT Software AutoDRAFT software consists of three AutoCAD applications that run with AutoCAD Releases 2006 and 2007, and AVEVA application macros to link these AutoDRAFT applications with DRAFT or ISODRAFT. The three AutoCAD applications are: •
Auto AutoDR DRAF AFT T Draw Drawin ing g Edit Editor or
The Drawing Editor is used to modify drawings transferred from a DRAFT application. •
Auto AutoDR DRAF AFT T Fra Frame me Edit Editor or
The Frame Editor is used to transfer AutoCAD drawings into backing sheets or overlay sheets in DRAFT. •
Auto AutoDR DRAF AFT T Symb Symbol ol Edi Edito tor r
The Symbol Editor is used to convert AutoCAD graphics into symbol templates within DRAFT symbol libraries.
11.3 1.3
Conf Confiigure gure Aut AutoD oDRA RAFT FT wit with h Auto AutoCA CAD D The AutoDRAFT software is installed under the PDMS executable folder:
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and its subsidiaries. subsidiaries. All rights reserved. reserved.
11:1
12 Series
PDMS & Associated Products Installation Guide Install AutoDRAFT
The autodraftACAD folder contains .bat files, AUTODRAFT scripts, AutoLISP programs, AutoCAD customisation files and an AutoCAD linestyle file. The autodraftfonts folder contains AutoCAD font files. All of these are needed to run AutoDRAFT programs in AutoCAD.
Note: The AutoDRAFT software will operate properly only if AutoCAD can be run using the acad command. AutoDRAFT may not work if the AutoCAD executable acad has been renamed, or if the acad command runs a user-supplied file which itself runs AutoCAD.
11.4 1.4
Inst Instal alll and and Conf Config igur ure e Aut AutoC oCAD AD In order to use AutoDRAFT, AutoCAD must be installed and configured for each computer where AutoDRAFT will be used. The AutoCAD Installation and Performance Guide supplied with AutoCAD describes how to do this. AutoCAD should be configured to locate the extra menus and fonts used in AutoDRAFT. The method depends on the AutoCAD version, typically: Add the appropriate paths to the autodraftACAD and autodraftfonts directories to the > Tools > Options > Support Support File Search Path field. The AutoDRAFT environment variable setting commands applicable to each release of AutoCAD are listed in the following sections. The environment variables are ar e set within the supplied pdms.bat file. These should be edited to suit the installed version of AutoCAD.
11.4.1
AutoCAD R2006 set PDMS_ACAD=2006 set PDMS_ACAD_PATH=pathname PDMS_ACAD_PATH=pathname for AutoCAD R2006 files e.g. C:\Program Files\AutoCAD 2006;C:\Program Files\Common Files\Autodesk Shared set ACAD_VERSION=%PDMS_ACAD% set path=location of autodraftACAD directory;%PDMS_ACAD_PATH%; directory;%PDMS_ACAD_PATH%; %path% Before running AutoDRAFT, the user needs to run AutoCAD R2006 and add the following as file paths:
11.4.2
•
Loca Locatio tion n of autod autodra raft ftACA ACAD D dire directo ctory ry
•
Loca Locati tion on of aut autod odraf raftf tfon onts ts dir direc ecto tory ry
AutoCAD R2007 set PDMS_ACAD=2007
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
11:2
12 Series
PDMS & Associated Products Installation Guide Install AutoDRAFT
set PDMS_ACAD_PATH=pathname PDMS_ACAD_PATH=pathname for AutoCAD R2007 files e.g. C:\Program Files\AutoCAD 2007;C:\Program Files\Common Files\Autodesk Shared set ACAD_VERSION=%PDMS_ACAD% set path=location of autodraftACAD directory;%PDMS_ACAD_PATH%; directory;%PDMS_ACAD_PATH%; %path% Before running AutoDRAFT, the user needs to run AutoCAD R2007 and add the following as file paths:
11.5
•
Loca Locatio tion n of autod autodra raft ftACA ACAD D dire directo ctory ry
•
Loca Locati tion on of aut autod odraf raftf tfon onts ts dir direc ecto tory ry
AutoCAD Before using the Drawing Editor make sure that AutoCAD has been correctly installed and configured by entering the command acad at the operating system command prompt.
11.6 1.6
Appl Applic icat atio ion n Mac Macro ros s for for use use wit with h DRA DRAFT FT The applicationware provides the additional menus and forms required to run the AutoDRAFT editors in AutoCAD directly from DRAFT and IS ODRAFT.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
11:3
12 Series
PDMS & Associated Products Installation Guide Install AutoDRAFT
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
11:4
12 Series
PDMS & Associated Products Installation Guide Configure Area Based ADP
12
Configure Area Based ADP Before starting the configuration process make sure the project has been set up with a Drafting database (PADD) for the administrative elements of ABA and at least one Drafting database (PADD) for the user elements. Make sure that access to the Drafting administration database is controlled via the Drafting administration team.
1.
Enter the Drafting module using the MDB for ABA administration and be sure to enter via Macro files, NOT Binaries.
2.
Once in the Drafting module select the Draft > Administration from the Draft menu and then Draft > Area Based ADP .
3.
Select the Settings > Area Based ADP Defaults from the menu.
4.
When the defaults form appears it shows the settings in the supplied DRA-ABADEFAULTS file. This is the hierarchy required for running the ABA application. For a detailed explanation of the elements defined in the Defaults file, refer to the Draft Administrator Application User Guide. Guide .
The fields in the defaults file are as follows:
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and its subsidiaries. subsidiaries. All rights reserved. reserved.
12:1
12 Series
PDMS & Associated Products Installation Guide Configure Area Based ADP
Defaults file
Specifies the location directory and name of the defaults file used to set or store the ABA default settings.
Library
The top-level LIBY element which holds all the required ABA administrative elements.
Templates
Templates are stored below a DRTMLB, which is a library used to hold ABA drawing templates (DRTMPL). If more that one Drawing template library is required, this should be set to a LIBY element and all DRTMPL placed below it.
Areas
A LIBY for DLLBs which are used as drawlist libraries which hold all the IDLI (ID List) elements that store the physical limit co-ordinates for each of the ABA geographical areas.
Classifications
a DLLB used to contain all the IDLI elements for each ABA classification. A Classification is a set of database elements that have something in common e.g. Equipment elements with a PURPose of PUMP. PUMP.
Keyplans
A SHLB is a sheet library used to hold all the OVER (overlay) elements for the keyplans.
Symbols
A SYLB is a symbol library that contains all ABA symbols e.g. north arrows.
Labelling
A TRLB is a tag-rule library that contains all the ABA tag rules.
Tasks
A TASKLB is a task library, which holds all the ABA tasks e.g. plot - send drawing to a plot file.
Create Hierarchy
This option is used to automatically create administrative hierarchy specified in the Defaults form.
the
To use this functionality: Modify the names to the desired settings. If the required structure exists, Create Hierarchy will show
However, if it does not exist, Create Hierarchy will show
.
Note: This only detects the existence of the LIBY, but not the elements contained within it. To create the hierarchy specified in the defaults form, click and select a db from the Create Aba Hierarchy form displayed. The previously mentioned process will also create some initial SYMBol elements. The icon will then turn to indicates that the structure is OK.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
12:2
, which
12 Series
PDMS & Associated Products Installation Guide Configure Area Based ADP
Logfile Location
Gives the directory path where the log files for drawings created using ABA are to be stored.
Batchfile Location
Gives the directory path where the batchfiles created by ABA are to be stored.
The default settings for the Batch User can be set by clicking Batch User to display the Batch Username and Password form.
User Name
Specifies name of user that will enter the Base Product.
Password
Specifies the password of the user.
The application is supplied with a series of example data files that can be used to make a test run of AB A using the standard supplie d AVEVA AVEVA sample project SAM. SAM . •
The administr administrator ator also also has has the facili facility ty to easily load these these supplie supplied d example example data data files. files. They are accessible by clicking Input File which displays the File Browser form.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
12:3
12 Series
PDMS & Associated Products Installation Guide Configure Area Based ADP
Any data files must be loaded in the same order as shown in the Files list, since some elements rely upon the existence of other elements. To load a file, select the one the user wants to load from the Files list and click Apply. Repeat this until all of the necessary library files are loaded and click Dismiss.
Note: It is not possible to mix Metric and Imperial libraries since they utilise the same element names. If the user wants to mix them the user will need to modify the source data files. 5.
6.
In the SAM project load each of the following files in order by selecting them in the Files list and then click Apply.
sam_area-METRIC.datal
builds a series of example limit areas
sam_discipline.datal
builds a series of example disciplines
sam_keyplan-METRIC
builds the keyplans used by the relevant tasks
sam_tagrule.datal
builds a series of example tagrules
sam_template-METRIC.datal
builds a series of sample templates
For an Imperial project, load the substitute files marked IMPERIAL
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
12:4
12 Series
PDMS & Associated Products Installation Guide Configure Area Based ADP
Once these data files have been loaded, the user can run AB A and produce some drawings. ABA is now configured. Drafting administrators can now create the required administrative elements (areas, classifications, tasks, labels, and drawing templates) for use by DRAFT users. Refer to the ABA Administrator ABA Administrator and and User Guides for Guides for further information.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
12:5
12 Series
PDMS & Associated Products Installation Guide Configure Area Based ADP
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
12:6
12 Series
PDMS & Associated Products Installation Guide MDS Installed Configuration
13
MDS Installed Configuration MDS is installed directly into the main installation directory instead of being installed in a separate folder
Note: This is also the case for ABA As a result r esult of this change MDS is now run using the standard set of PDMS shortcuts that are installed for the main product. This means that if MDS has been installed then it will be available for a project design or outfitting session providing that the project has been set up for MDS use (as described in the administration guide) and there is a valid MDS license available to the user.
13.1 13.1
Manua Manuall Con Confi figu gurat ratio ion n of of the the Pr Prod oduct uct and Pr Prod oduct uct Environment Variables All MDS environment variables are set in the evars.bat file in the main installation directory. These are defined initially during the MDS installation process however. •
if the insta installe llerr wants wants to create create their their own own environ environment ment vari variabl able e files files
OR, if at the time of install, the following is true, •
any modif modifica icatio tions ns are made made to the the product product inter internal nal struc structur ture/na e/namin ming g (This product has the same internal structure/naming as the base product, eg,) ( …\product\pmllib has same function as …\base\pmllib )
then the evars need manual (re-)definition and must be modified as follows.
13.1 13.1.1 .1
Set Set Env Envir iron onme ment nt Varia ariabl bles es Environment variables modifications are made to the base product's files evars.bat from pdms.bat. Some of these environment variables can be "searchpaths". AVEVA AVEVA "searchpath" variables are modified from the initial setting %EnvVar%, using a blank* as the separator and usually PREfixing the new value, in the form.
Note: *If the installation of PDMS has been made into a directory with spaces in the path name i.e. c:\aveva plant then environment variable settings need to be modified to deal with space delimiters. This is out of scope for this document but more detailed information regarding this topic can be found in the PDMS install guide. SET EnvVar={newEnvVarValue} EnvVar={newEnvVarValue} %EnvVar2% %EnvVar%
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and its subsidiaries. subsidiaries. All rights reserved. reserved.
13:1
12 Series
PDMS & Associated Products Installation Guide MDS Installed Configuration
This will force items in newEnvVarValue newEnvVarValue to be used in preference to those in %EnvVar2% or %EnvVar% Searchpath variables need only be changed if the administrator wishes to include additional PML code paths to their installation or otherwise include alternative locations for known files.
13.1 13.1.2 .2
Modi Modifi fica catio tion n of Evar Evars. s.ba batt for for MDS MDS The following environment variables are set up for MDS in the standard product evars.bat file:
mdsplots
Folder containing the plot files of MDS standard support types.
Licadmdsexe
sets the executable location for the Licad software interface if used.
Pslmdsexe
sets the executable location for the PS designer software interface if used.
Cplmdsexe
sets the executable location for the Witchhanger software interface if used.
If the user modifies the pmllib configuration after the install, the first operation when first running the product is to select the Command window and run the command,
“pml rehash all” Note: Write access is required to the PMLLIB folders to enable the several pml.indx files to be updated.
13.1 13.1.3 .3
Envi En viro ronm nmen entt Var Varia iabl bles es for for Pr Proj ojec ects ts Except for the standard sample projects supplied with the products, the install cannot create the environment variables for users projects. When the user creates projects they must set these adding into one of, •
the user user's 's Enviro Environmen nmentt variab variables les set (not (not recom recommen mended) ded)
•
as instruc instructio tions ns in one of the startup startup batfil batfiles es
The standard installation of MDS installs all of the sample M DS projects into the same folder as the standard projects folder. Each of the sample projects (detailed in Projects Projects)) contains its own environment variable batch file (i.e. evarsMDS.bat) that is called from the standard evars.bat file.
13.1 13.1.4 .4
For For Pr Proj ojec ectts Use Used d wit with h MDS MDS Note: MDS defines two additional environment variables, 'mdsdflts' & 'mdsinfo', for the AVEVA AVEVA project folders …\MDS\mdsdflts and …\MDS\mdsinfo used by MDS. All other projects, which will be required to u se the MDS applications, will need to have the two extra folders created, and the relevant environment variables set to point to these two new directories in the relevant evars batch file, e.g. For a project called 'abc' create the two required folders by copying the …/MDS/ mdsdflts and …/MDS/mdsinfo folders to where the 'abc' project folders are located, and rename them accordingly, i.e. rename the copied folders mdsdflts and mdsinfo to abcdflts and abcinfo respectively.
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
13:2
12 Series
PDMS & Associated Products Installation Guide MDS Installed Configuration
Project Variables for MDS mdsreports
destination of the MDS report files.
Mds000
project MDS, 000 files
Mdsmac
project MDS, mac files
Mdspic
project MDS, pic files
Mdsiso
project MDS, iso files
Mdsdflts
project MDS, dflts files
Mdsinfo
project MDS, info files
and similar project environment variables for any other projects.
13.2
Projects
13.2 13.2.1 .1
Proj Pr ojec ects ts Rele Releas ased ed with with this this Pr Prod oduc uctt There are five standard projects released with the Multi Discipline Supports product, these are: CPL
Carpenter and Paterson Catalogue Project
LIS
LISEGA Catalogue Project
MDS
Multi Discipline Supports project containing the catalogue component, catalogue application defaults and the design databases for use with the MDS application
MDU
Multi Discipline Supports project containing the catalogue database for the User defined MDS Ancillaries available in 12
PSL
Pipe Supports Ltd Catalogue Project
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
13:3
12 Series
PDMS & Associated Products Installation Guide MDS Installed Configuration
© Copyright 1974 to current year. AVEVA AVEVA Solutions Limited and and its subsidiaries. All rights reserved. reserved.
13:4
12 Series
View more...
Comments
