www.bentley.com>SELECTservices>Support>Support Tools>TechNotes and FAQs>ProjectWise
 Search

ProjectWise 2004 Edition Upgrade Planning

Support

<< Return to Index
Subject: ProjectWise 2004 Edition Upgrade Planning
Product: ProjectWise 2004 Edition
Operating System: All
Document Number: 8343

The following is the suggested process for upgrading an existing ProjectWise installation to ProjectWise 2004 Edition. The process is intended to serve as general guidance only and may not apply to all installations. Contacting Bentley Professional Services is highly recommended for site assessment, installation and configuration services in support of the upgrade process.

Bentley also recommends that the ProjectWise administrator become familiar with the new capabilities of ProjectWise 2004 Edition before upgrading their production environment to ensure a successful upgrade. It is also highly recommended that a test conversion be performed and validated prior to upgrading a production environment.

Upgrading ProjectWise 8.1.x to ProjectWise 2004 Edition

General

  1. ProjectWise 2004 Edition has been designed to allow for an easy and incremental upgrade for existing users of ProjectWise 8.1.x. To that end, existing ProjectWise 8.1.x Explorer clients will operate when connected to a ProjectWise 2004 Edition Application Server.
  2. The following matrix describes the supported combination of Explorer clients and servers:

    Version PW 8.1.x App Server PW 2004 App Server
    PW 8.1.x Explorer Supported Supported
    PW 2004 Explorer Not Supported Supported

    Note: Users of Bentley Facilities Planner and the ProjectWise GeoSpatial Extensions will not be able to have a mixture of ProjectWise 8.1 and 2004 Edition clients. All users in this environment must be upgraded to the 2004 Edition as ProjectWise 8.1 clients will not be able to connect to a ProjectWise 2004 Edition Server that is also running Bentley Facilities Planner or the ProjectWise GeoSpatial Extensions.

  3. It is possible to incrementally upgrade ProjectWise Explorer clients to 2004 Edition and to have a mixture of ProjectWise 8.1.x and 2004 Edition Explorer clients connected to a PW 2004 Edition Application Server.
  4. It is NOT supported to have both ProjectWise 8.1 and 2004 Edition Explorer clients installed on the same computer. ProjectWise 8.1.x Explorer must be uninstalled and replaced with ProjectWise 2004 Edition Explorer client.
  5. All server-based modules, including Application Server, Distributed File Servers, Web Server, Authentication Server, Distribution System and Component Services(now known as Automation Services) should be upgraded to 2004 Edition at the same time.
  6. All ProjectWise Administrator clients should also be upgraded to 2004 Edition at the same time as the server module upgrade.

Precautions

  1. Backup ProjectWise 8.1 database - a complete cold backup should be made and verified using the database vendors recommended back-up procedures.
  2. Back up all server-side ProjectWise configuration files, to include DMSKRNL.CFG, PWservlets.PROPERTIES and PWLiteServlets.PROPERTIES. While these files can not be used as is with ProjectWise 2004 Edition, they are useful for review when configuring ProjectWise 2004 Edition.
  3. Ensure that the database software that you are using with ProjectWise 8.1.x is still supported in ProjectWise 2004 Edition. This information is available in the ProjectWise 2004 Edition Application Server readme file. The suggestions in this document do not address the conversion between database types (i.e. Sybase to Oracle conversions).
  4. If there has been client API-driven customization of the ProjectWise 8.1.x system, that customization should be binary compatible with ProjectWise 2004 Edition. Installers will need to be updated to properly register the customizations on the new ProjectWise 2004 Edition clients.
  5. For Oracle users that are also migrating from Oracle 8i to Oracle 9i, an additional step of re-running DMSCONV.EXE is necessary to address changes in Unicode handling between Oracle 8i and Oracle 9i. Oracle users should first follow the migration steps below on their existing Oracle 8i datasource, then upgrade their Oracle installation to Oracle 9i and then re-run DSMCONV.EXE to address the Unicode changes in Oracle 9i.

