Model Management Installation Guide - cadfamily.com€¦ · For the installation of Clash Manager...

Model Management

Installation Guide

DisclaimerInformation of a technical nature, and particulars of the product and its use, is given by AVEVASolutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaimany and all warranties and conditions, expressed or implied, to the fullest extent permitted by law.

Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person orentity for any actions, claims, loss or damage arising from the use or possession of any information,particulars, or errors in this publication, or any incorrect use of the product, whatsoever.

CopyrightCopyright and all other intellectual property rights in this manual and the associated software, and everypart of it (including source code, object code, any data contained in it, the manual and any otherdocumentation supplied with it) belongs to AVEVA Solutions Ltd or its subsidiaries.

All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained inthis document is commercially sensitive, and shall not be copied, reproduced, stored in a retrievalsystem, or transmitted without the prior written permission of AVEVA Solutions Ltd Where suchpermission is granted, it expressly requires that this Disclaimer and Copyright notice is prominentlydisplayed at the beginning of every copy that is made.

The manual and associated documentation may not be adapted, reproduced, or copied, in any materialor electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also notreverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of theproduct described in this publication may be incorporated into any third-party software, product,machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted bylaw. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminalprosecution.

The AVEVA products described in this guide are to be installed and operated strictly in accordance withthe terms and conditions of the respective licence agreements, and in accordance with the relevantUser Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.

First published September 2007

© AVEVA Solutions Ltd, and its subsidiaries 2007

AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom

TrademarksAVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthoriseduse of the AVEVA or Tribon trademarks is strictly forbidden.

AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or itssubsidiaries, registered in the UK, Europe and other countries (worldwide).

The copyright, trade mark rights, or other intellectual property rights in any other product, its name orlogo belongs to its respective owner.

AVEVA Solutions Ltd

Model Management Installation Guide

Contents Page


Model ManagementIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Purpose of this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Model Management Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1Overview of Model Management Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2Structure of this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Environment Required for Model Management . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:2

Installing Model Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1Sequence for Installing Model Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1How the Model Management Products are Supplied . . . . . . . . . . . . . . . . . . . . . 3:1Installation - the Basic Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:1Previous Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2Installing with Setup.exe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2Locating the Installation on the DVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2

Installing from the AVEVA Support Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:2Running the Setup File to Install a Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:3Clash Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:7Custom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9Disk Space Requirements Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9

12.0i© 2007 AVEVA Solutions Ltd


Plant or Marine Connection Sample Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:10Installing Model Management Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3:12

Connecting and Configuring the Model Management Product Soft-ware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1PDMS Without Model Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1Adding the Model Management Products to PDMS . . . . . . . . . . . . . . . . . . . . . . 4:1Starting Model Management without PDMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2Model Management Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:2

Model Management Sample Project . . . . . . . . . . . . . . . . . . . . . . . . . 5:1

Summary Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . .A:1Installing the Environment and Products for Model Management Operation .A:1Actions to Install and Setup to Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A:1After Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A:2

Default Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B:1

Help with Oracle Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C:1Installing Oracle 10g (10.1.0.2) Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C:1Additional Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:1

Checking the Oracle Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C:2Checking if a connection exists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:2Checking if SQL Plus Can Use the Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:3

Summary Explanation of Entries (& Nomenclature) in Oracle Definition Files C:4sqlnet.ora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:4tnsnames.ora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C:4

Installing Deliverable Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C:5

Help with MS SQL Server Activities . . . . . . . . . . . . . . . . . . . . . . . . .D:1

Changed Environment Variables for each Product . . . . . . . . . . . . .E:1Model Object Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E:1Connectivity Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E:1Clash Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E:1Deliverable Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E:1PLOT Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E:2

12.0ii© 2007 AVEVA Solutions Ltd


Model Management Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E:2Area-Based ADP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E:2Multi-Discipline Supports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E:2Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E:2batfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E:3

Alternative Methods of Installing Model Management Products . .F:1Installation and Uninstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F:1Silent/Unattended Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F:2MSI Command Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F:2

Testing the Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F:3Installed Model Management Setup Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F:3Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F:4

Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F:4Optional Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F:4Feature Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F:5Installation Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F:6

Checking Product/Version Installation . . . . . . . . . . . . . . . . . . . . . . G:1

Installing for Untested (e.g. Foreign Windows) Environments. . . .H:1General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .H:1Completing the Installation for your Windows System . . . . . . . . . . . . . . . . . . .H:2“Support” Folder after Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .H:2Validated Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H:2Unsupported Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H:2Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H:3WARNING - “Unsupported Windows” Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H:3

12.0iii© 2007 AVEVA Solutions Ltd

Model Management Installation GuideIntroduction

1 Introduction

1.1 Purpose of this GuideThis guide is intended for IT managers and support staff who are planning to implementAVEVA Model Management. It describes the installation and software configuration ofModel Management, a suite of products, on a user workstation.

This guide assumes that the Plant Design Management System (PDMS) and PlantEngineering Workbench (PE Workbench) products have already been installed. It alsoassumes some understanding of the configuration of PDMS - particularly the use ofenvironment variables and searchpaths.

For the installation of Clash Manager onto an AVEVA Marine system, this guide assumesthat Marine Outfitting has already been installed.

If you are already familiar with PDMS installations and PE Workbench installations, you maybe able to satisfactorily complete the Model Management installation following the summarygiven in Summary Installation Instructions.

If you are not familiar with these installations, you are strongly advised to read Chapters 1-5of this Guide before starting installation.

Note: The licensing of Model Management products is managed by AVEVA’s Flexmansecurity system. A separate licence key must be obtained from AVEVA for each ofthe Model Management products.

1.2 Model Management ProductModel Management is a suite of products that provides facilities for controlling data relatedto engineering objects designed in 3D using PDMS. The facilities encompass creating andmaintaining the PDMS data from 2D engineering data for lines, equipment and instruments,as input using PE Workbench.

The standard Model Management installation contains four products:• Model Object Manager (AVEVA Plant)• Connectivity Manager (AVEVA Plant)• Clash Manager (AVEVA Plant and Marine)• Deliverable Manager (AVEVA Plant)

Model Object Manager, Connectivity Manager and Deliverable Manager interact with PEWorkbench and PDMS. These products require both PE Workbench and PDMS to beinstalled in order for them to be installable and for them to have a function. PE Workbenchrequires an Oracle installation.

12.0 1:1© 2007 AVEVA Solutions Ltd


Clash Manager requires a limited subset of PE Workbench. If PE Workbench is not presentwhen installing Clash Manager, running the Model Management Wizard provides therequired subset of PE Workbench. Refer to Model Management Configuration Guide. ClashManager however, still require that Oracle or MS SQL Server has been installed before itcan be installed itself.

Deliverable Manager requires the presence of the PE Workbench. PLOT Viewer is alsorequired but is deployed during the installation of Deliverable Manager. It is also dependenton functionality only available in Model Object Manager. See also Installing DeliverableManager for a special note on the installation of Deliverable Manager.

In addition to the standard Model Management products, AVEVA Engineering IT can providerelated optional products. Examples of such products are:

• Area-Based Automatic Drawing Production (Area-Based ADP)• Multi-Discipline Supports (MDS).

Note: PDMS must be present in order for the above products to be installable.MDS uses Area-Based ADP

