Spe Install Guide

SmartPlant Explorer Installation Guide

Version 2009 HF2 (06.00.00) August 2010 DSPE2-PE-200001G

Copyright Copyright © 1997-2010 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 from Intergraph Corporation.

U.S. Government Restricted Rights Legend Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at private expense and is "restricted computer software" submitted submitted with restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations Regulations ("FAR") and its successors, successors, and is unpublished and all all rights are reserved under the the copyright laws laws of the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3. Unpublished - rights reserved under the copyright laws of the United States. Intergraph Corporation P.O. Box 240000 Huntsville, AL 35813 Street address: 170 Graphics Drive, Madison, AL 35758

Terms of Use Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless the licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives licensee permission to print a reasonable number of copies of the documentation as defined in the applicable license agreement and delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for resale or redistribution.

Warranties and Liabilities All warranties warranties given by Intergraph Corporation about about equipment or software are set forth in the EULA provided with the software software or applicable license for the software product signed by Intergraph Corporation, 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. Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data. Users should verify for themselves that the data is accurate and suitable for their project work.

Trademarks Intergraph, the Intergraph logo, PDS, SmartPlant, SmartMarine, FrameWorks, I-Convert, I-Export, I-Sketch, IntelliShip, INtools, ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, SupportManager, and SupportModeler are trademarks or registered trademarks of Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered trademarks of Microsoft Corporation. MicroStation is a registered trademark of Bentley Systems, Inc. Other brands and product names are trademarks of their respective owners.

Copyright Copyright © 1997-2010 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 from Intergraph Corporation.

U.S. Government Restricted Rights Legend Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at private expense and is "restricted computer software" submitted submitted with restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations Regulations ("FAR") and its successors, successors, and is unpublished and all all rights are reserved under the the copyright laws laws of the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3. Unpublished - rights reserved under the copyright laws of the United States. Intergraph Corporation P.O. Box 240000 Huntsville, AL 35813 Street address: 170 Graphics Drive, Madison, AL 35758

Terms of Use Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless the licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives licensee permission to print a reasonable number of copies of the documentation as defined in the applicable license agreement and delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for resale or redistribution.

Warranties and Liabilities All warranties warranties given by Intergraph Corporation about about equipment or software are set forth in the EULA provided with the software software or applicable license for the software product signed by Intergraph Corporation, 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. Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data. Users should verify for themselves that the data is accurate and suitable for their project work.

Trademarks Intergraph, the Intergraph logo, PDS, SmartPlant, SmartMarine, FrameWorks, I-Convert, I-Export, I-Sketch, IntelliShip, INtools, ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, SupportManager, and SupportModeler are trademarks or registered trademarks of Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered trademarks of Microsoft Corporation. MicroStation is a registered trademark of Bentley Systems, Inc. Other brands and product names are trademarks of their respective owners.

Contents Internationalization ...................................................................................................................................... 5 Welcome to SmartPlant Explorer ............................................................................................................... 7 New Features in SmartPlant Explorer .................................................................................................... 7 Version 2009 .................................................................................................................................... 7 Hardware and Software Recommendations ........................................................................................... 8 Software Version Compatibility ............................................................................................................... 8 SmartPlant Explorer Hardware and Software Recommendations .............. ........................ ................... .................. .................. ......... 9 Basic Installation and Configuration...................................................................................................... 10 Impersonated Imperson ated Users ................. ................. ................. ................. ................................. ................ ................. .................... ..... 11 Upgrading from a Previous Version ...................................................................................................... 11 Remove SmartPlant Explorer ............................................................................................................... 12 Installing the SmartPlant Explorer Web Server .................................................................................... 12 Microsoft Internet Explorer Installation ........................................................................................... 13 Internet Information Service Installation ......................................................................................... 13 Install SmartPlant Explorer Web Server ......................................................................................... 13 Install Application Modules ............................................................................................................. 16 Configuration Activities ................................................................................................................... 18 PDS 3D Module .......................................................................................................................................... 21 Configuring the PDS 3D Module ........................................................................................................... 21 Creating DSNs.................................. ................ .................. ................. ................. ................. ................. ................. ......... 21 Adding a Project .................. ........................... .................. .................. ................... ................... .................. .................. ................... ................... .................. .................. ............... ...... 23 SmartPlant Instrumentation Module ........................................................................................................ 25 Configuring the SmartPlant Instrumentation Module ............................................................................ Setup for Oracle Networking Components ..................................................................................... Adding a Site using using an Oracle Database Database ............ ..................... .................. ................... ................... .................. ................... ................... .................. ........... Adding a Site using a Microsoft SQL SQL Server Database Database ............. ....................... .................... ................... ................... ................... ............. .... Adding a Domain .................. ........................... ................... ................... .................. .................. .................. ................... ................... .................. .................. ................. .............. ...... Define the Location of SmartPlant Instrumentation Server ................... ............................ ................... ................... ................... ............. ... Adding a Plant .................. ........................... .................. .................. ................... ................... .................. .................. ................... ................... .................. ................. ................. ...........

25 25 26 26 27 27 28

PDS PID Module ......................................................................................................................................... 29 Adding a Project................... ............................ .................. .................. ................... ................... .................. .................. ................... ................... ................. ................. .................. ............. .... 29 SmartPlant PID Module ............................................................................................................................. 31 Configuring Microsoft Excel Distributed COM Configuration Properties ............................ ..................................... .................. ......... 31 Installing Oracle Networking Components ............................................................................................ 32 Adding the SmartPlant SmartPlant PID Module Module to the Web Server Server .................. ........................... .................. .................. ................... ................... ................. ........ 32 Configuring the SmartPlant PID Module ............................................................................................... 32 SmartPlant Electrical Module ................................................................................................................... 35 Configuring Microsoft Excel Distributed COM Configuration Properties ............................ ..................................... .................. ......... 35 Installing Oracle Networking Components ............................................................................................ 36


3

Contents Adding the SmartPlant SmartPlant Electrical Electrical Module to the Web Server ................... ............................. ................... .................. ................... ................ ...... 36 Configuring the SmartPlant Electrical Module ...................................................................................... 36 Administrating SmartPlant Explorer ....................................................................................................... 39 Access Control ................... ............................ .................. ................... ................... .................. ................... ................... .................. ................... ................... .................. .................. ............. .... Add a Role .................. ........................... ................... ................... .................. .................. ................... ................... .................. .................. .................. ................. ................. ................ ....... Add a User.................. ........................... .................. .................. ................... ................... .................. .................. ................... ................... .................. ................. ................. ................ ....... System Security .................................................................................................................................... Basic Authentication ....................................................................................................................... Integrated Windows Authentication ................................................................................................ Certificate Authentication................................................................................................................ Switching Authentication Methods ................................................................................................. Changing Session Timeout ............................................................................................................ Important Files to Back Up .................................................................................................................... Changing Changin g Settings ................................. ................ ................. ................................. ................ ................. ................. ................. ..................... ........ Index

4

39 40 41 41 41 42 42 43 43 44 44

........................................................................................................................................................... 45


S

ECTION

1

Internationalization Supporting internationalization in a homogeneous environment is one of the enhancements available in SmartPlant Enterprise. A homogeneous environment uses elements from only a single locale. For example, a German customer running on a German operating system using only German characters and German cultural conventions is a fully supported homogeneous environment configuration.

Homogeneous Environments When starting a new project, use extra care during installation and configuration to ensure the proper creation and maintenance of homogeneous environments: 







All the computers (servers and clients) within an integrated SmartPlant Enterprise implementation must have the same regional settings, and no one should change the regional settings after the project has started. Do not cross the decimal locale boundary. This is the most common cause of numeric data corruption and calculation errors. Having users with different regional settings (like with a period versus a comma for the decimal point) causes the software to interpret values unpredictably. For example, a pipe run with a pressure of 35.3 psi can be read by the software as 353 psi to the user with different regional settings. A cable length defined as 39 ft 11,21 inches has been interpreted as 121718910971323 meters when published to an XML file. These incorrect interpretations may be used in internal software calculations and can be impossible to backtrack or correct. Do not change the decimal point character to try to solve an issue. Doing so will only corrupt values in the database or in text files. Do not cross the character-set locale boundary. For example, the character set boundary between Western (Latin-based) and Eastern Europe (Cyrillic-based), or between Eastern Europe and Japan. Create Microsoft SQL Server databases with locale-specific collation settings and ensure that all databases have the same setting.

Heterogeneous Environments In contrast, a heterogeneous environment using elements from different, or even multiple locales, is not supported. Many customers are currently operating in unsupported heterogeneous environments and are often not aware of that fact. Examples of heterogeneous environments:  

  

Entering or viewing Japanese data on an US/English operating system Using German Regional Settings (where the decimal point is a comma) on a US/English operating system Using databases with different character encodings such as CL8MSWIN1251 or JA16SJIS Using multiple languages in a project, especially when crossing language-group boundaries Using an English server with different local language clients

