The Pro2 web interface enables you to monitor and configure your replications, such as processed record counts per thread, table performance, and others.

Main steps to configure and deploy the web interface

  1. Create a repl and pro2 database.
  2. Create a source and target database.
  3. Start the PAS for OpenEdge instance and log in to the Pro2 web user interface.
  4. Load the configuration file.

Create a repl and pro2 database:

The repl and pro2 database instances contain the replication statistics data that is displayed on the Dashboard tab of the Pro2 web user interface.

To create a repl and pro2 database:

  1. Open a Proenv instance.
  2. Navigate to the Pro2 folder from the Proenv window. Type cd followed by the name of the folder where you installed Pro2, for example, cd Pro2v61.
  3. Type cd db to navigate to the database folder of Pro2.
    Note: Check the directory of the db folder to view the database instances. Type dir after navigating to the database folder.
  4. Create an empty repl database instance by typing prodb repl empty.
  5. Create an empty pro2 database instance by typing prodb pro2 empty.
  6. Load the required table definitions in the repl database by typing prowin repl -1.

    The Procedure Editor window appears.

  7. Navigate to Tools > Data Administration.
  8. In the Data Administration window, navigate to Admin > Load Data and Definitions > Data Definitions (.df file)….
  9. In the Load Data Definitions window, load the repl.df file and click OK.
    Note: The repl.df file is located in Pro2 folder/db.
  10. Load data in the pro2 database by typing prowin pro2 -1.

    The Procedure Editor window appears.

  11. Navigate to Tools > Data Administration.
  12. In the Data Administration window, navigate to Admin > Load Data and Definitions > Data Definitions (.df file).
  13. In the Load Data Definitions window, load the pro2.df file and click OK.
    Note: The pro2.df file is located in Pro2 folder/db.
  14. Start the repl and pro2 databases by typing:
    • Proserve repl
    • Proserve pro2
  15. Add the pro2 database connection details to the Pro2_HOME\bprepl\Scripts\replProc.pf file to connect the replication threads and PAS for OpenEdge instance to the pro2 database. Navigate to the bprepl\scripts folder and open the replProc.pf file. Add the complete path of the database in the file and click Save.


  16. To check both repl and pro2 database instances are connected successfully, Open the Procedure Editor from the bprepl\Scripts folder and navigate to Tools > Data Dictionary. If the connection is successful, the Tables section displays the tables.


Repl database

The Pro2 repl database, also known as a replication database, uses the following OpenEdge database tables:
  • ReplControl
  • ReplCustDefs
  • ReplCustFlds
  • ReplDBXRef
  • ReplFieldXref
  • ReplProperties
  • ReplQueue
  • ReplTableXRef
  • ReplThreadControl
These tables can be embedded in one of the source databases or they can be configured as a stand-alone OpenEdge database.

Stand-alone repl database

Standard OpenEdge database utilities are used to create the repl database. The structure file (.st) and schema definition file (.df) used to create the repl database can be found in the root Pro2 install folder. All end-user configuration files, parameter (.pf) files, and scripts need to be modified to include a connection to the repl database wherever there is a connection made to the source database.

Embedding the repl tables

Embedding the repl tables into the source database can simplify your implementation. If the repl tables are embedded, then no additional database connection is required. The repl database is used as a stand-alone to simplify schema updates made by the application provider to the source database. Pro2 functions the same if the repl tables are embedded or if the repl database is in a separate stand-alone database.

Repl database startup parameters

The repl database startup parameters are as follows:

Name Notes
Max Number of Users (-n,maxusers) All end users must connect to the repl database and to the source database. For this reason, the maximum number of users (the -n parameter when starting the database server with the proserve command or maximum users when using the DBMAN utility) specified for the repl database should not be lower than that of the source database. If this parameter is not set high enough, then end users might not be able to run the application.
Max Lock Table Entries ( -L,locktableentries) Each update to the source database, which requires an exclusive lock on the source record, results in a record being written to the replication queue in the repl database. This also requires an exclusive lock. The max number of lock table entries (the -L when starting the database server with the proserve command or lock table entries setting in the conmgr.properties file when using the DBMAN utility) specified for the repl database should not be lower than that of the source database. If this parameter is not set high enough, end-users may encounter errors while trying to make updates and those updates fail.
Max Number of Servers (-Mn, maxservers) If there are a high number of remote users connecting to the source database, then the default of five servers to handle all remote connections to the repl database may not be sufficient. The maximum number of servers for the repl database (the -Mn when starting the database server with the proserve command or maxservers setting in the conmgr.properties file when using dbman) should not be lower than that of the source database. If this parameter is not set high enough, then end users connected as remote clients may not be able to run the application.
Before-Image File Parameters For optimal performance, the repl database before-image (BI) file should be truncated at initial implementation to set the BI block size (-biblocksize) and the BI cluster size (-bi), for example, proutil Repl –C truncate bi –biblocksize 16 –bi 16384.

Connect to a source and target database