There is an installation sequence for these products, because the installation of someproducts depends on the presence of the other products.

Note: For further details of the installation of MDS and Area-Based ADP, see the InstallGuides for each of those products.

1.3 Overview of Model Management InstallationInstallation of Model Management has three major streams:

1. Install the base environment required for Model Management.2. Install and configure the product software by installing the individual software products

that make up Model Management. Then connect and configure these individualproducts to form Model Management.

3. Create and configure projects data and connections. To do this, create and configureprojects in PE Workbench, PDMS and Model Management. Then declare the projectsfor Model Management use with PDMS.

Configuring and declaring project items so that Model Management can function is achievedthrough a combination of registry entries and setting environment variables (eitherpermanently or at run time). More information on the first two of these stages is given in laterChapters of this Guide, and/or in the Appendices. Stage 3 is described in the ModelManagement Configuration Guide.

1.4 Structure of this GuideThis guide does not describe Oracle, MS SQL Server, PE Workbench, PDMS and MarineOutfitting installations - they are considered to be pre-requisites for a Model Managementinstallation. Details of these installations can be found in the Installation Guides for each ofthose products.

Prerequisites describes the environment required for a successful installation of ModelManagement.

Installing Model Management describes the recommended method of installing the ModelManagement System products on an individual workstation. An alternative method of



installing the Model Management System products from a central location is presented inAlternative Methods of Installing Model Management Products.

Connecting and Configuring the Model Management Product Software describes how PEWorkbench, PDMS and the Model Management product software are combined to form aModel Management system.

Summary Installation Instructions is a summary of the Installation process for ModelManagement. The default locations for installation are presented in Default Locations.


Model Management Installation GuidePrerequisites

2 Prerequisites

2.1 Environment Required for Model ManagementIn addition to the Windows operating system, other AVEVA and non-AVEVA products arerequired for the operating environment for Model Management.

For Model Object Manager Users:• Oracle• PDMS• PE Workbench• PE P&ID

For Connectivity Manager users:• Oracle• PDMS• PE Workbench• A Browser• PE P&ID

For Plant Deliverable Manager users:• Oracle• PDMS• PE Workbench• PLOTViewer

For Clash Manager users:• Oracle or MS SQL Server• PDMS (Plant) or Outfitting (Marine)

For Model Management Administrators (Model Management Wizard,MMSCMD):• Microsoft Excel

PE Workbench is implemented using the Oracle three-tier architecture, which consists ofthe components:

• Database Server - which runs the Oracle database and contains PE Workbench dataand a portion of the PE Workbench application

• Internet Application Server - which runs the Oracle iAS product and has the bulk of thePE Workbench application logic. The Internet Application Server, sometimes called theMiddle Tier, communicates with the Database server via the Oracle Net9 protocol.

• User Workstation - which communicates with the Internet Application Server using adirect socket connection.


Model Management Installation GuidePrerequisites

2.2 PreparationBefore starting to install Model Management, make sure that you have installed:

1. Oracle (V9 or V10) or MS SQL Server 2005 as the database server.2. PE Workbench 5.6 on the Internet Application Server.

For each workstation:

1. Make sure the Internet Application Server is visible from the workstation2. Make sure either Oracle 10g (10.1.0.2 Client with patch 10.1.05), including Application

User option with Oracle Windows Interfaces, is present.

Note: AVEVA recommends Oracle 10g client with Oracle 10 database (PE 5.6).

3. Make sure Microsoft Data Access - OLE DB Provider for Oracle is present4. Make sure that the Oracle runtime library path is in the %path% environment variable.

The file tnsnames.ora needs to contain Oracle connect path (connect string andserver).

5. If you intend using direct web-based forms access to PE Workbench, install Jinitiator.Newer versions of PE & VPRM install Jinitiator on first use.

6. In non-English environments, install MDAC 2.6 or later (For English environments, ifthe Model Management install does not detect MDAC 2.6 or later on the workstation, itwill be installed during the Model Management installation).

7. In non-English environments, install XML Parser 3 or later (For English environments, ifthe Model Management install does not detect XML Parser 3 or later on theworkstation, it will be installed during the Model Management installation).

8. Install PDMS 12.0.9. When installing for a Model Management/PDMS Project Administrator (Model

Management Wizard, MMSCMD), install Microsoft Excel.


Model Management Installation GuideInstalling Model Management

3 Installing Model Management

All the products in the Model Management group are compatible with PDMS. StandaloneClash Manager can be installed separately for either PDMS or Marine Outfitting.

The process of installing each of the Model Management standard products involvescopying files to a suitable location on the workstation and making appropriate records of filelocations.

3.1 Sequence for Installing Model Management Any combination of Model Management products can be installed except that:

• Multi-Discipline Supports uses Area-Based ADP to create drawings.

AVEVA recommend that those products that are to be installed are installed in the followingorder:

1. Model Management products2. Area-Based ADP3. Multi-Discipline Supports

The install procedures for each of the Model Management products are very similar, butthere are minor differences between products.

3.2 How the Model Management Products are SuppliedThe Model Management products may be delivered together on one DVD or on a number ofDVD or, often for upgrades, via the AVEVA Support website.

3.3 Installation - the Basic Steps

3.3.1 OverviewThe Model Management suite can be installed before or after any dependant applications.The installation has been designed not to fail, so that silent installations become morerobust, and installation failures can be separated from other issues.

Model Management applications have enhanced self diagnostics features to help diagnoseexternal (Non-Model Management) issues.



3.3.2 Previous InstallationsAll previous versions of Model Management need to be un-installed before installing ModelManagement 12.0.

During installation Model Management 12.0 does not uninstall previous versions however,previous versions are not compatible with Model Management 12.0, and this installation hasbeen designed to fail if it detects a previous Model Management installation on the system.

3.3.3 Installing with Setup.exeSetup.exe supports non silent installations and is the easiest way to begin an installation.However, the MSI can be run directly, in the usual manner for an MSI.

3.3.4 Locating the Installation on the DVDIf using the DVD directly on a workstation where ‘autorun’ is not enabled you will need tolocate the product’s setup.exe using Explorer.

The steps you need to take are:

1. Open a Windows Explorer.2. Load the DVD, and select the DVD drive folder (usually D:)3. Select the int folder, then the install folder {tnnnnn} for the product of interest, as

listed in the aareadme.txt file.4. In the product folder, {product_code}{version}, below the int folder, you should

find a file setup.exe.5. Either execute this file from the DVD, or copy the complete setup folder onto the

workstation and run setup.exe from there.6. Alternatively, run start.htm in the root folder of the DVD.7. Click on Contents of DVD. This will display a list of the products on the DVD.8. Click on the product you wish to install (e.g. Model Management 12.0). The Release

Documents screen for the product will be displayed.9. Read the Release Notes for any specific installation instructions. This is important, as

there may be release-specific instructions in the Release Notes.10. Click INSTALL. You will be offered a choice of installing directly from the DVD or

downloading a setup.exe file from the DVD.11. If you decide to download setup.exe then click Save on the File Download dialog box.12. Use the Save As dialog box to specify a folder where the product’s setup.exe file will

be stored, then click Save.