International / Bi-lingual Projects International bi-lingual projects are possible; however, great care must be used when configuring these environments. Limitations exist and must be properly understood:


5

Internationalization 







Oracle and MS SQL Server databases can reside on any language operating system, as long as the databases have been created and configured with proper Unicode and collation settings. All Microsoft operating systems (Japanese, Russian, German, and so forth) can enter English characters. The reverse, however, is not true in most cases. Keyboard-locale can be changed as long as a character-set and code- page boundary is not crossed. For example, English, German, French, and Spanish characters can all be used in the same project because the same Windows code-page (1252) is used. However, Russian characters (code-page 1251) cannot be used in a US/English environment. You must decide which language operating system will be the master for bi-lingual projects.

The following is an example of a Russian-based project: Companies in the United States and the United Kingdom are working a project with a Russian company and the deliverables (drawings, reports, and so forth) must ultimately be provided in Russian. The companies in the U.S. and the U.K. are working the project using the "master" Russian operating systems (possibly using virtual Russian operating systems running on VMware Workstation). The U.S. and U.K. companies can install and use English Microsoft Office products on the Russian operating system because Office products are globally enabled. If a Russian interface exists for the SmartPlant Enterprise application, then Russian users can use the Russian interface while the English-speaking users would continue to use the US/English interface. English-speaking engineers can enter English characters. Russian-speaking engineers can enter Russian characters. However, because the Russian locale uses different decimal and character-set locales, everyone (English and Russian engineers) must use the Russian decimal symbol which is a comma. For customization purposes, databases can be modified to accommodate new Russian-specific requirements (fields, properties, and so forth.) Using filters, display sets, and other software features, bi-lingual projects can be further customized. Graphic data, reports, and so forth can be created in either or both languages. Do not change regional settings to reflect a U.S. environment in order to resolve problems in a non-US/English homogeneous configuration. Doing this creates a heterogeneous configuration that will cause other possibly hidden problems that cannot be corrected. Everyone working on a project must use the same regional settings and character set throughout the life of the project.

Questions and Assist ance Please contact your support representative for assistance.

6


S

ECTION

2

Welcome to SmartPlant Explorer ®

SmartPlant Explorer is your data access solution for viewing, querying, and reporting on plant data throughout the plant life cycle. SmartPlant Explorer’s quick point-and-click display, navigation, and reporting functions reduce the time spent searching for plant data to the click of a button. With SmartPlant Explorer, you can find schematics, drawings, and engineering, vendor, and maintenance data for a particular pump, or locate all the valves of a certain type throughout your facility, without ever leaving your desk. With a point-and-click interface, SmartPlant Explorer is as easy to use as any Web browser. SmartPlant Explorer uses the project database as its information source and also takes advantage of the Microsoft Windows operating system technology and functionality, which provides ease of use, increased performance, and unsurpassed security. ®

SmartPlant Explorer provides a Web-enabled window into Plant Design System (PDS ), SmartPlant P&ID, SmartPlant Instrumentation, and SmartPlant Electrical projects, as well as other plant data. In short, SmartPlant Explorer creates a Web site where you can easily view and explore your plant design data, including instrumentation, piping and instrumentation diagrams (P&IDs), 3D models, and associated engineering data. Most importantly, anyone in the enterprise, and even beyond, can easily locate information by using SmartPlant Explorer. SmartPlant Explorer also helps lower project expenses by eliminating costly errors and rework due to erroneous or outdated information. Because SmartPlant Explorer accesses data directly from the data source, it eliminates the need to maintain a duplicate set of data. This direct access results in increased accuracy, quick turnaround and delivery of revised data, improved communications, and lowered project costs. Also, accessing data through the Web eliminates the need for dated paper documents, which often must be requested from a document control organization or from engineering personnel.

New Features in SmartPlant Explorer The following new features have been added:

Version 2009 

The SmartPlant Instrumentation module now displays Enhanced SmartLoop drawings as they were generated by the software, using the specific preferences and settings from the domain that the drawing was generated in, based on the user configuration in SmartPlant Explorer. 





You must have installed SmartPlant Instrumentation 2007 SP6 HF 13 or higher or SmartPlant Instrumentation 2009 SP1, for this feature to work. In the Settings.js file, change the var INtools_DomainSpecificEslPreferences =false; to true. This file can be found in the home folder where you installed SmartPlant Explorer in the Web Server folder.

In the SmartPlant P&ID module when opening a report for one of the following categories;

Equipment

Mechanical



Vessel



Heat Transfer






7

Welcome to SmartPlant Explorer When the item you select appears in more than one drawing, you can now select a specific drawing to be displayed instead of the default drawing. For example, if you choose a vessel that appears in drawing 1 and drawing 2, you can now select which of the drawings to display. 

SmartPlant Explorer 2009 supports Windows Vista Business Client 32-bit mode with Users Access Control (UAC) on. When installing Active X controls UAC must be turned off. Once installed you can restart UAC on your machine.

 





The SmartPlant P&ID module now supports the display and control of Typicals. The SmartPlant Electrical module now allows you to preview registered documents prior to printing. It is now possible for users registered in one domain, to access data and reports in another domain and save them to Excel. SmartPlant Explorer now gives you the option to generate your reports in the current browser window or in a new browser window. For this functionality to work you must disable you browsers pop-up blocker.



It is now possible when working in SmartPlant Explorer to connect to different SmartPlant Instrumentation databases from the same SmartPlant Explorer server.

Hardware and Software Recommendations This section contains important administrator information. Please read the entire section before you begin the installation.

Software Version Compatibility SmartPlant Explorer Version 2009 supports: 





SmartPlant Instrumentation Versions; 

2007 service pack 6.



2009 and its service packs.

SmartPlant Electrical Version; 




2009 and its service packs.

SmartPlant P&ID Versions; 





03.08.

SmartPlant Review Version;



8

07.01.

SmartPlant Markup Version; 



07.00.0.23.

PDS 3D Version 



2009.

PDS PID Version; 




06.02.00.11.


Welcome to SmartPlant Explorer

SmartPlant Explorer Hardware and Software Recommendations The following are the recommended hardware and software recommendations for SmartPlant Explorer's Web Server and Modules applications, which must be installed on the same computer. For multiple concurrent users (up to 25) a 2 or 4 core processor is recommended.

Hardware Recommendations    

Pentium IV with 3 GHz processor or Pentium dual core with 2 GHz processor or higher 2 GB RAM or higher CD-ROM drive access, either locally or through a network connection Windows supported printer access, either locally or through a network connection For multiple concurrent users (up to 25) a 2 or 4 core processor is recommended with 4 GB RAM and with 3GB switch enabled.

Supported Operating Systems   

Microsoft Windows XP Professional Service Pack 3 (32-bit) Microsoft Vista Business Client Service Pack 2 (32-bit) Microsoft Windows 7 



On a machine working with the Vista operating system and an Oracle database, after installing the Oracle client you must register the igrORASPConnect412.dll using the registeroracle.bat file. Both the .dll and the .bat file can be found in the SmartPlant Explorer > RAD folder on the drive where you installed SmartPlant Explorer. On a machine working with the Vista operating system, IIS 6.0 and IIS 7.0 must both be installed and working for SmartPlant Explorer to work.

Support ed Database  

Microsoft SQL Server 2005 Service Pack 2 Oracle Database 10g Release 2 (10.2.0.4) The client database software must be of the same version as the server database

software.

Recommended Disk Space  

At least 160 MB of free hard drive space for the web server. At least 60 MB of free hard drive space for the modules.

Software Prerequisites 







Adobe Reader 8.0 or later compatible version (required for viewing the Software License Agreement and Printable Guides). The latest version is downloadable from the Adobe Web site. Microsoft Internet Explorer 7.0 or Microsoft Internet Explorer 8.0 (required for viewing the Online documentation delivered with the software) Microsoft Office 2003 or 2007 (Microsoft Excel is required for working with report templates and for viewing the Installation Checklist and various other files). Microsoft XML Core Services (MSXML) 6.0 Service Pack 1


9

Welcome to SmartPlant Explorer  





Microsoft .NET Framework 3.5 Microsoft Data Access Components (MDAC) 2.8 Service Pack 1 or later service pack of MDAC 2.8 if installed with the operating system (MDAC 2.8 is delivered as part of Microsoft Windows XP Service Pack 3). For more information, see Install MDAC Driver (SPI_Install_MDAC_1h.htm). Microsoft Management Console (MMC) 3.0.(MMC 3.0 is included with Microsoft Windows Server 2003 R2 and Microsoft Windows Vista, or can be downloaded from Microsoft Help and Support.) Microsoft Visual C++ 2008 SP1 Redistributable Package (runtime components), available from the Microsoft Download Center.

Windows 7 users must select the Allow IIS intrinsic properties check box on the Advanced tab of each modules component propreties. The component properties can be found under Control Panel > Administrative Tools > Component Services, and then in the Component Services window by navigating to Com+ Applications > SmartPlant Web Server > Components.

