Live DGN publishing persists for testing and development purposes within current releases of Geo Web Publisher despite deprecation of the live publishing workflow.  While still available, users engaging in live publishing should be aware that this may need to be temporarilly disabled before proceeding with troubleshooting of supported functionality.

What follows is a example of live DGN publishing, simplified by re-utilizing the inherent Whistler dataset.

00 The directory utilized for live DGN Publishing must exist as a Connection, of the Raster type.  Within the Geo Web Publisher Administration client, we find the example Whistler Raster Connection, which suits this purpose.  The Physical Path utilized by the connection will be:

 .../GeoWebPublisher/Engine/WorkSpace/Projects/Examples/Geospatial/whistler/dgn/sid

 

01  The Whistler example utilizes parcelsXM.dgn, conveniently located in the parent directory of our existing Raster Connection.  This file can be copied and placed within the /sid subdirectory.  Once placed, rename the file to distinguish it from it's source file.  For this example: parcelsXM_LIVE.dgn is used:

02 Publishing is acheived by concatenating the Server name, Raster Connection name, and *.dgn name into a URL.

e.g. 

http://localhost/Whistler%20Raster/parcelsXM_LIVE.dgn

When Geo Web Publisher is not running as a web server extension, the GWP port must be specified:

e.g.

http://localhost:8087/Whistler%20Raster/parcelsXM_LIVE.dgn

 

Note:  When configuring connections, the same name must not be simultaneously defined in the Web Server and in Bentley Geo Web Publisher when Bentley Geo Web Publisher is not running as a Web server extension.(readme_geowebpublisher.chm)

 

 

 

03 When running as a Web Server Extension, and when IIS Directory Browsing is enabled for the virtual directory, this allows for browsing of the desired content:

 

 See also:  Geo Web Publisher Live DGN publishing.pdf