Suggested Migration Process

  1. Conduct necessary preparation and testing as recommended above.
  2. Uninstall any existing ProjectWise 8.1.x modules on the servers to be upgraded in the following order:

    • ProjectWise Distribution System Plugin for Digital InterPlot
    • ProjectWise Distribution System Administrator
    • ProjectWise Distribution System Server
    • ProjectWise Component Services Administrator
    • ProjectWise Component Services Server
    • ProjectWise Graphic Differencing Utility
    • ProjectWise Publishing Gateway
    • Bentley Publisher
    • Digital InterPlot
    • ProjectWise Web Server
    • ProjectWise Administrator
    • ProjectWise iDesktop(if installed on server)
    • ProjectWise Explorer(if installed on server)
    • ProjectWise Authentication Server
    • ProjectWise Application Server
    • ProjectWise File Transfer or Connection Server
    • Orchestration Framework

  3. Upgrade ProjectWise server and administrative modules to 2004 Edition. Upgrading ProjectWise server components requires that all server components be upgraded at the same time this includes ProjectWise Application Server, ProjectWise Web Server, Bentley Publisher, Digital InterPlot and any File Transfer or Connection Servers.
  4. Update Operating System and Database components as necessary to meet ProjectWise 2004 Edition Requirements.
  5. Following the ProjectWise Implementation Guide instructions install all necessary server modules for ProjectWise 2004 Edition including all remote File Servers.
  6. Update your datasources to add the new tables necessary for the new capabilities of ProjectWise 2004 Edition. This is done using the dmsconv.exe application to update the database schema. With this update, it is not necessary to modify data in any existing tables, DMSCONV is simply adding additional tables and data necessary for the operation of the new functionality delivered with ProjectWise 2004 Edition.

    Running DMSCONV.EXE to update an existing ProjectWise 8.1 datasource

    • On the ProjectWise Application Server machine, open command window and navigate to the \program files\bentley\projectwise\bin\ directory.
    • Running DMSCONV.EXE with no arguments displays list of available arguments.
    • A typical DMSCONV.EXE command line for a database update will look like:

      dmsconv -d <ODBC datasource> -u <db username.password> -f <full path and name to log file>

      Example: dmsconv - d PW81 -u dba.sql - f c:\temp\pw81convert.log

    • DMSCONV provides the capability to import new Application Association settings into the updated datasource. Default settings are delivered in the file \program files\bentley\projectwise\bin\appinfo.xml. There are several command line options that control the import of these new Application Association settings:

      –app - This imports the default appinfo.xml file.
      –appfile=<full path and name of .xml file> - This imports the XML file of your choice with Application Association settings.
      -appext=<0,1> - This is used in conjunction with either –app or –appfile to control whether any previously defined application extensions are remapped to new applications set in the XML file being imported.

      Example: dmsconv –d PW81 –u dba.sql –f c:\temp\convert.log –app –appext=1

      The above example imports the Application Association settings from the APPINFO.XML file and remaps any existing extension associations in the datasource to the new extension associations delivered in APPINFO.XML

  7. Login to new ProjectWise 2004 Edition datasource using the ProjectWise 2004 Edition Administrator client and update the datasource configuration as needed to take advantage of the new functionality available in ProjectWise 2004 Edition. During this first login to an upgraded datasource, the user will be prompted to create/upgrade tables. This prompt is expected and should accepted.
  8. Test operation of new ProjectWise 2004 Edition production environment to ensure that all functionality is operating normally.
  9. Conduct a complete backup of converted database and also a complete Server back-up of the new ProjectWise 2004 Edition system to serve as a base-line recovery.
  10. For Oracle users that wish to upgrade to Oracle 9i, at this point upgrade the Oracle installation and migrate the database to Oracle 9i. In Oracle 9i both that database character set and the national character set must be set to Unicode. Once this process is complete, it is necessary to run DMSCONV.EXE against the new Oracle 9i datasource.

    • DMSCONV should be launched with the following parameters:

      • dmsconv -d <ODBC datasource> -u <db username.password> –scu
      • –scu parameter converts Unicode column types from varchar/char to nvarchar/nchar

      If during migration from ProjectWise 3.x to ProjectWise 8.1.x/Oracle 8i the parameter –etf was used to convert non-registered (no entry in dms_tabs, usually look-up type tables) custom tables then during migration to ProjectWise 2004 Edition/Oracle 9i the parameter –etf will also have to be used to specific the list of tables to update. This will make sure that the Unicode columns in these non-registered custom tables will be updated correctly.

      If the conversion of column types fails on a custom table due to an index or other reasons, then the –ctf parameter can be used in conjunction with the –ctno and –scun parameters to re-run the Unicode column type conversion on that custom table.

  11. Login to updated ProjectWise 2004 Edition Administrator and Oracle 9i datasource and confirm operation.