Basic Installation and Configuration SmartPlant Explorer has two main parts: the SmartPlant Explorer Web Server and one or more SmartPlant Explorer application module servers (PDS 3D Module, SmartPlant Instrumentation Module, PDS PID Module, SmartPlant PID Module, and SmartPlant Electrical Module). The SmartPlant Explorer Web Server provides the central services for the SmartPlant Explorer application modules. These services include the roles, components, a nd basic actions required to interact with the individual SmartPlant Explorer application module servers. Users connect to the SmartPlant Explorer Web Server with Microsoft’s Internet Explorer Web browser. The Web browser sends a http request to view application data to the SmartPlant Explorer Web Server. The SmartPlant Explorer Web Server then forwards this request to the corresponding SmartPlant Explorer application module server. The SmartPlant Explorer application module server retrieves the requested information from the application-specific database and passes that information back to the SmartPlant Explorer Web Server. The SmartPlant Explorer Web Server then formats this information into an HTML page and displays this page to the user. You must install the Web Server and the application module servers on the same computer.

10



Impersonated Users Instead of using each individual user's login to communicate with the SmartPlant Explorer application module servers, the SmartPlant Explorer Web Server impersonates a single predefined Windows user. You need to decide who this user is and create the user in Windows before you install the SmartPlant Explorer Web Server. The impersonated user must have access to any shares that SmartPlant Explorer might ever need to access. For example, if you have associated documents on a share, this user must have access to that share. We highly recommend that you think about what user you want to use and create any needed users before you install the SmartPlant Explorer Web Server. This user needs to be a Windows domain user and an administrator on the computer on which you load the SmartPlant Explorer Web Server. The SmartPlant Explorer application module servers (the servers that communicate with the application database) will need to know who this Windows user is. You will be prompted for this user during the installation of each application. In addition, the SmartPlant Explorer application module servers also need a second Windows user account that has administrator access to the server on which they are installed. This second Windows user can be the same as the first user, but must have administrator access to the ap plication module server. You can change either user name or user password on the appropriate server after installation using Microsoft Component Services on Windows.

Upgrading from a Previous Version 

You must remove any previous versions of SmartPlant Explorer including any installed modules before installing Version 2009.

When removing a previous version, you are prompted whether or not you want to keep your actions and custom reports for use in version 2009. This functionality does not work for the SmartPlant Electrical module when upgrading from version 2007 SP6 You must, before upgrading, save the spespel.mdb file manually and then add it to the saved data folder after upgrade. 



On upgrading to Version 2009, the software automatically updates ActiveX controls and removes all previously-installed unused ActiveX controls. On an Vista operating system the UAC functionality must be set to off to install the Active X controls. After the installation of the Active X controls you can restart the UAC. After upgrading to Version 2009, or after installing a service pack you must restart your computer.


11


Remove SmartPlant Explorer 1.

On the server where SmartPlant Explorer is installed, open the Control Panel and activate Add or Remove Programs.

2. Select Intergraph SmartPlant Explorer from the list. 3. Select Intergraph SmartPlant Web Server . 4. Click Change/Remove. 5. Click Yes to confirm that you want to remove the Intergraph SmartPlant Web Server. 6.

When prompted whether or not you want to keep actions, roles, user access assignments, and custom reports, click Yes to keep the previous version’s information for use when installing the latest version. Click No to delete the previous version’s information and install the default settings for the latest version.





If any application modules were loaded in the previous version on a computer other than the Web Server computer, you will not be able to use the information for those modules in the latest version. This functionality does not work for the SmartPlant Electrical module when upgrading from version 2007 SP6 You must, before upgrading, save the spespel.mdb file manually and then add it to the saved data folder after upgrade.

7. Click Next to remove SmartPlant Explorer together with any modules installed on the same computer.

Installing the SmartPlant Explorer Web Server The SmartPlant Explorer Web Server requires that Windows 2003 Server, Microsoft Internet Explorer, and Microsoft Internet Information Service be installed on the server before installing the SmartPlant Explorer Web Server.

12



Microsoft Internet Explorer Installation When you insert the SmartPlant Explorer CD-ROM into the drive, setup checks for Microsoft Internet Explorer 7.0 or higher on your server. If Internet Explorer 7.0 or higher is not installed, you are asked if you want to install Internet Explorer now. Internet Explorer is available on the SmartPlant Explorer CD-ROM or from the Microsoft web site, http://www.microsoft.com (http://www.microsoft.com). We recommend that you use the Typical installation option when installing Internet Explorer.

Internet Information Service Installation SmartPlant Explorer uses Microsoft’s Internet Information Service (IIS) to provide the Internet services. You must install IIS on your SmartPlant Explorer Web Server. 1.

Open the Control Panel and activate Add or Remove Programs.

2. Click Add/Remove Windows Components. 3. Select Internet Information Services (IIS). Both IIS 6.0 and IIS7.0 must be selected for Windows Vista operating systems. 4. Click Next. 5. Click Finish. If you are running IIS 6.0 on a 64-bit server then you must configure IIS 6.0 to run 32-bit applications using the Windows 32–on–Windows–64 (WOW64) compatibility layer. For more information on running 32-bit applications on 64-bit Windows see the Microsoft TechNet article Running 32-bit Applications on 64-bit Windows (IIS 6.0) (http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/13f991a5-45eb496c-8618-2179c3753bb0.mspx?mfr=true)

Install SmartPlant Explorer Web Server With the prerequisite software installed, you are ready to install the SmartPlant Explorer Web Server. During installation, you are prompted for a Windows user login that the software will use to communicate with the SmartPlant Explorer application module servers as well as other resources located on the computer where the SmartPlant Explorer Web Server is installed. In addition, this user must have access to any shares that SmartPlant Explorer might ever need to access. For example, if you have associated documents on a share, this user must have access to the share. We highly recommend that you think about what user you want to use and create any needed user logins before you install the SmartPlant Explorer Web Server. This user needs to be a Windows domain user and an administrator on the computer on which you load the software. You are prompted for this user name when you install the SmartPlant Explorer application modules. You can change the login after installation if needed using Component Services. For more information, see Impersonated Users (on page 11). 1.

Open the Control Panel and activate System.

2.

Select the Advanced tab.

3. Click Environment Variables. 4.

Verify that the System Variables (not User Variables) TEMP and TMP are set to a valid directory.

5.

Insert the SmartPlant Explorer CD into the drive.

6. Click SmartPlant Explorer Installation.


13

Welcome to SmartPlant Explorer 7.

On the Welcome page, click Next.

8.

Select a destination folder for the SmartPlant Explorer Web Server files. We recommend the default location of c:\Program Files\SmartPlant\Explorer.

9.

On the Select Features page, select Web Server .

If you plan to load the PDS PID module and to view drawings created by PDS P&ID, you also need to select the Drawing Converter from the features list. The drawing converter is not needed for the PDS 3D Module, SmartPlant Instrumentation Module, SmartPlant PID Module, or SmartPlant Electrical Module. 10. Click Next. 11. Type your name, company name, and the serial number in the appropriate fields, and then click Next. 12. Select your country, and then click Display. You cannot install the Web server if you do not read and agree with the software license agreement. 13. Read the software license agreement, and then click Yes. 14. If you are installing on a computer running the Windows 2003 Server operating system, you may be prompted to allow Active Server Pages in IIS. SmartPlant Explorer will not run unless the Active Server Pages are allowed. Click Yes to permit setup to automatically set Active Server Pages to Allow in ISS. If you click No, setup will stop and you will need to set the Active Server Pages in IIS to Allow manually. For more information, see Configure Windows 2003 Servers (on page 18). 15. Wait while files are installed.

14


Welcome to SmartPlant Explorer 16. Type the impersonated user name. This user must have administrative access on the server. We recommend that you do not use a local user account because this user name accesses information on other computers on which a local user account is not valid. You can change the user name or user n ame password later in the Component Services if needed.

Selecting the check box Specify this user name for all SmartPlant Explorer application modules during this installation will use the user name and password that you entered for all the modules that you selected for installation on the Select Features page. If you clear the check box, you will be prompted to enter a separate name and password for each module.


15

Welcome to SmartPlant Explorer 17. Select Integrated Windows Authentication or Basic Authentication. For details, see System Security (on page 41).

18. Click Finish. 19. If you install the SmartPlant Explorer Web Server on a NTFS drive, you must change the security of the data subfolder to grant Full Control access to the Authenticated Users account.

Install Application Modules SmartPlant Explorer application modules should be installed on the same computer as the SmartPlant Explorer Web Server. You can install modules at the same time as the web server installation, or you can install modules on the same computer later. Windows 7 users must select the Allow IIS intrinsic properties check box on the Advanced tab of each modules component propreties. The component properties can be found under Control Panel > Administrative Tools > Component Services, and then in the Component Services window by navigating to Com+ Applications > SmartPlant Web Server > Components. 1.

Insert the SmartPlant Explorer CD into the drive.

2. Select SmartPlant Explorer Installations. 3.

