Smart Plant 3 d Installation Guide 409

SmartPlant 3D Installation Guide

Version 6.1 March 2006 DSP3D-PE-200019F

Copyright Copyright 2003-2006 Intergraph Corporation. All Rights Reserved.

Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available without proper authorization.

Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the Contractor Rights in Technical Data clause at DFARS 252.227-7013, subparagraph (b) of the Rights in Computer Software or Computer Software Documentation clause at DFARS 252.227-7014, subparagraphs (b)(1) and (2) of the License clause at DFARS 252.227-7015, or subparagraphs (c) (1) and (2) of Commercial Computer Software---Restricted Rights at 48 CFR 52.227-19, as applicable.

Unpublished---rights reserved under the copyright laws of the United States.

Intergraph Corporation Huntsville, Alabama 35894-0001

Warranties and Liabilities All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties. Intergraph believes the information in this publication is accurate as of its publication date.

The information and the software discussed in this document are subject to change without notice and are subject to applicable technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.

The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license.

No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.

Trademarks Intergraph, the Intergraph logo, SmartSketch, FrameWorks, SmartPlant, IntelliShip, INtools, PDS, and MARIAN are registered trademarks of Intergraph Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. ISOGEN is a registered trademark of Alias Limited. ACIS is a registered trademark of SPATIAL TECHNOLOGY, INC. Infragistics, Presentation Layer Framework, ActiveTreeView Ctrl, ProtoViewCtl, ActiveThreed Ctrl, ActiveListBar Ctrl, ActiveSplitter, ActiveToolbars Ctrl, ActiveToolbars Plus Ctrl, and ProtoView are trademarks of Infragistics, Inc. Portions of 2D DCM, 3D DCM, and HLM from D-Cubed Limited are incorporated. All rights reserved. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. Other brands and product names are trademarks of their respective owners.

Table of Contents

SmartPlant 3D Installation Guide 3

Table of Contents Preface.................................................................................................................................6

Welcome to SmartPlant 3D...............................................................................................7

Third-Party Integration ....................................................................................................9

Using The Engineering Framework...............................................................................11

Hardware and Software Requirements .........................................................................13 Database Server Requirements ...................................................................................14 Workstation Requirements .........................................................................................15 Software Requirements and Loading Order ...............................................................18 Disk Partitioning Guidelines.......................................................................................20

Setting Up the Database ..................................................................................................22 Special Instructions for Microsoft Windows Server 2003 .........................................23

Enable Network Access in Windows Server 2003 ........................................................... 23 Configure Microsoft Distributed Transaction Coordinator............................................... 25 Configure the Distributed COM Users Group .................................................................. 26

Installing and Configuring Microsoft SQL Server .....................................................28 Install Microsoft SQL Server 2000................................................................................... 28 Verify Automatic Startup of Microsoft SQL Server 2000 Services ................................. 29 Configure SQL Server 2000 Account for Name Generator Service................................. 29 Assign System Administrator Privileges .......................................................................... 30 Create a SQL Server Database Alert ................................................................................ 31

Installing and Configuring Oracle Server Software ...................................................34 Install Oracle Server Software (Basic Installation for Enterprise Edition)....................... 35

Initialize the Oracle Database.....................................................................................39 Configure Oracle Networking Components ..................................................................... 40 Verify Automatic Startup of Oracle Database Services.................................................... 41 Create the Oracle Streams Tablespace.............................................................................. 42 Create the Oracle Streams Administrator ......................................................................... 42

Monitoring the Databases ...............................................................................................44 Set Up the Database Server ........................................................................................45 Disk I/O ......................................................................................................................47 Disk Usage..................................................................................................................49 Loading Prerequisite Software on the Database Server .............................................51

Install SQL Server 2000 Service Pack 3a: Database Components ................................... 51 Install Microsoft .NET Framework................................................................................... 53

Setting Up the Client........................................................................................................54

Table of Contents

4 SmartPlant 3D Installation Guide

Special Instructions for Windows XP with Service Pack 2........................................57 Configure Microsoft Distributed Transaction Coordinator............................................... 57 Configure the Firewall to Allow DCOM Communication ............................................... 58

Installing and Configuring Microsoft SQL Server Client Software...........................61 Install Microsoft SQL Server 2000 Client Tools .............................................................. 61 Register SQL Server ......................................................................................................... 61 Verify Startup of Microsoft Distributed Transaction Coordinator ................................... 62

Installing and Configuring Oracle Client Software ....................................................64 Install Oracle Client Software........................................................................................... 64 Configure the Oracle Client .............................................................................................. 65 Verify Startup of Oracle Client Services .......................................................................... 66

Loading Prerequisite Software on the Client..............................................................67 Install SQL Server 2000 Service Pack 3a: Database Components ................................... 67 Install Microsoft .NET Framework................................................................................... 68 Install Microsoft XML 4.0 Service Pack 2 (Workstation)................................................ 69 Install Microsoft Data Access Components...................................................................... 69

Install Microsoft Office ..............................................................................................70

Installing SmartPlant 3D Software ................................................................................71 Install SmartPlant 3D Reference Data........................................................................72 Install SmartPlant 3D Client Software .......................................................................77

Configure Network Shares................................................................................................ 81 Configure for Large Model Drawing Generation ............................................................. 82 Register Solid Edge Version 16 .DLL File ....................................................................... 84 Configure for The Engineering Framework...................................................................... 84

Installing the Name Generator Service.......................................................................86 Install the Name Generator Service .................................................................................. 87 Configure the Name Generator Service ............................................................................ 92

Integrating with PDS ..................................................................................................98 Install PDS Data Access ................................................................................................... 98 Install SmartPlant 3D PDS Project Translators .............................................................. 100

Integrating with SmartPlant P&ID ...........................................................................102 Configure the Piping Specification Remote Access Server Service ............................... 102 Register the Site Database for P&ID Access .................................................................. 108

Viewing 3D Model Data...........................................................................................110 Install Intergraph Schema Component............................................................................ 110

Using Programming Resources ................................................................................111 Install Programming Resources ...................................................................................... 112 Install the SmartPlant 3D Command Wizard.................................................................. 114 Install the SmartPlant 3D Symbol/Part Definition Wizard ............................................. 116

Configuring the Databases ............................................................................................118 Upgrading Databases ................................................................................................122 Create the Site, Catalog, and Schema Databases for SQL .......................................123 Create the Site, Catalog, and Schema Databases for Oracle ....................................126 Create the Model and Reports Databases for SQL...................................................129 Create the Model and Reports Databases for Oracle................................................132 Assign Access Permissions.......................................................................................135

Table of Contents


Server-Based Interference Checking (Database Detect): An Overview...................139 Install Database Interference Detection Service.......................................................141

Configure Interference Service Properties...................................................................... 142 Start the Database Interference Detection Service.......................................................... 143

IFC Permission Requirements ..................................................................................144 Create IFC Permission Group Folder and Permission Group ..................................145

Set IFC Permissions........................................................................................................ 145 Check Database Interferences......................................................................................... 146 Interference Server Settings Dialog Box ........................................................................ 148 Database Detect Tab (Interference Dialog Box)............................................................. 149 Status Tab (Interference Dialog Box) ............................................................................. 150

Getting Started with SmartPlant 3D............................................................................152 Update Site Database Name and Path ......................................................................153 Open SmartPlant 3D.................................................................................................155 Configure Your Tasks...............................................................................................156 Define Your Workspace ...........................................................................................158 Save Session Files.....................................................................................................159

Troubleshooting the Software.......................................................................................160

User Assistance...............................................................................................................162

Customer Assistance......................................................................................................164

Common Acronyms .......................................................................................................165

Remove SmartPlant 3D Software.................................................................................167

Appendix: Recommendation for Database Monitoring (SQL Server) .....................170 Server Monitoring.....................................................................................................171

