Install and configure Pro2 for WAN

A WAN configuration for Pro2 and your OpenEdge application is best suited for cloud-based business solutions across multiple geographies. For example, assume that you have OpenEdge applications and databases spread across the US, Europe, and Asia, with a consolidated Microsoft SQL Server database in the US that is used for reporting and analytics. In this configuration, the source databases spread across the globe communicate with an application server that in turn, sends data to the target Microsoft SQL Server database.

You can install Pro2 along side of OpenEdge during your initial setup and configuration, or you can install Pro2 as an add-on to complement your OpenEdge environment later on. Installing Pro2 as an add-on can be especially useful when you are upgrading OpenEdge versions, or need to migrate databases. For more information about database migration, see Migrate your OpenEdge database with Pro2.

If you are installing Pro2 along with OpenEdge, then you will need to first install and configure OpenEdge, after the installation and configuration is complete, you then install and configure Pro2.

The Pro2 WAN configuration setup differs from the LAN configuration process in that, after the initial installation of Pro2, you must configure the application server before you can set replication configurations for your Pro2 instances. Moreover, unlike the LAN configuration, the source database does not directly communicate changes to the replication and target databases. The source database is connected to a Progress Application Server instance, which is then connected to an empty synchronized-copy of the replication database that connects to the Pro2 facing replication database.

System requirements

These are minimum recommendations. All parameters can be increased to accommodate more robust hardware.

For more information about OpenEdge system requirements, see the Progress Platform Compatibility Guide.

Before you begin

Ensure that you have OpenEdge installed and configured on the same machine as Pro2. For more information about installing OpenEdge, see Install OpenEdge on Windows.

Main steps to install and configure Pro2

Install Pro2

1. Close all applications before beginning the installation.
2. Locate and execute the Pro2.exe file.
   There can be a numeric value in the file name that indicates the version of Pro2, for example, Pro2-6.5.0.exe.

   Note: Starting with Pro2 6.5.2, after locating the Pro2.exe file, run the following command from the command prompt:

   Pro2.exe LAX_VM "C:\<JAVA_HOME>\bin\java.exe"

   The supported Java version is Java 11 and Java 17.
3. In the Pro2 installation wizard, click Next. The Choose the Install Folderscreen appears.
4. Specify the path or click Choose to browse and select where you want to install Pro2.

   The default installation directory is C:\Progress\Pro2.

5. In the Choose OpenEdge window, specify the path, or select Choose to browse and set the OpenEdge home directory.

   The OpenEdge home directory is where OpenEdge is installed on your machine.

   The default directory is C:\Progress\OpenEdge.

6. On the PAS Ports screen, enter the relevant PAS for OpenEdge information in the Port and Instance Name fields.

   The default instance name is Pro2Web. You can change this name to according to your needs. It is recommended to change the instance name for each Pro2 installation.

   Note: For each installation of Pro2, you must specify different port information. No two installations can use the same ports on the same machine.
7. Click Next and review the options you chose for this installation on the Pre-Installation Summary page.
8. Click Install to continue with the installation process.
   Note: The Pro2 installation wizard can take several minutes to complete and may appear to lag at times. Allow the installation wizard to complete before prematurely canceling the process.
9. Click Done to finish the installation process.
10. Check the installation logs at C:\Progress\Pro2\install\logs folder.

After the installation is complete, go to the Pro2 AS_Src root folder to continue the configuration process. If you used the default settings during the installation, then this folder would be C:\Progress\Pro2\bprelp\AppSrv\AS_Src. Copy this folder to the machine where you have your source database, and rename the folder.

All files, scripts, and procedures for Pro2 are relative to the root folder. This allows for Pro2 to be installed several times on the same drive without each installation interfering with each other. This functionality was designed to allow you the be able to create development and production environments to test implementations as needed without the risk affecting your production environment.

Create and configure a Repl database for WAN

On this step of the configuration process you create a WAN side Repl database. This Repl database is hosted on the same machine as your source database and communicates directly with the source database and the WAN application server.

It is important to note that this procedure describes the high level steps to create the WAN side Repl database. Later in the configuration process, you will need to create another Repl database on the same machine as your Pro2 database and Pro2 installation. When creating these databases every consideration and precaution should be taken, as if you were creating a database for an enterprise application in a production environment, to ensure their availability. Without these databases, data is not replicated from your source database to your target database. This can cause loss of synchronization.

Create and configure a WAN application server

