Upgrading Pro2 from 5.5 to 6.4 or above is a manual process that involves:

  • Installing and configuring Pro2 6.4 or later versions.
  • Importing your 5.5 properties file and table mapping.
  • Disconnecting and shutting down your Pro2 5.5 instance.
Pro2 6.4 or above includes all of the enhancements and benefits of the previous 6.x releases and offers many advantages over the 5.x series. Namely, a new intuitively designed user interface, enhancements for change data capture based replication, efficient bulk loading, and so much more. Because of these drastic differences between the two version series, upgrading Pro2 can best be achieved by:
  • Installing a fresh version of Pro2 6.4 or above.
  • Preparing your 5.5 instance of Pro2 for shutdown.
  • Initiating a cut over event to switch from using 5.5 to 6.4 or above.

An aspect of the upgrade process that requires special consideration, is determining whether or not you want to bring your 5.5 properties file into your new Pro2 instance. Generally, older Pro2 installations were performed by Progress Professional Services as a paid engagement. Pro2 configurations can vary greatly between one another depending on how thoroughly the default properties file and code are customized. During your upgrade planning phase, examine your properties and compare them to the new 6.4 properties.

Progress recommendeds that you first attempt the upgrade on a test environment, and backup your entire Pro2 directory, before upgrading the production environment.

Main steps to upgrade Pro2

  1. Plan for the upgrade.
  2. Save the 5.5 configuration files.
  3. Install Pro2 6.4 or above.
  4. Configure Pro2 for LAN or WAN.
  5. Load the 5.5 configuration files.
  6. Initiate the upgrade cut-over event.
  7. Test the upgraded deployment.

Upgrade planning

Due to the highly customizable nature of Pro2 instances, there is no definitive upgrade planning method. Your upgrade planning needs might be vastly different from another Pro2 user. You should confer with your database administrator and other stakeholders to determine the best way to plan for your upgrade.

However, you should consider the following guidelines while planning for your upgrade:
  • Determine when your application receives the least amount of user traffic.
  • Plan to initiate your upgrade cut-over during a low traffic window.
  • Learn about Pro2 6.4 or above features, functionalities, and enhancements.
  • Compare your custom 5.5 properties with the 6.4 or above properties. If your custom properties are still viable, create of copy of the file for later use.

    For more information about the Pro2 6.4 properties, see Properties.

  • Determine whether a LAN or a WAN configuration is right for your deployment. Accordingly, your application may need a new configuration or may retain the same configuration. For example, changing from LAN to WAN.
  • Identify where you want to install Pro2 6.4 or above.
  • Devise a test plan.
  • Create a backup strategy.

Save your configuration files

If you want to import your Pro2 5.5 configuration details into your 6.4 or above installation, save your properties and mapping file. Before importing them:
  1. On the machine where you have Pro2 installed, open the Pro2 Administration tool and click File > Save Configuration.
  2. Save your configuration file to an easily accessible location.
  3. Return to the Administration tool and click File > Save mapping file.
  4. Save your mapping file to an easily accessible location.

    You need both the mapping and the configuration files during the Pro2 6.4 or above configuration process.

Install Pro2 6.4 or above