Processor ......................................................................................................................... 171 Database.......................................................................................................................... 172

Results Analysis........................................................................................................175

Index................................................................................................................................178

Preface


Preface This document is an installation guide for SmartPlant 3D reference data and product software. The purpose of this document is to explain how to install and configure SmartPlant 3D and all necessary prerequisite software.

Important

This document does not cover basic Windows 2000 Server, Windows Server 2003, Windows 2000 Professional, Windows XP Professional, SQL Server 2000, or Oracle operation. Refer to those products' printed documentation for basic operation information.

Intergraph gives you permission to print as many copies of this document as you need for non-commercial use at your company. You cannot print this document for resale or redistribution outside your company.

Send documentation comments or suggestions to [email protected].

Note

For information on SmartPlant 3D commands, refer to the SmartPlant 3D online Help. You can find the most recent guides and online Help in the Help folder on the SmartPlant 3D product CD. Copy the updated files from the Help folder on the CD to the [Product Folder]:\Program Files\Common Files\Intergraph\SmartPlant\Help folder on the workstation computers.

Send documentation comments or suggestions to [email protected].

Welcome to SmartPlant 3D


Welcome to SmartPlant 3D The Intergraph SmartPlant family of process industry solutions is an open line of discipline-specific software tools that provide an integrated solution for the entire plant life cycle. SmartPlant provides knowledge-based, intuitive, easy-to-use, accessible, flexible, and data-driven tools that support global workflows. The software enables users to create logical and physical definitions of the plant model and enables access to plant data from conceptual design through decommissioning.

SmartPlant is the fulfillment of the Intergraph vision to speed and improve the creation of information and provide this data to multiple users at any moment in the appropriate form. Workflows are compressed, reducing production time, lowering costs, enhancing global execution, and extending the life and usability of plant information.

SmartPlant 3D: An Overview SmartPlant 3D uses Web and Windows technologies to provide a familiar interface for the user to produce step-changes in three-dimensional detailed plant design, procurement, construction, and operational system performance. This new data-centric solution approach generated by SmartPlant 3D synchronizes key elements of intragration and relationships.

Intragration - SmartPlant 3D allows multiple engineering disciplines to work concurrently and in real-time against relational databases.

Relationships - SmartPlant 3D's relationship manager controls design changes across disciplines, which in turn establishes and maintains appropriate behaviors among structures, equipment, and systems.

SmartPlant 3D understands that plant design encompasses more than just 3-D modeling. As such, SmartPlant 3D is designed to integrate the SmartPlant Product Model with Enterprise Resource Planning (ERP), Operations and Maintenance (O&M), and Front End Engineering and Design (FEED). Traditionally, the only way to extract and load data from one application to another was through neutral format text files.

Session files are used by SmartPlant 3D to empower users to define their own view of objects in the database. The Project Management task enables users to administer and restrict user permissions to areas within the design catalog and the plant model. The optimistic locking feature in SmartPlant 3D makes it possible for users to work concurrently in the same environment and with the same component, whether it's specific to plant design or associated with the relationship of the components themselves. Additional features, such as angle locking and interference checking, make SmartPlant 3D the ideal software to manage system performance and maintain design intent.

Welcome to SmartPlant 3D


Related Topics Hardware and Software Requirements, page 13

Third-Party Integration


Third-Party Integration Equipment Modeling Capability Whether using one of the delivered symbols or a custom symbol that you define yourself, symbols are a key building block used to create your model. The software uses two basic types of symbols: 2D and 3D.

The 2D symbols are used to represent structural member cross-sections. Two-dimensional symbols for structural cross-sections are delivered in the [Product Folder]:\CatalogData\Symbols\CrossSections folder. You can use any of the defined cross-sections or define your own cross-sections using the software's 2D Symbols application. This application allows you to define different representations for the cross-section using layers. You can also define variables to drive the dimensions of the cross-section symbol.

An extensive library of 3D symbols is delivered in the various subfolders located in the [Product Folder]:\Catalog Data\Symbols folder on the server machine. The 3D symbols are used to represent equipment, hangers, HVAC components, piping components, and so forth in your model. You can also customize your own three-dimensional symbols using the SmartPlant 3D Symbol/Part Definition Wizard or Solid Edge.

The SmartPlant 3D Symbol/Part Definition Wizard allows you to create and customize three-dimensional symbols that fit your company or project. The wizard produces a Visual Basic project for building the symbol ports and graphics, and generates an Excel workbook for bulkloading the symbol data into the Catalog database.

SmartPlant 3D also integrates with Solid Edge to provide parametric modeling and assembly design capabilities. With Solid Edge, you can build intelligent equipment reference data libraries of base parts that can be placed into the SmartPlant 3D model. An entire catalog of standard equipment can be modeled with Solid Edge, as well as custom, one-of-a-kind equipment for specific plants. Solid Edge's design assistance automatically monitors how close the assemblies match design objectives and comply with design rules.

Additional information on the software's equipment modeling capabilities, including parameter descriptions of the delivered symbols, how to create 2D and 3D symbols and incorporate them into your reference data, is available in the SmartPlant 3D Reference Data Guide, the SmartPlant 2D Symbols User's Guide, and the SmartPlant 3D Symbols Reference Data Guide. Each of these documents is available from Help > Printable Guides in the software.

Isometric Drawing Capability The software's isometric drawing interface gives users the ability to create piping isometric drawings by extracting data from 3D models. Additionally, the SmartPlant

Third-Party Integration


3D isometric drawing interface works with ISOGEN software that not only enables users to create piping isometric drawings, including dimensioning, but that also allows users to generate notes, recognize attribute changes, and define which symbols to use in the final drawings. Knowledge of isometric drawings is required to effectively utilize this functionality.

Related Topics Welcome to SmartPlant 3D, page 7

Using The Engineering Framework


Using The Engineering Framework The Engineering Framework (TEF) standardizes and improves the communication among the various authoring tools you use in the course of designing, constructing, and operating a plant. The Engineering Framework acts as a central repository for data and a medium through which information is shared among other tools, such as INtools, SmartPlant P&ID, and SmartPlant 3D.

The following graphic displays what SmartPlant 3D publishes and retrieves and additional information about what data is exchanged.

Most of the commands that provide access to TEF functionality exist on the Framework menu in the various SmartPlant 3D task environments. For example, in the SmartPlant 3D Drawings and Reports task, you can use the commands on the Framework menu to publish volume and snapshot drawings, isometric drawings, and reports. You can also use the Framework menu to access the SmartPlant Foundation Web Client in order to browse in TEF and subscribe to change notifications and compare documents. In other SmartPlant 3D tasks, you can use the Framework menu commands to correlate items between the plant and the SmartPlant Foundation database and retrieve P&IDs, DDP files, Plant Breakdown Structure and Work Breakdown Structure, and Project Lists.

Using The Engineering Framework


For detailed information about using the TEF commands found in SmartPlant 3D, see the Common User's Guide and the Drawings and Reports User's Guide. Both documents are available with the Help > Printable Guides command in the software.

For more information about configuring SmartPlant 3D to work with The Engineering Framework (TEF), see Configure for The Engineering Framework, page 84.

Related Topics Configure for The Engineering Framework, page 84

Hardware and Software Requirements


Hardware and Software Requirements SmartPlant 3D is a state-of-the-art graphics application, capable of creating and displaying very complex three-dimensional models. As such, this technology requires comparable state-of-the-art hardware to ensure a successful, productive, and efficient experience.

Before beginning the installation, verify that the computers you will use meet the recommended guidelines for disk partitioning and meet both hardware and software requirements.

Related Topics Database Server Requirements, page 14 Disk I/O, page 47 Disk Partitioning Guidelines, page 20 Software Requirements and Loading Order, page 18 Workstation Requirements, page 15



