Introduction

One of the benefits/features of ProjectWise is great flexibility in the system architecture, due in part to its three-tier architecture, which separates the data from the applications. It is also due to careful programming that allows even the server application software to be split seamlessly over several servers. In particular, it is possible to separate the components that serve the Web-based clients from those that serve the ProjectWise Explorer Client. 

Installation and Configuration

Server components should be installed on the two servers as described in the Component Location tables below. In the split Application and Web Server scenario, the Web Server components act like a Windows Client to the Application Server. With this in mind, if the Web Server cannot reach the Application Server with its broadcast request for available datasources, then the Connection Server needs to be installed on the Web/Publishing Server. TCP Port 5800 needs to be opened between the Application Server and the Web/Publishing Server for File Transfer.

Component Location

Application Server
Database Server
ODBC datasource
ProjectWise Application Server

Web/Publishing Server
Internet Information Services (IIS)
Java Runtime Environment (JRE)
JRun Professional
Bentley Publisher
ProjectWise Web Server
ProjectWise Publishing Gateway
ProjectWise Document Publisher (Optional)
ProjectWise MarkUp for the Web (Optional)
Connection Server (only needed if there is a router/firewall between the Application Server and the Web Server and the File Transfer Server is not already installed)

Possible Uses

There are three benefits to a Distributed Server Configuration:

1. Performance - By removing the memory and processing requirements of the Web and publishing components, the Application Server can be scaled smaller to maintain a high performance for the ProjectWise Explorer users.
2. Security - Most organizations would like to maintain the Application Server inside their Firewall and the Web Server in an area of the network that is accessible to the Internet.
3. Allow multiple Web/publishing servers - With this configuration it is possible to maintain a single, central Application Server and push the Web Servers out to remote offices. This is especially useful in the scenario where each remote office maintains its own ProjectWise File Transfer Servers. This reduces the amount of network traffic because there is no longer a need to transfer the source files from the Remote File Server to a central Web/Publishing Server. In this scenario the files are stored and published in the remote office.

See Also

Product TechNotes and FAQs

ProjectWise TechNotes And FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Overview

This document will provide an overview on how ProjectWise Caching works along with providing you step by step instructions on how to configure your ProjectWise Caching Server. It will also provide examples from a simple setup to a complex setup of how caching can be configured. The dmskrnl.cfg file provides detailed information on the [Gateway] & [Routing] sections and should be read for detailed information.

**PLEASE NOTE: Name change of service

ProjectWise V8 2004 Edition: File Transfer Server (FTS)

ProjectWise V8XM & V8i Edition: Caching Server

**PLEASE NOTE: It is not necessary to install ProjectWise Caching Server on the Integration Server or the ProjectWise Gateway Service. The Integration Server and the Gateway Service have the caching component already in there modules. Once you enable caching via the dmskrnl.cfg file, the Server will allow caching.

 A few terminologies that will be used in this tech note:

DMZ: Demilitarized zone. Section of an organization's network topology that is outside the company firewall.

UDP: User Datagram Protocol.

Caching: The temporary storage of files

Setup:

 In the examples below, all configurations have been made on Windows 2003 Servers.

There are three sections in the c:\Program Files\Bentley\ProjectWise\Bin\dmskrnl.cfg file that are very important to understand. Most of the configuration for caching will be done in this file.

FileTransferSrv=1

This variable is uncommented by default on the ProjectWise Caching Server.  It tells the ProjectWise service that it is configured to be a Caching Server. Enabling this configuration on an Integration Server will have negative effects such as not being able to see a datasource or completely deactivating the Integration Server's functionality.

ConnectionSrv=1

This variable is uncommented by default on the ProjectWise Gateway Server.   It tells the ProjectWise service that it is to act as a gateway for users to connect through to the Integration Server. If you are setting up caching on a Gateway\Connection server then this needs to be uncommented along with the FileTransferSrv=1

****************** 
[ServerNameResolution]

This section is newly added in SelectSeries1 (08.11.07.xx and above) If your Gateway/Caching server is publically accessible. This configuration is configured with the first binding NIC to a externally accessible FQDN. 

**In previous versions prior to SelectSeries1 this configuration was done under the Clustering Section.

******************* 

[NameResolution]

Provides name resolution for the Servers IP

[Cache]

This section in the dmskrnl file enables the temporary caching. In the example below each part of the line has be to uncommented by removing the ‘;' semi-colon. The description to each setting is to the right of each variable.

enabled = Can be set to true or false               ; true - enables caching, false -disables caching.(Mandatory)

servers=ipad1:port, ipad2:port                        ;Specifies which Server it will cache. If this section is left blank everything is cached from all servers. (Optional)

storagePath=                                                        ;Path  to where all cached files will be stored(Mandatory)

limit=xxx                                                               ;xxx is amount of disk space that can be taken up in the path where the cached files are stored. (In MB) The threshold for the cached folder is 80%, when the folder is 80% full files start to delete with the least modified dated first.   (Optional)

Examples from the dmskrnl

[Cache] 
;Enabled=true 
;Servers=192.168.32.129:5800 
;StoragePath=d:\cacheroot
;Limit=500

[Gateway]

The configurations under this section are for the ProjectWise Explorer (Client) application. The gateway section gives the Client directions on how to connect to make the request from the remote Server where the file lives.

This section does not give a route but tells the Client (s) the first hop in the route.

The best way to think of this section is Storage Area (where the files lives) = Caching Server (where the file will be taken to)

For example:

endpoint=gateway1

endpoint = is where the files reside usually storage area server
gateway1= is where the request from the client is going to get its gateway information from first.             

If the Client is making a request that is not on the same subnet as the Integration Server or the Gateway, you will need to tell the Client where it is getting its gateway information (directions) from. On the machine where ProjectWise Explorer is installed: Navigate to the Control Panel and open the ProjectWise Network Configuration Settings (In V8i it is called ProjectWise V8i Network Configuration Settings). Under the DNS Services tab point to the server where the client will be getting it's Gateway Information from. (Figure 1.)
(Figure 1.) 
 

[Routing] 
This section is telling the Caching Server where the next hop is to the Storage Area Server. This section is strictly for Server routing. All that is defined is the Server IP or Name and the port number.

Example from the dmskrnl:

Endpoint = 5800

ProjectWise Integration Server:
Storage Area:

When setting up caching it is recommended to use fully qualified domain names (FQDN).

**PLEASE NOTE: In V8i it is mandatory to use FQDN

If short names are used, it is necessary to use short names for ProjectWise Storage Areas as well. In ProjectWise Administrator under the Storage Area make sure the Computer Name is not an IP address if short names are used in the dmskrnl.cfg files (figure 2.)

(figure 2.) 
 

Examples of Caching Setups

Example 1: 
Simple caching between two locations.

See Figure 3 for the network configuration. Location one has an Integration Server called ServerA and Location 2 has an Integration Server called ServerB.  Both Servers are also acting as Caching Servers.

In this scenario the Clients on the ServerA side request a file from ProjectWise that is stored on the ServerB side.  However, if the file is already cached on ServerA, the Client will retrieve the file from ServerA. If it is not already cached, the client will retrieve the file from ServerB and it will be cached on ServerA.  The reverse would happen for Clients on the ServerB side,  When a client from ServerB side accesses a  file that lives on ServerA side, it will first try to get it from the cache on ServerB and if not found, retrieve it from ServerA and cache it on ServerB. 

(Figure 3.)

 

Example 2: 
In this example the Clients connect to the Integration Server through a Gateway Server and cache files on the Gateway Server.
In this scenario, the Clients in Location 1 are requesting files from ProjectWise that are located on ServerA in Location 2. When the Client makes a request if the file is not already cached on Gateway1, Gateway1 will make a request from ServerA in Location 2, retrieve the file back in to the cached folder on Gateway1 and then forward it to the Client. If the file already is in the cached folder on Gateway1, then the Client will retrieve the file from the Gateway1 folder. Figure 4 shows the configuration needed for this scenario.

(Figure 4.)

Example 3: 
In this scenario, all Clients are in different locations and have a storage area for their data stored locally on each of their Caching Servers. However, all users are caching files from all the other locations to their local Caching Server's cache folder. The company wanted to have all Clients pass through the Integration Server, however you do not need to.
Figure 5 shows the communication path for this configuration.
Following the Client request (red line), the user requests files via ProjectWise Explorer that are located on the Caching2 storage area. The request goes first to Caching1 server which then makes a request to INTServer1 on behalf of the Client. The ProjectWise Integration Server then consults the database for the location of the file.
Next, following the blue line, the request is acknowledged by the database on where the file location is, and then the request is sent back to the Client through the Caching1 Server.
The Client now knows where the file lives and sends a request back to the Caching1 server (Orange line) which then is routed to the (INTServer1) to the storage area location Caching2.
Finally, following the (green line) which brings the file via the INTServer1 server back to theCaching1 cache folder completing the request, with the file sent to the user.(Figure 5.)

(Figure 5.) 
 

Troubleshooting:

ProjectWise communicates on port 5800. 

**PLEASE NOTE: When communicating across different networks and through firewalls it is important to make sure port 5800 is open bidirectional to each ProjectWise server.

The following tools can be used for checking ProjectWise and network connectivity

**PLEASE NOTE:  If the router/firewall is blocking ping then these methods will not show accurate information.

A) ProjectWise Windows Socket Analyzer:

The ProjectWise Windows Socket Analyzer is installed when you install ProjectWise Explorer.

1. Start > All Programs > Bentley > ProjectWise > Tools > Users Tools
2. Double click on 'Windows Socket Analyzer'
3. Keep everything default until you get to 'Remote Host' (Type in the Name of the server you are going to communicate with) Click Next.

• Address: Will show the IP address of the remote host; Click Next.
• Local Host: information & Address: local host IP address will display; Click Next
• If the Local Server is able to communicate with the Remote Server via port 5800 you will get a message stating, "'Connection to remote host established and closed successfully"
• If you get an Error [60004] Invalid data or ' '; you will have to check with your network team and make sure port 5800 is open for bi-directional communication.

B) TELNET TO PORT 5800:

1. Go to Start > Run > type CMD 
2. In the DOS prompt type telnet 5800
a. If it is successful it will show Telnet on the top left window 
b. If it is not successful it will show ‘Connecting To ...Could not open connection to the host, on port 5800: Connect failed'

C) PWPING:

A command line tool delivered with ProjectWise that lets you run a network trace that reads the configurations set in the ProjectWise network control panel, which in turn reads the routing and gateway sections in the dmskrnl.cfg file.

1. Navigate in to C:\Program Files\Bentley\ProjectWise\bin and open file pwping.log.xml in notepad
2. Change the <priority value=>  to ‘all' and save the pwping.log.xml

i.e. change the "debug" to "all" 
<root>
<priority value="debug" />
<appender-ref ref="RollingFileAppender" />
</root>
</log4j:configuration>

3. In the MS-DOS prompt change directory to C:\Program Files\Bentley\ProjectWise\bin
4. Type pwping endpoint server name (Figure 6.)

(Figure 6.)

Usage: pwping [-d display-name] [-h hops] [-n count] [-t timeout]
Options:
-d display-name Display name of the endpoint datasource to trace route
to; name will be resolved via normal ProjectWise DNS.
If this switch is specified, the target_name command
argument must be omitted.

-h hops Maximum number of servers to transit on the way.
Defaults to the end of the route.

-n count Number of ping requests to send between hops.
Defaults to 1.

-t timeout Timeout in milliseconds to wait for each reply.
Defaults to 5000ms.