3.4 Installing from the AVEVA Support Web SiteOnly product updates are available for downloading from the AVEVA Support website. If aproduct update is delivered to you via the AVEVA Support website, then the Release Letteryou receive will inform you of the location of the self-extracting file containing the product.You need to:

1. Copy the self-extracting file from the website onto your workstation.2. Extract the contents. 3. Locate setup.exe as directed in the Release Letter.



3.5 Running the Setup File to Install a ProductTo install a product:

Navigate to the product’s ModelManagement.msi file and double-click it.

The Model Management Setup Wizard activates at this point and guides you through theinstallation of the product.

Before attempting to install any of the product software, a Software Audit of the targetcomputer will determine if the minimum required environment is present. Note that ModelManagement installation checks the location of PDMS from a registry entry. PDMS does nothave to be located on the workstation. If you choose to continue the installation after thesoftware audit, you will be prompted to browse to a valid version of PDMS.

If the environment is unsatisfactory, you will see an audit summary report listing the itemsyou need to attend to and then the installation will close. An example of the warnings theaudit report might contain is:



If here are no major inadequacies, the install will proceed.

If the only major problem is that the product is not validated for install and use on the targetWindows Operating System, this panel will ask whether you wish to proceed.

If you click Yes, software will be downloaded - but any items which might corrupt theWindows system will not be installed. See Installing for Untested (e.g. Foreign Windows)Environments for guidance on handling this situation.

The Setup Wizard displays the Type of Installation screen showing the Install optionsavailable:



When the Install Option is selected in the Wizard, then a description of the install option ispresented in the right-hand pane.

To install the appropriate documentation and help links for the selected installations optionscheck the relevant box.

To generate sample batch files and shortcuts which link to other supported AVEVA productscheck the relevant box. When checked the Plant or Marine Connection Sample form willbe displayed when Next is selected. Refer to Plant or Marine Connection Sample Form.

Clash Manager Only Install only Clash Manager and Model Management Wizard. Noother application will be installed. Available to both AVEVA Plantand AVEVA Marine users.

Typical User Install Installs all user applications, but no administration tools.

Complete Install Installs all applications and administration tools.

Custom Installs selected products. Custom installations are generallydiscouraged unless performed by a product expert.

Run from Installation Choose which features to install locally and which features torun from a network location. This installation must be runningfrom an Administrative install, which is in permanently apermanently accessible location.

This option is generally discouraged as Model Managementrequires a small amount of disk space.



Select Back button to step back a stage, Next button to continue the installation or Cancelbutton to terminate the Setup Wizard.

A default Install to folder C:\Aveva\MM12.0\ is recommended for the installation. This canbe changed by clicking the Browse button. The Change destination folder form isdisplayed.

All Model Management products except Clash Manager and the administration tools requireOracle to be installed. If Oracle is not installed the following message will be displayed:



3.5.1 Clash ManagerClash Manager is available to both AVEVA Plant and AVEVA Marine users. When choosingthe Clash Manager Only option from the Type of Installation screen, only Clash Managerand the Model Management Wizard is installed.

All the other options available on the Type of Installation screen are described earlier in thechapter. If the Generate sample Batch files and shortcuts which link to other supportedAVEVA Products is checked, the Plant or Marine Connection Sample Form will be displayedwhen the Next button is clicked. If left unchecked the Ready to Install Clash Managerscreen is displayed.



To continue the installation of Clash Manager click the Next button. The Installing ClashManager screen is displayed, showing the status of the installation via a taskbar.

When the installation is complete a Completed the Clash Manager Setup Wizard screenis displayed.

Click the Finish button to exit the screen and installation.



3.5.2 CustomIf the Custom option is selected, then you will need to select from the Custom Setup formthe Model Management products and components you wish to install.

The following options are available on the Custom Setup form:

3.5.3 Disk Space Requirements ScreenThe Disk Space Requirement screen displays the amount of disk space required for theselected custom install.

Browse Leads to the Change destination folder form

Reset Deselects all selected Model Management products previously selected.

Disk Usage Lead to the Disk Space Requirements Screen

Back Steps back a stage

Next Leads to the Plant or Marine Connection Sample Form

Cancel Cancels the Setup Wizard



Highlighted volumes indicates that there is not enough disk space available for the selectedfeatures. You can remove some of the files from the highlighted volumes, install fewerfeatures or select a different destination volume. Click the OK button to return to theCustom Setup form.

3.5.4 Plant or Marine Connection Sample FormThe Plant or Marine Connection Sample form requires information for use by the samplebatch file which launch Model Management. It is displayed when the Generate sampleBatch file and shortcuts which link to other supported AVEVA Products is checked on theType of Installation screen.



The Plant or Marine, ABA and MDS path information is used in Sample Batch files. TheSample Batch files are not intended to be used in production and are supplied with thesoftware as templates only. The user can copy and adapt these template files and createshortcuts to them.

The Ready to install Model Management screen is displayed when the Next button isselected.

Plant or MarinePath andVersion

This field is compulsory. It requires the path to the Plant or Marinesoftware. The version of software also requires checking.

ABA Path This field is optional. If used it requires the path to the Area Based ADPsoftware.

MDS Path This field is optional. If used it requires the path to the Multi-DisciplineSupport software.



The following options are available:

3.5.5 Installing Model Management ScreenThe Installing Model Management screen displays a taskbar showing the status of theinstallation.

Back Steps back a stage

Install Continues the installation and displays the Installing ModelManagement Screen.

Cancel Leads to a confirm screen, which prompts the user to confirm thecancel request by clicking the Yes button or clicking the No buttonand returns to the Ready to Install Model Management screen.



During the installation process the form displays a Cancel button, which can be clicked tostop the installation. When selected a form is displayed asking for confirmation that theModel Management Installation is to be cancelled.

Selecting the Yes button displays a screen showing the Status: Rolling back the action.



When the Rolling back action is complete a screen is displayed informing you that yoursystem has not been modified and if you wish to install at a later date to re-run theinstallation from the start.




Selecting the No button on the confirm screen returns you to the Installing ModelManagement Screen screen and continues the installation. When the installation iscomplete a Completed the Model Management Setup Wizard screen is displayed.


When you have rebooted the product is ready to run. The installation also creates theappropriate Start menu selections.

A Model Management selection will have been added under AVEVA.

Run PDMS (Model Management) from this selection will run PDMS with links to all ModelManagement products which have been installed

Note: Appropriate Project EVARs must be set. See Adding the Model ManagementProducts to PDMS.

PDMS can be run without the Model Management links from the existingAVEVA>VANTAGE PDMS {version} selection.

Run Model Management under this section enables the User to run the standard ModelManagement products which have been installed (Model Object Manager, ConnectivityManager, Clash Manager) without an active PDMS session.

If Deliverable Manager has been installed there will be an entry to start a stand-alonesession under AVEVA.

For each product that has been installed and which is entirely independent of a PEWorkbench session (PLOT Viewer, Area-Based ADP and MDS) there will be an entry tostart a session under AVEVA.


Model Management Installation GuideConnecting and Configuring the Model Management Product

4 Connecting and Configuring the Model Management Product Software

PDMS and the Model Management system both rely on the setting of environment variablesto configure the system. An administrator who understands how these environmentvariables are used can operate a more flexible installation policy for his/her company.