Creating your WAN application server can vary widely depending on your specific business needs and application environment. In general, creating a PAS for OpenEdge instance involves defining a name and location for the instance as well as defining various configuration properties. When you create an instance, the properties of the instance are automatically set to the directory where the new instance is created and the related files and logs are stored. The following properties are set when the new instance is created and can be controlled by the system administrator:

• The environment variables and paths for running commands
• The HTTP and HTTPS transports, and ports
• The username and password for the instance
• The type of instance (development or production)

For more information about PAS for OpenEdge, see Learn about PAS for OpenEdge administration.

To create and configure a WAN application server:

For more information about the OpenEdge properties command (oeprop), see OEPROP.

Create a Repl and Pro2 database:

While similar to the Repl database that you created earlier, this Repl database is hosted on the same machine as your Pro2 installation. You build a Repl database by using Proenv commands and the repl.df file.

Before you create your replication database, navigate back to the machine where you have Pro2 installed. This machine should be different than your source database machine where your PAS for OpenEdge instance is configured.

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 db folder of the Pro2 root folder. If you are using replication triggers with a LAN configuration, all 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. Change data capture (CDC) is not affected by this requirement.

It is important to note that this procedure describes the high level steps to create the Repl and Pro2 databases. When creating these databases every consideration and precaution should be taken, as if you were creating a database for an enterprise application in a production environment, to ensure their availability. Without these databases, data is not replicated from your source database to your target database. This can cause loss of synchronization.

Confer with your database administrator and other key stakeholders to when creating the Repl and Pro2 database for your production environment. For more information about database administration, see OpenEdge database essentials.

To create a Repl and Pro2 database:

1. Open a Proenv instance.
2. Set your working directory to the db folder in the Pro2 root directory.
   Note: Check the directory of the db folder to view the database instances. Type dir after navigating to the database folder.
3. Create an empty repl database instance by typing the following command prodb repl empty.
4. Create an empty Pro2 database instance by typing the following command prodb pro2 empty.
   Note: Ensure that the you set the code page of the Repl and Pro2 databases to match the code page of your source and target databases.
5. Load the table definitions file in the Repl database by typing prowin repl -1.

   The Procedure Editor window appears.

6. Navigate to Tools > Data Administration.
7. In the Data Administration window, navigate to Admin > Load Data and Definitions > Data Definitions (.df file)….
8. In the Load Data Definitions window, load the repl.df file and click OK.
   Note: The repl.df file is located in the db folder of the Pro2 root folder.
9. Load table definitions in the Pro2 database by entering prowin pro2 -1 -p _admin.

   The Data Administration window appears.

10. In the Data Administration window, navigate to Admin > Load Data and Definitions > Data Definitions (.df file).
11. 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.
12. Start the repl and pro2 databases by typing:
    • Proserve repl
    • Proserve pro2
13. Add the Pro2 database connection details to the replProc.pf file in the Pro2 root folder under \bprepl\Scripts\replProc.pf 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.
    The following is the example.pf parameter file that you can use as a reference for database connections in Pro2.

    # Example PF File for Database Connections for Pro2 Tool # Actual .pf file should be named after the logical name # for the Source database connection. # Source Databases go here (Required for MSS/ORACLE/PROGRESS as target type). -db example -ld example -H remotehost -S src-port # Schema Holder Databases go here. # If not built yet then just comment out all lines. (Required for MSS/ORA/PROGRESS as target type) -db c:\Pro2SQL\db\exsh -ld examplesh -RO # Schema Images go here. # If not imported yet, then just comment out all lines. -db exodbc # Required MSS/ORA -ld examplesql # Required MSS/ORA # Required MSS/ORA value should be (MSS/ORACLE) # For Oracle Target type need to enter username and password -dt <TGT_TYPE> -U Username -P Password -Dsrv QT_CACHE_SIZE,30000 #Required for MSS and ORA target type in other type just comment it -Dsrv TXN_ISOLATION,1 #Required for MSS target type in other type just comment it # -Dsrv BINDING,0 #Removed for v11 -Dsrv AUTOCOMMIT,1 #Required for MSS target type only -Dsrv PRGRS_PREPCACHE,100 #Required for MSS target type only -Dsrv MSS_PRESERVE_CURS,1 #Required for MSS target type only -Dsrv PRGRS_LOCK_ERRORS,08501 #Required for MSS target type only -Dsrv logginglevel,0,svub,1 #This will reduce the DataServer Log output Required for ORA/MSS #Added below to release locks earlier -Dsrv PRGRS_NATIVE_LOCKWAIT,0 #Required for MSS target type only -Dsrv PRGRS_NOWAIT_OVERRIDE,1 #Required for MSS target type only