-c Display caching configuration information1.

• A successful pwping shows 1 hop from a Gateway Server to the Integration Server

pwping: INFO  - Tracing route to host '<HOSTNAME>'
pwping: INFO  - Hop: 1  Host: <HOSTNAME>  Address: 111.11.11.1  PW Version: 08.11.05.37 AvgTime: <1ms  AvgTtl: 128

• A route that is mis-configured in the dmskrnl.cfg file under the gateway and routing section will result in information from the pwping that can guide you to fix the configuration. An example of an pwping that has mis-configuration in the dmskrnl.cfg file is below.

pwping: INFO  - Tracing route to host ‘<HOSTNAME>'
pwping: ERROR - Error 32768 "failed to trace route" at func: wmain line: 321

5. After you run a few reproducible errors or unsuccessful caching request , your log file will be located in C:\Documents and Settings\All Users\Application Data\Bentley\Logs

If you need assistance TSG can help. When contacting Support please have these items ready for review.

 

**PLEASE NOTE: (These files are mandatory for support)

1. Topography with ALL Servers that are being used. 
        a. Internal IP address
        b. External IP address
        c. Name resolution

2. Dmskrnl.cfg files from ALL Servers
        a. Integration Server
        b. Caching Server
        c. Gateway Server

See Also

Product TechNotes and FAQs

External Links

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

NAS = Network Attached Storage

An NAS device is typically a dedicated, inexpensive, storage device that can be placed on a network for sharing files. NAS devices are optimized to stand alone and serve specific storage needs. They generally have their own operating systems, integrated hardware, and software. Normally they run some flavor of UNIX and have a simple interface used for uploading or downloading files.

The following is a description of a technical issue that may be encountered when assigning a Microsoft network mapped drive to a ProjectWise Caching Server storage area:

Additional information

ProjectWise has historically allowed the administrator to configure storage areas for which the physical storage resides on a non-local resource.  Typically, a share is created on a machine that has large capacity disk storage, such as a NAS, SAN, or a separate server with an attached RAID.  On the machine hosting the ProjectWise Caching Server application, a local drive letter for the Windows service account under which the ProjectWise Caching Server executes is then mapped to the remote share.

Due to how Windows historically managed drive mappings, once the drive letter mapping was created for the service account user, that drive mapping was available to any application executing in the context of that service account.

Change in behavior

As of Microsoft Windows 2003 Server, this is no longer possible. Windows Server 2003 now isolates mapped drive letters to the specific login instance of the Windows account that created the mapping.  This means that although an interactive login of the service account may allow mapping of the drive, that mapping will not be visible to subsequent interactive and non-interactive logins of that same account.

