Two-way replication
Two-way replication is the synchronizing ofdata so that if a change is made in the source database, the change can be viewed in the destination database. Meanwhile, if a change is made to the data in the destination database, the data in the source database is changed.

Realtime replication
Realtime replication is the ability to query by form and lookup by key. It's available as an add-on installation.

How it works
Replic-Action consists of two component tools the Replic-Action Composer and the Replic-Action Server. As you can see in Figure A, the Replic-Action server (or servers) is connected to both to the ODBC-compliant DBMS (Database Management System) databases on the right side and the Notes database on the left side.

FIGURE A


Replica-Action server sits between the Notes database and the DBMS ODBC-compliant databases. Roll over picture for a larger image.

The job of the server is to replicate the data from the source database or databases to the destination database.

The work of creating the Replic-Action jobs is accomplished using the Replic-Action Composer; the work of running the jobs is designated to the Replic-Action Server.

Someone's gotta do the work
A job in Replic-Action consists of first defining the objects and then creating the job. An object, in Replic-Action, could be a link, an include table, a data transformation, an action, or a rule. The objects you create are true objects in the sense they can be shared among several Replic-Action jobs. For example, once you define a link to a DBMS, that link object can be used in any Replic-Action job.

Casahl Technology has done a good job of making friendly, easy-to-use interfaces. Figure B shows the main menu.

FIGURE B


Components and applications are clearly placed in the main menu of the Replic-Action Composer. Roll over picture for a larger image.

On the left we have the navigator, divided into two sections: components and applications. On the right we have a categorized list of all the objects created. There is little ambiguity in selecting what you want.

Components: the building blocks of the job
Okay, so you want to create a job that will import the data now living in your outdated, antiquated DB2 database into your new enterprise Notes application. However, before creating the job or jobs, you must at least define the links and include tables; additionally other objects such as data transformations, rules, and actions may be needed. Note: a link is required for each database (whether it is a DBMS database or a Notes database) that you're going to use with a specific job.

The forms for each of the objects are easy to use and consistent throughout the software. Figure C shows the Link form.

FIGURE C


Form for defining the link object. Roll over picture for a larger image.

Next to most fields is a red question mark within a yellow balloon, as seen in Figure D. When clicked, it displays information for field requirements.

FIGURE D

In your application, you'd click on this icon to get more information about the field requirements.

For example, when you click on the question mark next to Link name, it tells you to enter a name for the link that does not exceed 32 characters.