Pro2 - How to deploy Pro2


Article Number000093512
EnvironmentProduct: OpenEdge
Version: All supported versions
Product: Pro2Ent, Pro2Pro, Pro2SQL, Pro2Ora
Version: All supported versions
OS: Windows
Question/Problem Description
How to deploy Pro2?
Can I deploy Pro2 on my own? 
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Currently Pro2 deployment requires a Professional Services engagement as each environment configuration is different and requires customizations. 

At a high level a Pro2 deployment with triggers requires the following steps:
  • Either create a repl db to hold the repl tables or embed repl tables in the source database.
  • Create a DSN for the target database  
  • Edit Pro2 pf files and configure it to connect to all databases(source, target, repl)
  • Generate the target creation SQL code via the Pro2 Admin utility.
  • Run the SQL code on the target side.
  • Create the DataServer schema holder and schema image.
  • Map the tables to be replicated in the Pro2 admin utility. 
  • Generate the processor and bulk-loader libraries.
  • Generate the triggers.
  • Place triggers in a location that the application clients have access to via their PROPATH( These are clients that access and modify the source).
  • Run the replTrigInsert.p to insert triggers into the new databases( Make sure there aren't any existing replication triggers as this will require the triggers to be merged)
  • Create tasks in the task scheduler to auto start the Pro2 threads. 
References to Other Documentation:

Further information can be found in the Pro2 user guide and implementation guide under the Pro2 install directory.  
Last Modified Date12/26/2018 3:56 PM

Did this article resolve your question/issue?


Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025