(See Microsoft Knowledge Base article 180362 http://support.microsoft.com/?kbid=180362)

Recommendations

It is now recommended that all storage area mappings to remote disk resources be performed using UNC paths.  For instance, given a share file://fileserver/share/pw_storage, mapped to a local drive letter, "G:", identified by ProjectWise storage area name "Storage1", the previous behavior was to associate the Storage Area name "Storage1" to drive "G:". The new recommendation is to map the UNC directly to the storage area.

Examples:

Previous configuration using mapped drive "G:" on ProjectWise Caching Server "pwstor1":

Recommended new configuration using a UNC network share file://fileserver/share/pw_storage :

See Also

Product TechNotes and FAQs

ProjectWise TechNotes And FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Concept

The ProjectWise Gateway Server was developed to:

• Improve scalability in large networks 
• Improve flexibility in different network situations
• Improve performance when combined with Temporary Caching

A Gateway Server is a ProjectWise Server that users connect through to get to other ProjectWise Servers. This Server can be used to publish DataSource information from one or more Integration Servers and provide routes to one or more ProjectWise Servers.

The idea is that you can put Gateway Servers around your network rather than building your network around ProjectWise. For example you could put a Gateway Server in your DMZ to allow internet based users to connect to ProjectWise without exposing your Integration Server directly to the internet. You could setup Gateway Servers in your remote offices so all your users connect to a local Server, then that Server connects back to your main office. If you deal with several different Integration Servers in several different locations you can configure your Clients to point at one local Gateway Server. That Gateway Server would publish the Datasources from the different Integration Servers and make the connections for the users.

• It is important to note that this document is focused on Gateway Servers specify, however, ProjectWise Caching and Integration Servers can also function as gateways to route ProjectWise traffic. Most of the concepts presented here can apply directly to the other Servers.

How it works

When a Client starts, it looks at its ProjectWise Network Control panel to see if UDP is enabled and if it is pointing at any Servers on the DNS Services and Datasource Listing tabs. DNS Services is where the Gateway Server data is delivered to the client. The Client will poll any Servers listed on both of these tabs and any found via UDP (if UDP is not disabled) to download the [NameResolution], [Gateway] and [DB{x}] sections of the DMSKRNL.

With this data downloaded the Client displays the Datasource list and waits for the user to make a connection to a Server. Each time the client makes a connection to a server (be it to login or download a file) the Client looks though its DNS cache which includes anything delivered from the [NameResolution] section. The Client then looks through the Gateway list for gateways or ‘non-direct paths’ to the Server. By default the Client will try to make a direct connection to a Server, however if it finds a gateway entry for a Server it will route its traffic through that Gateway.

When the Client looks through its gateway list, it looks for an exact match between the Server the user is trying to access and an item in the list. IE FQDN = FQDN (fully qualified domain name), shortname = shortname. A FQDN will not equal a shortname so don’t mix and match. If it does not find an exact match then the Client will make a direct connection to the Server.

Mixing shortnames and FQDNs is the number one reason gateways / temporary caching doesn’t work for users.

• There are a few places in the newer versions where this doesn’t hold true (shortname will = a FQDN) but it’s still a bad idea to mix the two. Take the time to make your configuration consistent.

When a user tries to download a file the Client requests the storage location from the Integration Server; Storage Area server name and file path. The Storage Area Server name that the Client gets is the one entered in PW Admin for the Storage Area. So if you setup [gateway] entries for any Servers hosting storage areas you need to match the endpoint name to the name shown as the Storage Area server name in PW Admin. If you find you have a mix of name types (shortnames, FQDNs, IP addresses) you can always change the names in PW Admin to make things consistent.

How It’s Configured

To start we will focus on setting up the gateway configuration, we will look at Publishing DataSources second and Temporary caching third. Throughout setting up your Gateway Server you will need to provide the names of other Servers. You should always use FQDN if your network supports it. Almost all networks do support FQDN, your IT group should be able to help with this. No matter what you do, stay consistent as this will cut down on confusion later. If you start with FQDN’s stay FQDN, if you start with shortnames stay with shortnames.

• Bentley strongly recommends the use of FQDN names throughout your ProjectWise Implementation. 

Gateway Configuration

Depending on the version of ProjectWise you have there are 3 or 4 different sections of the DMSKrnl.CFG that you need to configure for a Gateway Server.

• In SS1 and later [Server Name Resolution] is read and used ONLY by the Server, [Name Resolution] is read and used ONLY by the Client
• Pre SS1 the [NameResolution] section is used by both the Server and the Client equally
• The [Gateway] section is ONLY used by the Client to find a gateway to a given Server. 
• The [Routing] section is ONLY used by the Server for Server to Server routing

The [Name Resolution] and [Server Name Resolution] section provides Name Resolution much in the same way network DNS does however it is specifically for ProjectWise. This should not be used as a replacement for DNS but rather as a helper. Most of the time you do not need to populate the [Name Resolution] or [Server Name Resolution] at all as Windows will use network DNS to resolve everything. You also do not need to add entries in the [Name Resolution] section for servers the Client will be using the gateway to access. It really doesn’t matter to the Client what the IP address of your Integration Server is if it will always use the Gateway Server to connect to it.

The [Gateway] section is only used by the Client and provides first hop information on how to connect to a given endpoint. You only need to tell the Client what Gateway Server to start with for any endpoint it needs to connect to. It doesn’t matter how may hops there are along the way, that’s handled by the [Routing] section.

The [Routing] section is only used by the Server and helps the Server determine its next hop and what port to use for that hop. For example, if a Gateway Server (we’ll call it gatewayA) is providing access to an Integration Server (we’ll call it int-server). If there are no other ProjectWise Servers in-between and it will use port 5800 then the route entry would look like “int-server=5800” (without the “”). If however there is another ProjectWise Server in-between (we’ll call it gatewayB), you would need to list that as a next hop like this, “int-server=5800,gatewayB” (without the “”). In this example we are telling ProjectWise to connect to int-server using port 5800 and direct the traffic through GatewayB. GatewayB could be configured to then connect directly to the Integration Server or through another Gateway Server but none of that matters to gatewayA, gatewayA just need to know what the next hop is.

• Please note: V8i and later internet accessible Gateway Servers: When a request is sent to any ProjectWise Server, the Server looks at who the request was sent to and what its name is based on how Windows is configured. If its name matches the name the user requested then it answers the request. If the names do not match it will look for a route to the Server you requested in the [Routing] section.

When a Server is on the internet its real name and its internet name often do not match. For example, the Server’s Windows name may be PWDMZ however on the internet you may have the external FQDN PW.COMPANY.COM set to resolve to the ProjectWise Gateway. This leads to a situation where the gateway server returns errors to the client because it doesn’t know it should be responding to requests for PW.COMPANY.COM.

• Please note: take the time to get an external FQDN for your internet facing Servers, configuring your Clients to point at the public IP address can create several different problems and makes the Server configuration much more complicated.

For Pre-SS1, the best way to deal with this was to “rebrand” the Server using the external FQDN. Under the [TeamMate] section in the DMSKrnl.cfg there are 2 configuration variables, ServerName= and ServerIPAddress=. This is commonly referred to the clustering configuration section (or clustering section) as it is used when you want to set ProjectWise up in a cluster. What these keys do is override the name and IP address that the Server thinks belongs to it and allows us to give a new identity to the Server. You would set the ServerName equal to the externally FQDN and the ServerIPAddress equal to the public IP address. You must also make an entry in the [Name Resolution] ( [Server Name Resolution] for SS1 and later) section for publicIP=FQDN. Once this is done and you restart the service the server will assume a new identity.

For SS1 and later the above still works, however we have a new option that can provide some more flexibility. In the [Server Name Resolution] section we can set an alias for the Server by setting Server bind address = alternate name, IE 192.168.0.100 = PW.COMPANY.COM. With the clustering section you can only give the Server one alternate name but with the Server name resolution section you can give as many as you need.

• Please note: The Server bind address can be tricky, when ProjectWise starts on the Server it ‘binds’ or attaches to the first network card it finds on the system and notes the primary IP address for the card as ProjectWise’s local address. If you have more than one network card on your system ProjectWise will not necessarily be bound to the NIC you might want it to. Also be aware that some system changes can change the binding order and the next time ProjectWise starts it will pick a new local address.

The binding order on each system is set on the “Network Connections” screen from the windows control panel. How you get to this screen depends on your version of windows, a quick search on your favorite engine should provide the correct steps. Once there you need to click on the ‘Advanced’ menu (on server 2008 and later systems pressing the ALT key will display the menus) and click ‘Advanced Settings’. The top frame on the screen displays the current binding order, to change the order click on an adapter and use the green arrows to move it up or down. When done press OK and restart the ProjectWise Service for the change to take effect.

In the example below you can see that Local Area Connection 3 is my primary NIC in the binding order. The IP address of this NIC is what ProjectWise will use as its local Address.

There’s one more trick to know when dealing with the bind address and that is that ProjectWise provides a way to force the address you can bind to. If you force the bind address the binding order of the NICs is no longer important. Under the [Broadcast] and [Listener] sections of the DMSKrnl.cfg there is a ‘BindAddress’ and a ‘BindAddressIPv6’ that let you set the exact address ProjectWise binds to. If you’re not using IPv6, just ignore the ‘BindAddressIPv6’ line.

If you force the binding order however there are a few things to keep in mind. If the IP address of the system ever changes the ‘BindAddress’ will have to be update or the service will not start. When ProjectWise binds on its own it will respond to requests that come in on any NIC to any IP address. If you force the binding order you are telling ProjectWise to ONLY listen to requests on that address. If you have more than one address on that NIC or more than one NIC users will use to talk with ProjectWise that traffic will be ignored. If you are using a NAT firewall requests sent to the public address that map to the server will work if you use the ‘BindAddress’ as NAT will translate the requests to the servers privet address.

There’s one last point to keep in mind for internet facing gateway servers when you are not using the clustering section. When a client requests the DataSourse listing and DNS services information from any ProjectWise server, the server tells it its real name and IP address as part of the response. The client adds this information to its DNS cache and uses it for lookups later. If the server’s real name and external FQDN do not match there’s nothing to worry about. If however the serve’s real name and FQDN do match and ProjectWise is bound to an ip address other than the one the user should use to connect to the server (private ip address) you’re client will not work. This is because the client will use the ip address that the server gave it rather than the one it got from windows DNS. The solution to this is to make sure the names do not overlap.

With these sections configured you’re Gateway should be up and running.

This is an example config from an SS3 gateway server setup as an internet facing gateway. The external FQDN for this server is pw.company.com. The comments in the file have been stripped for space but it is recommended to leave them in your file as they provide an handy reference when you are making changes.

[ServerNameResolution}
192.168.0.100=pw.company.com

[NameResolution}
;nothing for the client

[Gateway]
storageA.company.local=pw.company.com
storageB.company.local=pw.company.com
storageC.company.local=pw.company.com
int-server.company.local=pw.company.com

[Routing]
storageA.company.local=5800
storageB.company.local=5800
storageC.company.local=5800
int-server.company.local=5800,GatewayX.company.local

Publishing Datasources Configuration

To publish a Datasource we build upon the above configuration by first looking in the [team mate] section of DMSKrnl.cfg and finding ‘Databases=’. You must have an entry on this line for each Datasource you are going to configure below. For example, if you are going to setup three Datasources the line would look like this ‘Databases=db0,db1,db2’. If you are going to use ‘DSServer=1’ (well talk about that below) you only need one ‘db’ line for each a DSServer entry no matter how many Datasources that will return. Forgetting about the ‘Database=’ line is the number one reason people have trouble publishing Datasources.

Now we jump to the very bottom of the DMSKrnl.cfg, this is where each Datasource the Gateway will publish is setup. There are two ways of add Datasources to the list to be published. First is by listing each Datasource individually, the second is by using DSServer.

The individual list way of publishing DataSources only publishes the DataSources you have set in your list. This list can include links to as many different DataSources on as many different servers as needed. To individually list the DataSources you add the following 4 lines to the config for each DataSource you want to list.

[db{x}]
Description=<"Real" Datasource name on the Integration Server>
DisplayName=
Server= (can not be a non-integration server)

The easiest way to get started is to copy the entries from your integration server and edit out what you don’t need. {x} would become the number of the DataSource starting at 0 and incrementing by one for each entry you make. IE [db0] [db1] [db3] etc. Information listed this way is delivered via the DataSource Listing tab in the PW Network Control Panel.

For Example

[db0]
Description=MainDatasource
DisplayName=Main Datasource for Design Documents
Server=int-server.company.local

The DSServer way of publishing DataSources pulls all the DataSoures listed on a given server. You can pull form as many different servers as needed. For DSServer you add the following 3 lines to the config for each server you want to pull DataSources from.

[db{x}]
DSServer=1
server= (will not pull DataSources published with DSServer from another box)

You add one entry per server no matter how many DataSources are listed on that server. {x} would become the number for each server starting at 0 and incrementing by one for each entry you make. IE [db0] [db1] [db3] ect. Information listed this way is delivered via the DNS Services tab in the PW Network Control Panel. If you use this method you can leave the DataSource Listing tab blank.

For Example

[db1]
DSServer=1
server=remoteserver.anothercompany.com

The benefit of the individual listed DateSources is the Gateway server does not need to pull anything before giving the client the DataSource list. This can speed up client launch by a few seconds depending on how many servers you are listing DataSources for and where those servers are located. This also allows you to only publish the DataSources you wish to for a given server and the ability to change their display name.

The benefit of DSServer is that it’s dynamic, so if you add or delete a DataSource on a server it will automatically populate for users connecting through the gateway server. Because this data is delivered with the DNS Services tab it reduces the number of client side entries that need to be made. DSServer can be pointed at non-integration servers to pull its list however will not pull DataSources listed on other servers by DSServer.

Temporary Caching Configuration

Temporary Caching allows a Gateway server to keep a local copy of a file as users download files from remote servers. This helps improve file access times for remote files as after the first full copy is pulled only a delta checksum and maybe some file deltas have to cross the wan link.

It is important to note that a Gateway Server can be a temporary caching server, but doesn’t have to be. A Temporary Caching Server must be a Gateway Server because a Temporary Caching Server can only cache the files that are routed through it.

For A Gateway server to be a Temporary Caching Server or host a Storage Area, in the DMSKrnl.cfg, under the [team mate] section, FileTransferSrv=1 must be set. Note, once FileTransferSrv=1 is set on a Gateway server it will require a Caching Server licenses. 

To control Temporary Caching there is also a [cache] section in the DMSKrnl.CFG. Under this section you can set the following parameters.

enabled=true|false (required)

Setting enabled=true turns on temporary caching, if this is not present or set to false the server will not cache files. 

servers=ipaddr1[:port1][,ipaddr2:port2,...] 

This allows you to list the servers and optionally the ports for the servers you wish to cache files from. You would use this if you didn’t want to cache files from all server in your environment.

storagepath=path_to_cache_root (required)

This is the location on the Temporary Caching server where the cached files will be stored. You must create this folder. Under this fold ProjectWise will automatically create a number of different folders for its use. By default, files from each server you cache from will be stored in a folder named with the remote servers IP address and Port. IE 192.168.0.10-5800. If there is a need to change the IP address of a remote server you can preserve the cache by manually renaming this folder.

UseHostnameInPath = 1|0 (new to SS3, OFF by default)

New in SS3 is a way to force the folder cached files are stored in to be named by host name rather than IP address. So rather than the folder being named ‘192.168.0.10-5800’ it would appear as ‘StorageServer.domain.com-5800’. This can be useful if the IP address of the server you are caching from changed its address. If you are setting this on an existing Temporary Caching server you can rename the old cache folders from IP address to host name to retain the files you have already cached.

limit=xxx ; xxx=limit for cached files in megabytes (required)

This tells ProjectWise how much to cache on a server. This number is listed in megabytes with 1024 representing 1 GB. This value is often overlooked and set to low. Often users will use fetchfiles to pull down files over night and try to pull more files than the cache can handle. The results in users believing caching isn’t working correctly when in fact the cache is simply dumping just fetched files to make room for new ones.

purgebatchsize=1000 ; max # of files purged per pass, default 1000

This tells ProjectWise how many files to delete at a time when it reaches the cache limit. ProjectWise will delete batches of files until it gets under 80% used. In cases where you run close to your cache limit all of the time or in situations where you have very large or small files there can be some benefit to tweaking these settings however most users do not find the need to change this.

This caching example is specific to SS3 because of the UseHostNameInPath entry, with that remove it would work for any version of ProjectWise.

[cache]
enabled=true
storagepath=c:\cache
;cache up to 4gb of file
limit=4092
UseHostnameInPath=1

Once you have the required settings in place and any optional settings you may want, you should be able to copy out a file with your client and see it in the cache. Remember, if your Storage Area server name and Gateway entries do not match (FQDN=FQDN, short=short) your client will not use the Gateway and the file cannot be cached.
For more info on gateway / caching servers and a sample configuration checkout http://communities.bentley.com/products/projectwise/content_management/w/wiki/5614.aspx

Overview 

MIME (Multipurpose Internet Mail Extensions) is a specification for formatting non-ASCII messages so they can be sent over the Internet. ProjectWise uses file MIME types for various purposes, including integration with MicroStation and AutoCAD, for attribute exchange, and for the new photo preview feature in ProjectWise V8i. Some well-known file types may not get a MIME type assigned in ProjectWise, due to the fact that ProjectWise currently does not need a MIME type value in order to correctly process those file types. This is the intended behavior.

Since setting the document MIME type during a database conversion is an optional task, it is important to understand when and why the MIME type conversion should be performed when upgrading ProjectWise datasources from pre-V8 XM Edition versions to V8 XM Edition or V8i.

The purpose of this document is to explain:

• why MIME types are important to ProjectWise
• how ProjectWise Integration Server V8i and V8 XM Edition use the document MIME types
• what considerations should be given to MIME type management

MicroStation Integration

MIME type management was introduced in ProjectWise V8 XM Edition (8.9.2.33) to support the distributed DGN functionality. Because only V8 DGN files can be made shareable, ProjectWise uses the MIME type of each DGN file to determine whether it is a V8 DGN or a V7 DGN. For this reason, V7 DGN files and V8 DGN files have been assigned different MIME types:

• V7 = image/vnd.dgn
• V8 = image/vnd.dgn;ver=8

When files are imported into ProjectWise, ProjectWise stores the MIME type of each file in the database, and use that database value to determine whether the DGN file can be made shareable or not.

AutoCAD Integration

ProjectWise also uses the file MIME type for AutoCAD reference file management. When you check in or update the server copy of a master DWG file, any changes to the master file that affect its reference set information are then updated in the database. In order for this database update to occur, the MIME type of your DWG files must be set to image/vnd.dwg

Attribute Exchange\Titleblocks

Starting with the 8.9.4 version of ProjectWise V8 XM Edition, all types of attribute exchange require the proper MIME type to be set for the document. This includes:

• Manual update on user request (menu item or MicroStation key-in such as dmsupdate)
• Automatic update on document open
• Automatic update on document copy-out operation
• Automatic update on document check-out operation
• Automatic update on document export operation (starting with ProjectWise V8i)
• Manual update on multiple documents using the Bulk Update tool

For ProjectWise V8i, the attribute exchange configuration information is stored in the computer registry in the following location:

• HKEY_LOCAL_MACHINE\SOFTWARE\Bentley\ProjectWise iDesktop Integration\08.11\TitleBlocks\Tools\Auto Update
• HKEY_LOCAL_MACHINE\SOFTWARE\Bentley\ProjectWise iDesktop Integration\08.11\TitleBlocks\Tools\Bulk Extract

For ProjectWise V8 XM Edition, the attribute exchange configuration information is stored in the computer registry in the following location:

• HKEY_LOCAL_MACHINE\SOFTWARE\Bentley\ProjectWise iDesktop Integration\08.09\TitleBlocks\Tools\Auto Update
• HKEY_LOCAL_MACHINE\SOFTWARE\Bentley\ProjectWise iDesktop Integration\08.09\TitleBlocks\Tools\Bulk Extract

Under each version's keys there are sub-keys for each application:

• MS Excel, MS Word, Ustation, AutoCAD r15, AutoCAD r16, AutoCAD r17

Under each of these sub-keys there will be following registry values:

•  Name: FileType
• Type: REG_MULTI_SZ
• Value: values are different, depends on application

This value is a list of all MIME types that are supported by a given updating system. Therefore, a document must have one of these MIME types set to have any attributes updated. Otherwise, no attribute update will occur for that specific document.

Raster Streaming

Dynamically downloading, or streaming, raster data with integrated MicroStation was introduced in the 8.9.2.33 version of ProjectWise V8 XM Edition. This technology depends on the raster file that is being streamed having a ProjectWise MIME type set to "raster".

Photo Preview

ProjectWise V8i introduces the Photo Preview tab to the Preview pane in ProjectWise Explorer, which out of the box displays digital images and Microsoft Office documents. Additionally, the Photo Preview tab can be extended to display additional file types, such as Adobe PDFs, HTML and text files. When you select a document in the document list and then select the Photo Preview tab, a copy of the document is downloaded to your local working directory, and then displayed in the Photo Preview tab. To determine whether a document should be copied to the local working directory and displayed, ProjectWise checks the MIME type of the file. If the MIME type is not set, or not set to the correct value for the application, the document will not be copied out and displayed. The DMSCONV tool will set these MIME types correctly.

The table below shows the correct MIME type settings for files to display correctly in the Photo Preview tab.

Creating MIME Types

When you create a document in ProjectWise, whether by using a document creation wizard, no wizard, or by dragging files from the file system, ProjectWise sets the MIME type, if known, for each file. MIME types are stored in the DMS_DOC table, in the O_MIMETYPE field. However, pre-V8 XM Edition datasources have no concept of MIME types. When pre-V8 XM Edition datasources are upgraded to V8 XM Edition or V8i, the MIME types will still not be determined. To set MIME types for these files, a MIME type bulk update must be performed. This can be accomplished using the DMSCONV tool. The DMSCONV tool will prompt the user to update the MIME types of these files as part of the database upgrade to a V8 XM Edition or V8i platform. This does not have to be done as part of the conversion; it can be run after a datasource is converted. The DMSCONV tool will issue a MIME query command to the storage area for each file to determine the MIME type; note that this is a read-only operation, and the file is NOT transferred or modified during this process.

Also, the MIME type conversion process can also be stopped before completion, and when run at a later time, the process will start up where it left off and not reprocess files it has already processed. Because not all file types need to have a MIME type assigned, the MIME type determination process can be accelerated by defining an exclusion list on the DMSCONV command line. Files with matching extensions will be ignored for MIME type determination purposes. See the DMSCONV command-line help for examples.

While it is always recommend having your database completely up-to-date, including MIME types, you can assess how time-critical it is to have all MIME types converted. Upgrading the MIME types from a pre-V8 XM datasource is most important for reference file handling in AutoCAD, and for attribute exchanges\title block updates.
 

Summary of MIME Type Usage Introduction

See Also

Product TechNotes and FAQs

ProjectWise TechNotes And FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Overview

ProjectWise has historically allowed the user to configure complex routing configurations, in order to allow for external access to ProjectWise resources across a corporate firewall, as well as to allow the caching of CAD data so that the data is geographically closer to the users, removing the need for the users to access large files over a potentially slow WAN.

However, as the complexity of the routing configurations grows, the ability to determine by what route a given client contacts a server grows equally complex. Often, it is necessary to dig through configuration files on many machines in order to determine the route.  Additionally, it has historically been practically impossible for a client machine to determine the overall latency for a given route.

What is needed is a tool to display both information about what ProjectWise servers are transited in a given route, and the latency between those servers.

ProjectWise Traceroute Tool

This tool, when run from a client machine, will allow the user to determine the route to a given endpoint ProjectWise server, the latency between each hop in the route, and the caching configuration on each server that is transited.  If a connection cannot be made to a hop (either due to misconfiguration of the ProjectWise route, or a broken network link between machines), this tool will also report the last node that was successfully contacted, making it easier to determine the cause of networking issues.

Usage:

Usage: pwping [-d display-name] [-h hops] [-n count] [-t timeout]  target_name

Options:

-d display-name:      Display name of the endpoint datasource to trace route to; name will be resolved via normal ProjectWise DNS.

If this switch is specified, the target_name command argument must be omitted.

-h hops:                 Maximum number of servers to transit on the  way. Defaults to the end of the route.

-n count:               Number of ping requests to send between hops.

                               Defaults to 1.

-t timeout:             Timeout in milliseconds to wait for each reply.

                               Defaults to 5000ms.

-c:                        Display caching configuration information

Examples:

For this example, we shall assume that the server PW_INTSRV has a misconfigured route to server PW_FILESTOR. Thus, the output from pwping for each successive hop would be:

[c:\Program Files\Bentley\ProjectWise\bin]pwping pw_gateway

pwping: INFO  - Tracing route to host 'pw_gateway'

pwping: INFO  - Hop: 1  Host: pw_gateway  Address: 10.10.10.191  PW Version: 08.09.03.31 AvgTime: 6ms  AvgTtl: 125

[c:\Program Files\Bentley\ProjectWise\bin]pwping pw_intsrv

pwping: INFO  - Tracing route to host 'pw_intsrv'

pwping: INFO  - Hop: 1  Host: pw_gateway  Address: 10.10.10.191  PW Version: 08.09.03.31 AvgTime: 3ms  AvgTtl: 125

pwping: INFO  - Hop: 2  Host: pw_intsrv  Address: 10.10.10.190  PW Version: 08.09.03.31 AvgTime: 66ms  AvgTtl: 128

[c:\Program Files\Bentley\ProjectWise\bin]pwping pw_filestor

pwping: INFO  - Tracing route to host 'pw_filestor'

pwping: INFO  - Hop: 1  Host: pw_gateway  Address: 10.10.10.191  PW Version: 08.09.03.31 AvgTime: 2ms  AvgTtl: 125

pwping: INFO  - Hop: 2  Host: pw_intsrv  Address: 10.10.10.190  PW Version: 08.09.03.31 AvgTime: 5ms  AvgTtl: 128

pwping: ERROR - Failed to ping host 'pw_filestor': no route to next hop

In this example, we shall ask the utility to display any caching server configuration information it finds as it transits the various servers in the route:

[c:\Program Files\Bentley\ProjectWise\bin]pwping -c pw_intsrv

pwping: INFO  - Tracing route to host 'pw_intsrv'

pwping: INFO  - Hop: 1  Host: pw_gateway  Address: 10.10.10.191  PW Version: 08.09.03.31 AvgTime: 8ms  AvgTtl: 125

pwping: INFO  -     Caching enabled on host 'pw_gateway' : Cache Path: 'c:\pw_cache\files'   Cache Limit 200 MB

pwping: INFO  - Hop: 2  Host: pw_intsrv  Address: 10.10.10.190  PW Version: 08.09.03.31 AvgTime: 6ms  AvgTtl: 128

Next, we shall trace a route to a ProjectWise integration server based on a datasource's display-name value.  In this example, a datasource with the display-name value of "PCJ_TESTROUTE" is configured on server PW_INTSRV.

[c:\Program Files\Bentley\ProjectWise\bin]pwping -d"PCJ_TESTROUTE"

pwping: INFO  - Tracing route to host 'pw_intsrv'

pwping: INFO  - Hop: 1  Host: pw_gateway  Address: 10.10.10.191  PW Version: 08.09.03.31 AvgTime: 7ms  AvgTtl: 125

pwping: INFO  - Hop: 2  Host: pw_intsrv  Address: 10.10.10.190  PW Version: 08.09.03.31 AvgTime: 5ms  AvgTtl: 128

See Also

Product TechNotes and FAQs

ProjectWise TechNotes And FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Overview

The ProjectWise Gateway Service is used to enable external ProjectWise Explorer clients (individuals located outside the company's firewall) to reach a ProjectWise Integration Server residing on the secure local network inside the company's firewall.

This guide will help aid in troubleshooting some common issues.

Notes

• This requires a gateway configuration be set up on the Gateway and Caching servers. 
• It is necessary that the gateway machine be configured to advertise its IP address as an address that the client can connect to.
• If you are using thick client access, the gateway machine should be configured to advertise the public IP. 
• If a client is using the gateway as both a Web Server and a thick client Gateway Server, the thick client needs to associate the public IP with the gateway machine. 
• There may be times, if the Web Server is inside a DMZ and is configured to access the Application Server via the gateway, it may be unable to access the gateway via the advertised public IP.
• A Web Server, on the other hand, will be configured to connect directly to the Application Server via the ProjectWise Network Control Panel applet. 
• The existing routing entries on the Application Server will not need to change, and there should be no need to add or change any NameResolution config file information on the Application Server's dmskrnl.cfg file.
• ProjectWiseV8i client connections through ProjectWise Gateway Service are not supported using IPv6.
• If you installed the ProjectWise Gateway Service (which does not require a license), but then later enabled the file caching feature in that service's dmskrnl.cfg file you will need a license because this is essentially turning a ProjectWise Gateway Service into a ProjectWise Caching Server.

Getting Started

The following section provides a list of items to check when troubleshooting ProjectWise Gateway issues.

1. Port 5800 needs to be open bi-directionally through all firewalls. 
2. In the dmskrnl.cfg file, Disable Allow/deny statements until you know that caching/routing works.
3. Gateway Service can NOT be installed on computer on which ProjectWise Integration Server or ProjectWise Caching Server is already installed.

Configuration 

The following section shows the basic dmskrnl entries needed on the Gateway Server.

Check the following sections of the dmskrnl.cfg for each Caching/FTS Server and Gateway Servers under c:\ Program Files\Bentley\ProjectWise\bin\

[Name Resolution]
Ip = Gateway/Connection Server
Ip = Integration Server
Ip = Caching Server

[Gateway]
Integration Server=Connection/Gateway Server
Caching Server =Connection Server

[Routing)]
Integration Server =5800
Caching Server=5800

On Gateway Server Only
ConnectionSrv=1

[Cache]- Caching Server only
Enabled=true
Storagepath=c:\cache
Limit=200

The ProjectWise Network Control Panel

The ProjectWise Network Control Panel is used to point the client machine to use specific network settings when connecting to ProjectWise servers. Check the following two items to ensure they are configured correctly.

1. DNS and Datasource Tabs point to Gateway\Connection Server-Port 5800
2. UDP checked for Disabled on both tabs

Trouble Shooting Potential Issues

Firewall

When the Windows Firewall is ON (recommended) on the ProjectWise server computer that is publishing datasource lists, the firewall will block the default ProjectWise broadcasting and listening ports of 5799 and 5800.

• This means that clients of the server (ProjectWise Administrator, ProjectWise Explorer, ProjectWise Web Parts, etc.) will not be able to see that server or its datasources even if they are located on the same computer, and even if you have defined connections to the server through the ProjectWise Network Configuration Utility.

• On each of the ProjectWise Integration Server, Caching Server, and Gateway Service computers you will need to add ports 5799 and 5800 to the exception list of the Windows Firewall.

- Select Control Panel > Windows Firewall.
- The Windows Firewall dialog opens. The General tab displays whether the firewall is on or off.
- Assuming it is ON (recommended), select the Exceptions tab and click Add Port.
- To add port 5799, set name to "ProjectWise UDP", set port to 5799, and set protocol to UDP.
- To add port 5800, set name to "ProjectWise TCP", setport to 5800, and set protocol to TCP.

DNS

There may be instances when DNS is a factor. Therefore, it would be best to complete the (Name Resolution) section of the dmskrnl.cfg file.

1. Verify that each server can resolve either the short names of the other server or use the FQDN (Fully Qualified Domain Name) for each server. 
2. If you choose FQDN, the storage area for each data source must also be updated to a FQDN. ProjectWise needs to be able to resolve the servername listed in the storage area setup just as it must resolve the name of other ProjectWise servers.

All three of the commands should produce similar results, in a slightly different format.

Open a command prompt window and enter each command listed below.

• Nbtstat -c 
• Nslookup (hostname)
Nslookup (ip address)
• Ipconfig /all

Nbstat-c Displays protocol statistics and current TCP/IP connections using NBT
(NetBIOS over TCP/IP) and lists NBT's cache of remote [machine] names and respective IP addresses

NSlookup -will verify that the hostname and ip address being configured is not conflicting with any other machine

ipconfig /ALL -Allows to see both the computer name and if WINS is configured. 
**Please note your results

Connectivity

Make sure the gateway service is started and run the ProjectWise Tool "Socket Analyzer" to ensure you have a connection.

The Windows Socket Analyzer tests the connection to the remote host. (See the Help Section in ProjectWise Explorer for step by step instructions.)

PW PING

The PWPING utiliy provides detailed information on the connectivity between the client machine and server or from server to server. If you are experiencing problems, turn up the logging as indicated below, run the pwping command and review the logs.

1. Turn up logging utility by going to c:\program files\Bentley\ProjectWise\bin\pwping.log.xml . Open this file with NotePad. 
2. From the Menu, do an Edit, Replace. 
3. In the field "Find What" type "warn" and Replace with "all". 
4. Select Replace All, close the window and Save the file.

Go to a Command Prompt and browse to c:\ Program Files\Bentley\ProjectWise\bin\ 
Type Pwping - (hostname or ip of the remote destination)

Ping from each hop: Caching to Gateway, Gateway to Integration

The pwping.log file generated from the pwping will be located at c:\documents and settings\user that you are logged into the server as\application data\bentley\logs

See Also

Product TechNotes and FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Getting Started with ProjectWise StartPoint 2003

ProjectWise StartPoint is an entry-level collaboration tool, based on Microsoft Office SharePoint.  ProjectWise StartPoint can be used with MicroStation V8 XM Edition build 8.9.2.77 and higher, as well as with other MicroStation XM derivatives. This is only recommended if the server is running Windows SharePoint Services 2.0 or Microsoft SharePoint Portal Server 2003 (see below for more details).

Setting up SharePoint on the Server

*Note: Any issues relating to downloading, installing, configuring, site-creation, or administering of Windows SharePoint should be directed to Microsoft technical support.

1.  The SharePoint administrator must verify that Windows SharePoint Services 2.0 (WSSv2) has been setup and correctly installed.

WSSv2 is an add-on to Windows 2003 Server R2 Operating System and can be installed from your original Windows 2003 Server R2 Operating System or downloaded directly from Microsoft:  Windows SharePoint Services 2.0. 

For more information about WSSv2, see Windows SharePoint Services: Getting Started

*Note: Although ProjectWise StartPoint requires WSSv2, ProjectWise StartPoint will also work with Microsoft SharePoint Portal Server 2003 (SPS2003).  SPS2003 is a separately licensed and installed Microsoft product which adds additional functionality to WSSv2. 

For more information about SPS2003, see SharePoint Portal Server 2003 Help and How-to

2.  The SharePoint administrator must provide the CAD manager access to create sites on the server.

a. See Windows SharePoint Services 2.0 Help and How-to.

b. Click User Documentation and Resources.

c. Click Managing Permissions and Security.

3.  The CAD manager then creates team sites and document libraries on the server.

a. See Windows SharePoint Services 2.0 Help and How-to.

b. Click User Documentation and Resources.

c. Click Managing Sites and Settings.

4.  The CAD manager provides team members access to the team site and document libraries.

Setting up StartPoint on the Server

1.  Download ProjectWise StartPoint Administrator Help

2.  The SharePoint administrator must install the ProjectWise StartPoint Service on the server.

a. Download the latest release from Bentley SELECT Services. 

b. Click Downloads and Updates.

c. Click Search Downloads.

d. Log in.

e. Select ProjectWise as the Product

f. From the returned applications, select ProjectWise StartPoint Service.

Setting up MicroStation on a computer

1.  MicroStation V8 XM Edition, MicroStation PowerDraft XM Edition, Bentley View XM Edition, Bentley Redline 8.9.3 or 8.9.4, and Bentley Navigator 8.9.3 or 8.9.4 users do not have to install anything on their computer.  To obtain one of these versions:

a. Download these latest releases from Bentley SELECT Services.

b. Click Downloads and Updates.

c. Click Search Downloads.

d. Log in.

e. Select the appropriate application.

Setting up AutoCAD on a computer

1.  AutoCAD users must install and license ProjectWise StartPoint for AutoCAD on their computer, which also requires a ProjectWise Passport.

• a. Download ProjectWise StartPoint for AutoCAD.

Licensing ProjectWise StartPoint

There are three modules to ProjectWise StartPoint:

1. ProjectWise StartPoint Service

This server-side module does not require its own license.  However, its usage is reported in the Select Server logs.

2.  ProjectWise StartPoint Integration w/ MicroStation

This client-side module is included into MicroStation V8 XM Edition products. No additional client side install is needed.

It is licensed via a ProjectWise Named User License.

3.  ProjectWise StartPoint Integration w/ AutoCAD

This client-side module is a separate install on each client machine.

It is also licensed via a ProjectWise Named User License.

MicroStation V8 XM Edition, MicroStation PowerDraft XM Edition, Bentley View XM Edition, Bentley Redline 8.9.3 or 8.9.4, and Bentley Navigator 8.9.3 or 8.9.4 require a ProjectWise Passport to use ProjectWise StartPoint. This license is on your company's SELECT Server. If you don't have this license, you can "test-drive" ProjectWise StartPoint for 30 days.

There are three ways to procure a ProjectWise Passport:

1. License purchase
2. License subscription (monthly)
3. SELECT subscription (no-charge SELECT benefit for MicroStation SELECT subscribers)

**Additional ProjectWise Passports can be ordered through your Account Manager or Sales Representative.

Uploading Design Documents to ProjectWise StartPoint

1.  Download ProjectWise StartPoint User Help.

2.  Open your browser and go to the team site and document library set up by the CAD manager.

3. Upload design documents to the document library by clicking the Upload Document button.

a. To upload multiple design documents,  click Upload Multiple Files.

b. You can upload MicroStation design documents and AutoCAD drawings.

c. Before uploading a design document with reference files, be sure the reference files are attached to the master file using a relative path.

Gaining access to your Design Documents

To view a Design Document in a Document Library

1. Click the design document's name.
2. Choose the application in which you'd like to view it.

To Edit a Design Document

1. Point to a design document's name and click the arrow to its right.
2. Click Edit With and the application.

To Create a Design Document

1. Click New Document.
2. Select a seed file.
3. Choose the application in which you want to save it.

For more information on ProjectWise StartPoint, please refer to the Help and online information atwww.Bentley.com

See Also

Product TechNotes and FAQs

ProjectWise TechNotes And FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Overview

ProjectWise StartPoint is an entry-level collaboration tool, based on Microsoft Office SharePoint.  ProjectWise StartPoint can be used with MicroStation V8 XM Edition build 8.9.4.51 and higher, as well as with other MicroStation XM derivatives. This is only recommended if the server is running Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007.

Setting up SharePoint on the Server

*Note: Any issues relating to downloading, installing, configuring, site-creation, or administering of Windows SharePoint should be directed to Microsoft technical support.

1.  The SharePoint administrator must verify that Windows SharePoint Services 3.0 (WSSv3) has been setup and correctly installed.

WSSv3 is an add-on to Windows 2003 Server R2 Operating System and can be installed from your original Windows 2003 Server R2  Operating System or downloaded directly from Microsoft:  Windows SharePoint Services 3.0

For more information about WSSv3, see Tour a Windows SharePoint Server 3.0 Site

*Note: Although ProjectWise StartPoint 8.9.4 requires WSSv3, ProjectWise StartPoint will also work with Microsoft Office SharePoint Server 2007 (MOSS2007).  MOSS2007 is a separately licensed and installed Microsoft product which adds additional functionality to WSSv3. 

For more information about MOSS2007, see Microsoft Office SharePoint Server 2007 Help and How-to.

2.  The SharePoint administrator must provide the CAD manager access to create sites on the server.

a. See Windows SharePoint Services 3.0 Help and How-to.

b. Click Managing sites and settings.

c. Click Managing Permissions and Security.

3.  The CAD manager then creates team sites and document libraries on the server.

a. See Windows SharePoint Services 3.0 Help and How-to.

b. Click Managing sites and settings.

c. Click Managing Permissions and Security.

4.  The CAD manager provides team members access to the team site and document libraries.

Setting up StartPoint on the Server

1.  Download ProjectWise StartPoint Administrator Help.  

2.  The SharePoint administrator must install the ProjectWise StartPoint Service on the server.

a. Download the latest release from Bentley SELECT Services. 

b. Click Downloads and Updates.

c. Click Search Downloads.

d. Log in.

e. Select Bentley ProjectWise as the Product and click Search.

f. From the returned applications, select ProjectWise StartPoint Service and click

   Continue.

g. Select the Download radio button and click Continue.

h. After reading the SELECTservices Online Legal Terms of Use, click Accept.

i. Click the Download link.

j. Click Run to install the product or click Save to save the download locally.

   If you choice the Save option, you must still run the executable to install the

   product.

Setting up MicroStation on a computer

1.  MicroStation V8 XM Edition, MicroStation PowerDraft XM Edition, Bentley View XM Edition, Bentley Redline 8.9.4, and Bentley Navigator 8.9.4 users do not have to install anything on their computer.  To obtain one of these versions:

a. Download these latest releases from Bentley SELECT Services.

b. Click Downloads and Updates.

c. Click Search Downloads.

d. Log in.

e. Select the desired application as the Product and click Search.

f. From the returned applications, select version of the desired product and click

   Continue.

g. Select the Download radio button and click Continue.

h. After reading the SELECTservices Online Legal Terms of Use, click Accept.

i. Click the Download link.

j. Click Run to install the product or click Save to save the download locally.

   If you choice the Save option, you must still run the executable to install the

   product.

Setting up AutoCAD on a computer

1.  AutoCAD users must install and license ProjectWise StartPoint for AutoCAD on their computer, which also requires a ProjectWise Passport.

• a. Download ProjectWise StartPoint for AutoCAD.

Licensing ProjectWise StartPoint

There are three modules to ProjectWise StartPoint:

1. ProjectWise StartPoint Service

This server-side module does not require its own license.  However, its usage is reported in the Select Server logs.

2.  ProjectWise StartPoint Integration w/ MicroStation

This client-side module is included into MicroStation V8 XM Edition products. No additional client side install is needed.

It is licensed via a ProjectWise Passport.

3.  ProjectWise StartPoint Integration w/ AutoCAD

This client-side module is a separate install on each client machine.

It is also licensed via a ProjectWise Passport.

MicroStation V8 XM Edition, MicroStation PowerDraft XM Edition, Bentley View XM Edition, Bentley Redline 8.9.4, and Bentley Navigator 8.9.4 require a ProjectWise Passport to use ProjectWise StartPoint. This license is on your company's SELECT Server. If you don't have this license, you can "test-drive" ProjectWise StartPoint for 30 days.

There are three ways to procure a ProjectWise Passport:

1. License purchase
2. License subscription (monthly)
3. SELECT subscription (no-charge SELECT benefit for MicroStation SELECT subscribers)

**Additional ProjectWise Passports can be ordered through your Account Manager or Sales Representative.

Uploading Design Documents to ProjectWise StartPoint

1.  Download ProjectWise StartPoint User Help.  

2.  Open your browser and go to the team site and document library set up by the CAD manager.

3. Upload design documents to the document library by clicking the Upload Document button.

a. To upload multiple design documents, click Upload Multiple Files.

b. You can upload MicroStation design documents and AutoCAD drawings.

c. Before uploading a design document with reference files, be sure the reference files are attached to the master file using a relative path.

Gaining access to your Design Documents

To View a Design Document in a Document Library

1. Click the design document's name.
2. Choose the application in which you'd like to view it.

To Edit a Design Document

1. Point to a design document's name and click the arrow to its right.
2. Click Edit With and the application.

To Create a Design Document

1. Click New Document.
2. Select a seed file.
3. Choose the application in which you want to save it.

For more information on ProjectWise StartPoint, please refer to the Help and online information atwww.Bentley.com

See Also

Product TechNotes and FAQs

ProjectWise TechNotes And FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Overview

ProjectWise StartPoint has been tested against the following SharePoint versions:

ProjectWise StartPoint for AutoCAD has been tested against the following AutoCAD versions:

ProjectWise StartPoint is built into the following MicroStation versions:

See Also

Product TechNotes and FAQs

ProjectWise TechNotes And FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Overview

Note:  The SharePoint versions listed below are 32-bit applications. 64-bit SharePoint servers are also supported via the 64-bit StartPoint Service.

ProjectWise StartPoint has been tested against the following SharePoint versions:

ProjectWise StartPoint for AutoCAD has been tested against the following AutoCAD versions:

ProjectWise StartPoint is built into the following MicroStation versions:

See Also

Product TechNotes and FAQs

ProjectWise TechNotes And FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

What type of encryption is used when a user is logging into WEL without using SSL?

It uses standard base64-encoding. The user name is passed with clear text. Base64 is typically referred to as an encoding scheme not encryption. It is a very trivial encoding and is not considered secure.

What type of encryption is used when a user is logging into WEL with using SSL?

It uses 128 bit encryption for the user name and passwords that are passed over the wire. The strength of the SSL session between a browser and server depends on the strength of the session key that is generated during session negotiation. This is a symmetric key used to encrypt and decrypt data exchanged by the browser and server. Browsers and servers usually negotiate the strongest mutually supported session. This means that if the user's browser and your Web server both supports 128-bit SSL sessions, a 128-bit session is established. If the user's browser only supports 40-bit SSL sessions, then a 40-bit session is established even if your Web server supports 128-bit sessions.

What type of encryption is used when a user is logging in from ProjectWise Explorer using a Windows account from the domain to log into the datasource?

Using NTLM authentication and encryption method. Kerberos authentication is also supported, but neither NTLM nor Kerberos are used for encryption. Without separately activated SSL encryption (between the client and the server), only some most sensitive parts of some messages are encrypted by RC4 algorithm (using 128 bit keys). That is done independently of the authentication protocol.

What type of encryption is used when a user is logging into ProjectWise Explorer using a Logical ProjectWise account to log into the datasource?

It encrypted using RC4 algorithm (using 128 bit keys).

What type of encryption is used when a user is logging in using SSL on the ProjectWise Application Server where the datasources are published (Running ProjectWise in secure mode) ?

Using 128 bit encryption from the certificate server in your network. The keys are validated by the server running certificate server. It still uses port 5800. I would refer to this as the "ProjectWise Secure Connection" when not talking about WEL using HTTPS. SSL is a well know standard and our connection is not based on it.

Can I enable SSL with ProjectWise Explorer? Are there any port configuration changes?

Using ProjectWise in secure mode encrypts the data from ProjectWise Explorer to the application server. The configuration is done on the server. The encryption keys are handled by the certificate server.

Does the file get encrypted using ProjectWise when being transferred over the wire?

Only when using the PW secure connection.

What type of secure communication happens when communicating with the database?

ProjectWise communicates to the backend database through ODBC. ProjectWise will use whatever is the type of connection you have setup. For example MS SQL Server passing user/password in clear text. You can use the Server Network Utility to enable SSL encryption over all enabled network libraries. SQL Server 2000 can then use the SSL to encrypt all data transmitted over any network library between a SQL Server 2000 client (ProjectWise Application Server) and a server running SQL Server 2000. The encryption level, 40-bit versus 128-bit, depends on the level of encryption supported by the Windows operating system involved as well. For maximum security it is recommended that you use Microsoft integrated authentication for the database connection

How does ProjectWise work with Active Directory?

ProjectWise works with an Active Directory model in both Mixed and Native mode. ProjectWise Authentication Server will pull information from the Domain controller on users and groups within AD. Once in ProjectWise the users authenticate from the PW application server to the domain controller in AD.

Does ProjectWise store my Passwords in the Database?

For ProjectWise Windows Users we do NOT store the password in the database. The ProjectWise Authentication Server brings the user names from the domain into the database where they are stored in the DS_SID table. It then populates the user names to the dms_user table. When the user authenticates into ProjectWise, the ProjectWise Application makes a call to the domain controller in real time to authenticate the user. For this reason we do not store ProjectWise Windows accounts in the database. The actual passwords not stored in the database. In the PW logical user case only, a MD5 hash of the passwords is stored so that the plain text user password can not be recovered.

Does ProjectWise support Kerberos?

Not directly, ProjectWise will work with and Win2003 Active Directory using Kerberos. Authentication using Kerberos is supported.

If a user logs in from the WEL client using his NT account how does ProjectWise deal with the password sent over the wire. Again what protocol are we using?

If not using SSL it uses Base64 encoding and the password is encoded using that. For a more secure method it is recommended to use SSL within the web environment.

See Also

Product TechNotes and FAQs

ProjectWise TechNotes And FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Overview:

The following technote describes how to display general and environment attribute columns in WEL.

Pre-requisites \ Assumptions:

The following products will need to be installed in order to display general and environment attributes in WEL.
1) ProjectWise Integration Server
2) ProjectWise Administrator
3) ProjectWise Explorer
4) ProjectWise Web Server.