Suggested Areas for Review after Migration

  1. As suggested above, a thorough review of client integration and overall operation is recommended before an upgraded ProjectWise 2004 Edition installation is brought up into production use.
  2. Review both Datasource and User Settings as a number of new options have been added to both of these areas. The new settings are described in the ProjectWise Administrator Guide.
  3. Be aware that ProjectWise 2004 Edition Explorer clients will not read application association information from the PWV8.BRG file. This information now comes from either the Global Associations configured through the Application Actions in ProjectWise Administrator or through explicitly picked user overrides.

Upgrading ProjectWise 2.2.x to ProjectWise 2004 Edition

Precautions

  1. Ensure all documents are checked in before beginning server software and database upgrades.
  2. Backup ProjectWise 2.2 database - a complete cold backup should be made and verified using the database vendors recommended back-up procedures.
  3. Back up all server-side ProjectWise configuration files, to include TMD.CFG and JTM.PROPERTIES. While these files can not be used as is with ProjectWise 2004 Edition, they are useful for review when configuring ProjectWise 2004 Edition.
  4. Ensure that the database software that you are using with ProjectWise 2.2.x is still supported in ProjectWise 2004 Edition. This information is available in the ProjectWise 2004 Edition Application Server readme file or in the ProjectWise 2004 Edition Requirements document at http://selectservices.bentley.com/technotes/product36.htm. The suggestions in this document do not address the conversion between database types (i.e. Sybase to Oracle conversions).
  5. If there has been API-driven customization of the ProjectWise 2.2 system, that customization must be analyzed by the author to determine what should be done to upgrade the customization to ProjectWise 2004 Edition.
  6. Review any Environment definitions that include SQL Select statements or database triggers to ensure that they are current with the ProjectWise 2004 Edition table structure.
  7. Bentley recommends that at least one ProjectWise 2004 Edition client be installed and integration testing with all necessary desktop applications be conducted against a ProjectWise 2004 Edition test environment before upgrading the ProjectWise production environment.
  8. ProjectWise 2.x licenses will not operate with ProjectWise 2004 Edition. Bentley will provide test licenses of ProjectWise 2004 Edition on request to assist with this upgrade process. These licenses can be obtained through normal licensing channels.
  9. Bentley recommends that the Site Administrators for ProjectWise attend Administrator training for ProjectWise 2004 Edition. There are significant changes to ProjectWise 2004 Edition and Administrator training will help with the transition.

