Modeling for Replication Server

PowerDesigner supports the modeling of all the components required to deploy a Replication Server solution in your environment.

Network Components

The PowerDesigner DMM provides support for the following network components when modeling a Replication Server environment:

Replication Servers – coordinate the data replication activities for the local data servers and exchange data with Replication servers at other sites. PowerDesigner models replication servers as replication processes (see Replication Processes (DMM)) with a Replication Server type and additional properties (see Replication Server Properties).
Primary and Replicate databases – contain data that will be replicated and receive replicated data respectively. The structure of each database is modeled in an attached PDM. PowerDesigner models databases in a Replication Server environment as standard databases (see Databases (DMM)) with additional properties (see Replication Server Primary Database Properties).
Servers – provide a logical location for replication servers and databases. You should associate all of your network components to appropriate servers to ensure correct script generation and a model check is used to verify that each component is associated to a server (see Servers (DMM)).

Data Connections

Network components are connected via the following kinds of data connections:

Connections– specify a message stream from a database to a Replication Server, or from a Replication Server to a database. PowerDesigner models connections as standard data connections (see Data Connections (DMM)) with additional properties (see Replication Server Connection Properties).
Routes – specify one-way message streams that send requests from one Replication Server to another. PowerDesigner models routes as standard process connections (see Process Connections (DMM)) with additional properties (see Replication Server Route Properties).
Logical Connections – consist of a pair of physical connections that are configured in a warm-standby environment (see Modeling a Warm Standby Application) to link an active and a standby database. PowerDesigner models logical connections as data connection groups (see Data Connection Groups (DMM)) with additional properties (see Replication Server Logical Connection Properties).

Replication Definitions

Replication definitions describe the tables, views, databases, and stored procedures that you want to replicate:

Replication definitions – describe a source table to be replicated, the columns you want to copy, and may also describe attributes of the destination table. Destination tables that match the specified characteristics can subscribe to the replication definition. PowerDesigner models Replication Server replication definitions as articles (see Articles (DMM)) with additional properties (see Replication Server Replication Definition and Article Properties).
Database replication definitions – allow you to replicate an entire primary database to one or more replicate databases. PowerDesigner models database replication definitions as publications (see Publications (DMM)) with a Database type and additional properties (see Replication Server Database Replication Definition Properties).
Function replication definitions – specify information about a stored procedure to replicate. PowerDesigner models function replication definitions as publication procedures (see Procedures (DMM)) with additional properties (see Replication Server Function Replication Definition Properties).
Articles – specify a replication definition extension for tables or stored procedures that allow you to assign table or function replication definitions in a publication. PowerDesigner models Replication Server articles as standard articles (see Articles (DMM)) with additional properties (see Replication Server Article Column Properties).

Publications and Subscriptions

Replication definitions are grouped together into publications that replicate databases can subscribe to:

Publications – collect replication definitions together, to simplify subscriptions. PowerDesigner models Replication Server publications as standard publications (see Publications (DMM)) with additional properties (see Replication Server Publication Properties).
Subscriptions – instruct Replication Server to replicate the data specified in a replication definition or publication to a particular replicate database. PowerDesigner models Replication Server subscriptions as standard subscriptions (see Subscriptions (DMM)) with additional properties (see Replication Server Subscription Properties).

Other Objects

These sub-objects are created inside a Replication Server object:

Users – specifies a user name and password to connect to a Replication Server. PowerDesigner models Replication Server users as standard users (see Users (DMM)) with additional properties (see Replication Server User Properties).
Function strings – contain instructions for executing a function in a database. PowerDesigner models Replication Server function strings as event scripts (see Event Scripts (DMM)) with additional properties (see Replication Server Function String Properties).

Creating a Basic Replication Server Environment with the Replication Wizard
The replication wizard provides a quick way to configure a Replication Server process for replicating one database to another. You can replicate the entire database or choose specific tables to replicate. You can run the wizard as many times as necessary to create additional replications on a single or multiple Replication Servers.
Completing your Replication Environment
Once you have created any appropriate replication processes, replication definitions, publications and subscriptions with the replication wizard, you should complete your environment with the following kinds of supporting objects.
Modeling for Heterogeneous Replications with Replication Agents and ECDA
Heterogeneous databases are databases other than Sybase Adaptive Server Enterprise or Adaptive Server Anywhere/SQL Anywhere®. Replication agents allow Replication Server to communicate with heterogeneous primary databases.
Modeling a Warm Standby Application
A warm standby application is a pair of Adaptive Server or SQL Server databases, one of which is a backup of the other. Client applications update the active database, and Replication Server maintains the standby database as a copy of the active database.
Modeling for Mirror Activator
Mirror Activator is a combination of Mirror Replication Agent, Replication Server, and a third party disk replication system to add disk replication for transaction logs to the Replication Server transaction-based replication to provide an optimal disaster recovery solution.
Modeling for RepConnector
RepConnector™ allows you to use Sybase Real-Time Data Services to capture transactions in an ASE database and deliver them as events to external applications in real time. PowerDesigner supports modeling for replication environments in which RepConnector is deployed, but does not generate specific orders for RepConnector itself.
Modeling for High Volume Adaptive Replication (HVAR)
For Replication Server v15.5 and higher, PowerDesigner supports modeling for HVAR, whereby log-ordered, row-by-row changes are compiled into net-row changes.
Modeling for Multi-Path Replication
Replication Server v15.7 and higher supports multi-path replication™ of Adaptive Server Enterprise v15.7 and higher primary databases to increase replication throughput and performance, and reduce contention.
Modeling for SQL Statement Replication
For Replication Server v15.2 and higher, PowerDesigner supports modeling for SQL statement replication.
Modeling Replications to an SAP® Sybase® IQ Data Warehouse
SAP® Sybase® IQ (IQ) is a high-performance decision support server designed specifically for data warehousing. Since IQ is not optimized for inserting, updating and deleting row by row, you should implement a staging database to replicate data from OLTP databases to an IQ data warehouse.
Replication Server Object Properties
When modeling for a Replication Server environment, you use standard DMM objects with additional properties.

Parent topic: Working with SAP® Sybase® Replication Server®