The following configurations are needed in order to complete the process. 
1) A ProjectWwise Datastource
2) A ProjectWise Environment within a Datasource 
3) The Environment needs to be assigned to a Folder within the Datasource.
4) Files need to be in the folder.

Setting Up Default General Document Attributes in the Main Document Frame

This section describes the default general document attributes that are shown in the main document frame regardless of the environment used for the folder being displayed.

Example 1

Note: Documents will be sorted by the first field in the list in ascending order.

The following steps describe how to change and add the default attributes to be show in the main document frame in WEL:

1. Open the PWLiteServlet.properties file from C:\Program Files\Bentley\ProjectWise\WebServer\common\classes which is the default installation path for ProjectWise Web Server 

2. Scroll down to the #general.attributes section. By default, the general attributes is commented out and is set to display only the default attributes which are Name, Description, Version File Size, and Updated. (See above Example 1)

3. Uncomment the general.attributes section and add your desired general attributes from the given list and save the file.

For example:
general.attributes= Department; Description; Document ID

Possible Values are as follows: Application, Created, Creator, Department, Description, Document ID, File Name, File Size, File Updated, File Updater, Document Name, Node, Out To, State, Status, Storage, Updated, Updater, Version, Workflow, Sequence

4. Restart the ProjectWise Web Server Service from Windows Services. Right click on My Computer  Click on Manage  Click on Services and Applications  Then Click on Services and your ProjectWise Web Server Service will be listed.