Database Server Requirements Minimum System Resources 2.8 GHz Pentium 4 processor (Multiple processors for improved performance) SCSI Hard disk array, Raid level 0.1 or 10 recommended for server 4 GB RAM 100 BaseT or higher network interface Digital tape or DVD backup system for server CD-ROM drive access, either locally or through a network connection

Supported Operating Systems and Required Components Microsoft Windows 2000 Server Service Pack 4 Microsoft Windows Server 2003 Service Pack 1

Supported Databases Microsoft SQL Server Oracle Database

Software Prerequisites Microsoft SQL Server 2000 Service Pack 3a (or higher): Database Components; or Oracle Database 10g Release 2 (10.2) Microsoft .NET Framework 1.1 with Service Pack 1 (Delivered as part of Microsoft Windows Server 2003 SP1) and .NET Framework 2.0 Adobe Acrobat Reader 6.0 or higher (Required to view the Software License Agreement and Printable Guides. Version 7.0 is available on the product CD.)

Notes

For specifications regarding minimum hard drive disk space requirements by the product setup, refer to Disk Partitioning Guidelines, page 20.

On the server, distribute files across several disk drives with the following minimum distribution: OS and database software on one drive, database data files on another drive, and the database log file on the third drive.




Workstation Requirements Minimum System Resources: 2.8 GHz Pentium 4 processor or higher 2 GB RAM 100 BaseT network interface CD-ROM drive access, either locally or through a network connection 21" color monitor (capable of a minimum of 1024 x 768) Graphics cards designed for 3D intensive applications that meet the following requirements:

Color depth of 65,536 colors or higher 32-bit main RGBA pixel buffer Hardware OpenGL 1.1 support Hardware Z buffer: 32 bit 64 MB RAM recommended, 32 MB minimum, 128 MB RAM for dual

screens

4-bit minimum overlay buffer support 8-bit stencil buffer Hardware Alpha blending support Graphics acceleration set to full Hardware Anti-aliasing support recommended Latest available drivers should be installed Many of the recent generation video cards provide some level of OpenGL acceleration. Some manufacturers provide poor OpenGL drivers that can cause artifacts. Testing has shown that NVIDIA provides good drivers for its Geforce2 and beyond Graphics Processing Units (GPU). ATI GPU-based and Matrox graphic cards often seem to have OpenGL problems with their driver GPU combinations. Cards with double-buffered overlay planes (such as the Wildcat cards) have an advantage because highlighting can be done without having to do saves and restores, which may benefit performance in specific cases. In order to obtain better graphic performance with SmartPlant 3D, make the following setting for ATI, NVIDIA, and 3Dlabs graphics cards:

On ATI FireGL video cards, right-click on the desktop and select Properties > Settings > Advanced. On the Configuration tab, create a new configuration profile called SmartPlant 3D. After this configuration profile is created, select the SmartPlant 3D profile, select Modify and then check the Force copy swap box.



On NVIDIA GeForce cards, right-click on the desktop and select Properties > Settings > Advanced. On the NVIDIA Card tab, select OpenGL Settings in the Performance and Quality Settings section. In the dialog box that appears, change the Buffer-Flipping Mode selection to Use block transfer, and then and click OK.

On 3Dlabs Realizm cards, right-click on the desktop and select Properties > Settings > Advanced. On the 3Dlabs Card tab, select OpenGL and change the Buffer Swap Mode selection to Force Swap Copy, and then click OK.

Supported Operating Systems and Components Microsoft Windows 2000 Professional Service Pack 4 Microsoft Windows XP Professional Service Pack 2

Supported Database Clients Microsoft SQL Server 2000 Client (Required only when the Project Management option is installed.) Oracle Database 10g Client Release 2 (10.2)

Software Prerequisites Microsoft Internet Explorer 6.0 Service Pack 1 (Required for viewing the online documentation delivered with the software) Microsoft XML Core Services (MSXML) 4.0 Service Pack 2 Microsoft .NET Framework 1.1 with Service Pack 1 (Core product included on the product CD) and .NET Framework 2.0 Microsoft Data Access Components (MDAC) 2.7 or higher (MDAC 2.8.1 is delivered as part of Microsoft XP Service Pack 2.) Microsoft SQL Server 2000 SP3a (or higher): Database Components (Required only when the Project Management option is installed); or Oracle Database 10g Release 2 (10.2) Microsoft Office 2000 (with Service Pack 3 SR1a), Microsoft Office 2003, or Microsoft Office XP Adobe Acrobat Reader 6.0 or higher (Required to view the Software License Agreement and Printable Guides. Version 7.0 is available on the product CD.)

Notes

For specifications regarding minimum hard drive disk space requirements by the product setup, refer to Disk Partitioning Guidelines, page 20.

Dual screen configurations should have either a single graphics card with two VGA outputs or two identical graphics cards. The graphics card(s) should otherwise meet the requirements of the specified graphics card recommendations.

Use thread safe video drivers and CAD application certified video cards when using multiple processor systems.



Software Requirements and Loading Order Software Requirements The ability to run the software successfully is greatly affected by the order in which all the necessary and underlying products are loaded. Do not deviate from the recommended order. Doing so can result in a component that is out-of-sync with the guidelines; consequently, it will be difficult to determine the exact nature of any post-installation problems you encounter should you deviate from the recommended installation order.

The following table outlines the prerequisites associated with each of the SmartPlant 3D installations and the established load order for each:

Database Server Installation Workstation Installation Windows 2000 Server or Windows Server 2003 Windows 2000 Professional or

Windows XP Professional Windows 2000 Service Pack 4 or Windows Server 2003 Service Pack 1

Windows 2000 Service Pack 4 or Windows XP Service Pack 2

Microsoft .NET Framework 1.1 and .NET Framework 2.0

Microsoft .NET Framework 1.1 and .NET Framework 2.0

Microsoft .NET Framework 1.1 Service Pack 1 (Windows 2000 Server) or Microsoft .NET Framework 1.1 Service Pack 1 for Windows Server 2003

Microsoft .NET Framework 1.1 Service Pack 1

Internet Explorer 6.0 Service Pack 1

Microsoft XML 4.0 Service Pack 2

Adobe Acrobat Reader 6.0 or higher Adobe Acrobat Reader 6.0 or higher

Microsoft Office 2000, Microsoft Office 2003, or Microsoft Office XP1,3

Microsoft Data Access Components (MDAC) 2.7 or higher

Oracle Database 10g Release 2 (10.2) or SQL Server 2000

Oracle Database 10g Client Release 2 (10.2) or SQL Server 2000 Client Tools2



SQL Server 2000 Service Pack 3a (or higher): Database Components3

SQL Server 2000 Service Pack 3a (or higher): Database Components2

1In order for drawings that contain embedded Excel reports to display properly, you must install Service Pack 3 (SP3) and Service Release 1a for Office 2000. You can download SP3 and SR1a by clicking Start > Windows Update and then selecting Office Update on the Microsoft Windows Update website. 2Microsoft SQL Server 2000 Client Tools (with SQL Server 2000 SP3a or higher) is required only for the client software installation if the Project Management option is installed; otherwise, they are not integral to the default workstation software installation. 3When creating drawing borders or embedded reports within the Drawings and Reports task on computers with Microsoft Office XP or Office 2003, you must modify the security settings in Excel to allow Visual Basic projects to run. To change this setting, open Excel, and select Tools > Macros > Security. On the Trusted Sources tab, select Trust access to Visual Basic Project. This setting must be modified before you update drawings and generate the report(s) within it.

Important

Do not skip any restarts recommended by the system. Doing so can have unintended consequences.

Other users who want to perform different tasks in the overall plant design workflow might need additional software, such as Visual Basic 6.0 and Unigraphics Solid Edge Version 16. Additionally, if you intend to reference or export PDS projects, you must install the appropriate PDS add-in. The PDS data reference and export add-ins are delivered in PDS version-specific folders on the product CD.

