OpenEdge Management and OpenEdge Explorer: Configuration
OpenEdge Management and OpenEdge Explorer: Configuration
OpenEdge Management and OpenEdge Explorer: Configuration
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Configuring <strong>OpenEdge</strong> Databases<br />
Configuring an <strong>OpenEdge</strong> Replication-enabled database<br />
2–32<br />
To configure your source database <strong>and</strong> target database for <strong>OpenEdge</strong> Replication, you must<br />
configure the replication property files for both the <strong>OpenEdge</strong> Replication source database <strong>and</strong><br />
the <strong>OpenEdge</strong> Replication target database.<br />
In the <strong>OpenEdge</strong>-install-directory/properties folder, <strong>OpenEdge</strong> Replication provides two<br />
sample property files: source.repl.properties <strong>and</strong> target.repl.properties. You can save<br />
these files <strong>and</strong> modify them, using either <strong>OpenEdge</strong> <strong>Management</strong> or <strong>OpenEdge</strong> <strong>Explorer</strong>, or a<br />
text editor, so that you can use them with your source <strong>and</strong> target <strong>OpenEdge</strong> Replication<br />
databases. Because source.repl.properties <strong>and</strong> target.repl.properties are samples,<br />
some of the properties <strong>and</strong> values are generic; it is up to you to customize the properties to<br />
reflect the settings you want to use with your own source <strong>and</strong> target databases.<br />
When you use <strong>OpenEdge</strong> <strong>Management</strong> or <strong>OpenEdge</strong> <strong>Explorer</strong> to make configuration changes<br />
to the Replication server or Replication target properties, the changes are reflected in the<br />
applicable property file.<br />
Rules for setting properties for a Replication-enabled<br />
database<br />
From the management console, you can configure various properties for a database enabled for<br />
Replication. The options you have in the console for configuring these Replication-related<br />
properties depend upon the following rules:<br />
• For a database not enabled for Replication:<br />
– If the Replication property file does not exist, no Replication links are available.<br />
– If the Replication property file does exist but is empty, a Server (create new) link<br />
<strong>and</strong> an Agent (create new) link appear.<br />
Note: You can configure transition only when one of these groups exists.<br />
– If the Replication property file does exist <strong>and</strong> is not empty, then all groups defined<br />
in the property file appear.<br />
• For a database enabled for Replication:<br />
– If the Replication property file does not exist, Replication-related links still appear.<br />
However, you can create only the group for which the database is enabled. In other<br />
words, you can create the Server group for source-enabled databases <strong>and</strong> the Agent<br />
group for target-enabled databases.<br />
– If the Replication property file does exist, only the groups that are applicable to the<br />
database enablement appear. For source enablement, Server, ctrl-agents, <strong>and</strong><br />
transition appear. For target enablement, Agent <strong>and</strong> transition appear.<br />
– If the Transition group database-role is set to reverse, you either see the existing<br />
group for the reverse role or are allowed to create a new group for the reverse role.<br />
– If you specify Alternate buffer pool blocks for a Replication target database, the<br />
property setting is ignored.