On the Welcome page, click Next.

4.

Select the installation folder where you installed the SmartPlant Explorer Web Server. All modules that you subsequently select will be installed in this folder. If you want to install other modules in a different folder, you will need to run this installation procedure separately for those modules.

16



On the Select Features page, select the desired modules.

If you plan to load the PDS PID module and to view drawings created by PDS P&ID, you also need to select the Drawing Converter from the features list. The drawing converter is not needed for the PDS 3D Module, SmartPlant Instrumentation Module, SmartPlant PID Module, or SmartPlant Electrical Module. 6. Click Next. 7.

Type an administrative logon that the module is to use on this computer.

8.

Type the impersonated user name that the SmartPlant Explorer Web Server will be using to communicate with the module. You specified this user name when you installed the SmartPlant Explorer Web Server. For more information, see Impersonated Users (on page 11). If you do not specify the impersonated user name during the module installation, you must do the following after completing the installation:

9.

On the computer where the module is installed, start Windows Explorer.

10. Navigate to the folder where the module is installed. The default location is: ...\Program Files\SmartPlant\Explorer\SmartPlant Module. 11. Right-click on the folder, and then click Properties. 12. Click the Sharing tab. 13. Click Permissions. 14. Add the Windows user, with Full Control permission, that the SmartPlant Explorer Web Server is currently impersonating. 15. Navigate to ...\Common Files\Intergraph Shared\SmartPlant. 16. Right-click on the folder, and then click Properties. 17. Click the Sharing tab.


17

Welcome to SmartPlant Explorer 18. Click Permissions. 19. Add the Windows user, with Full Control permission, that the SmartPlant Explorer Web Server is currently impersonating.

Define Reference File Search Path If the PDS P&ID design files that you want to view in SmartPlant Explorer have reference files attached, you must define the search path for the reference files. Reference files are commonly used for drawing borders. If you did not install the Drawing Converter, you can skip ahead to Define Users and Roles (on page 18). 1.

In Windows Explorer, go to the folder where you installed the Drawing Converter.

2. Double-click SetMstnRefPath.exe. 3.

Type the full UNC paths to all folders that contain reference files. You must include paths for each PDS P&ID project that you plan to explore. Separate paths with semicolons.

4. Click OK.

Configuration Activities The following section contains information on various configuration activities that you must perform in order that SmartPlant Explorer will function correctly.

Config ure Windo ws 2003 Servers Because of increased security measures, additional configuration is required for SmartPlant Explorer to run when it is installed on a Windows 2003 Server computer. In Internet Information Services (IIS) Manager, Active Server Pages must be allowed to run. During Web Server setup, you are prompted whether or not to permit setup to change this option automatically. If you selected No, then you must do the following before you can install the SmartPlant Explorer Web Server: 1.

On the Windows 2003 Server, click Start > Administrative Tools > Internet Information Services (IIS) Manager .

2.

Expand the local computer node in the tree.

3.

Click the Web Service Extensions folder in the tree.

4. Select Active Server Pages in the right-hand view. 5. Click Allow.

D e f in e U s e r s a n d R o l e s After installing the SmartPlant Explorer Web Server, you need to define which users have access to SmartPlant Explorer. Use Windows Component Services to define users and roles in the SmartPlant Web Server component. SmartPlant Explorer defines three roles by default: Administrator, Users, and Viewers. You can add Windows users or groups to these roles or create your own roles and add users to them. Users log on to the SmartPlant Explorer Web Server using their regular Windows user name and password. SmartPlant Explorer checks the defined roles and users in Component Services to verify that they have been granted access. If they have access, SmartPlant Explorer starts. See Access Control (on page 39) for more information on users and roles. Novell users must be members of a Windows user group in order to access SmartPlant P&ID options.

18



S t a r t S m a r t P l an t E x p l o r e r 1.

Start Microsoft Internet Explorer.

2.

Type http:///spex/ in the Address box where is the name of the SmartPlant Explorer Web Server. An example is, http://smartplant/spex/.

3.

Type your Windows user name and password, if prompted. You may need to include your domain name in your username. An example is: intergraph\rljoe





You need to include the domain if the SmartPlant Explorer Web Server is not on your local area network. For example, http://smartplant.ingr.com/spex/. The first time that you connect to the SmartPlant Explorer Web Server, you are prompted to load two ActiveX controls: SPESafeHelper.CAB from Intergraph Corporation and ActiveBar ActiveX from Data Dynamics, LTD. You must load both controls for SmartPlant Explorer to run.

Your Internet Explorer security settings may interfere with SmartPlant Explorer. If you experience problems, verify the security settings are set as a minimum: 

  

 

You must allow per-session cookies. The Download signed ActiveX controls option must be set to Enabled or Prompt. The Download unsigned ActiveX controls option can be set to Disabled. The Initialize and script ActiveX controls not marked as safe option can be set to Disabled. The Run ActiveX controls and plug-ins option must be set to Enabled or Prompt. The Script ActiveX controls marked safe for scripting option must be set to Enabled or Prompt.

You can verify these setting by opening the Internet Options dialog box, selecting the Security tab, selecting either Internet or Local intranet depending on how you access SmartPlant Explorer, and then click Custom Level.

A d d a n A p p l i c at i o n 1.

Start SmartPlant Explorer in Internet Explorer by typing http:///spex/ where is the name of the web server. You must allow session cookies. You can verify this setting by opening the Internet Options dialog box, selecting the Privacy tab, and then clicking Advanced.

2.

Log on using the Windows user name and password that you entered during setup. If you are not sure of this user name, you can look on the Identity tab of the Properties dialog box for the SmartPlant Web Server package in Component Services for Windows. You may need to add the domain to your username to successfully log in. An example is: intergraph/jhdoe. If you do not want to use this logon, you can add yourself to the Administrator Role in the SmartPlant Web Server package using Component Services on Windows, and then log on using your Windows account. For more information on adding users, see Access Control (on page 39).

3. Right-click SmartPlant Explorer Web Server

.

4.

On the shortcut menu, click Add Application.

5.

Type the server name where the SmartPlant Explorer application module that you want to add is installed.

6. Click Search to display which modules are installed on that server.


19


From the list, select the module to load.

8. Click Add Selected Module. 9.

On the Installation Done message box, click OK.

10. If you have saved application data, you are asked if you want to reuse the data. Click Yes to reuse the data. Click No to install default application data. 11. If you are using the saved data, your published sites must be updated. Choose whether or not to let SmartPlant Explorer update the sites for you if prompted. 

  

If you choose not to reuse the application data, the saved data is deleted from the server and the default data is installed. You must add an application before you can view any projects created with that application. You must have administrator privileges to add an application. The application module that you are adding must have already been installed.

R em o v e a n A p p l i c a t i o n 1.

Right-click one of the following application icons:



PDS 3D



SmartPlant Instrumentation



PDS PID



SmartPlant PID



SmartPlant Electrical

1.

. .

. . .

On the shortcut menu, click Remove Application.

2. Select Save information. 3. Click Yes to confirm that you want to remove the application. 4.







20

If prompted, click Yes to save data from the application that you are removing or No to remove the application without saving data. You can save custom actions, reports, favorites, and published application data when you remove the application. SmartPlant Explorer can then reuse this information when you reinstall this application. If you are not sure, we recommend that you save the information. The software does not delete or affect your production application data in any way. You are only removing the ability to view that data from the SmartPlant Explorer Web Server. You must have administrator privileges to remove an application.


S

ECTION

3

PDS 3D Module The PDS 3D Module provides fast and easy access to your PDS 3D models and plant design data. It allows SmartPlant Explorer users to quickly locate, query, and display 3D models created with PDS. For example, you can query the PDS 3D model database for models that contain a specific equipment tag number. SmartPlant Explorer then displays a tabular list of models that meet the search criteria. When you select a model to view, the model automatically launches and displays the highlighted item in the 3D model.

Configuring the PDS 3D Module The required steps for configuring PDS 3D Module are: 





Creating the Data Source Name to connect to the database. For more information, see Creating DSNs (on page 21). Adding the PDS 3D Module to the SmartPlant Explorer Web Server. For more information, see Add an Application (on page 19). Adding a project to the PDS 3D Module. For more information, see Adding a Project (on page 23).

Creating DSNs The PDS 3D Module communicates with the application database using a Data Source Name (DSN). You must create the DSN before you can view data in SmartPlant Explorer. If you are using a SQL Server database, see DSN Setup for SQL Server (on page 21) for more information. If you are using an Oracle database, see DSN Setup for Oracle Networking Components (on page 22) for more information.

D S N S et u p f o r S Q L S e r v e r 1.

Open the Control Panel and activate Data Source (ODBC).

2.

Select the System DSN tab.

3. Click Add to add your new System DSN. 4. Select SQL Server from the list. 5. Click Finish. 6.

Type the name of your new DSN. The Description field is optional.

7.

Define the database server from which you want to read.

8. Click Next. 9.

Define the configuration that the DSN should use to access the SQL Server Database.