Suggested Migration Process

  1. Conduct necessary preparation and testing as recommended above.
  2. Install ProjectWise 2004 Edition client software on all workstations. All ProjectWise 2004 Edition client components can be installed in parallel with the ProjectWise 2.2.x client software.
  3. ProjectWise 2.x clients can NOT communicate with ProjectWise 2004 Edition Application Servers, nor can ProjectWise 2.x Application Servers operate with ProjectWise 2004 Edition clients.
  4. Upgrading ProjectWise server components requires that all server components be upgraded at the same time, this includes ProjectWise Application Server, ProjectWise Web Server, Bentley Publisher, Digital InterPlot and any File Transfer or Connection Servers.
  5. Install ProjectWise server software on production server. ProjectWise Application Server 2004 Edition service can be installed on the same server as the ModelServer TeamMate Server 2.2.x service, however only one service can be active at any time. Also install the ProjectWise 2004 Edition File Transfer Server on any remote File Servers. As with the ProjectWise Application Server only one File Transfer service can be active at any given time on a File Server.
  6. Stop ProjectWise 2.2.x services.
  7. Back up existing Database - When all activity is complete in the existing database, a complete cold backup should be made and verified before continuing.
  8. Start ProjectWise Application Server 2004 Edition service as well as any Remote File Transfer Servers.
  9. If your current RDMS does not meet the version requirements for ProjectWise 2004 Edition, upgrade your RDMS to the appropriate version.

    • For SQL Server 6.5 or 7 users, make sure that after upgrading your database to SQL Server 2000 that you set the database compatibility level to 80.

  10. Convert the ProjectWise datasource to the ProjectWise 2004 Edition schema using the DMSCONV.EXE utility installed with the ProjectWise 2004 Edition Application Server. At this time it is possible to also convert all of the existing History files into Audit Trail records. This step requires access to all Storage Areas containing History files and the ProjectWise 2004 Edition File Transfer service must be running on those File Servers. The Conversion of History files to Audit Trail records can be time-consuming, so an option is provided for the History files to be converted at a later time. When conducting a test conversion, be sure to re-set the storage areas to NOT point to your production Storage Areas. The conversion of History files to Audit Trail will delete any History files once they are imported. If this occurs then the History file will need to be re-covered from back-up to be available again during production conversion.
  11. If your database is SQL Server 2000, then your datasource is already able to support Unicode and you can skip to Step 13. For Sybase and Oracle users, continue with the next step.
  12. Sybase and Oracle users must create a new database (or instance) that supports a Unicode collation. The existing ProjectWise datasource must be exported using the database's administrative tools and then imported into the new database. More information about this process is located at the end of this document.
  13. Complete configuration of ProjectWise 2004 Edition server software. - Start ProjectWise 2004 Edition Administrator Client and create a new datasource that links to the converted database.
  14. Login to new ProjectWise 2004 Edition datasource using the ProjectWise 2004 Edition Administrator client and update the datasource configuration as needed to take advantage of the new functionality available in ProjectWise 2004 Edition Administrator. During this first login to an upgraded datasource, the user will be prompted to upgrade tables. This is expected and should be accepted.
  15. Test operation of new ProjectWise 2004 Edition production environment to ensure that all functionality is operating normally.
  16. Conduct a complete backup of converted database and also a complete Server back-up of the new ProjectWise 2004 Edition system to serve as a base-line recovery.
  17. Install and configure remaining ProjectWise server components such as ProjectWise Web Server, Distribution System and/or Automation Services.
  18. Remove ProjectWise 2.2.x software from servers and workstations.

Suggested Areas for Review after Migration

  1. As suggested above, a thorough review of client integration and overall operation is recommended before an upgraded ProjectWise 2004 Edition installation is brought up into production use.
  2. Review both Datasource and User Settings as a number of new options have been added to both of these areas. The new settings are described in the ProjectWise Administrator Guide.
  3. It is necessary that Scan for References be run after converting an existing ProjectWise datasource to ProjectWise 2004 Edition. This is to allow for the population of additional data into the ProjectWise database about reference file relationships for both MicroStation and AutoCAD and ensures the correct operation of reference data. This Scan for References process can be run using the “Update from current set” option to speed up the operation of the Scan for References tool.
  4. Be aware that ProjectWise 2004 Edition Explorer clients will not read application association information from previous version BRG files. This information now comes from either the Global Associations configured through the Application Actions in ProjectWise Administrator or through explicitly picked user overrides.

Upgrading ProjectWise 3.x to ProjectWise 2004 Edition