5. Log into ProjectWise to make sure the desired attributes are shown. It doesn't matter which folder is selected for the general attributes to be shown.

Adding Environment Attributes to the Main Document Frame

Example 1 shows the document main frame with default general attributes. In this section we will add environment attributes to the main document frame.

Example 1

These entries are used to define which environment attributes for each environment will be displayed in the main document frame when documents from that particular environment are listed. This means that as users change from folder to folder, the list of attributes displayed will change.

The steps below describe how to set an Environment to a folder and how to edit the PWLiteServlet.Properties file.

1. In ProjectWise Administrator, create an environment with your attributes. (See Example 2 below)

Please note: For information on creating an environment attribute see the Projectwise Administrator Help

2. In ProjectWise Explorer make sure the Environment is set to a folder. Right click on a folder and choose properties. On the General tab, use the pull down to select the environment (See Example 3 Below)

Example 3

3. On the Web Server: Navigate to C:\Program Files\Bentley\ProjectWise\WebServer\common\classes and open file PWLiteServlet.properties. Open this file using notepad.

4. Go to the section "Adding Environment Attributes to main document frame". The following is a description of what each part of the command line is used for in the PWLiteServlet.properties

<server host name> - this is the host name of the server that has ProjectWise Webserver installed. Note: Log intoWEL and take a look at the location section - that is how the server host name needs to be entered in the PWLiteServlet.properties file. ( See Example 4 below) In this example add "\:": SQLand89463 (case sensitive).