10. Click Next. 11. Define the default SQL Server database to be accessed by this DSN. This database contains your PDS 3D project. 12. Click Next. 13. Take the default settings on this page. 14. Click Finish.


21

PDS 3D Module 15. Verify that the information on the ODBC Microsoft SQL Server Setup dialog box is correct. 16. Click Test Data Source. If you have correctly defined your new DSN, a form appears indicating that the Data Source test was successful. The new DSN is now ready to be used by the PDS 3D Module.

D SN S e tu p f o r O r a c l e Ne t w o r k i n g C o m p o n e n t s You must load and configure Oracle SQL*Net (version 2.3.4 or higher) or Net Manager on the database server and on the SmartPlant Explorer Web Server for SmartPlant Explorer to access a PDS project. If the database server and the SmartPlant Explorer Web Server are the same computer, you still must load and configure Oracle SQL*Net. Oracle SQL*Net is comprised of a client, a listener, and a network adapter, each of which can be individually selected from within the Oracle loader utility. The SQL*Net listener and the network adapter, typically TCP/IP, must be loaded on the database server. The SQL*Net client and the TCP/IP adapter must be loaded on the SmartPlant Explorer Web Server. The version of SQL*Net client and listener must be the same on both computers. When the database server and the SmartPlant Explorer Web Server are the same computer, SQL*Net client and listener must both be configured. Refer to the Oracle documentation for more information on installing Oracle SQL*Net or Net Manager. Any attempts to configure an Oracle ODBC data source rely on a functional SQL*Net or Net Manager connection. When creating an ODBC data source you are asked for a connect string, and possibly database user name and password. The connect string is the alias name. If your ODBC driver does not require a database user name to be specified as part of the data source definition, you are prompted for a database user name and password when the connection is made. SmartPlant Explorer takes this into consideration and asks for the database user name and password when you are entering data in the Add Site and Add Project dialog boxes.

Configuring Microsoft ODBC for Oracle 1.

Open the Administrative Tools and activate Data Source (ODBC).

2.

Select the System DSN tab.

3. Click Add to create a new DSN. 4. Select Microsoft ODBC for Oracle on the Create New Data Source dialog box. 5. Click Finish. 6.

Type the new Data Source Name.

7.

Type a description for the data source. This field is optional.

8.

Type a Windows user name that is valid on the Database server (optional for SmartPlant Explorer DSN).

9.

Type the alias name in the server field.

10. Click OK. You can now use the new DSN for publishing a project in SmartPlant Explorer. If you want to verify that the ODBC connection is functioning correctly, you can use an y application or utility that allows access to a database through ODBCs.

22


PDS 3D Module

Adding a Project You need to add the projects that you want to explore. 1. Right-click 3D

.

2. Select Add Project. 3.

Type a name for the project.

4.

Select the DSN (Data Source Name) for the project control database. See Creating DSNs (on page 21) for more information.

5.

Type the user name and password for the project control database.

6.

Type the UNC path to the SmartPlant Review model data. This is the location of the SmartPlant Review Publisher database.

7. Click Add Project.


23

PDS 3D Module

24


S

ECTION

4

SmartPlant Instrumentation Module The SmartPlant Instrumentation Module allows you to view and analyze changes to the SmartPlant Instrumentation database. Web access eliminates physical and geographical boundaries, and because the instrumentation data is viewed as a Web page, you can easily navigate among data objects, such as plants, areas, loops, and tags. This ability facilitates tabular reports, such as instrumentation indexes or wiring lists, and graphical reports such as instrument loops or point-to-point wiring diagrams. With a single mouse click, you can transfer data to Microsoft Excel using Microsoft Web Query technology, providing direct access to your plant information using an Excel workbook.

Configuring the SmartPlant Instrumentation Module The required steps to configure the SmartPlant Instrumentation Module are as follows: 





 





Setup for Oracle Networking Components. For more information, see Setup for Oracle Networking Components (on page 25). Add the SmartPlant Instrumentation Module to the SmartPlant Explorer Web Server. For more information, see Add an Application (on page 19). Add a site to the SmartPlant Instrumentation Module. For more information, see Adding a Site using an Oracle Database (on page 26) or Adding a Site using a Microsoft SQL Server Database (on page 26). Add the site domains. For more information, see Adding a Domain (on page 27). Add the SmartPlant Instrumentation Web Server for reports. For more information, see Define the Location of SmartPlant Instrumentation Web Server (see "Define the Location of SmartPlant Instrumentation Server " on page 27). Add plants (or the next level if you are using a flexible hierarchy) to the domains. For more information, see Adding a Plant (on page 28). Add the users to the SmartPlantInstrumentationEngineer role that you want to access engineering projects (as opposed to As-Built projects). For more information, see Access Control (on page 39).

Setup for Oracle Networking Components You must load and configure Oracle SQL*Net or Net Manager on the SmartPlant Instrumentation database server and on the SmartPlant Instrumentation Module server for SmartPlant Explorer to access a SmartPlant Instrumentation project. If the SmartPlant Instrumentation database server and the SmartPlant Instrumentation Module server are the same computer, you still must load and configure Oracle SQL*Net. Oracle SQL*Net is comprised of a client, a listener, and a network adapter, each of which can be individually selected from within the Oracle loader utility. The SQL*Net listener and the network adapter, typically TCP/IP, must be loaded on the database server. The SQL*Net client and the TCP/IP adapter must be loaded on the SmartPlant Instrumentation Module server. The version of SQL*Net client and listener must be the same on both computers. Refer to the Oracle documentation for more information on installing Oracle SQL*Net or Net Manager.


25

SmartPlant Instrumentation Module Any attempts to configure an Oracle ODBC data source rely on a functional SQL*Net or Net Manager connection. When creating an ODBC data source you are asked for a connect string, and possibly database user name and password. The connect string is the alias name. If your ODBC driver does not require a database user name to be specified as part of the data source definition, you are prompted for a database user name and password when the connection is made. SmartPlant Explorer takes this into consideration and asks for the database user name and password when you are entering data in the Add Site and Add Domain dialog boxes. If working with an Oracle database, after installing the Oracle client you must register the igrORASPConnect412.dll using the registeroracle.bat file. Both the .dll and the .bat file can be found in the SmartPlant Explorer > RAD folder on the drive where you installed SmartPlant Explorer.

Adding a Site using an Oracle Database After you have added the SmartPlant Instrumentation Module server to the SmartPlant Explorer Web Server, you need to add the SmartPlant Instrumentation sites that you want to explore. Follow these steps if the SmartPlant Instrumentation site is using an Oracle database. If the SmartPlant Instrumentation site is using a Microsoft SQL Server database, refer to Adding a Site using a Microsoft SQL Server Database (on page 26). 1. Right-click SmartPlant Instrumentation

.

2.

On the shortcut menu, click Add Site.

3.

In the Site server name field, type the SmartPlant Instrumentation site server computer name.

4. Select Oracle as the database type. 5.

Enter the Oracle Net Service Name for the database.

6.

Enter the SmartPlant Instrumentation administrator database user name and password.

7. Click Add Site.

Adding a Site using a Microsoft SQL Server Database After you have added the SmartPlant Instrumentation Module server to the SmartPlant Explorer Web Server, you need to add the SmartPlant Instrumentation sites that you want to explore. Follow these steps if the SmartPlant Instrumentation site is using a Microsoft SQL database. If the SmartPlant Instrumentation site is using an Oracle database, refer to Adding a Site using an Oracle Database (on page 26). 1. Right-click SmartPlant Instrumentation

.

2. Select Add Site. 3.

In the Site server name field, type the SmartPlant Instrumentation site server computer name.

4. Select SQL Server as the database type. 5.

In the Database server name field, type the name of the SQL Server computer.

6.

Type the SQL database name.

7.

Type the SQL Server administrator user name and password.

8.

Enter the SmartPlant Instrumentation administrator database user name and password.

9. Click Add Site.

26


SmartPlant Instrumentation Module

Adding a Domain After you have added the SmartPlant Instrumentation site, you need to specify the domains that you want to view at the site. 1.

Right-click the SmartPlant Instrumentation site

.

2. Click Add Domain. 3.

Select the domain name.

4.

Type the user name and password for the project database.

5. Click Add Domain.

Define the Location of SmartPlant Instrumentation Server Before you can generate and view SmartPlant Instrumentation reports for a domain in SmartPlant Explorer, you must install the SmartPlant Instrumentation Server. For details of the correct installation procedure, refer to your SmartPlant Instrumentation documentation. After you have installed the SmartPlant Instrumentation Server, you must define the location of the SmartPlant Instrumentation Server in SmartPlant Explorer. 1.

Right-click the domain

.

2. Click Define SmartPlant Instrumentation Server . 3. Select SmartPlant Instrumentation Server . 4.

Type the server name.

5.

Type the SmartPlant Instrumentation user name.

6.

Type the password for the SmartPlant Instrumentation user name.

7.