Precautions

  1. Ensure all documents are checked in before beginning server software and database upgrades.
  2. Backup ProjectWise 3.x database - a complete cold backup should be made and verified using the database vendors recommended back-up procedures.
  3. Back-up all server-side ProjectWise configuration files, to include DMSKRNL.CFG, PWSERVLETS.PROPERTIES and PWLiteServlets.PROPERTIES. While these files can not be used "as is" with ProjectWise 2004 Edition, they are useful for review when configuring ProjectWise 2004 Edition.
  4. Ensure that the database software that you are using with ProjectWise 3.x is still supported in ProjectWise 2004 Edition. This information is available in the ProjectWise 2004 Edition Application Server readme file or in the ProjectWise 2004 Edition Requirements document at http://selectservices.bentley.com/technotes/product36.htm. The suggestions in this document do not address the conversion between database types (i.e. Sybase to Oracle conversions).
  5. If there has been API-driven customization of the ProjectWise 3.x system, that customization must be analyzed by the author to determine what should be done to upgrade the customization to ProjectWise 2004 Edition.
  6. Review any Environment definitions that include SQL Select statements or database triggers to ensure that they are current with the ProjectWise 2004 Edition table structure.
  7. Bentley recommends that at least one ProjectWise 2004 Edition client be installed and integration testing with all necessary desktop applications be conducted against a ProjectWise 2004 Edition test environment before upgrading the ProjectWise production environment.
  8. ProjectWise 3.x licenses will not operate with ProjectWise 2004 Edition. Bentley will provide test licenses of ProjectWise 8.1 on request to assist with this upgrade process. These licenses can be obtained through normal licensing channels.
  9. Bentley recommends that the Site Administrators for ProjectWise attend Administrator training for ProjectWise 2004 Edition. There are significant changes to ProjectWise 2004 Edition and Administrator training will help with the transition.

Suggested Migration Process

  1. Conduct necessary preparation and testing as recommended above.
  2. Install ProjectWise 2004 Edition client software on all workstations. All ProjectWise 2004 Edition client components can be installed in parallel with the ProjectWise 3.x client software. When a user first logs into ProjectWise Explorer 2004 Edition, if a PW.BRG file from ProjectWise 3.x exists, the settings from that PW.BRG are imported into a new PWV8.BRG file that is used by ProjectWise Explorer 2004 Edition. Be aware that ProjectWise 2004 Edition Explorer clients will not read application association information from previous version BRG files. This information now comes from either the Global Associations configured through the Application Actions in ProjectWise Administrator or through explicitly picked user overrides.
  3. ProjectWise 3.x clients can NOT communicate with ProjectWise 2004 Edition Application Servers, nor can ProjectWise 3.x Application Servers operate with ProjectWise 2004 Edition clients.
  4. Upgrading ProjectWise server components requires that all server components be upgraded at the same time, this includes ProjectWise Application Server, ProjectWise Web Server, Bentley Publisher, Digital InterPlot and any File Transfer or Connection Servers.
  5. Install ProjectWise server software on production server. ProjectWise 2004 Edition Application Server service can be installed on the same server as the ProjectWise 3.x Application Server service, however only one service can be active at any time. Also install the ProjectWise 2004 Edition File Transfer Server on any remote File Servers. As with the ProjectWise Application Server, only one File Transfer service can be active at any given time on a File Server.
  6. Stop ProjectWise 3.x services including ProjectWise Application Server and JRun.
  7. Back-up existing Database - Once all activity is complete in the existing database, a complete cold backup should be made and verified before continuing.
  8. Start ProjectWise 2004 Edition Application Server service as well as any Remote File Transfer Servers.
  9. If your current RDMS does not meet the version requirements for ProjectWise 2004 Edition, upgrade your RDMS to the appropriate version.
  10. Convert the ProjectWise datasource to the ProjectWise 2004 Edition schema using the DMSCONV.EXE utility installed with the ProjectWise 2004 Edition Application Server. At this time it is possible to also convert all of the existing History files into Audit Trail records. This step requires access to all Storage Areas containing History files and the ProjectWise 2004 Edition File Transfer service must be running on those File Servers. The conversion of History files to Audit Trail records can be time-consuming, so an option is provided for the History files to be converted at a later time. When conducting a test conversion, be sure to re-set the storage areas to NOT point to your production Storage Areas. The conversion of History files to Audit Trail will delete any History files once they are imported. If this occurs then the History file will need to be re-covered from back-up to be available again during production conversion.
  11. If your database is SQL Server 2000, then your datasource is already able to support Unicode and you can skip to Step 13. For Sybase and Oracle users, continue with the next step.
  12. Sybase and Oracle users must create a new database (or instance) that supports a Unicode collation. The existing ProjectWise datasource must be exported using the database's administrative tools and then imported into the new database. More information about this process is located at the end of this document.
  13. Complete configuration of ProjectWise 2004 Edition server software. - Start ProjectWise 2004 Edition Administrator Client and create a new datasource that links to the converted database.
  14. Login to new ProjectWise 2004 Edition datasource using the ProjectWise 2004 Edition Administrator client and update the datasource configuration as needed to take advantage of the new functionality available in ProjectWise 2004 Edition Administrator. During this first login to an upgraded datasource, the user will be prompted to upgrade tables. This is expected and should be accepted.
  15. Test operation of new ProjectWise 2004 Edition production environment to ensure that all functionality is operating normally.
  16. Conduct a complete backup of converted database and also a complete Server back-up of the new ProjectWise 2004 Edition system to serve as a base-line recovery.
  17. Install and configure remaining ProjectWise server components such as ProjectWise Web Server, Distribution System and/or Automation Services.
  18. Remove ProjectWise 3.x software from servers and workstations.