If you choose to use the same configuration (LAN or WAN) as your previous Pro2 deployment, Progress recommends that you install Pro2 6.4 or later versions on the same machine as your 5.5 deployment. Though on the same machine, this installation must be in a separate directory to ensure zero interference with your 5.5 deployment. By installing both the 5.5 and 6.4 or above versions on the same machine, you need fewer configurations to support the cut-over event.

  1. Depending on your choice of configuration, choose to install and configure 6.4 for LAN or WAN.
  2. Follow the installation and configuration procedure upto to the step for loading your configuration file. Then perform the following steps:
    1. In the Pro2 web interface, navigate to Actions > Tools > Load Configuration.
    2. Click Select Files to load the .ini configuration file, such as replbasev610.ini from the Pro2 folder, and click Submit.

      A success or failure notification is displayed after the upload is complete.

    3. Ensure that all the properties are successfully loaded into the Pro2 database.
    4. On the Pro2 dashboard menu, click Actions > Tools > Load Configuration.
    5. Select the Load v5 Properties File option and click Select Files to load the Pro2 5.5 properties.ini file.
    6. Select the Overwrite Pro2 Properties checkbox and click Submit.
    7. Ensure that all existing property values are overwritten with the Pro2 5.5 property values.
  3. Start the job runner.
    1. Navigate to the Pro2 Scripts folder, for example C:\Pro2\bprepl\Scripts.
    2. Select and run the jobrunner.bat file.
    3. Return to the web interface and confirm that the jobrunner.bat is running by checking the status in the Pending Jobs watch-box.
  4. Add the source database details.
    1. From the Pro2 web interface, navigate to the Manage Replication tab, and click New.

      The Create Replication window appears.

    2. In the Source DB Name field, type the name of the source database.
    3. Select Trigger or CDC as the Source Database Mode.
    4. In the Host Name field, type the name of the host.
    5. In the Host Port/Service field, type the port number (for example, 2233).
    6. If required by your source database, enter your your User Name and Password.
      Note: Enter your user name and password only if it is required by your source database.
    7. Select Test Connection and if the test is successful, move on to set the target database.
    8. Review your source database details to ensure their correctness, and Click Next.

      The Set Target tab appears.

  5. Add the target database details.
    1. In the Target Database Typelist, select Microsoft SQL Server, Oracle, or OpenEdge.
    2. If necessary, change the default values in the following fields:
      • Target Database Name
      • Target Schema Image
      • Schema Holder DB
      • Target ODBC Connection
    3. If required by your target database, enter your User Name and Password.
    4. Click Next.

      The Generate Target Schema tab appears.

      Note: If your target SQL database already exists and is not different than the one in your Pro2 5.5 instance, do not generate the target schema or load the file into target.
  6. Click Generate Target Schema.
  7. Create a schema holder for your target database.
    Note: Unless you are upgrading the OpenEdge version on the Pro2 instance machine, do not recreate the schema holder.
    1. To create an empty schema holder database, open a Proenv window, and enter prodb database name empty.
    2. Start a single user session by entering prowin database name -1.

      The Procedure Editor window appears.

    3. In the Procedure Editor window, select Tools > Data Administration.
    4. Select DataServer > <database-type> Utilities > Create DataServer Schema .

      The Create/Modify Record for Schema window appears.

    5. In the Logical Database Name field, type the name of your logical database.
    6. If the source database is MS SQL Server, specify the ODBC Data Source Name, and click Ok.
    7. In the User ID and Password dialog box, enter the Login ID and Password if required, and click OK.
    8. In the Pre-Selection Criteria For Schema Pull window, do the following:


      1. Type the values for Object Name, Object Owner (typically, dbo), and Qualifier, and select the Default to OpenEdge DATETIME checkbox.
      2. If you selected the Default to OpenEdge LOB for checkbox, ensure to select the BLOBs checkbox along with the CLOBs checkbox, so that the data server is forced to automatically treat certain target-side data types as LOBs.

        Notes:

        • Selecting the CLOBs checkbox automatically converts the varchar(max) and nvarchar(max) data types to CLOB.
        • Selecting the BLOBs checkbox forces the data server to consider all varbinary(max) data types as BLOB.
        • On the source fields that are character types, Pro2 may convert some types to varchar(max) when the source width is wider than the MAX_CHAR_WIDTH property setting. This conversion has the added benefit of avoiding row size limits for SQL Servers. However, varchar(max) and nvarchar(max) are not necessarily treated as CLOBs.
    9. On the Generate Target Schema page, open a new tab, and navigate to Actions > Tools > Load Map File.
      Note: The load map functionality deletes all the existing repl_tablexref and repl_fieldxref records and recreates them.

    10. Select the Load v5 Map File option and click:
      1. Select File in the Upload Table Map file box and load the Pro2 5.5 mapping_TBLxRef.map file.
      2. Click Select File in the Upload Field Map file box and load the Pro2 5.5 mapping_FLDxRef.map file.
        Note: Both the table map and field map files are required to complete the load process.
    11. Click Submit and return to the previous tab Generate Target Schema page.
    12. Click Next to navigate to Mapping Page.
  8. Review all the tables and fields mapping information, verify it against your Pro2 5.5 instance and, click Next.
  9. On the Advanced Configuration page, review all the table properties and thread mappings, and ensure that they match your Pro2 5.5 instance.
  10. Click Next to generate the code.
    Note: To ensure proper database connectivity, it is highly recommended to restart both jobrunner and PAS for OpenEdge web instance.

Initiate the upgrade cut-over event

Leaving the target database details unconfigured in the Pro2 UI, go to the Pro2 5.5 root folder and start a Proenv instance to shut down the 5.5 replication databases. To do it, perform the following steps:

  1. Open a Proenv window and enter the cd command to navigate to the Pro2 5.5 root folder.
  2. To shut down the replication (repl) database, enter proshut repl -by.
  3. To shut down the replperf database, enter proshut replperf -by.
  4. Return to the Pro2 6.4 or above user interface and continue the target-side configuration process.

Test the upgraded deployment

  1. After confirming that the bulk load was successful, test and troubleshoot the upgraded deployment using your test plan created during the planning phase.
  2. Review the test results, and note any abnormalities.
  3. Investigate ways to correct any abnormalities you find, and make the appropriate the corrections.
  4. If you find no abnormalities in your testing environment, choose a time to upgrade your production environment.