The Pro2 source database is an OpenEdge database where the data modifications are made, and the target database is the database where the modifications are replicated. The source database must be an OpenEdge database, the target database can be an OpenEdge database, Microsoft SQL server, or an Oracle database.

To create a source and target database instance:

  1. Open a Proenv instance.
  2. Create source database by typing prodb database name in the Proenv window.
  3. Start the source database instance by typing proserve database name -S port number.
    Note: You can assign any port number when you set up the source database for the first time.
  4. Create an empty target database by typing prodb target empty in the Proenv window.
  5. Start the target database instance by typing proserve target -S port number.
    Note: You can give any port number you want when you set up the target database for the first time.

(Alternative) Connect to an existing source database after the UI is configured

To add source database details:

  1. From the Pro2 web interface, navigate to the Manage Replication tab.
  2. Click New.

    The Create Replication window appears.

  3. Set up global settings for the replication instance, for example, Source DB Mode is set to Triggers, and the Source DB Connection is set to LAN.
  4. Click Next.

    The Select Source tab appears.

  5. Enter Source DB Name
  6. Enter Host Name
  7. Enter the port number in the Host Port/Service field (for example, 2233).
  8. (Optional) Enter your User Name and Password.
    Note: Enter your user name and password only if it is required by your source database.
  9. Select Test Connection.

    If the test is successful, move on to set the target database. Review your source database details to ensure they are correct.

  10. Click Next.

    The Set Target tab appears.

ReplProperties and ReplQueue

The OpenEdge replication source database and target database tables are stored in property files. There are configuration settings whose values you set in these tables that control different aspects of your replication environment. The following are the tables for the Pro2 replication environment:
  • ReplProperties—Configuration settings such as log file location, logical delete tables, and specification of procedure templates are stored in the ReplProperties table. Configuration settings can be saved to and loaded from a text file from the New button in the Manage Replication window on the Pro2 web interface.
  • ReplQueue—Information about change events is stored in the ReplQueue table. This information includes the ROWID of the record changed, event date, time, and queue thread. Typically, repl queue records represent updates made to the source database that are waiting to be written to the target SQL database.

Start the PAS for OpenEdge instance and log in to the Pro2 web application

Now that the database instances are set up successfully, start the PAS OpenEdge instance and log in to the Pro2 web application.

  1. Start a Proenv instance.
  2. Navigate to the Pro2 folder by entering cd followed by name of the folder where you installed Pro2, for example, cd Pro2v61.
  3. Type instance name\bin\tcman.bat env.
  4. Type instance name\bin\tcman.bat start.
  5. To check if the instance has started successfully, type instance name\bin\tcman.bat env. The server running section shows a number if the instance started.
  6. Open any browser and log in at localhost:port number/pro2/static/ using the default credentials.

Load the configuration file

Before using the Pro2 web interface, you must set up a basic configuration by loading the default configuration file. The configuration file consists of all the default properties and records that are necessary to set up the Pro2 environment.

To load the configuration file:

  1. In the Pro2 web interface, navigate to Actions > Tools > Load Configuration.
  2. Click Select Files and load the replbasev610.ini file from the Pro2 folder. The replbasev610.ini file is Pro2 configuration file.
  3. Click Submit. You get a success message after the upload is complete. Set the local Pro2 install directory (pro2=c:\Pro2).

You can view the default properties and records after the configuration file is successfully loaded.

Installation reference

The following is a description of the folders under the Pro2 root installation folder.

Folder Description
bprepl Root directory for application programs
bprepl\AppSrv Used in WAN implementations
bprepl\images Image files that can be used for shortcut icons
bprepl\misc Miscellaneous replication files and procedures
bprepl\repl_as_tgt Used in WAN implementations
bprepl\repl_d Directory for the Pro2 generated database replication delete trigger procedures
bprepl\repl_export Used in WAN bulk loads
bprepl\repl_inc Directory for Pro2 generated assigned include files
bprepl\repl_jtrig Directory for any Java triggers
bprepl\repl_log Default location of log files
bprepl\repl_mgtrig Directory of tables that require merged triggers
bprepl\repl_mproc Directory for the Pro2 generated bulk copy procedures
bprepl\repl_proc Directory for the Pro2 generated replication library
bprepl\repl_w Directory for Pro2 generated database replication write trigger procedures
bprepl\repl_tmpl Directory containing the templates used for various code generation
bprepl\Scripts Directory containing the .pf files, scripts, and shortcuts to start the Pro2 Admin Tool, replication processors, and bulk load procedures.
bprepl\SQL_inc Directory for the direct, SQL assigned include files
bprepl\SQL_mproc Directory for the direct, SQL bulk copy procedures
bprepl\SQL_proc Directory for the direct, SQL replication procedures
custom Directory to deploy your customized code so that it overrides the existing code in the bprepl folder.
Note: This folder must maintain the bprepl folder structure and is applicable for both LAN and WAN configurations.
db Location of schema holder database. Also, the initial temporary location for repl database during implementation.
Installation Initially empty. Used to save installation site-specific files.
misc Miscellaneous Pro2 utilities
tmp Miscellaneous Pro2 temporary files used during implementation