Suggested Areas for Review after Migration

  1. As suggested above, a thorough review of client integration and overall operation is recommended before an upgraded ProjectWise 2004 Edition installation is brought up into production use.
  2. Review both Datasource and User Settings as a number of new options have been added to both of these areas. The new settings are described in the ProjectWise Administrator Guide.
  3. It is necessary that Scan for References be run after converting an existing ProjectWise datasource to ProjectWise 2004 Edition. This is to allow for the population of additional data into the ProjectWise database about reference file relationships for both MicroStation and AutoCAD and ensures the correct operation of reference data. This Scan for References process can be run using the "Update from current set" option to speed up the operation of the Scan for References tool.
  4. Be aware that ProjectWise 2004 Edition Explorer clients will not read application association information from previous version BRG files. This information now comes from either the Global Associations configured through the Application Actions in ProjectWise Administrator or through explicitly picked user overrides.

Converting Datasources to ProjectWise 2004 Edition

There are two parts to the conversion of existing datasources to work with ProjectWise 2004 Edition. The first part is converting the table structure to meet the requirements of ProjectWise 2004 Edition. This part is done using a utility called DMSCONV.EXE. The second part is insuring that the database can support the use of Unicode. A quick description of Unicode from the Unicode Consortium is:

Unicode provides a unique number for every character
no matter what the platform
no matter what the program
no matter what the language

By supporting Unicode, ProjectWise is better able to store and sort characters from many different languages and character sets. To do this however, the underlying database that ProjectWise is storing the data must also be set to support Unicode. For users of Microsoft SQL Server 2000, this is automatic and nothing must be done. For Oracle and Sybase users the database used for ProjectWise must be converted to support Unicode. This means exporting all of the data out of the database, creating a new database with Unicode support and importing all of the data into this new database. These steps are accomplishing using the tools provided by Oracle and Sybase.

The next sections will go into some detail on how the two parts of the ProjectWise 2004 Edition datasource conversion are accomplished.

Converting database table structure using DMSCONV.EXE

  • DMSCONV.EXE is a command line utility used to migrate the database schema of an existing ProjectWise database to meet the requirements of ProjectWise 204 Edition.
  • This utility is delivered with the ProjectWise 2004 Edition Application Server installation.
  • The utility does not require the ProjectWise Application Server service be running, unless History files are also being converted to Audit Trail records.
  • If History files are to be converted and they exist in Storage Areas on remote File Servers, the remote File Server must have the ProjectWise 2004 Edition File Transfer Server installed and running.

