PW Implementation Guide

ProjectWise
V8i (SELECTseries 4)
Implementation Guide
Last Updated: April 25, 2013
Notices
Notices
Trademark Notice
Bentley and the B Bentley logo are either registered or unregistered trademarks or service marks of
Bentley Systems, Incorporated, or one of its direct or indirect wholly-owned subsidiaries.
Autodesk, AutoCAD, and Revit are registered trademarks or trademarks of Autodesk, Inc., and/or its
subsidiaries and/or affiliates in the USA and/or other countries.
Other brands and product names are trademarks of their respective owners.
Copyright Notice
Copyright 2013 Bentley Systems, Incorporated.
ProjectWise, Copyright 2013 Bentley Systems, Incorporated.
All Rights Reserved.
Including software, file formats, and audiovisual displays; may only be used pursuant to applicable
software license agreement; contains confidential and proprietary information of Bentley Systems,
Incorporated and/or third parties which is protected by copyright and trade secret law and may not be
provided or otherwise made available without proper authorization.
Acknowledgements
Certain portions 2008 Autodesk, Inc. All rights reserved.
Contains Autodesk DWG technology by Autodesk, Inc.
Portions Microsoft Corporation
Portions WebFX
Portions GDAL Core 1988, 2002 Frank Warmerdam
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit.
(http://www.openssl.org/)
Restricted Rights Legends

If this software is acquired for or on behalf of the United States of America, its agencies and/or
instrumentalities (U.S. Government), it is provided with restricted rights. This software and
accompanying documentation are commercial computer software and commercial computer
software documentation, respectively, pursuant to 48 C.F.R. 12.212 and 227.7202, and restricted
computer software pursuant to 48 C.F.R. 52.227-19(a), as applicable. Use, modification, reproduction,
release, performance, display or disclosure of this software and accompanying documentation by the
ProjectWise
Notices
Notices
U.S. Government are subject to restrictions as set forth in this Agreement and pursuant to 48 C.F.R.
12.212, 52.227-19, 227.7202, and 1852.227-86, as applicable.
Contractor/Manufacturer is Bentley Systems, Incorporated, 685 Stockton Drive, Exton, PA 19341-0678.
Unpublished - rights reserved under the Copyright Laws of the United States and International treaties.
ProjectWise
Table of Contents
Chapter 1: What's New? ............................................................................................13
New in ProjectWise V8i (SELECTseries 4) Refresh ...................................................................................................................13
ProjectWise Explorer Enhancements ...............................................................................................................................13
Integration Enhancements ....................................................................................................................................................14
ProjectWise Administrator Enhancements ....................................................................................................................16
Infrastructure Enhancements ..............................................................................................................................................17
Miscellaneous Enhancements ..............................................................................................................................................17
New in ProjectWise V8i (SELECTseries 4) ....................................................................................................................................17
ProjectWise Web Parts Enhancements ............................................................................................................................28
Bentley i-model Composition Server for PDF ..............................................................................................................29
ProjectWise Desktop and Server Applications for the Mobile Workflow .........................................................29
ProjectWise Dependency Service ......................................................................................................................................42
ProjectWise PDx Dynamic Review Service ....................................................................................................................42
Dynamic Composition Service Enhancement ...............................................................................................................43
Spatial Integration Enhancements .....................................................................................................................................44
ProjectWise Automation Service Enhancements ........................................................................................................52
ProjectWise Distribution Service Enhancements ........................................................................................................52
New in ProjectWise V8i .........................................................................................................................................................................54
Spatial Features Added to ProjectWise ............................................................................................................................62
ProjectWise
Chapter 2: Database Setup .......................................................................................67

Setting Up the Main ProjectWise Database ...................................................................................................................................67
Setting Up ProjectWise Orchestration Framework Service and its Database ...............................................................68
Before You Install ProjectWise Orchestration Framework Service ....................................................................69
To Install ProjectWise Orchestration Framework Service ......................................................................................70
To Create a New Orchestration Framework Database ..............................................................................................72
Chapter 3: ProjectWise Integration Server Configuration .....................................75

Setting Up the ProjectWise Integration Server Computer .....................................................................................................75
Full Text Indexing Configuration Checklist ....................................................................................................................75
Thumbnail Image Extractor Configuration Checklist ................................................................................................78
File Property Extractor Configuration Checklist .........................................................................................................79
Installing ProjectWise Integration Server ......................................................................................................................80
Installing ProjectWise Administrator ...............................................................................................................................85
Installing the Example Dataset and Business Process Template for BS1192 .................................................91
Creating Datasources ..............................................................................................................................................................................96
Before You Create the Datasource .....................................................................................................................................96
To Create a ProjectWise Datasource .................................................................................................................................97
Configuring the Example Datasource Template ......................................................................................................................111
To Manually Import the Example Template ...............................................................................................................112
To Manually Import the Example Attribute Exchange Rules ..............................................................................112
Run a Reference and Link Set Scan on the Example Dataset ...............................................................................112
Import a Coordinate System to Use with the Example Dataset ..........................................................................113
Create the Single Layer Background Maps To Use with the Example Dataset .............................................114
Create the Multi-layer Background Map To Use with the Example Dataset .................................................114
Assign Background Maps to Their Corresponding Projects/Folders ..............................................................115
Loading a Single Spatial Location File That Has Multiple Locations ................................................................116
Loading Multiple Spatial Location Files, Each Having One Location ................................................................117
Importing Example Access Control Settings ...............................................................................................................117
Importing the Delivered Rules Engine Templates and Workflow Rules .......................................................................118
To Import the Generic Workflow Rules Engine Template ....................................................................................118
To Import the ProjectWise Business Process Template for BS1192 ...............................................................120
Presetting the Full Text Index Storage Location ......................................................................................................................121
To Preset the Full Text Index Storage Location .........................................................................................................122
Moving Document Processors to a Secondary Server ...........................................................................................................122
To Move the Document Processors to a Secondary Server ..................................................................................122
Installing ProjectWise Servers on Computers with Non-English Regional Settings ................................................123
Setting Up ProjectWise Integration Servers in a Clustered Environment ....................................................................124
Setting Up Your Server Cluster .........................................................................................................................................124
Installing ProjectWise Integration Servers and Configuring the Datasource ...............................................125
Adding Servers to ProjectWise Integration Server's Trusted Servers List ..................................................................126
To Add a Server's IP Address to the Trusted Servers List ....................................................................................127
Chapter 4: ProjectWise User Synchronization Service Configuration ...............129

Before You Install ProjectWise User Synchronization Service ..........................................................................................129
To Install ProjectWise User Synchronization Service ...........................................................................................................129
To Set Up ProjectWise User Synchronization Service as an Intermediate Login Provider for Users with
Windows-based Accounts .................................................................................................................................................................132
Chapter 5: ProjectWise Caching Server Configuration ........................................135

Before You Install or Upgrade ProjectWise Caching Server ...............................................................................................135
ProjectWise
To Install ProjectWise Caching Server .........................................................................................................................................136

To Upgrade to ProjectWise Caching Server V8i (SELECTseries 4) ..................................................................................138
Chapter 6: ProjectWise Gateway Service Configuration ......................................141

Before You Install or Upgrade ProjectWise Gateway Service ............................................................................................141
To Install ProjectWise Gateway Service ......................................................................................................................................142
To Upgrade to ProjectWise Gateway Service V8i (SELECTseries 4) ...............................................................................144
Chapter 7: ProjectWise Indexing Service Configuration ......................................147

Before You Install ProjectWise Indexing Service ....................................................................................................................147
To Install ProjectWise Indexing Service ......................................................................................................................................148
To Register a Standalone ProjectWise Indexing Service ......................................................................................................150
Chapter 8: ProjectWise Explorer Configuration ....................................................153

Installing ProjectWise Explorer and iDesktop Integration .................................................................................................153
Before You Install or Upgrade ProjectWise Explorer .............................................................................................153
To Install ProjectWise Explorer (Without the DGN Navigator Control) .........................................................155
To Install ProjectWise Explorer and/or the DGN Navigator Control ...............................................................158
To Upgrade to ProjectWise Explorer V8i (SELECTseries 4) ................................................................................159
Adding Bentley Systems as a Trusted Publisher ......................................................................................................................162
Modifying Integration Options ........................................................................................................................................................162
To Integrate with an Application That Was Installed After ProjectWise Explorer ....................................162
To Turn Off Integration with an Application, After Installation .........................................................................163
To Upgrade Microsoft Office on Your Existing ProjectWise Explorer Installation ....................................163
To Upgrade Both Microsoft Office and ProjectWise Explorer .............................................................................163
Switching the Active Version of ProjectWise Explorer .........................................................................................................163
Desktop Integration for Bentley Applications ..........................................................................................................................164
To Disable Desktop Integration for Bentley Navigator, Bentley View, or Bentley i-model
Composer ...................................................................................................................................................................................164
Running ProjectWise Explorer on Citrix XenApp ....................................................................................................................165
To Configure ProjectWise Explorer to Run in a Citrix XenApp Environment ..............................................165
Installing the Delivered Add-ons to ProjectWise Explorer .................................................................................................167
To Install the ProjectWise Export/Import Tool ........................................................................................................167
To Install ProjectWise i-model Packager ......................................................................................................................169
Chapter 9: ProjectWise Web Server Configuration ..............................................171

ProjectWise Web Server Overview ................................................................................................................................................171
Before You Install and Deploy ProjectWise Web Server and Web View Server ........................................................171
Installing and Deploying ProjectWise Web Server with SharePoint Search Integration .......................................174
Configuring ProjectWise Web Server with SharePoint Search Integration ..................................................174
To Install ProjectWise Web Server with SharePoint Search Integration .......................................................175
To Send a Trust Request from SharePoint Central Administration After Installation .............................179
To Grant a SharePoint Search Integration Trust Request in ProjectWise Administrator .......................180
To Perform a Full Crawl of the ProjectWise Full Text Index ................................................................................181
To Configure This ProjectWise Web Server Deployment on SharePoint to Use ProjectWise Single
Sign-On ........................................................................................................................................................................................182
Installing ProjectWise Web Server Without SharePoint Search Integration ..............................................................183
To Install ProjectWise Web Server Without SharePoint Search Integration ...............................................183
Deploying ProjectWise Web Server and ProjectWise Web View Server ......................................................................184
To Deploy ProjectWise Web Server or ProjectWise Web View Server ...........................................................184
Configuring Single Sign-On for ProjectWise Web Server .....................................................................................................188
ProjectWise
To Create a Delegate User in ProjectWise Administrator .....................................................................................188

To Enter the Credentials of the Delegate User on the ProjectWise Web Server Computer ...................189
Integrating with ProjectWise Publishing Server .....................................................................................................................190
ProjectWise Publishing Server Integration Checklist .............................................................................................190
To Install the Web Server (IIS) Role and Role Services Required for ProjectWise Publishing
Server ...........................................................................................................................................................................................190
To Install ProjectWise Publishing Server .....................................................................................................................191
To Add the ProjectWise Publishing Server Address to the Datasource Settings ........................................195
To Set ProjectWise Publishing Server as the Web Viewer for DGN and DWG Documents .....................196
To Install ProjectWise Publishing Gateway Service ................................................................................................197
Using Workspace Profiles with ProjectWise Publishing Server .........................................................................199
Configuring Design Compare ............................................................................................................................................................200
To Set Up Design Compare on the ProjectWise Web Server / SharePoint Computer ..............................200
To Set Up Design Compare on a Computer Where ProjectWise Web Server and SharePoint Are Not
Installed ......................................................................................................................................................................................200
To Set Up a New IIS Site (for Design Compare) That Uses a 32-bit Application Pool, on a 64-bit
Windows Server 2008 Computer ....................................................................................................................................201
Authentication Methods for Design Compare ............................................................................................................202
Configuring ProjectWise Web Parts in SharePoint .................................................................................................................202
To Add ProjectWise Web Parts to a SharePoint Page .............................................................................................203
To Connect Web Parts to a Datasource Using Single Sign-on, on a SharePoint Website .........................204
To Connect Web Parts to a Datasource Without Single Sign-On, on a SharePoint Website ...................206
To Modify a Web Part's General SharePoint Settings .............................................................................................208
To Set the Topmost Folder or Project That Displays in the Navigation, Content, and Spatial Content
Web Parts ...................................................................................................................................................................................209
To Set Whether Searches Will Search the Topmost Folder, or the Entire Datasource .............................209
To Set the Search Web Part's Default Search Method .............................................................................................210
Configuring ProjectWise Web Parts in a Standalone IIS Website ....................................................................................210
Configuring IIS Settings in a Standalone IIS Deployment ......................................................................................210
Connecting Web Parts to the Datasource, in a Standalone IIS Deployment ..................................................211
Configuring ProjectWise Web Parts Client Computers .........................................................................................................215
Adding the Web Parts Site to the Trusted Sites List ................................................................................................215
Configure Internet Explorer Security Settings ...........................................................................................................215
Turning Off Your Browser's Popup Blocker ................................................................................................................216
Installing .NET Framework 3.5 for the Navigator Web Part ...............................................................................216
Remotely Installing ActiveX Controls for Users ........................................................................................................217
User Settings for ProjectWise Web Parts Users .......................................................................................................................217
Support for Microsoft Forefront TMG ..........................................................................................................................................218
Support for Microsoft Network Load Balancing ......................................................................................................................219
Upgrading ProjectWise Web Server on SharePoint ...............................................................................................................219
To Upgrade ProjectWise Web Server on the Same or Later Version of SharePoint ..................................219
To Upgrade SharePoint When ProjectWise Web Server Is Already Deployed ............................................220
Undeploying and Uninstalling ProjectWise Web Server and Web View Server ........................................................220
To Undeploy ProjectWise Web Server and/or Web View Server ......................................................................221
Chapter 10: Bentley i-model Composition Server for PDF Configuration ..........223
Bentley i-model Composition Server for PDF Overview ......................................................................................................223
Configuration Checklist for Bentley i-model Composition Server for PDF ..................................................................223
Setting Up the Bentley i-model Composition Server for PDF Working Directory .....................................................226
Installing the Required CAD Print Engines ................................................................................................................................227
Installing and Configuring the Applications Required for Creating Renditions from Office Documents .......228
ProjectWise
To Configure the Word and Excel Providers with Ghostscript ...........................................................................229

Installing Bentley i-model Composition Server for PDF ......................................................................................................230
Before You Install Bentley i-model Composition Server for PDF ......................................................................230
To Perform a Standard Installation of Bentley i-model Composition Server for PDF ..............................231
To Perform a Custom Installation of Bentley i-model Composition Server for PDF, with an
Orchestration Instance .........................................................................................................................................................241
To Perform a Custom Installation of Bentley i-model Composition Server for PDF, Without an
Orchestration Instance .........................................................................................................................................................243
Adding Bentley i-model Composition Server for PDF to the Trusted Servers List ...................................................245
Adding the Location of the Bentley i-model Composition Server for PDF IIS Web Service to dmskrnl.cfg ...245
To Add the Location of the Bentley i-model Composition Server for PDF IIS Web Service to
dmskrnl.cfg ................................................................................................................................................................................245
Setting Up the Default User ...............................................................................................................................................................245
To Set Up the Default User, and Other Bentley i-model Composition Server Administrator Users ...246
Configuring Users to Receive Email Notifications ...................................................................................................................247
Changing the Default ProjectWise InterPlot Organizer Printer ........................................................................................247
To Change the ProjectWise InterPlot Organizer Printer .......................................................................................248
Upgrading Job Schedules Created in 'ProjectWise Dynamic Composition Server for PDF' ..................................248
Chapter 11: ProjectWise Automation Service Configuration ..............................249

Automation Service Overview .........................................................................................................................................................249
Configuration Checklist for the Bentley i-model Composition Server for i-model Extension .............................249
Configuration Checklist for the DGN Indexing Extension ....................................................................................................251
Setting Up the Automation Service Working Directory ........................................................................................................252
Installing ProjectWise Automation Service ...............................................................................................................................252
Before You Install ProjectWise Automation Service ...............................................................................................253
To Install ProjectWise Automation Service (Standard Installation) ................................................................253
To Install Individual ProjectWise Automation Service Processors and Dispatchers (Custom
Installation) ...............................................................................................................................................................................262
Installing ProjectWise Automation Service Administrator .................................................................................................264
Before You Install ProjectWise Automation Service Administrator on Its Own Computer ...................265
To Install ProjectWise Automation Service Administrator ..................................................................................265
Adding ProjectWise Automation Service to the Trusted Servers List ............................................................................267
Setting Up the ProjectWise User(s) Who Will Run Automation Service Jobs .............................................................267
To Set Up a User to Run Jobs in Orchestration Framework Administrator ..................................................268
Uninstalling ProjectWise Automation Service ..........................................................................................................................268
Chapter 12: ProjectWise Distribution Service Configuration ..............................269

Distribution Service Overview .........................................................................................................................................................269
Configuration Checklist for ProjectWise Distribution Service ..........................................................................................269
Configuration Checklist for ProjectWise InterPlot Server ...................................................................................................271
Setting Up ProjectWise InterPlot Server for ProjectWise Distribution Service .........................................................271
To Configure the Identity of the Launching User ......................................................................................................272
To Create a NUL Printer Port .............................................................................................................................................272
Setting Up the Distribution Service Working Directory .......................................................................................................272
Installing ProjectWise Distribution Service ...............................................................................................................................273
Before You Install ProjectWise Distribution Service ...............................................................................................273
To Install ProjectWise Distribution Service (Standard Installation) ...............................................................273
To Install ProjectWise Distribution Service (Custom Installation) ...................................................................282
Installing ProjectWise Distribution Service Administrator ................................................................................................284
Before You Install ProjectWise Distribution Service Administrator on Its Own Computer ..................285
ProjectWise
To Install ProjectWise Distribution Service Administrator .................................................................................285

Installing ProjectWise Distribution Service Plug-in for ProjectWise InterPlot Server ...........................................287
To Install ProjectWise Distribution Service Plug-in for ProjectWise InterPlot Server ............................287
Adding ProjectWise Distribution Service to the Trusted Servers List ...........................................................................288
Setting Up the ProjectWise User(s) Who Will Run Distribution Service Jobs .............................................................289
Uninstalling ProjectWise Distribution Service .........................................................................................................................289
Chapter 13: ProjectWise web services Configuration ..........................................291

Installing and Deploying ProjectWise web services ..............................................................................................................291
Before You Install and Deploy ProjectWise web services .....................................................................................291
To Install ProjectWise web services ...............................................................................................................................292
To Deploy ProjectWise web services .............................................................................................................................293
To Test Your Deployment ...................................................................................................................................................293
Retrieving Datasource List Information ......................................................................................................................................294
To Configure the Datasource List ....................................................................................................................................294
To Test Your Datasource Connection Configuration ...............................................................................................294
Chapter 14: Language Packs ..................................................................................295

Before You Install the ProjectWise Language Pack ................................................................................................................295
To Install the ProjectWise Language Pack ..................................................................................................................................295
After You Install the ProjectWise Language Pack ...................................................................................................................296
Chapter 15: Configuring the ProjectWise Network ...............................................299

Connecting Clients and Servers (Overview) ..............................................................................................................................299
Connecting Individual Clients to the Server ..............................................................................................................................299
To Open the ProjectWise Network Configuration Settings Dialog ....................................................................301
To Connect to a Server and Get Its List of Datasources (TCP) ............................................................................302
To Point to the Server from Which the Client Can Get Server Name Resolution Information ..............303
To Prevent the Use of UDP ..................................................................................................................................................304
Publishing Datasource Lists to Multiple Clients ......................................................................................................................305
To Set Up a Gateway Service to Publish Datasource Lists from One or More Servers .............................305
To Create a Link to a Datasource on Another Server ..............................................................................................306
Setting Up Gateway Information to Redirect Client Requests ...........................................................................................310
To Configure the [Gateway] Section to Redirect Client Requests ......................................................................312
Setting Up Routing Information to Forward Redirected Client Requests ....................................................................313
To Configure a Server to Forward Requests ...............................................................................................................313
Configuring Server-to-Server Routing .........................................................................................................................................314
To Set Up a Standard Server-to-Server Routing Configuration ..........................................................................315
To Set Up a Unidirectional Server-to-Server Routing Configuration ...............................................................315
Broadcasting and Listening Ports Used by Servers ................................................................................................................316
To Change the Default Ports Used by the Server ......................................................................................................317
Windows Firewall Exceptions List (Windows XP only) .........................................................................................317
ProjectWise Server Name Resolution ...........................................................................................................................................318
Setting Up ProjectWise to Use IPv6 ..............................................................................................................................................318
To Enable ProjectWise Clients to Use IPv6 ..................................................................................................................319
To Enable ProjectWise Servers to Use IPv6 ................................................................................................................320
Chapter 16: Operational Procedures ......................................................................321

Backup and Restore Procedures .....................................................................................................................................................321
Full Backup: One-to-One Project Definition ................................................................................................................321
Full Restore ...............................................................................................................................................................................321
ProjectWise
10
Incremental Restore ..............................................................................................................................................................322

Full Backup: One-to-Many Project Definition .............................................................................................................323
Project Restoration Using the ProjectWise Import Wizard .................................................................................323
Archival Procedures .............................................................................................................................................................................324
Archive Approach 1 - Back Up All Data and Move to Offline Storage ...............................................................324
Project Restoration Using the ProjectWise Import Wizard .................................................................................326
Archive Approach 2 - Archival of Files Only ...............................................................................................................327
Archive Approach 3 - Keeping All Data Online ..........................................................................................................327
Disaster Recovery Procedures .........................................................................................................................................................329
ProjectWise Server Components .....................................................................................................................................329
ProjectWise Client Components .......................................................................................................................................330
Backing Up Configuration Files ........................................................................................................................................331
Rebuilding the ProjectWise Server .................................................................................................................................332
Chapter 17: Upgrade Planning ................................................................................335

ProjectWise Application Integration Compatibility ...............................................................................................................335
Setting Up a Test Environment ........................................................................................................................................................335
Upgrading to ProjectWise V8i (SELECTseries 4) .....................................................................................................................336
General ........................................................................................................................................................................................336
Precautions ................................................................................................................................................................................343
Suggested Migration Process .............................................................................................................................................344
Converting Database Table Structure Using DMSCONV.EXE ...............................................................................348
Areas for Review After Migration ....................................................................................................................................351
Chapter 18: Licensing ..............................................................................................353

ProjectWise Licensing Overview ....................................................................................................................................................353
ProjectWise Integration Server and ProjectWise Caching Server Licensing ...............................................................353
ProjectWise Gateway Service Licensing ......................................................................................................................................353
Client-side Licensing for ProjectWise Explorer and ProjectWise Administrator Users .........................................354
ProjectWise Web Server and Web View Server Licensing ..................................................................................................354
Client-side Licensing for ProjectWise Web Parts Users .......................................................................................................354
ProjectWise Automation Service Licensing ...............................................................................................................................355
Launching the Product Activation Wizard .................................................................................................................................355
ProjectWise
11
This page intentionally left blank
ProjectWise
12
What's New?
New in ProjectWise V8i (SELECTseries 4) Refresh

The following are the new features and updates in ProjectWise V8i (SELECTseries 4) Refresh
(8.11.11.5xx).
ProjectWise Explorer Enhancements

These are the ProjectWise Explorer enhancements in this release.
DGN Navigator Control, for Viewing DGNs and i-models
The Bentley DGN Navigator Control is now delivered with ProjectWise Client Setups, and is used for
viewing DGNs and i-models in ProjectWise Explorer.
Installing the control adds a Navigator tab to the Preview Pane in ProjectWise Explorer. To use the
control, simply select a DGN or i-model in the document list and then select the Navigator tab. The
selected document is copied out to your working directory, and then a full-sized preview of the selected
DGN or i-model displays in the Navigator tab. The view controls available are a subset of those available
in the Bentley Navigator desktop application, so you can easily zoom in and out of the view as needed.
Note that the Navigator tab will only appear in the Preview Pane when a DGN or i-model is selected.
To install the control, select the ProjectWise Explorer with DGN Navigator Control option on the
ProjectWise Client Setups master installer. This launches a ProjectWise Explorer bundle installer, which
first installs the ProjectWise Prerequisite Runtimes, then installs the Bentley DGN Navigator Control,
then finally installs ProjectWise Explorer. If you are upgrading from a previous version, the ProjectWise
Explorer installer will upgrade your installation as usual.
Citrix XenApp 6.5 Support
This release provides support for running ProjectWise Explorer on Citrix XenApp 6.5. This is in addition
to the existing support of Citrix XenApp 6.0, which was introduced in the initial ProjectWise V8i
(SELECTseries 4) release.
Send To > Mail Recipient As Link Now Always Creates URN Links
Links created as the result of selecting Document > Send To > Mail Recipient As Link are now always
URN links, regardless of the user setting, User Interface - Use URN Links. (URN links locate the item in
the datasource using the item's GUID, rather than the item's datasource path, as is the case with URL
links.)
Note that this is a change from previous releases, where the user setting above created URN links (if you
selected Document > Send To > Mail Recipient As Link and the setting was on) or URL links (if you
selected Document > Send To > Mail Recipient As Link and the setting was off).
ProjectWise
13
What's New?
New 'Include Engineering Component Access Rights' Option on the Project Properties Dialog
There is a new option on both the Project Creation Wizard and Project Properties dialog called Include
Engineering Component Access Rights. This option is used to control whether or not component
security is available in a given project. When on, project administrators can assign component security
permissions to project participants as usual. Turning this option off instantly removes component
security for all participants in a project, and also prevents further component security from being set in
the project. This option is set per project, so you can have component security available in one project
and not available in another project.
This option can be found:
on the Define the project participants page of the Project Creation Wizard
on the Participants tab of the Project Properties dialog
This option is off by default for new projects, or existing projects with no component security already
set. If the project has some component security already set, this option will be on by default.
ProjectWise Export/Import Tool Now Delivered with Client Setups
The ProjectWise Export/Import Tool is now delivered with ProjectWise Client Setups. While the tool
itself is not new, it was previously a separate download.
This tool is used to bulk import files and attribute data from external sources into ProjectWise, or to
bulk export files and attribute data out of ProjectWise. The tool uses an Excel spreadsheet as the data
interchange format.
Workflow Rules Engine Extension
Workflow Rules Engine is a new option of the ProjectWise Explorer installer. When installed, the user
will see new options or operations on the Document > Change State menu (and the standard Next,
Previous, and Change options will be disabled) when they select a document that is in one of the
workflows where these operations are enabled. Selecting one of the operations will trigger a rule, and
the actions the administrator has defined in that rule will be run on the selected document(s).
Integration Enhancements
These are the desktop application integration enhancements in this release.
Support for Autodesk 2013 Applications
This version of ProjectWise now provides integration support for the 2013 editions of AutoCAD, its
verticals, and Revit. See the Requirements page of the ProjectWise readme for a list of supported
Autodesk applications and the specific versions supported.
AutoCAD Civil 3D Advanced Integration
This release delivers advanced ProjectWise integration support for AutoCAD Civil 3D 2013 and 2012
(32-bit and 64-bit).
ProjectWise
14
What's New?
In addition to the basic AutoCAD integration, this advanced integration offers:
support for data shortcut / data reference workflows
support for creation of surfaces
integration of the Prospector Tree
Note: While ProjectWise does continue to provide basic integration for earlier versions of AutoCAD
Civil 3D (see the ProjectWise readme for a list of supported versions), this new, advanced integration is
only provided for AutoCAD Civil 3D 2013 and 2012.
Support for 64-bit 2010 Office Applications
This version of ProjectWise now provides integration support for:
64-bit Microsoft Office 2010 (Word, Excel, Outlook, PowerPoint) (32-bit version already supported
from a previous release)
Microsoft Project 2010 and Visio 2010 (32-bit and 64 bit)
See the Requirements page of the ProjectWise readme for a list of supported Office applications and
versions.
AutoCAD Integration Enhancements
You can now temporarily disable ProjectWise integration using the new Disable Integration button
on the ProjectWise tab in AutoCAD. This lets you quickly suspend integration, without having to
turn off the feature entirely through the ProjectWise Explorer installer. As soon as you click Disable
Integration, integration is disabled and the name of the button changes to Enable Integration.
When you are ready to resume integration, click Enable Integration.
(AutoCAD 2012 and later) Full integration support for the DGNIMPORTMODE variable, which controls
the default behavior of the DGNIMPORT command, which opens a ProjectWise dialog and lets you
select a DGN document to import. Previously, only the default mode (DGNIMPORTMODE=0) was
supported. Now all modes are supported (=0, =1, and =2).
When DGNIMPORTMODE=0, DGNIMPORT imports the selected DGN document into a new drawing
file.
When DGNIMPORTMODE=1, DGNIMPORT imports the selected DGN document into the currently
open drawing and ignores duplicated named objects.
When DGNIMPORTMODE=2, DGNIMPORT imports the selected DGN document into the currently
open drawing and adds the DGN file name as a prefix to all named objects.
Revit Integration Enhancements
Resolve Links dialog - This new dialog opens automatically when you open a Revit file from ProjectWise
Explorer that either contains broken links, or links that are pointing to local documents. Use the controls
in the dialog to fix any or all of the links as needed. The display of this dialog is controlled by an option
on the new Resolve Links tab on the ProjectWise Integration Options dialog in Revit.
ProjectWise
15
What's New?
Office Integration Enhancements

You can now temporarily disable ProjectWise integration using the new Disable Integration button on
the ProjectWise tab in your Office application (Word, Excel, PowerPoint, Project, or Visio). This lets you
quickly suspend integration, without having to turn off the feature entirely through the ProjectWise
Explorer installer. As soon as you click Disable Integration, integration is disabled and the name of the
button changes to Enable Integration. When you are ready to resume integration, click Enable
Integration.
This feature is available in Office 2007 and 2010 integrations.
ProjectWise Administrator Enhancements

These are the ProjectWise Administrator enhancements in this release.
Workflow Rules Engine
The Rules Engine helps organizations better enforce their business processes within ProjectWise by
applying custom rules to existing workflows.
To begin, workflow rules are first defined locally, in an Excel workbook. The administrator defines a set
of document operations for the user to select from, such as Approve, Revise, Reject, and for which
workflow(s) these operations will be enabled. Then they define what actions are to be run on a
document when a user selects one of those operations for a document in a particular workflow state. As
a simple example, a rule might be defined: if a document is in workflow1 and state2 and operation3 is
selected, then place the document in state4 of workflow1 AND create a new version. Once the rules are
defined, the administrator imports them through the Rules Engine node in ProjectWise Administrator.
The administrator can make changes at any time and re-import the rules.
In ProjectWise Explorer, if the user has the new Workflow Rules Engine extension installed, the user
will see the new operations on the Document > Change State menu (and the standard Next, Previous,
and Change options will be disabled) when they select a document that is in one of the workflows
where these operations are enabled. Selecting one of the operations will trigger a rule, and the actions
defined in that rule will be run on the selected document(s).
An example rules file containing pre-configured workflow rules is delivered to get you started. To get
this file, you must first install the example dataset (see the ProjectWise Implementation Guide for
instructions on installing the example dataset and importing the workflow rules). You can import these
workflow rules as is or customize them first and then import them.
Templates To Use with the Rules Engine
ProjectWise Admin Setups delivers two templates to use with the new Rules Engine:
a generic rules engine template (included with the Example Dataset)
the ProjectWise Business Process Template for BS1192
To use either template, you must first install it, and then import it into your datasource.
ProjectWise
16
What's New?
New in ProjectWise V8i (SELECTseries 4)
Updated Attribute Exchange Example Files for Microsoft Office 2003

The existing Attribute Exchange example files delivered in support of Office 2003
(idAttributeExchangeConfig2003.doc and idAttributeExchangeConfig2003.xls)
have been updated for this release. Note that these files are only to be used with Microsoft Word 2003
and Microsoft Excel 2003, respectively.
Using AutoCAD Profiles Stored in ProjectWise
You can now store AutoCAD profiles in ProjectWise. When creating workspace profiles for AutoCAD
profiles in ProjectWise Administrator, you can browse to an AutoCAD profile stored in ProjectWise.
Infrastructure Enhancements
Support for Windows 8 and Windows Server 2012 (see list of supported operating systems in the
ProjectWise readme for details)
ProjectWise Full Text Indexing supports Windows Search on Windows Server 2012, and Microsoft
Indexing Service on Windows Server 2008
New option in dmskrnl.cfg (LogLicenseToWindowsEventLog) that lets you control whether or
not an informative message is sent to the Windows event log every time the server license is
renewed.
Miscellaneous Enhancements
Rebranding:
ProjectWise Dynamic Composition Server for PDF is now Bentley i-model Composition Server for
PDF
ProjectWise Dynamic Composition Server for i-model extension to ProjectWise Automation Service
is now Bentley i-model Composition Server for i-model

The following are the new features and updates that were introduced in ProjectWise V8i (SELECTseries
4) (8.11.11.1xx).

Publishing Renditions from ProjectWise Explorer
When Bentley i-model Composition Server for PDF is installed and configured, users can publish
renditions from the documents they select in ProjectWise Explorer. Users can also publish renditions by
selecting a flat set (all the documents in the flat set will be processed) or by selecting a folder or project
(all documents in all subfolders/subprojects will be processed).
ProjectWise
17
What's New?
Reference Version Locking

In ProjectWise Explorer, you can update a master document to use a different version of the same
reference document. The version that you specify will be copied out when the master document is
opened and used instead of the active version. This version of the reference will continue to be used by
the master document until or unless you select another version to lock to the master document. You can
also set it so that the active version of the reference document is always the version that is attached to
and used by the master document.
Figure 1: Reference Version Manager dialog in ProjectWise Explorer, used to update the version of
selected references being used by the master document
In support of this feature, there are some new datasource settings that control reference version locking
behavior globally, at the datasource level. See New Datasource Settings for details.
Flat Set Versioning Enhancement
Flat set versioning is not new in this release, but there is a label change and a change to the default
behavior.
ProjectWise
18
What's New?
When working with flat sets, the check box Always Use Active Version has been renamed Lock to
Version. Also, this check box is now OFF by default instead of ON. These changes were made to be
consistent with the new reference version locking feature.
After you add a document to a flat set:
Turn on Lock to Version if you want the version of the document that was active at the time it was
added to always be the version included in the set.
Turn off Lock to Version if you want the active version of the document to always be included in the
set.
In a related change, the datasource setting Use active version in flat sets has been renamed Lock flat
set documents to versions.
Editing the Version's Label When Creating a New Version
The Version field in the Document section of the New Document Version dialog is now editable when
creating a new version.
Previously, the new version was automatically assigned the label of the current active version and you
could not change it.
Now, you can either accept the label provided for the new version (this field is still pre-populated with
the label of the active version), or you can edit the label of the new version.
Note: The Version field in the New version section is used to reset the label for the active version.
ProjectWise
19
What's New?
Document and File Name Synchronization

A documents name and file name are often the same in ProjectWise, but the property fields themselves
have always been independent of each other. This allowed you to give the document a different name
than its attached file. While this has always been a flexibility of the system, there was no way to
automatically force these two properties to have the same value.
In this release, you can now lock the document name and file name properties together, so that
whatever you set for the document name is automatically set for the file name. This makes naming and
renaming documents and their attached files much easier.
The administrator can choose to enforce document name locking across the entire datasource, or they
can let document name locking be optional for each user. When document name locking is on, existing
documents will not be affected unless a user renames a document, renames the attached file, or replaces
the attached file. When document name locking is optional, users will be able to lock or unlock the two
properties through a check box on the following dialogs:
ProjectWise
Create Document dialog (Document > New > Document)

Advanced Document Create Wizard (Document > New > Advanced Wizard)
Document Properties dialog (Document > Properties)
Modify Document(s) dialog (Document > Modify)
Rename Document dialog (Document > Rename)
Copy To dialog (Document > Copy To)
20
What's New?
Move To dialog (DocumentMove To)
Integrated File > Save As dialogs
Integrated File > New dialogs
The Rename Document dialog with the new document name locking check box and lock icon. When you
place the cursor over the lock icon, the tool tip displays, Make document name and file name the same.
Note: The locking option that is available on each of these dialogs is not a document property, rather it
is a client setting that gets saved in the computers registry under the user you are logged in as. If you
turn the option off from one dialog, it will continue to be off for you in the next dialog above that you
open. When the administrator is enforcing document name locking at the datasource level, then this
locking option will be on, but disabled from changing.
Access Control Tab Enhancements
Simplified workflow for importing exported access control settings (option to merge or override
settings)
You can now export access control settings to a CSV (comma separated values) file, in addition to an
Excel file
New button on the Access Control tab lets you discard any pending changes you have made for the
selected project, folder, or document. (Previously you had to navigate to another project, folder, or
document (before applying changes) in order to discard changes.)
The display (or non-display) of the Access Control tab is now controllable by your administrator,
through new datasource and user settings
Point Cloud and Raster Reference Streaming
Point cloud streaming is new in this release. When point cloud streaming is enabled and the point cloud
file is copied out, only the portions of the point cloud file that are necessary to complete the current
view in MicroStation are downloaded from ProjectWise. Additional portions are downloaded as
necessary as you pan and zoom. When point cloud streaming is disabled, the entire file is downloaded.
ProjectWise
21
What's New?
Point cloud streaming only applies when the point cloud file is copied out; when the point cloud file is
checked out, the entire file is always downloaded.
Point cloud streaming requires MicroStation V8i (SELECTseries 3), and is enabled on a per-datasource
basis in ProjectWise Administrator through the new File Streaming datasource node.
Raster reference streaming is not new in this release, but the way in which it gets enabled has changed.
In previous versions, raster reference streaming was enabled through a configuration variable in the
mcm.cfg file called PW_RASTER_REFERENCEOUT. In this release, raster reference streaming is now
enabled in the new File Streaming datasource node in ProjectWise Administrator. Because of this
change, this setting and its related variables PW_RASTER_REFOUT_MIN_FILE_SIZE and
PW_RASTER_REFOUT_1BIT have been removed from mcm.cfg / mcm.user.cfg and are no longer
valid.
Project Creation Wizard - Storage Area Override
On the Project Creation Wizard there is now the option to override the storage area for subfolders when
creating a project from a template.
Detailed Logging for Reference Scanning
The Scan for Reference Files and Link Sets Wizard lets you save the results of the scan to a log file.
Below the field in which you specify the name and location of the log file, there is a new option called
Enable detailed logging. When this setting is off (the default), ProjectWise will record the normal level
of scanning details in the log file (that is, the same level of details recorded as in previous versions).
When this setting is on, more detailed logging will occur.
Citrix XenApp Support
ProjectWise Explorer can be configured to run in a Citrix XenApp environment. Instructions for setting
this up are in the ProjectWise Explorer Configuration section of the ProjectWise Implementation
Guide.
Note: For the ProjectWise V8i (SELECTseries 4) Refresh, Citrix XenApp 6.0 and 6.5 are supported.
Support for Latest Bentley Applications
This version of ProjectWise now provides support for the latest versions of these Bentley applications:
ProjectWise
MicroStation V8i (SELECTseries 3)

MicroStation PowerDraft V8i (SELECTseries 3)
Bentley View V8i (SELECTseries 3)
Bentley i-model Composer V8i (SELECTseries 4)
Bentley Navigator V8i (SELECTseries 4)
22
What's New?
Note:
In Bentley Navigator V8i (SELECTseries 4), Bentley i-model Composer V8i (SELECTseries 4), and
Bentley View V8i (SELECTseries 3), desktop integration is now enabled by default, and you only need to
modify the PW.CFG file delivered with those applications if you want to disable that integration. This is
a change from previous versions of those applications, where desktop integration was disabled by
default.
Support for Autodesk 2012 Applications
This version of ProjectWise now provides integration support for the 2012 editions of AutoCAD, its
verticals, and Revit. See the Requirements page of the ProjectWise readme for a list of supported
Autodesk applications and the specific versions supported.
Support for Office 2010 (Word, Excel, PowerPoint, Outlook)
This version of ProjectWise now provides integration support for 32-bit Microsoft Office 2010 (Word,
Excel, PowerPoint, and Outlook) on either 32-bit or 64-bit operating systems.
MicroStation Integration Enhancements
These are the MicroStation integration enhancements in this release.
New mcm.user.cfg File
Configuration variables that were formerly delivered in the mcm.cfg file are now delivered in a file
called mcm.user.cfg. The mcm.cfg file is still delivered, however it now only contains system setup
settings and should not be edited by the user. Both files are installed to the \ProjectWise\bin
folder.
No configuration is needed unless you want to change the default settings in the new mcm.user.cfg
file. If this is the case, place a copy of the new mcm.user.cfg file into your user profile and edit that
copy as needed. MicroStation integration will load the delivered mcm.user.cfg first, then it will load
the copy of mcm.user.cfg in your user profile, if one exists. Changes you make in your personal
mcm.user.cfg will override the default settings in the delivered mcm.user.cfg. This will also make
future upgrades easier, as the new installation will always deliver a fresh mcm.user.cfg file,
sometimes with new settings, without affecting the settings in your personal mcm.user.cfg file.
If you need to change default settings, create the following local folder and place a copy of
mcm.user.cfg in it:
Windows Vista/Windows 7
%LOCALAPPDATA%\Bentley\ProjectWise
\Configuration\
Windows XP
%APPDATA%\Bentley\ProjectWise\Configuration\
Administrators can create the following local folder and place a copy of mcm.user.cfg in it, to be used
by all users working on this computer:
ProjectWise
23
What's New?
Windows Vista/Windows 7
%ALLUSERSPROFILE%\Bentley\ProjectWise
\Configuration\
Windows XP
%ALLUSERSPROFILE%\Application Data\Bentley
\ProjectWise\Configuration\
Point Clouds Dialog Integration

ProjectWise provides integration with the File > Attach, File > Convert, and File > Export commands
in the Point Clouds dialog in MicroStation V8i (SELECTseries 3).
Mini Toolbar Integration Support
ProjectWise provides integration with the new Mini toolbar for callouts in MicroStation V8i
(SELECTseries 3). Specifically, there is integration with the tools on the toolbar which can open or
create (or save as) documents.
Revit Integration Enhancements
Support for Type Catalogs The Scan for References and Link Sets wizard in ProjectWise Explorer
can now scan a Revit family file (RFA) to see if it has a related Type Catalog file (same name as the
RFA file, but with TXT extension); if found, a set is created for the relationship.
Using decal images stored in ProjectWise In Revit 2012, the Source browse button on the Decal
Types dialog is now integrated with ProjectWise. This lets you select an image stored in ProjectWise
to use when creating a decal type. Note, the Bump Pattern and Cutouts options on this dialog are not
integrated with ProjectWise.
Using background images stored in ProjectWise In Revit 2011 or later, the Image browse button
on the Background Image dialog is now integrated with ProjectWise. This lets you select an image
stored in ProjectWise to use as the background image when rendering the open project in Revit.
Exporting the rendered image to ProjectWise Clicking the Export button in Revits Rendering
dialog once the image has been rendered lets you export the rendered image to ProjectWise.
New Disable ProjectWise Integration option You can temporarily disable Revits integration with
ProjectWise using the new Disable ProjectWise Integration button on the Bentley tab in Revit. This
provides a quick and easy way to suspend integration without actually uninstalling the feature. As
soon as you click the button, integration is disabled and the name of the button changes to Enable
ProjectWise Integration. When you are ready to restore integration, click Enable ProjectWise
Integration.

New Renditions Datasource Node for Bentley i-model Composition Server for PDF
In support of Bentley i-model Composition Server for PDF, a new datasource node called Renditions
has been added to ProjectWise Administrator. Under this datasource node the administrator will define
reusable rendition profile components which can then be applied to rendition jobs as needed. Batch
ProjectWise
24
What's New?
rendition jobs are created and run from Bentley i-model Composition Server Administrator (in
Orchestration Framework Administrator), while on-demand rendition jobs are run from ProjectWise
Explorer.
New File Streaming Datasource Node for Point Cloud and Raster Reference Streaming
The new File Streaming datasource node in ProjectWise Administrator is used to enable or disable the
streaming of point cloud files and/or raster reference files on copy out. When streaming is enabled, only
the portions of the file necessary to complete the view in MicroStation are downloaded when the
respective reference file is copied out. Additional portions are downloaded as necessary as the user
pans and zooms. When streaming is disabled, the entire reference file is downloaded when it is copied
out.
While point cloud streaming is new in this release, raster reference streaming is not only the way in
which it gets enabled has changed (in previous versions, raster reference streaming was enabled
through configuration variables in the user's mcm.cfg file).
Note: Point cloud streaming and raster reference streaming are licensed features that are enabled first
at the server level (through settings in the dmskrnl.cfg file), and then on a per-datasource basis
using the File Streaming datasource node.
New Trusted External Indexers Node for SharePoint Search Integration
The new Trusted External Indexers node in ProjectWise Administrator contains a list of SharePoint
installations that have sent a trust request to the ProjectWise Integration Server. Any SharePoint
installation that you grant trust to can then crawl all of the full text indexes for all of the datasources of
the ProjectWise Integration Server. This node displays after the last datasource in the list for any
ProjectWise Integration Server.
New Point Cloud Scanner
Under the Spatial Metadata Scanners datasource node there is a new scanner, the Point Cloud
Scanner, which is used to extract spatial locations from point cloud files (POD) in the datasource. When
using this scanner, it is recommended that you also enable point cloud streaming in ProjectWise
Administrator, through the new File Streaming datasource node.
Managed Workspace Export and Import
The existing ProjectWise Export and Import Wizards have been updated to include the ability to export
managed workspace configuration settings blocks and their related data from one datasource, and then
import those blocks and related data into another datasource. Entry points to these existing wizards
have also been added to the Managed Workspaces datasource node in ProjectWise Administrator. You
can also drag and drop managed workspace configuration settings blocks from one datasource to
another.
User and Group Management Enhancements
There is a new Owner Of tab in the User Properties and User List Properties dialogs, so you can see a
list of all the groups and/or user lists that the selected user or user list owns.
ProjectWise
25
What's New?
New Datasource Settings

These are the new datasource settings in this release:
ProjectWise
Grant implicit
'Change
Permissions' rights
to owners of
projects, folders,
and documents
When on (the default), an owner of a project, folder, or document always has

the ability to change and assign access control for the item, regardless of what
their current access control settings are for the item. When off, an owner of a
project, folder, or document does not have any extra control over the item,
beyond what their current access control settings are for the item.
Display Access
Control tab in
Preview Pane
This setting determines whether or not the Access Control tab can be displayed
in ProjectWise Explorer for this datasource. When on (the default), then the
Access Control tab is able to be displayed; actual display of the tab is then
controlled at the user level, through the (also new) related user setting. When
off, then the Access Control tab cannot be displayed in ProjectWise Explorer for
this datasource, regardless of how any individual user's user settings are
configured.
Force file name to

be the same as
document name
This new setting goes along with the new document name locking feature
available to users in ProjectWise Explorer. When this setting is on, then the
document name locking feature is not optional, and the document name and file
name properties are always locked together. Existing documents are not
affected until a user renames a document, renames the attached file, or replaces
the attached file. When this setting is off (the default), then document name
locking is optional for each user.
Lock flat set

documents to
versions
The existing setting Use active version in flat sets has been renamed Lock flat
set documents to versions and its default status is now OFF instead of ON.
This name and slight behavior change was made to be consistent with the new
Lock reference documents to versions setting. (In a related change, the
Always Use Active Version check box in the flat set contents window in
ProjectWise Explorer has been renamed Lock to Version.)
Lock reference
documents to
versions
When off (the default), the master document will always use the active version
of a reference. (Off is the previous behavior, before the datasource setting was
introduced.) When on, and the user attaches a reference to a master, the
reference is locked to the sequence number of the reference's active version.
This way, as new versions of the reference are created and the active version's
sequence number slides forward, the master document will always use a fixed
version of the reference (specifically, the version which now has the sequence
number that the active version had when the reference was originally attached).
Prompt user to
update master
document's
reference versions
on open
If on, and the user opens a master document that is using a version of a
reference that is not the active version, the Reference Version Manager dialog
opens in ProjectWise Explorer to prompt them to update the master document
to use the active version of that reference document. Only the reference
documents that are not the active version are displayed in the dialog. The user
can choose to update some, all, or none of the reference documents, and then
open the master document.
26
What's New?
New User Settings

These are the new user settings in this release:
Working Directory When Using
ProjectWise Explorer
- Node identifier
Used to define the node name that will be used when the user checks out
documents from ProjectWise Explorer. This setting was introduced to
provide flexibility for ProjectWise Explorer users working in a Citrix XenApp
environment, but actually applies to all ProjectWise Explorer users.
The Node identifier setting has three options:
Use the users host computer name or user name This option is
selected by default, and there are two values you can choose from:
$HOSTNAME$ or $USERNAME$. When $HOSTNAME$ is set, the users host
computer name will be recorded as the node name when the user checks
out documents from ProjectWise Explorer. This is the same behavior as in
previous versions, before the Node identifier setting was introduced.
When $USERNAME$ is set, the users user name will be recorded as the
node name when the user checks out documents from ProjectWise
Explorer. The $HOSTNAME$ value should not be used for ProjectWise
Explorer users who are using Citrix XenApp, but the $USERNAME$ value
can be used for any ProjectWise Explorer user, whether using Citrix
XenApp or not.
Use a global unique identifier (GUID) Use this option to generate a
random global unique identifier (GUID) to be used as the node name. This
option can be used for any ProjectWise Explorer user, whether using
Citrix XenApp or not.
Use a logical name Use this option to enter a logical name to be used
as the node name (for example, Bob's Computer). This option can be
used for any ProjectWise Explorer user, whether using Citrix XenApp or
not.
Administrative Display Access

Control tab in
Preview Pane
Used to control which users can see this tab. If this setting is on, and the
related datasource setting Miscellaneous - Display Access Control tab in
Preview Pane is also on, then the Access Control tab displays in the user's
Preview Pane. If either setting is off, then the Access Control tab will not
display in the user's Preview Pane.
New Audit Trail Logging Options

These are the new audit trail logging options in this release:
ProjectWise
Document - Log Revit

Worksharing Mode
Actions
If on, audit trail creates a record for each document action related to Revit
worksharing mode. To record document actions that are not unique to the
Revit workflow, such as creating or checking out a standalone Revit file, you
simply turn on the standard audit trail options related to those actions.
Document - Log
Document Pack
If on, audit trail creates a record for each document that is added to a
package, when a package is created using ProjectWise i-model Packager.
27
What's New?
Document - Log
Document Unpack
If on, audit trail creates a record for each package or mobile overlay file that
is unpacked using ProjectWise i-model Packager, and also for each new
document that is created as a result of being unpacked from a package or
mobile overlay file.
Updated Datasource Template

A new datasource template is now delivered with ProjectWise Admin Setups, and is a replacement for
the datasource template (pwtemplate.aam) that was delivered in previous releases. Building on the
basic idea of the former template, this new template includes more documents and more real-world
examples so you can test new and existing features with minimal extra configuration. To use the new
template, you must first install the template from ProjectWise Admin Setups. Once installed, run the
New Datasource Wizard in ProjectWise Administrator and load the new datasource template when
prompted.
ProjectWise Web Parts Enhancements

These are the Web Server / Web Parts enhancements in this release.
SharePoint Search Integration
ProjectWise now provides integration with SharePoint's search tool, which lets you search both
ProjectWise and SharePoint at the same time using the same SharePoint search tool. (Note for
administrators: setting up integrated search requires both ProjectWise Integration Server-side and
ProjectWise Web Server-side configuration.)
Marking Up i-models in the Navigator Web Part
You can now markup i-models in the Navigator web part. The markup is saved in a new
*.overlay.dgn file that references the i-model.
One-Click Document Viewing
You can now just click a documents link in the Name column in the Content web part and the document
opens for viewing in its associated application. If there is not an associated viewing application installed,
you are prompted to save the file locally. If you need to view document properties, click anywhere else
in the row, like in the documents Description or File Name field, and then select the option you need
from the Document menu or the right-click menu.
iPad / Safari Support
iPad users can now connect to ProjectWise Web Parts using their Safari browser.
User Account Lock Out, After Invalid Password Attempts
(this feature was new in the initial ProjectWise V8i (SELECTseries 4) release, but was previously
undocumented)
ProjectWise
28
What's New?
User accounts will now be automatically locked out after several incorrect password attempts. The
number of password attempts allowed, and how long the user will be locked out, are configurable in the
website's web.config file.
Bentley i-model Composition Server for PDF

Bentley i-model Composition Server for PDF is a flexible, scalable server-based system that lets you
publish renditions (PDF, JPEG, TIFF, and/or CALS) from documents stored in ProjectWise.
Administrators use the Bentley i-model Composition Server Administrator interface (inside
Orchestration Framework Administrator) to create, schedule, run, monitor, and review batch rendition
jobs, while ProjectWise Explorer users can publish renditions on-demand from selected documents, flat
sets, folders, or projects. Upon completion of the job, the new rendition documents are stored in
ProjectWise, and if selected an email notification is sent to the user who ran the job.
Bentley i-model Composition Server for PDF runs on top of ProjectWise Orchestration Framework
Service (which manages all the processes) and uses ProjectWise InterPlot Organizer to generate the
renditions. Also, a new datasource node called Renditions has been added to ProjectWise
Administrator, for the purpose of defining reusable rendition settings which can be applied whether
publishing renditions from Bentley i-model Composition Server Administrator or ProjectWise Explorer.
Bentley i-model Composition Server for PDF requires a Bentley i-model Composition Server license.
Note that this same license can also be used for the Bentley i-model Composition Server for i-model
extension to ProjectWise Automation Service that is used to publish i-models from DGN documents
stored in ProjectWise.
Note: This product was called ProjectWise Dynamic Composition Server for PDF for the initial
ProjectWise V8i (SELECTseries 4) release, and has been rebranded as Bentley i-model Composition
Server for PDF for the ProjectWise V8i (SELECTseries 4) Refresh.
ProjectWise Desktop and Server Applications for the Mobile Workflow

ProjectWise i-model Packager - ProjectWise i-model Packager gets installed on top of ProjectWise
Explorer, and is used to create packages to be used by ProjectWise Explorer Mobile users, to unpack
packages that were created by ProjectWise Explorer Mobile users, or to convert mobile markup files
created in Navigator Pano Review to overlay.dgn files.
ProjectWise web services - ProjectWise web services is the server that provides ProjectWise
Explorer Mobile users with a list of ProjectWise datasources they can connect to.
These are the infrastructure or otherwise uncategorized enhancements in this release.
Native 64-bit Servers
ProjectWise now delivers a native 64-bit ProjectWise Integration Server. There is no corresponding 32bit version.
Because ProjectWise Integration Server is now a native 64-bit application, you must now use the 64-bit
ODBC Data Source Administrator when creating a datasource, rather than the 32-bit ODBC Data Source
Administrator as in previous releases.
ProjectWise
29
What's New?
ProjectWise delivers both a 32-bit and a native 64-bit ProjectWise Caching Server and ProjectWise
Gateway Service.
SQL Server 2012 Support
ProjectWise now supports the use of SQL Server 2012 for both ProjectWise Integration Server and
ProjectWise Orchestration Framework Service databases.
New ProjectWise Integration Server Installation Options
There are two new options on the ProjectWise Integration Server installer in this release:
Component Services EC plugin server-side files required for using Bentley OpenPlant with this
server. Installing this feature creates a website in IIS called Component Services.
ProjectWise Indexing Connector for SharePoint server-side files required for the SharePoint
search integration feature of ProjectWise Web Server. Installing this feature creates a website in IIS
called ProjectWise Indexing Connector.
Installation Adds dmskrnl.exe to the Firewall Exception List
The dmskrnl.exe file is now automatically added to the local computers Firewall exception list
during installation of ProjectWise Integration Server (and also for ProjectWise Caching Server,
ProjectWise Gateway Service, and ProjectWise Indexing Service installations), therefore you no longer
need to manually add the individual ProjectWise broadcasting and listening ports (5799 and 5800, by
default) to the exception list.
Server-to-Server Routing
Server-to-server routing lets you set up a ProjectWise Gateway Service in a DMZ in order to route
connections from a ProjectWise Integration Server to a ProjectWise Caching Server, in cases where the
ProjectWise Integration Server cannot directly connect to the ProjectWise Caching Server. For example,
if the ProjectWise Caching Server is hosted behind a firewall of another organization. To configure this
feature, routing information is needed in the dmskrnl.cfg file of the ProjectWise Integration Server,
the ProjectWise Caching Server, and the connecting ProjectWise Gateway Service.
Server Settings for Point Cloud and Raster Reference Streaming
A new section was added to the dmskrnl.cfg file, Configurations for Caching Server Functionality,
to enable point cloud and raster reference streaming at the server level, and log usage of this licensed
feature to SELECTserver. After enabling settings here, you can then enable point cloud and raster
reference streaming on a per datasource basis, through the File Streaming datasource node in
ProjectWise Administrator.
When enabling streaming, you only need to configure the dmskrnl.cfg file of any ProjectWise
Integration Server or ProjectWise Caching Server that is hosting a storage area that contains point cloud
and/or raster reference data.
ProjectWise
30
What's New?
New [RenditionWebServices] Section for Bentley i-model Composition Server for PDF
A new [RenditionWebServices] section has been added to the dmskrnl.cfg in support of
creating renditions from ProjectWise Explorer.
Using ProjectWise User Synchronization Service as an Intermediate Login Provider
If your ProjectWise Integration Server cannot access the local domain controller and authenticate
Windows users, you can install ProjectWise User Synchronization Service on a local area network (LAN)
to act as an intermediate login provider for ProjectWise users with Windows accounts. In support of
this, a new setting has been added to the dmskrnl.cfg file, UserSyncService=, which lets you
specify the computer on which ProjectWise User Synchronization Service is installed. See the
ProjectWise Implementation Guide for details about setting this up.
Ability to Disable Audit Trail Truncation in Load-balanced Configurations
When running ProjectWise Integration Servers in a load-balanced configuration and using audit trail
truncation, only one of the servers should be performing the truncation, and all the other servers in the
cluster should have audit trail truncation disabled.
To disable audit trail truncation on a particular ProjectWise Integration Server, open that servers
dmskrnl.cfg file (C:\Program Files\Bentley\ProjectWise\Bin) and add the line
DisableAuditTruncation=1 at the end of the datasource settings section ([db0], [db1]) for each
datasource where audit trail truncation is needed.
FIPS Compliancy
All ProjectWise Integration Server modules now use FIPS 140-2 compliant cryptographic routines.
ProjectWise PDx Dynamic Review Service Changes
The ProjectWise PDx Dynamic Review Service extension of ProjectWise Automation Service requires a
matching version of ProjectWise PDx Project Server. Until such time that a matching release version is
made available, please do not try to implement ProjectWise PDx Dynamic Review Service.
Also note that the ProjectWise PDx Project Server admin component is no longer delivered with
ProjectWise Automation Service and ProjectWise Automation Service, but will go back to being
delivered with ProjectWise PDx Project Server V8i (SELECTseries 4), as it was for the original
ProjectWise V8i (SELECTseries 2) release.
Help Delivery Changes
ProjectWise Administrator now installs all the core ProjectWise help files, so you do not have to install
each application in order to get that applications help file.
Also, a new help wrapper file (ProjectWise.chm) is now delivered with ProjectWise Explorer and
ProjectWise Administrator. The help wrapper file looks in the same folder (\ProjectWise\help) for
a list of CHM help files. Any of those help files it finds, it loads. Searches run from the Search tab of the
help wrapper file will search across all of the loaded help files. Likewise, the Index tab pulls in the
ProjectWise
31
What's New?
indexes from all of the loaded help files. The help wrapper file opens whenever you select Help >
Contents inside the application, and also replaces the individual help entries on the Start menu.

3) (8.11.9.x).

New Access Control Tab in the Preview Pane, for Setting Document and Folder Security
The Access Control tab is a new tab on the Preview Pane, and is used to simplify the way security is set
on documents, folders, and projects. When this tab is active, you simply select any document, folder, or
project, and you can see instantly what access control security permissions are set for the object
(whether inherited, or explicitly set). Using this same tab, you can turn on or off permissions as needed,
or add or remove users as needed. You can also export the selected folder's or project's current security
settings to an Excel spreadsheet, modify them if necessary, and then import that spreadsheet to the
same or another folder or project. You can also copy security settings from one folder/project/
document to another.
This tab is the new recommended way to set permissions in ProjectWise Explorer, however the existing
Security tabs remain on the Document and Folder Properties dialogs, and you can still edit permissions
from those tabs if you prefer. Setting security permissions in the Access Control tab automatically
updates the permissions shown on the Security tabs, and vice versa.
Group and User List Management Enhancements

The membership of groups and user lists could previously only be managed from ProjectWise
Administrator. Groups and user lists can now also be managed from ProjectWise Explorer, using the
new User / Group Management dialog that opens when you select Tools > User Management.
ProjectWise
32
What's New?
Group / user list owner is also a new concept in this release, and is how the administrator controls who
can manage groups and user lists from ProjectWise Explorer. For a user to be able to manage the
membership of a particular group or user list in ProjectWise Explorer, they must already be designated
an owner of that group or user list before they log in. A user can be the owner of multiple groups or user
lists. Each group or user list can have multiple owners. A user list can also be designated as an owner of
a group or another user list.
The administrator (from ProjectWise Administrator) will typically designate one or more users to be
owners of particular groups or user lists. Those users can then manage the membership of the group or
user list from ProjectWise Explorer. In addition to managing membership, an owner has the power to
add more owners to the group or user list they own, and they can remove owners (including
themselves) from the group or user list they own.
MicroStation No Longer Required for Reference Scanning

MicroStation is no longer required on the ProjectWise Explorer computer for any reference or related
file scanning, or link set scanning, nor is it required any longer to rewrite paths in DGN documents on
folder export. Installing ProjectWise Explorer is now the only requirement for these features.
ProjectWise
33
What's New?
New Storage Area Disk Usage Information

You can now view storage area space information when creating a folder, or when viewing the
properties of a folder or project. To view this information, click the new Browse (...) button that exists to
the right of the Storage list on the Create Folder and Folder Properties dialogs. A dialog opens showing
you the amount of space the selected storage area currently occupies, and how much space is still
available.
Display of Nested References in the Dependency Viewer

The nest depth set inside the master document now determines the number of nested reference levels
that are displayed in the Dependencies tab by default. You can further reduce the number of nested
reference levels displayed in the Dependencies tab (Block Filter tab > Depth Filter), but you cannot
display more levels of nested references than the document itself is configured to display when open in
its native application.
ProjectWise
34
What's New?
64-bit Components Delivered for Integration with 64-bit Autodesk Products

When installing on a 64-bit operating system, the ProjectWise Explorer installer displays a feature
called, ProjectWise 64-bit components. This feature is delivered in support of iDesktop Integration
support of 64-bit Autodesk products. Note that ProjectWise Explorer itself is still a 32-bit application.
Integration Support for the Following Bentley Applications and Their Updated Versions
In addition to the integration support ProjectWise continues to provide for other Bentley applications
and versions, this version of ProjectWise now also provides support for these additional Bentley
applications and versions:
Integration Support for the Following 64-bit Autodesk Applications and Their Updated
Versions
This version of ProjectWise now provides integration support for these 64-bit Autodesk applications
and versions:
AutoCAD 2011, 2010

AutoCAD Architecture 2011, 2010
AutoCAD Civil 3D 2011
AutoCAD Map 3D 2011, 2010
AutoCAD MEP 2011, 2010
AutoCAD P&ID 2011, 2010
AutoCAD Raster Design 2011, 2010
Autodesk Revit Architecture 2011, 2010
Autodesk Revit Structure 2011, 2010
Autodesk Revit MEP 2011, 2010
Integration Support for the Following 32-bit Autodesk Applications and Their Updated
Versions
In addition to the integration support ProjectWise continues to provide for earlier 32-bit Autodesk
releases, this version of ProjectWise now also provides integration support for these additional 32-bit
Autodesk applications and versions:
ProjectWise
AutoCAD 2011
AutoCAD Architecture 2011
AutoCAD Civil 3D 2011
AutoCAD Map 3D 2011
35
What's New?
AutoCAD MEP 2011

AutoCAD P&ID 2011
AutoCAD Raster Design 2011
Autodesk Revit Architecture 2011
Autodesk Revit Structure 2011
Autodesk Revit MEP 2011

Restricted Administrators and Granular Security
There is now a way to let certain users manage certain datasource nodes in ProjectWise Administrator,
without adding them to the Administrator group and giving them full control over all datasource nodes
in ProjectWise Administrator. This is referred to as granular security.
Granular security lets you designate which datasource nodes a user is allowed to manage. But before the
user can manage any node, they must first be added to a new group called the Restricted Administrator
group. The Restricted Administrator group is created along with the main Administrator group when
the datasource is created. After datasource creation you can add users to the Restricted Administrator
group as needed.
Membership to the Restricted Administrator group allows a user to log in to the datasource in
ProjectWise Administrator. If you add a user to this group but do not give them access to any datasource
nodes, then all the nodes will be hidden when they log in in ProjectWise Administrator. So after adding a
user to the Restricted Administrator group, the next step is to specify which datasource nodes you want
to let that user manage. You can give any user in the Restricted Administrator group access to as many
or as few datasource nodes as necessary.
To set granular security, each datasource node (including the main datasource node itself) now has a
Granular Security tab on its Properties dialog.
ProjectWise
36
What's New?
Group and User List Management Enhancements

The same User / Group Management dialog for managing group and user list membership that is now
available in ProjectWise Explorer is also available in ProjectWise Administrator. You can either use this
new dialog, or you can continue to use the Properties dialog for individual users, groups, or user lists if
you prefer to use the old method of managing membership.
Group / user list owner is also a new concept in this release, and is how you control who can manage
groups and user lists from the User / Group Management dialog in ProjectWise Explorer. To assign
ownership from ProjectWise Administrator, you can either use the new User / Group Management
dialog, or you can use the new Owners tab that has been added to the respective Group Properties and
User List Properties dialogs. An owner can be a user or a user list, and groups and user lists can have
multiple owners. A user or user list does not need to be a member of the group to be an owner of it.
When working in ProjectWise Administrator, any member of the Administrator group can manage the
membership and ownership of any group or user list. If a user is a member of the Restricted
Administrator group with access to the Groups node, that user can manage the membership and
ownership of any group. And if a user is a member of the Restricted Administrator group with access to
the User Lists node, that user can manage the membership and ownership of any user list.
ProjectWise
37
What's New?
Audit Trail Enhancements

Audit Trail now has its own tab on the Datasource Properties dialog. Existing Audit Trail settings
from the Settings tab are now located here.
There are new logging options to record folder and document access control changes, with detailed
additional data and comments
There are new logging options to record group and user list membership changes
You can now set different truncation rules for each audit trail action types, rather than just one rule
for the entire audit trail.
Folder ID and storage area name are now added to deletion action records
New Datasource Statistics

Total size of documents being managed
Inactive users
Users that have never logged in
ProjectWise
38
What's New?
Last time database statistics were updated
New User Settings

Administrative - Enable group and user list ownership If on, the user can be made an owner of a
group or user list. This setting is for use with group and user list enhancements documented above.
Network - Enable file transfer connection sharing Allows a single connection to be used, for use
when multiple files are being transferred to or from the storage area server as part of the same
transaction, as initiated by a ProjectWise Explorer user.
When this setting is on (the default), then only one connection is opened and used to transfer all the
files being uploaded or downloaded in a given transaction. When this setting is off (which is how
ProjectWise has worked in previous releases), a new connection is opened to transfer each file in a
given transaction.
This setting is recommended and may greatly reduce the time required to perform multi-file
operations, such as when ProjectWise Explorer users upload many files as part of an initial import,
or when they check out a master document that has many references and/or many managed
ProjectWise
39
What's New?
workspace files associated to it. (Users who only check out one file at a time with no attachments will
probably not notice any performance benefits from this user setting.)
By default, when a folder or document with spatial data is copied, the spatial data is not copied along
with the folder or document. This new datasource settings category and its settings have been added to
let the administrator enable the copying of spatial data along with the copied folder or document.
Event System Enable folder copy server event notifications
Event System Enable document copy server event notifications
New Storage Area Disk Usage Information
You can now view storage area space information when viewing the properties of a storage area. To
view this information, open the properties of a storage area and select the Disk Usage tab. This tab
shows the amount of space the storage area currently occupies, and how much space is still available.
ProjectWise
40
What's New?

Native 64-bit ProjectWise Web Server and Web View Server The 64-bit ProjectWise Web Server
and Web View Server installer now installs a native 64-bit version of the server, in addition to the
32-bit version previously delivered. When you go to deploy the server, you will have the option of
launching either the 64-bit or the 32-bit deployment wizard, depending on whether you are
deploying to a 64-bit or a 32-bit IIS web site.
New Web Parts log in page, for ProjectWise Web Server or ProjectWise Web View Server
deployments on a standalone IIS web site.
Delivered with ProjectWise Web Server is a new ProjectWise Navigator web part, which is used to
view packaged i-models accessed from the Content web part. Users connecting to a web site where
the ProjectWise Web Server and the ProjectWise Navigator Web Part have been deployed will be
prompted to install the necessary Bentley DGN ActiveX Control that displays the packaged i-model
inside the ProjectWise Navigator web part. The controls in the ProjectWise Navigator web part are a
subset of those found in the Bentley Navigator desktop application. Help about using the ProjectWise
Navigator web part is included in the ProjectWise Web Parts help.
Upgradable installers The installers for ProjectWise Explorer, ProjectWise Administrator,
ProjectWise Caching Server, and ProjectWise Gateway Service can now automatically upgrade an
existing installation of the product (ProjectWise V8i or later) to ProjectWise V8i (SELECTseries 3).
ProjectWise
41
What's New?
New DMSCONV switches, including a new password switch (username and password now have their
own switches)
A new ORDER attribute allows you to control the evaluation order of ALLOW / DENY access control
lists (ACLs) in the dmskrnl.cfg file. Using the ORDER attribute, you can allow access to a large group
of clients, and then deny access to a smaller set of clients. If you omit the ORDER attribute,
ProjectWise will evaluate the ALLOW and DENY entries as it always has, by treating ALLOW entries
as exceptions to DENY rules.
ProjectWise Explorer and Administrator support for installation on 64-bit Windows XP SP2
Integration support for Autodesk Revit is now delivered with ProjectWise Explorer V8i
(SELECTseries 3), as an iDesktop Integration option on the ProjectWise Explorer installer. The
administrative and server features of Revit integration have been merged into the ProjectWise
Administrator and ProjectWise Integration Server installers, respectively.
The admin component that used to be delivered with ProjectWise PDx Project Server is now
delivered with both Automation Service and Automation Service Administrator, and it has been
removed from ProjectWise PDx Project Server altogether. NOTE: This change has been reverted for
ProjectWise V8i (SELECTseries 4).
Improved performance when ProjectWise Explorer users in geographically distributed teams are
working over high-latency connections
Classless Inter-domain Routing (CIDR) support
ProjectWise Explorer and ProjectWise Administrator no longer store any local user configurations in
a local PWV8.BRG file. This information will now be stored in the local Windows Registry.

2) (8.11.7.4xx).
ProjectWise Dependency Service

ProjectWise Dependency Service lets ProjectWise Explorer users see instantly how documents are
connected to each other by examining the existing dependencies among logical reference sets, link sets,
and flat document sets in your datasources, using the new Dependency Viewer tab in the Preview Pane
in ProjectWise Explorer. You can leave the Dependency Viewer docked in the Preview Pane, or you can
un-dock the Dependency Viewer to become a floating, resizable window, independent of the
ProjectWise Explorer application window.
Important: The ProjectWise Dependency Service authoring capabilities and ProjectWise Dependency
Service Administrator introduced in ProjectWise V8i (SELECTseries 2) are no longer available in
ProjectWise V8i (SELECTseries 4) Refresh.
ProjectWise PDx Dynamic Review Service

ProjectWise PDx Dynamic Review Service is an new extension to ProjectWise Automation Service that
lets you create jobs that:
publish individual i-models for each file in a particular PDS project database
create a single packaged i-model from all the files in a particular PDS project database
convert the original PDS files into V8 DGN files
ProjectWise
42
What's New?
ProjectWise PDx Dynamic Review Service jobs are configured in, and can be scheduled from
ProjectWise Automation Service Administrator. All of the new documents created by your ProjectWise
PDx Dynamic Review Service jobs will automatically get stored in ProjectWise, in the folder you specify
in the job definition.
ProjectWise PDx Dynamic Review Service leverages ProjectWise PDx Project Server (formerly Bentley
OpenPlant PDx Manager) and also MicroStation.
ProjectWise PDx Project Server, which is also delivered with ProjectWise Server Setups, is used to
create PDx projects (one for each PDS project database). PDx projects provide read-only access to the
files in the corresponding PDS project database. The PDx projects you create can then be used as the
input set for the ProjectWise PDx Dynamic Review Service jobs you configure in ProjectWise
Automation Service Administrator. MicroStation's engine is used to do the actual publishing of models
and conversion of the original PDS files into V8 DGN files.
Note: ProjectWise PDx Dynamic Review Service does not require a license, but you do need a license to
use ProjectWise PDx Project Server.
Dynamic Composition Service Enhancement

Dynamic Composition Service jobs can now publish i-models from AutoCAD 2010 format DWG
documents.

There is a new Select View option available when you right-click in the document list in ProjectWise
Explorer. This same option is also available when you right-click in the document list that appears in
document selection dialogs in integrated applications.
There is a new View menu on the Define Search (Search Builder) dialog, which is used to set the
view to be applied to the search results list for the current search only. If you do not specify a view
on the Define Search dialog, then whatever is set as the default view for the search results list will be
used instead.
You can now send a link to a flat document set by selecting the set and then selecting Send To > Mail
Recipient As Link.
Integration Support for the Following Applications and Their Updated Versions
ProjectWise

AutoCAD 2010 (32-bit) (Update2)
43
What's New?
Managed Workspace Performance Improvement

The time it takes to validate a managed workspace when opening a document, when the workspace is
already copied out, has been significantly reduced.
Spatial Integration Enhancements

This release offers some spatial enhancements in both ProjectWise Administrator and ProjectWise
Explorer.
Background Map Setup Assistant
This new assistant in ProjectWise Administrator is used to help in the process of background map
creation. It is not a replacement of the entire background map creation process, but a tool to quickly and
easily create a background map.
Local Coordinate System Support
It is now possible to create a local coordinate system in ProjectWise Administrator. This type of
coordinate system is designed for use in campuses where data is always stored in local coordinates.
Multiple local coordinate systems can be used in the same datasource (for example: terminal 1, terminal
2). It is also possible to use a mix of local coordinate systems and coordinate systems from dictionary in
the same coordinate system.
Note that when working with this type of coordinate system, no re-projection to a Geographical
Coordinate System is possible. When performing spatial searches, only the documents with the same
local coordinate system as the background map used to perform the search will be part of the search
results. For example, if the background map Terminal1 is used to perform the spatial search, only the
documents with a spatial location that uses the same coordinate system as this background map will be
found by the search.
Spatial Views Dialog Enhancements
The Spatial View Editor dialog in ProjectWise Explorer has been improved (now accessible from the
new Manage Spatial Views dialog (View > Manage Spatial Views), and it is now possible to create spatial
views with thematic symbolization from ProjectWise Administrator.

ProjectWise Publishing Server V8i (SELECTseries 2) support
SharePoint 2010 support
ProjectWise Web Parts users with non-Windows-based ProjectWise user accounts (logical users)
can now change their passwords from ProjectWise Web Parts, on standalone (non-SharePoint)
websites
ProjectWise
44
What's New?
Support for Microsoft SQL Server 2008 R2, for both Integration Server and Orchestration
Framework databases
MicroStation V8i (SELECTseries 2) can now be installed for use with Full Text Indexing, to extract
text from AutoCAD 2010 format DWG documents.
AutoCAD 2010 no longer needs to be installed, to extract thumbnail images from AutoCAD 2010
format DWG documents.
MSG iFilter no longer needs to be installed, to extract file properties from Microsoft Outlooks
message (MSG) documents.

1) (8.11.7.1xx).

Extracting Spatial Locations from DGNs in Which the Geographic Coordinate System Has
Been Assigned Using Placemarks
ProjectWise Explorer now delivers a MicroStation VBA macro that enables you to extract the spatial
location from DGN documents (for example, Building Information Model (BIM) documents) in which the
geographic coordinate system has been assigned using placemarks. The VBA macro is called from the
Spatial Location Scanning Tool (Tools > Scan Spatial Location) in ProjectWise Explorer.
The VBA macro ( DgnTransformExtract.mvba ) can be found in the
...\ProjectWise\bin\v811 folder after installation, and can be customized if needed. For
example, you may decide to generate spatial locations in latitude and longitude, but also in another
geographic coordinate system. The VBA macro can also be easily modified to get a specific polygon
rather than the model footprint. For example, if the BIM is the model of a building that has a U or a L
shape, the spatial location could be a U or L shape rather than the extent of the DGN model.
New Thumbnails View for the Document List
There is a new option, View > Thumbnails, which changes the icons in the document list to display
thumbnail images for all the documents in the selected folder. If there is no thumbnail image for a
particular document, then a default image displays in its place.
Tip:
You can also add a Thumbnails icon to the Standard toolbar (using Tools > Customize). Clicking the
Thumbnails icon in the Standard toolbar is the same as selecting View > Thumbnails.
ProjectWise
45
What's New?
Tip:
The Thumbnails view is also available wherever the document list appears in a document selection
dialog, including those in integrated applications.
Tip:
The thumbnails that display in the document list are the same as the thumbnails that display on the
Document Properties tab of the Preview Pane in ProjectWise Explorer, and are generated by your
administrator, using ProjectWise Integration Servers Thumbnail Extractor.
Improved Handling of Office Documents in Photo Preview
The way that Office documents are displayed in the Photo Preview tab of the Preview Pane has been
enhanced. When you select an Office document and then select the Photo Preview tab, a read-only view
of the document is displayed (you can no longer manipulate the text as you could previously in the
Photo Preview tab), and also the controls of the selected documents editing application are no longer
displayed inside the tab.
New Document Permission: Free
ProjectWise lets you free documents you have checked out or exported, when your user setting
Document - Free is on. This is not new and has not changed. However, there is a new document
permission called Free, which can be set at the project, folder, or document level. This permission lets
administrators decide on a project-by-project basis which users can free which documents that are
checked out or exported by other users.
Note the following when working with the new Free permission:
In order to free a document that is checked out or exported to another user, you must have the Free
permission turned on for that particular document, and your user setting Document - Free must also
be on.
In order to free your own checked out or exported documents, you do not need the Free permission
to be on for those documents, you only need your user setting Document - Free to be on.
New Document Permission: Change Workflow State
ProjectWise gives you the general ability to change the workflow state of documents when your user
setting Document - Change State is on. This is not new and has not changed. However, there is a new
document permission called Change Workflow State, that can be set at the project, folder, or document
level. This permission lets administrators decide on a project-by-project basis which users can change
the states of which documents.
Note the following when working with the new Change Workflow State permission:
In order to change the workflow state of a document, you must have the Change Workflow State
permission turned on for that particular document, and your user setting Document - Change State
must also be on.
In order to set final status on a document, you must have the Change Workflow State permission
turned on for that particular document, and your user Document - Set Final Status must also be on.
ProjectWise
46
What's New?
In order to remove final status on a document, you must have the Change Workflow State permission
turned on for that particular document, and your user setting Document - Remove Final Status must
also be on.
Improved Handling of Versioned Documents in Flat Sets
When you add a document to a flat set, you can now specify whether the set is always going to include
the active version of that document (if additional versions of that document are created after the
original document is added to the set), or whether the set is always going to include the version of the
document that was active at the time it was added to the set. To control this, a column with a check box
called Always Use Active Version has been added to the Set Contents window. For each document you
add to a flat set, simply turn the Always Use Active Version check box on or off as necessary to control
which version of the document you want included in the set. (Administrators can control the default
status of this check box through a new datasource setting under the Versions category called, Use active
version in flat sets.)
Note the following when adding documents to flat sets:
The Always Use Active Version check box will be enabled if you add a document that has no versions,
or if you add the active version of a document.
If the Always Use Active Version check box is enabled, the check box will be on or off depending on
how your administrator has configured it.
The Always Use Active Version check box will automatically be disabled (and off) if you add an
inactive version of a document.
Whenever you have a document for which the Always Use Active Version check box is enabled and
off, the check box automatically becomes disabled then the next time you create a version of that
document. This is because the version of the document included in the set (which was formerly
either a document with no versions, or the active version) is now an inactive version.
Markup Replaces the Term Redline
With support for Bentley Navigator and the new workflow for marking up DGN and DWG documents,
you will notice that the term Redline has been replaced with the term Markup throughout the interface.
Reference Scanning Enhancements
The reference scanning wizard (Tools > Scan for References and Link Sets) can now also be used to:
create a set from newly imported shapefiles (SHP) and their related files.
create a set from newly imported raster files and their related file(s).
To perform shapefile scans, no additional software or application integration is required beyond the
installation of ProjectWise Explorer itself. To perform scans on raster files and their related files, you
need a valid DGN scanning engine installed.
Actions That Affect Shapefiles Also Affect Their Related Files
After a set is created in ProjectWise for a shapefile and its related files, or for a raster file and its related
files, then whenever you perform an action on the main file of the set, the same action is performed on
its related files. Actions that affect shapefiles and their related files (or raster files and their related files)
include: check out, copy out, purge, export, delete, free, version, copy, move, and rename.
ProjectWise
47
What's New?
RealDWG 2010 Libraries for DWG Reference Scanning

RealDWG 2010 libraries are now delivered with ProjectWise Explorer, for DWG reference scanning,
export, attribute bulk update, and title blocks.
ProjectWise QuickView Is No Longer Delivered
ProjectWise QuickView uses third-party software that Bentley Systems is no longer under agreement to
redistribute after October 30, 2009, therefore starting with ProjectWise V8i (SELECTseries 1),
ProjectWise QuickView will no longer be delivered with ProjectWise Explorer.
Users who are currently using ProjectWise QuickView from an earlier version of ProjectWise Explorer
can continue to use it, however be aware that ProjectWise QuickView will be removed from all versions
of ProjectWise Explorer that are currently posted on the Bentley SELECT Downloads page.
We apologize for any inconvenience, however we do not expect this to be a major impact on your dayto-day operations in ProjectWise Explorer, as there are many free file viewer applications available for
download from the Internet. For your convenience, we have provided a page on the Be Communities
website that has links to many common file viewers
http://communities.bentley.com/products/projectwise/content_management/w/wiki/5538.aspx
Integration Support Added for the Following Applications and Their Versions

AutoCAD 2010 (32-bit only)
Microsoft Office 2007 SP2

ProjectWise V8i included support for MicroStation V8i's new Print Organizer dialog, however you
could only run .PSET print jobs from MicroStation. ProjectWise V8i (SELECTseries 1) extends the
support of Print Organizer, so that you can now run .PSET print jobs from ProjectWise Explorer.
Support for shapefiles as references ESRI shapefiles can now be attached as vector references, in
integrated MicroStation V8i (SELECTseries 1).
When you are in integrated MicroStation V8i (SELECTseries 1) and you attach a shapefile to your
DGN, ProjectWise will create two sets one for the relationship between the master DGN and the
attached shapefile, and one for the relationship between the shapefile and its own related files.
Similarly, when you attach a raster file to your DGN, and that raster file has its own related files
(whether a world file or some other file(s)), ProjectWise again will create two sets one for the
ProjectWise
48
What's New?
relationship between the master DGN and the attached raster file, and one for the relationship
between the raster file and its own related file(s).
ProjectWise supports the dynamic views enhancements of MicroStation V8i (SELECTseries 1), which
allow for the automated creation of new drawing models, sheet models, saved views, or references
from a portion of an existing document. Integration with ProjectWise allows those new models to be
stored inside ProjectWise. Specifically, the new model, saved view, or reference can be stored inside
the same document, inside some other existing document, or inside a new document altogether.
The document list in File-Open dialogs can now be filtered by file extension.
In managed workspaces, a new level called Predefined is added to the top of the processing order for
configuration settings blocks. This level gives users the ability to set predefined variables in
MicroStation managed workspaces. Variables assigned to the Predefined level will be processed
before the MicroStation local configuration is gathered.
ProjectWise Navigator Integration Enhancements
Along with general integration with ProjectWise Navigator V8i (SELECTseries 1), ProjectWise supports
ProjectWise Navigator's new workflow for marking up DGN and DWG documents. When you select to
markup a DGN or DWG document, ProjectWise Navigator now creates an overlay document (with the
file extension .overlay.dgn) to contain the markup. The original document you selected to markup is
now called the reviewed document. Also, instead of prompting you to add the new overlay document to
ProjectWise as soon as the document opens in ProjectWise Navigator, ProjectWise Navigator simply
creates and opens the overlay document, allowing you to markup the document first, and then save it to
ProjectWise using File > Save As when you are ready.
ProjectWise Navigator is not delivered with the ProjectWise Client Setups, it is a separate download.
When you launch ProjectWise Navigator from the desktop, integration with ProjectWise Explorer is
turned off by default. To turn on desktop integration, you need to modify the PW.CFG file delivered with
ProjectWise Navigator.
The ProjectWise Passport you have for ProjectWise Explorer will automatically work for your
installation of ProjectWise Navigator.
Note: ProjectWise Navigator is now called Bentley Navigator . In Bentley Navigator V8i
(SELECTseries 4), desktop integration is now enabled by default, and you only need to modify the
PW.CFG file if you want to disable that integration.
New command, ProjectWise > Place On Sheet (DMSPLACEONSHEET)
There is a new DMSSET variable called SHOWMISSINGSHAPES, which is used to control what action
integrated AutoCAD takes when you open a document that has missing SHX files.
There is a new DMSSET variable called SHEETSETMODE, which is used to control whether or not
AutoCAD Sheet Set functionality is integrated with ProjectWise.
ProjectWise now provides integration with AutoCAD's File > eTransmit feature, which lets you
package the current DWG file and its related dependent files (such as external references and font
files) inside a single ZIP file, and store it in the datasource. You can turn the integration for this
feature on or off through the new DMSSET variable called ETRANSMITMODE
There is now a Recent Documents / Most Used Documents view in ProjectWise Session File Manager.
When the Recent Documents view is active, a thumbnail image is displayed for each of the
ProjectWise
49
What's New?
ProjectWise documents you have had open from the current and previous sessions of integrated
AutoCAD. If you then switch to the Most Used Documents view, then the documents are rearranged
to list the most recently used documents in the order they are most frequently used. As the list
grows, you can clear the Recent Documents / Most Used Documents view as needed.
Reorganization and renaming of some items on the ProjectWise menu
In integrated AutoCAD 2010, there is a ProjectWise tab on the AutoCAD ribbon bar.

New Datasource Setting: Use Active Version in Flat Sets
This datasource setting controls the default status of the new Always Use Active Version check box that
now appears in the Set Contents window in ProjectWise Explorer, whenever a document is added to a
flat document set. When this datasource setting is on, the check box in ProjectWise Explorer will be on
by default when a document that has no versions, or the active version itself, is added to a flat document
set. When this setting is off, the check box in ProjectWise Explorer will be off by default.
New User Setting: Working directory - When Accessing ProjectWise Over the Web
There is a new user setting under the Working directory category for users who are accessing
ProjectWise over the web through ProjectWise Web Server or ProjectWise Web View Server. This
means that each user can now potentially have two working directories set for them: one for when they
are using ProjectWise Explorer, and one for when they are using ProjectWise Web Parts. Thus the
Working directory category is now organized as follows:
Working directory
When using ProjectWise Explorer
(folder icon, used to set the location of the user's ProjectWise Explorer working directory)
When accessing ProjectWise over the web
(folder icon, used to set the location of the user's ProjectWise Web Parts working directory)
The default location for the Web Parts working directory is: %LocalAppData%\ProjectWise
\WebWorkDir\%Datasource%
New Full Text Indexing Setting: Skip Schedule for Document Property Indexing
This setting appears on the General tab of the Full Text Indexing Properties dialog.
When text indexing is enabled and this setting is off, text extractions will run according to the defined
schedule. This is the default behavior, and this is how text indexing has worked in general, prior to the
introduction of this setting.
When text indexing is enabled and this setting is on, text extractions for file contents will still run
according to the schedule, however text extractions for document properties will run according to the
setting, Retry extraction in (minutes). For example, if your text extractions are normally set to retry
every 30 minutes, then every 30 minutes the text indexing processor will search for new documents to
ProjectWise
50
What's New?
extract document property text from, even during periods when the text indexing processor is
scheduled to be sleeping.
Tip:
Whether this setting is on or off, text extractions for file contents will always run according to the
defined schedule.

There is now a single installer for ProjectWise Web Server and Web View Server (requires Windows
Installer 4.5). Once you install ProjectWise Web Server and Web View Server, you can choose which
server you want to deploy (ProjectWise Web Server or ProjectWise Web View Server) using one of
the two deployment wizards (ProjectWise Web Server Deployment Wizard or ProjectWise Web View
Server Deployment Wizard).
Simplified deployment, when deploying to non-SharePoint websites.
Support for installation on 32-bit and 64-bit Windows Server 2003.
Support for installation on 64-bit Windows Server 2008.
Support for deployment to 32-bit SharePoint on 32-bit Windows Server 2003.
Support for deployment to 64-bit SharePoint on 64-bit Windows Server 2003 and 2008.
Support for deployment to 32-bit non-SharePoint websites on 32-bit Windows Server 2003.
Support for deployment to 32- and 64-bit non-SharePoint websites on 64-bit Windows Server 2003
and 2008.
Support for Windows SharePoint Services 3.0 SP2 and Microsoft Office SharePoint Server 2007 SP2.
ProjectWise Explorer is no longer a prerequisite of ProjectWise Web Server and Web View Server.
ProjectWise Web Server and Web View Server supports ProjectWise Publishing Server whether it is
set to Run as Web Server Extension or not.
Site/Zone locking security added for ProjectWise Web Parts ActiveX control.
The working directory for each web parts user can now be preset from user settings in ProjectWise
Administrator.
The Content web part has the following new Folder menu options: Upload, Copy Out, Purge Copies,
Export, Import, Download.
You can now create new versions of documents from the Content web part.
You can now set the active environment interface through the Interface toolbar in the Content web
part, so that when you view the properties of a document in the Properties web part, the
Environment section of the General tab is filtered to display only the attributes of the active
interface, instead of the entire environment.
You can now specify an interface in the Search web part, which limits the attributes you can search
on to those in the specified environment interface.
You can now assign document code to documents in the Content web part.
Documents selected in Content web part are automatically highlighted in Spatial web part, and vice
versa.
Paging controls have been added for the Navigation web part. Default page size for folders, projects,
or components in the Navigation web part is 100 items. The page size setting is configured through
the web.config file.
There is a new timeout setting in the ecom.config file called PublishingTimeout, which allows
more time for workspaces to be loaded when viewing or marking up DGN documents (in the
ProjectWise
51
What's New?
Publishing and Markup web part) that have large workspaces associated to them. The default value
is 300 seconds.
For non-SharePoint deployments, the sample page now remembers the last used datasource by
default. If you are using single sign-on, this means you will be automatically logged in to the same
datasource using single sign-on the next time you visit the site. If you are not using single sign-on,
then the last used datasource and username are remembered the next time you visit the site, and you
will only have to enter your password. This feature can be disabled by editing the delivered
web.config file.
Internet Explorer 8 support, for ProjectWise Web Parts users.
ProjectWise Automation Service Enhancements

These are the ProjectWise Automation Service enhancements in this release.
Dynamic Composition Service
A new extension, called Dynamic Composition Service, is now delivered with Automation Service. This
extension lets you create Automation Service jobs that publish models from DGN and DWG data, and
supports publishing application data coming from MicroStation DGN, AutoCAD DWG, AutoPLANT V8i
(PDW and P&ID), AutoPLANT XM Edition (PDW and P&ID), Bentley ProSteel V8i, Bentley ProSteel XM,
Bentley PlantSpace Design Series (3D), Bentley Structural V8i, and Bentley OpenPlant P&ID. Dynamic
Composition Service requires a license.
Note: In ProjectWise V8i (SELECTseries 4) Refresh, the Dynamic Composition Service extension is now
called Bentley i-model Composition Server for i-model.
Locate Document Feature
There is a new Locate Document feature available from the Job Monitor window. Simply right-click a
document in the Job Monitor and select Locate Document, and ProjectWise, ProjectWise Explorer opens
directly to the selected source document's folder and highlights the document.
The Locate Document feature is also available when you open a job's HTML history file from the
Automation Service's working directory's \history folder.
ProjectWise Distribution Service Enhancements

You can now define parameters for how renditions will be named when they get created.
You now have the option to set whether you want files to be overwritten in the target folder (for
example, if you have already run the job once and you just want to overwrite the files that are
already there), or if you want to create versions for those files.
When mirroring the source directory, descriptions from the source folder are now copied over to the
target folder.
There is a new Locate Document feature available from the Job Monitor (Details tab) and Job
History windows. Simply right-click a document in either of these windows and select Locate
Document. ProjectWise Explorer opens (if not already open) directly to the selected source
document's folder and highlights the document.
ProjectWise
52
What's New?
Full Internet Protocol Version 6 (IPv6) Support
ProjectWise now fully supports Internet Protocol Version 6 (IPv6), with the following considerations.
To run ProjectWise V8i (SELECTseries 1) on IPv6:
You must have a fully-configured IPv6 DNS server.
All ProjectWise V8i (SELECTseries 1) clients and servers must be part of the IPv6 network.
All ProjectWise V8i (SELECTseries 1) clients must be configured to use IPv6, by enabling the IPv6
settings on the ProjectWise V8i Network Configuration Settings dialog.
All ProjectWise V8i (SELECTseries 1) servers must be configured to use IPv6, by enabling the IPv6
settings in the dmskrnl.cfg file.
Caution:
It is highly recommended that you contact Bentley Professional Services to assist you in setting up
ProjectWise V8i (SELECTseries 1) on IPv6.
Windows Server 2008 (SP2 and R2) Support (64-bit)
All of the ProjectWise server, admin, and client modules are now supported on 64-bit Windows Server
2008 (SP2 and R2).
Windows 7 Support (32-bit and 64-bit)
ProjectWise Administrator and ProjectWise Explorer are now supported on the 32-bit and 64-bit
versions of Windows 7.
SQL Server 2008, SP1 Support
ProjectWise now supports SQL Server 2008 SP1, Standard / Enterprise Edition, for the ProjectWise
Integration Server database.
ProjectWise now supports SQL Server 2008 SP1, Standard / Enterprise Edition OR Express Edition, for
the ProjectWise Orchestration Framework Service database.
SQL Server 2008 SP1, Express Edition is now delivered with ProjectWise Server Setups (in place of SQL
Server 2005 Express Edition).
New Search-related Feature, Cancelable Queries
There is a new feature of the Integration Server called cancelable queries. This feature controls the
number of items that may be returned in one search, and how long a search will be allowed to run
before the search stops. When a search times out, the results gathered up to that point are returned to
the user. The default number of items returned is 1024, and the default timeout setting is 30 seconds. By
ProjectWise
53
What's New?
New in ProjectWise V8i
default this feature is enabled, however using settings in the Integration Server's dmskrnl.cfg file, you
can disable the feature (DisableCancelableQueries, raise the maximum number of items that can
be returned (CancelableQueriesItemCount, or extend the timeout setting
(cancelableQueriesTimeout).
New [ServerNameResolution] Section in dmskrnl.cfg
This new section is used by the Integration Server, when a client requests a connection to a name or
address that does, in fact, describe the current server, but due to network configurations the current
server is unable to realize/determine that it is the target of the request.
Simplified Language Pack Installation
There is now just one ProjectWise language pack for all of ProjectWise, instead of a separate language
pack for each module.
Auto-install Script for Database, Server, and Clients
Delivered with ProjectWise Server Setups is a batch file called autoinstall.bat, which contains scripts for
automatically:
Installing SQL Server Express Edition

Creating the database inside SQL Server
Creating the ODBC connection to the database
Installing ProjectWise Integration Server, Administrator, and Explorer
The instructions for running the batch file and modifying the scripts if necessary are located inside the
file itself.

The following are the new features and updates that were introduced in ProjectWise V8i (8.11.5.x).

Quick Search, and the New Search Toolbar
To consolidate new and existing search tools, the Search toolbar was added to ProjectWise Explorer
(View > Toolbar > Search), and also to document selection dialogs in integrated applications.
From this toolbar users can either launch one of the existing search dialogs (Search by Form or Define
Search, now classified as Advanced Search options) to create, run and if necessary save their search, or
they can use the new Quick Search field. Quick Search is a Google-like search field that lets users
simply type the text they want to search by and click Start search. The search returns all of the
documents, projects, and folders that meet the search criteria. Quick searches are not case sensitive, and
the Quick Search field stores the most recently used searches for quick access.
ProjectWise
54
What's New?
Photo Preview
The new Photo Preview tab in the Preview Pane is designed to let you preview image documents
(particularly digital photographs) in ProjectWise Explorer without having to open a new window. When
you select an image document in the document list and then select the Photo Preview tab in the Preview
Pane, a copy of the document is downloaded to your working directory, and a preview of the image
displays in the Photo Preview tab.
ProjectWise Network Configuration Settings Dialog Now Also Opens from ProjectWise
Explorer
The new menu item in ProjectWise Explorer, Tools > Network Configuration Settings opens the
ProjectWise Network Configuration Settings dialog. This dialog, which still can also be opened from the
Control Panel, is used to set which ProjectWise servers your ProjectWise Explorer can connect to, and is
also used to configure the new auto-login settings for integrated applications.
More Ways To Open the Reference Scanning Wizard
You can now open the Scan for References and Link Sets wizard by:
selecting Folder > Scan References and Link Sets (new)

selecting Document > Set > Scan References and Link Sets (new)
selecting Tools > Scan References and Link Sets (existing)
right-clicking selected folders/projects and selecting Scan References and Link Sets (new)
right-clicking selected documents and selecting Set > Scan References and Link Sets (new)
When you have documents and/or folders/projects selected and you use any one of the new entry
points to open the wizard, the paths of selected documents and/or folders/projects are automatically
added to the Select master files and folders page of the wizard.
Local Document Organizer Enhancement
In previous versions, turning on the user setting, Show Local Document Organizer on log out, made the
Local Document Organizer open (if you had documents checked out or exported) when you logged out
of a datasource, whether you were in ProjectWise Explorer or an integrated application. Now this user
setting has three options: you can set it so that the Local Document Organizer never opens on log out,
opens on log out whether you are in ProjectWise Explorer or an integrated application, or only opens on
log out when you are in ProjectWise Explorer.
Cut, Copy, Paste
New Cut, Copy, and Paste options have been added to the Document menu in ProjectWise Explorer. Use
Document > Cut (or <ctrl+X>) and Document > Paste (or <ctrl+V>) together, to move the selected
document(s) from one folder to another. Use Document > Copy (or <ctrl+C>) and Document > Paste (or
<ctrl+V>) together, to create copies of the selected document(s) in the existing folder or in another
folder.
ProjectWise
55
What's New?
To differentiate from the existing Copy command in ProjectWise Explorer, the existing Document >
Copy command has been renamed Document > Copy To. Because of this change, the existing Document
> Move command has been renamed Document > Move To.
Back and Forward Navigation Buttons
New back and forward navigation buttons let you jump quickly back and forth between previously
selected items in the datasource.
File Transfer Operations Can Now Be Cancelled Through the Progress Bar
There is a new user setting called User Interface - Show progress indicator during file transfers, which
controls whether or not the progress bar displays during any ProjectWise Explorer operation that
involves the transferring of files. When this setting is on, then during a file transfer, you can cancel the
operation by cancelling the progress bar. If ProjectWise was in the middle of transferring multiple files
and you cancel the operation, the operation simply stops right there. Any files that were successfully
transferred are not affected.
XML File for Each Checked Out Master File in the Working Directory
For each master MicroStation or AutoCAD document you check out, an XML file is created in the
working directory. This file lists all the master document's references, and records all reference-related
changes to the master document. When you select Check In or Update Server Copy, the changes
documented in the XML file are saved to the logical set in the database. If you free the master document,
changes documented in the XML file are discarded and not saved to the database. Each XML file will
have the name of the master file prepended to the file name. For example, master1.dgn.fileinfo.xml,
master2.dwg.fileinfo.xml.
ProjectWise Application Compatibility Matrix
The ProjectWise readme lists the primary applications and versions known to be supported with
ProjectWise at the time of this release.
For a more comprehensive listing of applications and versions supported with ProjectWise, please refer
to the ProjectWise Application Compatibility Matrix document related to this release on the Be
Communities website. This is a living document and will be updated periodically.
Auto-login for Integrated Applications
You can now configure integrated applications so that when they are launched from the desktop, the
user is automatically logged in to a preselected datasource, either using their Windows domain account
through single sign-on, or using a specific ProjectWise account (which can be either a logical account or
a Windows-based account). Configuration of default auto-login settings is typically handled by the
administrator, who will install default settings onto your computer via some external tool, but users can
override these default settings if necessary by configuring their own auto-login settings for each
ProjectWise
56
What's New?
application on the new iDesktop Auto-Login tab on the ProjectWise Network Configuration Settings
dialog.
When auto-login is not enabled, users will see two new options on the Log in dialog they normally
encounter when launching integrated applications from the desktop. The first option, Use Windows
Single Sign-On for authentication, lets you specify whether or not you want to use your Windows
domain account to log in to the selected datasource. This option only displays if the selected datasource
is already enabled for single sign-on. The second option, Auto-login to this datasource the next time I
work with this application, lets you select whether or not to enable auto-login for this application.
Once enabled, the next time you launch this integrated application from the desktop, you will be
automatically logged in to the same datasource you last logged in to, and using the same account
(regardless of whether or not you used single sign-on).
If you want to override your default auto-login settings, you can change them using the ProjectWise
Network Configuration Settings dialog. If you want to change settings for a particular application, you
can do it from the integrated application itself by selecting File > Open; in the Open Document dialog,
select another datasource to log in to. This will open the Log in dialog, where you can then reset these
options.
Bentley View V8i (8.11.5.24) Integration Support
ProjectWise V8i supports integration with Bentley View V8i (08.11.05.24 or later).
When Bentley View V8i is installed on the same computer as ProjectWise Explorer V8i, and you select a
DGN or DWG document in ProjectWise Explorer and then select Document > View, the selected
document opens in Bentley View by default. That session of Bentley View remains integrated with
ProjectWise Explorer until you close Bentley View. When you launch Bentley View from the desktop,
integration with ProjectWise Explorer is turned off by default. To turn on desktop integration, you need
to modify the PW.CFG file delivered with Bentley View.
In Bentley View V8i (SELECTseries 3), desktop integration is now enabled by default, and you only need
to modify the PW.CFG file if you want to disable that integration.
ProjectWise
Support for MicroStation V8i's activate reference functionality for in-place editing.
Support for MicroStation V8i's new Print Organizer dialog, which replaces Batch Print.
Support for MicroStation V8i's dynamic views.
New variables in MCM.CFG.
You can now configure MicroStation title block settings in ProjectWise Administrator so that
MicroStation title blocks will be updated whenever you export a document with title blocks.
Support for workspace directives. Managed Workspaces will now process conditional statements
when variable directives are added to configuration settings blocks.
You can now attach configuration settings blocks to user groups and user lists.
The Configuration Settings Block Properties dialog has undergone some usability enhancements.
dms_project This new variable resolves to the nearest project folder up the folder tree from the
current location. For example: $(dms_project(_DGNDIR))
dms_parentproject This new variable resolves to the second project folder up the folder tree from
the current location.
57
What's New?

Support for AutoCAD 2008 and AutoCAD 2009
Support for AutoCAD's data link functionality, which lets you embed a link, inside the active DWG, to
an Excel document stored in ProjectWise.
Support for the referencing of DWF and DGN documents into DWG documents
Sheet Set Manager integration (with AutoCAD 2007, 2008, 2009)
ProjectWise Session File Manager This is a new ProjectWise window in integrated AutoCAD that
lets you manage the ProjectWise documents that are currently open in AutoCAD. When you open a
ProjectWise document into AutoCAD, the document is automatically added to the list of open
documents in ProjectWise Session File Manager. When you open a ProjectWise document that has
references, ProjectWise Session File Manager also lists the ProjectWise reference documents that are
copied out to your working directory. You can then perform a number of ProjectWise operations by
selecting the document in the ProjectWise Session File Manager and selecting an option from the
right-click menu.
Integration with AutoCAD-based AutoCAD vertical applications The integration provided for
AutoCAD-based AutoCAD vertical applications is exactly the same as that provided for base
AutoCAD. This means that when you install ProjectWise Explorer with iDesktop Integration support
for a particular AutoCAD-based AutoCAD vertical application, you get the same ProjectWise menu in
the vertical application that you normally get in integrated AutoCAD, and the same integration with
basic commands like File > Open and File > Save As, but ProjectWise will not provide any additional
integration with the additional tools and commands that are unique to that vertical application.

New ProjectWise Administrator Log In / Log Out Behavior
In previous versions, opening ProjectWise Administrator prompted you to log in to the last datasource
you were in when you closed ProjectWise Administrator, and the only way to log out of a datasource
was to close ProjectWise Administrator. Now, when you open ProjectWise Administrator, the available
datasources remain closed until you attempt to log in to one. Logging in to and out of datasources in
ProjectWise Administrator now resembles the way you log in to and out of datasources in ProjectWise
Explorer.
New User Settings
General - User can only log in through Web View Server When on, the user can only connect to
ProjectWise through the ProjectWise Web View Server; if they try to access ProjectWise from
ProjectWise Explorer or from a regular ProjectWise Web Server, they will not be permitted to log in.
When this setting is off, the user can access ProjectWise from ProjectWise Explorer and ProjectWise
Web Server as usual, and also the ProjectWise Web View Server if desired.
User Interface - Show progress indicator during file transfers Controls whether or not the progress
bar displays during any ProjectWise Explorer operation that involves the transferring of files.
Network - Allow user to change client/server network settings When on, the user can change the
default settings set for them under the Network category.
ProjectWise
58
What's New?
Network - Enable Delta File Transfer This setting is on by default, and enables delta file transfer for
specific users.
Network - Compress client/server request data This setting is also on by default, and enables data
compression for specific users.
Message folders - Disable message polling This setting is off by default. Turn this setting on only if
you do not want ProjectWise Explorer to automatically check to see if you have a new message from
another ProjectWise user, sent through ProjectWise Messenger.
Network - Enable
Delta File Transfer
Turning this setting on enables delta file transfer for all ProjectWise Explorer
clients connected to this datasource. Once you turn this setting on, you also
need to turn on the user setting of the same name, for each user you want to
benefit from delta file transfer. Delta file transfer is the ProjectWise technology
that improves performance when sending large files over networks with high
latency / low bandwidth connections, by only sending the changes needed to
update the file, rather than the entire file. For optimal performance, use delta
file transfer along with existing ProjectWise local file caching functionality.
Delta file transfer is enabled by default on every ProjectWise Integration Server,
ProjectWise Caching Server, and ProjectWise Gateway Service. If you want to
disable it for a particular server, there is a delta file transfer setting in the
respective server's dmskrnl.cfg file.
Network Turning on this setting enables data compression for all ProjectWise
Compress client/
Explorerand ProjectWise Administrator clients connected to this datasource.
server request data Once you turn this setting on, you also need to turn on the user setting of the
same name, for each user you want to benefit from this data compression. Data
compression is the ProjectWise technology that improves performance over
networks with high latency / low bandwidth connections by compressing the
data that is being sent to or retrieved from the ProjectWise database. The data is
then decompressed when it reaches its destination. Performance improvements
will be most noticeable with large amounts of data (for example, thousands of
documents in a folder) across high latency / low bandwidth connections.)
ProjectWise
Documents Update Access

Control Cache on
Document Delete
All of the access control security settings for a datasource are stored in the
database. For optimal performance, ProjectWise Integration Server maintains a
cache of this information. When this datasource setting is on, then any change
that affects access control will trigger the access control cache to be updated.
When this setting is off (default), the access control cache will not be updated
when a document, having security settings, is deleted. Information about the
deleted document will be updated the next time some other action occurs that
normally triggers the access control cache to be updated.
Audit Trail - User Log User Create
If on, audit trail records the date and time each user account was created in this
datasource (whether the account was created manually, or using ProjectWise
User Synchronization Service). The record can be seen on the new Audit Trail
tab on the User Properties dialog in ProjectWise Administrator.
Audit Trail - User Log Logins
If on, audit trail records the date and time each user last logged in to this
datasource. The record can be seen on the new Audit Trail tab on the User
Properties dialog in ProjectWise Administrator.
59
What's New?
Audit Trail - User Log Logouts
If on, audit trail records the date and time each user last logged out of this
datasource. The record can be seen on the new Audit Trail tab on the User
Properties dialog in ProjectWise Administrator.
Audit Trail Truncating Truncate type Keep records for

specific period
There are now two settings you can configure under this setting. The first
setting, which existed pre-V8i, lets you specify how many days, weeks, or years
to keep the audit trail records. The second setting, which is new in ProjectWise
V8i, lets you specify down to the hour, minute, or second how long to keep the
records. This way you can offset the truncation process to a time when you
suspect the server will be least busy.
Web Components Design Compare

Utility Address
When using ProjectWise InterPlot Server's Design Compare Utility with

ProjectWise Web Server, you need to specify the name of the Virtual Directory
Alias here. The Virtual Directory Alias is the virtual directory used in Internet
Information Server, and gets created during configuration of the Design
Compare Utility.
Audit Trail tab on User Properties Dialog

An Audit Trail tab has been added to the User Properties dialog in ProjectWise Administrator (this tab
will not be visible to users in ProjectWise Explorer). This tab lets the administrator see when a user
account was created, and when that user has logged in and out. Note that these actions are only
recorded if the respective new Audit Trail logging options (Log User Create, Log Logins, Log Logouts) are
also set.
Selecting Users By Groups / Lists
In ProjectWise Administrator you can now quickly identify and select all the users that belong to a
particular group or user list by right-clicking the Users icon and selecting the option, Select Users by
Groups / Lists. In the dialog that opens, select a group or user list, then click Select. All of the users who
are members of that group or user list are automatically selected in the Users list.
Automatic Updating of Project Type Property Values
A new setting has been added to the Project Type Properties dialog called Update this property value
when related property value changes. When this setting is on, and the property is connected by a
SELECT statement to another property, then this property value will be automatically updated in
ProjectWise Explorer, when the value of the connected property is updated.
Datasource Statistics
You can now view various datasource statistics (such as Number of Users, Maximum Documents Per
Folder, Items With Audit Trail, and so on) through the new Statistics tab on the Datasource Properties
dialog in ProjectWise Administrator. The Statistics tab shows the statistics of the datasource based on
the last time statistics were updated. The statistic update time is displayed in the bottom left corner of
the tab. By default, statistics are updated every 12 hours, but this can be changed through the
StatisticsFrequency setting in the Integration Server's dmskrnl.cfg file. You can also
manually update the statistics by clicking the Refresh button on the Statistics tab. Refreshing statistics
can take a few minutes for large datasources, during which time you will be unable to use ProjectWise
Administrator.
ProjectWise
60
What's New?
New System Variables

ProjectWise contains new system variables that can be used in environment attribute definitions and
title blocks:
$DOCUMENT.FULLDESC$ provides the full path to the document in ProjectWise using the
document description.
$DOCUMENT.FULLNAME$ provides the full path to the document in ProjectWise using the
document name.
$VAULT.FULLDESC$ provides the full path to the folder in ProjectWise using the folder
description.
$VAULT.FULLNAME$ provides the full path to the folder in ProjectWise using the folder name.

Administrators responsible for setting up ProjectWise Web Parts should note the following changes:
After installing ProjectWise Web Server and Web View Server, you can now deploy the server either
as a regular ProjectWise Web Server, or as a read-only server called ProjectWise Web View Server.
The advantage of deploying a ProjectWise Web View Server is that it allows casual users to have
read-only access to ProjectWise, without reporting ProjectWise Passport usage in SELECT Server.
You can now install ProjectWise Web Server and Web View Server on a computer that does not have
SharePoint installed. Or if SharePoint is installed, you can deploy ProjectWise Web Server or
ProjectWise Web View Server to any SharePoint or non-SharePoint IIS website on that computer.
When configuring ProjectWise Web Parts on a SharePoint site, the process for connecting
ProjectWise Web Parts to each other and to the datasource has been simplified.
ProjectWise Web Parts now lets users:
ProjectWise
create documents
check out and open documents
open documents as read-only
move and delete documents
export documents
free documents
view thumbnail images of documents
display set contents
compare the graphical differences of two DGN documents
create various types of links to documents
purge local copies of documents from the working directory
create, modify, and delete folders
right-click menu added to the Navigation web part
view the component tree, show component properties, and zoom in to components
view spatial data in the new Spatial Content web part
61
What's New?
Spatial Features Added to ProjectWise

Many of the features from ProjectWise Geospatial have been moved to core ProjectWise. To enable
these features, a Spatial option has been added to the installer for ProjectWise Integration Server,
ProjectWise Explorer, and ProjectWise Administrator. Also, a new Spatial Content web part is delivered
with ProjectWise Web Server.
When you install ProjectWise Administrator with the Spatial Administrator option enabled, the
following datasource nodes are available in ProjectWise Administrator:
Coordinate Systems
Symbologies
Background Maps
Spatial Metadata Scanners
When you install ProjectWise Explorer with the Spatial option enabled, the following functionality is
available in ProjectWise Explorer:
Ability to create and load spatial location files (SLF)

Spatial location scanner for CAD, Image, and SHP files
ESRI Set Support for SHP files
Basic background map interface
Basic symbology legend
Spatial properties for documents and folders
Spatial View toolbar
Spatial searches
Spatial iDesktop Integration with MicroStation
Delta File Transfer
Delta file transfer is the new ProjectWise technology that improves performance when sending large
files over networks with high latency / low bandwidth connections, by only sending the changes needed
to update the file, rather than the entire file. For optimal performance, use delta file transfer along with
existing ProjectWise local file caching functionality.
Delta file transfer settings exist in several places:
For every ProjectWise Integration Server, Caching Server, and Gateway Service, delta file transfer is
enabled by default. To disable it on a particular server, open that server's dmskrnl.cfg file, and in the
[DFT] section, add the line: enabled:false
On the Settings tab of the Datasource Properties dialog in ProjectWise Administrator, there is a new
setting called Network - Enable Delta File Transfer. This setting is on by default, and enables delta file
transfer for all ProjectWise Explorer client computers.
On the Settings tab of the User Properties dialog, there is also a new setting called Network - Enable
Delta File Transfer. This setting is also on by default, and enables delta file transfer for specific users.
ProjectWise
62
What's New?
To test and display the benefits of delta file transfer, delivered with ProjectWise is a Delta File Transfer
Benchmark Tool. This tool creates some example files in the selected storage area, runs a test check
out / check in on the files, and then displays the statistics about the transfer.
Note:
You do not need administrator privileges to run the Delta File Transfer Benchmark Tool, however on
Windows Vista and Windows Server 2008 computers, you will need to run the tool as an administrator
if you want the tool to collect performance counter data.
To Run a Delta File Transfer Test, Using the Delta File Transfer Benchmark Tool
1. In Windows Explorer, go to the ...\Bentley\ProjectWise\bin folder and double-click the
dftbmwiz.exe file.
2. When the Delta File Transfer Benchmark Tool opens, click Next.
3. Select a datasource, enter an administrative user name and password. The datasource you specify
must be a ProjectWise V8i datasource. The user account you specify must have the following user
settings turned on: Folder - Create, Folder - Delete, Document - Create, and Document - Delete. Click
Next.
4. Select the storage area you want to use in the delta file transfer test. Click Next.
5. Enter the name of a test folder to be created. This is where the test files will be stored. This folder
will be deleted after the test is run. Select Automatic DFT test. Click Next.
6. When the test is done, select the tabs at the top of the wizard to examine the results.
7. Please click the Email Results button, to send the results of the test to Bentley. The results get sent
to: pwbenchmarks@bentley.com.
If you want to save the results for your own information, click Save Results to save the results to a
text file.
8. Click Finish.
Data Compression
Data compression is the new ProjectWise technology that improves performance over networks with
high latency / low bandwidth connections by compressing the data that is being sent to or retrieved
from the ProjectWise database. The data is then decompressed when it reaches its destination.
Performance improvements will be most noticeable with large amounts of data (for example, thousands
of documents in a folder) across high latency / low bandwidth connections.
Data compression settings exist in two places:
On the Settings tab of the Datasource Properties dialog in ProjectWise Administrator, there is a new
setting called Network - Compress client/server request data. This setting is on by default, and data
compression for all ProjectWise Explorer client computers.
On the Settings tab of the User Properties dialog, there is also a new setting called Network Compress client/server request data. This setting is also on by default, and enables data compression
for specific users.
ProjectWise
63
What's New?
Microsoft Server 2008 Support

ProjectWise now supports Microsoft Server 2008. See the ProjectWise readme for details about which
specific ProjectWise modules are supported to run on Microsoft Server 2008.
Microsoft SQL Server 2008 and 2005 Support
ProjectWise Integration Server now supports Microsoft SQL Server 2008 and 2005.
Oracle Database 11g Support
ProjectWise Integration Server now supports Oracle Database 11g.
Limited Internet Protocol Version 6 (IPv6) Support
ProjectWise continues to support Internet Protocol Version 4 (IPv4) the same in V8i as it has in
previous releases. The initial release of ProjectWise V8i also supports Internet Protocol Version 6
(IPv6), with the following considerations.
To run ProjectWise V8i on IPv6:
Creating a new ProjectWise V8i datasource on an IPv6 computer is currently not supported. For
now, you can only use IPv6 with ProjectWise V8i if you are upgrading a datasource to ProjectWise
V8i from a previous version.
All ProjectWise V8i clients and servers must be part of the IPv6 network.
All ProjectWise V8i clients and servers must be configured to use IPv6, by enabling the new IPv6
settings on the ProjectWise V8i Network Configuration Settings dialog.
ProjectWise V8i client connections through ProjectWise Gateway Service are not supported.
Mixed mode (some modules running on IPv4 and some on IPv6) is not supported.
Caution:
It is highly recommended that you contact Bentley Professional Services to assist you in setting up
ProjectWise V8i on IPv6.
Increased File Size Limit
ProjectWise now has a built-in file size limit of 2^64 bytes (18,000,000 TB), however the size limit for
files stored in ProjectWise will depend on your own site's file system limitations, which may be lower
than what ProjectWise supports. Check your file system/operating system documentation for more
information.
Access Control Cache
By default, the access control cache maintained by ProjectWise Integration Server is no longer updated
each time a document, having security settings, is deleted. The access control cache will simply be
updated the next time some other action occurs that normally triggers the access control cache to be
ProjectWise
64
What's New?
updated. If for some reason you require the old behavior, you can turn on the datasource setting, Update
Access Control Cache on Document Delete.
Audit Trail Truncating
When you are keeping audit trail records for a specific period of time, you can now specify down to the
hour how long you would like to keep the records. This way you can offset the truncation process to a
time when you suspect the server will be least busy.
MSG File Property Extractions
Microsoft Outlook is no longer needed on the ProjectWise Integration Server computer in order to
extract file properties from MSG documents in the datasource. Instead, you now only need to install an
MSG iFilter (downloadable from Microsoft, which in turn requires Windows Desktop Search to be
installed). Note that you can use this same MSG iFilter for file property extractions as well as text
indexing.
Note: As of ProjectWise V8i (SELECTseries 2), the MSG iFilter is no longer required to extract file
properties from MSG documents.
ProjectWise
65
What's New?
ProjectWise
66
Database Setup
Setting Up the Main ProjectWise Database

When you are setting up the main ProjectWise server, before you install any ProjectWise software, you
should set up the database for your ProjectWise datasource. While this section does not attempt to
instruct you how to create your database, or the ODBC datasource, it does cover certain ProjectWise
requirements for each supported database. See your respective database's documentation for relevant
database instructions.
1. First, you need to have a supported database engine (Oracle or SQL Server) installed. Once the
database engine is installed, you need to create one database for each ProjectWise datasource you
plan to create. This database will contain the ProjectWise database tables, which get created when
you create the ProjectWise datasource.
2. ProjectWise supports languages that use multi-byte characters, and therefore requires that the
database engine used by ProjectWise support Unicode data storage.
SQL Server automatically supports Unicode, and requires no special action. For Oracle databases,
you must manually set the database Character Set and National Character Set encodings. These
values are typically defined when installing the Oracle database software and creating a new Oracle
database, although they may be changed on a running database with some effort (consult your
Oracle documentation). The two encodings most typically used in Oracle are UTF8 and AL32UTF8;
please consult your Oracle documentation for information regarding which character set you should
use when creating the database.
3.
4.
5.
6.
7.
If you will be running ProjectWise against an existing Oracle database, you will need to verify that
the database NLS character set parameters are set for Unicode. This information can be found in the
NLS_DATABASE_PARAMETERS table.
All connections to the database are supported by an ODBC connection from ProjectWise Integration
Server to the database. So after creating a database in Oracle or SQL Server, you must create an
ODBC datasource which points to that database. The ODBC datasource/driver must exist on the
same computer on which you install ProjectWise Integration Server. Make a note of the name you
give the ODBC datasource, as you will need to select it from a list of available ODBC datasources
when you are creating your ProjectWise datasource.
ProjectWise Integration Server is a native 64-bit application, therefore you must use the 64-bit ODBC
Data Source Administrator when creating an ODBC datasource, rather than the 32-bit ODBC Data
Source Administrator as in previous releases.
When SQL Server is your database, make sure that when configuring your ODBC datasource you turn
OFF the setting, Use regional settings when outputting currency, numbers, dates times.
When Oracle is your database, you cannot use the Microsoft ODBC driver for Oracle, you must use
the ODBC driver delivered with the Oracle client install.
When Oracle is your database, the Oracle database user must have (at a minimum) the following
privileges and permissions in order to run ProjectWise Integration Server:
CONNECT role
CREATE PROCEDURE privilege
CREATE SEQUENCE privilege
ProjectWise
67
Database Setup
Setting Up ProjectWise Orchestration Framework Service and its Database
CREATE TABLE privilege
CREATE VIEW privilege
UNLIMITED TABLESPACE privilege
EXECUTE permission on the DBMS_LOB package
8. When Oracle is your database, and you are using the Oracle Instant Client ODBC driver, you must do
one of following steps to ensure that ProjectWise can load the Oracle ODBC driver:
Make sure that the Windows environment variable TNS_ADMIN points to the directory where the
Oracle tnsnames.ora file exists. This environment variable either must be a System-level
environment variable, or must be set for the service account that the ProjectWise Integration
Server executes as. You must restart the ProjectWise Integration Server service for this
environment variable to be recognized by the ProjectWise Integration Server.
If you choose not to set the TNS_ADMIN environment variable, or if the Oracle ODBC driver
cannot find the directory pointed to by the TNS_ADMIN environment variable, it will search for
the tnsnames.ora file in the network\admin directory under your Oracle Instant Client
installation directory. For example, if you installed the Oracle Instant Client to C:\IC, then you
must copy the tnsnames.ora file to C:\IC\network\admin\tnsnames.ora.
Note: See the Requirements section of the ProjectWise readme
(C:\Program Files\Bentley\ProjectWise\readme_ProjectWise.chm) for the list of
supported databases and drivers.
Setting Up ProjectWise Orchestration Framework Service and its

Database
ProjectWise Orchestration Framework Service is a required supporting feature of:
ProjectWise Integration Server's automated document processors (full text indexing, thumbnail
image extraction, file properties extraction)
ProjectWise Automation Service
ProjectWise Distribution Service
During ProjectWise Orchestration Framework Service installation, you will specify the location of your
SQL Server database engine, and then either create a new Orchestration Framework database in it, or
select an existing one. You can use a local or remote installation of SQL Server.
While ProjectWise Orchestration Framework Service requires its own database, separate from your
ProjectWise Integration Server's databases, you can use the same SQL Server database engine for both
ProjectWise Orchestration Framework Service and ProjectWise Integration Server.
ProjectWise Integration Server, Bentley i-model Composition Server for PDF, ProjectWise Automation
Service, and ProjectWise Distribution Service should each be installed on a separate computer, therefore
you will need to install ProjectWise Orchestration Framework Service on each of those computers.
When you have multiple installations of ProjectWise Orchestration Framework Service, it is
recommended that you use the same database for all of them.
ProjectWise
68
Database Setup
Before You Install ProjectWise Orchestration Framework Service

1. See the ProjectWise readme (readme_ProjectWise.chm) for a list of supported operating
systems and other system requirements.
2. Make sure the computer you are installing on is on a domain.
3. Make sure Message Queuing is installed on this computer and that the service is running.
To enable on Windows Server 2012: Open Server Manager. On the Manage menu, click Add Roles
and Features. Click through the Add Roles and Features Wizard until you get to the Select features
page. Select the check box next to Message Queuing. Click Next, then click Install.
To enable on Windows Server 2008: Open Server Manager. Right-click Features in the left pane and
select Add Features. In the Add Features Wizard, select the check box next to Message Queuing.
Click Next, then click Install.
4. Install Microsoft SQL Server on this or another computer. See the readme for a list of supported
versions.
If you do not have a local or remote version of SQL Server installed, then you can install the SQL
Server 2008 R2 SP1 Express Edition that is delivered with ProjectWise Server Setups. Note that if
you need to use the delivered Express Edition, you must install it yourself, prior to installing
ProjectWise Orchestration Framework Service. The ProjectWise Orchestration Framework Service
installer will not prompt you to install it, if a local installation of SQL Server is not detected.
5. Set up the user account under which ProjectWise Orchestration Framework Service will run. You
will enter the credentials of this account during ProjectWise Orchestration Framework Service
installation when you encounter the Please Provide Credentials page of the installer. This account:
can either be a local account or a Windows domain account

must be a member of the Administrator group on this computer
must have log on as a service rights on this computer
must also exist in the SQL Server database (under Security > Logins) you plan to use
Tip: ProjectWise Orchestration Framework Service will stop running if and when this user accounts
password expires. Because Windows accounts typically have passwords that periodically expire, one
solution is to use a local account with a non-expiring password. Another solution is to use a Windows
domain account and set its password to never expire, or simply manually reset the password for
ProjectWise Orchestration Framework Service in the Services window, ideally before the password
expires.
6. Make sure the user account you use to launch the ProjectWise Orchestration Framework Service
installer is a Windows account that is a member of the Administrator group.
7. It is recommended that you use the same user account to install ProjectWise Orchestration
Framework Service, ProjectWise Integration Server, ProjectWise Distribution Service, ProjectWise
Automation Service, and/or Bentley i-model Composition Server for PDF software.
8. You must install MicroStation V8i (SELECTseries 3) before you install ProjectWise Orchestration
Framework Service, if you plan to install ProjectWise Integration Server with the Automated File
Processing - Full Text Indexing option and you want to extract text from DGN and DWG documents
in the datasource.
Note: During installation, you may be prompted to install .NET Framework 3.5 SP1, if the required
version is not already installed.
ProjectWise
69
Database Setup
To Install ProjectWise Orchestration Framework Service

1. Double-click the setup.exe file to open the ProjectWise Server Setups master installer.
2. Click Install next to ProjectWise Orchestration Framework Service.
3. When the Setup Wizard opens, click Next.
4. When the License Agreement page opens, accept the agreement and click Next.
The Custom Setup page opens, allowing you to select the location to which you want to install the
ProjectWise Orchestration Framework Service.
ProjectWise
70
Database Setup
On a 32-bit operating system, the default installation location is
C:\Program Files\Bentley\OrchestrationFramework.
C:\Program Files (x86)\Bentley\OrchestrationFramework.
5. Do one of the following:
Accept the default installation location and click Next.
or
Click the Change button to the right of the Install to field to change the default installation location,
then click Next.
Note: Unlike the rest of the ProjectWise modules, ProjectWise Orchestration Framework Service can
always be installed to a different location than other ProjectWise modules from the same release
version that are already installed on the same computer. Also, if ProjectWise Orchestration
Framework Service happens to be the first module you are installing from this release, then you will
still be able to change the installation location of the next module you decide to install from this
release.
6. On the Please Provide Credentials page, enter the credentials of the user account that ProjectWise
Orchestration Framework Service will run under, then click Next.
This should be the same user account you set up in the procedure, Before You Install Orchestration
Framework Service. If the user is a Windows account, enter the name of the domain to which the user
belongs in the Domain Name field. If the user is a local account, enter the users computer name in
the Domain Name field.
7. When the Ready to Install the Program page opens, click Install.
ProjectWise
71
Database Setup
8. When installation and setup is complete, click Finish.
The Orchestration Framework Database Setup dialog opens for you to create a new Orchestration
Framework database, or to select an existing one.
To Create a New Orchestration Framework Database

1. The Orchestration Framework Database Setup dialog opens at the end of the ProjectWise
Orchestration Framework Service installation. If needed, you can also open the dialog by doubleclicking the dbsetup.exe file from one of the following locations:
On 32-bit computers
C:\Program Files\Bentley\OrchestrationFramework\dbsetup.exe
On 64-bit computers
C:\Program Files (x86)\Bentley\OrchestrationFramework\dbsetup.exe
ProjectWise
72
Database Setup
2. In the Server field, enter name of the computer on which your SQL Server database engine is
installed. This field defaults to the local computer's name. If your SQL Server database is running
under a specific instance name, then enter the name of the computer, followed by a backslash,
followed the database instance name. For example, computername\SQLinstancename.
3. In the Database Security section, select the option for how you will be logging in to SQL Server. The
option you select here depends on the type of account you specified on the Please Provide
Credentials page of the Setup Wizard during ProjectWise Orchestration Framework Service
installation:
Select Use Windows integrated security to automatically log in to the specified SQL Server using
the credentials of the Windows account specified on the Please Provide Credentials page.
or
Select Use a specific name and password, and then in the User name and Password fields enter
the same credentials of the local account specified on the Please Provide Credentials page.
Remember: The account you specify here (whether a local or Windows account) must already exist
in the database, as described in Before You Install Orchestration Framework Service.
If you are setting up ProjectWise Orchestration Framework Service for the first time, click New to
create a new Orchestration Framework database in SQL Server. Once created, the new database will
display in the Database list, and the Database Status field will inform you that the selected
ProjectWise
73
Database Setup
database needs the latest Orchestration Framework schema. This is expected. Clicking OK on the
Orchestration Framework Database Setup dialog will install the schema.
or
If you have already set up the same version of ProjectWise Orchestration Framework Service on
another computer, then from the Database list, select the existing database that is being used by the
other installation of ProjectWise Orchestration Framework Service. The Database Status field will
inform you that the selected database already has the latest Orchestration Framework schema
installed.
5. When finished, click OK.
Note: If you are prevented from creating a new or selecting an existing database on the Orchestration
Framework Database Setup dialog, then one of the following may be true:
The service for the selected SQL Server instance may not be running. Make sure that it is running,
then try again.
The SQL Server computer name specified, or instance name, or both, may be incorrect. Make sure
you typed the name(s) correctly, then try again.
The account you are trying to use does not exist in SQL Server. Make sure this account (whether local
or Windows) exists in the database with appropriate database permissions, then try again.
ProjectWise
74
ProjectWise Integration Server Configuration
Setting Up the ProjectWise Integration Server Computer

ProjectWise Integration Server is the primary server of ProjectWise, and is the server on which your
datasources are created. Every other ProjectWise module, whether it is a user client, an administrative
client, or another server, is said to be a client of the ProjectWise Integration Server.
ProjectWise Integration Server delivers some optional automated file processing features which require
some additional configuration beyond a basic ProjectWise Integration Server installation. Please review
the configuration checklist for each automated file processing feature before proceeding with
ProjectWise Integration Server installation. If you plan to install all of the automated file processing
features, some of the configurations listed in each checklist may be duplicated and you will only need to
perform those steps once.
Note: You can host storage areas on the ProjectWise Integration Server computer, or you can also
install ProjectWise Caching Server on another computer and host storage areas on that computer.
Full Text Indexing Configuration Checklist

Full text indexing is the feature of ProjectWise Integration Server that extracts text from documents in
the datasource and then stores that text in a full text index catalog. Users can then search the datasource
for any documents containing the indexed text. To manage the catalog, ProjectWise uses Windows
Search on Windows Server 2012, or by Microsoft Indexing Service on Windows Server 2008. You can
store the catalog on the ProjectWise Integration Server computer itself, or on a separate computer
where ProjectWise Indexing Service is installed. When using a standalone ProjectWise Indexing Service,
the ProjectWise Integration Server forwards full text searches, and any text extraction updates, to the
ProjectWise Indexing Service, which in turn uses its own local Windows Search or Microsoft Indexing
Service.
The following is a checklist of things you need to install or configure on the ProjectWise Integration
Server computer to set up the full text indexing feature in general, for all datasources run by this server.
Once the feature is set up, you then use ProjectWise Administrator to enable and run full text indexing
extractions on a per datasource basis.
2. Make sure the computer you are configuring is on a domain.
3. Install Microsoft SQL Server or SQL Server Express Edition.
See Before You Install ProjectWise Orchestration Framework Service for details.
4. Set up the user account under which ProjectWise Orchestration Framework Service will run.
You will enter the credentials of this account during installation of ProjectWise Orchestration
Framework Service, when you encounter the Configure Shepherd Credentials dialog. This account:
ProjectWise
75

must also exist in the SQL Server database (under Security > Logins) that you plan to use
ProjectWise Orchestration Framework Service will stop running if and when this user accounts
expires.
5. Make sure you use the same user account to install ProjectWise Orchestration Framework Service
and ProjectWise Integration Server, and that the user account is a Windows account that is a
member of the Administrator group
6. Make sure the following Windows features are installed:
.NET Framework 3.5

Message Queuing
Windows Search (if using Windows Server 2012)
Microsoft Indexing Service (if using Windows Server 2008)
To install these features on Windows Server 2012: Open Server Manager. On the Manage menu, click
Add Roles and Features. Click through the Add Roles and Features Wizard until you get to the
Select features page. Turn on .NET Framework 3.5 Features, Message Queuing, and Windows
Search Service. Click Next, then click Install. After installation, make sure the Message Queuing and
Windows Search services are running.
To install .NET Framework and Message Queuing on Windows Server 2008: Open Server Manager.
Right-click Features in the left pane and select Add Features. In the Add Features Wizard, turn on .NET Framewo
and Message Queuing. Click Next, then click Install. After installation, make sure the Message
Queuing service is running.
To install Microsoft Indexing Service on Windows Server 2008: Open Server Manager. Expand Roles in
the left pane. Right-click the File Services role and select Add Role Services. In the Add Role
Services wizard, turn on Windows Server 2003 File Services (it automatically enables the
Indexing Service feature listed below it). Click Next, then click Install. After installation, make sure
Microsoft Indexing Service is running.
Note: If Windows Search Service is currently enabled on Windows Server 2008, you will have to
disable it first before you can enable Windows Server 2003 File Services and the Indexing
Service.
7. If you plan to host and maintain the catalog on this computer, you can either preset the index storage
location before installing ProjectWise Integration Server, or you can let ProjectWise Integration
Server set its own default location for the catalog. There is no setup required if you want to use the
default location, however, if you choose to preset your own index storage location, follow the steps in
the procedure, To Preset the Location of the Text Index Catalog, and the Text Index Proxy Files.
8. Depending on the file types of the documents you want to index text from, you may need to install
additional software on the computer performing the text extraction (which is typically the
ProjectWise Integration Server computer). The additional software required is an iFilter for the
required file type, but in some cases you may have to install the full application to get the required
iFilter. See the following table for some of the common file types that you will need to install
additional software for.
ProjectWise
76

To index text from
You must install
DGN and DWG documents
MicroStation V8i (SELECTseries 3), and it must be installed

before ProjectWise Orchestration Framework Service
PDF documents
Adobe PDF iFilter 9.0 (64-bit only)
Microsoft Outlook message

(MSG) documents
MSG iFilter
Documents attached to MSG

documents
MSG iFilter plus an iFilter for the attached document, and both
iFilters must be 64-bit
Note: Microsoft's MSG iFilter requires that you install Windows Search first, then the MSG iFilter.
However, ProjectWise does not support Windows Search when using Windows Server 2008.
Therefore, after installing the MSG iFilter on Windows Server 2008, turn off Windows Search and
turn on Microsoft Indexing Service.
Note: Currently, ProjectWise cannot index text from a DGN document attached to an MSG document.
9. Install ProjectWise Prerequisite Runtimes (available from ProjectWise Server Setups).
10. Install ProjectWise Orchestration Framework Service V8i (SELECTseries 4).
11. Install ProjectWise Integration Server V8i (SELECTseries 4) with the Automated File Processing Full Text Indexing option enabled.
12. You can host the text index catalog on this ProjectWise Integration Server computer, or another
computer entirely. If you want to host and maintain the text index catalog on another computer, then
you must install ProjectWise Indexing Service on that computer. Regardless of which computer you
designate to host and maintain the catalog, the ProjectWise Integration Server will always perform
the text extractions.
Note: While ProjectWise full text indexing in general supports the use of a standalone ProjectWise
Indexing Service for maintaining the full text index catalog, the SharePoint search integration feature
of ProjectWise Web Server does not currently support this configuration and only works when the
full text index catalog is located on the ProjectWise Integration Server computer. Likewise,
SharePoint search integration does not work if the full text index catalog is stored on the tail
Integration Server in a head-tail server configuration.
13. Whenever you install an iFilter, make sure you restart both the Microsoft Indexing Service and the
ProjectWise Integration Server service in the Services window.
14. On this or another computer, install ProjectWise Administrator V8i (SELECTseries 4) with the
Automated File Processing option enabled.
15. In ProjectWise Administrator:
a. Set up a user account in the datasource to use for running full text indexing jobs. The users user
setting General - Use access control should be OFF, to ensure the user has access to all
documents in the datasource.
b. Configure the Full Text Indexing document processor. See the Managing Document
Extractions section of the ProjectWise Administrator help for details.
ProjectWise
77

Thumbnail Image Extractor Configuration Checklist

Thumbnail image extraction is the feature of ProjectWise Integration Server that extracts thumbnail
images from documents in the datasource. ProjectWise Explorer users will then be able to see the
thumbnail images of their documents when the browse the document list.
Server computer to set up the thumbnail image extraction feature in general, for all datasources run by
this server. Once the feature is set up, you then use ProjectWise Administrator to enable and run the
feature on a per datasource basis.
Tip: No additional applications are required (beyond what is outlined below), in order to extract
thumbnail images from V8 DGN, AutoCAD DWG (including AutoCAD 2010 and later format), and Revit
documents.
Tip: Thumbnails cannot be generated from pre-V8 DGN documents.
See Before you install ProjectWise Orchestration Framework Service for details.

expires.
.NET Framework 3.5
Message Queuing
Select features page. Turn on .NET Framework 3.5 Features and Message Queuing. Click Next,
then click Install.
To install these features on Windows Server 2008: Open Server Manager. Right-click Features in the
left pane and select Add Features. In the Add Features Wizard, turn on .NET Framework 3.5
Features and Message Queuing. Click Next, then click Install.
ProjectWise
78

After installation, make sure the Message Queuing service is running.
To extract thumbnail images from PDFs, install Adobe Reader X.
Install ProjectWise Prerequisite Runtimes (available from ProjectWise Server Setups).
Install ProjectWise Orchestration Framework Service V8i (SELECTseries 4).
Install ProjectWise Integration Server V8i (SELECTseries 4) with the Automated File Processing File Property and Thumbnail Image Extractors option enabled.
10. On this or another computer, install ProjectWise Administrator V8i (SELECTseries 4) with the
11. In ProjectWise Administrator:
6.
7.
8.
9.
a. Set up a user account in the datasource to use for running thumbnail image extraction jobs. The
users user setting General - Use access control should be OFF, to ensure the user has access to
all documents in the datasource. Also, the users user setting Document - Modify must be ON.
b. Configure the Thumbnail Extraction document processor. See the Managing Document
File Property Extractor Configuration Checklist

File property extraction is the feature of ProjectWise Integration Server that extracts file properties from
documents in the datasource. ProjectWise Explorer users will then be able to see the file properties of
their documents on the File Properties tab of the Document Properties dialog.
Server computer to set up the file property extraction feature in general, for all datasources run by this
server. Once the feature is set up, you then use ProjectWise Administrator to enable and run the feature
on a per datasource basis.
Note: Due to an AutoCAD limitation, you cannot extract file properties from DWG documents.
Note: The MSG iFilter is no longer required to extract file properties from MSG documents.

expires.
ProjectWise
79

.NET Framework 3.5
Message Queuing
Select features page. Turn on .NET Framework 3.5 Features and Message Queuing. Click Next,
then click Install. After installation, make sure the Message Queuing service is running.
6.
7.
8.
9.
10.
11.
To install these features on Windows Server 2008: Open Server Manager. Right-click Features in the
left pane and select Add Features. In the Add Features Wizard, turn on .NET Framework 3.5
Features and Message Queuing. Click Next, then click Install.
To extract file properties from PDFs, install Adobe Reader X.
Install ProjectWise Prerequisite Runtimes (available from ProjectWise Server Setups).
Install ProjectWise Integration Server V8i (SELECTseries 4) with the Automated File Processing File Property and Thumbnail Image Extractors option enabled.
On this or another computer, install ProjectWise Administrator V8i (SELECTseries 4) with the
In ProjectWise Administrator:
a. Set up a user account in the datasource to use for running file property extraction jobs. The users
user setting General - Use access control should be OFF, to ensure the user has access to all
documents in the datasource. Also, the users user setting Document - Modify must be ON.
b. Configure the File Property Extractions document processor. See the Managing Document
Installing ProjectWise Integration Server
Before You Install ProjectWise Integration Server

2. Create a database in SQL Server or Oracle, then create an ODBC datasource that points to that
database.
3. Ideally, the computer you are about to install ProjectWise Integration Server on should be on a
domain.
4. Make sure that the computers on which you install ProjectWise Integration Server and all
ProjectWise Caching Servers have their clocks synchronized with the time of an authoritative
computer. If the clocks are not properly synchronized, then any tokens issued by ProjectWise
Integration Server may expire prematurely when a user attempts to check out a document, causing
the operation to fail. See the following Microsoft article for details:
http://technet.microsoft.com/en-us/library/cc773013(WS.10).aspx
ProjectWise
80

6. If you plan to install the ProjectWise Indexing Connector for SharePoint feature of ProjectWise
Integration Server, make sure the Web Server (IIS) role of Windows Server 2008 is installed (Server
Manager > Features > Add Roles).
After installing the Web Server (IIS) role, make sure the following Web Server (IIS) role services are
installed as well:
Web Server
Application Development
ASP.NET
Security
Windows Authentication
Management Tools
IIS Management Console
IIS 6 Metabase Compatibility
7. If you plan to install the ProjectWise Indexing Connector for SharePoint feature of ProjectWise
Integration Server, also make sure the following Windows Server 2008 features are installed
(Server Manager > Features > Add Features):
.NET Framework 3.5.1 Features
.NET Framework 3.5.1
WCF Activation
HTTP Activation
Non-HTTP Activation
Window Process Activation Service:
8.
9.
10.
11.
12.
13.
ProjectWise
Process Model
.NET Environment
Configuration APIs
If you plan to implement full text indexing, see the full text indexing configuration checklist.
If you plan to implement thumbnail image extractions, see the thumbnail image extractor
configuration checklist.
If you plan to implement file property extractions, see the file property extractor configuration
checklist.
Make sure Microsoft Core XML Services (MSXML) 6.0 is installed (available from ProjectWise Server
Setups, if necessary).
ProjectWise Integration Server cannot be installed on a computer on which ProjectWise Caching
Server, ProjectWise Gateway Service, or ProjectWise Indexing Service is already installed.
In previous releases, you had to manually add the ProjectWise broadcasting and listening ports of
5799 and 5800 to the Windows Firewall exception list on this ProjectWise Integration Server
computer. In the current release, the ProjectWise Integration Server, ProjectWise Caching Server,
and ProjectWise Gateway Service installer takes care of this automatically when installing on
Windows Server 2008 SP2 and R2 computers. Note that you will still have to manually add these
ports to the Windows Firewall exception list, if installing ProjectWise Caching Server or ProjectWise
Gateway Service on a Windows Server 2003 computer (ProjectWise Integration Server is not
supported Windows Server 2003).
81

14. If you plan to use the Product Activation Wizard as launched from the final page of the Setup Wizard,
then you must launch the master ProjectWise Server Setups installer using the Run as Administrator
option. This ensures that the Product Activation Wizard is also run as an administrator, which in
turn ensures that the licensing information you enter through the Product Activation Wizard gets
registered to the correct location in the Windows Registry.
To Install ProjectWise Integration Server
2. Click Install next to ProjectWise Integration Server.
ProjectWise
82

The Custom Setup page opens, showing you the features that can be installed, and the location to
which the product will be installed.
The following additional items can be installed through the ProjectWise Integration Server installer:
ProjectWise Indexing Connector for SharePoint server-side files that allow the search feature
of integrated SharePoint to leverage the ProjectWise full text index. Installing this feature creates a
website in IIS called ProjectWise Indexing Connector.
Component Services EC plugin server-side files required for using Bentley OpenPlant with this
server. Installing this feature creates a website in IIS called Component Services.
Automated File Processing > Full Text Indexing server-side files for performing full text
extractions, indexing of the extracted text to a catalog, and searching and retrieving text from the
catalog when users run full text searches
Automated File Processing > File Property and Thumbnail Image Extractors server-side
files for performing file property and thumbnail image extractions
Spatial extension provides basic spatial features to ProjectWise. This extension is automatically
installed when you install ProjectWise Integration Server, there is no option for it on the installer.
ProjectWise
83

Note: The Automated File Processing features are optional and will not be able to be installed if
ProjectWise Orchestration Framework Service is not installed.
5. To change whether or not a feature gets installed, click the feature's icon and select the appropriate
option from the menu. Items with an X to the left of them will not be installed.
6. Accept the default installation location, or click the Change button (if available) to change it.
The default installation location is C:\Program Files\Bentley\ProjectWise.
Note: The Change button will not display on this installer if another 64-bit application from this
release is already installed; if that is the case, the ProjectWise Integration Server will simply be
installed to the same location as the previously installed application.
7. When finished on the Custom Setup page, click Next.
9. (Optional) On the last page of the wizard, the options to launch the License Management tool and
start the servers service are on by default. You can turn either of these options off if you prefer to do
them later.
ProjectWise
84

10. Click Finish.

If you selected the option to launch the License Management tool, the Product Activation Wizard
opens for you to configure licensing for this module.
Installing ProjectWise Administrator

ProjectWise Administrator is the main administrative interface for ProjectWise. It provides tools for
datasource creation, as well as server, datasource, and user management. ProjectWise Administrator is
typically installed on the same computer as ProjectWise Integration Server and can also be installed on
other computers as needed.
Tip: Although ProjectWise Class Editor is installed through the ProjectWise Administrator installer, it
opens by selecting Start > All Programs > Bentley > ProjectWise V8i (SELECTseries 4) >
Administrative Tools > ProjectWise Class Editor.
Before You Install or Upgrade ProjectWise Administrator
2. Make sure Microsoft .NET Framework 3.5 SP1 is installed (available from ProjectWise Admin Setups,
if necessary).
3. If you are not installing ProjectWise Administrator on the same computer as ProjectWise Integration
Server, then both computers should be on the same domain.
ProjectWise
85

While it is not required for every operation in ProjectWise Administrator, operations such as
datasource creating, renaming, and deleting requires that ProjectWise Administrator and
ProjectWise Integration Server be on the same domain.
4. If necessary you can run both ProjectWise Administrator V8i (SELECTseries 4) and ProjectWise
Administrator V8 XM Edition on the same computer.
5. If two versions of ProjectWise Administrator are installed on the same computer, you do not need to
run versionSwitch.vbs to switch the active version, like you do for ProjectWise Explorer. Just
make sure you use ProjectWise Administrator V8i (SELECTseries 4) to connect to ProjectWise V8i
(SELECTseries 4) datasources, and use the earlier version of ProjectWise Administrator to connect
to the same earlier version datasource.
6. If you have an existing ProjectWise Administrator V8i or later installed, you can use the ProjectWise
Administrator V8i (SELECTseries 4) installer to upgrade the old version to the new version. If you
have additional ProjectWise modules installed from the same older (V8i or later) release version, see
Upgrading to ProjectWise V8i (SELECTseries 4) > Precautions for the recommended workflow for
upgrading.
To Install ProjectWise Administrator
1. Double-click the setup.exe file to open the ProjectWise Admin Setups master installer.
2. Click Install next to ProjectWise Administrator.

ProjectWise
86

5. When the Setup Type page opens, select Custom and click Next.
The following items can be installed through this installer:
ProjectWise Administrator itself, with Server and Datasource Management tools
Environment Administration (environments, interfaces)
General Administration (applications, departments, states, workflows, storage areas)
Messaging Services Management
ProjectWise Class Editor
Additional Administration Utilities (menu editor)
iDesktop Attribute Administrator
ProjectWise
87

Automated File Processing (thumbnails, full text, file properties)

Project Type Editor
Spatial Administrator (coordinate systems, symbologies, background maps, spatial metadata
scanners)
6. To change whether or not a feature gets installed, click the feature's icon and select the appropriate
option from the menu.
Items with an X next to them will not be installed.
7. You can either accept the default installation location, or click the Change button (if available) to
change it.
C:\Program Files\Bentley\ProjectWise.
C:\Program Files (x86)\Bentley\ProjectWise.
ProjectWise
88

Note: For non-upgrade installations, the Change button will not display on this installer if another
32-bit application from this release is already installed; if that is the case, ProjectWise Administrator
will simply be installed to the same location as the previously installed application.
Note: When upgrading from an existing ProjectWise Administrator V8i or later, the Change button
will not display for you to change the installation location, and the new version will be automatically
installed to the same location as the previous version.
10. When installation is complete, click Finish.
To Upgrade to ProjectWise Administrator V8i (SELECTseries 4)
2. Click Install next to ProjectWise Administrator.

A second ProjectWise Admin Setups window opens to show you the version(s) of ProjectWise
Administrator currently installed and what your installation options are. You may see the following
options depending on the existing configuration:
Install
ProjectWise
This button appears when the new version is not yet installed, and a pre-V8i
version is detected. An Install button displays rather than an Upgrade button
here, because you can install the new version next to an existing installation of
ProjectWise Administrator V8 XM Edition (8.9.x) or 2004 Edition (8.5.x).
89

Upgrade
This button appears next to any V8i (8.11.5) or later version detected. Clicking
Upgrade will replace the existing V8i version with the new version.
Change
This button appears when the current version is already installed. Clicking
Change from here is the same as modifying the installation of the version listed
using Add / Remove Programs.
Remove
This button appears next to any V8 XM Edition (8.9.x) or 2004 Edition (8.5.x)
version detected. Clicking Remove from here is the same as uninstalling the
version listed using Add / Remove Programs.
3. (Optional) If ProjectWise Administrator V8 XM Edition (8.9.x) or 2004 Edition (8.5.x) is currently

installed and you want to remove it, click the Remove button next to the version listed. (Remember,
you do not have to remove these particular older versions in order to install the new version.) When
uninstallation of the selected version is complete, continue with the next step.
If there is an Install button, click Install to install the new version.
or
If there is an Upgrade button, click Upgrade to replace the existing V8i version with the new version.
When the Setup Wizard opens, click Next. To finish the installation, follow the rest of the steps in the
previous procedure, To Install ProjectWise Administrator.
Tip: If the upgrade happens to fail for some reason of the system, you may need to repair and then
uninstall the old version of ProjectWise Administrator manually, using Add / Remove Programs.
ProjectWise
90

Installing the Example Dataset and Business Process Template for BS1192
ProjectWise Admin Setups delivers the following optional resources for setting up a datasource:
ProjectWise Example Dataset, which includes:
an example datasource template file
an example attribute exchange rules file
a generic workflow rules engine template
ProjectWise Business Process Template for BS1192
By default, installing the example dataset installs files to:
C:\Program Files (x86)\Bentley\ProjectWise\Example Datasets\Example
Template Datasource Map.pdf
Template
C:\Program Files (x86)\Bentley\ProjectWise\Example Datasets\Rules
Engine
By default, installing the Business Process Template for BS1192 installs files to:
C:\Program Files (x86)\Bentley\ProjectWise\Example Datasets\BS1192
To use any of these items, you must install them first, and then import them into your datasource. The
way in which you import and set up these items depends on the item. See below.
General Steps for Importing the Example Datasource Template
1. Install the ProjectWise Example Dataset.
2. Create a datasource.
3. Either import the example datasource template (Example Template.aam) into the datasource
through the Data Import Wizard that opens at the end of datasource creation, or import it later using
the ProjectWise Import Wizard (this is a different wizard).
General Steps for Importing the Example Attribute Exchange Rules
3. Either import the example attribute exchange rules file
(Example Attribute Exchange Rules.ini) into the datasource through the Data Import
Wizard that opens at the end of datasource creation, or import it later through the Attribute
Exchange Rules node in ProjectWise.
General Steps for Importing the Generic Workflow Rules Engine Template
3. Import the workflow rules engine template (RulesEngineTemplate.aam) into the datasource
using the ProjectWise Import Wizard.
ProjectWise
91

4. Export the workflow rules file (example_rules.xlsx) out of ProjectWise Explorer to a local
folder.
5. Import example_rules.xlsx into a datasource through the Rules Engine node in ProjectWise
Administrator.
General Steps for Importing the ProjectWise Business Process Template for BS1192
1. Install the ProjectWise Business Process Template for BS1192.
3. Import the ProjectWise Business Process Template for BS1192
(BS1192 Template for SQL Server.aam or BS1192 Template for Oracle.aam,
depending on your database) into the datasource using the ProjectWise Import Wizard.
4. Export the workflow rules file (bs1192_rules.xlsx) out of ProjectWise Explorer to a local folder.
5. Import bs1192_rules.xlsx into a datasource through the Rules Engine node in ProjectWise
Administrator.
To Install the Example Dataset
2. Click Install next to ProjectWise Example Dataset.
ProjectWise
92

5. When the Destination Folder page opens, select where to install the dataset and click Next.
ProjectWise
93

6. When the Ready to Install page opens, click Install.

To Install the ProjectWise Business Process Template for BS1192
2. Click Install next to ProjectWise Business Process BS1192 Template.
ProjectWise
94

ProjectWise
95

Creating Datasources
You create datasources in ProjectWise Administrator. Each datasource you create must have its own
database in SQL Server or Oracle. Creating multiple datasources that use a single database is not
supported.
Creating a datasource will add the necessary ProjectWise database tables to the supporting database.
After creating the datasource you can:
set up your datasource from scratch
import data from a previously exported datasource
import the delivered example datasource template
ProjectWise Admin Setups delivers an extensive example template, which you can use as a quick and
easy way to set up a datasource and become familiar with the new features of this version before setting
up your own production datasource.
Caution:
Please note that the ProjectWise database schema is unpublished and is subject to change without
notice.
Before You Create the Datasource

1. If you want to create a datasource using the new example template and you have not installed it yet,
install the example dataset now from ProjectWise Admin Setups.
2. Open ProjectWise Administrator by selecting Start > All Programs > Bentley > ProjectWise V8i
(SELECTseries 4) > ProjectWise Administrator.
ProjectWise
96

3. When ProjectWise Integration Server and ProjectWise Administrator are installed on the same
computer, the server's computer name is automatically registered and displayed under the Servers
node when you open ProjectWise Administrator. If you would like to create a datasource on a
ProjectWise Integration Server that is not displayed in ProjectWise Administrator, you need to
register the name or IP address of the ProjectWise Integration Server computer. To do this, rightclick the Servers node in ProjectWise Administrator and select Register Server. Type the computer
name or IP address of the computer on which ProjectWise Integration Server is installed and
running, then click Finish.
4. The Applications node in ProjectWise Administrator is populated when you create the datasource,
using the information contained in the appinfo.xml file (...\ProjectWise\bin). You can
modify this file as needed using any text editor before creating your datasource, or you can simply
modify the default list of applications in ProjectWise Administrator after creating the datasource.
To Create a ProjectWise Datasource

1. In ProjectWise Administrator, expand a server, right-click the main Datasources node, and select
New Datasource.
ProjectWise
97

2. When the New Datasource Wizard opens, click Next.
ProjectWise
98

3. On the Choosing datasource type page, select the default option, A datasource that is located on
<computername>, then click Next.
4. On the Naming the datasource page, in the Datasource name field, type a name for your
datasource. Optionally, you can enter a display name for the datasource in the second field. If you
only fill in the first field, the datasource will be displayed to users as
<computername>:<datasourcename>, for example, shaup123:projectwise. Entering a
display name lets you use a name that is more recognizable (or easier to remember) for your users,
and it also serves the purpose of hiding (from users) the computer name on which the server is
located. When finished, click Next.
Caution: The following characters may not be used in either the Datasource name or Display name
fields:
\/:*?"<>|@
ProjectWise
99

5. On the Specifying ODBC connection details page, select the ODBC datasource that you have
configured to connect to your ProjectWise database instance, then click Next.
ProjectWise
100

6. On the Specifying database user account for client connections page, type the user name and
password that matches the user name and password of an existing account in your database
instance, then click Next.
ProjectWise
101

7. On the Specifying administrator account page, create the initial ProjectWise administrator account
for this datasource by entering a user name and password of your choice, and then retyping the
password to confirm. (These can be (but are not required to be) the same as the user name and
password of the database account entered in the previous step.) Make a note of these credentials as
you will need them later to log in to this datasource in ProjectWise Administrator. When finished,
click Next.
ProjectWise
102

8. On the Finishing New Datasource Wizard page, do one of the following:

Turn on Create datasource data from template (to import datasource settings from a template)
and click Finish.
or
Turn off Create datasource data from template (if you do not want to import datasource settings)
and click Finish.
ProjectWise
103

The Create Database Tables dialog opens.
9. Turn on Enable "Create" Button and then click Create.

The Creating Tables dialog opens, displaying the progress of the creation of the ProjectWise tables.
Soon after the Creating Tables dialog opens, the Create Administrator and Storage dialog opens to
create administrator group accounts, establish a storage area, and verify administrator account
password.
ProjectWise
104

10. Required: On the Create Administrator and Storage dialog, do the following:
a. (Optional) In the Administrator Group section, change the name and description of the default
Administrator group if needed.
By default, the name and description are both set to Administrator. You can leave it as is for
now, and rename it later if necessary in ProjectWise Administrator, after the datasource is
created. After datasource creation, any user you add to this group will be able to log in to the
datasource in ProjectWise Administrator and will have full control over all the nodes in the
datasource.
b. (Optional) In the Restricted Administrator Group section, change the name and description of
the default Restricted Administrator group if needed.
By default, the name and description are both set to Restricted Administrator. You can
leave it as is for now, and rename it later if necessary in ProjectWise Administrator, after the
datasource is created. After datasource creation, any user you add to this group will be able to log
in to the datasource in ProjectWise Administrator, but will only have access to the nodes in the
datasource to which they are explicitly assigned access.
ProjectWise
105

c. In the Storage Areas section, in the Path field, type the location you want to create the main
storage area folder (for example, C:\exton-tbb-0822-storage1), or click Browse to
navigate to the location.
The storage area name, description, and host computer are already filled in by default. You can
accept the defaults or change them as necessary. The computer name listed in the Host field
defaults to the computer on which you are working (that is, the ProjectWise Administrator
computer). If you change the host, remember that either a ProjectWise Integration Server or
ProjectWise Caching Server must be installed on that computer to order create the storage area
on that computer.
d. In the Administrative User section, in the Verify Password field, type the password of the
Administrator account for this datasource (created in step 7).
e. When finished, click OK.
At this point, the Creating Tables dialog resumes showing progress of the ProjectWise tables being
created in the database.
11. When the dialog informs you that the tables have been created, click Close.

If you turned off Create datasource data from template on the last page of the New Datasource
Wizard, then at this point, datasource creation is complete and you are logged in to the datasource.
You can now manually configure each node in your datasource as required.
or
If you turned on Create datasource data from template on the last page of the New Datasource
Wizard, then at this point the Data Import Wizard opens; click Next.
ProjectWise
106

The Selecting template page opens for you to select which data template file you want to import,
and optionally, which attribute exchange template you want to import.
ProjectWise
107

Assuming you have already installed the new example dataset, the wizard automatically loads the
Example Template.aam file and supporting Example Attribute Exchange Rules.ini
file.
You can import these files to set up an example datasource for testing, or you can import your own
data from a previously exported datasource. The Example Template.aam file is in the same
format used by the ProjectWise Export and Import Wizards. The Data Import Wizard accepts .AAM
files exported from ProjectWise versions 2.x, 3.x, and 8.x.
Tip: Importing the new example template files is recommended if you are new to ProjectWise, as it is
a quick and easy way to set up a datasource. It is also a good way for administrators to get familiar
with the new features of this version before you set up your own production datasource.
13. On the Selecting template page:
a. Either leave the default template selected, or click the Browser button (...) to select another
template.
b. (Optional) Either leave the default Attribute Exchange template selected, or click the Browser
button (...) to select another template. You can also turn off Import Attribute Exchange
template file altogether if you do not want to import any Attribute Exchange template.
c. When finished, click Next.
The results of the import are displayed on the Review import results page.
ProjectWise
108

14. Review the import results and click Next.

15. Click Finish.
ProjectWise
109

You are now logged in to the datasource.
ProjectWise
110

Configuring the Example Datasource Template

The example datasource template is useful if you need to quickly setup a new datasource for testing
purposes. The easiest way to import the example datasource template, along with the corresponding
example attribute exchange rules file, is through the Data Import Wizard that opens at the end of the
datasource creation process.
If you do not use the Data Import Wizard to import these items, you can import them into your
datasource later. To import the example datasource template, use the ProjectWise Import Wizard (Start
> All Programs > Bentley > ProjectWise V8i (SELECTseries 4) > Tools > Import Wizard). Through
this import wizard you can select which items from the example template you want to import. It is not
necessary to choose every option when using the import wizard; however, to use every feature of the
example template, all options should be selected. To import the example attribute exchange rules file,
right-click the Attribute Exchange Rules node in ProjectWise Administrator and select Import
Mappings.
Tip: Installing the example dataset also installs a document called
Example Template Datasource Map.docx that describes the example dataset and where to find
things in ProjectWise Explorer once the example datasource template has been imported. To review this
ProjectWise
111

document, it is installed to
C:\Program Files (x86)\Bentley\ProjectWise\Example Datasets.
To Manually Import the Example Template

1. Make sure you have already installed the new example dataset.
2. Open a command prompt and enter:
3.
4.
5.
6.
7.
8.
pwimpt.exe /workflow
On the Welcome page of the ProjectWise Import wizard, select Yes to indicate that you will log in as
the administrator, then click Next.
When the ProjectWise Log in dialog opens, select the datasource you want to import the data into.
Enter the user name and password of an administrative user account in the selected datasource
(Password is case sensitive, User Name is not), and click Log in.
On the Define the import settings page, click the check box next to every option and click Next.
On the next page, turn on the check box next to Project/Folder in the Update if exists section, then
click Next.
On the next page, click Next to accept the default import settings for managed workspaces.
On the next page, click Browse to locate the Example Template.aam file.
By default the example template is installed to

Template.
9. Select the Example Template.aam file and click Open.
Selecting the AAM file automatically populates the Log file name field.
10. Click Next.
The next page lets you choose where the imported folders and documents will be placed.
11. Place all of the folders under the Documents root folder.
12. Select the storage area you want to use and click Import.
13. When finished, click Close.
To Manually Import the Example Attribute Exchange Rules

1. In ProjectWise Administrator, log in to your datasource.
2. Right-click the Attribute Exchange Rules datasource node and select Import Mappings.
3. When prompted, click Yes to confirm that you understand that the import will delete all existing
mappings.
4. In the Open dialog, navigate to
Template, select the Example Attribute Exchange Rules.ini file, and click Open.
Run a Reference and Link Set Scan on the Example Dataset

1. In ProjectWise Explorer, select Tools > Scan References and Link Sets and when the wizard opens,
click Next.
2. On the Specify Scan Options page, leave both options on (to scan for both master/reference
documents and link sets) and click Next.
ProjectWise
112

3. On the Select Master Files and Folders page, select these folders to scan:
BSI200 - Peterborough Geospatial Investigation

BSI300 - Medical Complex - Cordoba
BSI400 - W01 - Intersection of I-9 and SR 32
BSI900 - Adelaide Tower
Gas Authority, Inc.
Wedraw Drafters, Inc. - New Employee Training
Templates
4. Click Next.
5. On the Master Folder Settings page, turn on the check box next to every folder so that all subfolders
will be searched for references and link sets. Leave the Application filter check boxes unchecked.
Click Next.
6. On the Reference File Priority Search Options page, turn off Enable Priority Search and click
Next.
7. On the Reference File Proximity Search Options page, turn on Search Subfolders for References,
select Advanced, and enter 5 for the number of folders above the master files folder. Click Next.
8. On the Reference File Search Options page, optionally specify a log file, then click Next.
9. On the final page of the wizard, click Scan to start the scan.
10. Click Close when the scan is complete.
Import a Coordinate System to Use with the Example Dataset

1. In ProjectWise Administrator, right-click the Coordinate System datasource node and select Add
from Dictionary.
2. In the Add Coordinate Systems dialog, from the Coordinate Systems Groups list, select Projected
defs from ESPG, area undetermined.
ProjectWise
113

3. In the Available coordinate systems in the selected group list, select:
EPSG:2029
NAD27(76) / UTM zone 17N
4. Click Add.
Create the Single Layer Background Maps To Use with the Example Dataset
Before background maps can be viewed on the Spatial tab in ProjectWise Explorer, they must be created
in ProjectWise Administrator. First, create the example template background maps with a single layer.
1. In ProjectWise Administrator, right-click the Background Maps datasource node and select Create
Background Map.
The Background Map Settings dialog opens.
2. In the Map Name field, enter: Natural City
3. Set Coordinate System to EPSG:2029.
4. Click Add Layer.
The Edit Map Layer Settings dialog opens.
5. Click the down arrow next to the URL field and select Add DPR Layer.
The Choose a document for the layer dialog opens.
6. In the dialog, navigate to the following folder:
dmsSystem\Spatial\Background Map DPR Files
Take a moment to look at the descriptions for each of the documents in this folder.
7.
8.
9.
10.
11.
12.
The first value tells you which background map the document is for.
The second value tells you what order to add the documents in.
The third and fourth values tell you the minimum and maximum scale values, respectively.
Select the document that has the description Natural City - Layer 1 - 0_0 and click Open.
Click OK in the Edit Map Layer Settings dialog.
In the Background Map Settings dialog, click Browse.
In the Select Folder dialog, navigate to the
dmsSystem\Spatial\Background Map Settings Files folder and click OK.
In the Background Map Settings dialog, click Save.
Repeat steps 1 to 11 to create the Rose City, South City and West City background maps.
Create the Multi-layer Background Map To Use with the Example Dataset
Background maps can also have multiple layers. The example template has one multi-layer background
map called East City.
1. In ProjectWise Administrator, right-click the Background Maps datasource node and select Create
Background Map.
The Background Map Settings dialog opens.
2. In the Map Name field, enter: East City
3. Set Coordinate System to EPSG:2029.
4. Click Add Layer.
ProjectWise
114

dmsSystem\Spatial\Background Map DPR Files
Take a moment to look at the descriptions for each of the documents in this folder.
The first value tells you which background map the document is for.
The second value tells you what order to add the documents in.
The third and fourth values tell you the minimum and maximum scale values, respectively.
7. Select the document that has the description East City - Layer 1 - 0_0 and click Open.
8. Click OK in the Edit Map Layer Settings dialog.
9. Click Add Layer.
dmsSystem\Spatial\Background Map DPR Files and select the document that has the
description East City - Layer 2 - 4000_0 and click Open.
12.
13.
14.
15.
Remember the two numbers at the end of the description of this document (4000 and 0). You will
use them to specify the scale range in the next step.
In the Edit Map Layer Settings dialog, in the Minimum scale range field, enter 4000. In the
Maximum scale range field, enter 0. Click OK.
Repeat steps 9 to 12 to add Layer 3 and Layer 4.
In the Background Map Settings dialog, in the Folder field, click Browse. Navigate to and select the
dmsSystem\Spatial\Background Map Settings Files folder and click OK.
Click Save.
Because East City is the default background map for the example template, it needs to be set as the
reference map.
16. Right-click the East City background map and select Set as Reference.
Assign Background Maps to Their Corresponding Projects/Folders

Now that all five background maps have been created, they need to be assigned to their corresponding
projects in ProjectWise Explorer. Because East City is the reference map, it is currently set as the
background map for all folders and projects.
1. In ProjectWise Explorer, right-click the
BSI200 Peterborough Geospatial Investigation project and select Properties.
2. On the Spatial tab, in the Background Map section, set the background map to Use default map
and click OK.
3. Repeat steps 1 and 2 for each of the following projects and folders.
ProjectWise
115

Project/Folder
Background Map
BSI200 Peterborough Geospatial Investigation
Use default map
BSI300 Medical Complex Cordoba
Rose City
BSI400 W01 Intersection of I-9 and SR 32
West City
BSI900 Adelaide Tower
South City
Groningen Refinery (under the Gas Authority, Inc

project)
Natural City
Wedraw Drafters, Inc New Employee Training
Use default map
Each subfolder will inherit the map assigned to their parent project or folder.
Loading a Single Spatial Location File That Has Multiple Locations

1. In ProjectWise Explorer, select Tools > Load SLF.
2. When the Load SLF wizard opens, click Next.
3. On the Choose Spatial Location File page, click the folder icon next to the Spatial Location File
field.
The Select Spatial Location File to Import dialog opens.
4. Navigate to the dmsSystem\Spatial\Background Maps\Spatial Location Files
folder.
5. Set the Applications list to All Applications.
6. Select the East_City_SLF.slf document and click Open.
7. On the Choose Spatial Location File page, click Next.
8. On the Select the Coordinate System page, select ESPG:2029 and click Next.
9. On the Select the Target Folder page, click the folder icon next to the ProjectWise Target Folder
field.
10. In the Select Folder dialog, select BSI200 Peterborough Geospatial Investigation
and click OK.
11. Back on the Select the Target Folder page, turn on Include subfolders and click Next.
12. On the Import Options page, select any option and click Next.
13. On the Logging Options page, optionally specify a log file, then click Next.
14. On the final page, click Start Import.
15. When the locations have been loaded, click OK then Exit.
16. Repeat steps 1 to 15 to load the Rose City_SLF_Building 1.slf document, using
BSI300 Medical Complex Cordoba as the project in step 10.
Note: The SLF documents loaded above add spatial locations to the following folders:
BSI200 - Peterborough Geospatial Investigation\Project Data
ProjectWise
116

BSI300 - Medical Complex - Cordoba\CAD\MASTER FILES\3D MODELS
\BUILDING 1
You can also add multiple spatial location files to a project.
Loading Multiple Spatial Location Files, Each Having One Location

1. In ProjectWise Explorer, select Tools > Load SLF.
2. When the Load SLF wizard opens, click Next.
3. On the Choose Spatial Location File page, click the folder icon next to the Spatial Location File
field.
The Select Spatial Location File to Import dialog opens.
4. Navigate to the dmsSystem\Spatial\Background Maps\Spatial Location Files
folder.
5. Set the Applications list to All Applications.
6. Select the West City_SLF_03.slf document and click Open.
7. On the Choose Spatial Location File page, click Next.
8. On the Select the Coordinate System page, select ESPG:2029 and click Next.
9. On the Select the Target Folder page, click the folder icon next to the ProjectWise Target Folder
field.
10. In the Select Folder dialog, select BSI400 W01 Intersection of I-9 and SR 32 and
click OK.
11. Back on the Select the Target Folder page, turn on Include subfolders and click Next.
12. On the Import Options page, select any option and click Next.
13. On the Logging Options page, optionally specify a log file, then click Next.
14. On the final page, click Start Import.
15. When the locations have been loaded, click OK, then click Back until you get back to the Choose
Spatial Location File page.
16. Repeat steps 3 to 14 for the remaining two West City SLF documents.
17. After loading the final file click Exit.
The SLF documents loaded above add spatial locations to the following folder:
BSI400 W01 Intersection of I-9 and SR 32
Note: In order to view the spatial locations for folders and subfolders, you must enable View >
Geometry Display > Show Folder and View > Geometry Display > Show Subfolders. You can also
change how the spatial locations appear by selecting View > Manage Spatial Views and creating a
new view. Select View > Save Spatial Settings so that these settings do not need to be changed each
time you open ProjectWise Explorer.
Importing Example Access Control Settings

1. In ProjectWise Administrator, create two users: User 1 and User 2
The BSI300--Access Control Settings.csv file contains access control settings for the
BSI300 - Medical Complex - Cordoba project. This file gets installed when you install the example
dataset, and is also included in the example datasource in the Template Import Files folder. If you do
ProjectWise
117

Importing the Delivered Rules Engine Templates and Workflow Rules
2.
3.
4.
5.
6.
7.
8.
not have access to the local BSI300--Access Control Settings.csv file, you can export this
document to a local folder first before continuing with the next step.
In ProjectWise Explorer, select the BSI300 - Medical Complex - Cordoba project.
In the Preview Pane, select the Access Control tab.
Click Import Permissions.
In the Import dialog, navigate to the local BSI300--Access Control Settings.csv file and
click Open.
In the Import dialog, make sure that the All Levels check box is on and then click OK.
When prompted, click Replace to replace the existing access control on the selected folder.
Click Apply on the Access Control tab.
Importing the Delivered Rules Engine Templates and Workflow

Rules
After installing the Example Dataset (ProjectWise Admin Setups), you can then import the generic
workflow rules engine template into your datasource and set up workflow rules.
Likewise, after installing the ProjectWise Business Process Template for BS1192 (ProjectWise Admin
Setups), you can then import the template into your datasource and set up BS1192 workflow rules.
To Import the Generic Workflow Rules Engine Template

Important: This procedure uses the ProjectWise Import Wizard, which must be launched from a
command prompt as described below in order to import the predefined workflow. Do not launch the
wizard from the Start menu.
1. Open a command prompt and navigate to:
...\Program Files (x86)\Bentley\ProjectWise\bin
2. Enter the following command:
pwimpt /workflow
The ProjectWise Import Wizard opens.
3. Select Yes (yes, you will log in as an administrator) then click Next.
The ProjectWise Log in dialog opens.
4. Select the datasource you want to import the template into, enter the user name and password of an
account that is a member of the Administrator group in the selected datasource (Password is case
sensitive, User Name is not), and click Log in.
5. On the Define the import settings page, turn on Environments, Projects\Folders, and
Documents and click Next.
6. Click Next to skip the following pages until you reach the Import Script File page.
7. In the Import script file name field, click the Browse button (...) to navigate to the location where
the template is installed and select the .AAM script file.
For example:
C:\Program Files (x86)\Bentley\ProjectWise\Example Datasets\Rules
Engine\RulesEngineTemplate.aam
ProjectWise
118

8. Click Next. On the next page, you specify where to import the projects, folders, and/or documents.
The window on the left shows a list of the projects and folders contained in the export file. The
window on the right shows the folder list of the destination datasource.
a. In the left window, select Manually exported folders.
b. In the right window, select the Documents root folder as the destination.
c. Click the arrow button (->).
d. From the Choose storage area list, select the storage area that will be used in the event that the
Import Wizard encounters folders with an associated storage area that does not exist in the
destination datasource.
e. Click Import.
The wizard displays the progress of the import.
9. When the import is complete, click Close.
Importing the template adds the following datasource objects:
an environment called Rules Engine

an interface called Manager
a workflow called Rules Engine Workflow
four states - Approved, Draft, Obsolete, Pending Approval
Importing the template also adds a project called P03HA-Shangha_Water which has these
datasource objects already assigned to various items in the project.
At the root of the project is a file called example_rules.xlsx, which contains the default
workflow rules of the Rules Engine. You need to export the example_rules.xlsx file from
ProjectWise Explorer, and then use that file to import the workflow rules into ProjectWise
Administrator.
10. Export the example_rules.xlsx file:
a. In ProjectWise Explorer, log in to the datasource where you imported the template.
b. Under the Documents root folder, select the project, P03HA-Shangha_Water.
c. In the document list, select the example_rules.xlsx file and select Document > Export.
d. In the Document Export Wizard, select Export and click Next. On the next page, select an export
location and click Next. The file is exported. Click Finish.
11. Open the local example_rules.xlsx file to review and edit settings as needed before importing
to ProjectWise Administrator.
The Super User and Rollback User specified on the Settings tab of the worksheet must exist in the
datasource, otherwise import will fail. The Super User will need elevated privileges above those of
normal users, and the Rollback User must be a member of the Administrator group in the datasource.
Either add these users to the datasource, or on the Settings tab of the worksheet add the names of
existing users who have the appropriate permissions. They can be the same user, if necessary.
12. Import the rules from the example_rules.xlsx file:
a. In ProjectWise Administrator, log in to the datasource where you want to import the workflow
rules.
b. Right-click the Rules Engine node and select Import Rules.
c. Navigate to and select the exported local example_rules.xlsx file and select Open.
The rules are imported to the database. Note that nothing actually displays under the Rules Engine
node - this is expected.
13. Now go back to ProjectWise Explorer, select the exported example_rules.xlsx file and select
Document > Import to save any changes made to this file back to ProjectWise.
ProjectWise
119

To Import the ProjectWise Business Process Template for BS1192

Important: This procedure uses the ProjectWise Import Wizard, which must be launched from a
command prompt as described below in order to import the predefined workflows and user lists. Do not
launch the wizard from the Start menu.
1. Open a command prompt and navigate to:
...\Program Files (x86)\Bentley\ProjectWise\bin
2. Enter the following command:
pwimpt /workflow /groups
3.
4.
5.
6.
7.
The ProjectWise Import Wizard opens.

Select Yes (yes, you will log in as an administrator) then click Next.
The ProjectWise Log in dialog opens.
Select the datasource you want to import the template into, enter the user name and password of an
account that is a member of the Administrator group in the selected datasource (Password is case
sensitive, User Name is not), and click Log in.
On the Define the import settings page, turn on Environments, Projects\Folders, and
Documents and click Next.
Click Next to skip the following pages until you reach the Import Script File page.
In the Import script file name field, click the Browse button (...) to navigate to the location where
the template is installed and select the .AAM script file related to your database (Oracle or SQL
Server).
For example:
C:\Program Files (x86)\Bentley\ProjectWise\Example Datasets

\BS1192\BS1192 Template for SQL Server.aam
8. Click Next. On the next page, you specify where to import the projects, folders, and/or documents.
The window on the left shows a list of the projects and folders contained in the export file. The
window on the right shows the folder list of the destination datasource.
a. In the left window, select Manually exported folders.
b. In the right window, select the Documents root folder as the destination.
c. Click the arrow button (->).
d. From the Choose storage area list, select the storage area that will be used in the event that the
Import Wizard encounters folders with an associated storage area that does not exist in the
destination datasource.
e. Click Import.
The wizard displays the progress of the import.
9. When the import is complete, click Close.
Importing the template adds a few environments, a couple interfaces, several states, a group, and
many user lists.
Importing the template also adds various projects and folders with these datasource objects already
assigned.
ProjectWise
120

Presetting the Full Text Index Storage Location
Inside one of the folders is a file called bs1192_rules.xlsx, which contains BS1192-specific
workflow rules. You need to export the bs1192_rules.xlsx file from ProjectWise Explorer, and
then use that file to import the BS1192-specific workflow rules into ProjectWise Administrator.
10. Export the bs1192_rules.xlsx file:
a. In ProjectWise Explorer, log in to the datasource where you imported the template.
b. Under the Documents root folder, navigate to and select the folder,
System Admin\Rules Engine Configuration.
c. In the document list, select the bs1192_rules.xlsx file and select Document > Export.
d. In the Document Export Wizard, select Export and click Next. On the next page, select an export
location and click Next. The file is exported. Click Finish.
11. Open the local bs1192_rules.xlsx file to review and edit settings as needed before importing to
The Super User and Rollback User specified on the Settings tab of the worksheet must exist in the
datasource, otherwise import will fail. The Super User will need elevated privileges above those of
normal users, and the Rollback User must be a member of the Administrator group in the datasource.
Either add these users to the datasource, or on the Settings tab of the worksheet add the names of
existing users who have the appropriate permissions. They can be the same user, if necessary.
12. Import the rules from the bs1192_rules.xlsx file:
a. In ProjectWise Administrator, log in to the datasource where you want to import the workflow
rules.
b. Right-click the Rules Engine node and select Import Rules.
c. Navigate to and select the exported local bs1192_rules.xlsx file and select Open.
The rules are imported to the database. Note that nothing actually displays under the Rules Engine
node - this is expected.
13. Now go back to ProjectWise Explorer, select the exported bs1192_rules.xlsx file and select
Document > Import to save any changes made to this file back to ProjectWise.
Presetting the Full Text Index Storage Location

When you install ProjectWise Indexing Service, or when you install ProjectWise Integration Server with
Full Text Indexing enabled, ProjectWise sets the default full text index storage location to
C:\ProgramData\Bentley\pw-index-storage.
As you run text extractions, ProjectWise downloads copies of documents from the datasource and stores
them in a temporary extraction folder on the ProjectWise Integration Server computer. For each
document that gets processed, ProjectWise creates an intermediate file (*.DMSINDEX) which contains
the text extracted from the document. These intermediate files get stored in a subfolder (one subfolder
for each indexed datasource) under the main index storage folder. For example:
C:\ProgramData\Bentley\pw-index-storage\ed0bd9c2bec8-4230-89f9-0852c75c7140\
0a4d8ed5-fbd7-4db2-943c-d22cb98efd69.dmsindex
0b4893b0-4a86-4d31-af30-1aac40b689f4.dmsindex
0bbb8aa2-49de-4819-99ab-251f69872dfd.dmsindex
0c3ea069-efb6-4d7b-bee6-7992a674afb7.dmsindex
0c25a091-bbe2-4f7d-a2c2-810873bd96f0.dmsindex
ProjectWise
121

Moving Document Processors to a Secondary Server
If you know you need the index storage to be located in a different folder or on a different drive, you can
preset the index storage location using the following procedure, and then install ProjectWise Indexing
Service or ProjectWise Integration Server as needed. (See the ProjectWise Administrator help for details
about changing the index storage location after installation.)
To Preset the Full Text Index Storage Location

1. Open the Windows Registry Editor on the computer on which you are about to install ProjectWise
Integration Server or ProjectWise Indexing Service.
2. Create the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Bentley\ProjectWise\Automated File
Processing
3. Under that key, create a string called FtrIndexDataDir, and for its value enter the path to the
location where you want the index storage folder to be.
For example: D:\Bentley\pw-index-storage
4. Close the Windows Registry Editor.
The folder specified in the FtrIndexDataDir string will be created when the first extraction
occurs.
Moving Document Processors to a Secondary Server

Support for full text search, thumbnail images and file property display requires a number of processors
to be running on the Integration Server that extract the appropriate data from files managed by
ProjectWise and store that data in the ProjectWise database (or on the Indexing Service computer, in
the case of full text indexing). These processors can be somewhat resource intensive, and depending on
the amount of documents that are changing and how current the user wants to keep the extracted data,
this could potentially affect the overall performance of the ProjectWise Integration Server (and
therefore the perceived performance of ProjectWise in general).
To reduce the load on the ProjectWise Integration Server computer, you can offload the document
processors to a second computer. These two computers would then coordinate through ProjectWise
Orchestration Framework Service and the Orchestration Framework database.
To Move the Document Processors to a Secondary Server

1. Assume a preexisting ProjectWise Integration Server V8i (SELECTseries 4) with all document
processors installed.
2. Following the instructions in this Implementation Guide, on a second computer, install ProjectWise
Integration Server and all prerequisites (including MSMQ, Microsoft Indexing Service, MicroStation
V8i (SELECTseries 3), ProjectWise Orchestration Framework Service V8i (SELECTseries 4), and so
on).
During ProjectWise Orchestration Framework Service installation:
when you get to the Configure Shepherd Credentials dialog, be sure to use the same Windows
account that is being used to run the Orchestration Framework Service on the original ProjectWise
Integration Server.
ProjectWise
122

Installing ProjectWise Servers on Computers with Non-English Regional Settings
when asked for the database to be used by the ProjectWise Orchestration Framework Service,
select the same database that is being used by the original ProjectWise Integration Server. It is also
possible at this time to designate a new Orchestration Framework database on the second server and
reconfigure the ProjectWise Orchestration Framework Service on the original ProjectWise
Integration Server to point to this new Orchestration Framework database.
3. On the second computer that you just installed ProjectWise Integration Server, in order to have this
server not require a ProjectWise Integration Server license, edit the dmskrnl.cfg file and add the line
FullTextIndexSrv=1 to the [TeamMate] section. This will prevent this instance of ProjectWise
Integration Server from performing any of the real ProjectWise Integration Server functionality.
4. Install ProjectWise Automation Service Administrator on the original ProjectWise Integration
Server. Open it and connect the Orchestration Framework Browser to the database instance used by
both computers. You should notice that there are now Dispatchers and Processors running on both
computers. Looking at the monitor for one of the document processor instances you will notice that
there are now two parallel sets of dispatchers and processors for that instance that are not
connected. Close Automation Service Administrator. Your next step is to connect those parallel paths.
5. On the original ProjectWise Integration Server computer, open a command prompt and navigate to
the ...\ProjectWise\bin folder and type:
Dmsafpengine.exe -makeHead
This entry is case-sensitive so use an uppercase H.
6. On the second computer, open a command prompt and navigate to the ...\ProjectWise\bin
folder and type:
Dmsafpengine.exe -makeTail
7.
8.
9.
10.
This entry is case-sensitive so use an uppercase T.

Open Automation Service Administrator again and reconnect to the Orchestration Framework
Browser and select monitor on one of the instances. You should notice that the parallel paths are
now connected and the processors have been removed from the original ProjectWise Integration
Server and the dispatcher from the original ProjectWise Integration Server is connected to
processors running on the second computer.
Using ProjectWise Administrator, select Registered Full Text Indexing Services and make sure that
the second computer shows up in the list. If not, use the New > Indexing Service to add it. Log in to
each datasource and select Document Processors > Full Text Indexing > Properties and make sure
that the Indexing Service field shows the name of the second computer, if not select it from the list
and click Register Server.
Using ProjectWise Administrator, select one of the document processors and select a folder for
reprocessing and force processing now.
Using Automation Service Administrator, validate that the queues of the processors on the second
computer are populated with documents for processing.
Installing ProjectWise Servers on Computers with Non-English

Regional Settings
There is an installation issue with the ProjectWise server products on computers with non-English
regional settings. This issue prevents ProjectWise performance counters from being registered during
installation of ProjectWise Integration Server, ProjectWise Caching Server, and ProjectWise Gateway
Service, and thus prevents these servers from starting correctly after installation. As a workaround,
follow these steps to add missing registry items that will allow the respective ProjectWise servers to
start correctly.
ProjectWise
123

Setting Up ProjectWise Integration Servers in a Clustered Environment
1. Using the Windows Registry Editor, open the registry and go to the key HKey_Local_Machine
\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib and export the key
named 009 to a file.
2. Open that file in a text editor and change all occurrences of 009 to the appropriate Primary Language
Identifier. See http://msdn.microsoft.com/en-us/library/windows/desktop/dd318693(v=vs.85).aspx
for details.
3. Import that registry file and a new key HKey_Local_Machine\SOFTWARE\Microsoft
\Windows NT\CurrentVersion\Perflib should be created that matches your Primary
Language Identifier.
4. Re-register the performance counters:
regsvr32 dmsdbperf.dll
regsvr32 dmskrnlperf.dll
regsvr32 dmssrvperf.dll
We are working with Microsoft to resolve this issue and eliminate the need for this workaround.
Setting Up ProjectWise Integration Servers in a Clustered

Environment
ProjectWise Integration Server supports Cluster Service and Network Load Balancing features of
Windows Server 2008 and 2012. This section discusses the basic configuration of ProjectWise
Integration Servers in a clustered environment. It is recommended that you consult Bentley
Professional Services for assistance with setting this up in production.
Note: ProjectWise User Synchronization Service, and the Automated File Processing features delivered
with ProjectWise Integration Server are NOT cluster-aware and therefore will not fail over if the server
they are installed on fails. These services can be installed on servers in a cluster, however in the event of
a failure manual steps must be taken to ensure they continue to function correctly.
Setting Up Your Server Cluster

1. Before installing any ProjectWise software, you must first set up your cluster. This involves creating
a cluster using the Windows Cluster Management tool and then specifying each server that will be a
part of the cluster. See Microsoft documentation for details on this configuration. When ProjectWise
clients need to connect to the ProjectWise Integration Server, they point to the name of the cluster,
which will then decide which ProjectWise Integration Server will handle the request.
2. Once your basic cluster is configured, the next step is to set up a database to host the ProjectWise
database. Follow your normal database setup procedures, noting that the database server must
reside outside the cluster. Once the database is set up, on each ProjectWise Integration Server
computer in the cluster you must create an ODBC datasource that points to the database. Each of
these ODBC datasources must have the same name.
3. Next you need to decide how you will store your files. Your storage area must reside outside the
cluster. You can either host the storage area on a ProjectWise Caching Server outside the cluster, or
you can provision shared storage outside the cluster such that all clustered servers can access it.
Examples of shared storage include SAN (Storage Area Network), NAS (Network Attached Storage),
or SMB Share. If you use shared storage, the ProjectWise Integration Server service must be running
as a user that has rights to the shared storage location. Make sure this is set before you create any
ProjectWise
124

Setting Up ProjectWise Integration Servers in a Clustered Environment
datasources. If needed, you can change the user for the ProjectWise Integration Server service
through the Services window. Make sure you restart the service after changing the user.
4. Make sure the following reside outside the cluster:
the ProjectWise database
the full text index catalog (if full text indexing is used)
ProjectWise Caching Server
Installing ProjectWise Integration Servers and Configuring the Datasource

Once you set up the cluster, the next step is to install ProjectWise Integration Server on each server in
the cluster. All installation paths and other details must be the same on each server. After installation,
you will create a datasource on one server, modify the dmskrnl.cfg file accordingly, and then copy
the dmskrnl.cfg file to the rest of the ProjectWise Integration Servers in the cluster.
To Configure a Datasource To Be Used in a Clustered Environment
1. Install ProjectWise Integration Server on each server in the cluster.
2. If you are using shared storage for your storage area, make sure the ProjectWise Integration Server
service is running as a user who has access to the shared storage location and rights to run a service
on the local server. This change must be made on all servers in the cluster. Restart the ProjectWise
Integration Server service after you make your changes.
3. On all but one of these servers, stop the service for the ProjectWise Integration Server.
4. On the server with the service still running, install ProjectWise Administrator and use it to create
your datasource.
When you create your datasource and you get to the Create Administrator and Storage dialog, the
storage area node (Host field) defaults to the ProjectWise Integration Server computer on which you
are working.
If you are using a ProjectWise Caching Server outside the cluster, set the Host field to the server
name on which the ProjectWise Caching Server is installed, and in the Path field specify the storage
areas folder path on that server.
or
If you are using shared storage, leave the Host field as is (pointing to the local server), and in the
Path field specify the address of the shared storage location. For example: \\sharedstorage
\pw_storage
6. After you have created your datasource, stop the service for that ProjectWise Integration Server.
7. Open that ProjectWise Integration Server's dmskrnl.cfg file.
8. Uncomment the ServerName and ServerIPAddress properties and set their value to the
clusters name and IP address, respectively. For example:
[TeamMate]
...
ServerName=mycluster.mydomain.com
ServerIPAddress=192.168.1.10
ProjectWise
125

Adding Servers to ProjectWise Integration Server's Trusted Servers List
9. If you want ProjectWise to only respond to requests that come in on the cluster network interface,
uncomment the BindAddress properties under the [Broadcast] and [Listener] sections
and set their value to the cluster's IP address. For example:
[Broadcast]
...
BindAddress=192.168.1.10 (cluster IP address)
...
[Listener]
...
BindAddress=192.168.1.10 (cluster IP address)
Note: This causes ProjectWise Integration Server's service to attach to this address on startup. If this
address is not assigned to an NIC on the server the service will fail to start. Do not set the
BindAddress if you want ProjectWise to respond to requests on more than one adapter / IP
address, or if you are configuring ProjectWise with a hardware load balancer.
10. Find the FileAcccessTokenMasterKey, LoginTokenMasterKey1, and
LoginTokenMasterKey2 properties under the TeamMate section, and delete everything after the
= for each property, so that they now look like this:
[TeamMate]
...
FileAccessTokenMasterKey=
...
LoginTokenMasterKey1=
LoginTokenMasterKey2=
11. Add an entry in the Server Name Resolution section with the formatting, cluster IP address =
cluster name.
12.
13.
14.
15.
16.
For example:
[ServerNameResolution]
192.168.1.10=mycluster.mydomain.com
Save and close the dmskrnl.cfg file.
Restart the service for that ProjectWise Integration Server.
Copy the newly modified dmskrnl.cfg file to the rest of the ProjectWise Integration Servers in the
cluster.
Start the services for the rest of the ProjectWise Integration Servers in the cluster.
If using shared storage, log in to ProjectWise Administrator, select the Storage areas datasource
node, right-click the storage area that was just created and select Properties. In the Computer
name or IP address field, enter the cluster name and click OK.
Adding Servers to ProjectWise Integration Server's Trusted

Servers List
The IP addresses of computers on which you install the following ProjectWise applications need to be
added to the Trusted Servers list in the ProjectWise Integration Server's dmskrnl.cfg file:
ProjectWise

Bentley i-model Composition Server Administrator
ProjectWise Automation Service Administrator
126

ProjectWise Distribution Service Administrator
ProjectWise Web Server and Web View Server (only if using single sign-on with ProjectWise Web
Parts)
To Add a Server's IP Address to the Trusted Servers List

1. Open the ProjectWise Integration Server's dmskrnl.cfg file.
2. Find the [Trusted Servers] section.
3. Under the [Trusted Servers] line, add a new line that includes your server's IP address.
You can either add a specific IP address, or you can use a subnet mask. You can also add a new line
for each ProjectWise application, assuming that they are installed on different computers.
For example:
[Trusted Servers]
ProjectWise Web Server=194.215.205.19
Bentley i-model Composition Server for
PDF=192.168.100.0
255.255.255.0
The name before the = can be any name you choose.
The number after the = is the IP address.
The number after the IP address (with a space in between) is the optional subnet mask.
ProjectWise
127

ProjectWise
128
ProjectWise User Synchronization Service

Configuration 4
ProjectWise User Synchronization Service is the server module that lets you create user accounts in the
datasource, based on existing Windows domain or Active Directory accounts, and that also leverage the
credentials of those accounts. Once these ProjectWise user accounts are created, you can use
ProjectWise User Synchronization Service to keep those accounts synchronized with any changes made
to their domain or Active Directory counterparts.
The installer for ProjectWise User Synchronization Service has two options:
ProjectWise User Synchronization Service Administrator
ProjectWise User Synchronization Service Engine
You can install both options on the same computer, or you can install each option on a separation
computer. The ProjectWise User Synchronization Service Administrator option requires ProjectWise
Administrator.
The ProjectWise User Synchronization Service Engine runs as a native Windows service, and is managed
through the User Synchronization Service datasource node in ProjectWise Administrator (which is
available when the ProjectWise User Synchronization Service Administrator option is installed on the
ProjectWise Administrator computer).
After installation, see User and Group Management > User Synchronization Service in the ProjectWise
Administrator help.
Note: If your ProjectWise Integration Server cannot access the local domain controller and authenticate
Windows users, you can install ProjectWise User Synchronization Service on a local network to act as an
intermediate login provider for ProjectWise users with Windows accounts.
Before You Install ProjectWise User Synchronization Service

1. ProjectWise User Synchronization Service can be, but does not need to be, installed on the same
computer as ProjectWise Integration Server.
2. If you plan to install the ProjectWise User Synchronization Service Engine on one computer and then
install ProjectWise User Synchronization Service Administrator on another, make sure both
computers are on the same domain.
3. Before installing ProjectWise User Synchronization Service Administrator, you must first install
ProjectWise Administrator on this computer.
4. If you are only installing ProjectWise User Synchronization Service Engine, then you must install
ProjectWise Prerequisite Runtimes (available from ProjectWise Server Setups).
To Install ProjectWise User Synchronization Service

ProjectWise
129
ProjectWise User Synchronization Service Configuration

2. Click Install next to ProjectWise User Synchronization Service.
If ProjectWise Administrator is not installed, the next page that opens tells you that ProjectWise
Administrator is not detected, and that you can only install the ProjectWise User Synchronization
Service Engine on this computer. If you just want to install the ProjectWise User Synchronization
Service Engine, then click Next, otherwise click Cancel to exit the Setup Wizard, install ProjectWise
Administrator, then go back to step 1 of this procedure to launch the Setup Wizard again.
or
If ProjectWise Administrator is already installed, the Custom Setup page opens.
The Custom Setup page shows you the features that can be installed, and the location to which the
product will be installed.
If ProjectWise Administrator is installed, you will see these options:
ProjectWise User Synchronization Service Administrator
If ProjectWise Administrator is not installed, you will see only this option:
ProjectWise
130


6. (Optional) To change whether or not a feature gets installed, click the feature's icon and select the
appropriate option from the menu. Items with an X next to them will not be installed.

If ProjectWise Administrator is already installed, you will not be able to change the installation
location, and ProjectWise User Synchronization Service will automatically be installed to the same
location as ProjectWise Administrator.
or
If ProjectWise Administrator is NOT installed, and also no other module (not including ProjectWise
Orchestration Framework Service) from this release is installed, then you can either accept the
default installation location, or click the Change button to change it. Whichever installation location
you select here, each subsequent module (not including ProjectWise Orchestration Framework
Service) you install from this release will automatically be installed to the same location.
C:\Program Files\Bentley\ProjectWise.
C:\Program Files (x86)\Bentley\ProjectWise.
9. When the Service Options page opens, type a valid Windows Domain name, Account Name and
Password, then click Next.
ProjectWise
131

To Set Up ProjectWise User Synchronization Service as an Intermediate Login Provider for Users with Windowsbased Accounts
This account must have appropriate rights to connect to the Domain that you plan to synchronize
with the ProjectWise datasources.
12. If you installed the ProjectWise User Synchronization Service Engine, then after installation, make
sure the ProjectWise User Synchronization Service is started in the Services window.
To Set Up ProjectWise User Synchronization Service as an

Intermediate Login Provider for Users with Windows-based
Accounts
1. Install ProjectWise User Synchronization Service on a computer in the local area network (LAN) that
can access the local domain controller.
2. Open the ProjectWise User Synchronization Service's dmskrnl.cfg file in a text editor.
3. Uncomment the following line and set the value after the = to be the host name of the computer on
which ProjectWise User Synchronization Service is installed:
UserSyncService=<User Synchronization Service host name>
4. Sill in the dmskrnl.cfg file, add the IP address of the ProjectWise User Synchronization Service
host computer to the [Trusted Servers] list.
5. Save and close the dmskrnl.cfg file.
ProjectWise
132

6. Make sure that the account under which ProjectWise User Synchronization Service runs is a logical
user account (not a Windows-based account), and that the user's user setting Enable as delegate
user is turned on.
ProjectWise
133

ProjectWise
134
ProjectWise Caching Server Configuration
ProjectWise storage areas can exist on the ProjectWise Integration Server computer, but they can also
be hosted on another computer. ProjectWise Caching Server is the ProjectWise server to install when
you want to set up and host a storage area on a computer other than the ProjectWise Integration Server
computer. ProjectWise Caching Server can also be used for storing local copies of files in remote storage
areas, to improve access speed.
When users create folders or projects in ProjectWise, they associate each folder or project with a
particular storage area so that all files added to that folder or project will be stored in the associated
storage area. This storage area, defined in ProjectWise Administrator, can be located on the ProjectWise
Integration Server computer, but for performance reasons you may decide to create multiple storage
areas for your datasource, each located on a different computer. Before you can define the location of a
storage area in ProjectWise Administrator, you must first install ProjectWise Caching Server on the
computer that will host the storage area.
Once installed, use ProjectWise Administrator to set up a storage area on the ProjectWise Caching
Server's computer. The ProjectWise Administrator you work from can be, but does not need to be,
installed on the same computer as ProjectWise Caching Server.
Before You Install or Upgrade ProjectWise Caching Server

2. ProjectWise Caching Server cannot be installed on a computer on which ProjectWise Integration
Server, ProjectWise Gateway Service, or ProjectWise Indexing Service is already installed.
3. Make sure that the computers on which you install ProjectWise Integration Server and all
ProjectWise Caching Servers have their clocks synchronized with the time of an authoritative
computer. If the clocks are not properly synchronized, then any tokens issued by ProjectWise
Integration Server may expire prematurely when a user attempts to check out a document, causing
the operation to fail. See the following Microsoft article for details:
http://technet.microsoft.com/en-us/library/cc773013(WS.10).aspx
5. (Windows Server 2003 computers only) Manually add ProjectWise broadcasting and listening ports
(5799 and 5800) to the Windows Firewall exception list on this ProjectWise Caching Server
computer.
a. Select Control Panel > Windows Firewall.
The Windows Firewall dialog opens. The General tab displays whether the firewall is on or off.
b. Assuming the firewall is ON (recommended), select the Exceptions tab and click Add Port.
c. To add port 5799, set name to ProjectWise UDP, set port to 5799, and set protocol to UDP.
d. To add port 5800, set name to ProjectWise TCP, set port to 5800, and set protocol to TCP.
Note: The ProjectWise Caching Server installer takes care of this automatically when installing on
Windows Server 2008 or later.
ProjectWise
135

To Install ProjectWise Caching Server
6. If you have an existing ProjectWise Caching Server V8i or later installed, you can use the ProjectWise
Caching Server V8i (SELECTseries 4) installer to upgrade the old version to the new version. Note
that the new version will be installed to the default location, rather than the location to which the old
version was previously installed. If you have additional ProjectWise modules installed from the same
older (V8i or later) release version, see Upgrading to ProjectWise V8i (SELECTseries 4) > Precautions
for the recommended workflow for upgrading.
7. If installing on Windows Server 2008 or later and you plan to use the Product Activation Wizard as
launched from the final page of the Setup Wizard, then you must launch the master ProjectWise
Server Setups installer using the Run as Administrator option. This ensures that the Product
Activation Wizard is also run as an administrator, which in turn ensures that the licensing
information you enter gets registered to the correct location in the Windows Registry.

2. Click Install next to ProjectWise Caching Server.

ProjectWise
136

The Custom Setup page opens.
change it.
Note: The Change button will not display on this installer if another application of the same
architecture (64-bit or 32-bit) from this release is already installed; if that is the case, ProjectWise
Caching Server will simply be installed to the same location as the previously installed application of
the same architecture.
Note: When upgrading from an existing ProjectWise Caching Server V8i or later, the Change button
8. (Optional) On the last page of the wizard, the options to launch the License Management tool and
start the servers service are on by default. You can turn either of these options off if you prefer to do
them later.
ProjectWise
137

To Upgrade to ProjectWise Caching Server V8i (SELECTseries 4)
9. Click Finish.
If you selected Launch License Management Tool, the Product Activation Wizard opens for you to
configure licensing for this module.

ProjectWise
138

2. Click Install next to ProjectWise Caching Server.

A second ProjectWise Server Setups window opens to show you the version(s) of ProjectWise
Caching Server currently installed and what your installation options are. You may see the following
options depending on the existing configuration:
Install
ProjectWise Caching Server V8 XM Edition (8.9.x) or 2004 Edition (8.5.x).
Upgrade
Change
Remove
3. (Optional) If ProjectWise Caching Server V8 XM Edition (8.9.x) or 2004 Edition (8.5.x) is currently
you do not have to remove these particular versions, in order to install the new version.) When
or
previous procedure, To Install ProjectWise Caching Server.
Note: If the upgrade happens to fail for some reason of the system, you may need to repair and then
uninstall the old version of ProjectWise Caching Server manually, using Add / Remove Programs.
ProjectWise
139

ProjectWise
140
ProjectWise Gateway Service Configuration
ProjectWise Gateway Service is the server module to install for datasource list publishing.
For example, when the ProjectWise Integration Server is on a computer that your ProjectWise Explorer
clients cannot access, you can install a ProjectWise Gateway Service on a computer that both the clients
and the ProjectWise Integration Server can access, and then configure the ProjectWise Gateway Service
to retrieve the datasource list from the server. ProjectWise Explorer clients on the same subnet as the
ProjectWise Gateway Service, or those connected to it using the ProjectWise Network Configuration
Utility, will be able to see the ProjectWise Integration Server's datasources, as published through the
ProjectWise Gateway Service.
Before You Install or Upgrade ProjectWise Gateway Service

2. ProjectWise Gateway Service cannot be installed on a computer on which ProjectWise Integration
Server, ProjectWise Caching Server, or ProjectWise Indexing Service is already installed.
4. (Windows Server 2003 computers only) Manually add ProjectWise broadcasting and listening ports
(5799 and 5800) to the Windows Firewall exception list on this ProjectWise Gateway Service
computer.
c. To add port 5799, set name to ProjectWise UDP, set port to 5799, and set protocol to UDP.
d. To add port 5800, set name to ProjectWise TCP, set port to 5800, and set protocol to TCP.
Note: The ProjectWise Gateway Service installer takes care of this automatically when installing on
Windows Server 2008 or later.
5. If you have an existing ProjectWise Gateway Service V8i or later installed, you can use the
ProjectWise Gateway Service V8i (SELECTseries 4) installer to upgrade the old version to the new
version. Note that the new version will be installed to the default location, rather than the location to
which the old version was previously installed. If you have additional ProjectWise modules installed
from the same older (V8i or later) release version, see Upgrading to ProjectWise V8i (SELECTseries 4)
> Precautions for the recommended workflow for upgrading.
6. If installing on Windows Server 2008 or later, and you plan to use the Product Activation Wizard as
ProjectWise
141

To Install ProjectWise Gateway Service
Note: ProjectWise Gateway Service only requires a license if you enable local file caching on this
computer. If you do not plan to enable local file caching, then ProjectWise Gateway Service does not
require a license, and you do not need to run the Product Activation Wizard.

2. Click Install next to ProjectWise Gateway Service.
ProjectWise
142

The Custom Setup page opens.
change it.
Note: The Change button will not display on this installer if another application of the same
architecture (64-bit or 32-bit) from this release is already installed; if that is the case, ProjectWise
Gateway Service will simply be installed to the same location as the previously installed application
of the same architecture.
Note: When upgrading from an existing ProjectWise Gateway Service V8i or later, the Change button
8. On the last page of the wizard, the option to Launch License Management Tool is OFF by default
(because ProjectWise Gateway Service does not normally require a license), and the option to start
the servers service is ON by default. If you plan to use this ProjectWise Gateway Service for local file
caching, then turn on Launch License Management Tool, otherwise you can leave it off.
ProjectWise
143

To Upgrade to ProjectWise Gateway Service V8i (SELECTseries 4)
9. Click Finish.

2. Click Install next to ProjectWise Gateway Service.
ProjectWise
144

A second ProjectWise Server Setups window opens to show you the version(s) of ProjectWise
Gateway Service currently installed and what your installation options are. You may see the
following options depending on the existing configuration:
Install
ProjectWise Gateway Service V8 XM Edition (8.9.x) or 2004 Edition (8.5.x).
Upgrade
Change
Remove
3. (Optional) If ProjectWise Gateway Service V8 XM Edition (8.9.x) or 2004 Edition (8.5.x) is currently
you do not have to remove these particular versions, in order to install the new version.) When
or
ProjectWise
145

previous procedure, To Install ProjectWise Gateway Service.
uninstall the old version of ProjectWise Gateway Service manually, using Add / Remove Programs.
ProjectWise
146
ProjectWise Indexing Service Configuration
ProjectWise Indexing Service is the server module to install when you want the full text indexing
features text index catalog (for one or more datasources) to be hosted and maintained on a computer
other than the ProjectWise Integration Server computer. In this configuration, the ProjectWise
Integration Server forwards full text searches, and any text extraction updates, to the ProjectWise
Indexing Service, which in turn uses its own local Windows Search or Microsoft Indexing Service.
Once ProjectWise Indexing Service is installed, you need to register this ProjectWise Indexing Service
computer with the ProjectWise Integration Server in ProjectWise Administrator. Once the computer is
registered, you will be able to designate this ProjectWise Indexing Service as the Indexing Service to use
for any of that ProjectWise Integration Server's datasources.
You can also have more than one Indexing Service computer registered and then decide on a perdatasource basis (when configuring text indexing extractions) which Indexing Service will maintain the
datasource's full text index catalog.
Indexing Service for maintaining the full text index catalog, the SharePoint search integration feature of
ProjectWise Web Server does not currently support this configuration and only works when the full text
index catalog is located on the ProjectWise Integration Server computer. Because of this, you should
turn off the ProjectWise Indexing Connector for SharePoint feature when installing ProjectWise
Indexing Service.
Before You Install ProjectWise Indexing Service

1. On another computer, you must have already installed a ProjectWise Integration Server with the
Automated File Processing - Full Text Indexing option enabled.
3. ProjectWise Indexing Service cannot be installed on a computer where ProjectWise Integration
Server, ProjectWise Caching Server, or ProjectWise Gateway Service is already installed.
.NET Framework 3.5
Windows Search (if using Windows Server 2012)
Microsoft Indexing Service (if using Windows Server 2008)
Select features page. Turn on .NET Framework 3.5 Features and Windows Search Service. Click
Next, then click Install. After installation, make sure Windows Search is running.
To install .NET Framework on Windows Server 2008: Open Server Manager. Right-click Features in
the left pane and select Add Features. In the Add Features Wizard, turn on .NET Framework 3.5
Features. Click Next, then click Install.
ProjectWise
147

To Install ProjectWise Indexing Service
To install Microsoft Indexing Service on Windows Server 2008: Open Server Manager. Expand Roles in
the left pane. Right-click the File Services role and select Add Role Services. In the Add Role
Services wizard, turn on Windows Server 2003 File Services (it automatically enables the
Indexing Service feature listed below it). Click Next, then click Install. After installation, make sure
Microsoft Indexing Service is running.
Note: Windows Search Service is currently enabled, you will have to disable it first before you can
enable Windows Server 2003 File Services and the Indexing Service.
5. If you need to preset the index storage folder to a location other than the default, you must do so
before installing this ProjectWise Indexing Service.

2. Click Install next to ProjectWise Indexing Service.
The Custom Setup page opens, showing you the location to which the product will be installed.
Note: The ProjectWise Indexing Connector for SharePoint feature of ProjectWise Indexing Service is
currently unsupported and should not be installed.
ProjectWise
148

Note: The Change button will not display on this installer if another 64-bit application from this
release is already installed; if that is the case, ProjectWise Indexing Service will simply be installed to
the same location as the previously installed application.
ProjectWise
149

To Register a Standalone ProjectWise Indexing Service
8. Click Finish.

1. In ProjectWise Administrator, log in to at least one datasource for a particular server.
2. Under that server, select the Registered Full Text Indexing Services node.
The <local> server listed represents the ProjectWise Integration Server's built-in Indexing Service.
ProjectWise
150

3. Right-click the Registered Full Text Index Servers node and select New > Index Server.
The New Index Server Properties dialog opens.
ProjectWise
151

4. In the Server name field, type a display name for the Indexing Service.
5. In the Server DNS name or IP address field, type the actual computer name or IP address of
computer on which the ProjectWise Indexing Service is installed.
6. Click OK.
The new Indexing Service is added to the list of Registered Full Text Index Servers. You can later
modify its properties by right-clicking it and selecting Properties, or you can remove it from the list
by right-clicking and selecting Delete.
ProjectWise
152
ProjectWise Explorer Configuration
Installing ProjectWise Explorer and iDesktop Integration

ProjectWise Explorer is the main client interface for ProjectWise, from which users can check out, open,
modify, and otherwise manage their ProjectWise documents.
iDesktop Integration is an option of the ProjectWise Explorer installer that adds ProjectWise
functionality to supported applications such as MicroStation, AutoCAD, Revit, Microsoft Office, and
others. When an application is integrated with ProjectWise, you can access your datasources, check out
and open ProjectWise documents, and check them back in, all from inside the application without
having to open ProjectWise Explorer. The level of integration differs from application to application, but
typically the commands affected in each application are those which open and save files, automatically
presenting you the option to open from and save to ProjectWise rather than the Windows file system.
After installation, open ProjectWise Explorer by selecting Start > All Programs > Bentley >
ProjectWise V8i (SELECTseries 4) > ProjectWise Explorer. If the ProjectWise Explorer client you just
installed is on the same computer or within the same subnet as the ProjectWise Integration Server or a
ProjectWise Gateway Service that is publishing datasource lists, ProjectWise Explorer will automatically
display that servers datasources, assuming the server is running and you have permission to see that
servers datasources. If the ProjectWise Explorer client is not on the same subnet as the ProjectWise
Integration Server or a ProjectWise Gateway Service, you need to configure the ProjectWise network on
the ProjectWise Explorer client computer so that the necessary datasources display in ProjectWise
Explorer. See Connecting Individual Clients to the Server for details.
Before You Install or Upgrade ProjectWise Explorer

2. Make sure Microsoft .NET Framework 3.5 SP1 is installed (available from ProjectWise Client Setups,
if necessary).
.NET Framework is required for:
Office 2007 integration
ProjectWise Session File Manager in AutoCAD
3. Install the applications you want to integrate with ProjectWise Explorer.
See the ProjectWise readme for a list of supported applications.
4. Office 2010 integration requires Office 2010 Primary Interop Assemblies. Office 2007 integration
requires Office 2007 Primary Interop Assemblies. These may already be installed as part of your
Office installation. Make sure the necessary version is installed before you install ProjectWise
Explorer with iDesktop Integration support for your particular version of Microsoft Office.
Office 2007 Primary Interop Assemblies is available from ProjectWise Client Setups, if necessary. If
you need Office 2010 Primary Interop Assemblies, you can download it from here: http://
www.microsoft.com/download/en/details.aspx?id=3508
ProjectWise
153

5. Make sure Microsoft Core XML Services (MSXML) 6.0 is installed (available from ProjectWise Client
Setups, if necessary).
6. Make sure Microsoft DirectX 9.0c Runtime Components is installed (available from ProjectWise
Client Setups, if necessary).
Microsoft DirectX 9.0c Runtime Components is required for:
7.
8.
9.
10.
11.
12.
13.
14.
15.
Bentley Viewing, Redlining, and Printing control

Spatial Extension
(Windows Server 2008 only) If installing ProjectWise Explorer on a computer on which ProjectWise
Integration Server is already installed, the installer will display a Files in Use message. If this
happens, you can simply click Ignore and the ProjectWise Explorer installation will continue without
any problems. If you want to avoid this message, you can stop the ProjectWise Integration Server's
service before you install ProjectWise Explorer, and then restart the service once installation is
complete.
Make sure the editing application you want to integrate with is already installed.
If two MicroStation V8i versions are installed, then turning on the iDesktop Integration option for
MicroStation V8i during ProjectWise Explorer installation will install iDesktop Integration support
for both versions of MicroStation.
If necessary you can run both ProjectWise Explorer V8i (SELECTseries 4) and ProjectWise Explorer
V8 XM Edition on the same computer.
If you have an existing ProjectWise Explorer V8i or later installed, you can use the ProjectWise
Explorer V8i (SELECTseries 4) installer to upgrade the old version to the new version. If you have
additional ProjectWise modules installed from the same older (V8i or later) release version, see
Upgrading to ProjectWise V8i (SELECTseries 4) > Precautions for the recommended workflow for
upgrading.
A normal uninstallation of ProjectWise Explorer removes the PW.CFG and MCM.CFG files related to
MicroStation integration. Likewise, the automatic upgrade process described above removes the
existing PW.CFG and MCM.CFG files and replaces them with new ones. If you have made changes in
these files, please make a copy of them before you upgrade.
(Vista computers only) If you plan to use the automatic upgrade feature to upgrade your existing
installation of ProjectWise Explorer V8i (SELECTseries 1) or (SELECTseries 2) to ProjectWise
Explorer V8i (SELECTseries 4), then before you perform the upgrade, make sure you install the
ProjectWise Prerequisite Runtimes, available from ProjectWise Client Setups.
(Existing Revit integrations only) If you are upgrading to ProjectWise Explorer V8i (SELECTseries 4)
(whether using the automatic upgrade feature or not) and you also have the ProjectWise Integration
Module for Autodesk Revit installed for an earlier version of ProjectWise Explorer, then before you
upgrade, you must first uninstall the Revit integration module through Add / Remove Programs. The
ProjectWise Explorer V8i (SELECTseries 4) installer will then install the necessary Revit integration.
On the ProjectWise Client Setups master installer, there are now two ProjectWise Explorer installers:
ProjectWise Explorer - launches the ProjectWise Explorer installer as usual, but does not install
the new Bentley DGN Navigator Control
ProjectWise Explorer with DGN Navigator Control - launches a ProjectWise Explorer Bundle
installer, which installs the ProjectWise Prerequisite Runtimes first, then launches the
ProjectWise Explorer installer, and then finally launches the Bentley DGN Navigator Control
installer.
Make your selection based on whether you want to install the DGN Navigator Control or not.
If you have an existing ProjectWise Explorer V8i or later installation, both of the installers will
upgrade your installation to the current version as usual. The only difference in the upgrade
ProjectWise
154

workflow is that if you select the ProjectWise Explorer with DGN Navigator Control option,
ProjectWise Client Setups will not inform you about the existing installation. However, when the
ProjectWise Explorer installer finally launches, it will inform you that an upgrade will take place as
usual.
Finally, if you install ProjectWise Explorer without the DGN Navigator Control, then later decide you
want to install the DGN Navigator Control, simply return to ProjectWise Client Setups and launch the
bundle installer. The bundle installer will skip the ProjectWise Explorer installation and go straight
the DGN Navigator Control installation.
To Install ProjectWise Explorer (Without the DGN Navigator Control)

1. Double-click the setup.exe file to open the ProjectWise Client Setups master installer.
2. Click Install next to ProjectWise Explorer.

ProjectWise
155

The Setup Type page opens with the options Custom and Typical. A typical installation installs the
basic features of ProjectWise Explorer and will also install iDesktop Integration support for all
supported applications currently installed. It is recommended that you perform a Custom
installation so you can select which applications will and will not be integrated with ProjectWise. For
example, if you have both MicroStation and Microsoft Office installed but you only want MicroStation
to be integrated, select the Custom option so you can install iDesktop Integration support for
MicroStation but not Microsoft Office.
5. On the Setup Type page, select Custom and click Next.
The Custom Setup page opens, showing you the features that can be installed, the applications that
will be integrated with ProjectWise, and the location to which the product will be installed.
The following items can be installed through the ProjectWise Explorer installer:
ProjectWise 64-bit components (only available if installing on a 64-bit operating system)
ProjectWise Explorer (with options Bentley Viewing, Printing and Redlining (VPR),
Messaging Services, Document Creation Wizard)
iDesktop Integration (supported applications installed on the computer are listed)
Tools > Administrative Tools > Menu Editor
Tools > Export and Import
ProjectWise
156

Tools > User Tools

Spatial Extension
Dependency Viewer
Workflow Rules Engine
6. To change whether or not a feature gets installed, or whether or not to install integration support for
a particular application, click the feature's icon and select the appropriate option from the menu.
Items with an X next to them will not be installed.
7. Expand the iDesktop Integration feature and look at the applications listed. These are the installed
applications for which ProjectWise can install integration support. Click the icon next to the
application you do NOT want to integrate with ProjectWise and select the X option. Note that for
Microsoft Office you can turn off integration with individual Office applications. Also note that if you
have both MicroStation and MicroStation PowerDraft installed, you will only see one option
Bentley MicroStation. When both applications are installed, then installing this option installs
integration support for both applications.
Tip: The Bentley Application Base Integration item under iDesktop Integration is required for
integration with MicroStation and MicroStation PowerDraft, as well as other MicroStation-based
applications such as InRoads, AECOsim Building Designer, Bentley Navigator, and Bentley i-model
Composer. This item cannot be disabled, unless you turn off the entire iDesktop Integration
feature.
ProjectWise
157

On 32-bit operating systems, the default installation location is
C:\Program Files\Bentley\ProjectWise. The Change button will not display if another
application from this release is already installed, and in that case ProjectWise Explorer will simply be
installed to the same location as the previously installed application.
On 64-bit operating systems, the default installation location for the 32-bit components is
C:\Program Files (x86)\Bentley\ProjectWise, and the default installation location for
the 64-bit components is C:\Program Files\Bentley\ProjectWise. The Change button for
32-bit components will not display if another 32-bit application from this release is already installed,
and the Change button for 64-bit components will not display if another 64-bit application from this
release is already installed.
ProjectWise 64-bit components is a required feature when installing on a 64-bit operating system
and cannot be disabled.
Note: When upgrading from an existing ProjectWise Explorer V8i or later, the Change button will
not display for you to change the installation location, and the new version will be automatically
To Install ProjectWise Explorer and/or the DGN Navigator Control

ProjectWise
158

2. Click Install next to ProjectWise Explorer with DGN Navigator Control.
3. When the Bundle Setup Wizard opens, click Next.
The Bundle installer attempts to install each of the following items, and skips those of which are
already installed:
ProjectWise Prerequisite Runtimes
Bentley DGN Navigator Control
ProjectWise Prerequisite Runtimes and Bentley DGN Navigator Control will be installed without
prompting.
If and when the ProjectWise Explorer Setup Wizard opens, see To Install ProjectWise Explorer
Without the DGN Navigator Control to complete the procedure.
To Upgrade to ProjectWise Explorer V8i (SELECTseries 4)

ProjectWise
159


Click Install next to ProjectWise Explorer with DGN Navigator Control, if you want to upgrade to
the current version and also install the DGN Navigator Control.
or
Click Install next to ProjectWise Explorer, if you just want to upgrade to the current version
without also installing the DGN Navigator Control.
If you selected to install ProjectWise Explorer with the DGN Navigator Control, the ProjectWise
Explorer Bundle Setup Wizard opens next. See To Install ProjectWise Explorer and/or the DGN
Navigator Control to complete the procedure.
If you selected to install ProjectWise Explorer without installing the DGN Navigator Control, a second
ProjectWise Client Setups window opens next to show you the version(s) of ProjectWise Explorer
currently installed and what your options are. You may see the following options:
ProjectWise
Install
This button appears when the current version is not yet installed, and a
pre-V8i version is detected. An Install button displays rather than an
Upgrade button here, because you can install the current version next to an
existing installation of ProjectWise Explorer V8 XM Edition (8.9.x), 2004
Edition (8.5.x), or V8 (8.1).
Upgrade
This button appears next to any V8i (8.11.5) or later version detected.
Clicking Upgrade will replace the existing V8i version with the new version.
160

Change
Change from here is the same as modifying the installation of the version
listed using Add / Remove Programs.
Remove
This button appears next to any V8 XM Edition (8.9.x), 2004 Edition (8.5.x),
or V8 (8.1) version detected. Clicking Remove from here is the same as
uninstalling the version listed using Add / Remove Programs.
3. (Optional) If ProjectWise Explorer V8 XM Edition (8.9.x), 2004 Edition (8.5.x), or V8 (8.1) is

currently installed and you want to remove it, click the Remove button next to the version listed.
(Remember, you do not have to remove these particular versions, in order to install the new
version.) When uninstallation of the selected version is complete, continue with the next step.
or
When the Setup Wizard opens, click Next. See To Install ProjectWise Explorer Without the DGN
Navigator Control to complete the procedure.
uninstall the old version of ProjectWise Explorer manually, using Add / Remove Programs.
ProjectWise
161

Adding Bentley Systems as a Trusted Publisher
Tip: If ProjectWise Explorer V8 XM Edition was once installed and later uninstalled on this
computer, then the ProjectWise Explorer V8i (SELECTseries 4) Setup Wizard will not be able to
perform the automatic upgrade, and will display the following warning message:
ProjectWise family product is already installed in C:\Program Files (x86)\Bentley\ProjectWise\
directory.
There are two possible workarounds for this issue:
1. Close the Setup Wizard, manually uninstall the existing ProjectWise Explorer, then install
ProjectWise Explorer V8i (SELECTseries 4) as usual.
or
2. Close the Setup Wizard, remove the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Bentley
\ProjectWise\08.09\Path, then resume the upgrade.
Adding Bentley Systems as a Trusted Publisher

After installing ProjectWise Explorer with iDesktop Integration support for Microsoft Office, in order to
use integrated Word or Excel, you will need to add Bentley Systems to Microsoft Office's Trusted
Publishers list by opening integrated Word or Excel, and then when prompted, selecting to trust all
content from this publisher (Bentley Systems). You only need to do this once. For example, if you add
Bentley Systems to the Trusted Publishers list through integrated Word, then the next time you open
integrated Word or Excel, you will not be prompted about it again. See your Microsoft Office
documentation for more information about trusted publishers.
Modifying Integration Options

To integrate an application that was installed after ProjectWise Explorer was installed, or to turn off
iDesktop Integration support for a particular application, you need to modify the ProjectWise Explorer
installation.
Tip: Because MicroStation and MicroStation PowerDraft both get integrated through the same 'Bentley
MicroStation' option, if one is already installed and integrated with ProjectWise and you later install
the other, you can either perform a Modify or a Repair of the installation, and the newly installed
application will become integrated (without actually changing any settings).
To Integrate with an Application That Was Installed After ProjectWise

Explorer
1.
2.
3.
4.
5.
6.
ProjectWise
Make sure ProjectWise Explorer is closed.

Open the Control Panel and select Add/Remove Programs.
Find the listing for ProjectWise Explorer and click Change.
When the installer opens, click Next.
On the Program Maintenance page, select Modify and click Next.
On the Custom Setup page, expand the iDesktop Integration item. The application you installed after
ProjectWise Explorer will be listed with an X next to it, meaning it is not currently integrated. Click
the X next to the application and select the option, This feature, and all subfeatures, will be installed
on the local hard drive.
162

Switching the Active Version of ProjectWise Explorer
7. Click Next, then click Install.
To Turn Off Integration with an Application, After Installation

1.
2.
3.
4.
5.
6.
Make sure ProjectWise Explorer is closed.

Open the Control Panel and select Add/Remove Programs.
Find the listing for ProjectWise Explorer and click Change.
When the installer opens, click Next.
On the Program Maintenance page, select Modify and click Next.
On the Custom Setup page, expand the iDesktop Integration item. Click the icon next to the
application for which you want to turn off integration and select the X option.
7. Click Next, then click Install.
To Upgrade Microsoft Office on Your Existing ProjectWise Explorer

Installation
1. Upgrade the version of Microsoft Office.
2. Perform a repair of the existing ProjectWise Explorer installation to reestablish integration.
To Upgrade Both Microsoft Office and ProjectWise Explorer

1. Upgrade the version of Microsoft Office.
2. Upgrade the version of ProjectWise Explorer.
Note: This is the recommended order of upgrading, when you are upgrading both Microsoft Office
and ProjectWise Explorer. If you upgrade ProjectWise Explorer first and then Microsoft Office, you
will need to manually uninstall and reinstall ProjectWise Explorer and Office integration through the
Windows Control Panel. Performing a repair does not work in this case.
Switching the Active Version of ProjectWise Explorer

If necessary you can install ProjectWise Explorer V8i (SELECTseries 4) Refresh and ProjectWise
Explorer V8 XM Edition on the same computer.
When two versions of ProjectWise Explorer are installed on the same computer, the last version
installed is automatically the active version. In general, you can use either version of ProjectWise
Explorer without running the version switch. However, when you want to use iDesktop Integration of a
version that is not the active version, you must run the delivered command line switch
(...\ProjectWise\bin\versionSwitch.vbs) on that version to set it as the active version. The
version set as the active version remains the active version until you run the switch again.
1. Before you begin, ensure that the ProjectWise Explorer process (PWC.EXE) is not running.
Opening the Control Panel automatically loads the PWC.EXE process, which may interfere when you
try to switch the version of the ProjectWise Network Configuration Utility. If you have not opened
the Control Panel since starting your computer, you can skip this step.
2. Next, close any open ProjectWise windows.
3. Open a command prompt and navigate to the ...\ProjectWise\bin folder of the more recent
ProjectWise Explorer installation.
ProjectWise
163

Desktop Integration for Bentley Applications
Note: If the user you are logged in as is not a member of the Administrators group on this computer,
you must launch the command prompt with elevated privileges (right-click CMD.EXE and select Run
as administrator).
4. To switch the active version to ProjectWise V8 XM Edition, enter:
cscript versionSwitch.vbs /89
5. To switch the active version back to ProjectWise V8i (SELECTseries 4) Refresh, enter:
cscript versionSwitch.vbs /811
6. After the active version is switched, restart your computer.
Note: You should always run the version switch after modifying any iDesktop Integration settings. For
example, even if you switched the active version to /811 and then uninstalled integration for
ProjectWise Explorer V8 XM Edition, you should still rerun the version switch, again specifying /811 as
the active version.
Note: If the Spatial Extension feature of ProjectWise Explorer V8i (SELECTseries 4) Refresh is
installed, you should uninstall it before switching the active version to ProjectWise Explorer V8 XM
Edition. If this feature is installed and you switch the active version to ProjectWise Explorer V8 XM
Edition, ProjectWise Explorer V8i (SELECTseries 4) Refresh will crash when loading.
Desktop Integration for Bentley Applications

Installing ProjectWise Explorer with iDesktop Integration support for MicroStation and MicroStation
PowerDraft delivers a configuration file called PW.CFG to the
Bentley\<program name>\config\appl folder of your MicroStation or MicroStation PowerDraft
installation. This configuration file loads the MDL applications necessary for ProjectWise integration
and for starting MicroStation or MicroStation PowerDraft in integrated mode, when launched from the
desktop. To disable desktop integration for those applications, simply re-run the ProjectWise Explorer
installer and turn off integration for the desired application.
When Bentley Navigator V8i (SELECTseries 4), Bentley i-model Composer V8i (SELECTseries 4), and/or
Bentley View V8i (SELECTseries 3) are installed on the same computer as ProjectWise Explorer V8i
(SELECTseries 4), those applications are automatically integrated with ProjectWise Explorer, and
desktop integration is on by default. Use the following procedure only if you need to disable desktop
integration for any of those applications.
Tip: To re-enable desktop integration, comment out or delete the
PW_DISABLE_INTEGRATION_FROM_DESKTOP=1 line.
Tip: If you want to completely disable integration with ProjectWise, whether the application is launched
from the desktop or by opening a document from ProjectWise Explorer, then open the PW.CFG file and
add the line PW_DISABLE_INTEGRATION=1 just below the line
#PW_DISABLE_INTEGRATION_FROM_DESKTOP=1.
To Disable Desktop Integration for Bentley Navigator, Bentley View, or

Bentley i-model Composer
1. Go to the application's Bentley\<program name>\config\appl folder.
ProjectWise
164

Running ProjectWise Explorer on Citrix XenApp
2.
3.
4.
5.
Bentley Navigator
C:\Program Files\Bentley\Navigator
V8i\config\appl
Bentley View
C:\Program Files\Bentley\View V8i

\config\appl
Bentley i-model Composer
C:\Program Files\Bentley
\imodelComposer V8i\config\appl
Find the PW.CFG file in that folder and open it in a text editor.
Find the line #PW_DISABLE_INTEGRATION_FROM_DESKTOP=1
Remove the # character to uncomment and enable the variable.
Save and close the PW.CFG file.
When desktop integration is disabled, you can launch the application from the desktop, and it will
not be integrated with ProjectWise Explorer (you will not be prompted to log in to a ProjectWise
datasource). The application will still be integrated, however, whenever you open a document into it
from ProjectWise Explorer.

ProjectWise Explorer can be configured to run in a Citrix XenApp environment. For this release, Citrix
XenApp 6.0 and 6.5 are supported.
Before getting started, make sure the ProjectWise Integration Server computer can communicate with
the main Citrix XenApp computer.
Tip: When a users working directory node identifier is configured to use a logical name or a GUID, that
user must not use multiple computers to work with documents in ProjectWise.
Tip: The User Tools, Data Export and Import Wizards, Menu Editor, and Attribute Bulk Update tool that
can also be installed through the ProjectWise Explorer installer are not supported when running in a
Citrix XenApp environment.
Tip: Currently, you cannot drag local files into ProjectWise Explorer when running in a Citrix XenApp
environment. This is a Citrix XenApp issue and has nothing to do with ProjectWise. If you need to add
local files to ProjectWise, use Document > New in ProjectWise Explorer.
Tip: Saving the audit trail report when using ProjectWise Explorer through Citrix XenApp may take a
long time.
To Configure ProjectWise Explorer to Run in a Citrix XenApp Environment

1. In ProjectWise, log in to your datasource and select the Users datasource node.
2. Open the Properties dialog for a user and select the Settings tab.
3. Expand Working Directory > When Using ProjectWise Explorer and use a UNC path (for example,
\\workdirs\bobs_workdir) to define the folder path to the users working directory.
4. Next, expand Working Directory > When Using ProjectWise Explorer > Node identifier.
ProjectWise
165

This setting is used to define the node name that will be used when the user checks out documents
from ProjectWise Explorer. Because Citrix XenApp users cannot use the users host computer name
as the node name, you must change the default value for this setting to one of the other options.

To use the user's user name as the node name, select Use the user's host computer name or user
name and change the value from $HOSTNAME$ to $USERNAME$.
or
To create a random global unique identifier (GUID) to be used as the node name, select Use a global
unique identifier (GUID), then in the Unique Node ID dialog that opens, click Generate New ID and
click OK.
or
To enter a logical name to be used as the node name, select Use a logical name, then in the Unique
Node ID dialog that opens, enter a logical name for the node (for example, Bob's Computer) and
click OK.
6. Click OK in the User Properties dialog.
7. On the Citrix XenApp computer (or computers, if you are using a Citrix XenApp farm) install
ProjectWise Explorer.
ProjectWise
166

Installing the Delivered Add-ons to ProjectWise Explorer
8. On each Citrix XenApp computer where ProjectWise Explorer is installed, establish a connection to
the ProjectWise Integration Server computer using the ProjectWise Network Configuration Settings
dialog (Control Panel > ProjectWise V8i Network).
9. On the main Citrix XenApp computer, open the Citrix Delivery Services Console and use the Publish
Application wizard to publish the 'ProjectWise Explorer' application.
Among other settings, in this wizard you will set the display name that users will see (ProjectWise
Explorer) and also the location of the ProjectWise Explorer program executable (pwc.exe).
When publishing is completed, 'ProjectWise Explorer' will appear next to all other applications
which are available for Citrix XenApp users.

The following add-ons are delivered with ProjectWise Client Setups and can be installed on top of
ProjectWise Explorer as needed:
ProjectWise Export/Import Tool is used to bulk import files and attribute data from external sources
into ProjectWise, or to bulk export files and attribute data out of ProjectWise. The tool uses an Excel
spreadsheet as the data interchange format. This tool was previously a separate download.
ProjectWise i-model Packager is delivered in support of the Bentley mobile app, ProjectWise
Explorer Mobile. ProjectWise i-model Packager gets installed on top of ProjectWise Explorer, and is
used to create packages for ProjectWise Explorer Mobile app users, to unpack packages created by
ProjectWise Explorer Mobile app users, or to convert mobile markup files created in the Navigator
Pano Review app to overlay.dgn files.
To Install the ProjectWise Export/Import Tool

2. Click Install next to ProjectWise Export/Import Tool.
3. When the setup wizard opens, click Next.
ProjectWise
167

5. When the Destination Folder opens, accept the default installation location or click the Change
button to change it, then click Next.
ProjectWise
168

6. When the Setup Type page opens, select Complete and click Next.
To Install ProjectWise i-model Packager

2. Click Install next to ProjectWise i-model Packager.
ProjectWise
169

5. When the Custom Setup page opens, you can either accept the default installation location, or click
the Change button to change it, and click Next.
C:\Program Files\Bentley\ProjectWise i-model Packager.
C:\Program Files (x86)\Bentley\ProjectWise i-model Packager.
ProjectWise
170
ProjectWise Web Server Configuration
ProjectWise Web Server Overview

ProjectWise Web Server and Web View Server lets ProjectWise users connect to ProjectWise through a
website using ProjectWise Web Parts that have been embedded into the website by the sites
administrator.
The website you use can either be a SharePoint website, or it can be a standalone IIS website. If using a
standalone website, ProjectWise Web Server and Web View Server delivers two example ASP pages
(default.aspx or defaultspatial.aspx) with ProjectWise Web Parts already configured that
you can use out of the box. You can also create your own ASP pages and add ProjectWise Web Parts to
them.
ProjectWise Web Server and Web View Server is a single installation. After installation you choose
which server to deploy ProjectWise Web Server or ProjectWise Web View Server. ProjectWise Web
Server is the server to deploy when you want to provide users with normal access to ProjectWise,
where they can check out documents, add new documents and folders, and so on. ProjectWise Web
View Server is the server to deploy when you want to provide users with read-only access to
ProjectWise. ProjectWise Passport usage is reported in SELECT Server for the users who connect to
ProjectWise Web Server, however no ProjectWise Passport usage is reported in SELECT Server for the
users who connect to ProjectWise Web View Server.
Before You Install and Deploy ProjectWise Web Server and Web
View Server
How you configure the computer prior to installation depends on whether or not you are using
SharePoint. If using SharePoint, configuration further depends on whether or not you plan to use
ProjectWise Web Server's SharePoint search integration feature.
2. Be an administrator of the computer.
3. In Server Manager, turn on the Web Server (IIS) role and the necessary role services.
For Windows Server 2012, the following role services are required:
Web Server
Common HTTP Features
Static Content
Default Document
HTTP Errors
HTTP Redirection
ProjectWise
171

Before You Install and Deploy ProjectWise Web Server and Web View Server
.NET Extensibility 3.5
ASP
ASP.NET 3.5
ISAPI Extensions
ISAPI Filters
Health and Diagnostics
HTTP Logging
Security
Request Filtering
Management Tools
Web Server
Static Content
Default Document
HTTP Errors
HTTP Redirection
ASP.NET
.NET Extensibility
ISAPI Extensions
ISAPI Filters
Health and Diagnostics
HTTP Logging
Security
Request Filtering
Management Tools
4. In Server Manager, make sure the .NET Framework feature is installed.
5. For SharePoint deployments, install a version of SharePoint supported by this release of ProjectWise,
including the latest updates. See the ProjectWise readme for supported SharePoint versions.
You can use:
ProjectWise
Microsoft SharePoint Server 2010 SP1

Microsoft Search Server 2010 Express SP1
Microsoft SharePoint Foundation 2010 SP1
Microsoft Office SharePoint Server 2007 SP3
Windows SharePoint Services 3.0 SP3
172

Before You Install and Deploy ProjectWise Web Server and Web View Server
6. If upgrading from SharePoint 2010 to SharePoint 2010 SP1, you must run the SharePoint
Configuration Wizard after the upgrade.
7. If you plan to install ProjectWise Web Servers SharePoint search integration feature, you must first
install either SharePoint Server 2010 or Search Server 2010 Express (along with the latest updates),
and you must have appropriate rights to SharePoint.
The user account you use to install ProjectWise Web Server and the SharePoint search integration
feature must meet the same account requirements as the Setup user account in SharePoint. For
details about this account, see: http://technet.microsoft.com/en-us/library/ee662513%28office.
14%29.aspx
Note: Search Server 2010 Express includes SharePoint Foundation 2010. If you do not need the
SharePoint search integration feature, you can simply install SharePoint Foundation 2010 instead of
Search Server 2010 Express.
8. For standalone (non-SharePoint) deployments, if you are working on a computer from which
SharePoint has been uninstalled, make sure that correct IIS permissions are set as described in
http://support.microsoft.com/kb/812614/en-us, as uninstalling SharePoint will affect your IIS
permissions.
9. In IIS, it is strongly recommended that you set up SSL for the website where ProjectWise Web Server
or ProjectWise Web View Server will be deployed.
10.
11.
12.
13.
14.
15.
16.
SSL ensures that all communication between the user and the Web Server (including passwords and
other sensitive data) is encrypted and cannot be read or intercepted by a third party.
For security reasons, it is recommended that the IIS application pool you plan to use does not use the
LocalService or LocalSystem identity.
You can deploy to as many IIS websites as needed on the same computer. ProjectWise Web Server
and Web View Server supports parallel deployments to both SharePoint and standalone (nonSharePoint) websites on the same computer. ProjectWise Web Server and Web View Server also
supports parallel deployments of both ProjectWise Web Server and ProjectWise Web View Server to
different IIS websites on the same computer. You cannot, however, deploy both ProjectWise Web
Server and ProjectWise Web View Server to the same IIS website.
SharePoint lets you extend a web application to another IIS website, however this is not supported
by ProjectWise Web Server and Web View Server.
For cluster-like functionality in SharePoint, you can set up a web farm. Visit Microsoft's website for
more information. Note that when installing ProjectWise Web Server and Web View Server in a web
farm, you must install it on the front-end server.
If using ProjectWise Publishing Server with ProjectWise Web Server and Web View Server, for
performance reasons it is recommended that you do not install them on the same computer.
If you need to install a ProjectWise language pack, it is recommended that you install it after
installing ProjectWise Web Server and Web View Server, but before deploying ProjectWise Web
Server or ProjectWise Web View Server.
You must launch the installer with elevated privileges (Run as Administrator) if:
You plan to install the SharePoint search integration feature of ProjectWise Web Server and Web
View Server.
You plan to launch the Product Activation Wizard from the final page of the Setup Wizard. This
ensures that the Product Activation Wizard is also run as an administrator, which in turn ensures
that the licensing information you enter through the Product Activation Wizard gets registered to
the correct location in the Windows Registry.
ProjectWise
173

Installing and Deploying ProjectWise Web Server with SharePoint Search Integration
Note: To launch the ProjectWise Web Server and Web View Server installer with elevated privileges,
you must first use the Run as Administrator option to launch the main ProjectWise Server Setups
installer (setup.exe), and then launch the ProjectWise Web Server and Web View Server installer
from there. This is because Windows lets you use the Run as Administrator command on EXE files,
but not MSI files.
17. For SharePoint deployments, the user you use to deploy ProjectWise Web Server must be an
administrator on the computer you are deploying on, and also an administrator for the local
SharePoint installation.
Installing and Deploying ProjectWise Web Server with SharePoint

Search Integration
ProjectWise Web Server provides integration with SharePoint 2010's search tool. This integration lets
users search both ProjectWise and SharePoint at the same time from the same SharePoint search
interface. The search results will show both SharePoint and ProjectWise documents side by side in the
list.
Setting up SharePoint search integration requires both ProjectWise Integration Server-side and
ProjectWise Web Server-side configuration.
When configuring SharePoint search integration, the process of installing ProjectWise Web Server takes
care of deploying ProjectWise Web Server to the SharePoint site for you, therefore you do not need to
run the Deployment Wizard that opens at the end of installation. You can still run the Deployment
Wizard after installation if you want to deploy ProjectWise Web Server or ProjectWise Web View Server
to a standalone IIS website on this computer.
Indexing Service for maintaining the full text index catalog, the SharePoint search integration feature of
ProjectWise Web Server does not currently support this configuration and only works when the full text
index catalog is located on the ProjectWise Integration Server computer. Likewise, SharePoint search
integration does not work if the full text index catalog is stored on the tail Integration Server in a headtail server configuration.
Configuring ProjectWise Web Server with SharePoint Search Integration

The following are the general steps for configuring SharePoint search integration.
1. On another computer, install ProjectWise Integration Server with the ProjectWise Indexing
Connector for SharePoint and Full Text Indexing features turned on. Create your datasources as
usual.
2. Installing the ProjectWise Indexing Connector for SharePoint feature creates a website in IIS on
the ProjectWise Integration Server computer called ProjectWise Indexing Connector. Make sure
the ProjectWise Indexing Connector port (default is 5802) is open on the ProjectWise Integration
Server.
3. In ProjectWise Administrator, enable and run full text indexing on each of the datasources you want
to be indexed in SharePoint.
Note: At this time, SharePoint search integration does not support the use of a standalone
ProjectWise Indexing Service for maintaining the full text index catalog. For SharePoint search
ProjectWise
174

integration to work, the datasource you index must have its full text index catalog located on and
managed by the ProjectWise Integration Server.
4. On the SharePoint computer, install ProjectWise Web Server with the SharePoint search integration
feature turned on.
5. On the ProjectWise Integration Server computer, open ProjectWise Administrator and grant trust to
the SharePoint installation listed under the Trusted External Indexers node.
6. On the SharePoint computer, perform a full crawl of the ProjectWise Integration Servers full text
index.
Trust must be granted before SharePoint can crawl the ProjectWise full text index. Also, depending
on the amount of documents that need to be indexed first in ProjectWise, allow some time for the
ProjectWise full text indexing job to complete before you begin the crawl in SharePoint.
7. Configure this ProjectWise Web Server deployment to use ProjectWise single sign-on.
To Install ProjectWise Web Server with SharePoint Search Integration

1. Right-click the setup.exe file and select Run as Administrator to open the ProjectWise Server
Setups master installer with elevated privileges.
2. Click Install next to ProjectWise Web Server and Web View Server.
ProjectWise
175

Assuming you have already installed and configured the required SharePoint version, the
SharePoint search integration option is enabled by default. This option will be off by default if
SharePoint is not installed, or if the wrong SharePoint version is installed, or if SharePoint search is
not properly configured.
5. On the Custom Setup page, make sure SharePoint search integration is on, accept or change the
default installation location, then click Next.
The SharePoint Search Integration page opens for you to specify the ProjectWise Integration Server
whose datasources you want to index, and to select the SharePoint site you want to integrate with.
Note: All of the ProjectWise Web Parts will be automatically deployed to the site you select here, so
you can and should skip the Deployment Wizard that opens at the end of this installation.
ProjectWise
176

6. The option Enable searching for ProjectWise documents using SharePoint search is on by
default. Only turn this option off if you want to specify the ProjectWise Integration Server after
installation. Otherwise, leave this option on.
7. In the Address of the ProjectWise Integration Server to index field, enter the host name or IP
address of the computer on which ProjectWise Integration Server is installed and click Test. This
sends a request to the ProjectWise Integration Server to grant trust to this SharePoint installation.
The Trust Connection Needed dialog opens, informing you that the request was sent, and that you
need to go to ProjectWise Administrator to grant trust to this SharePoint installation. You can do this
step after installation is complete. Click Close on the Trust Connection Needed dialog.
When a request for trust is sent, the name of this SharePoint computer is added to the specified
ProjectWise Integration Server's Trusted External Indexers node in ProjectWise Administrator.
ProjectWise
177

8. Next, from the list of SharePoint websites, select the website you want to enable search integration
for and deploy ProjectWise Web Server to.
9. The Use ProjectWise Web View Server license to display details of a ProjectWise document
found via integrated search option lets you select whether you want to use ProjectWise Web
Server or ProjectWise Web View Server to display the results of integrated searches. This option is
off by default, meaning ProjectWise Web Server will be used. Turn this option on if you want to use
ProjectWise Web View Server instead.
10. When finished on this page, click Next.
12. When installation is complete, select No, thanks (because you do not need to run the Deployment
Wizard) and click Finish.
At the same time, the Product Activation Wizard opens for you to configure licensing for this server.
ProjectWise
178

To Send a Trust Request from SharePoint Central Administration After

Installation
If you skipped the option to send a trust request to ProjectWise Integration Server during installation,
or if you want to change the ProjectWise Integration Server (and therefore change the datasources to
index), you can do this now from a new ProjectWise page in SharePoint Central Administration.
1. Select Start > All Programs > Bentley > ProjectWise V8i (SELECTseries 4) > SharePoint Search
> ProjectWise Datasource Configuration.
You can also get to the same location by going to the SharePoint Central Administration page and
clicking the Searchable ProjectWise datasources link.
This opens the Configure ProjectWise Integration Server and Searchable Datasources page.
2. Click Configure integration server, and in the dialog that opens, enter or change the name or IP
address of the computer on which the ProjectWise Integration Server is installed, whose datasources
you want to index. Click OK.
3. Next, click Request Server Trust. A trust request is sent to the ProjectWise Integration Server
specified in the previous step, and a dialog opens, telling you to go to ProjectWise Administrator and
grant the trust request for this SharePoint installation. Click OK.
ProjectWise
179

Until you grant trust to in ProjectWise Administrator, the Status in SharePoint displays as No
trust. When you grant trust, the Status changes from No trust to OK.
To Grant a SharePoint Search Integration Trust Request in ProjectWise

Administrator
1. Open ProjectWise Administrator.
2. Expand the server node for the ProjectWise Integration Server you specified during ProjectWise
Web Server installation (or through the SharePoint Central Administration page) and select the
Trusted External Indexers node.
3. Log in to a datasource if prompted.
If you are not already logged in to at least one datasource of this ProjectWise Integration Server, the
ProjectWise Log in dialog opens. Select a datasource, enter the user name and password of an
administrator in the datasource, and click Log in.
4. In the Trusted External Indexers list, right-click the SharePoint computer listed and select Grant
Trust.
The Trust Granted column changes from No to Yes, and in SharePoint the Status changes from No
trust to OK.
ProjectWise
180

You can now go back to SharePoint and perform a crawl of the specified ProjectWise Integration
Server's full text index.
To Perform a Full Crawl of the ProjectWise Full Text Index

1. In SharePoint, go back to the Configure ProjectWise Integration Server and Searchable Datasources
page.
Again, you can get there by selecting Start > All Programs > Bentley > ProjectWise V8i
(SELECTseries 4) > SharePoint Search > ProjectWise Datasource Configuration, or by going to
the SharePoint Central Administration page and clicking the Searchable ProjectWise datasources
link.
2. Click Start full crawl.
To check the history of a document crawl, in SharePoint go to Central Administration > General
Application Settings > Farm Search Administration > Search Service Application > Crawl
History. Each ProjectWise document crawl will be listed as ProjectWise Documents. This is also a
hyperlink that lets you review the history of the crawl and to review any errors.
ProjectWise
181

Now your ProjectWise full text index is indexed in SharePoint, and you can perform integrated searches
that search both SharePoint and ProjectWise.
To Configure This ProjectWise Web Server Deployment on SharePoint to Use

ProjectWise Single Sign-On
The last part of the configuration for this ProjectWise Web Server deployment on SharePoint you
need to configure ProjectWise single-sign on. This is needed so that you and your users can open
ProjectWise documents from the search results, and also to use ProjectWise Web Parts on this
SharePoint site in general.
1. Configure ProjectWise Web Server to use ProjectWise single sign-on.
2. On the ProjectWise Web Server computer, log in to the SharePoint site with a Windows domain
account that has administrative rights to that site. Make sure this domain account also exists in the
ProjectWise datasource you plan to connect to.
3. Make sure that your ProjectWise users having Windows domain-based accounts are also added to
the SharePoint site.
If you need to set this up, in SharePoint go to Site Actions > Site Settings > Users and Permissions
> People and groups, click New > Add Users, then add your Windows domain groups and/or
Windows domain users. For most users, you should set their permissions to Team Site Visitors
[Read].
Note: This [Read] permission does not mean that the documents and folders found in ProjectWise
Web Parts are read-only, it simply means that users can access the SharePoint site, but they cannot
change anything on the site. For example, they will not be able to add a web part or close a web part.
If you want some of your users to have this ability, then for those users you can set their permissions
to Team Site Members [Contribute]. Team Site Members can also, for example, log in to the
datasource as a different user.
ProjectWise
182

Installing ProjectWise Web Server Without SharePoint Search Integration
Installing ProjectWise Web Server Without SharePoint Search

Integration
If you are not configuring SharePoint search integration, then installation and deployment is the same as
in previous releases. That is, you install ProjectWise Web Server, and then you run the Deployment
Wizard to select which IIS websites (SharePoint or standalone) to deploy ProjectWise Web Server or
ProjectWise Web View Server to.
To Install ProjectWise Web Server Without SharePoint Search Integration

2. Click Install next to ProjectWise Web Server and Web View Server.
5. Turn off SharePoint search integration, accept or change the default installation location, and click
Next.
ProjectWise
183

Deploying ProjectWise Web Server and ProjectWise Web View Server
The SharePoint search integration feature will be off by default if SharePoint is not installed on the
computer.
7. When installation is complete, select which Deployment Wizard you want to run next, then click
Finish.
The selected deployment wizard opens. At the same time, the Product Activation Wizard opens for
you to configure licensing for this server.
Deploying ProjectWise Web Server and ProjectWise Web View

Server
After installing ProjectWise Web Server and Web View Server (regardless of whether or not you
installed SharePoint search integration), you can deploy ProjectWise Web Server and ProjectWise Web
View Server to any IIS website (SharePoint or standalone) on the computer to which ProjectWise Web
Server or ProjectWise Web View Server has not already been deployed.
If you have already configured SharePoint search integration, you can still run the Deployment Wizard,
but you would only run it if you wanted to deploy ProjectWise Web Server or ProjectWise Web View
Server to another IIS website (either SharePoint or standalone) after installation. Also, if you do
configure SharePoint search integration and then use the Deployment Wizard to explicitly deploy
ProjectWise Web Server or ProjectWise Web View Server to some other SharePoint site on this
computer, the site you deploy to will not have SharePoint search integration.
To Deploy ProjectWise Web Server or ProjectWise Web View Server

1. If the Deployment Wizard you want to run is not already open, open it now by selecting either:
Start > All Programs > Bentley > ProjectWise V8i (SELECTseries 4) > Web Server and Web
View Server > ProjectWise Web Server Deployment Wizard
or
View Server > ProjectWise Web View Server Deployment Wizard
2. When the selected Deployment Wizard opens, click Next.
ProjectWise
184

The Deployment Type page opens, displaying the virtual servers (websites) currently available in IIS,
and whether or not ProjectWise Web Server or ProjectWise Web View Server is currently deployed
to any of them.
If you launched the ProjectWise Web Server Deployment Wizard, select Deploy ProjectWise Web
Server and click Next.
or
If you launched the ProjectWise Web View Server Deployment Wizard, select Deploy ProjectWise
Web View Server and click Next.
4. On the Virtual Server Selection page, select one or more virtual servers (websites) to deploy
ProjectWise Web Server or ProjectWise Web View Server to, then click Next.
ProjectWise
185

5. If the Site Update Required page opens, this means that one or more of the websites you selected to
deploy to does not meet the minimum requirements of ProjectWise Web Server or ProjectWise Web
View Server. Select the websites you want to upgrade, then click Next. (ProjectWise Web Server or
ProjectWise Web View Server will not be deployed to any website listed that you do not select to
upgrade.)
6. When the Custom Trust Policy page opens, do one of the following:
Select Automatically configure trust level (recommended) and click Next.
or
Select Do no configure trust policy - I will do it manually and click Next. If you select this option, a
text file opens when you click Finish in the Deployment Wizard. This text file contains the custom
trust policy information for you to manually add to your existing trust policy.
ProjectWise
186

7. On the Select working directory page, specify a temporary working directory for each website you
are deploying ProjectWise Web Server or ProjectWise Web View Server to.
This temporary working directory is used by the ProjectWise Web Server or ProjectWise Web
View Server to store things such as licensing data, images, and files that are being transferred
between the main ProjectWise server and the client making the request.
Each website must have its own working directory that is not being used by any other
ProjectWise Web Server or ProjectWise Web View Server deployment.
The working directory must be located on the same computer you are installing and deploying
on.
The working directory cannot be located under the website's home directory (for example, it
cannot be here: C:\inetpub\wwwroot).
Make sure the local system account has Write permission on the specified working directory.
To set the working directory for a particular website, click where it says <Click here to set the
working directory>, then in that field type the path to the local folder, or click the folder icon to
browse for a local folder to set as the working directory. Repeat this step for each website you are
deploying to.
UNC paths (\\servername\sharename) are not supported.
8. After you specify a working directory, click Start.

If you specify a working directory folder that does not yet exist, a dialog opens to ask if you would
like to create it now. Click Yes.
9. When deployment is complete, click Finish.
ProjectWise
187

Configuring Single Sign-On for ProjectWise Web Server
10. If in step 6 you selected to manually configure the trust policy, a text file opens when you click Finish.
This text file contains the custom trust policy information you need to add to your existing trust
policy. For more information, see your SharePoint documentation.
You can rerun the Deployment Wizard as needed to deploy to another website, or to remove a current
deployment from a website.

Single sign-on lets ProjectWise users log in to their datasources using the same Windows credentials
they used to log on to their computer. This assumes that their Windows account has already been added
to the ProjectWise datasource they are logging in to.
While the general concept of single sign-on is the same across the different ProjectWise clients, single
sign-on is configured a little differently for ProjectWise Web Server / ProjectWise Web Parts than it is
for ProjectWise Explorer and ProjectWise Administrator users. To enable single sign-on for ProjectWise
Explorer and ProjectWise Administrator users, the administrator simply adds the line SSO=1 to the
ProjectWise Integration Server's dmskrnl.cfg file. This line, however, does not apply for ProjectWise
Web Server single sign-on.
To configure single sign-on for ProjectWise Web Server / ProjectWise Web Parts, you need to do the
following:
1. Add the IP address of this ProjectWise Web Server computer to the [Trusted Servers] section in
the ProjectWise Integration Server's dmskrnl.cfg file.
2. Create a delegate user in ProjectWise Administrator.
3. Enter the credentials of the delegate user on the ProjectWise computer.
To Create a Delegate User in ProjectWise Administrator

1.
2.
3.
4.
In ProjectWise Administrator, log in to your datasource as usual and select the Users node.
Create a logical user account (right-click the Users node and select New > User).
Turn on that user's user setting, Enable as delegate user.
If needed, add the delegate user to the Administrator group.
This step is only required if any of the domain users in the datasource who plan to connect to
ProjectWise through ProjectWise are also members of the Administrator group in ProjectWise.
ProjectWise
188

5. Repeat this procedure as needed to configure a delegate user in other datasources.
Once a delegate user exists in the datasource, you can go to the ProjectWise Web Server computer and
specify which delegate user will be used for each datasource.
To Enter the Credentials of the Delegate User on the ProjectWise Web Server
Computer
1. On the ProjectWise Web Server computer, select Start > All Programs > Bentley > ProjectWise V8i
(SELECTseries 4) > Web Server and Web View Server > ProjectWise Web Server Single SignOn
Settings.
The Single Sign-On Settings dialog opens for you to specify the delegate user to use for each
datasource. If you have already specified a delegate user for a particular datasource, you can use this
same procedure to change the currently specified delegate user (assuming there is another delegate
user in the same datasource).
This dialog requires elevated privileges.
2. Select your datasource, enter the user name and password of the delegate user you created in this
datasource, and click Save Settings.
Repeat this step to specify the delegate user to use in other datasources.
3. Click Close.
Note: The datasource list displays whatever datasources are configured to display as the result of
configuring the ProjectWise network on this computer. If the datasource you need to connect to is
not listed, close this dialog, configure the ProjectWise network, then open this dialog again. The
ProjectWise network is configured using the ProjectWise Network Configuration Settings dialog. See
Connecting Individual Clients to the Server for details.
ProjectWise
189

Integrating with ProjectWise Publishing Server

To view and/or markup DGN and DWG documents in the Publishing and Markup web part, you need to
integrate ProjectWise Web Server and Web View Server with ProjectWise Publishing Server.
ProjectWise Publishing Server Integration Checklist

1. For better performance it is recommended that you install ProjectWise Publishing Server on a
different computer than ProjectWise Web Server and Web View Server, and also a different
computer than SharePoint, if also using SharePoint. If you need to install ProjectWise Publishing
Server and ProjectWise Web Server and Web View Server on the same computer for some reason,
you can only use a 64-bit Windows Server 2008 operating system.
2. Install the Web Server (IIS) Role and Role Services Required for ProjectWise Publishing Server.
3. Install ProjectWise Publishing Server V8i (SELECTseries 4). This server is not included with
ProjectWise Server Setups, but is a separate download on SELECT downloads.
4. On the same computer, install ProjectWise Publishing Gateway Service (delivered with ProjectWise
Server Setups).
The version of ProjectWise Publishing Gateway Service you install must always be of the same
release version as the ProjectWise Web Server and Web View Server you are using.
5. In ProjectWise Administrator, add the ProjectWise Publishing Server address to the datasource
settings.
6. In ProjectWise Administrator, set ProjectWise Publishing Server as the web viewer for all the
applications in the datasource associated with DWG and DGN documents.
To Install the Web Server (IIS) Role and Role Services Required for
ProjectWise Publishing Server
Web Server
Static Content
Default Document
HTTP Errors
ASP.NET
ISAPI Extensions
ISAPI Filters
Security
Basic Authentication
Management Tools
ProjectWise
190

IIS 6 Management Compatibility
Note: If you encounter a problem installing ProjectWise Publishing Server, check to make sure the
IIS 6 Metabase Compatibility role service is turned on, as it is not on by default.
To Install ProjectWise Publishing Server

1. Determine whether you want to run ProjectWise Publishing Server as a Web Server Extension, or as
a standalone HTTP server. Running ProjectWise Publishing Server as a Web Server Extension allows
serving ProjectWise Publishing Server requests through IIS. If you are installing ProjectWise
Publishing Server exclusively for use with ProjectWise Web Server and Web View Server, then Web
Server Extension is not required.
2. If you plan to install ProjectWise Publishing Server on the same computer as ProjectWise Web
Server and Web View Server (which is not recommended), and if you plan to run ProjectWise
Publishing Server as a Web Server Extension, then first create a separate IIS web site to install
ProjectWise Publishing Server to.
3. Install Prerequisites for Bentley Desktop Applications (8.11.7.03 or later).
4. Launch the ProjectWise Publishing Server installer and click Next when it opens.
5. When the License Agreement page opens, accept the license agreement and click Next.
6. When the Destination Folder page opens, click Next to install to the default location, or click Change
to select a different installation location and then click Next.
ProjectWise
191

7. On the Setup Type page, select Custom and click Next.

8. On the Custom Setup page, select which features to install. If Web Server Extension is not needed, do
not install the Web Server Extension Files and Examples Files features. When finished click Next.
ProjectWise
192

9. On the Web Site Selection page, select the IIS web site where ProjectWise Publishing Server files will
be installed. Important: If the Web Server Extension feature is selected to be installed from the
previous step, do not select the same web site where ProjectWise Web Server or ProjectWise Web
View Server is deployed. In this case, use the dedicated web site created in step 2. When finished,
click Next.
ProjectWise
193

12. If the Web Server Extension feature was not installed, configure ProjectWise Publishing Server to
run in standalone mode. To do this, open the ProjectWise Publishing Server Administration page
(Start > All Programs > Bentley > ProjectWise Publishing Server > ProjectWise Publishing
Server Administration), navigate to the General Settings page, turn off Run as Web Server
Extension, and click Submit. To apply configuration changes, a server needs to be restarted.
Navigate to the Server Control page and click Restart Server.
ProjectWise
194

To Add the ProjectWise Publishing Server Address to the Datasource

Settings
1. Open ProjectWise Administrator and log in to your datasource.
2. Right-click your datasource and select Properties.
The Datasource Properties dialog opens.
3. On the Settings tab, expand Web Components > Default ProjectWise Publishing Server and doubleclick the icon below it.
4. In the Specify server address dialog, enter the name of the computer on which ProjectWise
Publishing Server is installed, followed by a colon, followed by the port number. For example,
http://publishingserver:8087.
If ProjectWise Publishing Server is running as a Web Server Extension, specify the port number of
the IIS web site where ProjectWise Publishing Server is installed. Otherwise, specify the port number
of ProjectWise Publishing Server as configured in ProjectWise Publishing Server Administration
(default is 8087).
ProjectWise
195

5. Click OK in the Specify server address dialog, then click OK in the Datasource Properties dialog.
To Set ProjectWise Publishing Server as the Web Viewer for DGN and DWG
Documents
1. Open ProjectWise Administrator and log in to your datasource.
2. Under the Applications icon, select an application you have associated to DGN and/or DWG
documents and select Properties.
3. On the Web viewing tab, set the Associated web viewer to ProjectWise Publishing Server.
ProjectWise
196

4. Click OK.
Repeat this procedure for all other applications that are associated to DGN and/or DWG documents.
If this step is not done for an application to which a DGN or DWG is associated, then the selected
document will not be able to be viewed or marked up through the Publishing and Markup web part.
To Install ProjectWise Publishing Gateway Service

1. Make sure ProjectWise Publishing Server is installed on this computer, and that the ProjectWise
Publishing Server service is running.
3. Click Install next to ProjectWise Publishing Gateway Service.
ProjectWise
197

ProjectWise
198

Note: The installer automatically stops the ProjectWise Publishing Server service during installation,
and restarts it once ProjectWise Publishing Gateway Service is finished installing.
Using Workspace Profiles with ProjectWise Publishing Server

If your ProjectWise Web Parts users are viewing DGN documents in folders which have workspace
profiles associated to them, then ProjectWise Publishing Server must have access to:
the files pointed to by the workspace profile, whether the workspace profile points to a local or
network drive
the plot drivers in the workspace pointed to by the workspace profile
When a user selects to view a DGN in ProjectWise Web Parts, ProjectWise Publishing Server is really
plotting the DGN, therefore it needs access to the plot drivers, which it normally finds in its own
workspace folder. However if a workspace profile is assigned to the ProjectWise folder, ProjectWise
Publishing Server looks where the workspace profile points, rather than its own workspace directory.
MicroStation does not deliver the DPR.PLT driver (and ProjectWise Publishing Server does) which is
what ProjectWise Publishing Server needs to generate the DPR file. If your users are receiving an error
to the effect of engine failed to generate image/rendition file, check to make sure you have a copy of
the DPR.PLT in the workspace pointed to by the workspace profile. For example, copy DPR.PLT from:
C:\Bentley\Program\BentleyPublisher\Engine\Workspace\System\plotdrv
to
P:\Workspace\System\plotdrv
ProjectWise
199

Configuring Design Compare

If you want your users to be able to select two DGN documents (or two renditions produced from
MicroStation sources) in the ProjectWise Content web part, and then see the changed, unchanged,
added, and deleted graphics between those documents in the ProjectWise Publishing and Markup web
part, you need to install and set up the ProjectWise Design Compare utility that is delivered with
ProjectWise InterPlot Server.
Note: Renditions produced from non-MicroStation sources cannot be compared. Design Compare is
designed to detect changes in the element itself. In other words, the user must actually modify the
element by moving it, adding vertices, modifying it, changing color, weight, style, or fill. The feature is
not designed to detect changes in the mere appearance of the element that are caused by level
symbology setups, plot-time design scripts, view attribute changes, or shifts in color tables.
When ProjectWise Publishing Server is installed on a 64-bit Windows Server 2008 to a 64-bit
application pool site, the Design Compare utility must be installed to a separate site that uses a 32-bit
application pool.
To Set Up Design Compare on the ProjectWise Web Server / SharePoint

Computer
1. Install SharePoint. During install, click Advanced (instead of Basic), then select the Web Front End
option (instead of Stand-alone).
2. After SharePoint is installed, go to SharePoint Central Administration.
3. Go to Application Management > Create or extend web application > Create New Web
application.
4. Set Use existing IIS Web Site and make sure that Default Web Site is selected.
5. Set Application Pool and Database Name and Authentication sections as usual.
6. Click OK, then restart IIS.
7. Create Site collection on the newly created application.
8. Install and configure the Design Compare utility as described in the following procedure.
To Set Up Design Compare on a Computer Where ProjectWise Web Server

and SharePoint Are Not Installed
1. On a computer where ProjectWise Explorer is installed, install and configure ProjectWise InterPlot
Organizer to create/store IPS and IPARM files in ProjectWise.
Follow directions in the ProjectWise InterPlot Organizer's help under the heading, Using
ProjectWise InterPlot Organizer with other ProjectWise Applications.
2. On a computer where ProjectWise Publishing Server is installed, install ProjectWise InterPlot Server.
3. Once ProjectWise InterPlot Server is installed, go to the
...\ProjectWise InterPlot Server\pwdiffwu directory and double-click the
setupDesignCompareUtility.exe file to begin installing the ProjectWise Design Compare
utility.
4. When prompted to specify a Virtual Directory Alias, enter an alias name.
ProjectWise
200

A typical name might be PWDI. This will be the virtual directory that will be used in Internet
Information Server (IIS).
5. When the Virtual Server Selection dialog opens, select your site (PWDI) and finish installation.
6. When setup is complete you must grant the local user account that IIS is using (typically
IUSR_<COMPUTERNAME>) rights to the newly created directory,
C:\Program Files\Bentley\Design Compare Utility\tmp.
To grant these rights, in Windows Explorer, open the Properties dialog for the \tmp folder, click the
Security tab, select the user from the list and turn on Read and Write permissions.
7. Also, make sure you give your Web Parts users Write permission to the Design Compare tmp
directory, if the Design Compare Virtual Directory security does not allow anonymous access, but
only allows Windows authenticated users.
8. In ProjectWise Administrator, right-click your datasource and select Properties. On the Settings
tab, expand Web Components > Design Compare Utility Address, and double-click the icon below
it.
To configure the Design Compare utility to run in secure mode, in the Specify server address dialog
turn on Server uses secure protocol, then enter the name of the computer on which the Design
Compare utility is installed exactly as it appears in your certificate, followed by a forward slash,
followed by the name of the Virtual Directory Alias specified in step 4. For example, https://
interplotserver/PWDI. To find the computer name as it appears in the certificate, open
Internet Information Services, go to Web Sites > Default Web Site > Properties > Directory
Security tab > View Certificate > Issued to.
or
To configure the Design Compare utility to run in regular mode, in the Specify server address dialog
turn OFF Server uses secure protocol, then enter the name of the computer on which the Design
Compare utility is installed, followed by a forward slash, followed by the name of the Virtual
Directory Alias specified in step 4. For example, http://interplotserver/PWDI.
Note: If the Default Web Site port has been changed from the default port 80, or if you install the
Design Compare utility to a site other than the Default Web Site, then when specifying the Design
Compare utility address, you will also need to specify the port after the server name, and before the
Virtual Directory Alias. For example, https://interplotserver:88/PWDI
Note: The Document > Design Compare menu will be disabled in the ProjectWise Content web part
if the Web Components > Design Compare Utility Address datasource setting is empty, or if it
contains an incorrect Design Compare utility address.
To Set Up a New IIS Site (for Design Compare) That Uses a 32-bit Application
Pool, on a 64-bit Windows Server 2008 Computer
1. In the Control Panel, go to Administrative Tools and launch Internet Information Services (IIS)
Manager using the Run as Administrator option.
2. Under Connections, expand the local computer, right-click Web Sites and select Add Web Site.
3. In the Add Web Site dialog, do the following:
a. In the Web site name field, enter a name for the site, such as: PWDI
b. In the Physical Path field, enter the physical location to where the site lives.
ProjectWise
201

Configuring ProjectWise Web Parts in SharePoint
4.
5.
6.
7.
8.
9.
10.
11.
c. In the Port field, make sure you specify a port that is different than the port ProjectWise
Publishing Server is using.
d. Click OK.
Under Connections, expand the local computer and select Application Pools.
In the Applications Pools list, right-click the PWDI application pool and select Advanced Settings.
In the Advanced Settings dialog, do the following:
a. Set .NET Framework version to No Managed Code.
b. Set Enable 32-Bit Applications to True.
c. Set Managed Pipeline Mode to Classic.
d. Set Identity to NetworkService.
e. Click OK.
Under Connections, select the local computer, then click Features View.
In the Features list, double-click MIME Types.
Under Actions, click Add.
In the Add MIME Type dialog, do the following:
a. In the File Name Extension field, enter: .dpr
b. In the MIME Type field, enter: application/vpr
c. Click OK.
Close IIS Manager.
Authentication Methods for Design Compare

Design Compare supports both Windows and Anonymous authentication methods (Site Properties >
Directory Security > Edit > Anonymous or Windows access) when ProjectWise Publishing Server is
running as a web server extension.
When Windows access is enabled on the website where ProjectWise Publishing Server is installed, you
must also configure WinHTTP proxy settings to include the ProjectWise Publishing Servers computer
name in the proxy bypass list (for details, see http://support.microsoft.com/kb/291008).
On 64-bit operating systems, make sure you use the 32-bit configuration tools located in the
%systemroot%\SysWOW64 directory.
On 64-bit Windows Server 2008 SP2 and Windows Server 2008 R2, the proxycfg utility is not
available. Instead you must use the %systemroot%\SysWOW64\netsh winhttp set proxy
command to configure proxy settings. Also, if User Access Control is enabled, you must run this
command with elevated privileges.

Once ProjectWise Web Server or ProjectWise Web View Server has been deployed to a SharePoint site,
you can add ProjectWise Web Parts to your SharePoint team site. After adding them, you need to
connect them to a ProjectWise datasource. Once connected, then all your users have to do is point a
supported web browser to the SharePoint team site and they will be automatically logged in to the
datasource, either using their own Windows domain account if you have configured ProjectWise Web
Parts to use single sign-on, or using the ProjectWise account you have specified all ProjectWise Web
Parts users to use.
ProjectWise
202

Note: ProjectWise Web Server requires that the underlying website has Read and Script permissions
enabled in IIS. These permissions are typically configured automatically by your SharePoint installation.
Note: Make sure your ProjectWise Integration Server is also of the current version. The ProjectWise
Integration Server of the datasource you connect to must be of the same version as the ProjectWise Web
Server and Web View Server.
To Add ProjectWise Web Parts to a SharePoint Page

1. Go to the SharePoint page where you want to add a ProjectWise web part and select Site Actions >
Edit Page.
2. Go to the zone you want to configure and click Add a Web Part.
The following ProjectWise web parts are available:
ProjectWise Content
ProjectWise Navigation Tree
ProjectWise Navigator
ProjectWise Properties
ProjectWise Publishing and Markup
ProjectWise Search
ProjectWise Spatial Content
In SharePoint 2010, under Categories, click ProjectWise. Under Web Parts, select one or more
ProjectWise web parts and click Add.
or
In SharePoint 2007, select one or more ProjectWise web parts from the Add Web Parts window and
click Add.
Figure 2: Adding ProjectWise Web Parts in SharePoint 2010
ProjectWise
203

Note: If you only need to use the Navigation web part, you can add it to the page and use it
independently without adding any other ProjectWise Web Parts to the page.
Note: If you only need to use the Content web part, you can add it to the page and use it
independently without adding any other ProjectWise Web Parts to the page. Before adding the
Content web part and connecting to your datasource, make sure the user setting, Document list Show subfolders is on. This lets you see projects and folders in the Content web part, without
requiring the Navigation web part on the page. User settings can be modified from either
ProjectWise Explorer or ProjectWise Administrator.
Note: If you only need to use the Search web part, you can add it to the page and use it
independently without adding any other ProjectWise Web Parts to the page. Whenever you run a
search and the Content web part is not present, a new window opens to display the results of the
search, if there are any.
Note: It is recommended that you avoid adding the Properties web part to the page on SharePoint
2007, as some property values may not display correctly. When the Properties web part is not
present on the page and you go to view properties, a new Properties web part window will open
anyway, to display the properties of the selected document, folder, or project.
Tip: To remove a ProjectWise Web Part from the page, click the Edit menu in the upper-right corner
of the web part and select Close.
When you first add your ProjectWise Web Parts, none of them are connected to any datasource. That is
covered in the following procedures. When using SharePoint, it is recommended that you configure the
ProjectWise Web Parts to use single sign-on.
To Connect Web Parts to a Datasource Using Single Sign-on, on a SharePoint

Website
2. On the ProjectWise Web Server computer, log in to the SharePoint site with a Windows domain
account that has administrative rights to that site. Make sure this domain account also exists in the
ProjectWise datasource you plan to connect to.
3. Make sure that your ProjectWise users having Windows domain-based accounts are also added to
the SharePoint site.
If you need to set this up, in SharePoint go to Site Actions > Site Settings > Users and Permissions
> People and groups, click New > Add Users, then add your Windows domain groups and/or
Windows domain users. For most users, you should set their permissions to Team Site Visitors
[Read].
Note: This [Read] permission does not mean that the documents and folders found in ProjectWise
Web Parts are read-only, it simply means that users can access the SharePoint site, but they cannot
change anything on the site. For example, they will not be able to add a web part or close a web part.
If you want some of your users to have this ability, then for those users you can set their permissions
to Team Site Members [Contribute]. Team Site Members can also, for example, log in to the
datasource as a different user.
4. Add ProjectWise Web Parts to the page.
ProjectWise
204

5. In any ProjectWise web part (Navigation Tree web part is used for this example), select Edit >
Modify Shared Web Part.
A settings window for that web part opens on the right side of the screen.
6. Under Select web parts to connect, turn on all the ProjectWise Web Parts listed.
7. From the Location list, select the ProjectWise datasource you want to connect to.
Tip: The Location list displays whatever datasources are configured to display as the result of
configuring the ProjectWise network on this computer, and will contain the same datasources you
saw on the Single Sign-On Settings dialog in step 1.
8. Turn on Use Windows credentials (SSO) and click OK.
ProjectWise
205

You, the administrator, are now logged in to the datasource with the same Windows domain account
you used to log in to SharePoint (which also exists in the datasource).
9. When prompted, install the ProjectWise Web Server Client Components.
This installs the following ActiveX controls:
ProjectWise Web File Transfer ActiveX Control used by any operation that downloads a file to
your local web parts working directory
Bentley DGN Navigator (ActiveX) Control used by the Navigator web part
VPR ActiveX Control used by the Publishing and Markup web part
Spatial ActiveX Control used by the Spatial Content web part
10. In SharePoint, click Exit Edit Mode.
11. Make sure your users' Internet Explorer Internet Options are configured properly.
a. Have your users open Internet Explorer and open the Internet Options dialog (Tools > Internet
Options).
b. On the Security tab, and click Custom Level. In the Security Settings dialog, scroll down to the
User Authentication section and turn on Automatic logon with current username and
password. Click OK to close the Security Settings dialog.
c. On the Advanced tab, scroll down to the Security section and turn on Enabled Integrated
Windows Authentication (requires restart).
d. Click OK.
12. Have your users' point their browsers to the SharePoint site.
They will be automatically logged in to the datasource with their Windows domain account,
assuming they are logged in to their operating system with their Windows domain account, and
assuming that the domain account exists both in the datasource and also in SharePoint.
Have them install the ProjectWise Web Server Client Components when prompted.
To Connect Web Parts to a Datasource Without Single Sign-On, on a

SharePoint Website
If you are testing ProjectWise Web Parts in SharePoint, a quick way to configure the site is to connect to
a datasource without using single sign-on. You can always go back later and configure single sign-on
using the procedure above. Note that the procedure below should only be used for testing and is not
recommended for production. This is because if other users are using this site, they will all be
automatically logged in to the datasource with the same user account you connected with.
1. Add ProjectWise Web Parts to the page.
ProjectWise
206

2. In any ProjectWise web part (Navigation Tree web part is used for this example), select Edit >
A settings window for that web part opens on the right side of the screen.
3. Under Select web parts to connect, turn on all the ProjectWise Web Parts listed.
4. From the Location list, select the datasource you want to connect to.
The Location list displays whatever datasources are configured to display as the result of
not listed, close this SharePoint page, configure the ProjectWise network, then open this SharePoint
page again. The ProjectWise network is configured using the ProjectWise Network Configuration
Settings dialog. See Connecting Individual Clients to the Server for details.
5. Enter a ProjectWise user name and password (can be a logical account or a Windows domain
account) and click OK.
ProjectWise
207

You are now logged in to the datasource with the selected account.
7. In SharePoint, click Exit Edit Mode.
To Modify a Web Part's General SharePoint Settings

1. In the upper-right corner of a ProjectWise web part, click the Edit menu and select Modify Shared
Web Part.
On the right side of the screen, a settings window opens.
2. Expand Appearance, Layout, and Advanced, make the necessary changes, and click OK.
These settings are not related to ProjectWise. For more information about them, click the Help link at
the top of the team site page.
ProjectWise
208

To Set the Topmost Folder or Project That Displays in the Navigation,

Content, and Spatial Content Web Parts
By default, the Documents root folder is the topmost folder in any datasource. If necessary, you can set
any folder or project in the datasource to be the topmost folder that displays in the Navigation, Content,
and Spatial Content web parts.
1. In the Navigation, Content, Spatial Content, or Search web part, click the Edit menu and select
2. In the settings window, click the Browse button next to the Root path field.
3. In the window that opens, select a folder or project and click OK.
4. Back in the settings window, click OK.
The root folder for the Content, Navigation, and Spatial Content web parts changes from the
Documents root folder, to whatever project or folder you set here.
To Set Whether Searches Will Search the Topmost Folder, or the Entire
Datasource
The Search web part has a setting called Limit to Root Path. When this setting is on (the default), then
searches will only search within the folder that is set as the topmost folder to display in the Navigation,
Content, and Spatial Content web parts. If this setting is on and no top folder is set, then searches will
search the entire datasource. If you turn this setting off and there is a folder set as the topmost folder,
ProjectWise
209

Configuring ProjectWise Web Parts in a Standalone IIS Website
then searches will search the entire datasource instead of just searching the topmost folder and its
subfolders.
1. In the Search web part, click the Edit menu and select Modify Shared Web Part.
2. In the Search settings window, scroll to the bottom and expand Miscellaneous.
If you want searches to search only the topmost folder and its subfolder, turn on Limit to Root Path.
or
If you want searches to always search entire datasource, turn off Limit to Root Path.
4. Click OK.
To Set the Search Web Part's Default Search Method

1. In the Search web part, click the Edit menu and select Modify Shared Web Part.
2. In the Search settings window, expand Miscellaneous, and set Search Method to General or
Advanced.
3. Click OK.
The Search web part is refreshed to show the interface of the selected search mode.

When deploying ProjectWise Web Server or ProjectWise Web View Server in a standalone IIS website
that is, an IIS website without SharePoint you can use one of the delivered ASP pages
(default.aspx or defaultspatial.aspx) which has the ProjectWise Web Parts preconfigured,
or you can create and configure your own ASP pages.
This section discusses how to configure IIS for your standalone ProjectWise Web Server or ProjectWise
Web View Server website, and how to connect it to a ProjectWise datasource. Once connected, all your
users have to do is point their supported web browser to this website and they will be automatically
logged in to the datasource, either using their own Windows domain account if you have connected
ProjectWise Web Parts using single sign-on, or using the ProjectWise account you have specified all
ProjectWise Web Parts users to use.
Note: Make sure your ProjectWise Integration Server is also of the current version. The datasource's
ProjectWise Integration Server you connect to must be of the same version as the ProjectWise Web
Server and Web View Server.
Configuring IIS Settings in a Standalone IIS Deployment

When you have deployed a ProjectWise Web Server so that users within the organization (internal
users) can have web access to ProjectWise, you should configure the standalone IIS website to use
Windows authentication.
ProjectWise Web Server can also be used to provide external consultants access to ProjectWise
managed content. For this to work, you need a website that external users can securely log in to and
access only the data they have been authorized to access. In this case, the recommendation is to deploy
ProjectWise Web Server or ProjectWise Web View Server to a standalone IIS website, enable
anonymous access, and finally use ProjectWise native users used to authenticate external users.
ProjectWise
210

Note: Anonymous authentication is less secure than Windows authentication, so considering taking the
following additional security precautions if configuring a ProjectWise Web Server website with
anonymous authentication:
Configure the ProjectWise Web Server website to use SSL.
Restrict ProjectWise user rights to only those that are necessary (for example, disable the users
ability to delete documents and folders, if not required).
Enable Your Standalone IIS Websites Read and Script Permissions

1.
2.
3.
4.
5.
6.
Open IIS Manager.

In the Connections pane, navigate to and select the site you deployed to.
Click the Features View tab to go to the site's Home page.
On the Home page, in the IIS section, double-click Handler Mappings.
In the Actions pane, click Edit Feature Permissions.
In the Edit Feature Permissions dialog, enable the Read and Scripts permissions, then click OK.
Configure Your Standalone IIS Website to Use Windows Authentication

1.
2.
3.
4.
5.
Open IIS Manager.

On the Home page, in the IIS section, double-click Authentication.
On the Authentication pane, make sure Anonymous Authentication is set to Disabled, and make
sure Windows Authentication is set to Enabled.
Configure Your Standalone IIS Website to Use Anonymous Access

1.
2.
3.
4.
5.
Open IIS Manager.

On the Home page, in the IIS section, double-click Authentication.
On the Authentication pane, make sure Anonymous Authentication is set to Enabled.
Connecting Web Parts to the Datasource, in a Standalone IIS Deployment

You can configure the Web Parts in your standalone IIS website so that users can log in using single
sign-on, or using one ProjectWise account for all users who connect.
To Connect Web Parts to a Datasource Using Single Sign-on, on a Standalone IIS Website
2. On the ProjectWise Web Server computer, make sure you are logged in to the computer with a
Windows domain account. Make sure this domain account also exists in the ProjectWise datasource
you plan to connect to.
3. On the ProjectWise Web Server computer, launch Internet Explorer and enter either:
ProjectWise
211

http://localhost/default.aspx
or
http://localhost/defaultspatial.aspx
The delivered sample ProjectWise home page opens and displays the login form.
Tip: The Location list displays whatever datasources are configured to display as the result of
configuring the ProjectWise network on this computer, and will contain the same datasources you
saw on the Single Sign-On Settings dialog in step 1.
5. Click Sign in using your Windows credentials.
6. Once the credentials are verified, click Log in.
You, the administrator, are now logged in to the datasource with the same Windows domain account
you used to log in to the computer, which also exists in the datasource.
ProjectWise
212

8. Make sure your users' Internet Explorer Internet Options are configured properly.
a. Have your users open Internet Explorer and open the Internet Options dialog (Tools > Internet
Options).
b. On the Security tab, and click Custom Level. In the Security Settings dialog, scroll down to the
User Authentication section and turn on Automatic logon with current username and
password. Click OK to close the Security Settings dialog.
c. On the Advanced tab, scroll down to the Security section and turn on Enabled Integrated
Windows Authentication (requires restart).
d. Click OK.
9. Have your users' point their browsers to the ProjectWise Web Server by entering one of the
following in the Address field:
http://webserver:portnumber/default.aspx
or
http://webserver:portnumber/defaultspatial.aspx
where webserver is the name of the computer on which ProjectWise Web Server is installed, and
portnumber is the port that the default website is using.
They are now automatically logged in to the datasource, assuming they have a Windows domain
account in the datasource, and assuming they are also logged into their operating system with that same
domain account.
Have your users install the ProjectWise Web Server Client Components when prompted.
The next time they visit this site, they will be automatically logged in to the same datasource using
single sign-on.
To Connect Web Parts to a Datasource Without Single Sign-On, on a Standalone IIS Website
1. On the ProjectWise Web Server computer, launch Internet Explorer and enter either:
http://localhost/default.aspx
or
http://localhost/defaultspatial.aspx
The delivered sample ProjectWise home page opens and displays the login form.
ProjectWise
213

Note: The Location list displays whatever datasources are configured to display as the result of
not listed, close this browser, configure the ProjectWise network, then open a browser to this page
again. The ProjectWise network is configured using the ProjectWise Network Configuration Settings
dialog. See Connecting Individual Clients to the Server for details.
3. In the User Name and Password fields, enter the credentials of a ProjectWise user account.
This can be a logical account or a Windows-based account.
4. Click Log in.
You, the administrator, are now logged in to the datasource with the specified account.
ProjectWise
214

Configuring ProjectWise Web Parts Client Computers
6. Have your users' point their browsers to the ProjectWise Web Server by entering one of the
following in the Address field:
http://webserver:portnumber/default.aspx
or
http://webserver:portnumber/defaultspatial.aspx
where webserver is the name of the computer on which ProjectWise Web Server is installed, and
portnumber is the port that the default website is using.
7. When the sample page opens, have your users:
a. Select the ProjectWise datasource to connect to from the Location list.
b. Enter the correct user name and password and click OK.
c. Install the ProjectWise Web Server Client Components when prompted.
The next time they visit this site, the last used datasource and user name are remembered, and they
will only have to enter their password.

Adding the Web Parts Site to the Trusted Sites List
Adding the Web Parts website address to your browser's Trusted sites list is a requirement for using
ProjectWise Web Parts.
1.
2.
3.
4.
5.
6.
In Internet Explorer, go to Tools > Internet Options.

In the Internet Options dialog, select the Security tab.
Select Trusted sites and click the Sites button.
In the Trusted sites dialog that opens, type your Web Parts website address and click Add.
Click OK to close the Trusted sites dialog.
Click OK to close the Internet Options dialog.
Configure Internet Explorer Security Settings

1. In Internet Explorer, go to Tools > Internet Options > Security tab, select Trusted sites, click Custom
Level.
The Security Settings dialog opens for the Trusted Sites Zone.
2. For ActiveX controls to work properly in Internet Explorer, make sure the following options are set:
ProjectWise
Category
Setting
Value
ActiveX controls and plug-ins
Download signed ActiveX controls
Prompt
Download unsigned ActiveX controls
Disable
Initialize and script ActiveX controls not

marked as safe for scripting
Disable
215

Category
Scripting
Setting
Value
Run ActiveX controls and plug-ins
Enable
Script ActiveX controls marked safe for

scripting
Enable
Active Scripting
Enable
Allow paste operations via script
Enable
Scripting of Java applets
Enable
3. (Windows Server 2008 only) For downloading to work properly when using Internet Explorer on
Windows Server 2008, make sure the following options are set:
Category
Setting
Value
Downloads
Automatic prompting for file downloads
Enable
4. (Internet Explorer 9 only) Additional settings are required when using Internet Explorer 9:
Category
Setting
Value
Scripting
Allow Programmatic clipboard access
Enable
User Authentication
Logon
Automatically logon
with current user name
and password
5. Click OK to save changes and close the Security Settings dialog.

6. (Windows Vista only) For copy outs to function properly when using Internet Explorer on Windows
Vista, on the Security tab of the Internet Options dialog, turn off the setting, Enable Protected Mode.
7. Click OK to save changes and close the Internet Options dialog.
Turning Off Your Browser's Popup Blocker

Occasionally Web Parts needs to open items in a new window. For example, if you right-click a folder
and select Properties when the Properties web part is not present, the properties of the selected folder
display in a new window. When your popup blocker is enabled, these additional windows will not open;
therefore you should disable the popup blocker in your browser. See your browser's documentation for
instructions.
Installing .NET Framework 3.5 for the Navigator Web Part

ProjectWise Web Parts users who are using Windows 8 will need to install .NET Framework 3.5 on their
computers, in order to use the Navigator web part.
ProjectWise
216

User Settings for ProjectWise Web Parts Users
Remotely Installing ActiveX Controls for Users

When users visit the Web Parts site for the first time, they are prompted to download the ProjectWise
Web Server Client Components, which installs the following:
In some cases, you may have to remotely install these ActiveX controls for your users. For example, your
users may not have the administrative permissions on their computer necessary to install the ActiveX
controls. Another possibility is that you have upgraded the minor version of ProjectWise Web Server
and Web View Server (for example, from the initial version of 8.11.11.x to a later update of 8.11.11.x),
while your users are still using the ActiveX controls that were delivered with the original ProjectWise
Web Server and Web View Server installation, causing the two to become out of sync and requiring that
the users' ActiveX controls be upgraded.
To remotely install the ActiveX controls, you can either use a Group Policy to install them, or you can
remotely connect to your users computers and manually install them. When remotely installing the
ActiveX controls, you need to launch these two installers:
ProjectWise Web and Web View Servers V8i (SELECTseries 4) Client Components.msi this installs
the ProjectWise Web File Transfer ActiveX Control, the VPR ActiveX Control, and the Spatial ActiveX
Control
DgnNavigatorControlAx.msi this installs the Bentley DGN Navigator (ActiveX) Control
Note:
These installers are delivered with ProjectWise Server Setups, but are not listed when you launch on the
master setup.exe installer. Instead, you will find them in the ...\product\pwwebserver folder.
User Settings for ProjectWise Web Parts Users

The following user settings are specific to ProjectWise Web Parts users. Read the following to determine
if you need to configure these settings for any of your ProjectWise Web Parts users.
Working
Directory - When
Accessing
ProjectWise
Over The Web
Used to preset the user's working directory when using ProjectWise Web Parts.
In a new datasource, the default ProjectWise Web Parts working directory for
every user is set to:
%LocalAppData%\ProjectWise\WebWorkDir\%Datasource%
When this default working directory is set as shown above, the user's working
directory will be created automatically on their computer when they first log in to
the datasource through ProjectWise Web Parts. If it cannot be created in the
specified location for any reason, then the user will be prompted to set their own
working directory upon logging in.
ProjectWise
217

Support for Microsoft Forefront TMG
The user can always change the location of their working directory by selecting
Tools > Working Directory from the Content web part, however, changing the
location of the working directory from ProjectWise Web Parts does not change the
value set for this user setting in the datasource. If the user changes their working
directory from ProjectWise Web Parts on one computer, but then uses ProjectWise
Web Parts from another computer, the working directory on the new computer
will be created based on the value set for the user setting in ProjectWise
Administrator.
To change a user's default ProjectWise Web Parts working directory, expand this
setting, select the default location displayed, then select it again and wait for it to
become editable. You can enter plain text, a variable, or both. The value you enter
should specify the path to and including the folder name you want the user to use.
Note that if you specify a drive that does not exist on the user's computer, then the
user will simply be prompted to select another location for the working directory.
You can use any or all of the following variables to help create a unique
ProjectWise Web Parts working directory folder name for your users:
%LocalAppData% this variable will be expanded to the user's local folder
that stores the data for local applications. For example, on Windows Vista this
would expand to C:\Users\[user.name]\AppData\Local
%Datasource% the name of the datasource the user is logging in to
%User% the user's ProjectWise user name
If you modify the default ProjectWise Web Parts working directory setting for any
user, then instead of the working directory getting created automatically when
they log in to the datasource through ProjectWise Web Parts, they will be
prompted to create the working directory specified here. If you want to change the
default ProjectWise Web Parts working directory and you also want it to get
created automatically (without prompting the user), then you need to apply a
group policy that lets the working directory get created automatically.
User can only log
in through
ProjectWise Web
View Server
ProjectWise Web View Server is intended for casual ProjectWise Web Parts users
who only need read-only access to ProjectWise. The benefit of using ProjectWise
Web View Server is that ProjectWise Passport usage is not reported in
SELECTserver when a user logs in to ProjectWise, using ProjectWise Web Parts,
through a ProjectWise Web View Server.
If you have deployed a ProjectWise Web View Server, turn this user setting on for
those users who will only be connecting to ProjectWise through ProjectWise Web
View Server (if they try to access ProjectWise through ProjectWise Web Server or
ProjectWise Explorer they will not be permitted to log in). When this setting is off,
there is no restriction to which client the user can log in through.
Support for Microsoft Forefront TMG

ProjectWise Web Server and Web View Server supports Microsoft Forefront Threat Management
Gateway (Forefront TMG) 2010 with the latest updates. (Forefront TMG is Microsofts replacement for
ISA Server, which ProjectWise Web Server and Web View Server supported in previous releases.)
ProjectWise
218

Support for Microsoft Network Load Balancing
Support for Microsoft Network Load Balancing

ProjectWise Web Server and Web View Server supports Microsoft Network Load Balancing. For this to
work properly:
You must set the Network Load Balancing parameter, Affinity, to Single, on the Add/Edit Port Rules
dialog.
In the ecom.config file (located in the site's directory), the key="PublicAddress" setting should
be set to the external server name, when the internal server name differs from the external name.
For example:
<add key="PublicAddress" value="https://server1.bentley.com:442"
/>
Upgrading ProjectWise Web Server on SharePoint

Note:
If upgrading from SharePoint 2007 to SharePoint 2010, the SharePoint upgrade of sites from which
ProjectWise was undeployed will fail because SharePoint cannot find the ProjectWise web parts.
Therefore, you will need to rerun the SharePoint Configuration Wizard again after redeploying
ProjectWise Web Server to those sites. After configuration, you will need to update the site appearance
from SharePoint 2007 to SharePoint 2010 by connecting to the website and selecting Site Actions >
Visual Upgrade > Update the user interface.
Note:
Running the SharePoint Configuration Wizard again is also required after upgrading SharePoint 2010 to
SharePoint 2010 SP1.
To Upgrade ProjectWise Web Server on the Same or Later Version of

SharePoint
1. Undeploy ProjectWise Web Server and/or ProjectWise Web View Server from all SharePoint
websites.
The same wizard used to deploy ProjectWise Web Server is the same wizard used to undeploy it.
Depending on the version of the previous installation, use one of the following paths to launch the
deployment wizard and follow the prompts to completion:
Start > Programs > Bentley > ProjectWise V8 XM > Web Parts > ProjectWise Web Part
Deployment Wizard
Start > Programs > Bentley > ProjectWise V8i > Web Server and Web View Server >
ProjectWise Web Server Deployment Wizard or ProjectWise Web View Server Deployment
Wizard
Start > Programs > Bentley > ProjectWise V8i (SELECTseries 1) > Web Server and Web
View Server > ProjectWise Web Server Deployment Wizard or ProjectWise Web View
Server Deployment Wizard
ProjectWise
219

Undeploying and Uninstalling ProjectWise Web Server and Web View Server
2. Uninstall ProjectWise Web Server.
Depending on the version of the previous installation, uninstall:
ProjectWise Web Server Components for Web Parts (if the version was ProjectWise V8 XM Edition)
ProjectWise Web Server and Web View Server (if the version was ProjectWise V8i or later)
3. If the previous version was ProjectWise V8 XM Edition, also uninstall ProjectWise Explorer.
ProjectWise Explorer is no longer a requirement of ProjectWise Web Server and Web View Server.
4. If you are also upgrading your version of SharePoint, uninstall the previous version now, then install
a supported newer version.
5. Install ProjectWise Web Server and Web View Server V8i (SELECTseries 4) and deploy ProjectWise
Web Server and/or ProjectWise Web View Server as needed.
To Upgrade SharePoint When ProjectWise Web Server Is Already Deployed

1. Undeploy ProjectWise Web Server and ProjectWise Web View Server from all SharePoint sites.
2. Upgrade the version of SharePoint.
3. Redeploy ProjectWise Web Server and ProjectWise Web View Server to the desired SharePoint
websites.
Undeploying and Uninstalling ProjectWise Web Server and Web

View Server
If necessary you can undeploy a particular instance of ProjectWise Web Server or ProjectWise Web
View Server from a website, and leave the other deployments deployed.
If you need to completely uninstall ProjectWise Web Server and Web View Server from your computer,
you must first undeploy all instances of ProjectWise Web Server and ProjectWise Web View Server that
are currently deployed.
Note: Because installing ProjectWise Web Server with SharePoint search integration also takes care of
deploying ProjectWise Web Server to the selected SharePoint site, you cannot use the Deployment
Wizard to undeploy ProjectWise Web Server from the site. In this case only, simply uninstalling
ProjectWise Web Server will also undeploy ProjectWise Web Server from the site.
Tip: If you have a ProjectWise Language Pack installed and you are uninstalling ProjectWise Web Server
and Web View Server, make sure you uninstall the ProjectWise Language Pack after uninstalling
ProjectWise Web Server and Web View Server.
ProjectWise
220

To Undeploy ProjectWise Web Server and/or Web View Server

1. From the Windows Start menu, launch the Deployment Wizard for the type of server you have
deployed:
View Server > ProjectWise Web Server Deployment Wizard
or
View Server > ProjectWise Web View Server Deployment Wizard
2. When the selected Deployment Wizard opens, click Next.
3.
4.
5.
6.
ProjectWise
The Deployment Type page opens, displaying the virtual servers (websites) currently available in IIS,
and whether or not ProjectWise Web Server or ProjectWise Web View Server is currently deployed
to any of them.
Select the Remove option and click Next.
On the Virtual Server Selection page, select the websites from which to undeploy the selected server
type (ProjectWise Web Server or ProjectWise Web View Server click Next.
When prompted, click Yes to confirm removal.
When removal is complete, click Finish.
221

ProjectWise
222

Configuration 10
Bentley i-model Composition Server for PDF Overview
Bentley i-model Composition Server for PDF is a flexible, scalable server-based system that lets you
create renditions (PDF, JPEG, TIFF, and/or CALS) from documents stored in ProjectWise.
Administrators use the Bentley i-model Composition Server Administrator interface (inside
Orchestration Framework Administrator) to create, schedule, run, monitor, and review batch rendition
jobs, while ProjectWise Explorer users can run on-demand rendition jobs on selected documents, flat
sets, folders, and/or projects. Upon completion of the job, the new rendition documents are stored in
ProjectWise, and if selected an email notification is sent to the user who ran the job. In ProjectWise
Administrator, the administrator is also responsible for defining various job-related settings under the
Renditions datasource node.
Tip: As delivered, Bentley i-model Composition Server for PDF lets you distribute the newly created
renditions (and/or source documents) to any project or folder in the same datasource, or to another
datasource altogether. Through custom connectors you can distribute to other document management
systems. Contact Bentley Professional Services about the availability of custom connectors.
Configuration Checklist for Bentley i-model Composition Server

for PDF
This checklist assumes that ProjectWise Integration Server is already installed on another computer and
at least one datasource is already configured.
Note: Bentley i-model Composition Server for PDF requires a Bentley i-model Composition Server
license.
Caution: For performance reasons it is recommended that you install Bentley i-model Composition
Server for PDF on a dedicated server, and that you do not install it on the same computer as any of
these:
ProjectWise Integration Server

ProjectWise Web Server
Caution: Do not attempt to run Bentley i-model Composition Server for PDF and ProjectWise
Distribution Service on the same computer. This configuration is not supported.
ProjectWise
223
Bentley i-model Composition Server for PDF Configuration

Configuration Checklist for Bentley i-model Composition Server for PDF
Framework Service, when you encounter the Please Provide Credentials page of the installer. This
account:

expires.
and Bentley i-model Composition Server for PDF.
6. Make sure Microsoft Message Queuing (MSMQ) is enabled and that the service is running.
See Before You Install ProjectWise Orchestration Framework Service for details about enabling MSMQ.
Web Server
Default Document
Static Content
Security
Request Filtering
ASP.NET 3.5
ASP.NET 4.5
ISAPI Extensions
ISAPI Filters
Management Tools
ProjectWise
224

Configuration Checklist for Bentley i-model Composition Server for PDF
Web Server
Static Content
Default Document
ASP.NET
.NET Extensibility
ISAPI Extensions
ISAPI Filters
Security
Request Filtering
Management Tools
8. In Server Manager, install the necessary features.
For Windows Server 2012, the following features are required:
.NET Framework 3.5 Features
.NET Framework 3.5 (Includes .NET 2.0 and 3.0)
HTTP Activation
.NET Framework 4.5 Features
.NET Framework 4.5
ASP.NET 4.5
WCF Services
HTTP Activation
TCP Port Sharing
Message Queuing
Message Queuing Services
Message Queuing Server
For Windows Server 2008, the following features are required:
.NET Framework 3.5.1 Features
.NET Framework 3.5.1
WCF Activation
HTTP Activation
Non-HTTP Activation
Message Queuing
Message Queuing Services
ProjectWise
225

Setting Up the Bentley i-model Composition Server for PDF Working Directory
Message Queuing Server
10. Set up the Bentley i-model Composition Server for PDF working directory.
11. Install the Prerequisites for Bentley Desktop Applications (this is a separate download, available
from Bentley SELECT).
12. Install the print engine or engines necessary for publishing renditions from your CAD documents (at a
minimum, install MicroStation V8i (SELECTseries 3) or Bentley View V8i (SELECTseries 3)).
13. Install and configure the applications required for publishing renditions from Office documents.
14. Install ProjectWise InterPlot Organizer V8i (SELECTseries 4) (this is a separate download, available
from Bentley SELECT).
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
ProjectWise InterPlot Organizer requires that you restart the computer after installation, however
you can wait until you finish configuring this computer to do the restart.
Install ProjectWise Explorer V8i (SELECTseries 4).
Install Bentley i-model Composition Server for PDF V8i (SELECTseries 4).
Add the Bentley i-model Composition Server for PDF computer to the Trusted Servers list in the
ProjectWise Integration Server's dmskrnl.cfg file.
Configure the [RenditionWebServices] section in the ProjectWise Integration Servers
dmskrnl.cfg file.
Set up the default user.
In order to receive email notifications, make sure that each user who runs a job has a valid email
address specified in their user properties.
Make sure that the storage area used by the destination folder/datasource has adequate disk space
for the new rendition documents. You should estimate about the same amount of free disk space that
you set aside for the Bentley i-model Composition Server for PDF working directory.
In ProjectWise Administrator, create the rendition profile components necessary to run jobs in
Bentley i-model Composition Server Administrator. (See Rendition Administration in the
ProjectWise Administrator help for details.)
In ProjectWise Administrator, create the rendition profiles necessary for users to create renditions
in ProjectWise Explorer. (See Rendition Administration in the ProjectWise Administrator help for
details.)
In ProjectWise Explorer, optionally assign rendition profiles to projects and folders. (See the
ProjectWise Explorer help for details.)
At this point you should restart the Bentley i-model Composition Server for PDF computer.
Setting Up the Bentley i-model Composition Server for PDF

Working Directory
Bentley i-model Composition Server for PDF needs a shared working directory so it can copy out the
files it has been told to process. Before installing Bentley i-model Composition Server for PDF, you need
to set up this working directory by:
creating and sharing a folder (for example, C:\ics_workingdir)
making sure your users have access to the shared working directory. Specifically, the user installing
Bentley i-model Composition Server for PDF needs full control, as well as any user who will be
creating, modifying, or running Bentley i-model Composition Server for PDF jobs.
ProjectWise
226

Installing the Required CAD Print Engines
making sure that the number of simultaneous users that can access the working directory is high
enough for your needs. This is a Windows permission, set on the folder itself.
The working directory is recommended to be set up on the same computer as Bentley i-model
Composition Server for PDF. Make a note of the path to this working directory, as you will be prompted
to specify the location of this folder during Bentley i-model Composition Server for PDF installation.
To get an idea of how much free disk space to set aside for the working directory, consider that the
working directory will hold:
a copy of all files selected for a job along with all of their reference files
all renditions created by the job
job history
additional data extracted from ProjectWise such as document and folder properties
system files, such as installed connectors, installed extensions, and logging files
Tip: As you run jobs, the working directory will continue to grow in size. You can periodically empty the
working directory using Orchestration Framework Administrator. It is recommended that you never
manually delete files from the working directory.
Installing the Required CAD Print Engines

To publish renditions from DGN and DWG source documents, Bentley i-model Composition Server for
PDF requires that you have at least one CAD print engine installed on the Bentley i-model Composition
Server for PDF computer. You can use multiple CAD print engines if needed. When multiple engines are
installed, ProjectWise InterPlot Organizer will load the correct engine(s) at runtime to process the
source documents. ProjectWise application associations are used to determine which source documents
require which print engine.
Which CAD print engine or engines should you install?

Bentley i-model Composition Server for PDF supports using either MicroStation V8i (SELECTseries 3) or
Bentley View V8i (SELECTseries 3) as the default print engine for publishing renditions from DGN and
DWG source documents. ProjectWise InterPlot Organizer delivers Bentley View if needed, and installing
ProjectWise InterPlot Organizer will automatically install Bentley View by default if neither
MicroStation nor Bentley View is detected on the computer. For many organizations, either of these may
be the only CAD print engine you need to install.
For other organizations, you may have some DGNs which require special processing and which
MicroStation or Bentley View alone cannot adequately publish. In those cases, you will need to install (in
addition to MicroStation or Bentley View) the necessary print engines to process those other DGNs.
What are some examples of when you might need additional CAD print
engines?
1. AECOsim Building Designer is the preferred print engine to use for DGN documents authored by
Bentley building and architecture applications. If you have not yet adopted AECOsim Building
Designer and are still using earlier Bentley architectural products, please contact Bentley technical
support for assistance.
2. Some geo/mapping products may need to be installed, to ensure full fidelity with the screen display.
ProjectWise
227

Installing and Configuring the Applications Required for Creating Renditions from Office Documents
3. Other products may need to be installed, to ensure that the output PDFs display all of the property
information that would normally display in the source documents.
How can you determine which additional CAD print engines you might need?
Open a particular DGN in MicroStation. If the graphics appear correct and the Items dialog (File > Item
Browser) shows the correct properties, then you can assume you do not need to install that DGN's
source design application on the Bentley i-model Composition Server for PDF computer, and you can
simply use MicroStation or Bentley View as the print engine.
What happens when the required additional CAD print engines are not
installed?
In this case, MicroStation or Bentley View will be used to publish renditions from DGNs and DWGs as
usual, but some of the renditions may not properly display all of the graphics or all of the property
information you are expecting.
Installing and Configuring the Applications Required for Creating

Renditions from Office Documents
To publish renditions from Microsoft Word 2007/2010 and Microsoft Excel 2007/2010 source
documents, Bentley i-model Composition Server for PDF requires that you have a PDF creator
application installed on the Bentley i-model Composition Server for PDF computer. The PDF creator
application will work in conjunction with the Word and Excel providers delivered with ProjectWise
InterPlot Organizer and a specified Windows postscript printer to publish the renditions. It is important
to note that the PDF creator application is required when publishing renditions from Microsoft Word
and Microsoft Excel documents, regardless of the output file type (PDF, JPEG, TIFF, and/or CALS) you
specified in the Output File Format rendition profile component.
Which PDF creator application should you install?

Ghostscript (32-bit version) works well with ProjectWise InterPlot Organizers Word and Excel
providers, and is the recommended choice for the PDF creator application.
You can download the latest release of Ghostscript from http://sourceforge.net/projects/ghostscript/.
What other requirements are necessary to publish renditions from Microsoft

Word and Microsoft Excel documents?
Besides having to install a Postscript to PDF converter such as Ghostscript, you should do the following:
Install the native Microsoft application (Microsoft Word/Excel) for each type of document you plan
to publish renditions for.
Create a Windows postscript printer and specify that printer on the ProjectWise InterPlot Organizer
Configure - Integrate dialog.
For prints up to 11 x 17, use the HP Color LaserJet 8500 PS printer driver. For prints larger than 11 x
17, use the HP DesignJet T7100ps PS3 printer driver.
Install the Word and Excel providers when installing ProjectWise InterPlot Organizer by selecting
the Specifications feature (the Specifications feature is installed by default).
ProjectWise
228

Installing and Configuring the Applications Required for Creating Renditions from Office Documents
To Configure the Word and Excel Providers with Ghostscript

Note: The ProjectWise InterPlot Organizer Configure dialog must be launched with elevated privileges
(Run as administrator).
1. Select Start > All Programs > Bentley > ProjectWise InterPlot Utilities > ProjectWise InterPlot
Organizer Configure.
The ProjectWise InterPlot Organizer Configure dialog opens.
2. Click Integrate.
The ProjectWise InterPlot Organizer Configure - Integrate dialog opens.
3. On the Office tab, turn off Use Specifications Provider.
4. Click Browse next to the PDF Creator Application field and navigate to the Ghostscript installation
folder.
5. Select gswin32c.exe or gswin32.exe, and then click Open.
6. (Optional) Type in any additional PDF creator application arguments.
7. Select a postscript printer from the list.
If you do not see a postscript printer in the list, you can exit the dialog and create one.
8. Click OK.
ProjectWise
229

Installing Bentley i-model Composition Server for PDF
A dialog opens stating that the product has been successfully integrated with your installed products.
9. Click OK.
10. Click Exit Configure.

The Bentley i-model Composition Server for PDF installer guides you through the installation and
general configuration of Bentley i-model Composition Server for PDF. When installation is complete, the
Configuration Wizard is immediately launched. Among other things, the Configuration Wizard is used to
specify the location of the working directory and to select which type of configuration to perform.
There are two configuration types to select from (Standard or Custom), but there are really three types
of configurations you can perform:
Standard Creates a Bentley i-model Composition Server for PDF orchestration instance and
automatically installs one of each dispatcher and processor on the computer.
Custom (with an orchestration instance) Creates an orchestration instance and gives you the
option to increase the default number of the dispatchers and processors that are installed on the
computer.
Custom (without an orchestration instance) Does not create an orchestration instance, but gives
you the option to select which dispatchers and/or processors to install on the computer, and how
many of the selected dispatchers and/or processors to install. This configuration type is used to
distribute the workload across multiple computers, and requires that you perform a Standard or
Custom configuration on another computer. In this case, you would use the same Orchestration
Framework database for each installation so that the orchestration instance will be aware of and
make use of any additional dispatchers and processors installed on extra computers.
Bentley i-model Composition Server Administrator is the main client interface for Bentley i-model
Composition Server for PDF, and is an option of the Bentley i-model Composition Server for PDF
installer. Typically you install this with the server, but you can install it on a separate computer for
remote administration if needed. Installing Bentley i-model Composition Server Administrator installs
Orchestration Framework Administrator with the Bentley i-model Composition Server Administrator
extension.
To install just Bentley i-model Composition Server Administrator, you run the same Bentley i-model
Composition Server for PDF installer and simply turn off the server and IIS components. Note that
Bentley i-model Composition Server Administrator does not require ProjectWise InterPlot Organizer or
ProjectWise Orchestration Framework Service, but it does require ProjectWise Explorer, and it does
require MSMQ (with HTTP Support) to be enabled and running. If Bentley i-model Composition Server
for PDF is on the domain, then the computer on which you install Bentley i-model Composition Server
Administrator must also be on the domain, you must be logged in to the computer with a domain
account, and the domain account used to open Bentley i-model Composition Server Administrator must
also be a member of the local administrators group.
Before You Install Bentley i-model Composition Server for PDF

2. Review the Configuration Checklist for Bentley i-model Composition Server for PDF.
ProjectWise
230

To Perform a Standard Installation of Bentley i-model Composition Server for

PDF
2. Click the Install button next to Bentley i-model Composition Server for PDF.
The following items can be installed through this installer:
IIS Web Service for Bentley i-model Composition Server for PDF (required for ProjectWise Explorer
jobs only)
Bentley i-model Composition Server Administrator (installs Orchestration Framework
Administrator with the Bentley i-model Composition Server Administrator extension; required to
configure batch rendition jobs only, not required for ProjectWise Explorer jobs)
5. (Optional) If you do not want to install one of the features, click the feature's icon and select X
This feature will not be available.
ProjectWise
231


If you selected to install the IIS Web Service for Bentley i-model Composition Server for PDF, then
the Select Website page opens with a list of IIS websites available on this computer.
If, for testing purposes, you have other Bentley applications installed that are already deployed to IIS
(such as ProjectWise Web Server or ProjectWise Publishing Server), then make sure you select a
different website to deploy this IIS Web Service to.
ProjectWise
232

7. Select a website to deploy the service to and click Next.

ProjectWise
233

Next, the Bentley i-model Composition Server for PDF Configuration Wizard opens.
The Configuration Wizard automatically finds the Orchestration Framework database instance you
created during the ProjectWise Orchestration Framework Service installation, and shows you which
version of the Bentley i-model Composition Server for PDF schema will be installed, in order to
configure the Orchestration Framework database for Bentley i-model Composition Server for PDF.
ProjectWise
234

10. Click Next.

The Datasource Configuration page opens.
ProjectWise
235

This page requires you to select a shared folder somewhere on the file system, which will serve as
the working directory for Bentley i-model Composition Server for PDF jobs. If you have not yet
created and shared a folder on the file system to be used as the working directory, do so now before
continuing.
11. If you know the name of the computer on which the shared working directory is located, you can
type the location using the UNC path to the folder name (\\computername\fileshare) or you
can click the Browse button to locate and select the working directory. When finished, click Next.
The User Credentials page opens. On this page you must specify the ProjectWise user whose working
directory ProjectWise InterPlot Organizer will use to copy out any managed workspace files.
Specifically, whenever a user runs a rendition job from ProjectWise Explorer, ProjectWise InterPlot
Organizer will use the ProjectWise working directory of the user specified here, for the purpose of
downloading managed workspace files. The user you specify here does not need to exist now, but it
must exist, of course, by the time you run a job in ProjectWise Explorer.
ProjectWise
236

12. Enter the user name and password of a ProjectWise account and click Next.
The next page that opens lets you specify email server information, so that the user can opt to
receive an email notification whenever a job is complete.
ProjectWise
237


If you do not plan to use email notifications with rendition jobs, or if you want to configure this
information later, you can skip this page and click Next.
or
If you do plan to use email notifications with rendition jobs and you have the information ready,
enter information about your email server. When finished, click Next.
The Configuration Type page opens with two options, Standard and Custom. The Standard option
installs all of the individual processors and dispatchers that make up Bentley i-model Composition
Server for PDF; the Custom option is only used when you want to install additional processors and/
or dispatchers on another computer, to share the workload of the main Bentley i-model Composition
Server for PDF instance.
ProjectWise
238

14. Select Standard and click Next.

15. When the DMS Connectors page opens, select the ProjectWise Connector and click Next to begin
configuration of Bentley i-model Composition Server for PDF.
As delivered, Bentley i-model Composition Server for PDF only delivers one connector the
ProjectWise Connector. This connector is selected by default, and is required to store the newly
created rendition documents in the same or other datasource.
ProjectWise
239

16. When the word Done appears over the progress bar on the Configuration In Progress page, click
Close.
ProjectWise
240

To Perform a Custom Installation of Bentley i-model Composition Server for

PDF, with an Orchestration Instance
1. Follow the steps in To Perform a Standard Installation of Bentley i-model Composition Server for PDF
until you get to the Configuration Type page.
ProjectWise
241

2. Select Custom and click Next.

The Orchestration Components page opens.
3. Turn on Create orchestration instance.
4. Leave all of the dispatchers selected.
5. To install more than one of a particular processor, increase the number next to the processor as
needed.
6. Leave the other processors set to 1.
7. Click Next.
ProjectWise
242

Close.
To Perform a Custom Installation of Bentley i-model Composition Server for

PDF, Without an Orchestration Instance
1. Follow the steps in To Perform a Standard Installation of Bentley i-model Composition Server for PDF
until you get to the Configuration Type page.
ProjectWise
243

2. Select Custom and click Next.

The Orchestration Components page opens.
3. Turn off Create orchestration instance.
4. Turn off any dispatcher you do not need to install on this computer.
5. To install more than one of a particular processor, increase the number next to the processor as
needed.
6. Set the number to 0 next to the ProjectWise Connector Processor; you do not need to install this
processor when you are not creating an orchestration instance.
7. Set the number to 0 next to any other processor you do not want to install on this computer.
8. Click Next.
Close.
Note: You can re-run the Configuration Wizard at any time to change any of the settings you just set, by
selecting Start > All Programs > Bentley > ProjectWise V8i (SELECTseries 4) > Bentley i-model
Composition Server for PDF > Bentley i-model Composition Server for PDF Configuration.
Note: If you create an orchestration instance during installation (either by Standard or Custom
configuration), and then on another computer perform a Custom configuration without creating an
orchestration instance, you will need to configure the orchestration instance on the main computer so
ProjectWise
244

Adding Bentley i-model Composition Server for PDF to the Trusted Servers List
that the additional processors and dispatchers are included in the instance. For details, see Configuring
Bentley i-model Composition Server for PDF Orchestration Instances in the Bentley i-model
Composition Server for PDF help.
Adding Bentley i-model Composition Server for PDF to the

Trusted Servers List
Before you can define and run Bentley i-model Composition Server for PDF jobs, you need to add the IP
address of the Bentley i-model Composition Server for PDF computer to the Trusted Servers list in the
ProjectWise Integration Server's dmskrnl.cfg file. If you install Bentley i-model Composition Server
Administrator on a different computer than Bentley i-model Composition Server for PDF, then you also
need to add the IP address of the Bentley i-model Composition Server Administrator computer to the
Trusted Servers list.
See Adding Servers to ProjectWise Integration Server's Trusted Servers List.
Adding the Location of the Bentley i-model Composition Server

for PDF IIS Web Service to dmskrnl.cfg
The [RenditionWebServices] section in the ProjectWise Integration Server's dmskrnl.cfg file is
used to specify the location of the Bentley i-model Composition Server for PDF IIS Web Service, in order
to route rendition requests submitted from ProjectWise Explorer users. You do not need to configure
this section to be able to create or run batch rendition jobs from Bentley i-model Composition Server
Administrator.
To Add the Location of the Bentley i-model Composition Server for PDF IIS
Web Service to dmskrnl.cfg
1. On the ProjectWise Integration Server computer, open the dmskrnl.cfg file.
2. Find the [RenditionWebServices] section.
3. Under that, add a new line to represent location of the IIS Web Service on the Bentley i-model
Composition Server for PDF computer.
For example:
[RenditionWebServices]
Bentley iCS for PDF web service=http://iCSforPDFcomputername/
RenditionService/RenditionService.svc
Setting Up the Default User

During Bentley i-model Composition Server for PDF installation, you specified the log in credentials of a
default ProjectWise user. This default user is used by ProjectWise InterPlot Organizer whenever a user
creates renditions from ProjectWise Explorer. Specifically, ProjectWise InterPlot Organizer uses the
default users working directory to copy out any managed workspace files and also any ancillary
InterPlot files, such as pen tables and color tables.
ProjectWise
245

Setting Up the Default User
You can change the default user at any time either by rerunning the Bentley i-model Composition Server
for PDF configuration wizard, or by changing the default user through Orchestration Framework
Administrator.
This same user is entered by default in the ProjectWise Datasource Selection dialog which opens when
you create a job in Bentley i-model Composition Server Administrator. At that point, you can either
leave the default user selected and log in to the selected datasource, or you can enter a different user
name and password and log in.
Perform the following procedure in each datasource you plan to use with Bentley i-model Composition
Server for PDF. The following procedure should also be performed to configure the user(s) who will
create and run jobs in Bentley i-model Composition Server Administrator, if you decide not to use the
default user for those jobs.
To Set Up the Default User, and Other Bentley i-model Composition Server
Administrator Users
1. Open ProjectWise Administrator, log in to your datasource, and select the Users datasource node.
Right-click the Users node and select New > User to create a new user if necessary.
or
Right-click an existing user and select Properties.
If you are setting up the default user, give this user the same user name and password as the user
you specified as the default user during Bentley i-model Composition Server for PDF installation.
or
If this user is not the default user, the user name and password can be different from the default user
you specified during Bentley i-model Composition Server for PDF installation.
4. On the Settings tab of the User Properties dialog, expand the Working Directory category.
5. Under the subcategory, When Using ProjectWise Explorer, enter the folder path of the folder you
want to set for this users working directory.
For any user (including the default user) who will create and run jobs in Bentley i-model
Composition Server Administrator, set that user's User Credential Expiration Policy to No
expiration.
or
If the default user is NOT going to be used to create and run jobs in Bentley i-model Composition
Server Administrator, and instead is only being used for renditions jobs submitted through
ProjectWise Explorer, then you do not need to set the default user's User Credential Expiration
Policy to No expiration.
To set a user's User Credential Expiration Policy to No expiration:
On the Settings tab of the User Properties dialog, expand the General category.
Double-click User Credential Expiration Policy. The default setting is Server default.
Double-click Server default. The User Credential Expiration Policy dialog opens.
ProjectWise
246

Configuring Users to Receive Email Notifications
Change Server default to No expiration and click OK.
7. For any user (including the default user) who will create and run jobs in Bentley i-model
Composition Server Administrator, turn OFF the user setting, Use Access Control (User Properties
dialog > Settings tab > General category > Use Access Control).
This ensures that the user account under which the job runs always has access to all of the source
documents in the input set.
Tip: This step is not needed for users creating renditions from ProjectWise Explorer.
8. Click OK to save the changes and close the User Properties dialog.
9. On the Bentley i-model Composition Server for PDF computer, create the default user's working
directory, and also the working directory for any user who will create and run jobs in Bentley imodel Composition Server Administrator.
You can do this by opening ProjectWise Explorer on the Bentley i-model Composition Server for PDF
computer, logging in to the datasource as the required user, and then creating the users working
directory when prompted.
Tip: Repeat step 9 for each default user in each datasource you plan to use with Bentley i-model
Composition Server for PDF. Make sure that each default user is using its own working directory, and
is not sharing the working directory of a default user of another datasource.
Configuring Users to Receive Email Notifications

For users to be able to receive an email notification when a rendition job is complete, the following must
be true:
1. During installation of Bentley i-model Composition Server for PDF, you can configure email server
information to be used by the email notification feature. If you do not configure this during
installation, you can rerun the Configuration Wizard any time after installation by selecting Start >
All Programs > Bentley > ProjectWise V8i (SELECTseries 4) > Bentley i-model Composition
Server for PDF > Bentley i-model Composition Server for PDF Configuration. You can also
configure this information in Bentley i-model Composition Server Administrator.
2. Any user who runs a rendition job and who wants to receive email notifications first must have a
valid email address specified in their ProjectWise user accounts properties. You can do this in
ProjectWise Administrator by logging into your datasource, selecting the Users node, and then
modifying the properties of the users who plan to create renditions from ProjectWise Explorer.
3. When configuring jobs in Bentley i-model Composition Server Administrator, or when configuring
rendition profiles in ProjectWise Administrator, turn on the option for the user running the job to
receive an email after a rendition job is complete.
4. When creating renditions from ProjectWise Explorer, turn on the option to receive an email after a
rendition job is complete.
Changing the Default ProjectWise InterPlot Organizer Printer

During installation, the Bentley i-model Composition Server for PDF configuration wizard adds the
default printer that ProjectWise InterPlot Organizer uses for creating renditions (ProjectWise InterPlot
Organizer already delivers the corresponding driver). This printer is named ProjectWise Dynamic
Composition Server and supports a wide variety of paper sizes. The ProjectWise InterPlot Organizer
configuration variable IP_DCS_RENDITION_PRINTER lets users change the default printer if necessary.
ProjectWise
247

Upgrading Job Schedules Created in 'ProjectWise Dynamic Composition Server for PDF'
Tip: If you remove the printer for any reason, rerunning the configuration wizard will add the printer
back again. Also, uninstalling Bentley i-model Composition Server for PDF will remove the printer.
To Change the ProjectWise InterPlot Organizer Printer

Note: The ProjectWise InterPlot Organizer Configure dialog must be launched with elevated privileges
(Run as administrator).
1. Select Start > All Programs > Bentley > ProjectWise InterPlot Utilities > ProjectWise InterPlot
Organizer Configure.
The ProjectWise InterPlot Organizer Configure dialog opens.
2. Click Configure.
The Edit Configuration dialog opens.
3. Under Data formats, select Common, then click Edit.
4.
5.
6.
7.
The Edit Common Configuration dialog opens.

Locate the IP_DCS_RENDITION_PRINTER configuration variable and change the printer.
Click OK on the Edit Common Configuration dialog.
Click Close on the Edit Configuration dialog.
Click Exit Configure.
Upgrading Job Schedules Created in 'ProjectWise Dynamic

Composition Server for PDF'
With the rebranding of 'ProjectWise Dynamic Composition Server for PDF' as 'Bentley i-model
Composition Server for PDF', various internal process names were changed as well. As a result, any
schedule you created for a 'ProjectWise Dynamic Composition Server for PDF' job in Orchestration
Framework Administrator will no longer display in the Job Scheduler window. (The job definitions
themselves will still display in the Bentley iCS for PDF Browser and can still be run manually.)
To upgrade these job schedules:
1.
2.
3.
4.
5.
6.
Open the Windows Task Scheduler (%windir%\system32\taskschd.msc).

Open the Task Properties dialog for each job schedule (task).
Select the Actions tab and click the Edit button.
In the argument field, change ProjectWise DCS to Bentley iCS.
Click OK to close the Task Properties dialog.
Click OK to close the Windows Task Scheduler.
If you have a significant number of job schedules to update, contact Bentley technical support for
assistance.
ProjectWise
248
ProjectWise Automation Service Configuration
11
Automation Service Overview

ProjectWise Automation Service runs on top of ProjectWise Orchestration Framework Service and uses
different extensions to automate various processes:
Bentley i-model Composition Server for i-model This delivered extension is used to publish imodels (and optionally create packaged i-models) from existing documents in your datasource, and
then store the newly created i-models in the same datasource. Bentley i-model Composition Server
for i-model leverages Bentley i-model Composer to publish i-models. This extension requires a
Bentley i-model Composition Server license.
DGN Indexing This delivered extension is used to create an index in the datasource of componentlevel information extracted from standard 2D and 3D DGN or DWG documents in the datasource.
This extension does not require a license.
ProjectWise PDx Dynamic Review Service This extension (originally delivered with ProjectWise,
but now available as a separate download) is used to publish i-models from files in a PDS project
database. You can also use it to convert the source PDS files into V8 DGN files, or create a single
packaged i-model from the entire project. All new files generated are automatically stored in
ProjectWise as part of the process. ProjectWise PDx Dynamic Review Service uses ProjectWise PDx
Project Server to access the PDS project database, and uses MicroStation as the engine to publish imodels and convert PDS files to V8 DGN files. ProjectWise PDx Project Server requires a license.
ProjectWise Automation Service has a set of basic requirements, however you should note that some of
the requirements will vary, depending on the specific extension you plan to install. For that reason, each
of the following sections provides a checklist of things you need, based on the specific extension you
plan to install, with links to installation procedures where applicable.
Note: This ProjectWise V8i (SELECTseries 4) Refresh does not support the latest version of ProjectWise
PDx Dynamic Review Service (which is intended for the base V8i (SELECTseries 4) release), but rather
will support the future version of ProjectWise PDx Dynamic Review Service which is being rebranded as
Bentley i-model Composition Service for PDS
Configuration Checklist for the Bentley i-model Composition

Server for i-model Extension
The following is a checklist for setting up ProjectWise Automation Service with the Bentley i-model
Composition Server for i-model extension on a single computer. This also assumes ProjectWise
Integration Server is already installed on another computer, and a datasource is already configured.
Note: Bentley i-model Composition Server for i-model requires a Bentley i-model Composition Server
license.
ProjectWise
249

Configuration Checklist for the Bentley i-model Composition Server for i-model Extension
account:

expires.
and all ProjectWise Automation Service software.
See Before You Install ProjectWise Orchestration Framework Service for details. MSMQ must be
enabled on the ProjectWise Automation Service computer, as well as each computer on which
ProjectWise Automation Service software will be installed. For example, if you install ProjectWise
Automation Service Administrator on another computer, you must enable MSMQ on that computer
as well.
7. Make sure Microsoft .NET Framework 3.5 SP1 is installed (delivered with ProjectWise Server Setups
if necessary).
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
ProjectWise
Set up the ProjectWise Automation Service working directory.
Install ProjectWise Administrator V8i (SELECTseries 4).
Install ProjectWise Explorer V8i (SELECTseries 4) (before Bentley i-model Composer) if you plan to
run Bentley i-model Composition Server for i-model jobs that access data from AutoPLANT models.
Install Bentley i-model Composer V8i (SELECTseries 4).
Install ProjectWise Automation Service V8i (SELECTseries 4), with the Bentley i-model Composition
Server for i-model extension enabled.
Configure licensing for Bentley i-model Composition Server for i-model.
Install ProjectWise Automation Service Administrator V8i (SELECTseries 4).
Add the ProjectWise Automation Service computer to the Trusted Servers list.
Set up a user in the datasource with non-expiring credentials.
250

Configuration Checklist for the DGN Indexing Extension
Configuration Checklist for the DGN Indexing Extension

The following is a checklist for setting up ProjectWise Automation Service with DGN Indexing on a
single computer. This also assumes ProjectWise Integration Server is already installed on another
computer, and a datasource is already configured.
Note: The DGN Indexing extension to ProjectWise Automation Service does not require a license.
account:

expires.
See Before You Install ProjectWise Orchestration Framework Service for details. MSMQ must be
enabled on the ProjectWise Automation Service computer, as well as each computer on which
ProjectWise Automation Service software will be installed. For example, if you install ProjectWise
Automation Service Administrator on another computer, you must enable MSMQ on that computer
as well.
7. Make sure Microsoft .NET Framework 3.5 SP1 is installed (delivered with ProjectWise Server Setups
if necessary).
9. Install MicroStation.
For the DGN Indexing extension, the version of MicroStation can be:
MicroStation V8i (SELECTseries 3) (08.11.09.xx)
MicroStation V8i (SELECTseries 2) (08.11.07.4xx)
MicroStation V8i (SELECTseries 1) (08.11.07.1xx)
ProjectWise
251

Setting Up the Automation Service Working Directory
10.
11.
12.
13.
Set up the ProjectWise Automation Service working directory.

Install ProjectWise Administrator V8i (SELECTseries 4).
Install ProjectWise Automation Service V8i (SELECTseries 4), with the DGN Indexing extension
enabled.
14. Install ProjectWise Automation Service Administrator V8i (SELECTseries 4).
15. Add the ProjectWise Automation Service computer to the Trusted Servers list.
16. Set up a user in the datasource with non-expiring credentials.
Setting Up the Automation Service Working Directory

ProjectWise Automation Service needs a shared working directory so it can copy out the files it has been
told to process. Before installing ProjectWise Automation Service, you need to set up this working
directory by:
creating and sharing a folder (for example, C:\pwasjob_workingdir)
ProjectWise Automation Service needs full control, as well as each user who will be creating,
modifying, and running ProjectWise Automation Service jobs.
The working directory is recommended to be set up on the same computer as ProjectWise Automation
Service. Make a note of the path to the working directory, as you will be prompted to specify the location
of this folder during ProjectWise Automation Service installation.
a copy of all files selected for a job
system files, such as installed connectors and extensions
Tip: As you run jobs, the working directory will continue to grow in size. You can periodically clean out
the working directory using Orchestration Framework Administrator. It is recommended that you never
Installing ProjectWise Automation Service

The ProjectWise Automation Service installer guides you through the installation and general
configuration of ProjectWise Automation Service. Typically you will perform a standard installation,
which installs all the ProjectWise Automation Service components on one computer, with the
ProjectWise Automation Service orchestration instance already configured. If you have already installed
ProjectWise Automation Service on one computer, you may decide to perform a custom installation on
another computer to install only certain ProjectWise Automation Service components (in order to share
the workload, if necessary).
ProjectWise Automation Service Administrator is the main client interface for ProjectWise Automation
Service. Typically you install ProjectWise Automation Service Administrator on the same computer as
ProjectWise Automation Service, but you can install it on another computer if necessary. When
ProjectWise
252

installing both on the same computer, install ProjectWise Automation Service first, then ProjectWise
Automation Service Administrator.
Caution: For performance reasons it is recommended that you DO NOT install ProjectWise Automation
Service on the same computer as the ProjectWise Integration Server.
Note: You can re-run the Configuration Wizard any time after installation if you need to change any of
the settings you just set, by selecting Start > All Programs > Bentley > ProjectWise V8i
(SELECTseries 4) > Automation Service > Automation Service Configuration. For example, if you
later install an extension product on top of this ProjectWise Automation Service installation, you would
need to the Configuration Wizard again in order to incorporate the new extension.
Note: If you perform a complete installation on one computer, and then on another computer perform a
custom installation also to the same Orchestration Framework database, you will need to configure the
overall orchestration instance so that all processors and dispatchers are being used. For details, see
Configuring Automation Service Orchestration Instances in the ProjectWise Automation Service help.
Before You Install ProjectWise Automation Service

2. If you plan to install the Bentley i-model Composition Server for i-model extension, review the
Configuration Checklist for the Bentley i-model Composition Server for i-model Extension.
3. If you plan to install the DGN Indexing extension, review the Configuration Checklist for the DGN
Indexing Extension.
4. If installing on Windows Server 2008 or later, and you plan to use the Product Activation Wizard as
To Install ProjectWise Automation Service (Standard Installation)

2. Click Install next to ProjectWise Automation Service.
ProjectWise
253

The Custom Setup page opens, showing the location to which the product will be installed.
5. On the Custom Setup page, click Next.
ProjectWise
254

ProjectWise
255

Next, the Automation Service Configuration Wizard opens.

version of the ProjectWise Automation Service schema will be installed, in order to configure the
Orchestration Framework database for ProjectWise Automation Service.
ProjectWise
256

8. Click Next.
The Automation Service file share page opens.
ProjectWise
257

the working directory for ProjectWise Automation Service jobs. If you have not yet created and
shared a folder on the file system to be used as the ProjectWise Automation Service working
directory, do so now before continuing.
can click the Browse button to locate and select the ProjectWise Automation Service working
directory. When finished, click Next.
The next page that opens lets you enable the ProjectWise Automation Service extension(s) you want
to install.
DGN Indexing
Bentley i-model Composition Server for i-model (formerly Dynamic Composition Server for imodel)
Bentley i-model Composition Service for PDS
ProjectWise
258

10. Select the extension(s) you plan to use and click Next.
The Automation Service Configuration Type page opens with two options, Standard and Custom.
The Standard option installs all of the individual processors and dispatchers that make up
ProjectWise Automation Service; the Custom option is only used when you want to install additional
processors and/or dispatchers on another computer.
ProjectWise
259


12. When the word Done appears over the progress bar on the Automation Service Configuration In
Progress page, click Next.
ProjectWise
260

The Automation Service Configuration Completed page opens. If you selected to install the Bentley imodel Composition Server for i-model extension, the Launch License Management Tool option
displays, and is enabled. If you did not select to install the Bentley i-model Composition Server for imodel extension, you will not see the Launch License Management Tool option, as the other
extensions do not require a license.
13. On the Automation Service Configuration Completed page, click Close.
ProjectWise
261

14. If the Launch License Management Tool option was available and enabled on the previous page,
then the Product Activation Wizard opens for you to configure licensing for the Bentley i-model
Composition Server for i-model extension.
15. On this or another computer, install ProjectWise Automation Service Administrator.
To Install Individual ProjectWise Automation Service Processors and

Dispatchers (Custom Installation)
1. Follow steps 1 through 10 of the procedure, To Install ProjectWise Automation Service (Standard
installation).
2. When the Automation Service Configuration Type page opens, select Custom and click Next.
ProjectWise
262

3. When the Automation Service Orchestration Components page opens, turn on the individual
processors and/or dispatchers you want to install on this computer, then click Next.
ProjectWise
263

Installing ProjectWise Automation Service Administrator
4. When the word Done appears over the progress bar on the Automation Service Configuration In
Progress page, click Next.
The Automation Service Configuration Completed page opens. If you selected to install the Bentley imodel Composition Server for i-model extension, the Launch License Management Tool option
displays, and is enabled. If you did not select to install the Bentley i-model Composition Server for imodel extension, you will not see the Launch License Management Tool option, as the other
extensions do not require a license.
5. On the Automation Service Configuration Completed page, click Close.
6. If the Launch License Management Tool option was available and enabled on the previous page,
then the Product Activation Wizard opens for you to configure licensing for the Bentley i-model
Composition Server for i-model extension.
7. On this or another computer, install ProjectWise Automation Service Administrator.

ProjectWise Automation Service Administrator is the interface through which ProjectWise Automation
Service jobs are created and scheduled to be run. Typically, you install ProjectWise Automation Service
Administrator on the same computer as ProjectWise Automation Service, but you can install it on
another computer if necessary.
Tip: If ProjectWise Automation Service is already installed, skip the procedure below and go straight to
the procedure, To Install ProjectWise Automation Service Administrator.
ProjectWise
264

Before You Install ProjectWise Automation Service Administrator on Its Own

Computer
5. Install ProjectWise Administrator.
6. Add this computer to the Trusted Servers list.
version is not already installed.
To Install ProjectWise Automation Service Administrator

If ProjectWise Automation Service is already installed on this computer, then continue with step 2.
or
If ProjectWise Automation Service is not installed on this computer, then you need to first install or
configure prerequisites as necessary. See Before You Install ProjectWise Automation Service
Administrator for details, then return to this procedure and continue with step 2.
3. Click Install next to ProjectWise Automation Service Administrator.
ProjectWise
265

ProjectWise
266

Adding ProjectWise Automation Service to the Trusted Servers List
You can now use ProjectWise Automation Service Administrator to configure and run ProjectWise
Automation Service jobs. To get started, select Start > All Programs > Bentley > ProjectWise V8i
(SELECTseries 4) > Automation Service > Automation Service Administrator.
Adding ProjectWise Automation Service to the Trusted Servers

List
Before you can define and run ProjectWise Automation Service jobs, you need to add the IP address of
the ProjectWise Automation Service computer to the Trusted Servers list in the ProjectWise Integration
Server's dmskrnl.cfg file. If you install ProjectWise Automation Service Administrator on a different
computer than ProjectWise Automation Service, then you also need to add the IP address of the
ProjectWise Automation Service Administrator computer to the Trusted Servers list.
Setting Up the ProjectWise User(s) Who Will Run Automation

Service Jobs
The ProjectWise user account you log in with to create your job in ProjectWise Automation Service
Administrator must have the user setting, User Credential Expiration Policy, set to No Expiration.
ProjectWise
267

Uninstalling ProjectWise Automation Service
Also, it is recommended that this user has the user setting, Use Access Control, turned off. This gives
the user full access to every document and folder in the datasource, so that all documents and folders
specified in the job can be accessed when the job is run.
To Set Up a User to Run Jobs in Orchestration Framework Administrator

1. Open ProjectWise Administrator, log in to your datasource, and select the Users datasource node.
2. (Optional) Create a new user who will only be used to run jobs in Orchestration Framework
Administrator.
3. Right-click the user(s) to be used for Orchestration Framework Administrator jobs and select
Properties.
4. On the Settings tab of the User Properties dialog, expand the General category.
5. Double-click User credential expiration policy.
The default value is Server default.
6. Double-click Server default.
The User credential expiration policy dialog opens.
7. Change the value to No expiration and click OK.
8. Back on the Settings tab of the User Properties dialog, turn off Use Access Control (also under the
General category).
9. Click OK to save the changes and close the User Properties dialog.
Uninstalling ProjectWise Automation Service

When uninstalling ProjectWise Automation Service modules, make sure you uninstall them in the
reverse order that you installed them on that computer. For example, if everything is installed on one
computer, go to Control Panel > Programs and Features and uninstall the software in this order:
1. First uninstall ProjectWise Automation Service Administrator.
2. Then uninstall ProjectWise Automation Service.
3. Then uninstall ProjectWise Orchestration Framework Service.
After all ProjectWise Automation Service installations that share the same working directory have been
uninstalled, you can remove the following items left behind:
Delete the contents of your Automation Service working directory (so that it is still reusable)
Go to the folder
C:\Program Files\Common Files\Bentley Shared\OrchestrationFramework
\extlocal and delete the file UstationBootStrapForPASExtension.dll
Go to the folder
\extremote and delete the Automation Service working directory in that folder. For example,
\extremote\servername\pas_workdir
ProjectWise
268
ProjectWise Distribution Service Configuration
12
Distribution Service Overview

ProjectWise Distribution Service runs on top of ProjectWise Orchestration Framework Service and can
be used to automate:
the copying of source files from one folder to another in the same datasource
the copying of source files from one datasource to another
the creation of archive renditions (including PDFs)
the creation of DPR renditions
When creating renditions, ProjectWise Distribution Service works in conjunction with MicroStation,
ProjectWise InterPlot Organizer, and ProjectWise InterPlot Server to create renditions of CAD drawings.
Once created, the renditions are stored in the designated target folder in the same datasource, in
another datasource, or to another document management system.
As delivered, ProjectWise Distribution Service lets you distribute documents to a folder in the same
datasource, or to another datasource altogether. Through custom connectors you can distribute to the
document management system of your choice. Contact Bentley Professional Services for more
information about currently available connectors.
Configuration Checklist for ProjectWise Distribution Service

The following is a checklist of all the things you need to do, in order to set up ProjectWise Distribution
Service on a single computer. Note that this assumes ProjectWise Integration Server is already installed
and a datasource is already configured on another computer.
Caution: For performance reasons it is recommended that you DO NOT install ProjectWise Distribution
Service on the same computer as ProjectWise Integration Server.
Caution: Do not attempt to install ProjectWise Distribution Service and Bentley i-model Composition
Server for PDF on the same computer. This configuration is not supported.
account:
ProjectWise
269

Configuration Checklist for ProjectWise Distribution Service
expires.
and all ProjectWise Distribution Service software.
See Before you install ProjectWise Orchestration Framework Service for details about enabling MSMQ.
Note that MSMQ must be enabled on each computer that is part of the overall ProjectWise
Distribution Service network. For example, if you install ProjectWise Distribution Service
Administrator on another computer, you must enable MSMQ on that computer as well.
8. Install Internet Information Server (IIS).
On Windows Server 2008, IIS is installed and configured by opening Server Manager and installing
the Web Server (IIS) role.
On Windows Server 2003, IIS is installed by turning on the option for it in the Windows Component
Wizard, which opens when you click the Add/Remove Windows Components button in the Add/
Remove Programs dialog (Start > Control Panel > Add/Remove Programs).
9. If you plan to run jobs that create archive renditions and/or DPR renditions, then on the ProjectWise
Distribution Service computer you need to install the following:
10.
11.
12.
13.
14.
15.
16.
17.
18.
ProjectWise

ProjectWise InterPlot Organizer V8i (SELECTseries 4)
If you plan to run jobs that create archive renditions, you will also need to set up a ProjectWise
InterPlot Server, but this does not need to be installed on the ProjectWise Distribution Service
computer. See Setting Up ProjectWise InterPlot Server for ProjectWise Distribution Service for
information about setting up a printer, identify the launching user, and setting up a ProjectWise
InterPlot Server archive.
MicroStation, ProjectWise InterPlot Organizer and ProjectWise InterPlot Server are not needed to
run jobs that do not create renditions, and simply copy source files from one folder to another, or to
another datasource.
Set up the ProjectWise Distribution Service working directory.
Install ProjectWise Orchestration Framework Service V8i (SELECTseries 4). During installation, you
may be prompted to install .NET Framework 3.5 SP1, if the required version is not already installed.
Install ProjectWise Explorer V8i (SELECTseries 4).
Install ProjectWise Distribution Service V8i (SELECTseries 4).
Install ProjectWise Distribution Service Administrator V8i (SELECTseries 4).
If ProjectWise InterPlot Server is installed, then also install ProjectWise Distribution Service Plug-in
for ProjectWise InterPlot Server. This must be installed on the same computer as ProjectWise
InterPlot Server.
Add the ProjectWise Distribution Service computer to the Trusted Servers list.
270

Configuration Checklist for ProjectWise InterPlot Server
19. Create a special user account in the datasource, where the user has non-expiring credentials.
20. Make sure that the computer on which the target document management system server is located
has adequate disk space for distributed renditions and source documents. You should estimate about
the same amount of free disk space that you set aside for the ProjectWise Distribution Service
working directory.
Configuration Checklist for ProjectWise InterPlot Server

ProjectWise InterPlot Server is required by ProjectWise Distribution Service if you plan to run jobs that
create archive renditions. Your ProjectWise InterPlot Server can be but does not need to be installed on
the ProjectWise Distribution Service computer.
The following is a checklist of all the things you need to do, in order to set up ProjectWise InterPlot
Server for use with ProjectWise Distribution Service, assuming that you are installing ProjectWise
InterPlot Server on a different computer than ProjectWise Distribution Service.
3.
4.
5.
6.
Install ProjectWise InterPlot Server.
See Setting Up ProjectWise InterPlot Server for ProjectWise Distribution Service for information about
setting up a printer, identify the launching user, and setting up a ProjectWise InterPlot Server
archive.
Install ProjectWise Distribution Service Plug-in for ProjectWise InterPlot Server.
Add the ProjectWise InterPlot Server computer to the Trusted Servers list.
Setting Up ProjectWise InterPlot Server for ProjectWise

Distribution Service
If you plan to use ProjectWise Distribution Service for renditioning, you must have a printer and a
ProjectWise InterPlot Server archive set up on the computer on which ProjectWise InterPlot Server is
installed. This archive should be a separate digital archive that will be used only for ProjectWise
Distribution Service. Use a different file and web storage folder from your normal digital archives
(dsweb, dsfile). When sharing these new folders, make sure you change share permissions to Everyone
with Full Control, also make sure (on the Security tab) to add Everyone with Full Control permissions
for each of these folders. When creating the filestore, use the administrator or special ProjectWise
Distribution Service user account with password.
You will also need to configure the identity of the launching user.
Note: While ProjectWise InterPlot Server supports the use of Microsoft Access databases, when used
with ProjectWise Distribution Service, ProjectWise InterPlot Server must use a SQL Server database.
Also the ProjectWise InterPlot Server archive must be created using the Enterprise option instead of the
Workgroup option.
Make a note of the computer name on which this printer is installed, and also the name of the
ProjectWise InterPlot Server archive, as you will be prompted for this information during the
ProjectWise Distribution Service installation.
ProjectWise
271

Setting Up the Distribution Service Working Directory
If you are installing the ProjectWise Distribution Service on a different computer than where
ProjectWise InterPlot Server is installed, make sure you add the ProjectWise InterPlot Server printer
(Windows Control Panel > Printers > Add Printer) to the list of available printers for the ProjectWise
Distribution Service computer.
If any of your distribution jobs will be generating hard copy output, when setting up your ProjectWise
InterPlot Server printer, make sure you use a port that is connected to a physical printer.
If you do not intend to generate hard copy output, you should set up a NUL port for your ProjectWise
InterPlot Server printer. A NUL port is a virtual port that can be used for testing purposes, since it is not
a real device. Depending on your version of Windows, the NUL port may not be in the default list of
available ports for a printer, but can be easily added using the following procedure. Once added, the NUL
port will be available for all printers attached to the Windows print server.
To Configure the Identity of the Launching User

1. Log on as administrator, open a command prompt, and enter: dcomcnfg
2. In the Component Services window that opens, expand Console Root > Component Services >
Computers > My Computer > DCOM Config.
3. Under DCOM Config, find DPRArchServ. Right-click DPRArchServ and select Properties. In the
Properties dialog, on the Identity tab, select This user and enter the admin user created earlier
(distuser or administrator).
4. Under DCOM Config, find ProjectWise InterPlot Organizer Documents. Right-click ProjectWise
InterPlot Organizer Documents and select Properties. In the Properties dialog, on the Identify
tab, select The launching user.
To Create a NUL Printer Port

1. Open the Control Panel and double-click Printers.
2. In the Printers folder, select File > Server Properties.
The Print Server Properties dialog opens.
3. On the Ports tab click Add Port.
The Printer Ports dialog opens.
4. From the Available port types list, select Local Port, then click New Port.
5. Type NUL as the port name and click OK.
6. Close the Printer Ports dialog, then close the Print Server Properties dialog.
The NUL port is now listed in the Ports tab of the Properties dialog of all the printers installed on this
computer.
Setting Up the Distribution Service Working Directory

ProjectWise Distribution Service needs a shared working directory so it can copy out the files it has
been told to process. Before installing ProjectWise Distribution Service, you need to set up this working
directory by:
creating and sharing a folder (for example, C:\pwdsjob_workingdir)
ProjectWise
272

Installing ProjectWise Distribution Service
ProjectWise Distribution Service needs full control, as well as each user who will be creating,
modifying, and running distribution jobs.
The working directory is recommended to be set up on the same computer as ProjectWise Distribution
Service. Make a note of the path to the working directory, as you will be prompted to specify the location
of this folder during ProjectWise Distribution Service installation.
a copy of all files selected for a job along with all of their reference files
any renditions created by the job
job history
system files, such as installed connectors, installed extensions, and logging files
Tip: As you run jobs, the working directory will continue to grow in size. You can periodically clean out
the working directory using Orchestration Framework Administrator. It is recommended that you never

The ProjectWise Distribution Service installer guides you through the installation and general
configuration of ProjectWise Distribution Service. Typically you will perform a standard installation,
which installs all the ProjectWise Distribution Service components on one computer, with a ProjectWise
Distribution Service orchestration instance already configured. If you have already installed ProjectWise
Distribution Service on one computer, you may decide to perform a custom installation on another
computer to install only certain components (in order to share the workload, if necessary).
ProjectWise Distribution Service Administrator is the main client interface for ProjectWise Distribution
Service. Typically you install ProjectWise Distribution Service Administrator on the same computer as
ProjectWise Distribution Service, but you can install it on another computer if necessary. When
installing both on the same computer, install ProjectWise Distribution Service first, then ProjectWise
Distribution Service Administrator.
Before You Install ProjectWise Distribution Service

2. Review the Configuration Checklist for Distribution Service.
To Install ProjectWise Distribution Service (Standard Installation)

2. Click Install next to ProjectWise Distribution Service.
ProjectWise
273

The following items can be installed through the ProjectWise Distribution Service installer:
Distribution Service (cannot be disabled)
IIS Web Service for InterPlot Organizer
5. (Optional) If you do not want to install the IIS Web Service for InterPlot Organizer, click the
feature's icon and select X - This feature will not be available.
ProjectWise
274


ProjectWise
275

Next, the Distribution Service Configuration Wizard opens.

version of the ProjectWise Distribution Service schema will be installed, in order to configure the
Orchestration Framework database for ProjectWise Distribution Service.
ProjectWise
276

9. Click Next.
The Distribution Service Datasource Configuration page opens.
ProjectWise
277

the working directory for ProjectWise Distribution Service jobs. If you have not yet created and
shared a folder on the file system to be used as the ProjectWise Distribution Service working
directory, do so now before continuing.
can click the Browse button to locate and select the ProjectWise Distribution Service working
directory. When finished, click Next.
The Distribution Service Datasource Configuration page opens.
ProjectWise
278

11. In the Archive Groups field, type a name for the ProjectWise InterPlot Server archive group that will
be used for generating renditions.
You can name the Archive Group anything you want.
12. In the Printer field, type the name of the ProjectWise InterPlot Server printer you intend to use,
using the format:
\\PWIPS_computername\PWIPS_printername
13. In the Archive Name field, type the name of a valid ProjectWise InterPlot Server archive.
Click Add, then click Next.
or
Click Add, repeat the steps to define additional archive groups, then click Next.
The Distribution Service Configuration Type page opens with two options, Standard and Custom.
The Standard option installs all of the individual processors and dispatchers that make up
ProjectWise Distribution Service; the Custom option is only used when you want to install additional
processors and/or dispatchers on another computer.
ProjectWise
279


16. When the Distribution Service DMS Connectors page opens, select connectors that you expect to use
and click Next to begin configuration of ProjectWise Distribution Service.
In a default installation, with no custom connectors installed, there will be only one option the
ProjectWise Connector. This connector is required to distribute documents to another folder in the
same datasource, or to another ProjectWise datasource altogether.
ProjectWise
280

17. When the word Done appears over the progress bar on the Distribution Service Configuration In
Progress page, click Close.
ProjectWise
281

18. On this or another computer, install ProjectWise Distribution Service Administrator.

Note: You can re-run the Configuration Wizard any time after installation to change any of the settings
you just set, by selecting Start > All Programs > Bentley > ProjectWise V8i (SELECTseries 4) >
Distribution Service > Distribution Service Configuration.
To Install ProjectWise Distribution Service (Custom Installation)

1. Follow steps 1 through 14 of the procedure, To Install ProjectWise Distribution Service (Standard
installation).
2. When the Distribution Service Configuration Type page opens, select Custom and click Next.
ProjectWise
282

3. When the Distribution Service Orchestration Components page opens, turn on the processors and/or
dispatchers you want to install on this computer, then click Next.
ProjectWise
283

Installing ProjectWise Distribution Service Administrator
4. When the word Done appears over the progress bar on the Distribution Service Configuration In
Progress page, click Close.
5. On this or another computer, install ProjectWise Distribution Service Administrator.
Note: If you perform a complete installation on one computer, and then on another computer perform a
custom installation also to the same Orchestration Framework database, you will need to configure the
overall orchestration instance so that all processors and dispatchers are being used. For details, see
Configuring Distribution Service Orchestration Instances in the ProjectWise Distribution Service help.

ProjectWise Distribution Service Administrator is the interface through which Distribution Service jobs
are created and scheduled to be run. Typically, you install ProjectWise Distribution Service
Administrator on the same computer as ProjectWise Distribution Service, but you can install it on
another computer if necessary.
Tip: If ProjectWise Distribution Service is already installed, skip the 'Before You Install' procedure
below and go straight to the procedure, To Install ProjectWise Distribution Service Administrator.
ProjectWise
284

Before You Install ProjectWise Distribution Service Administrator on Its Own

Computer
and all ProjectWise Distribution Service software.
5. Install ProjectWise Explorer.
6. Add this computer to the Trusted Servers list.
version is already installed.
To Install ProjectWise Distribution Service Administrator

If ProjectWise Distribution Service is already installed, continue with step 2.
or
If you are installing ProjectWise Distribution Service Administrator on a separate computer, install
prerequisites as necessary. See Before You Install ProjectWise Distribution Service Administrator for
details.
3. Click Install next to ProjectWise Distribution Service Administrator.
ProjectWise
285

ProjectWise
286

Installing ProjectWise Distribution Service Plug-in for ProjectWise InterPlot Server
You can now use ProjectWise Distribution Service Administrator to configure and run ProjectWise
Distribution Service jobs. To get started, select Start > All Programs > Bentley > ProjectWise V8i
(SELECTseries 4) > Distribution Service > Distribution Service Administrator.
Installing ProjectWise Distribution Service Plug-in for ProjectWise

InterPlot Server
The following procedure assumes that you have already installed and configured ProjectWise InterPlot
Server, which includes setting up a printer and a ProjectWise InterPlot Server archive on the computer
on which you are about to install ProjectWise Distribution Service Plug-in for ProjectWise InterPlot
Server. If that is not the case, install and configure ProjectWise InterPlot Server now before continuing.
Note: Make sure this computer is on a domain.
To Install ProjectWise Distribution Service Plug-in for ProjectWise InterPlot

Server
2. Click the Install button next to ProjectWise Distribution Service Plug-in for ProjectWise InterPlot
Server.
3. When the ProjectWise Distribution Service Plug-in Setup Wizard opens, click Next.
ProjectWise
287

Adding ProjectWise Distribution Service to the Trusted Servers List
5. When the Start Copying Files page opens, click Next to install the plug-in.
When the files have been installed, the Select Archives page opens.
6. Select an ProjectWise InterPlot Server archive from the Available Archives list, and click the Add ()
button to add it to the Configured Archives list. Repeat this step for all of the available archives you
want to configure.
7. Click Next.
Adding ProjectWise Distribution Service to the Trusted Servers

List
Before you can define and run ProjectWise Distribution Service jobs, you need to add the IP address of
the ProjectWise Distribution Service computer to the Trusted Servers list in the ProjectWise Integration
Server's dmskrnl.cfg file. If you install ProjectWise InterPlot Server or ProjectWise Distribution
Service Administrator on a different computer than ProjectWise Distribution Service, then you also need
to add the IP address of those computers to the Trusted Servers list.
ProjectWise
288

Setting Up the ProjectWise User(s) Who Will Run Distribution Service Jobs
Setting Up the ProjectWise User(s) Who Will Run Distribution

Service Jobs
To create a job in Distribution Service Administrator, you first log in to the datasource containing the
documents you process. You can log in with any account in the datasource, just make sure that the user
you log in with has their ProjectWise user setting, User Credential Expiration Policy, set to No
Expiration. Note that when selecting a destination folder in another datasource, the user you use to log
in to the destination datasource must also have their ProjectWise user setting, User Credential
Expiration Policy, set to No Expiration.
It is also recommended that for this user, you turn off the ProjectWise user setting, Use Access Control.
When off, the user will be able to add any document, folder, or project in the datasource to the input set.
If this setting were to be on (which is otherwise recommended for regular ProjectWise users), the user
might not have access to some documents they need to process.
Uninstalling ProjectWise Distribution Service

When uninstalling ProjectWise Distribution Service modules, make sure you uninstall them in the
reverse order that you installed them on that computer. For example, if everything is installed on one
computer, open Add / Remove Programs from the Control Panel and uninstall the software in this
order:
1.
2.
3.
4.
First uninstall ProjectWise Distribution Service Plug-in for ProjectWise InterPlot Server.
Then uninstall ProjectWise Distribution Service Administrator.
Then uninstall ProjectWise Distribution Service.
Then uninstall ProjectWise Orchestration Framework Service.
After all ProjectWise Distribution Service installations that share the same working directory have been
uninstalled, you can remove the following items left behind after uninstallation:
Delete the contents of your Distribution Service working directory (so that it is still reusable)
Delete the folder
C:\Program Files\Common Files\Bentley Shared\DistributionService
Go to the folder
\extremote and delete the Distribution Service working directory in that folder. For example,
\extremote\servername\pds_workdir
ProjectWise
289

Uninstalling ProjectWise Distribution Service
ProjectWise
290
ProjectWise web services Configuration
13
Installing and Deploying ProjectWise web services

ProjectWise web services is the server that provides ProjectWise Explorer Mobile users with a list of
ProjectWise datasources they can connect to.
The ProjectWise web services installation package can be downloaded from Bentleys SELECT
downloads website.
ProjectWise web services is supported with ProjectWise V8i (SELECTseries 4) and ProjectWise V8i
(SELECTseries 3).
Caution: No license is required for ProjectWise web services, however a ProjectWise Passport license is
required for each ProjectWise Explorer Mobile user connecting to ProjectWise web services.
Tip: You can rerun the deployment wizard if you need to deploy to another website, or if you need to
undeploy ProjectWise web services from a particular website. Rerun the deployment wizard as needed
by selecting Start > All Programs > Bentley > ProjectWise Web Services > ProjectWise Web
Services Deployment Wizard.
Tip: ProjectWise web services writes to a log file at the following location:
C:\Users\Public\Bentley\Logs\pwmobileaccess.log
Before You Install and Deploy ProjectWise web services

2. Be an administrator of the computer.
3. ProjectWise web services can also be installed on the same computer as ProjectWise Web Server,
however it is recommended that you do not deploy them to the same IIS website.
4. The IIS role services required for ProjectWise Web Server are different than those required for
ProjectWise web services. If you have already installed the Web Server (IIS) role and role services
required for ProjectWise Web Server, you can leave those role services on; they do not interfere with
ProjectWise web services. Just make sure you install the following role services mentioned in the
next step, for ProjectWise web services.
5. In Server Manager, make sure the Web Server (IIS) role is installed along with the following role
services:
ASP.NET
.NET Extensibility
ISAPI Extensions
ISAPI Filters
Performance
ProjectWise
291

Dynamic Content Compression
6. In Server Manager, make sure the .NET Framework feature is installed. To install it, right-click
Features and select Add Features, then turn on the .NET Framework 3.5.1 Features option in the
Add Features Wizard.
(ProjectWise Web Server also requires .NET Framework.)
7. ProjectWise web services requires Anonymous Authentication, which is enabled by default when
you create websites in IIS.
8. ProjectWise web services delivers the ProjectWise Network Configuration Settings applet for you to
configure the datasource list.
9. Enable SSL for your website using the following steps:
a. Open IIS Manager and go to Connections > computer_name > Sites.
b. Right-click the website you plan to deploy ProjectWise web services to and select Edit Bindings.
c. In the Site Bindings dialog, click Add.
d. In the Add Site Bindings dialog, change Type to https, select an SSL certificate from the list, and
click OK.
e. Click Close to close the Add Site Binding dialog.
f. Add the SSL port 443 to the Windows Firewall exception list on this computer.
Tip: Contact your IT department if you need help obtaining an official SSL certificate. To create a selfsigned certificate, see the following Microsoft topic: http://technet.microsoft.com/en-us/library/
cc753127(v=ws.10).aspx
10. The SSL port is the port through which ProjectWise web services communicates with ProjectWise
Explorer Mobile app users. If ProjectWise Web Server is also installed and using SSL port 443, it is
recommended that you use another SSL port for ProjectWise web services, and then make sure that
port is also added to the Windows Firewall exception list on this computer.
11. The port used for communication with ProjectWise Integration Server depends on which port is set
as the listener port on the ProjectWise Integration Server computer. 5800 is ProjectWise Integration
Servers default listener port; contact your ProjectWise administrator to verify the correct port
number to use. Whatever the port, make sure you add the port number to the Windows Firewall
exception list on this computer. To add / open a port:
c. Set name to ProjectWise TCP, set port to 5800, and set protocol to TCP.
d. Repeat these steps to add the SSL port.
To Install ProjectWise web services

1.
2.
3.
4.
Download the ProjectWise web services installation package and launch the installer.
When the Setup Wizard opens, click Next.
When the License Agreement page opens, accept the agreement and click Next.
When the Destination Folder page opens, accept the default installation location or click Change to
change it, then click Next.
The default installation location is

C:\Program Files\Bentley\ProjectWise Web Services.
ProjectWise
292

6. On the final page of the wizard, select the option to Launch ProjectWise web services Deployment
Wizard, and click Finish.
The Deployment Wizard opens to help you deploy ProjectWise web services to an IIS website. See
the next procedure for details about deploying.
To Deploy ProjectWise web services

1. If you did not select to launch the Deployment Wizard at the end of your installation, you can launch
it now by selecting Start > All Programs > Bentley > ProjectWise Web Services > ProjectWise
Web Services Deployment Wizard.
2. When the Deployment Wizard opens, click Next.
3. On the Deployment Type page, select Deploy ProjectWise web services and click Next.
4. On the Web Site page, select the IIS website to which you want to deploy ProjectWise web services
and click Next.
5. On the Virtual Directory page, enter the name of the directory you want to create for ProjectWise
web services under the selected IIS website.
The Virtual Directory field is set to pwmobileaccess by default. You can accept the default or
change it if needed. When the pwmobileaccess is used, users connecting to this ProjectWise web
services website from ProjectWise Explorer Mobile only need to specify the fully-qualified domain
name of the computer on which ProjectWise web services is installed (for example,
servername.domain.com). If you change the default virtual directory name from
pwmobileaccess to anything else, then ProjectWise Explorer Mobile app users will have to specify
the fully-qualified domain name of the computer plus the virtual directory name, when entering the
address (for example, servername.domain.com/virtualdirectoryname).
6. On the Working Directory page, enter the path to a local folder to use as ProjectWise web services's
working directory (such as, C:\pwmas_workdir), or click Browse to select a folder.
Notes about the working directory:
This working directory is used by ProjectWise web services to store files that are being
transferred between the main ProjectWise server and the ProjectWise Explorer Mobile app
making the request.
Make sure the folder you specify is not already being used by any other deployment.
The working directory must be located on the ProjectWise web services computer.
The working directory cannot be located under the website's home directory (for example, it
cannot be here: C:\inetpub\wwwroot)
Make sure the local system account has Write permission to the specified folder.
UNC paths (\\servername\sharename) are not supported.
7. Click Deploy.
8. When deployment is complete, click Finish.
To Test Your Deployment

1. Enter your websites address into a web browser. For example:
https://localhost/pwmobileaccess
Where pwmobileaccess is the name of the virtual directory you entered in step 3 of the previous
procedure, To Deploy ProjectWise web services.
ProjectWise
293

Retrieving Datasource List Information
A page displays with a message that you have successfully installed ProjectWise web services.
Retrieving Datasource List Information

Now that you have installed and deployed ProjectWise web services, you need to configure the
datasource list that ProjectWise Explorer Mobile users will see when they connect to this ProjectWise
web services.
To Configure the Datasource List

1. Open the Control Panel and set the view to Category.
2. Open the Network and Internet category and double-click the ProjectWise V8i Network icon.
The ProjectWise V8i Network Configuration Settings dialog opens.
3. On the General tab, turn on Prevent UDP for DNS and Listing.
(Make sure there is a check mark in the check box.)
4. On the DNS Services tab:
a. In the Name field, enter a descriptive name for the ProjectWise server you are connecting to. For
example, Main Production Server
b. In the Hostname field, enter the fully-qualified domain name (FQDN) of the computer on which
the ProjectWise server you want to connect to is installed.
c. If the ProjectWise server's listener port is set to the default (5800), then you can leave the Port
field empty. If the ProjectWise server's listener port is set to something other than 5800, then you
must enter the server's listener port in the Port field.
d. Click Add.
e. At the bottom of the tab, turn on Prevent UDP (make sure there is a check mark in the check
box).
5. On the Datasource Listing tab, repeat the steps described in step 4 for the DNS Services tab.
6. When finished, click OK.
You are done. If ProjectWise Explorer is installed on this computer, open it now. If you have
configured everything correctly, the datasource list will display the list of datasources that the
specified ProjectWise server is running. If ProjectWise Explorer was already open, right-click the
ProjectWise Explorer Datasources item at the top of the datasource list and select Refresh.
To Test Your Datasource Connection Configuration

1. Enter your websites address into a web browser. For example:
https://localhost/pwmobileaccess/datasources/
A Save As dialog opens for you to save the datasource list information to a text file. When you open
this file, it will list the datasources to which your users can connect.
ProjectWise
294
Language Packs
14
The text that displays in the various windows, menus, dialogs, and error messages of your ProjectWise
software can be switched to another language by installing a ProjectWise language pack.
ProjectWise language packs provide localized interfaces for users of:
ProjectWise Administrator
ProjectWise Web Parts
ProjectWise Orchestration Framework Administrator
Review the Downloads page on Bentley SELECT for available languages.
Before You Install the ProjectWise Language Pack

1. The ProjectWise module for which you are installing the language pack must be installed before you
install the language pack. If you install the ProjectWise module after you install the ProjectWise
language pack, the language pack will not apply to that module, and you will have to uninstall the
language pack and install it again if you want the language pack to apply.
2. For ProjectWise Explorer and/or ProjectWise Administrator, make sure you first install ProjectWise
Explorer with the User Tools option turned on, as this will be used to set the new locale for these
applications.
3. For ProjectWise Web Parts, the ProjectWise language pack is not installed on user's computers, but
on the ProjectWise Web Server and Web View Server computer. It must be installed to each website
in IIS that ProjectWise Web Server or ProjectWise Web View Server is deployed to, that you want to
change the language for. You must install ProjectWise Web Server and Web View Server before you
install the ProjectWise language pack, but you can install the ProjectWise language pack either
before or after you deploy ProjectWise Web Server or ProjectWise Web View Server.
4. If your are going to deploy ProjectWise Web Server or ProjectWise Web View Server to a SharePoint
site, make sure the appropriate Microsoft SharePoint Language Packs are obtained from Microsoft
and installed. SharePoint Site Language selection determines use of localized user interfaces.
5. If you are going to deploy ProjectWise Web Server or ProjectWise Web View Server to a nonSharePoint site, then make sure your website is configured properly (for details, see http://
msdn.microsoft.com/en-us/library/bz9tc508.aspx
To Install the ProjectWise Language Pack

1. Download the desired ProjectWise language pack from Bentley SELECT. Once downloaded, extract
the contents of the download file to a folder on your computer. The extracted folder will look
something like this:
C:\BentleyDownloads
ProjectWise
295
Language Packs
After You Install the ProjectWise Language Pack
\pw08110901xx
\product
Where XX at the end of the folder name is the two letter abbreviation that indicates the language.
2. In Windows Explorer, open the C:\BentleyDownloads\pw08110901xx\product folder and
double-click the setup.exe file.
3. When the Setup Wizard opens, click Next and follow the prompts to completion.

1. ProjectWise Explorer and ProjectWise Administrator computers:
When the language pack installation is complete, select Start > Programs > Bentley > ProjectWise
V8i (SELECTseries 4) > Tools > User Tools. In the ProjectWise Tools dialog, select the Set Locale
icon and click the Execute button. In the dialog that opens, select the newly installed language, click
OK, then click Close.
2. ProjectWise Web Server computers:
When the language pack installation is complete, deploy ProjectWise Web Server or ProjectWise
Web View Server, then restart both ProjectWise Web Server Host Service and Internet Information
Services (IISRESET).
3. Bentley i-model Composition Server for PDF, ProjectWise Automation Service, ProjectWise
Distribution Service computers:
ProjectWise
296
Language Packs
When the language pack installation is complete, change the display language of the operating
system.
ProjectWise
297
Language Packs
ProjectWise
298
Configuring the ProjectWise Network
15
Connecting Clients and Servers (Overview)

When ProjectWise Explorer is installed on the same subnet as ProjectWise Integration Server (or on the
same subnet as a ProjectWise Gateway Service that has been set up to publish the ProjectWise
Integration Server's datasource lists), users are able to see that server's datasources automatically when
they open ProjectWise Explorer. The same general behavior is true for ProjectWise Web Server; when
the administrator goes to connect a web part to the datasource, they are able to see the datasources
published by servers within the same subnet.
This is because by default, each installation of ProjectWise Explorer and ProjectWise Web Server
broadcasts a request to the network for a list of datasources; any ProjectWise Integration Server or
ProjectWise Gateway Service on the same subnet that receives the broadcast will respond by sending
that client a list of its datasources. These broadcast requests and their responses are carried out using
UDP (User Datagram Protocol). UDP is a connectionless protocol that, like TCP (Transmission Control
Protocol), runs on top of IP networks.
When ProjectWise Explorer or ProjectWise Web Server is not on the same subnet as the ProjectWise
Integration Server, some configuration is required to connect them. ProjectWise provides two options
for this:
Use the ProjectWise Network Configuration Settings dialog on computers on which ProjectWise
Explorer or ProjectWise Web Server is installed. This dialog, available from ProjectWise Explorer or
from the Control Panel, is used to establish a TCP connection from a client computer to the server
computer.
or
Install ProjectWise Gateway Service on a computer that your clients can access. Once installed,
configure the ProjectWise Gateway Service so that it retrieves the datasource list from one or more
ProjectWise Integration Servers. Clients on the same subnet as the ProjectWise Gateway Service, or
those connected to it through the ProjectWise Network Configuration Settings dialog, are then able
to see the selected ProjectWise Integration Servers' datasources.
Connecting Individual Clients to the Server

The ProjectWise Network Configuration Settings dialog is delivered with ProjectWise Explorer and
ProjectWise Web Server and Web View Server, and is primarily used to establish a TCP connection from
the client to one or more servers and thereby obtaining the necessary datasource list information to
populate the datasource lists in these applications.
ProjectWise
299

You can also use this dialog to:

Establish a TCP connection to the computer on which ProjectWise Integration Server or a
ProjectWise Gateway Service is installed (whether it is local or remote), and then block the client
from broadcasting UDP requests, thus improving performance on the client computer.
Direct the client to a server from which they can get server name resolution information.
Depending on the client's socket version and/or the network configuration, the client may have
problems solving IP addresses by host name. For example, a client may be really slow at solving IP
addresses by host name, or may not be able to solve them at all, or the client may fail to retrieve a file
from the storage area, or file operations may be really slow. To eliminate these problems, you should
configure the [NameResolution] section of a server's dmskrnl.cfg file, and then point the
client to that server.
Configure auto-login settings for integrated applications (for ProjectWise Explorer only)
The iDesktop Auto-Login tab is used to control whether or not ProjectWise Explorer users will be
automatically logged into a particular integrated application, when that integrated application is
opened from the desktop.
Enable ProjectWise clients to use IPv6
ProjectWise
300

Caution: For better performance it is strongly recommended to prevent the use of UDP when using
ProjectWise Web Server and Web View Server.
Note: Information entered on the DNS Services and Datasource Listing tabs of the ProjectWise
Network Configuration Settings dialog only affects the client computer you are working on. When
ProjectWise Explorer is installed on a 32-bit operating system, the information gets added to the
computer's registry under the key HKEY_LOCAL_MACHINE\SOFTWARE\Bentley\ProjectWise
\08.11\NetworkConfig. When ProjectWise Explorer and ProjectWise Web Server and Web View
Server are installed on 64-bit operating systems, the information gets added to the computer's registry
under the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Bentley\ProjectWise
\08.11\NetworkConfig.
Note: Although ProjectWise permits you to enter a hostname (computer name), an IP address, or a
fully-qualified domain name (hostname + domain name) in the Hostname fields on the DNS Services
and Datasource Listing tabs, it is recommended that you use fully-qualified domain names (FQDN)
here. Direct use of IP addresses should only be reserved for cases when using DNS names is not an
option.
Note: When using host names, make sure the host names are configured for reverse lookup.
Tip: The default listener port used for TCP connections is 5800. You only need to enter a port number
on the DNS Services and Datasource Listing tabs if the default listener port has been changed in the
dmskrnl.cfg file of the ProjectWise Integration Server or ProjectWise Gateway Service to which you
are connecting.
Note: Whether or not you turn on Prevent UDP on the Datasource Listing tab, your server's
datasources will always display in ProjectWise Explorer, or in the Locations list when connecting
ProjectWise Web Parts, if your ProjectWise Integration Server happens to be on the same computer as
ProjectWise Explorer or ProjectWise Web Server and Web View Server. However, in the case of
ProjectWise Explorer clients only, if you do turn on Prevent UDP on the Datasource Listing tab, the
datasources of the server on the same computer as ProjectWise Explorer will not display in the
datasource list of the ProjectWise Log in dialog that opens when you launch integrated applications
from the desktop, or when you open the ProjectWise Export Wizard or the ProjectWise Import Wizard.
In those cases, you can still log in to the datasource by entering the servername:datasourcename
in the Datasource field.
To Open the ProjectWise Network Configuration Settings Dialog

In ProjectWise Explorer: Select Tools > Network Configuration Settings.
or
From the Control Panel, on 32-bit operating systems: Double-click the ProjectWise V8i Network
icon.
or
ProjectWise
301

From the Control Panel, on newer 64-bit operating systems: Set the view of the Control Panel to
Category view, then open the category called Network and Internet and double-click the
ProjectWise V8i Network icon.
or
From the Control Panel, on older 64-bit operating systems: Open the folder called View 32-bit
Control Panel Items, then double-click the ProjectWise V8i Network icon.
or
From a command prompt on Windows Vista or later, enter: control.exe /name
Bentley.ProjectWiseNetConfiguration
Note: The option to open the ProjectWise Network Configuration Settings dialog from a command
prompt is not available when using Windows XP.
To Connect to a Server and Get Its List of Datasources (TCP)

1. Open the ProjectWise Network Configuration Settings dialog.
2. Select the Datasource Listing tab.
3. In the Name field, enter a descriptive name for the ProjectWise server you are connecting to.
For example: Main Production Server
4. In the Hostname field, enter the fully-qualified domain name (FQDN) of the computer on which the
ProjectWise server you want to connect to is installed.
For example: servername.domain.com
If the ProjectWise server's listener port is set to the default (5800), then leave the Port field empty.
or
If the ProjectWise server's listener port is set to something other than 5800, then you must enter the
server's listener port in the Port field.
6. Click Add.
7. Click OK.
ProjectWise
302

On 32-bit operating systems, the information gets added to the computer's registry under the key
HKEY_LOCAL_MACHINE\SOFTWARE\Bentley\ProjectWise\08.11\NetworkConfig
\DsListing\Servers.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Bentley\ProjectWise
\08.11\NetworkConfig\DsListing\Servers.
To Point to the Server from Which the Client Can Get Server Name Resolution
Information
2. Select the DNS Services tab.
3. In the Name field, enter a descriptive name for the ProjectWise server you are connecting to.
For example: Main Production Server
4. In the Hostname field, enter the fully-qualified domain name (FQDN) of the computer on which the
ProjectWise server you want to connect to is installed.
For example: servername.domain.com
ProjectWise
303

If the ProjectWise server's listener port is set to the default (5800), then leave the Port field empty.
or
If the ProjectWise server's listener port is set to something other than 5800, then you must enter the
server's listener port in the Port field.
6. Click Add.
7. Click OK.
HKEY_LOCAL_MACHINE\SOFTWARE\Bentley\ProjectWise\08.11\NetworkConfig\Dns
\Servers.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Bentley\ProjectWise
\08.11\NetworkConfig\Dns\Servers.
To Prevent the Use of UDP

ProjectWise
304

Publishing Datasource Lists to Multiple Clients
To prevent the use of UDP entirely, turn on Prevent UDP for DNS and Listing on the General tab.
or
To prevent the use of UDP for just server name resolution information, turn on Prevent UDP on the
DNS Services tab.
or
To prevent the use of UDP for just datasource list information, turn on Prevent UDP on the
Datasource Listing tab.
3. Click OK.

It may not always be practical to use the ProjectWise Network Configuration Settings dialog on every
client computer that needs to connect to the ProjectWise Integration Server. For one reason, you might
have too many users that need to connect to the server. Or maybe your users need to connect to
multiple ProjectWise Integration Servers. Or maybe your ProjectWise Integration Server is on a
computer that you do not want users to have direct access to.
In these situations it is better to set up a ProjectWise Gateway Service on the same subnet as your
clients, and then configure the ProjectWise Gateway Service so that it gets the datasource lists from one
or more ProjectWise Integration Servers. By default, the ProjectWise Gateway Service (like the
ProjectWise Integration Server) also broadcasts configuration information to clients using UDP.
Ultimately this makes configuration much easier, since you can set up one ProjectWise Gateway Service
that connects to as many ProjectWise Integration Servers as you like, and the only configuration you
need to perform on your clients' computers is the installation of the client software itself. Also, users
who need to access multiple servers will experience faster datasource list refreshing when using the
ProjectWise Gateway Service instead of the ProjectWise Network Configuration Settings dialog.
Note: If the ProjectWise Gateway Service you have set up is not on the same subnet as some of your
clients, you can use the ProjectWise Network Configuration Settings dialog on those client computers to
connect to the ProjectWise Gateway Service.
If you have ProjectWise Administrator installed on the same computer as ProjectWise Gateway Service,
you can also use the New Datasource Wizard in ProjectWise Administrator to create a link to a
datasource located on another server. Afterwards, ProjectWise Explorer clients on the same subnet as
the ProjectWise Gateway Service will automatically see the linked datasource the next time they refresh
their datasource list in ProjectWise Explorer.
Note: Though the following procedure is typically performed on ProjectWise Gateway Service
computers, you can also use it on a ProjectWise Integration Server computer, to create a link to a
datasource on another ProjectWise Integration Server.
To Set Up a Gateway Service to Publish Datasource Lists from One or More

Servers
1. Install ProjectWise Gateway Service on a computer that your ProjectWise clients can access (a
computer on the same subnet, if possible).
2. In any text editor, open the ProjectWise Gateway Service's dmskrnl.cfg file located in the
...\ProjectWise\Bin directory.
ProjectWise
305

3. Find and make sure the lines Databases=db0 is uncommented.
To uncomment a line, remove the semicolon from the beginning of the line.
4. Find and make sure the line ConnectionSrv=1 is also uncommented.
5. Below the line ConnectionSrv=1 you will see several commented out settings that enable
datasource list publishing. To enable publishing of just one server's datasource list, configure the
following section of lines:
Databases=db0
[db0]
DsServer=1
Server=INTSERVER
Though it is actually further up in the dmskrnl.cfg file, the line Databases=db0 is shown in this
location to give context.
The line Server= is where you specify the name or IP address of the ProjectWise Integration Server
computer. In this example, we are assuming the ProjectWise Integration Server computer name is
INTSERVER.
6. For each additional server you want to publish, add another entry to the Databases= line (db1,
db2, and so on), and then add a corresponding server section below it. For example, the following
section enables the publishing of three ProjectWise Integration Server's datasource lists:
Databases=db0,db1,db2
[db0]
DsServer=1
Server=INTSERVER
[db1]
DsServer=1
Server=INTSERVER2
[db2]
DsServer=1
Server=INTSERVER3
To Create a Link to a Datasource on Another Server

1. In ProjectWise Administrator, right-click the Datasources node and select New > Datasource.
2. When the New Datasource Wizard opens, click Next.
ProjectWise
306

3. When the Choosing Datasource Type page opens, select the option, A link to a datasource that is
located on another server, then click Next.
ProjectWise
307

4. When the Specifying the linked server page opens, type the name of the server that publishes the
datasource to which you want to link, or click Browse to select the server, then click Next.
ProjectWise
308

5. When the Selecting the linked datasource page opens, select a ProjectWise datasource from the list,
and optionally, type a display name in the field below the Datasource name. If no display name is set,
then users will see this internal name, plus the name of the computer on which the datasource's
ProjectWise server is located (for example: <computername>:<datasourcename>). If a display name
is specified, users will see only the display name. When finished, click Next.
ProjectWise
309

Setting Up Gateway Information to Redirect Client Requests
6. When the Finishing New Datasource Wizard page opens, click Finish.
The New Datasource Wizard closes and the selected remote datasource is now listed in ProjectWise
Administrator. The icon for this datasource has an arrow on it, signifying that this is just a link
pointing to a datasource that is actually located on another server.

By configuring the [Gateway] section the dmskrnl.cfg file of a ProjectWise Integration Server or
ProjectWise Gateway Service, you can instruct clients listening to or connected to that server, to redirect
their requests normally bound for one server to another server instead. When requests to one server
are redirected through another server or servers, the requests are said to be routed, and the destination
of the request is referred to as the routed server.
For example, you might want to configure a ProjectWise Gateway Service's [Gateway] section so that
clients listening to or connected to that server send their requests to it, instead of directly to the
ProjectWise Integration Server. (In this example you would also configure the ProjectWise Gateway
Service's [Routing] section to forward those requests to the ProjectWise Integration Server). This way you
can set up your network so that no clients have any direct contact with the ProjectWise Integration
Server. The following simple diagram illustrates this example:
ProjectWise
310

Gateway information is echoed to all clients listening to or connected to that ProjectWise Integration
Server or ProjectWise Gateway Service, so that those clients automatically know where to send their
requests. In this way you can change the way information travels between clients and servers, without
changing the configuration on client computers. Only those clients explicitly allowed (in the
[Gateway] section) to be redirected will have their requests redirected; clients not listed, or those
explicitly denied (also in the [Gateway] section), will not have their requests redirected when
connected to or listening to this particular server.
Note: Currently, when a client is on a different subnet than the ProjectWise Integration Server or
ProjectWise Gateway Service you want them to obtain Gateway information from, that client must add
the server's information to both the DNS Services and Datasource Listing tabs in the ProjectWise
Network Configuration Settings dialog.
A sample, commented out [Gateway] section exists in each dmskrnl.cfg file by default, with
general instructions of usage and syntax. It is recommended that you make a copy of the delivered
examples so you can use the original as a reference. The following is the entire [Gateway] section as
delivered in any dmskrnl.cfg file:
;[Gateway]
;This section provides PW Explorer clients information about where to
direct
;requests when a Routing configuration is desired. All DMS communication
will
;be directed to the Gateway server rather then the Routed server. This
information
;is sent to the PW Explorer client, so it is critical that the Gateway
Server hostname
;be a hostname that the PW Explorer can route to, for example the
external host name
;configured in the NAT server
;Format
;Routed Server = Gateway Server(typically the server on which this config
file appears)
;Integration Server host name = Gateway Service host name
ProjectWise
311

;Examples
;server1 = server2
Tip: There may be cases in which you do not need to specify clients to allow, however it is still good
practice to do so. For example, at the time of configuration, the clients you are allowing may happen to
be the only clients connected to the server. In that case it would not be necessary to explicitly allow
them. However, in the future you might set up other clients that connect to this server, and you may not
want those clients' file requests to be redirected. Or maybe there are newly set up clients, connected to
the server, which you do not know about. If you have already configured the Allow portion to allow
certain clients, the new clients will automatically be denied.
To Configure the [Gateway] Section to Redirect Client Requests

1. Open the dmskrnl.cfg file on the server (ProjectWise Integration Server or ProjectWise Gateway
Service) to which clients are connected or listening.
2. Uncomment the line ;[Gateway] by removing the semicolon (;) from the beginning of the line.
3. Below that, add a line that specifies the server that would normally be the recipient of client
requests, and the server to which those client requests will now be directed.
For example:
[Gateway]
INTSERVER=PGS
This example tells all clients connected or listening to this particular server that any requests they
would normally send to the server called INTSERVER, to send them to the ProjectWise Gateway
Service called PGS instead.
4. If you only want specific clients to have their requests redirected, append a list of those clients to the
line you added in the previous step.
For example:
[Gateway]
INTSERVER=PGS[Allow(userA,userB,userC)]
The Allow list in this example says that regardless of the clients connected to or listening to this
server, only clients userA, userB, and userC will have their requests to INTSERVER redirected to
PGS.
Note: The clients you specify in the Allow list can be specific computer names, IP addresses, or a
range of IP addresses. IP addresses can include wildcards. If you want to allow all clients with the
exception of specific clients, add a Deny list just after the Allow list. For example:
[ALLOW(*.*.*.*),DENY(62.236.163.*,62.236.164.*)]
5. Add additional lines to redirect requests bound for other servers through this server or to another
server.
For example, maybe your ProjectWise network consists of one ProjectWise Gateway Service and
multiple ProjectWise Integration Servers, and you want all client requests to those ProjectWise
Integration Servers to be sent to the ProjectWise Gateway Service instead. In that case, you would
configure the [Gateway] section like this:
[Gateway]
INTSERVER1=PGS
INTSERVER2=PGS
INTSERVER3=PGS
ProjectWise
312

Setting Up Routing Information to Forward Redirected Client Requests
For simplicity, none of the lines in the example above use an Allow list, but as needed you can
append an Allow list (or an Allow/Deny list) for each line you add to this section.
6. On the server now receiving redirected requests, you need to configure the Routing section in that
server's dmskrnl.cfg file so that server can forward these requests on to the appropriate server.
Setting Up Routing Information to Forward Redirected Client

Requests
After you configure a server's [Gateway] section to redirect client requests to another server, you
must then go to the server now receiving the requests (often the same server, as in many ProjectWise
Gateway Service configurations) and configure the [Routing] section in its dmskrnl.cfg file so that
that server will know where to forward these requests. Most often you will configure the server now
receiving the requests (referred to as the gateway server) to forward requests to the routed server (that
is, the final destination of the request). In some cases, however, you may find it necessary to forward
requests to another gateway server, which will then forward the request to its destination. This subtle
difference affects the way you configure the [Routing] section, as you will see below.
A sample, commented out [Routing] section exists in each dmskrnl.cfg file by default, with
general instructions of usage and syntax. It is recommended that you make a copy of the delivered
examples so you can use the original as a reference. The following is the entire [Routing] section as
delivered in any dmskrnl.cfg file:
;[Routing]
;This section is used by the Gateway server that this config file is
installed on
;to determine where to route requests that have been sent to it on behalf
of a Routed Server
;If there are multiple hops necessary to get to the Routed server, this
will direct this server
;to forward to the next hop on a particular port, otherwise only the
information about what
;port number the Routed server is listening on is necessary
;Format
;Routed Server = Port Number,Next Gateway Server
;Examples (shows two different scenarios)
;server1=5800,server3
;server1=5800
Note: The servers specified on both sides of the = character can be represented by the server's name or
IP address.
Note: The port number specified in these examples must match the port number set as the listening
port in the dmskrnl.cfg file of the server you are forwarding the request to. 5800 is the port used in
these examples because it is the default listening port on any ProjectWise Integration Server,
ProjectWise Gateway Service, or ProjectWise Caching Server.
To Configure a Server to Forward Requests

1. Open the dmskrnl.cfg file on the server that is receiving redirected client requests.
2. Uncomment the line ;[Routing] by removing the semicolon (;) from the beginning of the line.
ProjectWise
313

Configuring Server-to-Server Routing
3. To forward requests directly to the routed server (that is, to forward a request to its final
destination), use the following example:
[Routing]
INTSERVER1=5800
This example tells the server that if it receives any requests bound for the server called
INTSERVER1, to go ahead and forward it to INTSERVER1 through port 5800.
4. To forward requests to another gateway server (that is, to a server which will also forward the
request) on its way to the routed server, use the following example:
[Routing]
INTSERVER2=5800,PGS2
This second example tells the server that if it receives any requests bound for the server called
INTSERVER2, to forward it to the ProjectWise Gateway Service called PGS2 through port 5800.
Your next step would be to open PGS2's dmskrnl.cfg file and configure its [Routing] section to
forward requests to the appropriate server.
5. Add additional lines for each routed server this server is forwarding requests to.

Server-to-server routing lets you set up a ProjectWise Gateway Service in a DMZ in order to route
connections from a ProjectWise Integration Server to a ProjectWise Caching Server, in cases where the
ProjectWise Integration Server cannot directly connect to the ProjectWise Caching Server. For example,
if the ProjectWise Caching Server is hosted behind a firewall of another organization.
To configure this feature, routing information is needed in the dmskrnl.cfg file of the ProjectWise
Integration Server, the ProjectWise Caching Server, and the connecting ProjectWise Gateway Service.
For the configuration examples below, assume the following host names for these servers:
PWIS = ProjectWise Integration Server
PWGS = ProjectWise Gateway Service
PWCS = ProjectWise Caching Server
ProjectWise
314

When a client requests a file from a ProjectWise Caching Server, the Caching Server uses the
ProjectWise Integration Server's public key to validate the request and verify the user's access. In a
standard configuration, the Caching Server requests the ProjectWise Integration Server's public key
directly, but in a routed scenario the Caching Server may not be able to connect to the ProjectWise
Integration Server. If this is the case, you must manually specify the ProjectWise Integration Server's
public key in the [FileTokenPublicKeys] section of the Caching Server's dmskrnl.cfg file.
To Set Up a Standard Server-to-Server Routing Configuration

1. In the dmskrnl.cfg file of the ProjectWise Integration Server (PWIS), add the following
information:
[ServerGateway]
PWCS=PWGS
[Routing]
PWGS=5800
2. In the dmskrnl.cfg file of the ProjectWise Gateway Service (PWGS), add the following
information:
[Gateway]
PWIS=PWGS
PWCS=PWGS
[Routing]
PWIS=5800
PWCS=5800
3. In the dmskrnl.cfg file of the ProjectWise Caching Server (PWCS), add the following information:
[ServerGateway]
PWIS=PWGS
[Routing]
PWGS=5800
To Set Up a Unidirectional Server-to-Server Routing Configuration

1. In the dmskrnl.cfg file of the ProjectWise Integration Server (PWIS), add the following
information:
[ServerGateway]
PWCS=PWGS
[Routing]
PWGS=5800
2. In the dmskrnl.cfg file of the ProjectWise Gateway Service (PWGS), add the following
information:
[Gateway]
PWCS=PWGS
[Routing]
PWCS=5800
3. In the dmskrnl.cfg file of the ProjectWise Caching Server (PWCS), add the ProjectWise
Integration Server's public key (note the key below is just an example):
[FileTokenPublicKeys]
PWIS=BgIAAACkAABSU0ExAAQAAAEAAQBb6A14vA1opzUqBH0PFdmYNN1+TzfOyWLumgvuv8
ProjectWise
315

Broadcasting and Listening Ports Used by Servers
FvYgi8eqwmVKW8gReJBWx7Ogr
+Wj0psFMNzUZCqBFuYxQTtqxBL5+udhTUz74QbttqVAfolhwkDuVTRfVGblDO1MKLDUnHpa
vttFr6UoC71Ox8g79kKxa3AzPZxtbt2XEWsA==
Your ProjectWise Integration Server's public key can be found by right-clicking the host name of the
ProjectWise Integration Server in ProjectWise Administrator and selecting Properties. In the
Properties dialog, select the Encryption tab. You can then copy the key found on this tab and paste it
into the [FileTokenPublicKeys] section above as shown.

When ProjectWise Explorer and ProjectWise Web Server clients use UDP to broadcast requests to
ProjectWise servers on the network, the default port open on the ProjectWise server to receive and
respond to these requests is 5799. This is referred to as the broadcast port. When clients use the
ProjectWise Network Configuration Settings dialog to establish a TCP connection to the server, the
default port that the server listens for client connections on is port 5800. This is referred to as the
ProjectWise
316

listener port. The following sections are included in a ProjectWise server's dmskrnl.cfg file for
configuring broadcasting and listening settings:
; -----------------------------------------------------------; Section defines broadcasting settings (UDP connections)
; -----------------------------------------------------------[Broadcast]
; Port number for broadcasting list of datasources
Port=5799
; Name of service in etc\services file to use if port is not specified
;Name=dmsbdr
...
; -----------------------------------------------------------; Section defines listening settings (TCP connections)
; -----------------------------------------------------------[Listener]
; Port number for incoming TCP connections
Port=5800
; Name of service in etc\services file to use if port is not specified
;Name=dms
...
You can leave the defaults as is or change them as necessary. If you change the broadcasting (UDP) port
on the server, no configuration on your client computers is necessary. If you change the listening (TCP)
port on the server, you will have to also change the port specified on your clients' ProjectWise Network
Configuration Settings dialog.
Note: If the TCP listening port is changed from the default value of 5800, and you have UDP datasource
discovery disabled, you must create an entry for that server in the DNS Services tab of the ProjectWise
Network Configuration Settings dialog, on any client computer that will access that server.
To Change the Default Ports Used by the Server

1. Open the dmskrnl.cfg file (...\ProjectWise\bin) in a text editor.
2. To change the default broadcasting port, find [Broadcast] and below that line, change
Port=5799 to Port=new broadcasting port #.
3. To change the default listening port, find [Listener] and below that line, change Port=5800 to
Port=new listening port #.
4. When finished, save and close the dmskrnl.cfg file and restart the server in the Services window.
Windows Firewall Exceptions List (Windows XP only)

The installation of certain Windows updates may turn on your Windows Firewall and block the default
ProjectWise broadcasting and listening ports 5799 and 5800. If you install Windows updates on a
ProjectWise Explorer computer and later notice that the datasources which normally display through
UDP are not showing up in ProjectWise Explorer, check to see if the Windows Firewall on that computer
is on and if it is blocking ports 5799 and 5800. You can either turn off the firewall, or you can add the
ProjectWise ports into the firewall's exceptions list. To check to see if the firewall is on, go to Start >
Settings > Control panel > Windows Firewall. The General tab displays whether it is on or off. If you
decide to leave the firewall on, add each port to the firewall's exceptions list by clicking Add Port on the
ProjectWise
317

ProjectWise Server Name Resolution
Exceptions tab. For port 5799, set name to ProjectWise UDP, set port to 5799, and set protocol to UDP.
For port 5800, set name to ProjectWise TCP, set port to 5800, and set protocol to TCP.
ProjectWise Server Name Resolution

Depending on a ProjectWise Explorer client's socket version and/or the network configuration, the
client may have problems solving IP addresses by host name. For example, a client may be really slow at
solving IP addresses by host name, or not able to solve it at all, or the client may fail to retrieve a file
from the storage area, or file operations may be really slow. To eliminate these problems, you can
configure the [NameResolution] section of a server's dmskrnl.cfg file, and then point the client to
that server through the ProjectWise Network Configuration Settings dialog.
For each NameResolution entry, the value name is the IP address (recommended) or host name. The
value is a comma separated host name list that can be extended with allow and deny masks if required.
In some installations the same host name can be bound to different IP addresses depending on the client
who is requesting the internal DNS information.
For example, we could have a server with a host name serverA having an internal IP address of
62.236.163.41. The internal IP address will be used by the clients located in the local networks
62.236.136.* or 62.236.164.*. This address cannot be used by clients located outside the local
networks. There may be a firewall machine that has an internal IP address of 62.236.136.98
(accessible by clients located in local networks) and an IP address outside (accessible by clients that are
not located in the local network) of 75.129.120.98. Then there is port to port mapping configured, so
that requests sent to 75.129.120.98 to port 5800 are transferred to 62.236.163.41 to port 5800.
In this scenario host name serverA must be bound to 62.236.163.41 when requests are sent by
62.236.136.* or 62.236.164.* clients. But for all other clients the same host name serverA
must be bound to 75.129.120.98.
Let us also include in this scenario a server with the host name serverB with an IP address of
65.230.152.1 that is accessible by all clients. Also in this example we have serverC and we let the
server solve the IP address for it on runtime when the configuration file is loaded.
This case can be solved by adding two entries for serverA in the [NameResolution] section, both
having allow/deny masks and one entry for serverB and one for serverC:
[NameResolution]
62.236.163.41=serverA.domain.com[ALLOW(62.236.163.*,62.236.164.*)]
75.129.120.98=serverA.domain.com[ALLOW(*.*.*.*),DENY(62.236.163.*,
62.236.164.*)]
65.230.152.1=serverB.domain.com
serverC=serverC.domain.com
All the [NameResolution] section entries that do not have allow/deny masks can also be used by the
server itself to solve the addresses of routed servers and datasource server addresses, and so on.
In this example serverB and serverC entries would be echoed to clients and could be used by the
server itself, but entries for serverA are only echoed to the clients and not used by the server itself.
Setting Up ProjectWise to Use IPv6

ProjectWise fully supports Internet Protocol Version 6 (IPv6).
ProjectWise
318

Caution: Before you begin, it is highly recommended that you contact Bentley Professional Services to
assist you in setting up ProjectWise V8i (SELECTseries 4) on IPv6.
To run ProjectWise V8i (SELECTseries 4) on IPv6:
All ProjectWise V8i (SELECTseries 4) clients and servers must be part of the IPv6 network.
All ProjectWise V8i (SELECTseries 4) clients and servers must be configured to use IPv6, by enabling
the IPv6 settings on the ProjectWise V8i Network Configuration Settings dialog.
All ProjectWise V8i (SELECTseries 4) servers must be configured to use IPv6, by enabling the IPv6
settings in the dmskrnl.cfg file.
Note: On Windows XP and Windows Server 2003, IPv6 is not installed by default. On those operating
systems you will need to manually install IPv6 before enabling the IPv6 settings in the ProjectWise
Network Configuration Settings dialog.
Note: For situations in which you need to enter a datasource name using both the IP address and the
datasource name (IP:datasource) for example, when logging in through ProjectWise Explorer or
integrated applications when using IPv6 you need to enter the IP address inside square brackets [ ].
For example:
[2001:ffff:ffff::1]:datasource
The same is true, when using IPv6, for situations in which you need to enter a server address using the
IP address followed by a port number (IP:port). For example:
[2001:ffff:ffff::1]:port
To Enable ProjectWise Clients to Use IPv6

1. Open the ProjectWise Network Configuration Settings dialog on each of the ProjectWise Explorer,
ProjectWise Administrator, and ProjectWise Web Server computers in your network.
2. On the General tab, turn on IPv6 Enabled and IPv6 Preferred.
3. Click OK.
ProjectWise
319

To Enable ProjectWise Servers to Use IPv6

1. Open the dmskrnl.cfg file (...\ProjectWise\bin) on the server computer you are
configuring.
2. Find ;IPV6Enabled=0. Uncomment the line and change the value to 1. For example:
IPV6Enabled=1
3. Find ;IPV6Preferred=0. Uncomment the line and change the value to 1. For example:
IPV6Preferred=1
ProjectWise
320
Operational Procedures
16
Backup and Restore Procedures

This section discusses the following types of project restoration and backup procedures:
Full Backup - One-to-One Project Definition

Full Restore
Incremental Restore
Full Backup - One-to-Many Project Definition
Project Restoration Using the ProjectWise Import Wizard
Full Backup: One-to-One Project Definition

The process for this archive type differs depending on the project definition in use.
To Archive Using One-to-One Project Definition
1. From ProjectWise Administrator, record all storage area definitions used by this project, including
computer hostname or IP address, and folder name.
2. Restrict access to the database so that the project is in a known and stable state during the backup.
To do this, stop the ProjectWise Integration Server service.
3. Back up the entire database to offline media using tools supplied by the database vendor.
4. From the list compiled in step 1, back up all storage areas used by this project to offline media using
operating system tools or off-the-shelf backup tools.
Note: These storage areas can be on the ProjectWise Integration Server or distributed on the
network to computers running the ProjectWise Caching Server.
5. When done, restart the ProjectWise Integration Server service.
Full Restore
To restore the entire project using this method, simply reverse the backup procedure.
To Restore Using One-to-One Project Definition
1.
2.
3.
4.
ProjectWise
Restrict access to the database by stopping the ProjectWise Integration Server service.
Restore the database using tools supplied by the database vendor.
Restore all storage areas using operating system tools or off-the-shelf backup tools.
When done, restart the ProjectWise Integration Server service.
321
Incremental Restore
In some cases, the system administrator needs to selectively restore files, rather than the entire
database. In this case, the file likely exists, but has been damaged and it is necessary to revert back to a
previous version.
This method is sufficient provided that file names are unique within your project. If you are searching
for a file that exists in multiple folders within the backup, you will need to obtain the Folder Identifier
(Folder ID) in order to retrieve the correct file from the backup media. Files are stored in storage areas
under folders named per the Folder ID, not the Folder Name. One of the benefits of this approach is that
folder names can be changed without adverse effects on the project.
To Restore a Single File
1. Open ProjectWise Explorer, log in to the datasource, and view the properties of the document in
question.
2. Note the File Name (as opposed to the Document Name, which may be different).
3. Restore the file from the backup media to a temporary folder.
4. Return to ProjectWise Explorer and once again, view the properties of the document in question.
5. On the General tab of the Document Properties dialog, click Remove to delete the existing file.
6. Click Import and browse to the temporary folder to attach the restored file to this document.
7. Click OK to save the changes to the document.
8. Close the Properties dialog when done.
To Restore a Single File That Exists in Multiple Folders
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
ProjectWise
Open ProjectWise Explorer and log in to the datasource.

Select View > Managed Views.
In the Manage Views dialog, click New.
In the Create View dialog, create a view called Admin.
(You only need to do this the first time.)
Add columns to the new view for Document Name, File Name, Folder Name, and Folder ID. You
can add other columns as required.
Close the Create View dialog.
In ProjectWise, browse to the document in question and note the Folder ID column. It should be a
number like 184.
The folder in which to look on the archive media will be named per the folder ID. Specifically, the
folder name will have the format dmsXXXXX where XXXXX will be replaced by the folder ID you
obtained. It will be five characters long and will be padded with leading zeros as required to fill out
the five characters. In the example above, the folder name would be dms00184.
Note the File Name (as opposed to the Document Name, which may be different).
Restore this file from the correct folder on the backup media to a temporary folder.
Return to ProjectWise Explorer and view the properties of the document in question.
On the General tab of the Document Properties dialog, click Remove to delete the existing file.
Click Import and browse to the temporary folder to attach the restored file to this document.
Click OK to save the changes to the document.
322
15. Close the Properties dialog when done.
Full Backup: One-to-Many Project Definition

If the one-to-many project definition is in use, then you must decide whether to back up the entire
database (all projects) or a subset of (selected projects) the database. If you want to back up the entire
database, refer to the procedure above for Full Backup. If you want to back up individually selected
project(s), use the ProjectWise Export Wizard to back up the metadata. Prior to starting the backup
process, you must prevent users from checking out files by restricting access to the database. In this
case, the ProjectWise Integration Server service cannot be stopped (or the Export Wizard will not be
able to log in). You can limit access to the project by IP address filtering. This can be accomplished in
ProjectWise Administrator under general settings for the datasource.
At this point, the Export Wizard exports all folders, files, metadata, application definitions, environment
definitions, and so on required to restore this data at a future date. This project can then be imported
into any other datasource using the ProjectWise Import Wizard. The Export Wizard does not export
users and associated group membership, workflow states or security schema(s).
Once the Export Wizard has finished, the script file and the actual document files will be in the
temporary folder specified for the script file. The files will be in a subfolder named failles. The script
file created by the export process is critical as it contains all the metadata mentioned above. This file will
be needed to restore the project using the Import Wizard. You are now ready to move the contents of
the temporary folder to the offline media of your choice. Once this is accomplished, you can remove the
IP address filter from the database to allow general access again.
This second procedure could also be used in the first case (the one-to-one project definition). The
advantage of using this method is that all files will be copied to the temporary folder automatically,
rather than the administrator having to copy them from each storage area. The disadvantages are:
Users, Groups, Security and Workflow schemas are not captured by this method.
Only the most recent version of a document will be backed up.
To Perform a Full Backup on a Selected Project Using the ProjectWise Export Wizard
1. Create a temporary folder in which to store the exported files prior to committing to backup media.
2. In ProjectWise Administrator, record all storage area definitions used by this project, including
3. Launch the ProjectWise Export Wizard by selecting Start > All Programs > Bentley > ProjectWise
V8i (SELECTseries 4) > Tools > Export Wizard, then follow the steps in the procedure, To Export
Datasource Data Using the ProjectWise Export Wizard, which can be found in the ProjectWise
Explorer help under ProjectWise User Tools > Exporting Datasource Data.
Note: When you are specifying the script file path and name, use the temporary folder created in
step 1.

A project that was backed up using the ProjectWise Export Wizard can be restored using the Import
Wizard. The project can be imported into any ProjectWise datasource, not just the original.
ProjectWise
323
Archival Procedures
To Restore a Project if the Datasource Already Exists

1. Restore files from backup media to a temporary folder structure.
2. If necessary, restrict access to the datasource by establishing IP address filter(s).
3. In ProjectWise Administrator, create any necessary storage areas for the project you are about to
import.
4. Launch the ProjectWise Import Wizard by selecting Start > All Programs > Bentley > ProjectWise
V8i (SELECTseries 4) > Tools > Import Wizard, then follow the steps in the procedure, To Import
Exported Datasource Data Using the ProjectWise Import Wizard, which can be found in the
ProjectWise Explorer help under ProjectWise User Tools > Importing Exported Datasource Data
Note: You will receive warnings if the project is being imported into a ProjectWise datasource that
contains other projects. These warnings occur when the Import Wizard attempts to import an
environment or application definition that already exists in the datasource.
5. When prompted in the wizard, browse to the script file that you restored to the temporary folder,
and continue with the instructions in the section mentioned above.
Archival Procedures
The process of archiving project data can take several different forms, depending on the organization,
the nature of their projects, and the available infrastructure. For many organizations, the term archive
means to move all project data to offline storage in order to make room for future projects. For others,
the term means to keep the data online, but in such a manner that it can be referenced or copied, but not
modified. Still others would prefer to move only the files to offline storage, keeping the metadata online
for searching. In this case, one might include an attribute in the environment definition to indicate
which offline media contains the file after archival. In the event that a search turns up an archived file,
the system administrator would then locate the offline media and restore the file. This section addresses
the tools made available by ProjectWise to facilitate these processes, and how to build standard archival
procedures from them.
This section discusses the following types of archival and restoration procedures:
Archive Approach 1 Back up all data and move to offline storage

Project Restoration using the ProjectWise Import Wizard
Archive Approach 2 Archival of files only
Archive Approach 3 Keeping all data online
Archive Approach 1 - Back Up All Data and Move to Offline Storage

In this case, all project data (both files and metadata) will be removed from ProjectWise so that future
searches will not locate any documents from the project.
Advantages:
All data is archived for safe keeping
Infrastructure resources are freed for future projects
Disadvantages:
Cannot locate documents from this project through ProjectWise searches
ProjectWise
324
Archival Procedures
Remote storage location must also be moved to offline media
The process for this archive type differs depending on the project definition in use.
If the one-to-many project definition is in use, then the process must take into account that the entire
database cannot be removed. In this case, the metadata for this project must be removed from the
database, while leaving the metadata for other projects online. ProjectWise provides Import and Export
Wizards to facilitate this process. Prior to starting the archive process, you must prevent users from
checking out files while you are removing them from the database. To do this, you may either limit
access to the entire ProjectWise datasource (by denying all IP addresses except your own from
ProjectWise Administrator) or by changing the security schema for the project root folder to allow
access only to yourself.
At this point, the Export Wizard exports all folders, files, metadata, application definitions, environment
definitions, and so on, required to import this data at a future date. This project can then be imported
into this or any other datasource using the ProjectWise Import Wizard. The Export Wizard does not
export users and associated group membership, workflow states or security schema(s).
Once the export Wizard has finished, the script file and the actual document files will be in the
temporary folder specified for the script file. The files will be in a subfolder named files000. The
script file created by the export process is critical as it contains all the metadata mentioned above. This
file will be required should the need arise to bring this project online again using the Import Wizard.
You are now ready to move the contents of the temporary folder to the offline media of your choice.
Once this has been accomplished, you will then need to remove the project folder structure from
ProjectWise since the Export Wizard does not do this.
It should be noted that this second procedure could also be used in the first case (the one-to-one project
definition). The advantage of using this method is that all files will be copied to the temporary folder
automatically, rather than the administrator having to copy them from each storage area. The
disadvantages are:
Users, Groups, Security and Workflow schemas are not captured by this method.
Only the most recent version of a document will be archived.
To Archive All Data and Move to Offline Storage
2. In ProjectWise Administrator, delete the datasource from the ProjectWise server to prevent future
access.
3. Record the database connection information in case the database needs to be brought online in the
future.
4. Back up the entire database to offline media using tools supplied by the database vendor.
5. If using an ODBC connection to the database, remove it at this time.
6. Back up all storage areas used by this project to offline media using operating system tools or offthe-shelf backup tools.
7. Delete all files from the storage areas once they have been verified on the backup media.
8. If the storage area(s) were used solely for this project (as is recommended), then they should now be
removed from the host computer.
ProjectWise
325
Archival Procedures
To Archive Using the ProjectWise Export Wizard

1. Create a temporary folder in which to store the exported files prior to committing to archive media.
3. Launch the ProjectWise Export Wizard by selecting Start > All Programs > Bentley > ProjectWise
V8i (SELECTseries 4) > Tools > Export Wizard, then follow the steps in the procedure, To Export
Datasource Data Using the ProjectWise Export Wizard, which can be found in the ProjectWise
Explorer help under ProjectWise User Tools > Exporting Datasource Data.
Note: When you are specifying the script file path and name, use the temporary folder created in
step 1.
To Remove the Project Folder Structure from ProjectWise
1. From ProjectWise Explorer, select the root level folder for the project.
2. Right-click the folder and select Delete.
The Delete Folder dialog opens.
3. On the General tab, turn on all options.
4. On the Advanced tab, turn on Ignore members of undeleted sets. If documents are still checkedout, then also turn on Ignore checked out documents and/or Free and delete own check outs.
5. Click Delete to complete the operation.
6. In ProjectWise Administrator, remove any storage areas that were used solely for this project.
7. If the storage area(s) were used solely for this project (as is recommended), then the folder can now
be removed from the host computer.

A project that was archived using the ProjectWise Export Wizard may be brought online again using the
Import Wizard. The project can be imported into any ProjectWise datasource, not just the original.
Assuming the ProjectWise datasource already exists, the process for importing an archived project
follows below.
To Import an Archived Project
1. In ProjectWise Administrator, create any necessary storage areas for the project you are about to
import.
2. Launch the ProjectWise Import Wizard by selecting Start > All Programs > Bentley > ProjectWise
V8i (SELECTseries 4) > Tools > Import Wizard, then follow the steps in the procedure, To Import
Exported Datasource Data Using the ProjectWise Import Wizard, which can be found in the
ProjectWise Explorer help under ProjectWise User Tools > Importing Exported Datasource Data
Note: You will receive warnings if the project is being imported into a ProjectWise datasource that
contains other projects. These warnings occur when the Import Wizard attempts to import an
environment or application definition that already exists in the datasource.
ProjectWise
326
Archival Procedures
Archive Approach 2 - Archival of Files Only

In some cases, administrators select to archive files only, while leaving the document metadata online.
This approach enables users to still search against the metadata, although not to access the file without
requesting it be restored. This is most easily accomplished when storage area(s) are dedicated to single
projects. This method is limited in that there is no mechanism to detach the file from the document
record in the datasource other than individually. This is accomplished for a single file by opening the
Properties dialog for that document. You may want to create a CD of the files and redirect the storage
area to that CD. The CD would then be kept online. In this manner, the files would still be available, but
would not be able to be modified. Users would be able to view or copy these documents to create new
documents without Administrator intervention.
To Move a Project to CD
1. In ProjectWise Administrator, note all storage areas used by the project.
2. Make sure all files are checked in, and then limit access to the project. Accomplish this by limiting
connections to the datasource (by IP address filtering), or by applying a restricted security schema to
the root level folder for the project.
3. Once access has been restricted, create a CD of the entire storage area directory structure associated
with the project.
4. Mount the newly created CD in a drive that is accessible from either the ProjectWise Integration
Server or one of the ProjectWise Caching Servers.
5. In ProjectWise Administrator, modify the existing storage area(s) to point to the drive in which the
CD is mounted. You will be warned that you must manually move all files to the new storage area.
6. From the operating system, remove the folder structure representing the old storage location.
To Remove the Files Without Transferring to a CD
1. In ProjectWise Administrator, note all storage areas used by the project.
2. Make sure all files are checked in, and then limit access to the project. This can be accomplished by
limiting connections to the datasource (by IP address filtering) or by applying security to the root
level folder for the project.
3. Using operating system or off-the-shelf backup tools, back up all files in the noted storage area(s).
4. In ProjectWise Explorer, create and run a search that finds all documents in the project.
5. From the search results, select the first document and open the Properties dialog.
6. On General tab of the Document Properties dialog, click Remove to detach the file from the
document.
7. Click > to advance to the next document.
8. Click Remove and continue until all files have been removed.
Archive Approach 3 - Keeping All Data Online

The final approach for archiving project data is to keep all project files online but to limit access, thus
preventing documents from being checked out. For instance, you may want to make all files read-only to
all project team members, yet still have them visible. As an alternative, the documents can be read-only
to some, yet invisible to others.
ProjectWise
327
Archival Procedures
These and other variations can be accomplished through ProjectWise access control, by applying
Workflow or Folder level security as needed. Another approach is to simply apply the Set Final Status
command on all project documents. In all cases, all data (both files and metadata) remains online and
can quickly be made active or visible again.
The simplest method is to apply the Set Final Status command on the project documents.
To Keep Files Online But Limit Access
1.
2.
3.
4.
Make sure that all documents are checked in.

From ProjectWise Explorer, create and run a search that finds all documents to be archived.
From the search results, select all documents.
Select Document > Change State > Set Final Status.
All documents will now be read-only, but will still be visible. In addition, the project folder structure
itself remains visible. Documents in this state can be viewed or copied, but not modified. Finally, the
document attributes can be viewed but not modified when a document is in this state. It should be noted
that the Set final status and Remove final status privileges may be granted to any user as deemed
necessary by the system administrator (through user settings).
As an alternative, you can accomplish the same goal within ProjectWise using Folder level security. This
method has the added advantage of being able to hide, some or all folders within the project or to hide
documents. In contrast, the previous method left all documents visible. The following procedure can be
adapted to the needs of the organization to perform online archival using Folder and Document level
security.
To Keep Files Online But Hide Folders or Documents
1.
2.
3.
4.
5.
In ProjectWise Explorer, select the root folder for the project.

Right-click and select Properties.
In the Folder Properties dialog, select the Security tab.
Remove all groups except Administrator and click Apply.
When prompted, select Apply changes to this folder only, which causes all subfolders to inherit
this security.
6. Close the Folder Properties dialog.
In this case, the entire project folder structure is only visible to the Administrator, so the documents
themselves do not need to be protected.
As an alternative, you might decide to leave the folder structure visible, but restrict access to the
documents. To do so, use the following procedure.
To Keep Files Online and Visible But Restrict Access
1.
2.
3.
4.
5.
ProjectWise
Make sure that all documents in the project are checked in.
In ProjectWise Explorer, select the root folder for the project.
Right-click and select Properties.
In the Folder Properties dialog, select the Document Security tab.
On the Document Security tab, select each group and set its access so that Read and File Read are
the only enabled options.
328
Disaster Recovery Procedures
Read allows users to look at the properties of a document. File Read allows them to view the actual
file.
6. When all groups have been correctly set, click Apply.
7. When prompted, select Apply changes to this folder only, which causes all subfolders to inherit
this security.
8. Close the Folder Properties dialog.

This section provides a process for recovering ProjectWise in the event of a complete failure of the
ProjectWise server. Recovering ProjectWise after such a failure is not a difficult task, provided the
proper precautionary steps have been taken to prepare for such an event. These steps involve creating
backups of critical configuration and license files, as well as the ProjectWise database instance(s) and
file storage locations. In addition, complete documentation of the deployment must be created in order
to redeploy the ProjectWise software modules in a like fashion after such an event. Due to the modular
nature of the three-tier ProjectWise architecture, this section serves only as a guideline because each
ProjectWise deployment is unique. You should view this section in the context of your deployed
ProjectWise modules, as all modules are addressed herein.
It is assumed that all ProjectWise modules are deployed on the same physical computer. This is rarely
the case when all modules are deployed. In large scale deployments, ProjectWise modules are typically
spread across multiple computers. In addition to enhancing performance, this approach also means that
a system failure does not result in a complete redeployment of all ProjectWise modules. Only those
modules deployed on the failed hardware need to be restored. All ProjectWise modules, including
server and client, are listed to clarify their purpose, although disaster recovery only refers to the server
modules.
ProjectWise Server Components
ProjectWise
Components
Deployment
Status
Provided By Notes
Database Engine
Required
Other
Oracle or SQL Server
ProjectWise Orchestration
Framework Service
Optional
Bentley
Required if using Bentley i-model

Composition Server for PDF, ProjectWise
Automation Service, ProjectWise
Distribution Service, and/or the
automated document processors
delivered with ProjectWise Integration
Server.
ProjectWise Integration
Server
Required
Bentley
This is the main ProjectWise server.
ProjectWise User
Synchronization Service
Optional
Bentley
Used for account synchronization with

Windows Domain servers.
329
Components
Deployment
Status
Provided By Notes
Optional
Bentley
Provides access to datasources through a

web browser using ProjectWise Web
Parts.
ProjectWise Publishing
Server
Optional
Bentley
Used for viewing and marking up

MicroStation and AutoCAD documents
from ProjectWise Web Parts.
ProjectWise Publishing
Gateway Service
Optional
Bentley
Used to integrate ProjectWise Publishing

Server with ProjectWise Web Server.
ProjectWise Caching
Server
Optional
Bentley
Only installed on computers that will act

exclusively as files servers.
ProjectWise Gateway
Service
Optional
Bentley
Typically used in DMZ configurations.

Can also be used in configurations
involving multiple subnets.
Bentley i-model
Composition Server for
PDF
Optional
Bentley
Enables ProjectWise Explorer users to

publish renditions from selected
documents, and lets administrators
define rendition jobs to publish
renditions in batch.
ProjectWise Automation
Service
Optional
Bentley
Delivers several extensions for the

automation of certain processes,
including i-model publishing and
component indexing.
ProjectWise Distribution
Service
Optional
Bentley
Used in conjunction with ProjectWise

InterPlot Server, to render and
distribute documents.
ProjectWise web services
Optional
Bentley
Provides ProjectWise Explorer Mobile

users with a list of ProjectWise
datasources they can connect to.
ProjectWise Client Components
ProjectWise
Components
Deployment
Status
Provided By Notes
Required
Bentley
330
Required for accessing documents.
Components
Deployment
Status
Provided By Notes
ProjectWise iDesktop
Integration
Optional
Bentley
Used for application integration at the

desktop level.
iDesktop Integration is installed through
the ProjectWise Explorer installer.
ProjectWise i-model
Packager
Optional
Bentley
Requires ProjectWise Explorer.
ProjectWise Administrator Optional
Bentley
Often installed on server as well as

administrative computers.
Bentley i-model
Composition Server
Administrator
Optional
Bentley
For creating and running Bentley imodel Composition Server for PDF jobs.
ProjectWise Automation
Service Administrator
Optional
Bentley
For creating and running Automation

Service jobs.
ProjectWise Distribution
Service Administrator
Optional
Bentley
For creating and running Distribution

Service jobs.
Bentley i-model Composition Server

Administrator is installed through the
Bentley i-model Composition Server for
PDF installer.
Backing Up Configuration Files

It is important to back up all configuration files for disaster recovery purposes. These files rarely change
once the configuration has been established so it is not necessary to include them in daily backups. You
might include them in weekly backups or whenever configuration changes are made. In the discussion
below, we will examine each component and the critical files that should be included in the disaster
recovery backup plan.
Database Engine
ProjectWise supports several industry standard databases. All databases use an ODBC connection. See
the database vendor's documentation for critical file recovery.
ODBC Configuration
The ODBC connection information needs to be recorded for disaster recovery purposes. Since ODBC
configurations are stored in the Windows Registry, the easiest way to record this information is to take
screen captures of each tab in the ODBC configuration dialog. If your ODBC configuration includes a
password (see the Login tab on the ODBC configuration dialog), this information will not print out, so it
should be recorded in a document and printed along with the screen captures.
ProjectWise
331
ProjectWise Integration Server, ProjectWise Caching Server, and ProjectWise Gateway

Service
ProjectWise Integration Server's main configuration file is dmskrnl.cfg, which can be found here
after a default installation:
C:\Program Files\Bentley\ProjectWise\bin\dmskrnl.cfg
Important: If the server is to be completely rebuilt (reinstallation of operating system), it should be
built with the same hostname.
ProjectWise Caching Server and ProjectWise Gateway Service installations also deliver a dmskrnl.cfg
file, each of which should also be backed up, in addition to the ProjectWise Integration Server's
dmskrnl.cfg file. 64-bit versions of ProjectWise Caching Server and ProjectWise Gateway Service are
installed to the same default location as ProjectWise Integration Server as noted above, while 32-bit
versions of ProjectWise Gateway Service and ProjectWise Caching Server are installed to:
C:\Program Files (x86)\Bentley\ProjectWise
Licenses
ProjectWise licensing is managed by SELECTserver, therefore, the license file(s) on your SELECTserver
should be saved for disaster recovery purposes.
Rebuilding the ProjectWise Server

Again, this section assumes that all ProjectWise server components need to be restored. It is also
assumed that the operating system has been restored, and all required service packs / security patches
have been installed. In this case, the process is essentially a redeployment of ProjectWise. However,
since the database(s), configuration files and license files are available on backup media, the process can
be shortened. Most project configuration parameters are stored in the ProjectWise datasource itself,
leaving only a few server specific (rather than project specific) configuration parameters to be stored in
the ProjectWise configuration file. The disaster recovery procedure below discusses the redeployment
process only when it differs from the standard procedures in the main chapters of this ProjectWise
Implementation Guide.
To Rebuild the Server
1. Reinstall database server software. Rather than creating a new database, restore the database(s)
from backup media. Follow the remainder of the instructions to reestablish the database, including
creating the ODBC Connection if required by the particular database. At the time of this writing, all
databases require ODBC connections.
2. Install ProjectWise Integration Server. Be sure to install the Integration Server to the same path as
the original installation.
3. Install ProjectWise Administrator, selecting the Typical installation option.
A standard deployment calls for the connection of ProjectWise to the database instance. It then
proceeds to create the mandatory ProjectWise tables in the new database. Since we are not creating
a new database, we can skip these steps. Rather than adding the database to the ProjectWise
ProjectWise
332
4.
5.
6.
7.
8.
9.
10.
ProjectWise
configuration using ProjectWise Administrator, copy the saved ProjectWise configuration file from
the backup media to the appropriate directory.
Find dmskrnl.cfg on the backup media and copy it to:
C:\Program Files\Bentley\ProjectWise\bin.
To activate the new configuration file, either restart the ProjectWise Integration Server service or
reboot the computer.
(Optional) Install ProjectWise Explorer and log in to the datasource to verify connectivity.
Reinstall ProjectWise Web Server.
Reinstall and configure ProjectWise Publishing Server. If necessary, restore the Bentley SELECT
Server license for ProjectWise Publishing Server (in the event that the SELECT Server was running
on the same computer).
Reinstall ProjectWise Publishing Gateway Service to integrate ProjectWise Publishing Server with
ProjectWise Web Server.
Reboot the computer to activate all configuration and license files.
333
ProjectWise
334
Upgrade Planning
17
This section discusses the suggested process for upgrading a ProjectWise V8 2004 Edition or later
system to ProjectWise V8i (SELECTseries 4). The process outlined below is intended to serve as general
guidance only and may not apply to all installations. You should become familiar with the new
capabilities of this version before upgrading your production environment to ensure a successful
upgrade.
Caution: Contacting Bentley Professional Services is highly recommended for site assessment,
installation, and configuration services in support of the upgrade process.
Caution: It is highly recommended that a test conversion be performed and validated prior to
upgrading a production environment.
Caution: Upgrading from V8 (8.1x) or earlier requires assistance from Bentley Professional Services
due to the complexity of the upgrade.
Caution: Some upgrades, depending on the version you are upgrading from, require that you check in
all checked out documents before upgrading, to ensure the integrity of master/reference document
relationships. Exported documents can remain exported during the upgrade. See the Precautions section
for details.
ProjectWise Application Integration Compatibility

The ProjectWise readme lists the primary applications and versions known to be supported with
ProjectWise at the time of this release.
For a more comprehensive listing of applications and versions supported with ProjectWise, see the
ProjectWise Application Integration Compatibility document on the Be Communities website. This
document will be updated periodically.
Setting Up a Test Environment

Before you upgrade your production environment to ProjectWise V8i (SELECTseries 4), it is
recommended that you first set up and run ProjectWise V8i (SELECTseries 4) in a test environment. To
do so, you can use the same instructions to upgrade your database and datasource as described in the
section, Upgrading to ProjectWise V8i (SELECTseries 4), with the following exceptions:
1. Make a copy of your current ProjectWise database, to be used in the upgrade test. Use your
database's standard backup and restoration tools to do this.
2. When setting up your test environment, install the new ProjectWise V8i (SELECTseries 4) software
on a dedicated server or servers, and NOT on any of your production servers. Consider using virtual
servers for your test environment.
3. Make a copy of your current ProjectWise storage area(s), to be used for your test datasource. Next,
open your database, and open the dms_store table for write. There will be one row in this table for
ProjectWise
335
Upgrade Planning
Upgrading to ProjectWise V8i (SELECTseries 4)
each storage area used by the datasource. For each storage area row, change the value in the
o_node column to be the computer name (or IP Address if that is how you are configured) of the
computer you copied the storage area to, then change the value in the o_path column to be the path
to the specific storage area folder on that computer.
Caution: If the conversion of your database should fail for some reason, do not run DMSCONV on it a
second time, as this can cause further corruption of the database. Instead, after you have determined the
cause of the failure and found a solution, you will need to start the DMSCONV process over, using a fresh
backup copy of your database.

After you have completed a test upgrade, as well as a test of the new features, use the following
guidelines to upgrade your production environment to ProjectWise V8i (SELECTseries 4). Again, it is
recommended that you contact Bentley Professional Services to assist you in your upgrade.
General
1. Upgrading to ProjectWise V8i (SELECTseries 4) generally requires upgrading both server and client
modules.
2. Depending on the version you are upgrading from, you may still be able to use your older client with
the new server, or vice versa. The following table lists which versions of ProjectWise Explorer,
ProjectWise Administrator, ProjectWise Web Server and Web View Server, and ProjectWise Caching
Server will work with the ProjectWise Integration Server from this release, and conversely, which
versions of ProjectWise Integration Server will work with ProjectWise Explorer, ProjectWise
Administrator, ProjectWise Web Server and Web View Server, and ProjectWise Caching Server from
this release.
(X = supported, blank = not supported)
ProjectWis
e Explorer
V8i
(SELECTse
ries 4)
Refresh
(8.11.11.5
xx)
ProjectWise
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 4)
Refresh
(8.11.11.5
xx)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 4)
(8.11.11.1
11)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 3)
(8.11.9)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 2)
(8.11.7.4x
x)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 1)
(8.11.7.13
3)
336
ProjectWi
se
Integratio
n Server
V8i
(8.11.5)
ProjectWi
se
Integratio
n Server
pre-V8i
Upgrade Planning
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 4)
Refresh
(8.11.11.5
xx)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 4)
(8.11.11.1
11)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 3)
(8.11.9)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 2)
(8.11.7.4x
x)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 1)
(8.11.7.13
3)
ProjectWis
e Explorer
V8i
(SELECTse
ries 4)
(8.11.11.1
11)
ProjectWis
e Explorer
V8i
(SELECTse
ries 3)
(8.11.9)
ProjectWis
e Explorer
V8i
(SELECTse
ries 2)
(8.11.7.4x
x)
ProjectWis
e Explorer
V8i
(SELECTse
ries 1)
(8.11.7.13
3)
ProjectWis
e Explorer
V8i
ProjectWis
e Explorer
pre-V8i
ProjectWise
ProjectWi
se
Integratio
n Server
V8i
(8.11.5)
ProjectWi
se
Integratio
n Server
pre-V8i
337
Upgrade Planning
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 4)
Refresh
(8.11.11.5
xx)
ProjectWis
e
Administr
ator V8i
(SELECTse
ries 4)
Refresh
(8.11.11.5
xx)
ProjectWis
e
Administr
ator V8i
(SELECTse
ries 4)
(8.11.11.1
11)
ProjectWis
e
Administr
ator V8i
(SELECTse
ries 3)
(8.11.9)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 4)
(8.11.11.1
11)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 3)
(8.11.9)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 1)
(8.11.7.13
3)
ProjectWi
se
Integratio
n Server
V8i
(8.11.5)
ProjectWi
se
Integratio
n Server
pre-V8i
ProjectWis
e
Administr
ator V8i
(SELECTse
ries 2)
(8.11.7.4x
x)
ProjectWise
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 2)
(8.11.7.4x
x)
338
Upgrade Planning
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 4)
Refresh
(8.11.11.5
xx)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 4)
(8.11.11.1
11)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 3)
(8.11.9)
ProjectWis
e
Administr
ator V8i
(SELECTse
ries 1)
(8.11.7.13
3)
ProjectWi
se
Integratio
n Server
V8i
(8.11.5)
ProjectWi
se
Integratio
n Server
pre-V8i
ProjectWis
e
Administr
ator preV8i
ProjectWise
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 1)
(8.11.7.13
3)
X
ProjectWis
e
Administr
ator V8i
(8.11.5)
ProjectWis
e Web
Server and
Web View
Server V8i
(SELECTse
ries 4)
Refresh
(8.11.11.5
xx)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 2)
(8.11.7.4x
x)
339
Upgrade Planning
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 4)
Refresh
(8.11.11.5
xx)
ProjectWis
e Web
Server and
Web View
Server V8i
(SELECTse
ries 4)
(8.11.11.1
11)
ProjectWis
e Web
Server and
Web View
Server V8i
(SELECTse
ries 3)
(8.11.9)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 4)
(8.11.11.1
11)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 3)
(8.11.9)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 1)
(8.11.7.13
3)
ProjectWi
se
Integratio
n Server
V8i
(8.11.5)
ProjectWi
se
Integratio
n Server
pre-V8i
ProjectWis
e Web
Server and
Web View
Server V8i
(SELECTse
ries 2)
(8.11.7.4x
x)
ProjectWis
e Web
Server and
Web View
Server V8i
(SELECTse
ries 1)
(8.11.7.13
3)
ProjectWise
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 2)
(8.11.7.4x
x)
340
Upgrade Planning
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 4)
Refresh
(8.11.11.5
xx)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 4)
(8.11.11.1
11)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 3)
(8.11.9)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 2)
(8.11.7.4x
x)
ProjectWis
e Web
Server and
Web View
Server V8i
(8.11.5)
ProjectWis
e Caching
Server V8i
(SELECTse
ries 4)
Refresh
(8.11.11.5
xx)
ProjectWis
e Caching
Server V8i
(SELECTse
ries 4)
(8.11.11.1
11)
ProjectWis
e Caching
Server V8i
(SELECTse
ries 3)
(8.11.9)
ProjectWi
se
Integratio
n Server
V8i
(8.11.5)
ProjectWi
se
Integratio
n Server
pre-V8i
ProjectWis
e Caching
Server V8i
(SELECTse
ries 2)
(8.11.7.4x
x)
ProjectWise
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 1)
(8.11.7.13
3)
341
Upgrade Planning
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 4)
Refresh
(8.11.11.5
xx)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 4)
(8.11.11.1
11)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 3)
(8.11.9)
ProjectWis
e Caching
Server V8i
(SELECTse
ries 1)
(8.11.7.13
3)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 2)
(8.11.7.4x
x)
ProjectWi
se
Integratio
n Server
V8i
(SELECTs
eries 1)
(8.11.7.13
3)
ProjectWi
se
Integratio
n Server
V8i
(8.11.5)
ProjectWi
se
Integratio
n Server
pre-V8i
ProjectWis
e Caching
Server V8i
(8.11.5)
Note: In order to use ProjectWise Explorer V8i (SELECTseries 4) Refresh with ProjectWise
Integration Server V8i (SELECTseries 1), the Integration Server requires an updated DMSKRNL.EXE
file, build version 08.11.07.152. Please contact Bentley technical support for details.
3. Typically, all ProjectWise servers in a ProjectWise system must be of the same release version, and
should be upgraded to ProjectWise V8i (SELECTseries 4) Refresh at the same time. However you
may temporarily use your existing ProjectWise Caching Server(s) from ProjectWise V8i
(SELECTseries 4), V8i (SELECTseries 3), V8i (SELECTseries 2), or V8i (SELECTseries 1) against the
new Integration Server from ProjectWise V8i (SELECTseries 4) Refresh, until such time that a
ProjectWise Caching Server upgrade can be performed.
4. Except where a parallel installation is supported (see the next step), all ProjectWise modules on a
single computer must be of the same release version. For example, you cannot have some modules
from ProjectWise V8i (SELECTseries 4) Refresh and some modules from ProjectWise V8i
(SELECTseries 3) installed on the same computer. Rather, they must all be ProjectWise V8i
(SELECTseries 4) Refresh, or all ProjectWise V8i (SELECTseries 3), and so on.
5. A parallel installation is when two versions of the same program are installed and run on the same
computer. Note the following supported combinations:
ProjectWise Explorer V8i (SELECTseries 4) Refresh and ProjectWise Explorer V8 XM Edition
ProjectWise Administrator V8i (SELECTseries 4) Refresh and ProjectWise Administrator V8 XM
Edition
ProjectWise
342
Upgrade Planning
Precautions
1. Some upgrades, depending on the version you are upgrading from, require that you check in all
checked out documents before upgrading, to ensure the integrity of master/reference document
relationships. Exported documents are not affected and can remain exported during the upgrade.
ProjectWise V8i (8.11.5) introduced a file called file_name.fileinfo.xml, which gets created
locally upon check out of a master document. Because of this change, upgrading a pre-V8i version
ProjectWise database to ProjectWise V8i (SELECTseries 4) Refresh requires that you check in all
checked out documents having references, raster references, or link sets before upgrading.
2.
3.
4.
5.
6.
7.
ProjectWise V8i (SELECTseries 1) (8.11.7.1xx) introduced the creation of shapefile sets and raster
sets. Because of this change, upgrading a pre-V8i (SELECTseries 1) version ProjectWise database to
ProjectWise V8i (SELECTseries 4) Refresh requires that you check in all checked out DGN documents
having links to shapefiles and/or raster files (which have their own related files) before upgrading.
Back up your existing database. A complete cold backup should be made and verified using the
database vendor's recommended backup procedures.
Back up all server-side ProjectWise configuration files, including dmskrnl.cfg.
Ensure that your database software is still supported in ProjectWise V8i (SELECTseries 4) Refresh
(see the readme - readme_ProjectWise.chm). Note that the suggestions in this upgrade
planning document do not address the conversion between database types (for example, SQL Server
to Oracle conversions, or vice versa).
If there has been API-driven customization of your ProjectWise system, that customization will at a
minimum need to be recompiled to be binary compatible with ProjectWise V8i (SELECTseries 4)
Refresh. Installers will need to be updated to properly register the customizations on the new
ProjectWise V8i (SELECTseries 4) Refresh clients.
The administrative user performing the upgrade will need to have access to the top folder of the
datasource. If you are concerned about whether this user has access, you may want to turn off that
user's user setting, General - Use access control, before you begin your upgrade, then turn it back
on after upgrade is complete.
The following ProjectWise V8i (SELECTseries 4) Refresh installers can be used to automatically
upgrade an earlier version of the product to the current version, when the earlier version is
ProjectWise V8i or later:
ProjectWise Gateway Service
An automatic upgrade will uninstall the earlier version and then install the new version. Note that
you are not required to use the automatic upgrade feature; you can still use Add / Remove Programs
to manually uninstall the earlier version before installing the new version, if you prefer.
The ideal situation in which to use the automatic upgrade feature, is when one of the above modules
is the only module from ProjectWise V8i or later installed on the computer. If you have more than
one of the above modules from the same ProjectWise V8i or later version installed, you must
perform back-to-back upgrades of each module, as you cannot have modules from different
ProjectWise V8i versions installed and running on the same computer.
Note: To upgrade a module not listed above, you must use Add / Remove Programs to manually
uninstall the existing version before installing the new version. If you have a mix of modules installed
ProjectWise
343
Upgrade Planning
from the same V8i or later version (that is, some from the list above and some not), then it is
recommended that you do not use the automatic upgrade feature for the modules listed above, and
instead use Add / Remove Programs to uninstall all modules from that release version before you
install the new ones.
Note: If you have a ProjectWise V8i or later module from the list above installed next to a pre-V8i
version of the same module on the same computer, then you can still use the automatic upgrade
feature to automatically upgrade the ProjectWise V8i or later version of the module(s) listed above.
Suggested Migration Process

1. Conduct the necessary preparation and testing as recommended above.
2. On the servers to be upgraded, uninstall any existing ProjectWise modules in the following order:
ProjectWise Distribution Service Plug-in for ProjectWise InterPlot Server

ProjectWise Design Compare Utility
ProjectWise Publishing Gateway Service
ProjectWise InterPlot Server
ProjectWise User Synchronization Service
ProjectWise Integration Server or ProjectWise Caching Server or ProjectWise Gateway Service or
ProjectWise Indexing Service
ProjectWise Prerequisite Runtimes
ProjectWise Orchestration Framework Service
MicroStation (if installed for ProjectWise Orchestration Framework Service)
3. Install servers from this release as needed, per this Implementation Guide.
4. Stop the ProjectWise Integration Server V8i (SELECTseries 4) service.
5. Migrate configurations from your existing dmskrnl.cfg file to the current versions delivered
dmskrnl.cfg file.
Note the following new default installation location, for 64-bit servers:
C:\Program Files\Bentley\ProjectWise\Bin
6. In the Windows Registry, move all ProjectWise ODBC datasources from HKEY_LOCAL_MACHINE
\SOFTWARE\Wow6432Node\ODBC\ODBC.INI to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC
\ODBC.INI
7. Perform any necessary database product upgrades.
The upgrade process will drop and recreate all the ProjectWise product tables in the database.
Specifically, a copy of each tables data is created and the original database tables are then deleted.
Once this is done, new tables are created and the original data rows are inserted into the new tables.
ProjectWise
344
Upgrade Planning
This is to reconcile any minor inconsistencies that may exist in the database table structure (such as
minor differences in a column size, or a column declared as CHAR instead of VARCHAR, and so on).
Your database should have enough storage space to allow the upgrade process to copy the largest
table in the ProjectWise database. For instance, if you have one million documents in your database,
you should have at least enough storage in your database to allow one million document records to
be copied to a temporary table.
If you have created any custom database triggers or indexes on those tables, you will need to recreate them after conversion.
Updating The Database To Support Unicode INSTRUCTIONS FOR ORACLE USERS ONLY
By supporting Unicode, ProjectWise is better able to store and sort characters from many different
languages and character sets. To do this, the underlying database must also be set to support
Unicode. For SQL Server users, this is automatic and nothing needs to be done. For Oracle users, the
database used by ProjectWise must be converted to support Unicode. This means exporting all of the
data out of the old database, creating a new database with Unicode support, and importing all of the
data into this new database. These steps are accomplishing using Oracle tools.
General Procedure Updating databases to Unicode
Export data from existing database using database tools.

Create a new database using UTF8 or AL32UTF8 character sets
Import data into new database using database tools.
Upgrade the database table structure using the DMSCONV.EXE utility.
Connect to new database with ProjectWise Administrator and log in to complete the upgrade.
For Oracle users upgrading to Oracle 10g or 11g, at this point back up your existing database,
upgrade the Oracle installation, and migrate the database to Oracle 10g or 11g. Make sure you have
specified a valid Unicode character set for your new database. In Oracle 10g and 11g, both the
database character set and the national character set must be set to a Unicode character set (see
Setting Up the Main ProjectWise Database).
When creating your export from your old Oracle database, you must export the data using the active
database server NLS_LANG* settings. This is to prevent your default client NLS_LANG setting from
affecting the character set conversion during the export process.
For example, to create the backup from the existing database:
SQL> select * from nls_database_parameters;
ProjectWise
PARAMETER
VALUE
------------------------------
--------------------------------------------------
NLS_LANGUAGE
AMERICAN
NLS_TERRITORY
AMERICA
NLS_CURRENCY
NLS_ISO_CURRENCY
AMERICA
345
Upgrade Planning
NLS_NUMERIC_CHARACTERS
.,
NLS_CHARACTERSET
UTF8
NLS_CALENDAR
GREGORIAN
NLS_DATE_FORMAT
DD-MON-RR
NLS_DATE_LANGUAGE
AMERICAN
NLS_SORT
BINARY
NLS_TIME_FORMAT
HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT
DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT
HH.MI.SSXFF AM TZH:TZM
NLS_TIMESTAMP_TZ_FORMAT
DD-MON-RR HH.MI.SSXFF AM TZH:TZM
NLS_DUAL_CURRENCY
NLS_COMP
BINARY
NLS_NCHAR_CHARACTERSET
UTF8
NLS_RDBMS_VERSION
8.1.7.0.0
c:\> set NLS_LANG=AMERICAN_AMERICA.UTF8

c:\> exp userid=scott/tiger file=expdat.dmp
c:\> set NLS_LANG=
Next, import the database backup into your new 10g or 11g database using the target database's
NLS_LANG settings. Again, this is to prevent your default client NLS_LANG setting from affecting the
character set conversion during the import process.
ProjectWise
PARAMETER
VALUE
------------------------------
--------------------------------------------------
NLS_CSMIG_SCHEMA_VERSION
NLS_NCHAR_CHARACTERSET
UTF8
NLS_LANGUAGE
AMERICAN
NLS_TERRITORY
AMERICA
346
Upgrade Planning
NLS_CURRENCY
NLS_ISO_CURRENCY
AMERICA
NLS_NUMERIC_CHARACTERS
.,
NLS_CHARACTERSET
AL32UTF8
NLS_CALENDAR
GREGORIAN
NLS_DATE_FORMAT
DD-MON-RR
NLS_DATE_LANGUAGE
AMERICAN
NLS_SORT
BINARY
NLS_TIME_FORMAT
HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT
DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT
HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT
DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY
NLS_COMP
BINARY
NLS_LENGTH_SEMANTICS
BYTE
NLS_NCHAR_CONV_EXCP
FALSE
NLS_RDBMS_VERSION
10.2.0.2.0
c:\> set NLS_LANG=AMERICAN_AMERICA.AL32UTF8

c:\> imp userid=scott/tiger fromuser=scott touser=scott file=expdat.dmp
Import: Release 10.2.0.2.0 - Production on Wed Dec 13 10:22:30 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release
10.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Export file created by EXPORT:V08.01.07 via conventional
pathimport done in AL32UTF8 character set and UTF8 NCHAR character set
export client uses UTF8 character set (possible charset conversion)
. importing PROJECTWISE's objects into PROJECTWISE
. . importing table
"AA_DOCASSOC"
0 rows imported
ProjectWise
347
Upgrade Planning
. . importing table
.... etc...
"AA_RULE"
1 rows imported
Once this process is complete, the ProjectWise database can be upgraded.

8. Using ProjectWise's DMSCONV.EXE utility, update your datasources to make the necessary database
modifications for the new capabilities of ProjectWise V8i (SELECTseries 4).
Converting Database Table Structure Using DMSCONV.EXE

Converting existing ProjectWise datasources to work with ProjectWise V8i (SELECTseries 4) is done
using the DMSCONV.EXE command line utility (or DMSCONV, for short), which is delivered with the
ProjectWise Integration Server installation. DMSCONV will migrate the database schema of your
existing ProjectWise database to meet the requirements of the current version.
1. Before you start, update the database statistics to maximize database performance (consult your
database's documentation).
2. Stop the service for ProjectWise Integration Server V8i (SELECTseries 4) in the Services window.
3. Open a command prompt and navigate to the ...\ProjectWise\bin directory.
4. (Optional) Before converting the database, type DMSCONV and press <Enter>. This displays a list of
options you can use with DMSCONV.
5. To update the database schema, enter:
DMSCONV -d ODBC_datasourcename -u ODBC_username -p ODBC_password
This is the basic DMSCONV command, which is used to update the database schema. You can add
switches to the command as necessary, depending on what else you want DMSCONV to do, as
described in the following steps.
6. To also control how document MIME type information in the database will be updated, you can add
one of the following switches to the DMSCONV command:
Switch
Description
-mime
This will automatically perform the MIME type update.

For example:
DMSCONV -d ODBC_datasourcename -u
ODBC_username -p ODBC_password
-mime
-nomime
This will automatically skip the MIME type update for all
MIME types.
For example:
-nomime
ProjectWise
348
Upgrade Planning
Switch
Description
-skipmime
Used in conjunction with the -mime switch, this will

automatically skip the MIME type update for the specified
extensions.
For example:
-mime -skipmime "*.doc;*.xls;*.ppt"
Note: You can also run DMSCONV without entering any of the above MIME switches; if you do, you
will be prompted to update document MIME type information after the database structure is
upgraded. While a document MIME type update is required for proper functioning of ProjectWise V8i
(SELECTseries 4), this step may be deferred until later. If you use the -nomime switch during the
database upgrade, or if you do not enter any MIME switch and you select to skip the MIME type
update when prompted, make sure you perform a MIME type update soon after upgrading the
datasource, and before putting the datasource into production. (Consult ISOC RFC 2046 for more
information about MIME types.)
7. (Optional) The -notransaction switch is for SQL Server upgrades, and should only be used when
absolutely necessary. Using this option will disable the use of upgrade transactions. This may speed
up the upgrade and reduce transaction log usage, but is riskier because any failure will require
restoring your database from backup. Consult with Bentley Professional Services before using this
option.
8. (Optional) The -force-cursor-sharing switch is for Oracle upgrades, and should only be used
when absolutely necessary. This option was added to increase database performance in certain
configurations. Consult with Bentley Professional Services before using this option.
9. (Optional) The -nosatellites switch is for skipping the creation of sets in the database for
existing raster files and their sister files, and also various ESRI files (including shapefiles (SHP)) and
their related files.
10. (Optional) DMSCONV also provides the capability to import application association settings into the
updated datasource. Default application association settings are delivered in the appinfo.xml file
located in the ...\ProjectWise\bin directory, but you can define and import your own custom
application association settings if necessary. There are several command line switches that control
the import of these application association settings:
Switch
Description
-app
This imports the application association settings in the

delivered appinfo.xml file.
For example:
-app
You can import the appinfo.xml file as is, or edit the
application association settings in the file first, as needed,
and then run DMSCONV.
ProjectWise
349
Upgrade Planning
Switch
Description
This imports the XML file of your choice. Use this option if
appfile=<path_to_and_name_o you have created your own XML file with custom
f_xml_file>
application association settings.
For example:
-appfile=C:\import\myappsettings.xml
-appext=<0,1>
This is used in conjunction with either -app or -appfile

to control whether or not any previously defined
application extensions will be remapped to new
applications set in the XML file being imported. Enter a
value of 1 after the = character, if you want extensions
remapped; enter 0 if you do not want extensions
remapped.
For example:
-app -appext=1
The above example imports the application association
settings from the delivered appinfo.xml file and remaps
any existing extension associations in the datasource to the
extension associations defined in appinfo.xml.
Note: You are not required to import application association settings at the same time you are
upgrading the database table structure. If you prefer, you can first run DMSCONV without any of the
-app switches to only upgrade the database table structure, and then run DMSCONV again with the
appropriate -app switches to import the necessary application association settings.
11. Start the service for ProjectWise Integration Server V8i (SELECTseries 4) in the Services window.
12. Open ProjectWise Administrator, recreate the datasource entry for the converted database, then log
into this new datasource you will be prompted to complete the datasource conversion. This step
is required before you can log into the datasource using ProjectWise Explorer V8i (SELECTseries 4).
13. Test the operation of the new ProjectWise V8i (SELECTseries 4) production environment to ensure
that all functionality is operating normally.
14. If you delayed updating the MIME type information, use DMSCONV to update them now (see step 6
for details).
15. Conduct a complete backup of converted database and also a complete server backup of the new
ProjectWise V8i (SELECTseries 4) system to serve as a baseline recovery.
Caution: If the conversion of your database should fail for some reason, do not run DMSCONV on it a
second time, as this can cause further corruption of the database. Instead, after you have determined the
cause of the failure and found a solution, you will need to start the DMSCONV process over, using a fresh
backup copy of your database.
ProjectWise
350
Upgrade Planning
Areas for Review After Migration

1. As suggested above, a thorough review of client integration and overall operation is recommended
before an upgraded ProjectWise V8i (SELECTseries 4) Refresh installation is brought into
production use.
2. Review both datasource settings and user settings, as new options have been added to both of these
areas. It is also suggested to review the new dsmkrnl.cfg options as well as the new logging system
configuration. These settings are described in the ProjectWise Administrator help.
3. In ProjectWise V8i (SELECTseries 1), the Redline action was renamed to Markup. For
applications such as MicroStation, the Markup action is set by default to use Bentley Navigator,
which points to the application class name ProjectWise.Navigator.Application in the
Windows Registry. After upgrading to ProjectWise V8i (SELECTseries 4) Refresh from a preProjectWise V8i (SELECTseries 1) version, you may notice that some of your applications now have
two Markup actions. One is the new Markup action, and the other is the old Redline action which
got renamed to Markup during the upgrade. If you see two Markup actions after an upgrade, simply
delete the second Markup action (the old Redline action which got renamed to Markup) in
4. You must run a scan for references and link sets (in ProjectWise Explorer) after converting a pre-8.1
datasource to ProjectWise V8i (SELECTseries 4) Refresh. This is to allow for the population of
additional data into the ProjectWise database about reference file relationships for both
MicroStation and AutoCAD, and ensures the correct operation of reference data.
5. Some upgrades, depending on the version you are upgrading from, require that you check in all
checked out documents before upgrading, to ensure the integrity of master/reference document
relationships. If you did this, then your master/reference document relationships should be in tact
after upgrading. However, if you did not do this, and you find that some of your master/reference
document relationships are broken, then running a scan for references and link sets (in ProjectWise
Explorer) after upgrading will fix the broken relationships. Note that before you run the scan, you
must check in all checked out documents.
ProjectWise
351
Upgrade Planning
ProjectWise
352
Licensing
18
ProjectWise Licensing Overview

ProjectWise licensing is managed by SELECTserver, which tracks the usage of Right to Run licenses
reported by:

ProjectWise Web Server and Web View Server
Bentley i-model Composition Server for i-model (extension to ProjectWise Automation Service)
ProjectWise PDx Project Server
SELECTserver also tracks the usage of ProjectWise Passport licenses used by ProjectWise Explorer,
ProjectWise Administrator, Bentley Navigator, and ProjectWise Web Parts users who are logging in
through ProjectWise Web Server.
Note: SELECTserver does not track ProjectWise Web Parts users who log in through ProjectWise Web
View Server.
Note: On each computer that you have Bentley software installed, that computer can only report to one
SELECTserver. Therefore if you have multiple products on the same computer that require licensing
through SELECTserver, you only need to run the Product Activation Wizard once on that computer for
all the products that require licensing.
ProjectWise Integration Server and ProjectWise Caching Server

Licensing
In the Product Activation Wizard that launches at the end of your ProjectWise Integration Server and
ProjectWise Caching Server installations, you need to enter the name of a SELECTserver and that
server's Site Activation Key. The SELECTserver you specify will track the usage of the Right to Run
license reported by ProjectWise Integration Server and ProjectWise Caching Server, respectively.
You can also run the Product Activation Wizard any time after installation. For example if you skipped the
licensing step after installation, or if you need to change your existing licensing information.
ProjectWise Gateway Service Licensing

ProjectWise Gateway Service delivers a Product Activation Wizard, but you are not prompted to launch
it at the end of your ProjectWise Gateway Service installation because ProjectWise Gateway Service
does not require a license. However, if you enable the file caching feature in the ProjectWise Gateway
Service's dmskrnl.cfg file, then you will need to run the Product Activation Wizard on this computer
in order to specify a SELECTserver and Site Activation Key for this server to use. This is because you
ProjectWise
353
Licensing
Client-side Licensing for ProjectWise Explorer and ProjectWise Administrator Users
have essentially turned the ProjectWise Gateway Service into a ProjectWise Caching Server, which
requires a Right to Run license.
Note: Whenever launching the Product Activation Wizard on Windows Server 2008 or later, you need to
launch the wizard with elevated privileges (Run as Administrator).
Client-side Licensing for ProjectWise Explorer and ProjectWise

Administrator Users
By default, ProjectWise Passport license usage by ProjectWise Explorer and ProjectWise Administrator
users is automatically reported to SELECTserver through the ProjectWise Integration Server's
connection to SELECTserver, and there is nothing you need to configure.
However, if users need their ProjectWise Passport license usage tracked by a SELECTserver different
from the one being used by the ProjectWise Integration Server, then you must do the following:
1. On the ProjectWise Explorer or ProjectWise Administrator computer, launch the Product Activation
Wizard (ActivationWizard.exe, in the ...\Bentley\ProjectWise\bin directory) and
enter the name of another SELECTserver and that server's Site Activation Key.
2. Next, there is a user setting you must configure for each user who needs to use a SELECTserver that
is different from the one being used by the ProjectWise Integration Server. To do this, open
ProjectWise Administrator, go to the Users datasource node, right-click the user account you need to
change and select Properties. On the Settings tab, expand the Administrative category and set
Client Licensing to Activate and record usage through client's configured SELECT Server.
ProjectWise Web Server and Web View Server Licensing

In the Product Activation Wizard that launches at the end of your ProjectWise Web Server and Web
View Server installation, you need to enter the name of a SELECTserver and that server's Site
Activation Key. The SELECTserver you specify will track the usage of the Right to Run license reported
by ProjectWise Web Server and Web View Server.
Note: If you independently launch the Product Activation Wizard after ProjectWise Web Server and
Web View Server installation, then after entering your SELECTserver information, you must restart IIS.
Client-side Licensing for ProjectWise Web Parts Users

By default, ProjectWise Passport license usage by ProjectWise Web Parts users connecting to
ProjectWise Web Server is automatically reported to SELECTserver through the ProjectWise Integration
Server's connection to SELECTserver, and there is nothing you need to configure.
However, if you need to report your ProjectWise Web Parts users' ProjectWise Passport license usage to
a different SELECTserver, then you must do the following:
1. On the ProjectWise Web Server computer, launch the Product Activation Wizard and enter the name
of a SELECTserver and that server's Site Activation Key.
ProjectWise
354
Licensing
ProjectWise Automation Service Licensing
2. Then in ProjectWise, log in to your datasource and go to the Users datasource node. For each
ProjectWise Web Parts user, right-click the user account and select Properties. On the Settings tab,
expand the Administrative category and set Client Licensing to Activate and record usage
through client's configured SELECT Server.
ProjectWise Automation Service Licensing

ProjectWise Automation Service itself does not require a license, but you do need a license if you plan to
install the Bentley i-model Composition Server for i-model extension. Therefore if you enable the
Bentley i-model Composition Server for i-model extension during ProjectWise Automation Service
installation, you will be prompted to launch the Product Activation Wizard at the end of your
installation.
In the Product Activation Wizard, you need to enter the name of a SELECTserver and that server's Site
Activation Key. The SELECTserver you specify will track the usage of the Right to Run license reported
by ProjectWise Automation Service.
Launching the Product Activation Wizard

The Product Activation Wizard can be launched automatically after installation of the following
modules:

ProjectWise Web Server and Web View Server
ProjectWise Automation Service with Bentley i-model Composition Server for i-model extension
enabled
You can also run the Product Activation Wizard any time after installation by launching the
ActivationWizard.exe file, or by first launching the License Management Tool
(LicenseTool.exe) and then selecting Tools > Product Activation Wizard.
The ActivationWizard.exe and LicenseTool.exe files are located under:
...\Bentley\ProjectWise\bin
for ProjectWise Integration Server, ProjectWise

Caching Server, and ProjectWise Automation
Service
...\Bentley\ProjectWise\Web\Bin
for ProjectWise Web Server and Web View Server
Because of certain access control restrictions to the Windows Registry in Windows Server 2008 and
later, the Product Activation Wizard must be launched with elevated privileges. This can be done by
logging in to the computer with the Administrator account and then launching
ActivationWizard.exe or LicenseTool.exe, or by right-clicking ActivationWizard.exe or
LicenseTool.exe and selecting Run as Administrator.
ProjectWise
355
Licensing
Launching the Product Activation Wizard
If the Product Activation Wizard is not launched with elevated privileges, the Product Activation Wizard
will add the licensing information to the HKEY_CURRENT_USER section of the Registry instead of
HKEY_LOCAL_MACHINE. When the server looks for and cannot find the licensing information under
HKEY_LOCAL_MACHINE, the server enters 30-day countdown mode. After the 30-day countdown
mode expires, the server enters 4-hour evaluation mode. You cannot fix the problem simply by
rerunning the Product Activation Wizard, because the Product Activation Wizard will find a valid
licensing configuration under HKEY_CURRENT_USER and therefore will not move the licensing
information to location it needs to be in.
To correct the issue if it occurs:
1. Launch the Windows Registry Editor (regedit.exe) application with elevated privileges. This can
be done by logging in to the computer with the Administrator account and launching regedit.exe,
or by right-clicking regedit.exe and selecting Run as Administrator.
2. In the Registry Editor, navigate to the HKEY_CURRENT_USER\Software\Bentley registry node,
then delete the Licensing registry key and all its subkeys.
3. Close the Registry Editor.
4. Launch the Product Activation Wizard with elevated privileges as described above, then reenter your
SELECTserver activation information.
ProjectWise
356

PW Implementation Guide

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

PW Implementation Guide

Încărcat de

Drepturi de autor:

Formate disponibile

ProjectWise

Restricted Rights Legends

Chapter 2: Database Setup .......................................................................................67

Chapter 3: ProjectWise Integration Server Configuration .....................................75

Chapter 4: ProjectWise User Synchronization Service Configuration ...............129

Chapter 5: ProjectWise Caching Server Configuration ........................................135

To Install ProjectWise Caching Server .........................................................................................................................................136

Chapter 6: ProjectWise Gateway Service Configuration ......................................141

Chapter 7: ProjectWise Indexing Service Configuration ......................................147

Chapter 8: ProjectWise Explorer Configuration ....................................................153

Chapter 9: ProjectWise Web Server Configuration ..............................................171

To Create a Delegate User in ProjectWise Administrator .....................................................................................188

To Configure the Word and Excel Providers with Ghostscript ...........................................................................229

Chapter 11: ProjectWise Automation Service Configuration ..............................249

Chapter 12: ProjectWise Distribution Service Configuration ..............................269

To Install ProjectWise Distribution Service Administrator .................................................................................285

Chapter 13: ProjectWise web services Configuration ..........................................291

Chapter 14: Language Packs ..................................................................................295

Chapter 15: Configuring the ProjectWise Network ...............................................299

Chapter 16: Operational Procedures ......................................................................321

Incremental Restore ..............................................................................................................................................................322

Chapter 17: Upgrade Planning ................................................................................335

Chapter 18: Licensing ..............................................................................................353

This page intentionally left blank

New in ProjectWise V8i (SELECTseries 4) Refresh

ProjectWise Explorer Enhancements

Office Integration Enhancements

ProjectWise Administrator Enhancements

Updated Attribute Exchange Example Files for Microsoft Office 2003

New in ProjectWise V8i (SELECTseries 4)

ProjectWise Explorer Enhancements

Reference Version Locking

Document and File Name Synchronization

Create Document dialog (Document > New > Document)

MicroStation V8i (SELECTseries 3)

Point Clouds Dialog Integration

ProjectWise Administrator Enhancements

New Datasource Settings

When on (the default), an owner of a project, folder, or document always has

Force file name to

Lock flat set

New User Settings

Administrative Display Access

New Audit Trail Logging Options

Document - Log Revit

Updated Datasource Template

ProjectWise Web Parts Enhancements

Bentley i-model Composition Server for PDF

ProjectWise Desktop and Server Applications for the Mobile Workflow

New in ProjectWise V8i (SELECTseries 3)

ProjectWise Explorer Enhancements

Group and User List Management Enhancements

MicroStation No Longer Required for Reference Scanning

New Storage Area Disk Usage Information

Display of Nested References in the Dependency Viewer

64-bit Components Delivered for Integration with 64-bit Autodesk Products

AutoCAD 2011, 2010

AutoCAD MEP 2011

ProjectWise Administrator Enhancements

Group and User List Management Enhancements

Audit Trail Enhancements

New Datasource Statistics

New User Settings