Note

This version of the software supports PDS 8.0 or higher. PDS software and all of its prerequisite software are also required in order

to use the PDS integration functionality. For more information, see Integrating with PDS, page 98.

Special Consideration for Non-English Locales The system language specified for Microsoft Office must be the same as the system language specified by the operating system. For example, if your operating system language is English, Microsoft Office must also be set to English. For overall assistance with installing the software in a non-US English environment, visit the Intergraph Support web site at http://ppm.intergraph.com/support/support.asp.




Disk Partitioning Guidelines For best performance when loading and running the software, partition the hard drive according to the following guidelines:

Format all partitions as NTFS file systems. By default, the software is installed to C:\Program Files\SmartPlant\3D.

Ensure you have sufficient free space on your C:\ partition (or another partition if you wish to install there) according to the following information:

Minimum Disk Space Requirements for Prerequisite Software Windows 2000 Service Pack 4 Varies. Refer to the ReadMe information

delivered with the Service Pack. Windows 2003 Server Service Pack 1

329.3 MB

Windows XP Service Pack 2 Varies. Refer to the ReadMe information delivered with the Service Pack.

Internet Explorer 6.0 Service Pack 1

12 MB

Microsoft Office 2000, Microsoft Office 2003, or Microsoft Office XP

Varies depending on system configuration. Refer to the ReadMe information delivered with the product.

Adobe Acrobat Reader 7.0 60 MB Microsoft .NET Framework 1.1 with Service Pack 1 and .NET Framework 2.0

36 MB

Microsoft XML 4.0 Service Pack 2 1.3 MB Microsoft Data Access Components (MDAC) 2.7 or higher

20 MB

Microsoft SQL Server 2000 270 MB Microsoft SQL Server 2000 Client Tools

153 MB

Microsoft SQL Server 2000 Service Pack 3a (or higher): Database Components

147 MB

Oracle Database 10g 512 MB, 1 GB Swap space, 400 MB in temp location, 1.5 GB for Oracle software, 1.5 GB for preconfigured database



Oracle Database 10g Client 550 MB

Minimum Disk Space Requirements for Software Setup SmartPlant 3D Installation - Default setup for a workstation computer1 762 MBSmartPlant 3D Installation - Administrative setup for a workstation computer2

944 MB

SmartPlant 3D Installation - Complete setup for a workstation computer3 951 MBSmartPlant 3D Reference Data - Default setup for database server 529 MB

1 The default setup for a SmartPlant 3D workstation computer provides all the environments necessary for general SmartPlant 3D modeling. 2 The administrative setup for a SmartPlant 3D workstation computer provides the following functionality: plant creation, database migration, access management, database interference detection and includes the following options only: Catalog, Project Management, SmartPlant 3D Server Connectivity, Bulkload Reference Data, and Database Interference Detection Service. 3 The complete setup for a SmartPlant 3D workstation computer includes all features and combines the functionality provided in the default and administrative setups. Additionally, a complete setup includes the 3D Model Import and Piping Specification Remote Access Server options, which installs the required components for importing model data into SmartPlant 3D and the necessary software for correlating piping specification data between SmartPlant 3D and SmartPlant P&ID, respectively.

You also will need additional disk space if you intend to use other products, such as Visual Basic 6.0 with Visual Studio Service Pack 5 or Solid Edge version 16. Please consult your system administrator for this and additional software not provided by Intergraph PPM.

Warning

Do not continue with installation until enough disk space is free on the database server and each workstation computer as stated in the aforementioned procedure.


Setting Up the Database


Setting Up the Database SmartPlant currently supports Oracle 10g Release 2 (10.2) and Microsoft SQL Server 2000.

Installing any database involves significant decisions regarding the size of the database, the maximum number of users, the frequency of automatic backups, and other important issues. Therefore, the following sections provide only suggestions for tuning your database configuration to work with SmartPlant software. The ultimate database creation and configuration depends on the policies and standards at your company.

Related Topics Configure Microsoft Distributed Transaction Coordinator, page 25 Configure the Distributed COM Users Group, page 26 Configure the Oracle Client, page 65 Enable Network Access in Windows Server 2003, page 23 Install Oracle Client Software, page 64 Installing and Configuring Microsoft SQL Server Client Software, page 61 Installing and Configuring Microsoft SQL Server, page 28 Installing and Configuring Oracle Server Software, page 34 Special Instructions for Microsoft Windows Server 2003, page 23



Special Instructions for Microsoft Windows Server 2003

When you install Windows Server 2003, most of the services are disabled by default, including MSDTC network access. If you are using COM+/DTC, you are most likely to receive errors when you attempt to perform distributed actions, including flowing transactions to another computer or talking to a resource manager such as SQL Server on another machine. To enable your distributed scenarios you need to enable MSDTC network transactions.

When you install Service Pack 1 (SP1) for Windows Server 2003, all network MSDTC transactions are disabled, even if network transactions were enabled prior to installing the service pack. Consequently, you must manually configure MSDTC and re-enable your distributed transactions. Installing SP1 also adds the Distributed COM Users group as a new group to the Local Users and Groups on the server machine. Members of this group are permitted to launch, activate, and use Distributed COM objects, such as the SmartPlant 3D Name Generator Service. Because SmartPlant 3D users and groups must have access to COM+ objects, you must manually add the necessary members to the Distributed COM Users group.

Related Topics Configure Microsoft Distributed Transaction Coordinator, page 25 Configure the Distributed COM Users Group, page 26 Enable Network Access in Windows Server 2003, page 23

Enable Network Access in Windows Server 2003 The following procedures for enabling network access are required only if you are using Windows Server 2003.

Enable Network COM+ Access 1. Open the Control Panel and double-click Add or Remove Programs. 2. In the Add or Remove Programs window, click Add/Remove Windows

Components. 3. On the Windows Components Wizard page, select Application Server in the

Components list, and then click Details. 4. In the Subcomponents of Application Server list, click Enable network COM+

access and then click OK. 5. Click Next to complete the Windows Components Wizard. 6. Click Finish on the Configuring Components page.



Enable Network DTC Access COM+ applications that use databases, and that you install on separate computers do not always perform optimally unless you enable network DTC access. Use the following procedure to enable network DTC access:

1. Open the Control Panel and double-click Add or Remove Programs. 2. In the Add or Remove Programs window, click Add/Remove Windows

Components. 3. On the Windows Components Wizard page, select Application Server in the

Components list, and then click Details. 4. In the Subcomponents of Application Server list, click Enable network DTC

access and then click OK. 5. Click Next to complete the Windows Components Wizard. 6. Click Finish on the Configuring Components page. For the settings to take

effect, you must stop and restart the Distributed Transaction Coordinator service.

Stop and Restart MSDTC 1. Open the Control Panel, double-click Administrative Tools, and then double-

click Services. 2. Right-click the Distributed Transaction Coordinator service, and select Stop

from the shortcut menu.

3. Right-click the Distributed Transaction Coordinator service again, and select

Start from the shortcut menu.

Important

If you have additional resource manager services that participate in the distributed transactions, you must stop and restart those services as well.



Related Topics Special Instructions for Microsoft Windows Server 2003, page 23

Configure Microsoft Distributed Transaction Coordinator This procedure to configure Microsoft Distributed Transaction Coordinator (MSDTC) is required only if you are using Windows Server 2003 with Service Pack 1 (SP1).

1. Open the Control Panel, double-click Administrative Tools, and then double-click Computer Management.

2. Under Console Root, expand the Component Services and Computers nodes. 3. Under the Computers node, right-click on My Computer and select Properties.

4. In the My Computer Properties dialog box, click the MSDTC tab. 5. On the MSDTC tab, click Security Configuration. The Security Configuration

dialog box displays. 6. In the Security Settings section, enable Network DTC Access. 7. In the Client and Administration section, enable Allow Remote Clients and

