Thank you for downloading Autodesk Topobase Web 2010 Update 1.

This readme contains the latest information regarding the installation and use of this update. It is strongly recommended that you read this entire document before you apply the update to your product. For reference, you should save this readme to your hard drive or print a copy.

Contents

• Who Should Install This Update?
• Topobase Web 2010 Update 1 Information
  • Action Required
  • General Information
• Primary Issues Resolved by This Update
  • Updates to Topobase Web 2010
  • Updates to MapGuide Enterprise 2010
  • Known Issues with This Update
• Supported Operating Systems
• Installation Instructions

Update 1 is for Autodesk Topobase Web 2010, in all languages, running on Windows 2003 Server and Windows 2008 Server.

Action Required

For a complete Topobase Web 2010 update you must install the Topobase Client 2010 Update 1 and update the Topobase System User (TBSYS) and the documents. We recommend performing these steps before you install the Topobase Web 2010 Update.

For more information, see Topobase Client 2010 Update 1 readme.

NOTE: You can only update the document structure in the database using Topobase Client or Administrator.

General Information

This Readme contains information regarding the installation and use of this update.

NOTE: To work with Topobase Web you do not need the Oracle 10g R2.2 patch.

During the installation of this update, you may be prompted for the original installation DVD.

Once this update is applied, you cannot run an automatic uninstall to remove the update. To undo update changes, uninstall and then reinstall the product.

Updates to Topobase Web 2010

The following defects have been fixed:

Login

• In parameterized requests, you can now use "WINDOWS_USERNAME" to login to Topobase Web.

Other

• Maps with composite line styles can now be created.

Plot

• Filters on label layers are now removed after the Plot preview.

Updates to MapGuide Enterprise 2010

Autodesk MapGuide Enterprise 2010 Update 1 resolves the following issues:

• Some FDO feature source searches were failing because there were issues with some of the identity property types.
• Search commands in Flexible Web Layouts were not executing correctly when executed from the task pane.
• There were problems correctly displaying Arab and Hebrew characters in labels.
• Labels on road data were being displayed inconsistently.
• When using the Autodesk Raster Provider, tiff catalogs on Linux could not be accessed properly.
• Autodesk Raster Provider was rendering thin image strips incorrectly.
• Feature Labels were not being displayed when a Japanese font was used in the Ajax viewer on Linux.
• Using a large point library sometimes caused errors.
• Selecting a Symbol Library in the Point Stylization dialog sometimes caused an error.
• Symbols were being displayed incorrectly in the symbol library editor, symbol previews, and map legends.
• The option "Allow other labels to obscure feature symbols on this layer" was missing from Autodesk MapGuide Studio 2010.
• Using Autodesk MapGuide Enterprise with Oracle 10g data on a Windows 2003 Server machine was consuming excessive amounts of memory.
• On Linux servers, a memory leak during data requests was causing the server to run out of memory unexpectedly.
• Selection set requests were using excess amounts of memory.
• MapGuide Server was running out of memory when accessing Oracle databases with large schemas.
• Coordinate system transformations were limiting CPU usage, preventing more than one person from using the system at a time.
• Common.php in Fusion and common.php in the PHP API were using an incorrect function call in FormatMessage which prevented exceptions from being raised properly.
• There were unexpected results with raster images when file connections were released.
• Warning error messages were being displayed when the advanced logging feature was enabled.
• Some older SDF files failed to open due to spatial index errors.
• The FDO WFS Provider was not retrieving all feature classes from the server.
• There were unexpected results with the SQL Server providers when null geometries existed.
• The Oracle Spatial provider was not displaying all the features when null z ordinate values existed in the geometries.
• Joining an SDF file to an Oracle feature class did not work.

The following are known issues in Autodesk MapGuide 2010:

Issue: Ajax Viewer - Digitizing features, when a large number of layers is loaded.

Known Issue: Using the Ajax viewer, you cannot digitize features, if your map definition contains a large number of layers (>100).

Workaround: Use a map definition with less layers, and use layer names with less characters.

This update can be used with the following:

• Windows Server 2003 R2 (SP2)
• Windows Server 2008 (SP1)

Follow these instructions to install this update on a single computer.

1. From the Product Support web site, download the update file.
2. Copy and unzip the TB2010_Web_SP1.zip to a temporary folder on your computer. Run the two files and follow the on-screen instructions.

Update 1 contains two files for the following update:

• TopobaseWeb_*.exe updates the Topobase Web Extensions.
• TopobaseServer_*.exe updates the Topobase Web Server.

The order of installation is irrelevant. Both files must be installed.

Copyright ^® 2009 Autodesk, Inc.