Model Management programs require both program environment variables and projectenvironment variables. Model Management installation will create files which set theprogram environment variables. Administrators are responsible for ensuring required projectenvironment variables are set.

4.1 PDMS Without Model ManagementPDMS relies on a number of environment variables to define and “connect” the software andprojects databases. Some environment variables define product software locations, someuser output folders and some project-specific folders/data. The environment variables canbe set to represent alternative locations that should be searched in a preset sequence tofind the required items. In this case the values of the environment variables are calledsearch-paths.

Scripts (called batfiles because the files have extension .bat) are provided with PDMS to setthe PDMS environment variables for a standard installation.

The significant PDMS batfiles are pdms.bat and evars.bat. The script pdms.bat is thescript called when PDMS is invoked from the Start menu. It calls evars.bat to set all theenvironment variables required by standard PDMS, based on the installed product location.The PDMS evars.bat file allows for preset environment variables, and if any environmentvariable is already set it is not reset by evars.bat.

4.2 Adding the Model Management Products to PDMSTo maintain the ability to run PDMS in non-Model Management mode, Model Managementproducts take a copy of the standard PDMS scripts and only alter this renamed copy. Thebase PDMS pdms.bat (and evars.bat) is unchanged. This protects the base versionseven if the Model Management product is installed directly into PDMS.

The modified version of the PDMS script is mms_pdms.bat. For Model Management,mms_pdms.bat calls evars.bat for each installed Model Management related product(including evars.bat for PDMS) to set the essential Model Management environmentvariables (including PDMS environment variables) in the same way that pdms.bat callsevars.bat to set the essential PDMS environment variables.



The modified start-up script, mms_pdms.bat, is called when PDMS is invoked from theModel Management option of the Start menu. The installed locations of the ModelManagement products are recorded here, enabling it to call other batfiles to ensure productenvironment variables for all installed Model Management products are set. However theinstallation process does not know about Model Management projects which, being PDMSprojects, also require relevant environment variables to be set.

For Model Management, as for PDMS, the project environment variables can be set eitherby having them set by a batfile on program start-up (e.g. modify mms_evars.bat) or(deprecated) from Control Panel>System, selecting the Advanced tab and theEnvironment variables… option. An example of an environment variable modified forModel Management is PDMSUI. PDMSUI is the searchpath for files containing PDMSapplicationware. In a default PDMS installation this may be set to:

set PDMSUI=C:\AVEVA\PLANT\PDMS12.0\PDMSUI

For Model Object Manager:

set PDMSUI=C:\AVEVA\MM12.0\pdmsui %PDMSUI%

Single blanks separate the values in environment variables.

Note: Each folder name’s path in the searchpath must not contain any blanks (else PDMSfails). Therefore the paths to the locations where Model Management products areinstalled must not have blanks in them.

Each product requires different environment variables to be set. Changed EnvironmentVariables for each Product summarises these for each Model Management product.

It is possible to install the Model Management product physically into the same group namefolder in the PDMS folder. Then modifying the environment variables and .bat files isunnecessary. However installing Model Management products in the same folders as PDMSitself is not recommended because it complicates the uninstall procedure; uninstalling ModelManagement in this situation would result in an incomplete PDMS.

4.3 Starting Model Management without PDMSIt is possible to start all the Model Management products without having PDMS running,although only Deliverable Manager and the Model Management Wizard are usually run inthis mode. The relevant installs create batfiles, dm.bat, mmwizard.bat ormms_pdms.bat for using to set required environment variables and start the programs. Thebatfile dm.bat calls evars.bat to set the required product environment variables.

Note: Some tasks require Model Management to be linked to an active PDMS session, sothere may be reduced functionality if Model Management is started without PDMSrunning.

When one of the constructed batfiles (dm.bat, mms_pdms.bat) is run to execute a productthen an additional task which is performed is the creation of a batfile which would set theenvironment variables for a batch run.

4.4 Model Management WizardBefore Model Management products can be used, an administrator must run the ModelManagement Wizard. The Model Management Wizard is supplied with each of the ModelManagement products, and can be installed as an option when installing a product if the



Custom setup type is selected. Only administrators need to install Model ManagementWizard.

The Model Management Wizard performs some administration tasks applicable to all ModelManagement products.

Refer to the Model Management Configuration Guide for details on how to use the ModelManagement Wizard.


Model Management Installation GuideModel Management Sample Project

5 Model Management Sample Project

A Model Management project consists of a PE Workbench project, a PDMS project and aset of configuration files.

Any sample project PE Workbench project will be supplied as an Oracle dump, to be loadedinto a new Oracle instance on the Oracle server.

No sample Model Management project is supplied in the standard Model Management 12.0release. Please contact your AVEVA Customer Support Engineer if you require a sampleModel Management project.

Example text files for project configuration are supplied. (These may be used at the NewConfiguration step of the Model Management Wizard):


Model Management Installation GuideModel Management Sample Project


Model Management Installation GuideSummary Installation Instructions

A Summary Installation Instructions

A.1 Installing the Environment and Products for Model Management OperationThis appendix provides a summary of the installation and configuration for ModelManagement. It simply lists objects/settings.

Before starting make sure that you have installed on your network and visible from yourWorkstation:

• Oracle DB server

and on your Workstation,• Oracle 10g Runtime Client plus Oracle Windows Interfaces• Oracle 10 OLE DB Provider• the Oracle Runtime library path added to your environment variable %path%.

Your Project Administrators must also have created the:• PE Workbench project (see the PE Workbench 5.5 Release Document).

And the Model Management project file:• {project}.cfg

Project Administrators will also require:• the project .txt and perops.xls files associated with Model Management

A.2 Actions to Install and Setup to Run1. Set up the environment.

For example: set the Project evar for PDMS project SAM : set SAM000=\\pdms_server\pdms\sam000. Mapped drive locations can also bedefined. For example: for PDMS Projects, W: => \\pdms_server\pdms. Then setSAM000=W:\sam000.

2. Check or Set the registry entry {Key: HKLM\Software\ORACLE, Name:TNS_ADMIN}to point to the folder containing the folder containing tnsnames.ora andsqlnet.ora (containing Oracle connection data). e.g.TNS_ADMIN=V:\Oracle\network\admin.

3. Install PDMS - make sure the version is compatible with the release of ModelManagement.

4. Install the Model Management application, selecting the desired products, createprojects and place on the drive (e.g. W:). If you or unzip the sample projects, theinternal structure is created automatically. For each product you install, check for andas needed, unzip the zip file contained in the project sub-folder on the CD.

12.0 A:1© 2007 AVEVA Solutions Ltd

Model Management Installation GuideSummary Installation Instructions

5. Check/Create the start-up bat files.6. You must do item 1 manually. Items 2 - 5 can be done manually, or using a script to

install Model Management products.

A.3 After InstallationAfter the installation is complete, on reboot selecting:-Start>Programs>AVEVA>Model Management 12.0>Model Management PDMS

starts PDMS with the Model Management facilities enabled - you can start ModelManagement from PDMS DESIGN.

To run Model Management Wizard:

Start>Programs>AVEVA>Model Management 12.0>Model Management Wizard

To run Deliverable Manager

Start>Programs>AVEVA>Model Management 12.0>Deliverable Manager