14. To check that both the Repl and Pro2 database instances are connected, open the Pro2 Editor from the bprepl\Scripts folder and navigate to Tools > Data Dictionary. If the connection is successful, then the Tables section displays the tables.

Create an empty local copy of the source database

Embed the repl tables (optional)

You can choose to embed the repl tables into your source and source copy database. Embedding the repl tables into the source database and source copy database can simplify implementation. If the repl tables are embedded, no additional database connection is be required. One major reason to choose to keep repl as a stand-alone database is to simplify schema updates made by the application provider to the source database. Pro2 works the same whether the repl tables are embedded or in a separate stand-alone 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 Pro2v62.
3. Enter instance name\bin\tcman.bat env.
   Note: The default instance name is Pro2Web.
4. Type instance name\bin\tcman.bat start.
5. To verify that the instance 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 login credentials, where the default username and password are both set to admin.
   Note: It is strongly recommended to change the default credentials immediately after the initial login. Update the password to a strong, unique value to prevent unauthorized access and ensure security.

Load the configuration file

To load the configuration file:

1. In the Pro2 web interface, navigate to Actions > Tools > Load Configuration.
2. Click Select Files and load the .ini configuration file, for example replbasev610.ini, from the Pro2 folder.
3. Click Submit. A success or failure notification is displayed after the upload is complete.

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

Connect to your WAN application server instance

After the properties are loaded, you must connect to your WAN PAS for OpenEdge instance from the Pro2 user interface.

Start the job runner

1. Navigate to the Pro2 Scripts folder, for example: C:\Pro2\bprepl\Scripts.
2. Select and execute the jobrunner.bat file.
3. Navigate back to the web interface and confirm that the jobrunner.bat is running by checking the status in the Pending Jobs watch-box.

Add the source database details

You can set up either trigger-based replication or CDC-based replication. In a trigger-based-replication, the replication queue records (also known as ReplQueue records) are generated by deploying Pro2 triggers on a source database. In a CDC-based replication the ReplQueue records are generated from change tracking table. However, for CDC-based replication, the source database must be CDC enabled.

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. (Optional) Enter your User Name and Password.
   Note: Enter your user name and password only if it is required by your source database.
4. 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.

5. Click Next.

Generate and load the source schema file

By generating the source schema file, you build the files necessary to enable your local empty copy of your source database to communicate with the application server-side source database.

Add the target database details

The target database can be either a Microsoft SQL Server, Oracle database, or OpenEdge database. If your target database is an OpenEdge database, the you can forgo some of the configuration processes like generating the schema holder. However, there for a Microsoft SQL Server or Oracle database there are several configuration considerations to take into account. For more information about configuring Microsoft SQL Server or Oracle as a target database, see Configure Pro2 to target SQL database connectivity.

To add target database details:

1. Select Target Database Type. Choose Microsoft SQL Server, Oracle database, or OpenEdge databases.
2. Following fields are automatically filled, but can be changed if necessary
   • Target Database Name
   • Target Schema Image
   • Schema Holder DB
   • Target ODBC Connection
3. (Optional) Enter your user name and password.
   Note: Entering your user name and password only if it is required by your target database.
4. Click Next.

   The Generate Target Schema tab appears.

Generate the target schema file

By generating the target schema file, you load the target database with files necessary to build out the target database. Pro2 reads the source database schema, and generates scripts that are then executed on the target database server to create the target schema. By default, all tables and fields are created in the target. The rest of the files (drop.sql, index.sql, trunc.sql, errors.log, and warnings.log) are created separately. You can execute these files as necessary. Typically, tables that are not replicated remain unmapped.

Pro2 reads the source Progress schema and generates scripts that are then executed on the target database server to create the target schema. By default, all tables and fields are created in the target. Typically, tables not replicated remain in the target bur are simply not mapped for replication, however, if it is desired that the tables do not exist at all on the target side, the generated scripts can be edited to remove the pertinent statements.

To generate target schema file:

1. Click Generate Target Schema. A table that contains a replication job appears.
   Note: Do not execute this job until you run the job runner file. A job runner batch file continuously processes replication jobs from the job queue. This file is in the Scripts folder.
2. Click Download under the Download Schema files column, to download the target schema files.

Create a target database

If you have not done so already, create a target database for you replicated data. The target database can be either a Microsoft SQL Server, Oracle, or OpenEdge database. Creating a target database will depend largely on they type of database you want to use and your development tooling. The following lists the general steps to create your target database:

For more information about target databases, see

Create a schema holder for your target database

