The initial settings for all properties are loaded from the replbaseverson#.ini file. The file can be found in the root Pro2 install folder. You can modify the properties manually or use the Properties tab in the user interface.

Use the following table as a reference for the configurable Pro2 properties and their default configurations.

Table 1. General properties
Property Default Value Description
ADMIN_TITLE Pro2

You can define the title of a particular Pro2 instance.

ALERT_1_PER_DAY YES
Sends 1 replication thread status email per-day for all three thread types. After sending one status alert email, Pro2 will not send another on the same day for the same thread unless the alarms are cleared.
Note: This property overrides all other alert properties and settings.
APPSRV_CDCPROC_SRCSIDE NO

Use this property to can check the status of CDC threads that are running on the application server. If this property exists, and the value is "YES", the thread status will be visible. This property is disabled by default.
Bulk_Max_Cache 25

Sets the maximum number of rowids that are cached per-table during bulk loads. This value is used during bulk load restarts.
CDCADMIN_BASENAME cdcadmin Contains the name of the log file for cdcadmin records during each cdcadmin process cycle. Database name,date, queue thread number, and log file suffix are appended to the file name. For example, cdcadmin_sports_20201117-1.log.
CDC_MAX_PROCESSED 5000

The number of rows per table a CDC Admin thread processes before it begins processing additional tables in the same block. If is value of 0 is set, then all rows in a table are process before the thread moves on to the next table.

CDC_PURGE_DAYS 10

CDC records with create dates older than this value are be purged during the CDC purge process. This value is used in conjunction with a disposition of "mark as applied".
CDC_QUEUE_COMPRESSION NO

Enables or disables queue compression for CDC threads.
CHUNK_SIZE 1000000 This property defines the size of file to be transferred.
DATA_RETENTION_DAYS 14 This property sets the maximum number of days that a Pro2 database dashboard and job data is stored before being purged from the database.
DBDOWN_RETRIES 5

Sets the maximum number of attempts to reconnect database instance if it stops working.
DB_LOCATION db

Contains the location of the Pro2 database instances (repl, Pro2, source and target database instances).
DELETE_TRIG_DIRECTORY bprepl/repl_d

Contains the location of the REPLICATION-DELETE schema trigger procedures.
DEL_TRIG_TEMPLATE tplt_repltrig.p

Contains the name of the template used in generating the REPLICATATION-DELETE schema trigger procedures.
ENTERPRISE_PUSH_LOG_FILE enterprise_push Contains the name of log file for the enterprise push job. The date and log file suffix are appended to name. It is used by Repllogchk.
EXTENT_DELIMITER ##

SQL and Oracle schema generation, and SQL and Oracle differential use this value as the delimiter for definitions of Progress array fields.
FETCH_WITH_LOCK NO If this property value is YES, then an exclusive record lock is initiated while the record is fetched from the source database, otherwise the record is fetched with out being locked. This is a LAN only property. The WAN counterpart property is APPSRV_FETCH_WITH_LOCK.
HEARTBEAT_CHECK_MINUTES 15

Sets the time stamp to detect a replication threads most recent replication activity and to detect if a replication thread is stalling. The heart beat check is applicable to CDC and Replication-CDC threads.
INCLUDE_DIRECTORY bprepl/repl_inc

Contains the table programs present in the source database. Each table program contains the field assignment from source to target.
INCLUDE_LOB NO

Enables or disables the inclusion of LOB fields in the replication process, schema generation process, schema differential process, and bulk-load process.
JAVA_TRIGGER_DIR bprepl/repl_jtrig/

The folder name to where Java triggers are generated.
JOBRUNNER_LOG_FILE jobrunner Contains the name of file for logging job details during each jobrunner cycle. Date and log file suffix are appended to name. It is used by Repllogchk.
LOG_ALERT_DAILY_LIMIT 10

Sets the daily limit on replication log generation process.
LOGICAL_DELETE_TABLES XXX_so_mstr,XXX_sod_det

A comma delimited list of table names that are logically deleted, as opposed to physically deleted, from the target database

.
LOG_DIRECTORY bprepl/repl_log

The folder location of Pro2 log files.
LOG_FILE_SUFFIX .log

An extension used for Pro2 log file names.
LOG_RETENTION_DAYS 10

Sets the maximum number of days that a log file is stored before being purged from the disk.
MASS_LOAD_DIRECTORY bprepl/repl_mproc

This property designates the folder that Pro2 Bulk Load procedures are generated.
MASS_LOAD_LOG_DIR bprepl/repl_mproclog