The install will have created a working setup which can be run. However, users may wellwish to recreate the environment setup for specific projects working.

12.0 A:2© 2007 AVEVA Solutions Ltd

Model Management Installation GuideDefault Locations

B Default Locations

The Model Management products will be installed in the following locations (where “C” isreally the disk on which the Windows operating system was installed) unless these areoverridden during the installation process:

Product Default Location

Plant Design PlotViewer 12.0 C:\AVEVA\programfiles\commonfiles\AVEVAshared\plot

AVEVA Model Object Manager 12.0 C:\AVEVA\MM12.0\

AVEVA Connectivity Manager 12.0 C:\AVEVA\MM12.0\

AVEVA Clash Manager 12.0 C:\AVEVA\MM12.0\

Model Management Wizard C:\AVEVA\MM12.0\

AVEVA Deliverable Manager 12.0 C:\AVEVA\MM12.0\

12.0 B:1© 2007 AVEVA Solutions Ltd

Model Management Installation GuideDefault Locations

12.0 B:2© 2007 AVEVA Solutions Ltd

Model Management Installation GuideHelp with Oracle Activities

C Help with Oracle Activities

This Appendix contains hints which some installers have found useful when difficultiesrelated to Oracle.

C.1 Installing Oracle 10g (10.1.0.2) Client You can begin installing the Oracle 10g Client in one of two ways.

1. Start from the Oracle CD screens invoked from autorun, and then select Oracle10g…Install/Deinstall Products and then click Next on the Welcome screen.

2. Or, if autorun hasn’t run or isn’t enabled, browse the CD and navigate to{Oracle}\install\win32\setup.exe.

When the installation program starts follow through the dialog boxes as follows:

Install patches to Oracle client as recommended in the product Release Letter.

C.1.1 Additional ComponentsIn addition to the default Oracle components you will also need to install the Oracle Providerfor OLE DB 10.1.0.2.0. This component appears under the Oracle Windows Interfaces10.1.0.2.0 section:

Dialog Box Purpose and Selections

Specify File Locations Self-explanatory

Select Installation Types Custom.

Select the option to install Windowscomponents

Summary Install

Oracle Net Configuration Assistant Click CANCEL, and continue exitingthrough a number of checks.

12.0 C:1© 2007 AVEVA Solutions Ltd


C.2 Checking the Oracle Connection

C.2.1 Checking if a connection existsThe Oracle connection may be checked at any time, to make sure it has not failed. In acommand window enter:

tnsping <WORLD>

where WORLD is a valid instance name in tnsnames.ora. Refer to tnsnames.ora.



For a successful connection, you will see a message like:

For an unsuccessful connection you will see something like this:

C.2.2 Checking if SQL Plus Can Use the ConnectionFrom the Windows Start menu select:

Start>Programs>Oracle {Oracle Home}>Application Development>SQL Plus

On the login dialog box, the fields have the following meanings:

+-----------------------------------+tnsping MOMTESTTNS Ping Utility for 32-bit Windows: Version 10.1.0.2.0 -Production on 07-OCT-2

005 16:55:06Copyright (c) 1997, 2003, Oracle. All rights reserved.Used parameter files:C:\oracle\product\10.1.0\db_1\network\admin\sqlnet.oraUsed TNSNAMES adapter to resolve the aliasAttempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = oracle_server)(PORT = 1521))) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = MOMTEST.WORLD)))OK (40 msec)+-----------------------------------+

+-----------------------------------+tnsping MOMTEST1TNS Ping Utility for 32-bit Windows: Version 10.1.0.2.0 -Production on 07-OCT-2

005 16:57:38Copyright (c) 1997, 2003, Oracle. All rights reserved.Used parameter files:C:\oracle\product\10.1.0\db_1\network\admin\sqlnet.oraTNS-03505: Failed to resolve name

+-----------------------------------+

User A valid user for the instance/project.

Password Users password.

Host String The first part of the value associated with SERVICE_NAMEin tnsnames.ora, for example van1sys fromvan1sys.WORLD.



If the login is successful, you will see a new window showing text similar to that shownbelow:

C.3 Summary Explanation of Entries (& Nomenclature) in Oracle Definition FilesThe following describes the format and meaning of some of the entries in Oracle Definitionfiles.

C.3.1 sqlnet.oraEntry NAME.DEFAULT_ZONE = …, for example WORLD gives the suffix applied to a set ofOracle Instances, each of which is defined in more detail in tnsnames.ora.

C.3.2 tnsnames.oraThis file contains any number of Oracle Instances, each of which is headed with its InstanceName suffixed as defined in sqlnet.ora.

For example, in van1sys.WORLD the instance name is van1sys.

Each instance is described in its own definition set:

In the above definition, (Host = PSORACLEDEVTEST) refers to the name of the ORACLEmain server in the lines containing

van1sys.WORLD =}

+----------------------------------------------------------------------+SQL*Plus: Release 10.1.0.2.0 - Production on Wed Oct 12 08:42:55 2005Copyright (c) 1982, 2004, Oracle. All rights reserved.Connected to:Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - ProductionWith the Partitioning, OLAP and Data Mining optionsSQL> ------------------------------------------------------------------+

+-----------------------------------+van1sys.WORLD =(DESCRIPTION =

(ADDRESS_LIST =(ADDRESS =(COMMUNITY = tcp.world)(PROTOCOL = TCP)(Host = PSORACLEDEVTEST)(Port = 1521)

))(CONNECT_DATA =

(SERVICE_NAME = van1sys.WORLD))

)+-----------------------------------+



and

(SERVICE_NAME = van1sys.WORLD)}

van1sys need not be the same in both.

The SERVICE_NAME is used in PE Workbench/Model Management files. The InstanceName is used in PE Workbench/Model Management file.

C.4 Installing Deliverable ManagerFor Deliverable Manager to handle decimal values correctly a period must be used as thedecimal character and a comma as the group separator. This is the default in Englishenvironments. In non-English environments, where this is not the default, it is important tohave the NLS_NUMERIC_CHARACTERS parameter set in Oracle. For example:

NLS_NUMERIC_CHARACTERS = '.,'

indicates that a period is to be used as the decimal character and a comma as the groupseparator viz.:

999,999,999.999

Deliverable Manager requires that the decimal character is defined as a period in the Oracleinitialisation file Init.Ora.


Model Management Installation GuideHelp with MS SQL Server Activities

D Help with MS SQL Server Activities

When using the Stand Alone Clash Manager application with MS SQL Server the followingactions should be taken by a Database Administrator prior to launching the Stand AloneClash Manager for the first time:

• If installing an MS SQL Server for the first time, the default SA account passwordshould be changed. A password should be set for a user account for Stand Alone ClashManager to work correctly.

• Create a new Empty Database, there is no need to populate this with data, this will bedone by the Model Management Wizard while creating a project for the Stand AloneClash Manager.

12.0 D:1© 2007 AVEVA Solutions Ltd

Model Management Installation GuideChanged Environment Variables for each Product

E Changed Environment Variables for each Product

To run the Model Management products certain environment variables used by PDMS needto be changed. These environment variables and the necessary changes for each productare given below.

In the paths {Model Object Manager location} denotes the location where Model ObjectManager was installed. The default values for these locations are given in DefaultLocations.

