Use Case I – Central Configuration
In central configuration, Data Director is installed in one central location accessible to head office and all store databases. The DD Services will be created in this machine which will cater to head office as well as to all the stores.
FIGURE 7.5 -1: CENTRAL CONFIGURATION
In this configuration all the distribution locations will be defined in the database from where the job will be initiated and the database should have the distribution location card defined for source and destination database and at the distribution location for source (for example head office) should contain the DD Service which is catering to source database (DD HO) and similarly for stores also.
Use Case II – Split Configuration
In Split configuration, Data Director is installed at head office as well as at stores. The DD service catering to stores will be created at stores and services catering to head office will be created at head office. In this configuration, data should be pushed from source to destination.
FIGURE 7.5 -2: SPLIT CONFIGURATION
To push data from source to destination, the distribution location for source as well as for destination database should be defined in source database. The distribution location for store should contain DD service running at store and distribution location for head office should contain DD Service running at head office. Distribution locations should be defined absolutely in the same way whether it is head office database or store database.
DD ST1 DD ST2 DD ST3
DD STn DD HO
Store1 Store2 Store3
StoreN HO . . . . . . . . . . . . StoreN DDHO HO Store1 DD ST1 Store2 Store3 DD ST2 DD ST3 . . . . DD STN
Use Case III – When Fixed IP is available only at head office
When Fixed IP is available only at one central location, data needs to be pushed or pulled from stores. Store service will be used to read data from the store database and send data to head office service which will write data into the head office database. Store services will be used to pull data from head office; that is, store service will read data from the head office and write data into the store database. This configuration is little different from Split configuration; that is, the store server has the address of the head office server or DD services running at head office but the head office services cannot communicate with store services or the store server because the head office server cannot recognize the store server as it has no Fixed IP address.
In this configuration, Distribution Location Cards should be defined in store databases and to pull data from store to head office, the distribution location should be defined for store as well as for head office with DD Service running at store that may be same service for both store and head office or it may be different. To send data from store to head office, one more distribution location card should be defined for head office which should contain the DD Service running at head office.
Use Case IV – When number of stores is very high
In this case, different services can be created to forward data packages to a set of stores. For example if there are 100 stores there can be 10 forwarder services which will be used to forward data packages. 1 forwarder services will forward data package to 10 stores, The 2nd service will forward to next 10 stores and so on. This will speed up the process and there can be different services to read and write the data at head office.
In this configuration, distribution location cards should be defined in the head office database (Scheduler database if different from head office database).The Distribution location card for head office should have DD Service running at head office (If there are different services for reading the data and writing the data then in head office database, distribution location for sending data from head office to store should contain the reading DD service) and the distribution location cards for store1 to store 10 should contain distribution server as DD Service running at store (which will receive the package being forwarded by DD Service at head office) and in forwarder, DD Service running at head office in forwarder mode (2nd stage Data Director for which data package owner is the DD service running at head office that created the package – reading DD service).
The same method is used to send data from store to head office, distribution location card for head office should be defined in the store database with DD Service running at head office (If there are different services for reading the data and writing the data then in head office database, distribution location for sending data from head office to store should contain the writing DD service) and distribution location card for store should be defined in store database with DD Service running at store.
Summary
This section explains about Optimizing the Replication, Tables to replicate, Fields and Tables to exclude from replication. Following are the topics covered in this section:
Preload Actions Tables to Replicate
Fields and Tables to exclude from replication Specifying general replication information LS Configuration Use Cases.