Type the profile name of the SmartPlant Instrumentation database if you are working in a multi-database environment. The profile must be one that appears in the Intools.ini file.

8.

Type the SmartPlant Instrumentation Preferences Users name. 



You must have installed SmartPlant Instrumentation 2007 SP6 HF 13 or higher or SmartPlant Instrumentation 2009 SP1, for this feature to work. In the Settings.js file, change the var INtools_DomainSpecificEslPreferences =false; to true. This file can be found in the home folder where you installed SmartPlant Explorer in the Web Server folder.

9. Click Test Connection. At this point, the you may be asked if it is okay to access information not under the page’s control. The test may need to access data across domains and in that case, the security setting Access data sources across domains (under Miscellaneous) will need to be set at least to Prompt. You need to click OK. 10. If the test was successful, click Add/Update SmartPlant Instrumentation Web Server .


27

SmartPlant Instrumentation Module

Adding a Plant When the sites and domains have been added, you need to specify the plants (or the next item in the hierarchy) that you want to view. 1.

Right-click the domain

.

2. Click Add Plant. 3.

Select the plants that you want to add.

4. Click Add >. 5. Click Add Plant. SmartPlant Explorer may take several minutes while adding SmartPlant Instrumentation plants to the domain.

28


S

ECTION

5

PDS PID Module The PDS PID Module provides search and view capabilities on information accessed from the PDS P&ID database. You can quickly locate, query, and display P&IDs, as well as associated documents created in PDS P&ID. This module provides for the on-demand conversion of P&ID schematics to a Web-viewable format. Intelligent data is hyperlinked to the graphics, resulting in rapid, enterprise-wide access and display of the P&ID database, with agile window navigation.

Adding a Project After you have added the PDS PID Module server to the SmartPlant Explorer Web Server, you need to add the PDS P&ID projects that you want to explore. 1. Right-click PDS PID

.

2. Click Add Project. 3.

Type a project name. The software displays this name in the tree view.

4.

Select whether you are connecting to an Oracle or SQL Server PDS database.

5.

For Oracle databases, enter the Oracle alias name, database administrator user name and password, and the PDS P&ID database user name and password.

6.

For SQL Server databases, enter the database server name, database name, database administrator user name and password, and the PDS P&ID database user name and password.

7. Click Next. 8.

Type the passwords for the P&ID Task, P&ID Master, Document Task, and Document Master database users.

9. Click Add Project. If one or more of the four possible schemas are not available in the database that you selected, the software disables the missing schema. In addition, SmartPlant Explorer may take several minutes to add a project.


29

PDS PID Module

30


S

ECTION

6

SmartPlant PID Module The SmartPlant PID Module accesses information in the SmartPlant P&ID database, providing search and view capabilities through a logical, hierarchical structure such as plant-unit. You can quickly locate, query, and display P&IDs, as well as associated data created in SmartPlant P&ID. This module provides for the on-demand display of P&ID schematics in a Web-viewable format. Intelligent data is hyperlinked to the graphics, resulting in rapid, enterprise- wide access and display of the P&ID database, with agile window navigation. You can also run and view reports using the same filters and layouts available in SmartPlant P&ID without having to run SmartPlant P&ID.

Configuring Microsoft Excel Distributed COM Configuration Properties If you plan to view SmartPlant P&ID reports using SmartPlant Explorer, you need to modify the default Distributed COM Configuration Properties for Microsoft Excel on the SmartPlant PID Module server. If you do not modify these properties, the impersonated user that SmartPlant Explorer uses cannot access Microsoft Excel to generate the reports for the client. 1.

On the SmartPlant PID Module server, click Start > Run.

2.

Type dcomcnfg.exe, and then click OK.

3.

On the tree view select Component Services > Computers > My Computer > DCOM Config > Microsoft Excel Application.

4.

Right-click and select Properties.

5.

Select the Security tab.

6.

On the Access Permissions group box, select Customize.

7. Click Edit. 8. Click Add. 9.

Add the Administrators group for your SmartPlant PID Module server with Allow Access privileges.

10. Click OK. 11. Click OK again. 12. On the Launch and Activation Permissions group box, select Customize. 13. Click Edit. 14. Verify that the Administrators group for your SmartPlant PID Module server has Allow Launch access.


31

SmartPlant PID Module

Installing Oracle Networking Components Because the SmartPlant P&ID site you are going to explore uses an Oracle database, you must load and configure Oracle Net Manager on the SmartPlant P&ID database server and on the SmartPlant PID Module server for SmartPlant Explorer to access the SmartPlant P&ID project. If the SmartPlant P&ID database server and the SmartPlant PID Module server are the same computer, you still must load and configure Oracle Net Manager. Oracle Net Manager is comprised of a client, a listener, and a network adapter, each of which can be individually selected from within the Oracle loader utility. The listener and the network adapter (typically TCP/IP) must be loaded on the database server. The client and the TCP/IP adapter must be loaded on the SmartPlant PID Module server. The version of client and listener must be the same on both computers. You can configure the networking components with the Net Manager Assistant. If you do not install Oracle Client on your SmartPlant PID Module server before installing the SmartPlant PID Module software, you will receive an error message during the setup indicating that the igrORASPConnect412.dll will not be registered. You will have to manually register this dll using the registeroracle.bat file after you install Oracle Client.

Adding the SmartPlant PID Module to the Web Server After you have installed the SmartPlant PID Module and configured the Oracle connection, you need to add the module to the SmartPlant Explorer Web Server. 1.


2.

Type http:///spex in the Address field where is the name of the SmartPlant Explorer Web Server.

3. Right-click SmartPlant Web Server

.

4. Select Add Application from the menu. 5.

Type the name of the SmartPlant PID Module server.

6. Click Search. 7. Select SmartPlant Explorer SmartPlant PID Module from the list. 8. Click Add Selected Module.

Configuring the SmartPlant PID Module After you have added the SmartPlant PID Module to the SmartPlant Explorer Web Server, you need to specify which SmartPlant Engineering Manager sites you want to explore. 



1.

The Impersonated User used by SmartPlant Explorer must be an administrator on the computer where the site smartplantv4.ini file is shared and be granted network login access to the computer. In addition to adding users to the SmartPlant Explorer user access control (using Component Services), all users accessing this SmartPlant Engineering Manager site must be granted access to the site using SmartPlant Engineering Manager's user access functionality. Start SmartPlant Explorer.

2. Right-click SmartPlant PID

.

3. Select Add Site Server .

32


SmartPlant PID Module 4.

Type a name for the site as you want it to appear in the tree view. The name is limited to 30 characters and cannot contain any of these characters: " & ' \ ^ ; < | characters.

5.

Enter the full UNC path to the SmartPlant site server smartplantv4.ini file, for example, \\server\site_folder\smartplantv4.ini. You can also use the Browse button to locate the smartplantv4.ini file on the site server.

6. Click Add Site Server .


33

SmartPlant PID Module

34


S

ECTION

7

SmartPlant Electrical Module The SmartPlant Electrical Module accesses the information in the SmartPlant Electrical database, providing search and view capab ilities through a logical, hierarchical structure such as plant-unit. You can quickly locate, query, and display SmartPlant Electrical item properties.

Configuring Microsoft Excel Distributed COM Configuration Properties If you plan to view SmartPlant Electrical reports using SmartPlant Explorer, you need to modify the default Distributed COM Configuration Properties for Microsoft Excel on the SmartPlant Electrical Module server. If you do not modify these properties, the impersonated user that SmartPlant Explorer uses cannot access Microsoft Excel to generate the reports for the client. 1.

On the SmartPlant Electrical Module server, click Start > Run.

2.

Type dcomcnfg.exe, and then click OK.

3.

On the tree view select Component Services > Computers > My Computer > DCOM Config > Microsoft Excel Application.

4.

Right-click and select Properties.

5.

Select the Security tab.

6.

On the Access Permissions group box, select Customize.

7. Click Edit. 8. Click Add. 9.

Add the Administrators group for your SmartPlant PID Module server with Allow Access privileges.

10. Click OK. 11. Click OK again. 12. On the Launch and Activation Permissions group box, select Customize. 13. Click Edit. 14. Verify that the Administrators group for your SmartPlant Electrical Module server has Allow Launch access.


35

SmartPlant Electrical Module

Installing Oracle Networking Components Because the SmartPlant Electrical site you are going to explore uses an Oracle database, you must load and configure Oracle Net Manager on the SmartPlant Electrical database server and on the SmartPlant Electrical Module server for SmartPlant Explorer to access the SmartPlant Electrical project. If the SmartPlant Electrical database server and the SmartPlant Electrical Module server are the same computer, you still must load and configure Oracle Net Manager. Oracle Net Manager is comprised of a client, a listener, and a network adapter, each of which can be individually selected from within the Oracle loader utility. The listener and the network adapter (typically TCP/IP) must be loaded on the database server. The client and the TCP/IP adapter must be loaded on the SmartPlant Electrical Module server. The version of client and listener must be the same on both computers. You can configure the networking components with the Net Manager Assistant. If you do not install Oracle Client on your SmartPlant Electrical Module server before installing the SmartPlant Electrical Module software, you will receive an error message during the setup indicating that the igrORASPConnect412.dll will not be registered. You will have to manually register this dll using the registeroracle.bat file after you install Oracle Client.