E.1 Model Object Manager To run Model Object Manager, the following environment variables need to be setPDMSEXE={Model Object Manager location}\exe %PDMSEXE%PDMSUI={Model Object Manager location}\pdmsui %PDMSUI%PMLLIB={Model Object Manager location}\pmllib %PMLLIB%PDMSDFLTS={Model Object Manager location}\pdmsui\dflts %PDMSDFLTS%

E.2 Connectivity Manager To run Connectivity Manager, the following environment variables need to be setPDMSEXE={Connectivity Manager location}\exe %PDMSEXE%PDMSUI={Connectivity Manager location}\pdmsui %PDMSUI%PMLLIB={Connectivity Manager location}\pmllib %PMLLIB%PDMSDFLTS={Connectivity Manager location}\pdmsui\dflts %PDMSDFLTS%

E.3 Clash Manager To run Clash Manager, the following environment variables need to be setPDMSEXE={Clash Manager location}\exe %PDMSEXE%PDMSUI={Clash Manager location}\pdmsui %PDMSUI%PMLLIB={Clash Manager location}\pmllib %PMLLIB%PDMSDFLTS={Clash Manager location}\pdmsui\dflts %PDMSDFLTS%

E.4 Deliverable Manager If paths to the installed Plant products are denoted, {PDMS location}, the path to PDMS,and {Deliverable Manager location} the path to Deliverable Manager., then DeliverableManager requires environment variables as follows, plus any environment variables used todefine file of folder locations in the Deliverable Manager configuration of the project:

12.0 E:1© 2007 AVEVA Solutions Ltd


PDMSEXE={PDMS location}

PDMSUI={PDMS location}\pdmsui

PMLLIB={PDMS location}\pmllib

PDMSDFLTS={PDMS location}\pdmsui\dfltsPDMSPLOTS={path for folder where you want plots to output}PDMSWK={path for work area folder}DM_PROJ_DIR={Deliverable Manager project location}DPCLIB={Deliverable Manager project location}\LibDPCPLT={Deliverable Manager project location}\Lib\pltEQUDRAFT={Deliverable Manager project location}\Lib\MacDPCEXE={Deliverable Manager location}\exePMLLIB={Deliverable Manager location}\pmllib %pmllib%

PV_INSTALLED_DIR={PDMS PlotViewer 2.1 location}\exe

See:{Deliverable Manager location}\evars_dm.bat

E.5 PLOT Viewer The PLOT Viewer product does not require any further environment modifications.

E.6 Model Management Wizard The Model Management Wizard requires a full PDMS, and PDMS project, environment. Italso requires:{project}DM=(Project Deliverable Manager data location)

If the PDMS project is to be configured for Deliverable Manager

E.7 Area-Based ADPAB_ADP needs new variables (as compared with standard PDMS), contained in{Area-BasedADP installation folder}\evars-aba_product.bat.

For full details refer to Area Based ADP Installation Guide.

E.8 Multi-Discipline Supports MDS needs new variables (as compared with standard PDMS), contained in

{MDS installation folder}\evars-MDS_product.bat.

For full details refer to Multi-Discipline Supports Installation Guide.

E.9 SummaryAfter a number of add-on products have been installed, if you displayed the searchpathenvironment variable, for exampleecho PDMSUI= %PDMSUI%

it might now look like:PDMSUI=C:\AVEVA\MDS12.0\pdmsui C:\AVEVA\AB_ADP12.0\pdmsui C:\AVEVA\MMS12.0



\pdmsui C:\AVEVA\PLANT\PDMS12.0\pdmsui

Note: Versions may be different from the above example.

E.10 batfilesBatfiles will be installed if the user chooses during installation.

The optionally installed batfiles are only intended as samples. AVEVA recommend adaptingcopies of these files for production use.


Model Management Installation GuideAlternative Methods of Installing Model Management Products

F Alternative Methods of Installing Model Management Products

There are a number of additional facilities in the setup folder, which may help with multipleinstallations.

However, please note that only the process previously described in Installing ModelManagement, which runs setup.exe to install the product, is supported.

The primary and supported installation mode is live/interactive in which the installerresponds to install dialog queries to control the content and location of the components inthe product release.

Note: Many AVEVA product releases also have another unsupported install mode silent inwhich the install uses pre-prepared answers to the install dialogs.We expect the silent mode to work satisfactorily but, as yet, AVEVA have insufficientworldwide testing coverage, in often highly customised company IT environments, togive a warranty.The silent installation performs the same operations as the live install. The onlydifference is that the silent install will automatically handle any events such as arequest to overwrite a read-only file.The file tnnnnn_pppnnn_Install_FileHandlingExceptions.log in the…\AVEVAInstalls\tnnnnn_pppnnn directory lists what occurred.AVEVA would welcome your reports on your experience using the silent install.AVEVA recommend that you do at least one live install into the intended environment- to check whether/how the install modifies the target system.The Silent Install capability, indicated by a file setup.iss in the setup folder, willhave been created for the Typical setup type option.The targets listed in this file can be changed - but change nothing else.You can also re-create your own silent install instructions (setup.iss) by runningCreateSilentInstall.bat and use RunSilentInstall.bat to install silently.Appendix D describes these files and processes more fully.

Note: If you have any problem with silent install, go back to using the supported normal liveinstall mode.

F.1 Installation and UninstallingThe ‘silent’ installs behave differently to live installs. If setup does not detect the productalready installed, it will install silently; if the product is detected, it will ‘repair’- which willcheck for any missing or differently versioned/dated files within the installed product andrepair them back to that originally installed. So repeated silent installs simply re-install.

Uninstall should be initiated from:

12.0 F:1© 2007 AVEVA Solutions Ltd


Start>Settings>Control Panel>Add/Remove Programs

F.2 Silent/Unattended InstallationModel Management is installed using the Microsoft® Installer (MSI). You can invoke MSIdirectly from the command line allowing you to install Model Management on a machinewithout user interaction. This process is called Silent/Unattended installation.

The Msiexec command uses parameters to give MSI some or all of the information thatwould normally be specified as part of an interactive installation using the ModelManagement Installer.

F.2.1 MSI Command Line ParametersExamples of performing a Silent/Unattended installation are shown below.

• Silent Installation of Selected FeaturesMSIEXEC /I "[ModelManagement.msi]" /QN ADDLOCAL=FEATURE1,FEATURE3

Installs FEATURE1 and FEATURE3 silently. If, for example, FEATURE3 was the child ofFEATURE2, then FEATURE2 would also be installed. The /qn switch makes the installationsilent.

Note: ADDLOCAL and the FEATURE IDs are case sensitive.

Refer to the Feature Guide for a list of allowable features.

• Silent Installation of selected Features to a non-default FolderMSIEXEC /I "[ModelManagement.msi]" /QN ADDLOCAL=FEATURE1,FEATURE3INSTALLDIR="C:\My Dir\"

Using the INSTALLDIR parameter it is possible to specify a folder where features should beinstalled. If this parameter is not used the default location is:

C:\Aveva\ModelManagement12.0\, on a single HDD computer.

• Silent and Logged Installation of selected Features.MSIEXEC /I "[ModelManagement.msi]" /LV "[Install.log]" /QNADDLOCAL=FEATURE1,FEATURE3

