Example: Defining TimesTen Replication in a Scalable Subscriber Configuration

This procedure defines the TimesTen replication.

1. Define the replicated data stores.

   On the master node and on both cluster nodes that host the subscriber service, add the following lines to the /timesten/TimesTen/info/sys.odbc.ini file.

   [replicated]
   DataStore=/timesten/data/replicated
   PermSize=64
   DatabaseCharacterSet=WE8MSWIN1252

2. Define the datastore content on the node that hosts the master server, including a user with administrative permissions.

   zone1$ ttIsql replicated
   Command> create table 
   t1 (col1 integer not null, col2 varchar(30), primary key (col1));
   Command> CREATE REPLICATION repscheme
          > ELEMENT complete DATASTORE
          > MASTER replicated on "master-host"
          > subscriber replicated on "zone1"
          > subscriber replicated on "zone2";
   
   Command> CALL ttRepStart;
   Command> create user repl identified by 'repl';
   Command> grant admin to repl;

3. Duplicate the data store replicated to the subscriber node and start the replication agent.

   zone1$ ttRepAdmin -duplicate -from replicated \
   > -host master-host -uid repl -pwd repl "dsn=replicated"
   zone1$  ttIsql -e "call ttrepstart;exit;" active
   
   zone2$ ttRepAdmin -duplicate -from replicated \
   > -host master-host -uid repl -pwd repl "dsn=replicated"
   zone2$  ttIsql -e "call ttrepstart;exit;" active

4. Define the replication policy on all hosts.

   zone1$ ttAdmin -repPolicy always active
   zone2$ ttAdmin -repPolicy always active