Designates the Bulk Load log files storage folder location.
MASS_LOAD_TEMPLATE tmpl_mreplproc_restart-auto-push.p

Sets the name of the template procedure that is used during the bulk-load generation.
MASS_LOAD_TEMPLATE_PRO2ORA tmpl_mreplproc_oracle.p

Sets the name of the template procedure that is used during the bulk-load procedure for a target Oracle database. If this property does not exist, then the template is considered present on the “MASS_LOAD_TEMPLATE” property.
MASS_LOAD_TEMPLATE_PRO2PRO tmpl_mreplproc_pro2pro.p

Sets the name of the template procedure that is used during the bulk-load generation when the source as well as target databases belong to OpenEdge. If this property does not exist, then the template is considered present on the “MASS_LOAD_TEMPLATE” property.
MASS_LOAD_TEMPLATE_PRO2SQL tmpl_mreplproc_restart-auto-push.p

Sets the name of the template procedure that is used during the bulk-load generation for a target Microsoft SQL database. If this property does not exist then the template is considered present on the “MASS_LOAD_TEMPLATE” property.
MAX_CHAR_WIDTH 250

Sets the maximum character width character width for the source precession field at the time of SQL or Oracle generation and differential
MAX_DEC_PREC 38 Maximum number of positions to the right of the decimal when generating a target schema or differential for Microsoft SQL Server or Oracle.
MERGED_TRIGGER_TEMPLATE tmpl_mrgdtrig.i

Contains the default information required to list tables that require merged triggers.
MERGED_TRIG_DIRECTORY bprepl/repl_mgtrig

Contains the directory listing tables of merged trigger procedures.
MERGED_TRIG_TEMPLATE tmpl_mrgdtrig.i

The name of the template that is used to generate merged triggers.
MSS_DB_PF MSS-DB-EXAMPLE.pf
Example .pf file for Microsoft SQL server database connections for the Pro2 user interface. This example file can be used to automatically generate a database .pf file after all values of the source and target page are passed from the manage replication wizard.
Note: Actual .pf file should be named after the logical database name.
ORA_DB_PF ORA-DB-EXAMPLE.pf
Example .pf file for Oracle database connections for Pro2 user interface. This example file can be used to automatically generate a database .pf file after all values of the source and target page are passed from the manage replication wizard.
Note: Actual .pf file should be named after the logical database name.
ORACLE_NATIVE_ROWID NO If the property exists and contains a value of "YES", the Pro2Oracle SQL/Differential generator changes the standard output to:
  1. Suppress output the progress_recid column
  2. Suppress output the progress_recid index
  3. Suppress output of the target table specific sequence definitions
  4. The datatype for prrowid changes from varchar2(36) to number
OUTPUT_BASENAME replproc

Contains the replication processorlog file name. The times tamp, queue, thread number, and log file suffix are appended to the base file name, for example: replproc20210209-1.log.
OUTPUT_BASENAME_REPLCDC replcdcproc Contains the Replication-CDC processor log file name. The time stamp, queue thread number, and log file suffix are appended to the base name, for example: replproc20210209-1.log.
PF_DIRECTORY bprepl/Scripts

Directory containing the .pf files, scripts, and shortcuts to start the Pro2 web user interface, replication processors, and bulk-load procedures.
PRO2_SYNC_DIRECTORY bprepl/repl_pro2dbtrigs Contains the folder path which is used in the utils/ReplPro2TrigInsert.p program to insert triggers into Pro2 sync tables.
PRO2_SYNC_TABLES
  • Repl_Control
  • Repl_CustDefs
  • Repl_CustFlds
  • Repl_DBXref
  • Repl_TableXref
  • Repl_FieldXref
  • Repl_Properties
  • Repl_ThreadControl
 Used in utils/Replpro2TrigInsert.p and utils/Replpro2TrigDelete.p program files which are used to delete or insert the replication triggers from Pro2 database tables.
PROC_DIRECTORY bprepl/repl_proc