Running DMSCONV.EXE to convert an existing datasource

  1. Open command window and navigate to the \program files\bentley\projectwise\bin\ directory.
  2. Running DMSCONV with no arguments displays list of available arguments.
  3. A typical DMSCONV command line for a database conversion will look like:

    • dmsconv -d <ODBC datasource name> -u <db username.password> -f <full path and name to log file>
    • Example: dmsconv - d PW381 -u dba.sql - f c:\temp\pw381convert.log

  4. For datasources that have history turned on, DMSCONV will attempt to convert the history files to Audit Trail records. This is somewhat time consuming. This also requires that DMSCONV is able to contact the PW App Server or FTS that has the storage area containing the History files. You have three options on how to handle the history data; the first option is to convert it, which is the default (and deletes the History files, which is why back-up is important). The second is to ignore it and delete the History files from the storage area (which is why back-up is important). The second option is enabled by adding the -hfd argument. The third option is to convert the History files at a later time, this option is enabled by adding the –hfs argument. This allows for the conversion of the datasource and operation in ProjectWise 2004 Edition without immediately converting the History files. These can be then converted at a later time.
  5. DMSCONV provides the capability to import new Application Association settings into the updated datasource. Default settings are delivered in the file \program files\bentley\projectwise\bin\appinfo.xml. There are several command line options that control the import of these new Application Association settings:

    • –app - This imports the default appinfo.xml file
    • –appfile=<full path and name of .xml file> - This imports the XML file of your choice with Application Association settings
    • -appext=<0,1> - This is used in conjunction with either –app or –appfile to control whether any previously defined application extensions are remapped to new applications set in the XML file being imported
    • Example: dmsconv –d PW81 –u dba.sql –f c:\temp\convert.log –app –appext=1
    • The above example imports the Application Association settings from the APPINFO.XML file and remaps any existing extension associations in the datasource to the new extension associations delivered in APPINFO.XML.

  6. If SQL Server 2000 is the underlying database, then this converted database is ready for use with ProjectWise 2004 Edition. If Oracle or Sybase, then the database must also be converted to Unicode.

Updating databases to Unicode

  1. The basic process of updating a database to Unicode is the following:

    1. Export data from existing database using database tools.
    2. Create database using UTF8 collation.
    3. Import data into new database using database tools.
    4. Connect to new database with ProjectWise Administrator and login.

  2. The following example demonstrates the update process for a Sybase 7.0.4 database.

    Export data from existing Sybase database. This done via the dbunload utility in Sybase.

    1. From command line use the following:

      • dbunload -ix -c "uid=<user>;pwd=<password>;dbf=<full path and database filename>" -r <full path and name of reload file> <full path to location of export files>
      • Example: dbunload -ix -c"uid=dba;pwd=sql;dbf=c:\data\pw\orig\pw.db" -r c:\export\reload.sql c:\export\

    2. Create a new empty Sybase database. Make sure that the collation sequence is set to "UTF8". Create ODBC datasource pointing to this new database.
    3. Run DMSCONV against the new Sybase database to "authenticate" the database for use with ProjectWise. This step is specific to the OEM version of Sybase that is used with ProjectWise. From the command line:

    4. Run DMSCONV against the new Sybase database to "authenticate" the database for use with ProjectWise. This step is specific to the OEM version of Sybase that is used with ProjectWise. From the command line:

      • dmsconv -a -d <ODBC datasource name> - u <db user.password>
      • Example: dmsconv -a -d pw -u dba.sql
      • The command will return a message about the database being authenticated.

    5. Import data into newly created and "authenticated" UTF8 database.
    6. From command line run Sybase "dbsrv7" utility which starts database:

      • start dbsrv7 <full path and name of database>
      • Example: start dbsrv7 c:\data\pw\utf8\utf8.db

    7. From command line run Sybase "dbisql" utility which imports exported data into database:

      • dbisqlc -c "uid=<user>;pwd=<password>;dbn=<name of database file>" <full path and name of reload file>
      • Example: dbisqlc -c "uid=dba;pwd=sql;dbn=utf8" c:\export\reload.sql

    8. Stop the Sybase Database and create a new ProjectWise 2004 Edition datasource connected to the converted database.
    9. Login with ProjectWise 2004 Edition Administrator.

8343
How useful was this page?
less
  more
Suggest new content or let us know how we can improve this content (optional):
<< E-mail this page