Adding the SmartPlant Electrical Module to the Web Server After you have installed the SmartPlant Electrical Module and configured the Oracle connection, you need to add the module to the SmartPlant Explorer Web Server. 1.


2.

Type http:///spex in the Address field where is the name of the SmartPlant Explorer Web Server.

3. Right-click SmartPlant Web Server

.

4. Select Add Application from the menu. 5.

Type the name of the SmartPlant Electrical Module server.

6. Click Search. 7. Select SmartPlant Explorer SmartPlant Electrical Module from the list. 8. Click Add Selected Module.

Configuring the SmartPlant Electrical Module After you have added the SmartPlant Electrical Module to the SmartPlant Explorer Web Server, you need to specify which SmartPlant Engineering Manager sites you want to explore. 



36

The Impersonated User used by SmartPlant Explorer must be an administrator on the computer where the site smartplantv4.ini file is shared and be granted network login access to the computer. In addition to adding users to the SmartPlant Explorer user access control (using Component Services), all users accessing this SmartPlant Engineering Manager site must be granted access to the site using SmartPlant Engineering Manager's user access functionality.

1.

Start SmartPlant Explorer.

2.

Right-click SmartPlant Electrical

.


SmartPlant Electrical Module 3. Select Add Site Server . 4.

Type a name for the site as you want it to appear in the tree view. The name is limited to 30 characters and cannot contain any of these characters: " & ' \ ^ ; < | characters.

5.

Define the location of the SmartPlant Electrical server.

6.

Enter the full UNC path to the SmartPlant site server smartplantv4.ini file, for example, \\server\site_folder\smartplantv4.ini. You can also use the Browse button to locate the smartplantv4.ini file on the site server.

7. Click Add Site Server .


37

SmartPlant Electrical Module

38


S

ECTION

8

Administrating SmartPlant Explorer This section contains useful information if you are responsible for administrating a SmartPlant Explorer Web Server including user access control and system security.

Access Control After installing the SmartPlant Explorer Web Server, you need to define which roles and users have access to SmartPlant Explorer. Roles are groups of users who have access to SmartPlant Explorer. You add users to roles using their standard logon details for the Windows domain. Users can be individual Windows users or Windows user groups. Users login to the SmartPlant Explorer Web Server using their regular Windows user name and password. SmartPlant Explorer checks the defined roles and users in the Component Services on Windows to verify that they have b een granted access. If they have access, SmartPlant Explorer starts. All users must have Windows logon privileges to the SmartPlant Explorer Server. Users without logon privileges cannot access SmartPlant Explorer even though they have been added to a SmartPlant Explorer Role. By default, the software creates three roles, or groups, when you install SmartPlant Explorer: Administrator, User, and Viewer. You can add more roles, for example, Purchasing, by using the Component Server Explorer.

Administrators have full access to all SmartPlant Explorer features, including defining reports, editing reports, and controlling who can run which reports. Users have less access than Administrators, but can still define and edit report definitions. Users cannot control who can run which reports. Viewers can only run reports and view the results. They cannot create any new report definitions.


39

Administrating SmartPlant Explorer Users who belong to more than one role a re granted the access privileges of the higher role. For example, if John were in the User and Viewer roles, John would have User privileges. Users who belong to more than one role are able to run all Actions available to all of the roles for which they are members. You can add your own roles using the Component Services Explorer. If you choose to create your own roles, you need to add those roles to the component interface so SmartPlant Explorer knows the needed access privileges. The four component interfaces in SmartPlant Explorer are: 







_AllActions - Roles in this interface can modify every Action menu in the application regardless of to whom and to what the Actions apply. By default, the Administrator role belongs to this interface. _Application - Roles in this interface can add and remove SmartPlant Explorer Modules. By default, the Administrator role belongs to this interface. _SPApplication - Roles in this interface can access SmartPlant Explorer. By default, the Administrator, User, and Viewer roles belong to this interface. _UserSpecificActions - As a user in a Role in this interface, you can create, delete, and modify your Actions. Other users do not see these Actions. The user also cannot modify Actions that other users own. By default, the Administrator and User roles belong to this interface.

In addition to the component interfaces, you must add your own roles to the ObjectControl interface. If you do not want to add your custom roles to the interfaces, you can still define access privileges by adding the user to both your custom role (to control what Actions they see) and to one of the delivered roles (to control access privileges). In some ways, this is a better alternative because you can define a single Administrator for your custom role and set the remaining role members as Users or Viewers. Roles that are not in _UserSpecificActions or _AllActions cannot modify Actions.

Add a Role Users must belong to one of the three delivered roles; administrator, user, or viewer; in addition to any custom defined roles. You need to restart SmartPlant Explorer in Internet Explorer to see the changes. 1. Click Start > Settings > Control Panel > Administrative Tools > Component Services . 2.

Select the computer on which the SmartPlant Explorer Web Server is installed.

3. Double-click COM+ Applications. 4.

Double-click the SmartPlant Web Server package.

5. Select Roles. 6.

Right-click, point to New, and click Role.

7.

Type the role name.

8. Click OK when prompted if you are certain the SmartPlant Explorer Web Server supports the changes. 9. Double-click Components. 10. Right-click SPEApplication.SPApplication , and then click Properties. 11. Select the Security tab. 12. Place a check next to your roles. 13. Right-click the SmartPlant Web Server package. 14. Select Shut down.

40


Administrating SmartPlant Explorer

Add a User 1. Click Start > Settings > Control Panel > Administrative Tools > Component Services . 2.

Select the computer on which the SmartPlant Explorer Web Server is installed.

3. Double-click COM+ Applications. 4.

Double-click the SmartPlant Web Server package.

5. Double-click Roles. 6.

Double-click the roles to which you want to add a user.

7.

Select the Users folder under the role.

8.

Right-click, point to New, and click User .

9.

Identify the user who you want to add.

10. Click OK. 11. Right-click the SmartPlant Web Server package. 12. Select Shut down.

System Security Every time a user attempts to access the SmartPlant Explorer Web Server, the Server authenticates, or confirms, the identity of the user to ensure that the user has a valid Windows account. This method is indispensable for limiting access to your data. Different authentication methods are available from which you can choose:  



Basic Authentication - Prompts users to type user names and passwords. Integrated Windows Authentication - Cryptographically obtains user identification information from the Web browser of the user. Secure Sockets Layer (SSL) Client Certification Authentication - Authenticates users by checking the contents of an encrypted digital identification that the Web browser submits during the logon process.

You selected either the Basic or the Integrated Windows Authentication method when you installed the SmartPlant Explorer Web Server. SmartPlant Explorer does not support Anonymous Authentication or Digest Authentication for Windows.

Basic Authentication The Basic Authentication method is a widely used, industry- standard method for collecting user name and password information. Basic Authentication proceeds as follows: 1.

The user's Web browser displays a dialog box where users can enter their previously assigned Windows account user names and passwords.

2.

The Web browser then attempts to establish a connection using this information. (The password is Base64 encoded before being sent over the network).

3.

If the server rejects the information, the Web browser repeatedly displays the dialog box until the user either enters a valid user name and password or closes the dialog box.

4.

When your Web Server verifies that the user name and password correspond to a valid Windows user account, a connection established.

For information about setting up Basic Authentication, see the IIS Documentation.


41

Administrating SmartPlant Explorer The disadvantage in using Basic Authentication is that Web browsers using Basic Authentication transmit passwords in an unencrypted form. By monitoring communications on your network, someone could easily intercept and decipher these passwords by using publicly available tools. Therefore, Basic Authentication is not recommended unless you are confident that the connection between the user and your Web Server is secure, such as a direct cable connection or a dedicated line. Integrated Windows Authentication takes precedence over Basic Authentication. The browser will choose integrated Windows Authentication and will attempt to use the current Windows logon information before prompting the user for a user name and password.

Integrated Windows Authentication Integrated Windows Authentication is a secure form of authentication because the user name and password are not sent across the network. When you enable integrated Windows authentication, the user's browser proves its knowledge of the password through a cryptographic exchange with your Web Server, involving hashing. Integrated Windows Authentication can use both the Kerberos v5 authentication protocol and its own challenge/response authentication protocol. If Directory Services is installed on the server, and the browser is compatible with the Kerberos v5 authentication protocol, both the Kerberos v5 protocol and the challenge/response protocol are used; otherwise only the challenge/response protocol is used. The Kerberos v5 authentication protocol is a feature of the Windows Distributed Services architecture. In order for Kerberos v5 authentication to be successful, both the client and server must have a trusted connection to a Key Distribution Center (KDC) and be Directory Services compatible. For more information about the protocol, see the Windows documentation. Integrated Windows Authentication proceeds as follows: Unlike Basic Authentication, it does not initially prompt users for a user name and password. The current Windows user information on the client computer is used for the integrated Windows authentication. 