Sets the operating system directory where the replication processor procedure library is located.
PROC_CDC_DIRECTORY bprepl/replcdc_proc Sets the operating system directory where the Replication-CDC processor procedure library is located.
PROC_CDC_TEMPLATE tmpl_replcdcproc.p Sets the name of the template procedure that is used during the creation of the Replication-CDC procedure library for a LAN configuration.
PROC_CDC_TEMPLATE_PRO2ORA tmpl_replcdcproc.p The name of the template that is used to generate Replication-CDC procedures for Oracle based target databases. If this property does not exist, then the template is considered present on the “PROC_CDC_TEMPLATE” property.
PROC_CDC_TEMPLATE_PRO2PRO tmpl_replcdcproc.p The name of the template that is used to generate replication procedures for OpenEdge based target databases. If this property does not exist, then the template is considered present on the “PROC_CDC_TEMPLATE” property.
PROC_CDC_TEMPLATE_PRO2SQL tmpl_replcdcproc.p The name of the template that is used to generate replication procedures for Microsoft SQL Server based target databases. If this property does not exist, then the template is considered present on the “PROC_CDC_TEMPLATE” property.
PROGRESS_DB_PF PRO-DB-EXAMPLE.pf
Example .pf file for OpenEdge database connections for Pro2 user interface. This example file can be used to automatically generate a database .pf file after all values of the source and target page are passed from the manage replication wizard.
Note: Actual .pf file should be named after the logical database name.
PROC_TEMPLATE tmpl_replproc.p

Sets the name of the template procedure used during the creation of the replication procedure library.
PROC_TEMPLATE_PRO2SQL tmpl_replproc.p

The name of the template that is used to generate replication procedures for Microsoft SQL Server based targets. If this property does not exist, then the template is considered present on the “PROC_TEMPLATE” property.
PROC_TEMPLATE_PRO2ORA tmpl_replproc.p

The name of the template that is used to generate replication procedures for Oracle based targets. If this property does not exist, then the template is considered present on the “PROC_TEMPLATE” property.
PROC_TEMPLATE_PRO2PRO tmpl_replproc_pro2pro.p

The name of the template that is used to generate replication procedures for OpenEdge based targets. If this property does not exist, then the template is considered present on the “PROC_TEMPLATE” property.
PRROWID_ADD_DB NO

When this property is set to YES Pro2 prefixes the source database name to the PRROWID column that is stored in the target database.
REFRESH_DASHBOARD 60

Sets the refresh time interval for the Pro2 user interface dashboard.

REFRESH_REPLICATION_INTERVAL 60

Sets the refresh time interval for the replication threads on the Pro2 user interface dashboard.
REPL_RESTART_ON_SKIPPED YES Use this property to indicate if a thread should go through the replqueue before attempting to reprocess skipped events.

Threads check for shutdown events every 1000 reads of the replqueue table. If set to YES, during the shutdown check the thread indicates in the thread log that REPL_RESTART_ON_SKIPPED is enabled and leaves the replqueue processing block. It then goes through the standard sleep interval and restarts processing from the top of the queue, oldest records first. The property is set to YES by default.
REFRESH_WATCHBOXES 60

Sets the refresh time interval for all the Watchboxes present on the Pro2 user interface dashboard.
REPL_LOG_BASENAME
  • repllog
  • replproc

Contains the name of file for logging replication of records during each replication cycle. Date, queue thread number, and log file suffix are appended to name for example: repllog20210209-1.log.
REPLCDC_LOG_BASENAME
  • replcdclog
  • replcdcproc
 Contains the name of file for logging Replication-CDC of records during each replication cycle. Database name, Date, queue thread number, and log file suffix are appended to the file name. For example replcdclog_sports_20210308-1.log, replcdclog_qaddb_20210308-1.log.
SCHEMA_DEL_DIRECTORY bprepl/repl_d

Contains the directory for the Pro2 generated database replication delete trigger procedures.
SCHEMA_WRI_DIRECTORY bprepl/repl_w

Contains the directory for the Pro2 generated database replication write trigger procedures.
SMTP_AUTH username, password
Contains the username and password authentication details for email alerts.
Note: The username and password details must be separated by a comma.
SMTP_DEBUG NO

When this property is set to YES a debug log for troubleshooting email send issues is created in the bprepl/repl_log folder.
STATUS_CHECK_DEBUG NO

When this property is set to YES a debug log for troubleshooting the status check procedures is created in the bprepl/repl_log folder.
STATUS_CHECK_MAXQUEUECNT 10 Used in the status check function, this property sets the number of rows per thread for the replqueue count.
STATUS_CHECK_MAXCDCCNT 10 Used in the status check function, this property sets the number of rows per thread for the CDC queue count.
SQL_DIRECTORY bprepl/repl_sql