The LV parameter creates a Verbose Log of the installation. Logging is often necessary totrouble shoot silent installations, and can be used to verify deployments.

• Clash ManagerMSIEXEC /I "[ModelManagement.msi]" /QN ADDLOCAL=CLASHHLP,MMWIZHLP,V120,V116,V115

V120, V116, V115 Features install appware, to a folder of the same name underneath theroot application folder

• V120 appware works with Version 12.0 Plant and Marine installations• V116 appware works with Version 11.6 Plant and Marine installations• V115 appware works with Version 11.5 Plant and Marine installations



If only PDMS 11.6 will be used, there is no need to include V120 and V115. For example:MSIEXEC /I "[ModelManagement.msi]" /QN ADDLOCAL=CLASHHLP,MMWIZHLP,V116

• Clash Manager with Sample Shortcuts and Batch FilesMSIEXEC /I "[ModelManagement.msi]" /QN ADDLOCAL=CLASHHLP,MMWIZHLP,V120,V116,V115 SAMPLES=1 PMVERSION=V120 PMPATH="[Path to Plant or MarineInstallation]"

The sample batch files deployed with Clash Manager need to include the path to a Plant ora Marine installation and need to know what version of the software is installed.

Note: Only Versions 11.5, 11.6 and 12.0 are supported.

Sample Batch files and Shortcuts will not be deployed unless SAMPLES=1 is specified.

• Complete InstallMSIEXEC /I "[Path]ModelManagement.msi" /QN ADDLOCAL=ALL REMOVE=MMLOGIN

The ALL option includes every Feature in the installation. However, most users will not want"Discipline based logging in" (MMLOGIN), hence REMOVE=MMLOGIN deselects thisFeature.

• Complete Install with Sample Shortcuts and Batch FilesMSIEXEC /I "[Path]ModelManagement.msi" /QN ADDLOCAL=ALL REMOVE=MMLOGINSAMPLES=1 PMVERSION=V116 PMPATH="[Path to Plant or Marine Installation]"ABAPATH="[Path to (optional) ABA Installation]" MDSPATH="[Path to (optional) MDSInstallation]"

The additional batch file deployed during a full installation can optionally reference an ABAand MDS installation. Do not specify either an ABAPATH or MDSPATH unless you intend towork with these products.

F.3 Testing the InstallFollowing a Silent/Unattended installation, small syntax errors, missing quotes aroundvalues with spaces in them, incorrect capitalisation, and even the order on the CommandLine could cause unanticipated results. Without logging enabled no errors will be reported.Two options are available to test the installation has been sucessful.

F.3.1 Installed Model Management Setup DialogViewing the Model Management Setup dialog is the simplest method of viewing what hasbeen installed. The Model Management Setup dialog is displayed when a user wishes tochange the original installation choices, or when performing a Custom installation. Whenfirst opened in Change mode, it shows the current installation state. It is accessed asfollows:

1. Install the program silently using the command line, onto a computer which doesn'talready have any Model Management applications installed.

2. Select Start>Settings>Control Panel, then choose "Add/Remove Programs".3. Highlight AVEVA Model Management, and then click the Change button.4. The Change, repair or remove installation screen is displayed



5. Click the Change button.6. The Custom Setup screen is displayed showing which features are currently installed.

F.3.2 Log FileViewing the log (created using the LV parameter) file is the hardest but most concise way totest the installation. Features, Properties and their values are displayed in the log as theyare changed and used, so it is quite clear to see how the CommandLine was handled.However log files can be large and complex, and so are not recommended as a first choice.

F.4 Reference

F.4.1 Optional ParametersThe following parameters effect installation when used with the MSIEXEC command.



Note: Property references are always in Uppercase.

F.4.2 Feature GuideIf a child Feature is selected, then its parents are also selected. So for example ifADDLOCAL=CLASHHLP then CLASHMAN would also be deployed, because theCLASHHLP Feature is a child of CLASHMAN. See the Installation Hierarchy diagram forthe relationships, or run the installation and choose a Custom Installation, to besubsequently presented with the Model Management Setup dialog.

Note: Feature references are always in Uppercase

Property Name (Case Sensitive)

Function

SAMPLES Triggers deployment of sample batch files and shortcuts forselected Features, when SAMPLES=1. SAMPLES defaults to 0.

PMVERSION The version of the Plant or Marine installation that is specified byPMPATH.PMPATH and PMVERSION must both be specified ifSAMPLES=1. Their values are entered into the sample batch fileswhich run Model Manager.

PMPATH The path to root folder of an installation of PDMS or Marine, thatModel Management is to work with.PMPATH and PMVERSIONmust both be specified if SAMPLES=1. Their values are enteredinto the sample batch files which run Model Manager.

ABAPATH The path to root folder of an installation of ABA that ModelManagement is to work with.This value is entered into the samplebatch files which run Model Management. If SAMPLES=1 andyou wish to work with ABA, then this value must be specified.

MDSPATH The path to root folder of an installation of MDS ABA that ModelManagement is to work with.This value is entered into the samplebatch files which run Model Management. If SAMPLES=1 andyou wish to work with MDS, then this value must be specified.

INSTALLDIR The folder path where Model Management will be installed. ThisProperty defaults to C:\Aveva\ModelManagement12.0\

Feature command lineName (Case sensitive)

What it Contains

CLASHMAN Clash Manager

CLASHHLP Clash Manager Help

MODOBMAN Model Object Manager

MODOBHLP Model Object Manager Help

CONMAN Connectivity Manager

CONMANHLP Connectivity Manager Help

DELIVMAN Deliverable Manager

DELMANHLP Deliverable Manager Help



F.4.3 Installation HierarchyMODMAN -> CLASHMAN -> CLASHHLPMODMAN -> MODOBMAN -> MODOBHLPMODMAN -> MODOBMAN -> CONMAN -> CONMANHLPMODMAN -> DELIVMAN -> DELMANHLPMODMAN -> V115MODMAN -> V116MODMAN -> V120MODMAN -> ADMTOOLS -> MMWIZMODMAN -> ADMTOOLS -> MMSCMDMODMAN -> MMLOGIN

V115 PDMS or Marine Version 11.5 Compatibility



MMWIZ Model Management Wizard

MMSCMD MMS Command

MMLOGIN Discipline based Logging in


Model Management Installation GuideChecking Product/Version Installation

G Checking Product/Version Installation

For a single workstation, if there is doubt about a Model Management product’s installation itcan be uninstalled and re-installed.

For companies with centrally-managed installation, where the procedures of InstallingModel Management have been used, it may be necessary to check whether a ModelManagement product/version is already installed on a workstation. This could be done byrunning the runSilentInstall.bat script with a suitable setup.iss file. However, even if no repairis needed, this will typically take about 1 minute for twelve product/version releases. This istoo slow to be used at every invocation of the system, so a quick check activity is provided.The same process is run during a Model Management product set installation.

12.0 G:1© 2007 AVEVA Solutions Ltd

Model Management Installation GuideInstalling for Untested (e.g. Foreign Windows) Environments

H Installing for Untested (e.g. Foreign Windows) Environments