Example 4

<datasource name> - CASE-SENSITIVE: jutin
<environment name> - CASE-SENSITIVE: Office
<attribute name> - NOT CASE-SENSITIVE: Status;WFStatus;

Example of the entire syntax:
<server host name>\:<datasource name>, <environment name>=<attribute name>;<attribute name>;<attribute name>

Example of the syntax with the correct entries to display to attribute columns using the example data above: 
SQLand89463\:jutin.Office=Status;WFStatus

Note: If you have multiple Environments, create a new line with the new environment name and attribute names and make sure that a folder has been set to the environment (from step 2.)

5. Save the PWLiteServlet.properties file
6. Restart the Web Server Service (See Section 1 on how to restart the ProjectWise Web Server Service)
7. Log into WEL and make sure the desired attributes from the environment are being displayed.

Example 5

Note: It is possible to set general attributes with environment attributes together by un-commenting the general.attributes section and setting your environment attributes as well. See Example 6.

The syntax in the PWLiteServlet.Properties file will be as follows for Example 6:

SQLand89463\:jutin.Office=Department; Description; Document ID; Status; WFStatus

Example 6

See Also

Product TechNotes and FAQs

ProjectWise TechNotes And FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Overview

ProjectWise Web Explorer Lite has added the ability to add logon credentials to any valid URL. This means that a customer can form a URL that will allow them to display folder contents, document properties or publish a file using Document Publisher or Bentley Publisher.

By default this feature is not enabled. To enable it, modify the web.xml file located in the <installdir>\projectwise\webserver\webapps\WEL\WEB-INF directory.

Change the Filter Mappings section