Allow Remote Administration. 8. In the Transaction Manager Communication section, enable the Allow

Outbound, Allow Inbound, and No Authentication options. 9. Verify that Enable XA Transactions is enabled. 10. In the DTC Logon Account section, verify that NT AUTHORITY/Network

Service appears in the Account box. 11. Click OK.



12. In the DTC Console Message box, click Yes to stop and restart the MSDTC service.

13. Click OK in the DTC Console Message box after the MSDTC service is

restarted. 14. Click OK to close the My Computer Properties dialog box.

Related Topics Special Instructions for Microsoft Windows Server 2003, page 23 Special Instructions for Windows XP with Service Pack 2, page 57

Configure the Distributed COM Users Group This procedure to add users to the Distributed COM Users group is required only if you are using Windows Server 2003 with Service Pack 1 (SP1).

1. Open the Control Panel, double-click Administrative Tools, and then double-click Computer Management.

2. Under Computer Management, expand the System Tools and Local Users and Groups nodes.

3. Under the Local Users and Groups node, click Groups.

4. In the right pane of the Computer Management window, double-click

Distributed COM Users. 5. In the Distributed COM Users Properties dialog box, click Add.



6. In the Select Users, Computers, or Groups dialog box, type the user accounts you want to add to the Distributed COM Users Group into the Enter the object names to select box.

Tip

You can enter multiple accounts by separating each one with a semicolon. For example, you can type Domain1\User1;Domain1\User2;Domain1/User3, and so on.

7. Click OK to close the Select Users, Computers, or Groups dialog box. 8. Click OK to close the Distributed COM Users Properties dialog box.

Related Topics Special Instructions for Microsoft Windows Server 2003, page 23



Installing and Configuring Microsoft SQL Server Because system configurations, database software, and individual company standards vary, use this section as a checklist instead of step-by-step instructions. Please contact Intergraph Customer Support for specific configuration questions.

If you intend to use the software with an Oracle database, skip the topics in this section. For information about setting up and configuring an Oracle database to run with the software, see Installing and Configuring Oracle Server Software, page 34.

Related Topics Assign System Administrator Privileges, page 30 Configure SQL Server 2000 Account for Name Generator Service, page 29 Create a SQL Server Database Alert, page 31 Install Microsoft SQL Server 2000, page 28 Verify Automatic Startup of Microsoft SQL Server 2000 Services, page 29

Install Microsoft SQL Server 2000 Because system configurations, database software, and individual company standards vary, use this section as a checklist instead of step-by-step instructions. Please contact Intergraph Customer Support for specific configuration questions.

During installation of the database components, setup displays various dialog boxes that prompt you for information. We recommend the following:

1. Use the Typical installation to install a named instance of the Microsoft SQL Server software on your database server.

2. On the Services Accounts page, select Use the same account for each service. Auto start SQL Server Service button.

3. Select Service Settings as required for your situation.

Tips

A local system account does not have network access rights in Windows 2000 and restricts your SQL Server installation from interacting with other servers.

A domain user account offers more flexibility and is typically used because many server-to-server activities can be performed only with a domain user account, including remote procedure calls, replication, and backing up network drives.

4. On the Authentication Mode page, select Windows Authentication Mode.



Important

Because SmartPlant 3D backups use SQL Server functionality, the User ID to which the SQL server is mapped must have Write permission to the backup folder.

Related Topics Installing and Configuring Microsoft SQL Server Client Software, page 61 Installing and Configuring Microsoft SQL Server, page 28

Verify Automatic Startup of Microsoft SQL Server 2000 Services

1. Open the Control Panel, double-click Administrative Tools, and then double-click Services.

2. Verify that the Status field is set to Started and the Startup Type field is set to Automatic, for each of the following services: Distributed Transaction Coordinator, Microsoft Search, and MSSQL$

Tip

The MSSQL service is appended with the named instance you specified when you installed SQL Server 2000. For example, if you installed SQL Server 2000 as an instance named Instance1, the service appears as MSSQL$Instance1.

3. To change the Status or Startup Type fields, right-click the service name, and select Properties from the shortcut menu.

4. On the General tab, select Automatic from the Startup type list. 5. In the Service status section, click Start. 6. Click OK.


Configure SQL Server 2000 Account for Name Generator Service

If the SQL Server is not registered in the Enterprise Manager console on the server computer, you must register it before using the SQL Server 2000 software. Perform the following procedure on the server computer to register the SQL Server in the Enterprise Manager console.

1. Open Enterprise Manager and expand the listing under Microsoft SQL Servers in the left tree view.



2. In the tree view, right-click SQL Server Group, and select New SQL Server Registration in the shortcut menu. The Register SQL Server Wizard appears.

3. Click Next on the Register SQL Server Wizard page. 4. Select the server name in the Added Servers box. If the server name does not

appear in the Added servers box, locate the server in the Available servers list, and click Add.

5. Click Next. 6. On the Select an Authentication Mode page, leave the default setting: The

Windows account information I use to log on to my computer (Windows Authentication).

7. Click Next. 8. On the Select SQL Server Group page, leave the default setting: Add the SQL

Server(s) to an existing SQL Server group. 9. Click Next. 10. Click Finish on the Completing the Register SQL Server Wizard page.

Note

A Register SQL Server Messages dialog box appears with the following message: WORKSTATION NAME - Registered successfully.

11. On the Register SQL Server Messages dialog box click Close.

Note

Before exiting Enterprise Manager, perform the steps Assign System Administrator Privileges, page 30.

Close the Microsoft SQL Server Enterprise Manager.


Assign System Administrator Privileges Perform the following steps on the SmartPlant 3D server computer.

1. Open Enterprise Manager and expand the listing under Microsoft SQL Servers in the left tree view.

2. Expand the listing under SQL Server Group in the left tree view. 3. Expand the listing under the in the left tree view. 4. Expand the listing under Security in the left tree view. 5. In the left pane, right-click Logins.



6. Select New Login from the shortcut menu. 7. On the General Tab of the SQL Server Login Properties - New Login dialog

box, enter the user account you want to be assigned administrative privileges in the Name text box. For example, type Plant1\SP3DAdminUser1.

8. On the Server Roles tab, select the System Administrators check box.

9. Click OK.


Create a SQL Server Database Alert When the SmartPlant 3D database server is running low on disk space, the software begins to display error messages since data can no longer be persisted or logged. SQL Server, however, does not issue any particular alerts for the workstation computers when the disk is full or becoming limited.

Using System Monitor, the SmartPlant 3D administrator can create an alert to be issued when a threshold value for a System Monitor has been reached. In response to the alert, System Monitor can launch an application to handle the alert condition. For example, you can create an alert that is raised when the number of deadlocks exceeds a specific value.

You must perform the following procedure on the SmartPlant 3D server computer.

1. If you are running Windows 2000 Server, click Start > Settings > Control Panel, and then double-click Administrative Tools.

If you are running Windows Server 2003, click Start > Administrative Tools > Performance, expand the Performance Logs and Alerts node, and then skip to step 4.

2. In the Administrative Tools window, double-click Performance.



3. On the Tree tab of the Performance window, expand the Performance Logs and Alerts node.

4. Right click on Alerts and select New Alert Settings on the shortcut menu. 5. In the New Alert Settings dialog box, type a name for the new alert in the Name

field and click OK.

Tip

A dialog box appears titled with the name you defined for the new alert.

6. On the General tab of the Alert dialog box, click Add to add a counter to the alert.

Note

All alerts must have at least one counter. 7. On the Select Counters dialog box, select a Microsoft SQL Server object in the

Performance Object drop-down list. 8. In the Select counters from list drop-down list, select a counter and click Add to

add the counter to the alert.

Tip

You can repeat steps 7 and 8 to select and add additional counters to the alert.

