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

UI configuration and deployment process

  1. Create a repl and replperf database.
  2. Create a source and target database.
  3. Start the PAS instance and login to the Pro2 Web UI.
  4. Load the configuration file.

Create a repl and replperf database

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

Use the following procedure to a repl and replperf database

  1. Open a Proenv.
  2. Navigate to the Pro2 folder from the Proenv window. Type cd followed by name of the folder where you installed Pro2. For example, cd Pro2v60.
  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 replperf database instance by typing prodb replperf 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 replperf database by typing prowin replperf -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 replperf.df file and click OK.
    Note: The replperf.df file is located in <Pro2 folder>/db.
  14. Start the repl and replperf database by typing:
    • Proserve repl
    • Proserve replperf
  15. Add the replperf database connection details to the Pro2_HOME>\bprepl\Scripts\replProc.pf file to connect the replication threads and PAS for OpenEdge instance to the replperf 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 if both repl and replperf 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 will display tables.


Repl database

Pro2 replication process uses the following OpenEdge database tables (also known as repl database):
  • 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 file) and schema definition file (.df file) 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.

If your PAS for OpenEdge instance is configured to update the replication source database, then the ubroker.properties file needs to be modified to add a connection to the repl db. Another point to consider is conmgr.properties modifications, start/shutdown scripts, and backups. A stand-alone repl database requires standard database administration. This includes conmgr.properties modifications, startup/shutdown scripts and backups.

Embedding the repl Tables

Embedding the repl tables into the source database can simplify implementation. If the repl tables are embedded, no additional database connection is required. The repl database is used as a standalone 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 it 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 as well as to the source database. For this reason, the max number of users (the -n parameter when starting the database server with the proserve command or maximum users when using dbman) 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 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 replqueue 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 dbman) 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, the default of five servers to handle all remote connections to the repl database may not be sufficient. The max 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, 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.

Create a source and target database

The Pro2 source database is an OpenEdge database where the data modifications are made, the target database is the database where the modifications are replicated. While the source database must be an OpenEdge database, the target Database can be an OpenEdge, MSS SQL, or an Oracle database. In this example, the source database is named sports.

Perform the following steps to create a source and target database instance:

  1. Open a Proenv.
  2. Create source database by typing prodb sports sports in the Proenv window.
  3. Start the source database instance by typing proserve sports -S <port number>.
    Note: You can assign any port number while setting 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 target database instance by typing proserve target -S <port number>.
    Note: You can give any port number you want to when setting up the target database for the first time.

Repl properties and repl queue

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 which control different aspects of your replication environment. The following are the tables for 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 user interface.
  • ReplQueue—Information on 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 instance and login to Pro2 web application

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

  1. Start a PROENV session.
  2. Navigate to the Pro2 folder by entering cd followed by name of the folder where you installed Pro2. For example, cd Pro2v60.
  3. Type Pro2LAN\bin\tcman.bat env
  4. TypePro2LAN\bin\tcman.bat start
  5. To check if the instance has started successfully, type Pro2LAN\bin\tcman.bat env. The server running section shows a number if the instance has started.
  6. Open any browser and login at localhost:9991/pro2/static/
  7. Use the default credentials which are admin and admin.

Load the configuration file

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

Use the following procedure to load the configuration file:

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

You can view the default properties and records once 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 assign include files
bprepl\repl_jtrig Directory for any java triggers
bprepl\repl_log Default location of log files
bprepl\repl_mgtrig Directory listing 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 assign 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(s). 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