The user Id and Password are added to the URL or request package for a given document or folder action. In order to add some level of security to the process the password must be base64 encoded. This is the same password encryption that web browsers use for basic authentication. It is further recommend that the customer runs the server in SSL mode (HTTPS). Forming the URL A typical URL to view a document from Web Explorer Lite looks like: http://servername/WEL/servlet/LiteServlet?REQUEST_TYPE=VIEW&DSId=datasourceName&VaultId=61&DocId=50 In order to login from another system 3 pieces of information must be added to the URL. The users login id, base64 encoded password and the server name of the server the datasource is published on. Item Required URL Variable Comment Login Id Password Datasource Server Name Id Pw DSServer Plain text user login Base 64 encoded password Host name of the server in which the DSid datasource is running   ProjectWise Web Explorer Lite ships with 2 tools to make forming the URLs easier. A javascript file that can be used in the customers application to base64 encode the password for use in the URL. The javascript file is in: <installdir>\projectwise\webserver\webapps\WEL\gfx\styles\base64.js A sample HTML page that will assist in generating URLs. User is prompted for required information and URLs are generated for viewing a Document List, Document Properties and viewing a document. The URL page generation page is located in <installdir>\projectwise\webserver\webapps\WEL\ WELUrlGen.htm http://servername/WEL/ WELUrlGen.htm Please note that the parameter names and values are case sensitive. The following is a list of request type available. Datasources LiteServlet?REQUEST_TYPE=GetDSList Input &Parameters=refresh Output Retrieve all registered datasources in the ProjectWise Web Application Server machine Style Sheets DS.xsl Remarks None   LiteServlet?REQUEST_TYPE=LoginScreen Input &DSId=<datasource_name> &DSServer=<pw_app_server_hostname> Output Show ProjectWise login screen Style Sheets LoginScreen.xsl Remarks This screen is not mandatory as users are prompted for login when LiteServlet requests occur without an opened session.   LiteServlet?REQUEST_TYPE=Logout Input &DSId=<datasource_name> Output Close user session Style Sheets LoggedOut.xsl Remarks None   Vaults LiteServlet?REQUEST_TYPE=GetVaultList Input &DSId=<datasource_name> &VaultId=<vault_id> Output List sub-vaults for the selected vault Style Sheets DS.xsl Remarks &vaulted=0 would return all root vaults.   LiteServlet?REQUEST_TYPE=RemoveVaultList Input &DSId=<datasource_name> &VaultId=<vault_id> Output Collapse sub-vaults for the selected vault Style Sheets DS.xsl Remarks &vaulted=0 would collapse all root vaults.   LiteServlet?REQUEST_TYPE=GetDocList Input &DSId=<datasource_name> &VaultId=<vault_id> Output Retrieve all documents for the selected vault. Style Sheets Document.xsl Remarks Access control applies. Users would only see documents that they have access to.   Documents LiteServlet?REQUEST_TYPE=Properties Input &DSId=<datasource_name> &VaultId=<vault_id> &DocId=<document_id> Output Return attributes in "General" sheet. Style Sheets Properties.xsl Remarks This shows the "General" sheet in ProjectWise Explorer.   LiteServlet?REQUEST_TYPE=ShowGeneral Input &DSId=<datasource_name> &VaultId=<vault_id> &DocId=<document_id> Output Return attributes in "General" sheet. Style Sheets Properties_General.xsl Remarks If LiteServlet?REQUEST_TYPE=Properties is called, you can switch between property page without the above parameters.   LiteServlet?REQUEST_TYPE=ShowAttributes Input &DSId=<datasource_name> &VaultId=<vault_id> &DocId=<document_id> Output Return attributes in "Attribute" sheet. Style Sheets Properties_Attributes.xsl Remarks If LiteServlet?REQUEST_TYPE=Properties is called, you can switch between property page without the above parameters.   LiteServlet?REQUEST_TYPE=ShowMoreAttributes Input &DSId=<datasource_name> &VaultId=<vault_id> &DocId=<document_id> Output Return attributes in "More Attributes" sheet. Style Sheets Properties_MoreAttributes.xsl Remarks If LiteServlet?REQUEST_TYPE=Properties is called, you can switch between property page without the above parameters.   LiteServlet?REQUEST_TYPE=ReferenceFiles Input &DSId=<datasource_name> &Set=<set_id> Output Return a document list show all the reference files for the selected file. Style Sheets Document.xsl Remarks LiteServlet?REQUEST_TYPE=ReferenceFiles is also applicable to flatset.   LiteServlet?REQUEST_TYPE=View Input &DSId=<datasource_name> &VaultId=<vault_id> &DocId=<document_id> Output View the select file using an appropriate viewer defined in global.viewers.properties. Style Sheets vpr.xsl Bentley Publisher ActiveX viewer Publish.xsl Bentley Publisher Java viewer TextPage.xsl Document Publisher viewer Remarks If no viewer is associated to the select file type, WEL would perform the action defined in "noviewer.action" in "PWLiteServlet.properties". Default is "copyout".   LiteServlet?REQUEST_TYPE=CopyOut Input &DSId=<datasource_name> &VaultId=<vault_id> &DocId=<document_id> Output Copy ouy the select file. Style Sheets Download.xsl Remarks If no viewer is associated to the select file type, WEL would perform the action defined in "noviewer.action" in "PWLiteServlet.properties". Default is "copyout".   Queries LiteServlet?REQUEST_TYPE=OpenSearches Input &DSId=<datasource_name> &QueryId=<query_id> Output Expand "Searches" list in WEL. Style Sheets DS.xsl Remarks Use &QueryId=0 for root.   LiteServlet?REQUEST_TYPE=QueryByForm Input &DSId=<datasource_name> &Environment=<environment_id> Output Display ProjectWise default search form for the selected environment. Style Sheets QueryForm.xsl Remarks None   Examples for the various Request Types http://KMBPWWEB/WEL/servlet/LiteServlet?REQUEST_TYPE=Login&DSId=Kevin_Oracle9i&DSServer=matrix&Id=admin&Pw=YmVudGxleQ== http://KMBPWWEB/WEL/servlet/LiteServlet?REQUEST_TYPE=View&DSId=Kevin_Oracle9i&DSServer=matrix&Id=admin&Pw=YmVudGxleQ==&VaultId=137&DocId=1 http:// KMBPWWEB\WEL/servlet/LiteServlet?REQUEST_TYPE=Properties&DSId=Kevin_Oracle9i&DSServer=matrix&Id=admin&Pw=YmVudGxleQ==&VaultId=137&DocId=1 http://KMBPWWEB/WEL/servlet/LiteServlet?REQUEST_TYPE=ShowAttributes&DSId=Kevin_Oracle9i&DSServer=matrix&Id=admin&Pw=YmVudGxleQ==&VaultId=137&DocId=1 http://KMBPWWEB/WEL/servlet/LiteServlet?REQUEST_TYPE=CopyOut&DSId=Kevin_Oracle9i&DSServer=matrix&Id=admin&Pw=YmVudGxleQ==&VaultId=137&DocId=1 http://KMBPWWEB/WEL/servlet/LiteServlet?REQUEST_TYPE=OpenSearches&DSId=Kevin_Oracle9i&DSServer=matrix&Id=admin&Pw=YmVudGxleQ==&QueryId=0   See Also Product TechNotes and FAQs ProjectWise TechNotes And FAQs External Links Bentley Technical Support KnowledgeBase Bentley LEARN Server Comments or Corrections? Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Overview:

The following technote describes how to display general and environment attribute columns in WEL.

Pre-requisites \ Assumptions:

The following products will need to be installed in order to display general and environment attributes in WEL.
1) ProjectWise Integration Server
2) ProjectWise Administrator
3) ProjectWise Explorer
4) ProjectWise Web Server.

The following configurations are needed in order to complete the process. 
1) A ProjectWwise Datastource
2) A ProjectWise Environment within a Datasource 
3) The Environment needs to be assigned to a Folder within the Datasource.
4) Files need to be in the folder.

Setting Up Default General Document Attributes in the Main Document Frame

This section describes the default general document attributes that are shown in the main document frame regardless of the environment used for the folder being displayed.

Example 1

Note: Documents will be sorted by the first field in the list in ascending order.

The following steps describe how to change and add the default attributes to be show in the main document frame in WEL:

1. Open the PWLiteServlet.properties file from C:\Program Files\Bentley\ProjectWise\WebServer\common\classes which is the default installation path for ProjectWise Web Server 

2. Scroll down to the #general.attributes section. By default, the general attributes is commented out and is set to display only the default attributes which are Name, Description, Version File Size, and Updated. (See above Example 1)

3. Uncomment the general.attributes section and add your desired general attributes from the given list and save the file.

For example:
general.attributes= Department; Description; Document ID

Possible Values are as follows: Application, Created, Creator, Department, Description, Document ID, File Name, File Size, File Updated, File Updater, Document Name, Node, Out To, State, Status, Storage, Updated, Updater, Version, Workflow, Sequence

4. Restart the ProjectWise Web Server Service from Windows Services. Right click on My Computer  Click on Manage  Click on Services and Applications  Then Click on Services and your ProjectWise Web Server Service will be listed.

5. Log into ProjectWise to make sure the desired attributes are shown. It doesn't matter which folder is selected for the general attributes to be shown.

Adding Environment Attributes to the Main Document Frame

Example 1 shows the document main frame with default general attributes. In this section we will add environment attributes to the main document frame.

Example 1

These entries are used to define which environment attributes for each environment will be displayed in the main document frame when documents from that particular environment are listed. This means that as users change from folder to folder, the list of attributes displayed will change.

The steps below describe how to set an Environment to a folder and how to edit the PWLiteServlet.Properties file.

1. In ProjectWise Administrator, create an environment with your attributes. (See Example 2 below)

Please note: For information on creating an environment attribute see the Projectwise Administrator Help

2. In ProjectWise Explorer make sure the Environment is set to a folder. Right click on a folder and choose properties. On the General tab, use the pull down to select the environment (See Example 3 Below)

Example 3

3. On the Web Server: Navigate to C:\Program Files\Bentley\ProjectWise\WebServer\common\classes and open file PWLiteServlet.properties. Open this file using notepad.

4. Go to the section "Adding Environment Attributes to main document frame". The following is a description of what each part of the command line is used for in the PWLiteServlet.properties

<server host name> - this is the host name of the server that has ProjectWise Webserver installed. Note: Log intoWEL and take a look at the location section - that is how the server host name needs to be entered in the PWLiteServlet.properties file. ( See Example 4 below) In this example add "\:": SQLand89463 (case sensitive).

Example 4

<datasource name> - CASE-SENSITIVE: jutin
<environment name> - CASE-SENSITIVE: Office
<attribute name> - NOT CASE-SENSITIVE: Status;WFStatus;

Example of the entire syntax:
<server host name>\:<datasource name>, <environment name>=<attribute name>;<attribute name>;<attribute name>

Example of the syntax with the correct entries to display to attribute columns using the example data above: 
SQLand89463\:jutin.Office=Status;WFStatus

Note: If you have multiple Environments, create a new line with the new environment name and attribute names and make sure that a folder has been set to the environment (from step 2.)

5. Save the PWLiteServlet.properties file
6. Restart the Web Server Service (See Section 1 on how to restart the ProjectWise Web Server Service)
7. Log into WEL and make sure the desired attributes from the environment are being displayed.

Example 5

Note: It is possible to set general attributes with environment attributes together by un-commenting the general.attributes section and setting your environment attributes as well. See Example 6.

The syntax in the PWLiteServlet.Properties file will be as follows for Example 6:

SQLand89463\:jutin.Office=Department; Description; Document ID; Status; WFStatus

Example 6

See Also

Product TechNotes and FAQs

ProjectWise TechNotes And FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Overview

ProjectWise Web Explorer Lite has added the ability to add logon credentials to any valid URL. This means that a customer can form a URL that will allow them to display folder contents, document properties or publish a file using Document Publisher or Bentley Publisher.

By default this feature is not enabled. To enable it, modify the web.xml file located in the <installdir>\projectwise\webserver\webapps\WEL\WEB-INF directory.