9. Once all counters have been added, click Close to return to the Alert dialog box. 10. In the Alert dialog box, click either Over or Under from the Alert when value is

list. 11. In the Limit box, enter a threshold value.



Note

Depending on what you selected in step 10, the alert will be generated when the value for the counter is more than or less than the threshold value.

12. In the Interval box, enter the number of units of time that define the duration of the sample interval.

Tip

You can use the scroll arrows, to change the units. 13. In the Units box, define the unit of time to determine the duration of the sample

interval. 14. On the Action tab, specify the actions to occur each time the alert is triggered. 15. On the Schedule tab, set the start and stop schedule for the alert scan. 16. Click OK to close the Alert dialog box and activate the alert setting.

Note

For more information about using System Monitor and setting up SQL Server alerts, see the documentation delivered with Microsoft SQL Server 2000.




Installing and Configuring Oracle Server Software Because system configurations and individual company standards vary, use this section as a checklist instead of step-by-step instructions. Please contact Intergraph Customer Support for specific configuration questions.

Notes

Intergraph recommends that you set up the Windows server network before installing Oracle. Also Oracle recommends a static IP address. You should install the Oracle server software as the local administrator. For more information, refer to your Oracle installation documentation.

If you intend to use the software with a SQL Server database, skip the topics in this section. For information about setting up and configuring a SQL Server database to run with the software, see Installing and Configuring Microsoft SQL Server, page 28.

Oracle Instances If one server hosts the databases of several products, Intergraph recommends that each product's database be a separate instance, each of which can host multiple plants.

The advantage of placing each product's database its own instance is that only the affected application will be off-line during backup, performance tuning, and other database maintenance activities. Additionally, global tuning parameters that apply to one instance can be tailored to the specific product requirements.

According to Oracle documentation, the only limit to the number of instances you can have on any machine is the availability of resources. However, the number of instances on one database server should be minimized, because each additional instance puts additional load on the server.

Each instance adds redundant tablespaces, rollback segments, background processes, and memory requirements for each SGA (System Global Area). For this reason, you should start by putting the database of one product for several plants into a single instance. Then, when the number of plants increases, or a plant becomes very large, consider separating the database into new instances, adding server memory, or even adding database servers.

Important

Oracle recommends that database activity on the database server consume no more than 50 percent of the available memory. Refer to your Oracle documentation for specific requirements.

Related Topics Configure Oracle Networking Components, page 40 Initialize the Oracle Database, page 39



Install Oracle Server Software (Basic Installation for Enterprise Edition), page 35

Verify Automatic Startup of Oracle Database Services, page 41

Install Oracle Server Software (Basic Installation for Enterprise Edition)

During installation of the database components, setup displays various dialog boxes that prompt you for information. We recommend that you refer to your Oracle documentation for specific instructions concerning the dialog boxes and wizard pages. The steps below show an example installation using Basic Installation for Enterprise Edition.

Install Oracle Using Basic Installation for Enterprise Edition 1. Select the Basic Installation method to install the Oracle Server software on your

database server and specify Enterprise Edition as the Installation Type. 2. Check the Create Starter Database to create the initial database setup.

Note

The starter database will be deleted later and replaced with the appropriate database setup for SmartPlant 3D. Creating it during initial installation allows Oracle to set up appropriate support for the database and makes updates easier.

3. Click Next through the Prerequisite and Summary dialogs to verify the minimum requirements for installation.

4. When the End of Installation page displays, click Next, then click Yes on the confirmation dialog box.

5. Run the Oracle Universal Installer from the Startup menu. Click Next on the Welcome page.

6. On the Specify Source Location page, browse to the appropriate installation path and file. Click Next.

7. On Select Installation Type page, select Custom installation type so you can select which components to install. Click Next.

8. On the Specify Home Details page, specify the destination information for the installation. Click Next.

Caution

Make sure the destination information points to the Oracle home as defined in the registry. If not, this installation creates a second Oracle home location that will cause problems when running Oracle.



9. On the Available Product Components page, check Oracle Services For Microsoft Transaction Server 10.2.0.1.0 under Oracle Windows Interfaces 10.2.0.1.0, then click Next.

Note

For information on the other interfaces, see your Oracle installation documentation.

10. On the Product-Specific Prerequisite Checks page, verify the information and click Next.

11. On the Oracle Services for Microsoft Transaction Server page, leave the default Port Number and click Next.

12. On the Summary page, verify the settings and click Install. If any of the settings are incorrect, click Back to return to the previous installation pages.

13. After installation completes, click Yes on the confirmation dialog to exit the Oracle Universal Installer.

Delete the Starter Database 1. The Oracle Database Configuration Assistant automatically launches. Click

Next to continue with database configuration.

Note

If the Oracle Database Configuration Assistant does not start automatically, run it from the Startup menu.

2. On the Database Configuration Assistant, Step 1 of 2: Operations page, select Delete a Database, then click Next.

Note

You will delete the starter database only. The database configuration information remains so you can create a new database for use with SmartPlant 3D.

3. On the Database Configuration Assistant, Step 2 of 2: Operations page, select the database you want to delete and click Finish. Click Yes on the confirmation dialog box.

4. When the database deletion is complete, click Yes to perform another operation and create a new database for use with SmartPlant 3D.

Create a New Database 1. The Database Configuration Assistant starts again so you can configure a new

database. On the initial page, select Create a Database and click Next. 2. On the Step 2 page, select Custom Database and click Next.

Tip

Click Show Details to view the template setting for creating a customized database. Refer to your Oracle documentation for more



information concerning the settings shown on this dialog box. Click Close to return to the Database Configuration Assistant.

3. On the Step 3 page of the Database Configuration Assistant, specify the database name and SID. Click Next.

4. For Step 4, check Configure the Database with Enterprise Manager and select the Use Database Control for Database Management option. Refer to your Oracle documentation for more information concerning this option. Click Next to continue.

5. On Step 5, specify passwords as needed for the database accounts, then click Next.

6. For Step 6, select File System as the storage mechanism for the database. Click Next to continue. Refer to your Oracle documentation for more information concerning file storage settings.

7. On the Database Configuration Assistant, Step 7 of 12 page, select Use Common Location for All Database File as the location in which to create database files. Browse to the appropriate location, if necessary. Click Next to continue.

Tips

Click File Location Variables to view and specify variables and their values.

8. If you are using Global Workshare, on Step 8 of the Database Configuration Assistant, check Specify Flash Recovery Area. Browse to a location to use as the Flash Recovery Area and specify an area size. Check Enable Archiving and click Edit Archive Mode Parameters to set the archiving parameters for your database.

These options not necessary if you do not use Global Workshare. Click Next to continue.

9. For Step 9, on the Database Components tab, select Enterprise Manager Repository and click Next.

10. On Step 10 of the Database Configuration Assistant, select the Memory tab and select the Typical memory option. Set the percentage to 40%.

Tip

Click Show Memory Distribution to see the SGA Size, PGA Size, and Oracle Process Size values. Refer to your Oracle installation documentation for more information.

11. Click All Initialization Parameters, then click Advanced Initialization Parameters to show the current parameter definitions.

12. Set os_authent_prefix to empty quotation marks (""), removing the OPS$ value. Check the Override Definition field.

13. Set open_cursors to 1000.



14. Click Close to return to Step 10 of the Database Configuration Assistant. 15. Select the Sizing tab and set the number of Processes. We recommend setting this

value to 15 processes per user plus additional for other activity in the database. 16. Select the Character Sets tab and select the Use the default option. For more

information on the Character Set options, see your Oracle installation documentation.

17. On the Connection Mode tab, select the server mode for your database. Click Next to continue to the next configuration step.

18. On Step 11 of 12, set your database storage options. Select Controlfile in the hierarchy to specify the Controlfile mirror image files.

