Escolar Documentos
Profissional Documentos
Cultura Documentos
Installation Guide
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.
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.
Trademarks
Intergraph, the Intergraph logo, PDS, SmartPlant, SmartMarine, FrameWorks, I-Convert, I-Export, I-Sketch, IntelliShip, INtools,
ISOGEN, MARIAN, SmartSketch, SPOOLGEN, 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 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 ............................................................................ 25
Setup for Oracle Networking Components ..................................................................................... 25
Adding a Site using an Oracle Database ....................................................................................... 26
Adding a Site using a Microsoft SQL Server Database ................................................................. 26
Adding a Domain ............................................................................................................................ 27
Define the Location of SmartPlant Instrumentation Server ............................................................ 27
Adding a Plant ................................................................................................................................ 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 PID Module to the Web 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
Contents
Adding the SmartPlant Electrical Module to the Web Server ............................................................... 36
Configuring the SmartPlant Electrical Module ...................................................................................... 36
Administrating SmartPlant Explorer ....................................................................................................... 39
Access Control ...................................................................................................................................... 39
Add a Role ...................................................................................................................................... 40
Add a User ...................................................................................................................................... 41
System Security .................................................................................................................................... 41
Basic Authentication ....................................................................................................................... 41
Integrated Windows Authentication ................................................................................................ 42
Certificate Authentication................................................................................................................ 42
Switching Authentication Methods ................................................................................................. 43
Changing Session Timeout ............................................................................................................ 43
Important Files to Back Up.................................................................................................................... 44
Changing Settings ................................................................................................................................. 44
Index ........................................................................................................................................................... 45
SECTION 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
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.
SECTION 2
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.
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 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.
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.
Supported Database
software.
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
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.
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 application module server. You can change either user
name or user password on the appropriate server after installation using Microsoft Component
Services on Windows.
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
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.
12
13
10.
11.
12.
13.
14.
15.
14
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.
Click Next.
Type your name, company name, and the serial number in the appropriate fields, and then
click Next.
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.
Read the software license agreement, and then click Yes.
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).
Wait while files are installed.
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
16
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).
9.
10.
11.
12.
13.
14.
15.
16.
17.
If you do not specify the impersonated user name during the module installation, you
must do the following after completing the installation:
On the computer where the module is installed, start Windows Explorer.
Navigate to the folder where the module is installed. The default location is: ...\Program
Files\SmartPlant\Explorer\SmartPlant Module.
Right-click on the folder, and then click Properties.
Click the Sharing tab.
Click Permissions.
Add the Windows user, with Full Control permission, that the SmartPlant Explorer Web Server
is currently impersonating.
Navigate to ...\Common Files\Intergraph Shared\SmartPlant.
Right-click on the folder, and then click Properties.
Click the Sharing tab.
17
Configuration Activities
The following section contains information on various configuration activities that you must
perform in order that SmartPlant Explorer will function correctly.
18
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.
Add an Application
1. Start SmartPlant Explorer in Internet Explorer by typing http://<server>/spex/ where <server>
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
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.
Remove an Application
1. Right-click one of the following application icons:
PDS 3D
SmartPlant Instrumentation
PDS PID
SmartPlant PID
1.
2.
3.
4.
.
SmartPlant Electrical
On the shortcut menu, click Remove Application.
Select Save information.
Click Yes to confirm that you want to remove the application.
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.
20
.
.
.
.
SECTION 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.
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.
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.
22
PDS 3D Module
Adding a Project
You need to add the projects that you want to explore.
1.
2.
3.
4.
Right-click 3D
.
Select Add Project.
Type a name for the project.
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
SECTION 4
25
26
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.
2.
3.
4.
5.
27
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.
2.
3.
4.
5.
.
Right-click the domain
Click Add Plant.
Select the plants that you want to add.
Click Add >.
Click Add Plant.
SmartPlant Explorer may take several minutes while adding SmartPlant Instrumentation
plants to the domain.
28
SECTION 5
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.
2.
3.
4.
5.
6.
7.
8.
9.
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
30
SECTION 6
31
32
33
34
SECTION 7
35
36
37
38
SECTION 8
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 been
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
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
Add a User
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
Click Start > Settings > Control Panel > Administrative Tools > Component Services.
Select the computer on which the SmartPlant Explorer Web Server is installed.
Double-click COM+ Applications.
Double-click the SmartPlant Web Server package.
Double-click Roles.
Double-click the roles to which you want to add a user.
Select the Users folder under the role.
Right-click, point to New, and click User.
Identify the user who you want to add.
Click OK.
Right-click the SmartPlant Web Server package.
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
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
43
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
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
Index
software recommendations 8
software requirements 9
SPApplication 39
47