Change the Filter Mappings section

The user Id and Password are added to the URL or request package for a given document or folder action. In order to add some level of security to the process the password must be base64 encoded. This is the same password encryption that web browsers use for basic authentication. It is further recommend that the customer runs the server in SSL mode (HTTPS). Forming the URL A typical URL to view a document from Web Explorer Lite looks like: http://servername/WEL/servlet/LiteServlet?REQUEST_TYPE=VIEW&DSId=datasourceName&VaultId=61&DocId=50 In order to login from another system 3 pieces of information must be added to the URL. The users login id, base64 encoded password and the server name of the server the datasource is published on. Item Required URL Variable Comment Login Id Password Datasource Server Name Id Pw DSServer Plain text user login Base 64 encoded password Host name of the server in which the DSid datasource is running   ProjectWise Web Explorer Lite ships with 2 tools to make forming the URLs easier. A javascript file that can be used in the customers application to base64 encode the password for use in the URL. The javascript file is in: <installdir>\projectwise\webserver\webapps\WEL\gfx\styles\base64.js A sample HTML page that will assist in generating URLs. User is prompted for required information and URLs are generated for viewing a Document List, Document Properties and viewing a document. The URL page generation page is located in <installdir>\projectwise\webserver\webapps\WEL\ WELUrlGen.htm http://servername/WEL/ WELUrlGen.htm Please note that the parameter names and values are case sensitive. The following is a list of request type available. Datasources LiteServlet?REQUEST_TYPE=GetDSList Input &Parameters=refresh Output Retrieve all registered datasources in the ProjectWise Web Application Server machine Style Sheets DS.xsl Remarks None   LiteServlet?REQUEST_TYPE=LoginScreen Input &DSId=<datasource_name> &DSServer=<pw_app_server_hostname> Output Show ProjectWise login screen Style Sheets LoginScreen.xsl Remarks This screen is not mandatory as users are prompted for login when LiteServlet requests occur without an opened session.   LiteServlet?REQUEST_TYPE=Logout Input &DSId=<datasource_name> Output Close user session Style Sheets LoggedOut.xsl Remarks None   Vaults LiteServlet?REQUEST_TYPE=GetVaultList Input &DSId=<datasource_name> &VaultId=<vault_id> Output List sub-vaults for the selected vault Style Sheets DS.xsl Remarks &vaulted=0 would return all root vaults.   LiteServlet?REQUEST_TYPE=RemoveVaultList Input &DSId=<datasource_name> &VaultId=<vault_id> Output Collapse sub-vaults for the selected vault Style Sheets DS.xsl Remarks &vaulted=0 would collapse all root vaults.   LiteServlet?REQUEST_TYPE=GetDocList Input &DSId=<datasource_name> &VaultId=<vault_id> Output Retrieve all documents for the selected vault. Style Sheets Document.xsl Remarks Access control applies. Users would only see documents that they have access to.   Documents LiteServlet?REQUEST_TYPE=Properties Input &DSId=<datasource_name> &VaultId=<vault_id> &DocId=<document_id> Output Return attributes in "General" sheet. Style Sheets Properties.xsl Remarks This shows the "General" sheet in ProjectWise Explorer.   LiteServlet?REQUEST_TYPE=ShowGeneral Input &DSId=<datasource_name> &VaultId=<vault_id> &DocId=<document_id> Output Return attributes in "General" sheet. Style Sheets Properties_General.xsl Remarks If LiteServlet?REQUEST_TYPE=Properties is called, you can switch between property page without the above parameters.   LiteServlet?REQUEST_TYPE=ShowAttributes Input &DSId=<datasource_name> &VaultId=<vault_id> &DocId=<document_id> Output Return attributes in "Attribute" sheet. Style Sheets Properties_Attributes.xsl Remarks If LiteServlet?REQUEST_TYPE=Properties is called, you can switch between property page without the above parameters.   LiteServlet?REQUEST_TYPE=ShowMoreAttributes Input &DSId=<datasource_name> &VaultId=<vault_id> &DocId=<document_id> Output Return attributes in "More Attributes" sheet. Style Sheets Properties_MoreAttributes.xsl Remarks If LiteServlet?REQUEST_TYPE=Properties is called, you can switch between property page without the above parameters.   LiteServlet?REQUEST_TYPE=ReferenceFiles Input &DSId=<datasource_name> &Set=<set_id> Output Return a document list show all the reference files for the selected file. Style Sheets Document.xsl Remarks LiteServlet?REQUEST_TYPE=ReferenceFiles is also applicable to flatset.   LiteServlet?REQUEST_TYPE=View Input &DSId=<datasource_name> &VaultId=<vault_id> &DocId=<document_id> Output View the select file using an appropriate viewer defined in global.viewers.properties. Style Sheets vpr.xsl Bentley Publisher ActiveX viewer Publish.xsl Bentley Publisher Java viewer TextPage.xsl Document Publisher viewer Remarks If no viewer is associated to the select file type, WEL would perform the action defined in "noviewer.action" in "PWLiteServlet.properties". Default is "copyout".   LiteServlet?REQUEST_TYPE=CopyOut Input &DSId=<datasource_name> &VaultId=<vault_id> &DocId=<document_id> Output Copy ouy the select file. Style Sheets Download.xsl Remarks If no viewer is associated to the select file type, WEL would perform the action defined in "noviewer.action" in "PWLiteServlet.properties". Default is "copyout".   Queries LiteServlet?REQUEST_TYPE=OpenSearches Input &DSId=<datasource_name> &QueryId=<query_id> Output Expand "Searches" list in WEL. Style Sheets DS.xsl Remarks Use &QueryId=0 for root.   LiteServlet?REQUEST_TYPE=QueryByForm Input &DSId=<datasource_name> &Environment=<environment_id> Output Display ProjectWise default search form for the selected environment. Style Sheets QueryForm.xsl Remarks None   Examples for the various Request Types http://KMBPWWEB/WEL/servlet/LiteServlet?REQUEST_TYPE=Login&DSId=Kevin_Oracle9i&DSServer=matrix&Id=admin&Pw=YmVudGxleQ== http://KMBPWWEB/WEL/servlet/LiteServlet?REQUEST_TYPE=View&DSId=Kevin_Oracle9i&DSServer=matrix&Id=admin&Pw=YmVudGxleQ==&VaultId=137&DocId=1 http:// KMBPWWEB\WEL/servlet/LiteServlet?REQUEST_TYPE=Properties&DSId=Kevin_Oracle9i&DSServer=matrix&Id=admin&Pw=YmVudGxleQ==&VaultId=137&DocId=1 http://KMBPWWEB/WEL/servlet/LiteServlet?REQUEST_TYPE=ShowAttributes&DSId=Kevin_Oracle9i&DSServer=matrix&Id=admin&Pw=YmVudGxleQ==&VaultId=137&DocId=1 http://KMBPWWEB/WEL/servlet/LiteServlet?REQUEST_TYPE=CopyOut&DSId=Kevin_Oracle9i&DSServer=matrix&Id=admin&Pw=YmVudGxleQ==&VaultId=137&DocId=1 http://KMBPWWEB/WEL/servlet/LiteServlet?REQUEST_TYPE=OpenSearches&DSId=Kevin_Oracle9i&DSServer=matrix&Id=admin&Pw=YmVudGxleQ==&QueryId=0   See Also Product TechNotes and FAQs ProjectWise TechNotes And FAQs External Links Bentley Technical Support KnowledgeBase Bentley LEARN Server Comments or Corrections? Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Overview

The following Technote describes how to set up Single Sign On (SSO) for Projectwise Web Parts set up on a SharePoint Server.

Pre-requisites/Assumptions

A working ProjectWise implementation with the following programs needs to be installed. 
1) ProjectWise Integration Server
2) ProjectWise Administrator
3) ProjectWise Explorer
4) SharePoint 2007 
5) .Net Framework 3.0 SP1
6) ProjectWise Web Parts 

The following are basic steps involved in configuring SSO. 
1) Modify the dmskrnl.cfg file on the Integration Server (Section 1)
2) Enable the delegate user for the datasource. (Section 2)
3) Modify ProjectWise Web Parts to enable Windows credentials - Single Sign On. Modify IIS to enable anonymous access. 
4) Make changes to a client's machine prior to them logging on to ProjectWise Web Parts.

Modify the dmskrnl.cfg file on the Integration Server

This section describes the two configuration changes that need to be made in the c:\program files\Bentley\Projectwise\bin\dmskrnl.cfg file.

1. Start by adding the SharePoint Server to the Trusted Servers section in the dmskrnl.cfg file.

Notice how the name SharepointSrv = 10.97.0.53 was added under the Trusted Servers section.

2. Next add the line SSO = 1 to the bottom of the dmskrnl.cfg file under the datasource settings. This configuration needs to be set for each datasource requiring single sign on.

Enable a Delegate user for the datasource 

After creating the Delegate user in ProjectWise Administrator, we will need to save the user's settings on the SharePoint Server.
 
Note: The following configuration needs to be made on the SharePoint Server where ProjectWise Web Parts is deployed.

1. Log on to our the SharePoint Server and click on Start  All Programs  Bentley  ProjectWise V8i  Web Server and Web View Server  ProjectWise Web Server Single Sign On Settings.

2. From the database dropdown menu, chose the corresponding datasource where you want to enable Single Sign On.

3. Add the new Delegate user name and password you just created and then click "Save Settings."

4. The Delegate user has been enabled for the datasource.

Modify ProjectWise Web Parts to enable Windows credentials - Single Sign On. Modify IIS to enable anonymous access.

1. Log on to the newly created SharePoint Site as an Administrator and click on the dropdown menu on any one of the Web Parts and select Modify Shared Web Part.

Note: It doesn't matter which Web Part is clicked on because you get the option to select which Web Part to modify as shown in the example below.   

2. Enable SSO for our datasource by checking on the "Use Windows credentials (SSO)" option. You can select which Web Parts to enable SSO on by checking those on or off.

Note: All users who will be authenticating into SharePoint for SSO Web Parts will need to exist in SharePoint as users.

3. In IIS, right click on the SharePoint website under Web Sites and then click on Properties  then click on the Directory Security Tab. The following dialogue box should appear.

4. Click on the edit button under Authentication and access control, and the Authentication Methods dialogue box will appear. In this box, uncheck Enable anonymous access as shown below and make sure "Integrated Windows Authentication" is checked.

5. Click on OK and proceed to the client's workstation for testing

Make changes to a client's machine prior to them logging on to ProjectWise Web Parts

This section describes what changes to make on the client's machine in order for the user to access Web Parts using Single Sign On.
 
In order for the client to access ProjectWise Web Parts using Single Sign On, you will need to be logged into the domain that connects to their ProjectWise datasource using their correct Windows credentials. To test this, make sure Single Sign On is working with ProjectWise Explorer on the user's machine. 

Once the user has successfully logged on to the domain and their machine, they will need to do the following

1. Open Internet Explorer and click on Tools  Options. When the Internet Options dialogue box appears, the user will need to click on the Security Tab  Internet  Custom Level.

 2. Scroll down to the User Authentication Section and make sure the setting "Automatic logon with current user name and password" is selected then click okay.

3. Under Internet Options, click the Advanced Tab and scroll down to the Security section. In this section make sure the option "Enable Integrated Windows Authentication" is checked on (this takes effect after restarting Internet Explorer).

The user should now be able to connect to ProjectWise Web Parts using Single Sign On.

See Also

Product TechNotes and FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!