Directory for the direct Microsoft SQL assign include files, bulk copy procedures and replication procedures. Directory to store the delta .df file for Pro2 to Pro2 databases, SQL generation and differential, generate linked server SQL, and more.
SQL_EXCLUDE_LIST
  • ReplControl
  • ReplCustAsgn
  • ReplCustDefs
  • ReplCustFlds
  • ReplDBXRef
  • ReplFieldXRef
  • ReplProperties
  • ReplQueue
  • ReplTableXRef
  • ReplThreadControl

Contains the excluded list of tables in the MS SQL database.

TEMPLATE_DIRECTORY bprepl/repl_tmpl

Directory containing the templates used for various code generation such as the bulk-load procedure, replication procedure, and more.
TRIGGER_FORCE_LOWERCASE NO

When this property is set to YES the file names that are used for trigger generation are set to lower case and the case of the source table names is ignored.
TGT_USE_LITERAL_NAMES NO

Property to use the same naming convention as the source database for tables and columns without modifying them to meet the requirements of the target database (SQL only).
TRIGGER_EXTENSION .t

The extension that is used when Pro2 trigger files are generated.
THREADACT_DETAIL_MINUTES 30 This property is used to assign the DETUNIT field from thread activity details table.
USE_3RD_PARTY_EMAIL NO

When this property is set to YES Pro2 calls bprepl/Scripts/mail.bat or mail.sh. These files contain third party specific email calls.
USE_SQL_TRIGGERS NO

This property is used for backwards compatibility with data servers that require SQL triggers for maintaining the PROGRESS_RECID column.
VARCHAR_TYPE varchar This property is used to generate the field type with a property value at the time of SQL or Oracle schema generation, for example: varchar or nvarchar.
WRITE_TRIG_DIRECTORY bprepl/repl_w

Sets the operating system directory where the REPLICATION-WRITE trigger procedures are located.
WRI_TRIG_TEMPLATE tplt_repltrig.p

Contains the template file used by GenReplTrigs.p to create the replication triggers.
Table 2. WAN only properties
Property Default Value Description
APPSRV_CDC_PROC_TEMPLATE tmpl_asCDCTgtDb.p Sets the name of the template procedure that is used during the creation of the Replication-CDC procedure library for a WAN configuration.
APPSRV_FETCH_WITH_LOCK NO If this property value is YES, then an exclusive record lock is initiated while the record is fetched from the application server.
APPSRV_GET_PROGS_DIR bprepl/AppSrv/as_mproc

Stores the WAN process libraries.
APPSRV_LOG_DIRECTORY bprepl/repl_log

Stores the Pro2 application server log file on the source database server.

APPSRV_LOG_FILE appsrv.log

Sets the name of the Pro2 application server log file on the source DB server.
APPSRV_MASS_LOAD_DIRECTORY bprepl/AppSrv/as_mproc

Stores the details of a bulk-load procedure on the Pro2 server.
APPSRV_MASS_LOAD_TEMPLATE tmpl_ASmproc.p

Contains the default information used in generating WAN bulk-load procedures.
APPSRV_PROC_DIR_TGTDB bprepl/repl_as_tgt

Contains details of WAN replication procedures on the Pro2 server.

APPSRV_PROC_TEMPLATE tmpl_asTgtDb.p

Contains default information used in generating WAN replication procedures.

ASCII_BULK_EXP_DATA_FULL_PATH /apps/Pro2/XXX/bprepl/repl_export/data

Contains the location on target database server of ASCII bulk export data files.
ASCII_BULK_EXP_DIR /apps/Pro2/XXX/bprepl/repl_export

Sets the Bulk export root directory.
ASCII_BULK_LOAD_DATA_FULLPATH C:\Pro2\XXX\bprepl\repl_export\data

Contains the location of the target database server for ASCII bulk export data files.
ASCII_BULK_TGT_ROOT_DIR C:\Pro2\XXX

Contains the location of the target database server for ASCII bulk load SQL scripts.
APPSRV_FETCH_COUNT 1000

Specifies how many records are sent across a WAN connection to the Pro2 server at each replqueue records request.
APPSRV_FETCH_COUNT_MASS_BULK 50000

Specifies the number of bulk-load replications that are sent across the WAN connection to the Pro2 server at each replqueue records request.
APPSRV_QUEUE_COMPRESSION NO

Enables or disables queue compression for replication threads for WAN configuration.
APPSRV_FETCH_WITH_LOCK NO If this property value is YES, then an exclusive record lock is initiated while the record is fetched from the source database, otherwise the record is fetched with out being locked.
Oracle_Bulk_Transaction_Count 25 This property is used only in bulk-load WAN programs such as tmpl_ASmproc_oracle. You can use this property to set the limit of transactions to the property value.