H.1 GeneralBefore installing any software, the installation does a software environment check to see ifthe target computer has an environment that has been validated for using the product. If not,it will warn you if the installation can continue but cannot complete.

If you choose to proceed, all the software will be downloaded - but any items which mightcorrupt the host Windows OS will not be completely installed.

Although the installation is incomplete, the product has been registered. Should you notthen attempt to complete the installation yourself, please UnInstall the product.

At the end of the install, displaying the panel below, it will remind you that the install isincomplete, directing you to this section of the Installation Guide.

A number of system files will not have been installed or registered; their non-registration willthen prevent AVEVA-created items from registering.

The downloaded files will be placed into the folder “Support” within the product folder in anumber of sub-folders.

The following notes give some guidance to help you if you wish to try to create your ownlocalised install.

If you have any doubts about this process, contact your Support Office before starting.

This product is NOT validated with the language installed on this computer.

* * * The installation is NOT ready for use. * * * *

The English versions of files required for this product have been downloaded into,

{INSTALLDIR}\Support

but NOT installed; if installed on this system, these files may damage the system.

AT YOUR OWN RISK

you may wish to try installing the equivalent 'local' set for your Windows, but AVEVAcannot guarantee that the product will work and AVEVA can take no responsibility for theoutcome.

12.0 H:1© 2007 AVEVA Solutions Ltd


H.2 Completing the Installation for your Windows SystemThe contents of the Support\sub-folders, named like winsys_…_{language}, containitems which may have language-specific properties. You must determine which of theEnglish files need to be replaced by localised files (at the equivalent version level) for yourhost Windows OS.

Folders named like winsys_…_PreExisting_{language}” contain copies of files thatwere already on the target system before the installation started.

The release Contents document tnnnnn.txt gives names and English version numbers.

Consulting MSDN may help you determine which need changing to match your Windows.See:

support.microsoft.com/servicedesks/fileversion/dllinfo.asp?fr=0&sd=msdn

In some cases, the product is supplied with a set of items which are believed to be suitablefor the unsupported Windows OS/language environment - BUT are NOT guaranteed.

Before use, you must check and/or change these and be satisfied that they are suitable foryour system.

H.3 “Support” Folder after Installation

H.3.1 Validated EnvironmentsIf the environment is validated for the product, then the Support folder contains only a filelisting the replaced items/version ids.

H.3.2 Unsupported EnvironmentsFor an unsupported environment, the Support folder contains a number of batfiles and anumber of folders containing versions of the items.

(See a typical example in next section.)

When you are satisfied that you have acquired the appropriate local items and placed themin an appropriately named folder.

the batfile register_{product}.bat contains instructions to complete the installation.

Browsing this file summarises the process.

Each batfile and folder is systematically appropriately named to indicate its contents. Forexample. winsys_SelfReg_XXXX indicates items for placing in the Windows system32folder that are registered there for XXXX OS/language.

The files/folders winsys_…_English contain the Windows English language environmentitems which were used in validating the product: these may need localising.

Files and folders suffixed _PreExisting relate to copies of your system before the productinstallation started - which then enable you to recover back to your original state should thisbe needed.

Each folder has an accompanying batfile for completing the install,winsys_SelfReg_XXXX.bat, a batch file called from register_{product}.bat orrun individually as required.



H.3.3 ExampleFor a product validated for use in all English environment only, but installed into Windows forlanguage XXXX, folder Support will contain:

You need to create sub-folder winsys_Self/UnReg_XXXX containing the equivalentlocalised items as in winsys_Self/UnReg_English.

Then run register_{product}.bat - which will internally run the winsys_Self/UnReg_XXXX.bat files and other batfiles registering other product items whose ownregistration may be dependent on the items in the winsys folders.

If the resulting environment is unsatisfactory, run winsys_Self/UnReg_XXXX_PreExisting.bat to replace your original environment.

H.3.4 WARNING - “Unsupported Windows” InstallationsRemember:

1. If the product is not validated for use on this target environment, it is NOT supported.2. Use at your own risk.3. Please report success, or any problems due to the installation, to your local AVEVA

Support.

Sub-folder Batfile (to handle contents of folder)

winsys_SelfReg_XXXX_PreExisting winsys_SelfReg_XXXX_PreExisting.bat

winsys_UnReg_XXXX_PreExisting winsys_UnReg_XXXX_PreExisting.bat

winsys_SelfReg_English winsys_SelfReg_XXXX.bat

winsys_UnReg_English winsys_UnReg_XXXX.bat


Index


AAdding . . . . . . . . . . . . . . . . . . . . . . . . . . . 4:1Alternative Methods . . . . . . . . . . . . . . . . F:1Area Based ADP . . . . . . . . . . . . . . . . . . . E:2

Bbatfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . E:3

CClash Manager . . . . . . . . . . . . .3:7, E:1, F:2Configuring . . . . . . . . . . . . . . . . . . . . . . . 4:1Connecting . . . . . . . . . . . . . . . . . . . . . . . 4:1Connectivity Manager . . . . . . . . . . . . . . . E:1Custom . . . . . . . . . . . . . . . . . . . . . . . . . . 3:9

DDefault Locations . . . . . . . . . . . . . . . . . . B:1Deliverable Manager . . . . . . . . . . . . C:5, E:1Disk Space Requirements Screen . . . . . 3:9

EEnvironment . . . . . . . . . . . . . . . . . . . . . . 2:1Environment Variables . . . . . . . . . . . . . . E:1

FFeature Guide . . . . . . . . . . . . . . . . . . . . . F:5

IInstallation Hierarchy . . . . . . . . . . . . . . . F:6

LLog File . . . . . . . . . . . . . . . . . . . . . . . . . F:4

MModel Management Wizard . . . . . . .4:2, E:2Model Object Manager . . . . . . . . . . . . . . E:1MS SQL Server . . . . . . . . . . . . . . . . . . . D:1MSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F:2Multi Discipline Supports . . . . . . . . . . . . E:2

OOptional Parameters . . . . . . . . . . . . . . . F:4Oracle Connection . . . . . . . . . . . . . . . . . C:2

PPlant or Marine Connection Sample Form 3:10PLOT Viewer . . . . . . . . . . . . . . . . . . . . . E:2Preparation . . . . . . . . . . . . . . . . . . . . . . . 2:2Prerequisites . . . . . . . . . . . . . . . . . . . . . 2:1

SSample Project . . . . . . . . . . . . . . . . . . . . 5:1Setup File . . . . . . . . . . . . . . . . . . . . . . . . 3:3Silent/Unattended Installation . . . . . . . . F:2Support Web Site . . . . . . . . . . . . . . . . . . 3:2

12.0© 2007 AVEVA Solutions Ltd Index page i


TTesting . . . . . . . . . . . . . . . . . . . . . . . . . . F:3tnsnames . . . . . . . . . . . . . . . . . . . . . . . .C:4

UUninstalling . . . . . . . . . . . . . . . . . . . . . . . F:1Untested . . . . . . . . . . . . . . . . . . . . . . . . .H:1

12.0© 2007 AVEVA Solutions Ltd Index page ii

Model Management Installation Guide - cadfamily.com€¦ · For the installation of Clash Manager...

Documents

Transcript of Model Management Installation Guide - cadfamily.com€¦ · For the installation of Clash Manager...