An empty OpenEdge database is created to act as the schema holder for the Microsoft SQL Server or an Oracle database. The schema holder is the layer that allows ABL to interact with the Microsoft SQL Server or Oracle database as though it were a native OpenEdge database.

To create a schema holder:

1. Open a Proenv window, and type prodb database name empty to create an empty schema holder database.
2. Start a single user session by typing prowin database name -1.

   The Procedure Editor window appears.

3. From the Procedure Editor, select Tools > Data Administration.
4. Select DataServer > database type Utilities > Create DataServer Schema .

   The Create/Modify Record for Schema window appears.

5. Specify the Logical Database Name.
6. If the source database is a SQL Server, specify the ODBC Data Source Name. Click OK.
7. Enter the login ID and password if required in the next dialog box and click OK.
8. Enter criteria for Object Name, Object Owner (typically, dbo), and Qualifier.
9. Select the Default to OpenEdge DATETIME option.
10. If you are using LOB fields in replication, ensure that the Default to OpenEdge LOB for BLOBs option is selected along with the CLOBs option. This forces the data server to automatically consider certain target side data types to be treated as LOBs.

    By selecting CLOBs, varchar(max)/nvarchar(max) data types are automatically converted to CLOBs. By selecting BLOBs the data server is forced to consider all varbinary(max) as BLOBs. On 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)/nvarchar(max) are not necessarily treated as CLOBs.

    
    
    
11. Click OK to finish.

Load the target database table definitions

After the target schema file is downloaded, load the target database with the appropriate tables required for replication.

For OpenEdge target databases:

1. Copy and paste the target schema file in the db folder of Pro2.
2. Open a Proenv window, enter prowin target database name.
3. In the Procedure Editor, select Tools > Data Administration.
4. Select Admin > Load Data and Definitions > Data Definitions (.df file)
5. Add the target schema fileas the Input File and click OK.
6. Navigate to the Pro2 web interface and click Next.

   The Mapping Source to Target Tables tab appears.

Map tables and fields

You must map data fields between your source and target database so that data in the source can be replicated to the target. You can do this from the Mapping dashboard in the web interface. The repl database contains all the mapping information for the replication of the databases, tables, and fields between the source and target. This information is stored in the ReplDBXref, ReplTableXref, and ReplFieldXref tables. Mapping information can be saved to and loaded from a text file.

Depending on the number of schemas, primary keys, and foreign keys of the databases, the data sources and the database mapping information has varying degrees of complexity.

Map source tables to target tables and generate code

To map source tables to target tables and generate code:

1. On the Mapping Source to Target Tables tab, select the tables from the source database that you want to map with the target database. You can map the tables in the following ways:
   • Map—Choose the Map option if you want to map a single source table with a single target table.
   • Automap—Choose the Automap option if you want to map one or more source tables to the corresponding target tables.
   Note: You can also unmap the tables based on your needs using the Unmap option.
2. Select the tables to map, click Automap, and click Next.
3. In the Advanced Configuration tab, change thread assignments and other optional control flags if required.
   Note: The Advanced Configuration tab is an optional settings tab.
4. Click Next.

   The Generate Code tab appears.

5. Click Generate Code. You are directed to the Pro2 web interface dashboard. Click the Pending Jobs watch-box to see which replication jobs are running.
6. Run the replication file to execute the replication jobs. In Windows Explorer, navigate to \bprepl\Scripts.
7. Double-click the Replbatch1.bat file.

   The corresponding replication thread starts running on the Dashboard.

   Note: In a CDC-based replication, double-click the CDCbatch.bat file.
8. Refresh the Pro2 user interface to complete the replication configuration process.

Manually test a replication

Testing is an important part of any enterprise applications configuration process. Consider an testing example where a city is assigned to a customer. This change is made in the source database, and needs to be replicated to the target database. To perform the test scenario:

1. In a Proenv window, navigate to your Pro2 root folder. For example, C:\Pro2v62\db.
2. Enter the command prowin -db database name -db repl.

   The Procedure Editor window appears.

3. Assign city to the first customer in source database.

   FIND FIRST customer
   ASSIGN city = “NY”
   

4. Open the Pro2 web interface and click the Total Threads watch-box. Notice the event type in the Replication thread window. This event will show the recent change made to the source database.
   
   
   
5. Run the replication file by navigating to \bprepl\Scripts .
6. Double click the Replbatch1.bat file to run the replication thread. This action removes the event type in the replication thread which implies that the replication record is processed by the replication thread and sent to the target database.
   
   
   

Directory reference

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

ReplProperties and ReplQueue