19. If you are using Global Workshare, set the following: Select Tablespaces > SYSTEM in the hierarchy and go to the Storage tab. In the Extent Management box, select Locally managed and Automatic Allocation. In the Segment Space Management box, select Automatic. In the Enable Logging box, select Yes to generate redo logs and make the database recoverable.

If you are not using Global Workshare, this step is not necessary.

20. Select Redo Log Groups in the hierarchy. On the General tab, click File Location Variables to set the redo log variables and values. Click OK to return to Step 11 and continue defining database storage options.

Tip

Intergraph highly recommends that you use a redo log file size of at least 100 MB.

When setting up log sizes, keep in mind that the model database has the most activity and requires the most space for operation.

21. Click Next to continue to Step 12 and set Creation Options for the database. 22. On Step 12, select Create Database. Selecting Generate Database Creation

Scripts is optional, but we recommend you use it and set a destination directory accordingly.

23. Click Finish to begin database creation. A confirmation dialog displays all of the custom database settings and shows the operations to be performed. Review the settings and click OK to proceed.

24. When the database creation is complete, check the logfiles as indicated by the Database Configuration Assistant. Click Exit.

Related Topics Installing and Configuring Oracle Server Software, page 34



Initialize the Oracle Database After the Oracle software is installed and configured (that is, you can connect from a client to the Oracle database), you must next configure the database to run with SmartPlant 3D software.

The SmartPlant 3D Reference Data Installation delivers the following three sample script files to the \Tools\ScriptsToInitOracleDB folder. These files must be run in the following order:

SP3DRoles.sql SP3DUser.sql SP3DProjectAdministrator.sql You use these script files to create the necessary schemas, users and roles used to run the software on Oracle. The delivered script files, however, are only samples and must be edited to fit your server configurations.

Caution

An administrative user must run the scripts on the server. Before proceeding, place a copy of each of the five sample script files on the server computer.

The scripts must be run in the specific order listed as previous scripts create items that are used in subsequent scripts. Do not deviate from the following sequence of steps.

Create the Roles Needed for SmartPlant 3D Users 1. Log on to the Oracle database server computer using the local administrative

account. 2. Open SQL Plus. The Log On dialog box appears. 3. In the User Name field, type SYS. 4. In the Password field, type the password for the SYS account. 5. In the Host String field, type as SYSDBA. 6. Click OK. The Oracle SQL *Plus window displays. 7. At the SQL prompt, type @:\SP3DRoles.sql and press Enter.

For example, if you placed a copy of the script file in the root folder on the C drive, you type @C:\SP3DRoles.sql.

8. After the script finishes, click File > Exit.

Create the Users Needed for SmartPlant 3D 1. Log on to the Oracle database server computer using the local administrative

account.



2. Navigate to the SP3DUsers.sql script file and open it in Notepad. 3. Edit the external user identified in the file as needed. Use the following syntax:

domain name\username, and then click File > Save 4. Open SQL Plus. The Log On dialog box appears. 5. In the User Name field, type SYS. 6. In the Password field, type the password for the SYS account. 7. In the Host String field, type as SYSDBA. 8. Click OK. The Oracle SQL *Plus window displays. 9. At the SQL prompt, type @:\SP3DUsers.sql and press Enter.

For example, if you placed a copy of the script file in the root folder on the C drive, you type @C:\SP3DUsers.sql.


Create the Administrative User 1. Log on to the Oracle database server computer using the local administrative

account. 2. Navigate to the SP3DProjectAdministrator.sql script file and open it in

Notepad. 3. Edit the external user identified in the file as needed. Use the following syntax:

domain name\username, and then click File > Save 4. Open SQL Plus. The Log On dialog box appears. 5. In the User Name field, type SYS. 6. In the Password field, type the password for the SYS account. 7. In the Host String field, type as SYSDBA. 8. Click OK. The Oracle SQL *Plus window displays. 9. At the SQL prompt, type @:\SP3DProjectAdministrators.sql

and press Enter.

For example, if you placed a copy of the script file in the root folder on the C drive, you type @C:\SP3DProjectAdministrators.sql.


Related Topics Installing and Configuring Oracle Client Software, page 64 Installing and Configuring Oracle Server Software, page 34

Configure Oracle Networking Components Oracle Net combines configuration abilities with component control to provide an integrated environment for configuring and managing client connections to services



via a net service name. The SmartPlant 3D software uses the Oracle net service to establish and maintain network sessions from client applications to the Oracle database server. After a network connection is established, this utility acts as a data courier for the client application and the database server.

If you follow the procedures provided to and , the Oracle Networking Components should be configured correctly.

Oracle Net Configuration Assistant The Oracle Net Configuration Assistant allows you to configure the listening protocol address and service information for an Oracle database. See the Oracle Net Services Administrator's Guide in your Oracle documentation for more information about using this utility and creating net service name connections.

Important

If you are using Global Workshare, you should configure a net service for each server involved in the workshare environment.

Related Topics Configure the Oracle Client, page 65 Install Oracle Client Software, page 64 Installing and Configuring Oracle Server Software, page 34

Verify Automatic Startup of Oracle Database Services 1. Open the Control Panel and double-click Administrative Tools. 2. Double-click Services. 3. Verify that the Status field is set to Started and the Startup Type field is set to

Automatic, for each of the following services:

Distributed Transaction Coordinator

OracleMTSRecoveryService

OracleService

OracleDBConsole

OracleTNSListener

Notes

The OracleService is your Oracle database instance. It is appended with the named Oracle System identifier (SID) you specified when you created the Oracle database. For example, if your SID is Plant1, the service appears as OracleServicePlant1.



The TNSListener service is required to allow clients to connect to the Oracle database.

4. To change the Status or Startup Type fields, right-click the service name, and select Properties from the shortcut menu.

5. On the General tab, select Automatic from the Startup type list. 6. In the Service status section, click Start. 7. Click OK.


Create the Oracle Streams Tablespace You must perform the following procedure at the Host and all the Satellite locations that will participate in Global Workshare.

1. Open SQL *Plus and connect as an administrative user who can create users, grant privileges, create tablespaces, and alter users.

2. At the SQL prompt, type the following statement to create a Streams tablespace: CREATE TABLESPACE streams_tbs LOGGING DATAFILE 'c:\oracledatafiles\streams_tbs1.ora' SIZE 25M REUSE AUTOEXTEND ON NEXT 8K MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL;

3. Repeat the procedure at each database that will participate in the Workshare environment.

Note

Do not specify any tablespace name other than streams_tbs when you create the Streams tablespace. Streams_tbs is the tablespace name used by the software when it generates the replication scripts.


Create the Oracle Streams Administrator You must perform the following procedure at the Host and all the Satellite locations.

1. Open SQL *Plus and connect as an administrative user who can create users, grant privileges, create tablespaces, and alter users.

2. Create the Streams administrator. At the SQL prompt, type the following statement and press Enter: CREATE USER STRMADMIN IDENTIFIED BY STRMADMIN



DEFAULT TABLESPACE streams_tbs QUOTA UNLIMITED ON streams_tbs;

3. Grant the CONNECT, RESOURCE, and DBA roles to the Streams administrator. At the SQL prompt, type the following statement and press Enter: GRANT CONNECT, RESOURCE, DBA TO STRMADMIN;

4. Use the GRANT_ADMIN_PRIVILEGE procedure in the DBMS_STREAMS_AUTH package to grant the required privileges to the Streams administrator. At the SQL prompt type the following statement and press Enter: BEGIN DBMS_STREAMS_AUTH.GRANT_ADMIN_PRIVILEGE ( grantee => ' STRMADMIN', grant_privileges => true); END;/

5. In order to assist with administration, grant the following roles to the Streams administrator. At the SQL prompt, type the following statements and press Enter: GRANT SELECT_CATALOG_ROLE to STRMADMIN; GRANT SELECT ANY DICTIONARY to STRMADMIN;