However, if the authentication exchange initially fails to identify the user, the browser will prompt the user for a Windows user account user name and password, which it will process by using integrated Windows authentication. Internet Explorer will continue to prompt the user until the user enters a valid user name and password, or closes the prompt dialog box. Although integrated Windows authentication is secure, it does not work over HTTP Proxy connections. Therefore, integrated Windows authentication is best suited for an intranet environment, where both user and Web Server computers are in the same domain.

Certificate Authentication You can also use your Web Server's Secure Sockets Layer (SSL) security features for two types of authentication. You can use a server certificate to allow users to authenticate your Web site before they transmit personal information, such as a credit card number. Also, you can use client certificates to authenticate users requesting information on your Web site. SSL authenticates by checking the contents of an encrypted digital identification submitted by the user's Web browser during the logon process. (Users obtain client certificates from a mutually trusted third-party organization.) Server certificates usually contain information about your company and the organization that issued the certificate. Client certificates usually contain identifying information about the user and the organization that issued the certificate.

42


Administrating SmartPlant Explorer

Client Certificate Mapping You can associate, or map, client certificates to Windows user accounts on your Web Server. After you create and enable a certificate map, each time a user logs on with a client certificate, your Web Server automatically associates that user to the appropriate Windows user account. This way, you can automatically authenticate users who log on with client certificates, without requiring the use of either Basic or integrated Windows authentication. You can either map oneclient certificate to one Windows user account or many client certificates to one account. For example, if you had several different departments or businesses o n your server, each with its own Web site, you could use many-to-one mapping to map all of the client certificates of each department or company to its own Web site. This way each site would provide access only to its own clients.

Switching Authentication Methods You can switch between Basic Authentication and Integrated Windows Authentication. 1. Click Start > Settings > Control Panel > Administrative Tools > Internet Services Manager . 2.

Open the computer where you installed the SmartPlant Explorer Web Server.

3.

Open the Default Web Site on the server.

4. Right-click SPE, and then click Properties. 5.

Click the Directory Security tab.

6. Click Edit in the Anonymous Access and Authentication Control group. 7. Select Basic Authentication or Integrated Windows Authentication . You cannot use both authentication methods at the same time with SmartPlant Explorer. You must select one or the other. 8. Click OK. 9. Click OK. 10. Exit Internet Information Services.

Changing Session Timeout The SmartPlant Explorer Web Server disconnects an inactive client connection after 20 minutes (the default IIS setting). This operation ensures that memory and processing resources on the web server are not wasted on inactive connections. However, if you are frequently receiving the "Your connection to the SmartPlant Explorer server has timed out" message, you can increase this timeout period. We do not recommend setting the timeout period greater than 20 minutes unless your web server has the memory and p rocessing resources to handle it. 1.

Log on as an administrator on the web server.

2. Click Start > Settings > Control Panel > Administrative Tools > Internet Services Manager . 3.

Open the Internet Information Server folder.

4.

Double-click your computer name to expand the branch.

5. Double-click Default Web Site to expand the branch. 6. Right-click SmartPlant Explorer , and then select Properties. 7.

Select the Virtual Directory tab.

8. Click Configuration in the Application Settings grouping. 9.

Select the Options tab.

10. Change the Session timeout option to new timeout period.


43

Administrating SmartPlant Explorer 11. Click OK. 12. Click OK on the SmartPlant Explorer Properties dialog box.

Important Files to Back Up SmartPlant Explorer uses several Microsoft Access databases to track actions, reports, projects, and connection information. When you are finished installing, publishing, and configuring SmartPlant Explorer, you need to backup these databases. If your hard drive fails or you buy a new server, you can simply install SmartPlant Explorer and copy the database files, and you will be exploring again without re- publishing or re-creating custom reports. Regularly backup these files: ..\SmartPlant\Explorer\Web Server\System\Actions.mdb ..\SmartPlant\Explorer\3D Module\SPE3D.mdb ..\SmartPlant\Explorer\INtools Module\SPEINtools.mdb ..\SmartPlant\Explorer\SmartPlant Module\SPESP.mdb ..\SmartPlant\Explorer\PDS PID Module\SPEPDS2D.mdb ..\SmartPlant\Explorer\Electrical Module\SPESPEL.mdb The default installation folder is C:\Program Files. If you installed SmartPlant Explorer to a different folder, substitute your installation path.

Changing Settings As the administrator of SmartPlant Explorer, you may need to change a setting in the c:\Program Files\SmartPlant\Explorer\Web Server\settings.js file. All settings are documented in the file. Only make a change to this file if you are experiencing a problem that editing a setting may correct or if you are directed to make the change by Intergraph support.

44


Index A active server pages • 18 allowing • 18 ActiveX settings • 19 adding • 23, 26, 28, 40, 41 PDS 3D projects • 23 roles • 40 SmartPlant Instrumentation Oracle site • 26 SmartPlant Instrumentation plants • 28 SmartPlant Instrumentation SQL site • 26 users • 41 administration • 39 administrator • 18 administrators role • 39 AL16UTF16 • 5 AL32UTF8 • 5 AllActions • 39 allowing active server pages • 18 Application • 39 applications • 19, 20 adding • 19 removing • 20 authentication methods • 43 switching • 43

B backup files • 44 Basic Authentication • 41 bi-lingual projects • 5

C Certificate Authentication • 42 changing • 43 session timeout • 43 character sets • 5 client connection timeout • 43 COM configuration • 31, 35 components • 39 AllActions • 39 Application • 39 SPApplication • 39 UserSpecificActions • 39 configuration • 18 configuring • 18, 21, 25, 32, 36 PDS 3D Module • 21 SmartPlant Electrical Module • 36 SmartPlant Instrumentation Module • 25


SmartPlant PID Module • 32 Windows 2003 Server • 18 cookies • 19 creating DSNs • 21, 22 Oracle • 22 SQL Server • 21 creating roles • 40 cultural conventions • 5

D database • 5 character sets • 5 date format • 5 decimal point • 5 distributed COM configuration • 31, 35 distributed installation • 10 domains • 27 adding SmartPlant Instrumentation • 27 DSNs • 21, 22 Oracle • 22 SQL Server • 21

F files • 44 backup these • 44

H hardware recommendations • 8 hardware requirements • 9 heterogeneous environment • 5 homogeneous environment • 5

I IIS • 18 allowing active server pages • 18 impersonated users • 11 inactive client connection • 43 installing • 13, 16 installing SmartPlant Explorer • 12, 13 Internet Explorer • 13 modules • 16 web server • 13 Integrated Windows Authentication • 42 internationalization • 5 Internet Explorer • 13, 19 ActiveX settings • 19 installing • 13

45

Index introduction • 7

K keyboard • 5 locale • 5

L locale boundary • 5

M Microsoft Excel • 31, 35 MicroStation reference files • 18 modules • 16, 19, 20 adding • 19 installing • 16 removing • 20 MTS • 18

N new features • 7 new roles • 40 NLS_LANG • 5

O ObjectControl • 39 Oracle • 25, 32, 36 SmartPlant Electrical Module • 36 SmartPlant Instrumentation Module setup • 25 SmartPlant PID Module • 32

P paths to MicroStation reference files • 18 PDS • 7 PDS 3D Module • 21, 22, 23 adding a project • 23 configuring • 21 creating DSNs • 21, 22 PDS PID Module • 29 adding projects • 29 plants • 28 adding to SmartPlant Instrumentation • 28 projects • 23, 29 adding a PDS 3D • 23 adding to PDS PID Module • 29

R recommendations • 8 hardware • 8

46

software • 8 regional settings • 5 removing • 12 SmartPlant Explorer • 12 reports • 31, 35 roles • 18, 39, 40 adding • 40 administrators • 39 introduction • 39 users • 39 viewers • 39

S security • 19, 41 ActiveX settings • 19 cookies • 19 session timeout • 43 SetMstnRefPath.exe • 18 settings • 19, 44 ActiveX • 19 cookies • 19 sites • 26 adding SmartPlant Instrumentation Oracle site • 26 adding SmartPlant Instrumentation SQL site • 26 SmartPlant Electrical Module • 36 adding to web server • 36 configuring • 36 Oracle networking • 36 SmartPlant Engineering Manager • 32, 36 SmartPlant Explorer • 11, 12, 19, 44 SmartPlant Explorer modules removing • 12 settings • 44 starting • 19 upgrading • 11 SmartPlant Instrumentation • 7 SmartPlant Instrumentation Module • 25, 26, 27, 28 adding a domain • 27 adding Oracle site • 26 adding plants • 28 adding SQL site • 26 configuring • 25 Oracle • 25 report web server • 27 SmartPlant Module • 31, 35 SmartPlant PID Module • 32 adding to web server • 32 configuring • 32 Oracle networking • 32 SmartPlant Review • 21


Spe Install Guide

Recommend Documents