PDMS Installation Guide
PDMS Installation Guide
Version 11.6.SP1
Windows 2000 and Windows XP
This manual provides documentation relating to products to which you may not have
access or which may not be licensed to you. For further information on which Products
are licensed to you please refer to your licence conditions.
All rights reserved. No part of this document may be reproduced, stored in a retrieval
system or transmitted, in any form or by any means, electronic, mechanical,
photocopying, recording or otherwise, without prior written permission of AVEVA
Solutions.
The software programs described in this document are confidential information and
proprietary products of AVEVA Solutions or its licensors.
For details of AVEVA's worldwide sales and support offices, see our website at
http://www.aveva.com
AVEVA SolutionsEMail:[email protected]
www.cadfamily.com Ltd, High Cross, Madingley Road, Cambridge CB3 0HB, UK
The document is for study only,if tort to your rights,please inform us,we will delete
Revision History
10 Troubleshooting...........................................................................................10-1
10.1 General...............................................................................................10-1
10.2 License Manager Errors ....................................................................10-1
10.3 Entering PDMS .................................................................................10-2
10.4 Problems with Graphics ....................................................................10-3
The document is for study only,if tort to your rights,please inform us,we will delete
Contents
This guide explains how to install and set up PDMS Version 11.6.SP1 on
a workstation running the Microsoft Windows 2000 or Windows XP
operating system (hereafter referred to jointly as 'Windows'). Local
Administrator rights are required to perform the installation.
This guide assumes you are familiar with the concepts of folder/file
hierarchies for storing data on disks and with basic Windows
terminology and commands. If you are not, you may also need to refer to
your operating system documentation while you carry out the
installation.
The guide also assumes that you have already gained access to the
PDMS installation files via a CD, from the AVEVA Web site, or by some
other route.
The document is for study only,if tort to your rights,please inform us,we will delete
2 Hardware and Software Requirements
2.1 Hardware
1
PDMS 11.6 will run on Windows XP SP2, but requires changes to the default settings. The Internet
Connection Firewall (ICF) should be turned off or configured to ensure access to the database server.
In addition, Group Policy changes (which alter the registry) are required for VANTAGE Plant Design
Global to ensure that RPC requests do not require authentication. Details are given in the Global
Installation Guide.
The document is for study only,if tort to your rights,please inform us,we will delete
3 Installing PDMS
You must install and set up the FLEXMAN license system before PDMS
can be used. This will usually be done only on the server. Please see the
FLEXMAN Installation Guide. News and update information is also
available for FLEXMAN on the AVEVA support web-site.
The document is for study only,if tort to your rights,please inform us,we will delete
Installing PDMS
If you wish to have one server installation of PDMS accessed from remote
workstations, you must ensure that the Windows system DLLs on each
remote workstation are upgraded to a suitable version for running the
PDMS 11.6.SP1 application programs. You can achieve this by installing
PDMS 11.6.SP1 itself in minimal form; that is, select the Custom
Installation type and then deselect everything except 'PDMS Core
Components'.
In addition, this release includes a stand-alone 'Thin Client' installer
which can be used on individual workstations to update the necessary
Windows system DLLs, and which also provides start menu shortcuts to
the main PDMS installation.
The Thin Client installer is a self-extracting InstallShield® executable
which is held in the C:\AVEVA\PDMS11.6.SP1\thin_client_installer\
subfolder. It is applicable when the main PDMS 11.6.SP1 product is
installed either from the 'Full Installation' option or the 'Custom
Installation' option with the 'Thin Client Installer' component selected.
The document is for study only,if tort to your rights,please inform us,we will delete
4 Setting Up the Windows Environment
The Windows Control Panel contains tools that are used to change the
way Windows looks and behaves. This Install Guide describes how to use
Control Panel tools to configure Windows to run PDMS.
Open the Control Panel as follows:
Windows 2000
Click Start, point to Settings, and then click Control Panel
Windows XP
If your computer is set up with the Classic Start menu, click Start,
point to Settings, and then click Control Panel.
If your computer is set up with the standard Start menu, click Start
and then click Control Panel.
You should set your display to a resolution of at least 1024 x 768 and the
colour depth to True colour or 16.7 million colours.
This can be set by opening the Control Panel. Select Display and select the
Settings tab. Make the appropriate selections on the form for your
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
Support Web pages (http://www.aveva.com/engineeringit) contain a
current list of both tested and supported graphics cards, along with
advice on configuration of graphics device drivers.
Before you can use PDMS, you must set up the FLEXMAN license
system and connect to the FLEXMAN License Manager daemon (see the
FLEXMAN Installation Guide).
Each User needs to set a license path that defines the location of the
license file or service. For earlier versions of FLEXMAN, setting the
environment variable LM_LICENSE_FILE did this. However, this
applied to all software using FLEXlm. You can now set
CADCENTRE_LICENSE_FILE instead that applies only to software
using our Vendor License Manager Daemon.
To avoid users having to repeatedly set such an environment variable,
FLEXlm itself now remembers the current setting in the Windows
Registry. This Registry setting will initially come from the value of the
corresponding environment variable, but cannot then be modified by
changing the environment variable – you must use the FLEXlm utility
lmtools or the new command-line lmpath to query or set the license
path. These utilities are installed with FLEXMAN.
The environment variable can be set in one of three ways, either in the
PDMS entry script, as a User Environment Variable in the Control Panel
or manually in a command window.
To set manually or in the PDMS entry script, type the following in a
command window or in the entry script before starting PDMS:
set CADCENTRE_LICENSE_FILE=Port@Computername
The document is for study only,if tort to your rights,please inform us,we will delete
Setting Up the Windows Environment
To set automatically:
Windows 2000 and Windows XP
• Open the Control Panel.
• Select System, and pick the Advanced tab
• Click on the Environment Variables button
• Set the CADCENTRE_LICENSE_FILE user environment
variable to the location of the license obtained from AVEVA
(Port@Computername). For example:
CADCENTRE_LICENSE_FILE
744@licserv
To confirm the licence environment variable setting, open a command
window and type the command SET. You should see a list of
environment variables, including:
CADCENTRE_LICENSE_FILE=Port@Computername
To check the Registry setting, you will need to use the FLEXMAN utility
lmpath –status
You should see an output including the following:
The document is for study only,if tort to your rights,please inform us,we will delete
Setting Up the Windows Environment
but they should have their own local defaults area. This is
achieved by setting a PDMSDFLTS search path, e.g.
‘C:\USERDFLTS C:\AVEVA\pdms11.6.SP1\pdmsui\dflts’
Project Environment Variables
For each PDMS project, four more 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
PDMS is installed with sample project data (See Chapter 7 PDMS
Projects). PDMS Project Environment variables for these projects are set
in evars.bat.
You can run PDMS from a Command Prompt window rather than using
the Start/Programs menu. To do this you must set your PATH variable
to include the folder where PDMS is installed.
Windows 2000 and Windows XP
• Open the Control Panel.
• Select System, and pick the Advanced tab.
• Click on the Environment Variables button.
• Edit the system variable Path to add the PDMS folder (for example,
C:\AVEVA\pdms11.6.SP1) to the list of folders in the Path
variable.
Once the Path variable includes the pdms11.6.SP1 folder, you can run
PDMS by typing pdms at a command prompt.
• You can create a shortcut on your desktop to run your batch file.
With the cursor in the desktop area, click with the right-hand
button and select New>Shortcut. This shows a sequence of dialogs to
help you create the shortcut. Type in the location of pdms.bat, for
example:
C:\AVEVA\pdms11.6.SP1\pdms.bat
then press Next and give the shortcut a name.
Press Finish.
You should now be able to double-click on the shortcut icon to enter
PDMS.
• If you have C:\AVEVA\pdms11.6.SP1(the path name for the
pdms.bat file) in your PATH environment variable, just type pdms
in a command window to execute the batch file.
• Otherwise, navigate to the folder where the batch file is stored and
type pdms or pdms.bat.
You can set up your own batch files to run PDMS. For example, you may
wish 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:\AVEVA\pdms11.6.SP1\pdms.bat TTY SAM SYSTEM/XXXXXX /STRUC
$M/mymacrofile
Where:
• TTY tells PDMS not to start the PDMS GUI. This gives command line
only operation.
• SAM is the project name.
• SYSTEM/XXXXXX is the PDMS username/password to be used
when running the command macro
• /STRUC selects the required MDB
• mymacrofile is the pathname of a PDMS command macro, containing
the commands that you want to execute in 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.
The document is for study only,if tort to your rights,please inform us,we will delete
Setting Up the Windows Environment
4.8 Plotting
Where options are the AVEVA PLOT utility options, and may be omitted.
See the PLOT User Guide for more information. Note that the options
must be enclosed in quotes.
For example:
plotcadc.bat c:\pdms\plot1 ps \\ntserver\NTPostScript
plotcadc.bat c:\pdms\plot1 hpgl \\ntserver\NThpgl 'CE=Y'
The document is for study only,if tort to your rights,please inform us,we will delete
5 Language Support
By default, your PDMS project can use any language whose characters
are contained within the Latin-1 character set. The Languages covered
by the Latin-1 character set a listed in the table below. If you want to use
any of the other, non-Latin-1 languages supported by PDMS, it is
necessary to configure your PDMS project and the Windows operating
system. This chapter describes how to use PDMS on Windows 2000 and
Windows XP Professional in each of the supported language groups:
• Latin-1
• Latin-2
• Latin-Cyrillic
• Far Eastern
Supported languages
PDMS does not support any other language character set, nor does it
support the mixing of any of the above, except for mixing one Far
Eastern language with English.
5.1.2 Windows XP
To add an additional language in Windows XP, follow these steps:
1. Open the Control Panel.
2. Double-click Regional and Language Options.
3. On the Regional options tab, under “Standards and formats”,
select the required language from the list.
4. Click the Languages tab, and then click Details under "Text
services and input languages".
5. Under “Default input language”, select the required language. If
the required language appears in the list, click OK.
If it does not appear in the list, then click Add under "Installed
Services", and then click the language you want to add and the
keyboard layout you want to use for that language.
To configure the settings for the Language bar, click Language
Bar under "Preferences". The Language bar is used to switch
between languages while you are using PDMS. Click OK to close
the Language Bar Settings dialog.
Click OK to close the “Text Services and Input Languages” dialog.
The document is for study only,if tort to your rights,please inform us,we will delete
Language Support
In PDMS ADMIN, you must specify a character set for each project by
using one of the following commands on the PDMS ADMIN command
line:
The corresponding font family must be selected for Draft and Isodraft
drawings. Use Project>Font Families and select the Font Type appropriate
for you chosen language.
For details, see the VANTAGE PDMS ADMIN User Guide and
VANTAGE PDMS ADMIN Command Reference Manual.
You must ensure that your licence file is for the language version you
require.
Before you use PDMS, you must set the environment variable
CADC_LANG as follows:
CADC_LANG=Japanese Kanji
CADC_LANG=Korean
CADC_LANG=Chinese Simplified Chinese
CADC_LANG= TChinese Traditional Chinese
In PDMS ADMIN, you must specify the multibyte character set for each
project by using the command corresponding to your required language:
PROJECT MBCHARSET JAP
PROJECT MBCHARSET KOR FILE /<font filename>
PROJECT MBCHARSET CHI Simplified Chinese
PROJECT MBCHARSET TCHIN FILE /<font filename>
Traditional Chinese
For details, see the VANTAGE PDMS ADMIN User Guide and
VANTAGE PDMS ADMIN Command Reference Manual.
The document is for study only,if tort to your rights,please inform us,we will delete
6 Running PDMS under Windows
To run macros with spaces in the filenames, you must enclose the
filename in quotes, without a leading slash. For example:
$m'c:\Program Files\Macros\space.mac' arg1 arg2
Due to the way in which PDMS parses its command lines, this format is
also recommended for use with filenames containing Asian characters.
You can make your reports load directly into a Microsoft Excel
spreadsheet, as comma-separated files:
• Select Utilities>Reports>Modify from the PDMS main menu bar.
• Pick a report template.
• Click on OK: the Modify Template form is displayed.
• Select Options>Other Formats... from the Modify Template form menu
bar. This displays the Report Format form. From this form:
• Choose the CSV option from the Format drop-down list.
• Click on OK: this returns you to the Modify Template form.
• Select the Overwrite radio button
• For the filename enter %PDMSUSER%/fname.csv (the .csv
extension is important).
• In the System command text box enter
'cmd/c “C:\<excel folder>\excel.exe” %PDMSUSER%\fname.csv'
where C:\<excel folder> is the location of Excel on your system.
Note that it is necessary to enclose Windows command arguments
in double quotation marks if the argument contains embedded
spaces. :\<excel folder>\
The document is for study only,if tort to your rights,please inform us,we will delete
7 PDMS Projects
The project files are held in two directories: sam000 holds all design
data and catalogue data; sampic holds the DRAFT picture libraries.
Free User
The Free user has username/password SYSTEM/XXXXXX.
General Users
Team Username/password
CATS CATS/CATS
DEMO DEMO/DEMO
EQUI EQUI/EQUI
HANGER HANGER/HANGER
HVAC HVAC/HVAC
PIPE PIPE/PIPE
SAMPLE SAMPLE/SAMPLE
STRUC STRUC/STRUC
USERA USERA/A
USERB USERB/B
USERC USERCC
USERD USERD/D
USERE USERE/E
USERF USERF/F
USERG USERG/G
The document is for study only,if tort to your rights,please inform us,we will delete
PDMS Projects
For full information on setting up your own projects, see the VANTAGE
PDMS ADMIN User Guide.
You will need to create project folders for each project; for example, for a
project xyz:
md xyz000
md xyzpic
md xyziso
md xyzmac
Set the corresponding environment variables that point to these
directories. You can do this by setting Environment Variables using the
Control Panel, or by modifying the evars.bat file used to configure
your PDMS Windows installation. (see Chapter 4, Setting Up the
Windows Environment, for further details). Alternatively, type the
following in an MS-DOS window:
set XYZ000=pathname\xyz000
set XYZPIC=pathname\xyzpic
set XYZISO=pathname\xyziso
set XYZMAC=pathname\xyzmac
Note: Users converting from UNIX should note that there is no direct
equivalent of the .cshrc file in which these variables can be set.
Use the 'Make PDMS project' icon supplied to start the PDMS Make
program, then enter:
XYZ
$m/%PDMSEXE%/makemac.mac
FINISH
Note: Users converting from UNIX should note that the makemac.mac
file is the same as on UNIX. The executable for each module is
also named identically to that on UNIX, e.g. DESIGN runs
%PDMSEXE%/des. The extension '.exe' needed by Windows is
added automatically.
The document is for study only,if tort to your rights,please inform us,we will delete
8 Installing AutoDRAFT
8.1 Compatibility
The document is for study only,if tort to your rights,please inform us,we will delete
Installing AutoDRAFT
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.
The document is for study only,if tort to your rights,please inform us,we will delete
9 Upgrading Projects to Version 11.6.SP1
The document is for study only,if tort to your rights,please inform us,we will delete
10 Troubleshooting
Here are some suggestions about solving some problems you may
encounter when using PDMS under Windows.
10.1 General
Error: The dynamic link library DFORMD.dll could not be found in the
specified path.
Explanation: This is supplied with PDMS. Perhaps you have not set your PATH
variable. The PATH setting must include ‘C:\AVEVA\pdms11.6.SP1’.
Error: When you start up lmgrd it says <time> (lmgrd) Can't make folder
C:\FLEXlm, errno: 2 No such file or folder, etc.
Solution: There is no C: drive for the license manager to write to. As the System
Administrator or a Power User, you need to make a shared disk called
C:. This can be done on a networked or non-networked computer.
Within the Windows Explorer’s File menu, create a new folder (e.g.
D:\C_drive) and make it current. Select File>Properties and select
the Share tab. Click on the Shared As: radio button and then click OK.
Then from the Tools menu select Map Network Drive. Select C: from
the Drive: drop-down list in the displayed form and type
\\hostname\C_drive
in the Path box. Then click on OK. (C:) should now appear in the list of
available drives in Explorer.
Pop-up Mess.: FLEXlm: checkout failed: Cannot connect to license server (-15,
10:10061) WinSock error code.
Explanation: lmgrd has not been started up - see above for details.
Pop-up Mess.: FlexLM: checkout failed: Cannot find license file (-1,73:2) No such file
or folder.
Explanation: lmgrd has not been started up - see above for details.
Pop-up Mess.: FlexLM: checkout failed: Licensed number of users already reached
(-4,132).
Explanation: You have exceeded the permitted number of users specified in your
license file.
The document is for study only,if tort to your rights,please inform us,we will delete
Troubleshooting
The document is for study only,if tort to your rights,please inform us,we will delete
11 Structure of PDMS on .NET
From PDMS 11.6.SP1, the GUI uses the Microsoft .NET environment including
the latest WinForms based user interface components. Using this state-of-the-
art technology enables docking forms and toolbars in PDMS and provides a
robust foundation for the future provision of standard application programming
interfaces.
This does affect the way PDMS is installed: this section gives a brief overview
and the following one outlines how to troubleshoot the installation.
11.1 Overview
This section describes the overall structure and components of the PDMS .NET
installation, and the environment necessary to run it. Each PDMS GUI module
now consists of a thin .NET exe, a .NET Wrapper DLL and a Win32 DLL plus
some other shared components including 3rd party controls from Infragistics.
The .NET components are private assemblies installed under the root directory
%PDMSEXE%.
11.2 PDMSEXE
Each GUI module is structured in the same way. For Design the structure looks
like this
des.exe
Wrappers.dll
des.dll
where des.exe and des.dll live in the directory %PDMSEXE% and Wrappers.dll
lives in the Design subdirectory below %PDMSEXE%. So, when running a PDMS
GUI module %PDMSEXE% is used to locate the executable, .NET loading rules
are used to load Wrappers.dll and Win32 DLL loading rules are used to load
des.dll (and other Win32 DLLs on which des.dll depends).
11.3.1 Wrappers
For each GUI module (Design, Draft, Admin, Isodraft and Monitor) there is a
Wrappers.dll in a subdirectory with the same name as the module. Each
Wrapper.dll has a dynamic link to the appropriate Win32 DLL for that module.
.NET loading rules are used to load the appropriate Wrappers.dll for a given
module. So, when running des.exe, the version of Wrappers.dll linked with
des.dll will be loaded. Design and Draft subdirectories also contain a
drawlistWrapper dll which is used by the Drawlist add-in.
The document is for study only,if tort to your rights,please inform us,we will delete
Structure of PDMS on .NET
11.4 Components
Design/Spooler
des.exe, des.dll, des.exe.config, des.exe.manifest, DesignAddins.xml,
SpoolerAddins.xml
Draft
dra.exe, dra.dll, dra.exe.config, dra.exe.manifest, DraftAddins.xml
Monitor
mon.exe, mon.dll, mon.exe.config, mon.exe.manifest
Isodraft
iss.exe, iss.dll, iss.exe.config, iss.exe.manifest, IsodraftAddins.xml
Admin
adm.exe, adm.dll, adm.exe.config, adm.exe.manifest
Shared
Depends.dll, DrawList.dll, DrawListAddin.dll, ExplorerAddin.dll,
ExplorerControl.dll, ForeignLanguage.dll, HistoryAddIn.dll, MyDataAddIn.dll,
ReferenceListAddin.dll, PDMSCommands.dll, PDMSFilters.dll,
PDMSResources.dll, PDMSResources.resources, StartUp.dll,
ApplicationFramework.dll, udNet.dll, DruidNet.dll
Infragistics
This is a third-party GUI tool-kit:
Infragistics.Shared.v3.dll, Infragistics.Win.UltraWinDock.v3.dll,
Infragistics.Win.UltraWinExplorerBar.v3.dll,
Infragistics.Win.UltraWinGrid.v3.dll,
Infragistics.Win.UltraWinStatusBar.v3.dll,
Infragistics.Win.UltraWinTabbedMdi.v3.dll,
Infragistics.Win.UltraWinTabControl.v3.dll,
Infragistics.Win.UltraWinToolbars.v3.dll, Infragistics.Win.UltraWinTree.v3.dll,
Infragistics.Win.v3.dll, Infragistics.Win.Misc.v3.dll
System
msvcp71.dll, msvcr71.dll
The document is for study only,if tort to your rights,please inform us,we will delete
Structure of PDMS on .NET
11.4.7 Add-ins
These new user interface .NET components are loaded by the Application
Framework. Each module has an addin file which defines the set of add-ins it
will load, e.g. for Design this file is DesignAddins.xml. The toolbar entries to
show and hide each add-in are defined in PML.
Most of the User Interface is still defined in PML located in %PMLLIB% and
%PDMSUI%.
The document is for study only,if tort to your rights,please inform us,we will delete
12 Troubleshooting the .NET installation
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
<module>.exe.config to see whether it contains any path hints. Path hints are stored
in the <probing> element. So, for example, des.exe.config has the following probing
path <probing privatePath="Design" />. This means that Wrappers.dll is loaded
from the subdirectory Design below the application directory. Each Wrappers.dll
depends on the given modules Win32 DLL e.g. Design’s Wrappers.dll found in the
Design subdirectory depends on des.dll. Win32 DLL loading rules apply here. These
are
• The directory from which the importing component loaded. (i.e. the Design
subdirectory where Wrappers.dll is loaded in the case of Design)
• The Windows directory (default: C:\Windows) (we don’t install anything here)
Since the module DLL does not live in the same directory as the Wrappers.dll then
unless PDMS is running from %PDMSEXE% the %PATH% will be used to locate
the module DLL. (The Wrappers.dll subdirectory is effectively is the directory which
is first looked in for all the Win32 DLL’s which Wrappers depends on i.e.
<module>.dll, sglNet.dll, udDNet.dll, …)
Make sure that both %PDMSEXE% and %PATH% point to the root directory in
which PDMS is installed.
Error:
An exception ‘System.MissingMethodException’ has occurred in mon.exe
Or
An exception ‘System.IO.FileNotFoundException’ has occurred in mon.exe
Additional information: A procedure imported by 'Wrappers' could not be loaded.
Solution: .NET security gets in the way when running PDMS across the network
where the 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. However this means that any
.NET assembly may run. Alternatively, Full Trust may be given to a specified group
of strongly named assemblies. This is done using the code access security policy tool
caspol. This should be 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.
If the security Policy has not been set, this can be done by hand using:
The document is for study only,if tort to your rights,please inform us,we will delete
Troubleshooting the .NET installation
Or
If you are not concerned about other .NET remote assemblies running on your
machine, this can be set for the entire intranet using:
Control Panel>Administrative Tools>Microsoft .Net Framework 1.1
Configuration>Configure Code Access Security Policy>Adjust Zone Security>Make
changes to this computer
Then change Local Intranet to Full Trust
12.5 No Add-ins
Problem: Window layout is not restored e.g. Add-ins position and/or docked
state, …
Solution: The file <module><version>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.
12.7 Serialization
Serialization is the process used to store the data – e.g. history stacks, toolbar state
– for the GUI in a .NET environment.
Problem: Information is stored per project and per module in the following files
in the %PDMSUSER% directory:
<project><version>Settings.bin
<module><version>Settings.bin.
Solution: These files may be deleted or transferred between users working on the
same project.
The document is for study only,if tort to your rights,please inform us,we will delete