6. Repeat steps 1 through 5 to set up a Streams administrator on each of the databases that will participate in the Workshare.

Note

Do not specify any user name other than STRMADMIN when you create the Streams administrator. STRMADMIN is the user name used by the software when it generates the replication scripts.


Monitoring the Databases


Monitoring the Databases You can use the following guidelines for setting up and monitoring your databases. Since there are many viable hardware and software configurations that you can use to set up the databases, refer to the documentation for your components for more information on performance and scalability issues.

To achieve adequate performance and measurements while monitoring the system, use the settings outlined in Set Up the Database Server, page 45.

Related Topics Appendix: Recommendation for Database Monitoring (SQL Server), page

170 Disk I/O, page 47 Disk Usage, page 49 Set Up the Database Server, page 45



Set Up the Database Server The needs of a database server are different than those of a file server. Perform the following procedure to configure the settings for the database server:

1. Open the Control Panel and double-click the Network and Dial-up Connection Properties folder.

2. Double-click the Local Area Connection icon, and click Properties on the Local Area Connection Status dialog box.

Tip

You can also right-click Local Area Connection icon, and select Properties on the shortcut menu.



3. In the Local Area Connection Properties dialog box, select File and Printer Sharing for Microsoft Networks, and click Properties.

4. In the File and Printer Sharing for Microsoft Network Properties dialog box,

select Maximize data throughout for network application, and click OK. 5. Click OK to close the Local Area Connection Properties dialog box.

Related Topics Monitoring the Databases, page 44



Disk I/O Data file and log file location and sizing are critical to obtaining optimal performance. I/O is one of the most common bottlenecks in database servers. Consequently, sizing I/O is critical to performance.

Caution

Disk drives should not be run at more than 75% of the maximum I/O capacity.

The two types of I/O are Random I/Os and Sequential I/Os. The type of I/O determines the number of I/Os per second that a disk drive can handle. Random I/Os require a longer time to complete than sequential I/Os.

Random I/Os The amount of time spent performing random I/Os is governed by the time it takes to perform the seek operations. Since the random I/O involves requests for data on different parts of the disk, most of the time spent in the I/O will be the seek time. If a disk drive takes 10 milliseconds (averaging read and write), it is theoretically possible to perform 100 random seeks per second (1/.001 sec), excluding such things as overhead associated with the I/O bus or latencies associated with processing the I/O. Queuing begins as you get closer to the theoretical limit of the disk drive. As queuing occurs, the I/O latency increases and database performance begins to suffer.

Note

You can increase the system's random I/O capacity by spreading the data across multiple files or install the data files on a RAID array.

Data files are mostly accessed by random I/Os.

Sequential I/Os Because there is no seek operation involved in sequential I/O, a disk drive can handle several hundred sequential I/Os per second without seeing increasing latencies. Therefore, using sequential I/O whenever possible can greatly improve the performance of the disk drives. Microsoft SQL Server and Oracle keep a log of the transactions; this log is primarily sequential to take advantage of sequential I/Os.

Important

In order to achieve maximum performance, the data file and log file must not be on the same physical drive.


170 Disk Usage, page 49



Monitoring the Databases, page 44



Disk Usage Disk usage should remain under 85% of the maximum disk capacity, and the partition should not be compressed.

Sizing the Files With SQL Server 2000, a database is created by default with a data file of 1MB and a log file of 1MB.

Note

A database can be associated to more than one data file and more than one log file.

Both files are set to grow by 10% increments until space is no longer available on the drive. These defaults, however, are not adequate for monitoring or for a production system. When the data or log files are growing, the process may consume a very large amount of server resources and slow down the interactive users or perturb the monitoring performed on the system. As a result, we recommend that you set the size of the files to avoid automatic growth.

Note

Set the size to the maximum anticipated size of the file. Set the growth increment to size of the available space or 85% of the capacity of the drive.

If automatic file growth occurs, re-evaluate the situation and try to set more accurate sizes or plan to add more capacity for your database.

The following table proposes some reasonable orders of magnitude for small pilots based on testing conducted by Intergraph PPM. The most critical files for performances and monitoring are isolated on their own physical drives (the G, H, I, and J drives) while the less critical files share two drives (the E and F drives). The operating system, SQL server and paging files are installed on their own drives.

File Initial Size Growth Increment Drive Model data 10 GB 1 GB G or Raid 5/Raid 1 Model log 1 GB 500 MB H or Raid 1 Catalog data 1 GB 500 MB I or Raid 5/Raid 1 Catalog log 500 MB 100 MB J or Raid 1 Catalog schema data Default Default E Catalog schema log Default Default F Site data 50 MB 10 MB E Site log 50 MB 10 MB F



Site schema Default Default E Site schema log Default Default F Report data Default Default E Report log N/A N/A F Temp DB data 50 MB 50 MB E Temp DB log 50 MB 50 MB F

Notes

The size of your Model database log file depends on your backup strategy. For more information about backing up your SmartPlant 3D data, see the Project Management User's Guide, available from Help > Printable Guides.

Tempdb size is reset to the default every time the server is re-started.


170 Assign System Administrator Privileges, page 30 Monitoring the Databases, page 44



Loading Prerequisite Software on the Database Server

The following prerequisite software is required in order to install and use the software on a database server:

Microsoft SQL Server 2000 Service Pack 3a (or higher): Database Components (SQL Server only)

Microsoft .NET Framework 1.1 and the latest service pack, and .NET Framework 2.0

Adobe Acrobat Reader 6.0 or higher

Related Topics Loading Prerequisite Software on the Client, page 67

Install SQL Server 2000 Service Pack 3a: Database Components

If you have previously installed SQL Server 2000 Service Pack 3 on the database server, you do not need to apply Service Pack 3a (SP3a). SP3a is only for SQL Server users who have not installed any versions of SP3.

To identify which version of SQL Server 2000 database components you have installed, do one of the following:

On a Windows 2000 Server computer, click Start > Programs > Microsoft SQL Server > Query Analyzer. In the in the Query window, type SELECT @@Version, and then click Query > Execute. SQL Server 2000 Service Pack 3 and Service Pack 3a display version number 8.00.760.

On a Windows Server 2003 computer, click Start > All Programs > Microsoft SQL Server > Query Analyzer. In the in the Query window, type SELECT @@Version, and then click Query > Execute. SQL Server 2000 Service Pack 3 and Service Pack 3a display version number 8.00.760.



Install SQL Server 2000 SP3a You can download and install SP3a (or higher) directly from the Service Packs for SQL Server web site at http://www.microsoft.com/sql/downloads/servicepacks.asp. During installation of the database components, setup displays various dialog boxes that prompt you for information. We recommend the following:

On the Authentication Mode dialog box, select The Windows information I use to log on to my computer with (Windows Authentication).

On the SA Password Warning dialog box, select the response most appropriate for your organization. The dialog box appears only if Setup detects a blank password for the sa login. The SA account is what the database administrator uses to manage SQL Server. Although you can continue your installation with a blank password for the sa login by explicitly choosing to ignore the recommendation and continue Setup, a blank password poses a security risk. For more information about SA passwords, refer to the documentation delivered with the Microsoft SQL Server 2000 software.

On the Backward Compatibility Checklist dialog box, select Upgrade Microsoft Search and apply SQL Server 2000 SP3 (required).

Tip

Cross-database ownership chaining is turned off by default. After installation, you can enable cross-database ownership chaining for individual databases.

On the Error Reporting dialog box, make your selection as required the policy of your company.

Related Topics Loading Prerequisite Software on the Database Server, page 51



Install Microsoft .NET Framework If you are using Microsoft Windows Server 2003 with Service Pack 1 (SP1), you can skip this procedure. Microsoft .NET Framework 1.1 and SP1 are delivered during Windows Server 2003

Documents

Smart Plant 3 d Installation Guide 409