How to create a Replication target database for an existing database.

How to create a target replication enabled database from an existing database?
Fathom Replication Setup example.
OpenEdge Replication creating a target database example.
How to create a target database?

Steps to enable Site Replication on a database that is already running with After Imaging enabled.

Follow the rules and guidelines provided in the OpenEdge Replication Users Guide to customize replication requirements which should be verified and documented in a test environment before deploying to production.

1. Shut down live database.
$   proshut <databasename> -by
 
2. Take a full backup.
 
3a Copy the source replication configuration properties file  to the source database directory:
%DLC%\properties\source.repl.properties

3b Rename this file changing "source" to match the name of the database.
 
3c Edit the configuration properties. For detailed property descriptions please refer to the OpenEdge Replication: Users Guide.
 
Example:

[server]
    control-agents=agent1
    database=source
    transition=manual
    transition-timeout=600
    defer-agent-startup=900     ( This parameter is not available or supported in Replication 1.0A or 2.0A )
 
[control-agent.agent1]
   name=agent1
   database=target
   host=localhost
   port=4501
   connect-timeout=120
   replication-method=async
   critical=0

4a Copy the target replication configuration properties file  to the target database directory:
%DLC%\properties\target.repl.properties

4b Rename this file changing the database name to match the "target" database name.
 
4c  Edit the configuration properties. For detailed property descriptions please refer to the OpenEdge Replication: Users Guide.
 
Example:

[agent]
   name=agent1
   database=target
   listener-minport=4387
   listener-maxport=4500

5. Set the environmental variables (not required in 3.0A and later):

DSRHOME= installation directory FathomR.
PROCFG= %DLC%\progress.cfg
 
6. Enable the source database for replication:
 
$  proutil dbname –C enableSiteReplication source
 
7.Take a full backup of the source database in order to make the target replication enabled database:
 
Versions prior to 9.1E must use an offline backup method, otherwise an offline or online backup of the source can be taken in order to be used to establish the replication target baseline.
 
 Method 1 OFF-LINE:   
$  probkup D:\Applications\Replication\Origin\dbname dbnameS.bck

 Method 2 ON-LINE:  
$   proserve <source> -DBService replserv -S 5555 -n 150 -Mn 22 -L 100000  
$   probkup online D:\Applications\Replication\Origin\dbname dbnameS.bck –REPLTargetCreation
 
The online method requires the defer-agent-startup parameter has been used in the sourcel.repl.properties file and that the database  has been started for replication. Since OpenEdge 10.1B, replication can also be enabled online. Refer Article 000011697.
 
Considerations for deferred agent startup:

Schema updates are not allowed while the Fathom Replication server is performing synchronization.
If schema updates are being performed when failure recovery synchronization begins, source database updates will be blocked until failure recovery is complete.
Source database activity cannot continue without the agent(s) connected when synchronous replication is being used.
 
8.  With a .st file for the target database structure in target database directory, perform a restore using full backup created from either method listed above in step 7 to create the Target database.
 
$   prorest <target-name> <path>\dbnames.bck
 
9. Enable AI for the target database, if after imaging is required:
AI extents must be added using the prostrct add prior to enabling ai if the structure used for the PROREST did not include ai files.
$   rfutil dbname –C aimage begin -G 0

10. Enable replication for the target database:
$   proutil dbname –C enableSiteReplication target
 
11.  Start databases for replication adding the respective “-DBService” startup parameter. Ensure the -Mn, -n and -L parameters match, so that the transaction table is sufficiently sized at startup for the AI transaction notes to be applied from the source to the target database.
 
Example:

$   proserve <target> -DBService replagent -S 4501 -n 150 -Mn 22 -L 100000
$   proserve <source> -DBService replserv -S 5555 -n 150 -Mn 22 -L 100000
 
If the source has already been started, ensure that the Replication Agent is running or restart it:
$  dsrutil <source> -C restart server

References to Other Documentation:

OpenEdge Replication: Users Guide, "Implementing Fathom Replication" 

Progress Article(s):

000010538: "How does defer agent startup work?"
000011697: "What are the steps to enable OpenEdge Replication on a live database on OpenEdge 10.1B or later"
000020912: "How to configure databases when using multiple brokers and Progress Replication."   
"How To Add AI Extents in an Existing V9 or V10 Progress Database"