You are on page 1of 2

Guidelines for deciding between file or databasecheckpointing: ++++++++++++++++ 1.

Duplicate detection can only be done across multipleengines on different machine s if a database is used tostore process engine data. If you are running faulttol erant process engines (that is, only one process engineis running at a particula r time), or if all process enginesrun on the same machine, you can use a file sy stem forprocess engine storage. 2. For true fault tolerance, you must store the data in adatabase. You specify a JD BC Connection resource for thedatabase to be used when you configure your projec t inTIBCO Designer. The database is then one of the availableoptions on the Chec kpoint Data Repository pop-upmenu. 3. Because fault-tolerant engines are expected to be onseparate machines, you shoul d specify to use a database forstorage for each process engine. This allows you to specifythe same JDBC Connection resource for the master andsecondary engines, and therefore all engines can share theinformation stored for process instance checkpoints. 4. Also, your servers may not have all of the necessarysoftware for restarting all of instances. For example, yourdatabase may reside on the same machine as your m asterprocess engine. If that server goes down, any JDBCactivities will not be ab le to execute. Therefore, you maynot wish to load process definitions that use J DBCactivities in your secondary process engine.++++++++++++++++++++++++++++++ # Here you understand better which explain about advantagesand disadvantages of databases storage and file storage. Most of the information a process engine stores areinformation about each servic e state when a checkpoint is taken. There is, however, some other internal informationstored by the engine. You can specify that this informationis stored in the file system (the default) or in a databasebased on your need.For some systems, using a file system for storage may besufficient. However, some functionality is only availablewhen you use a datab ase for storing information aboutservice state: 1. With a database for storage, fault-tolerant engines canrecover services up to a checkpoint. Without a database,running services cannot be recovered to their las tcheckpoint.(File based is not recommended for FT. Also, otherwise thefile shoul d be on the local machine else the performancewill be poor because it is quite o bvious that file based istaking much longer than DB based checkpointing) 2. With a database for storage, Wait/Notify activities canbe used to pass data betw een services running on differentmachines. Without a database, the wait and noti fyactivities cannot communicate across machines. 3. Duplicate detection can only be done across multipleengines on different machine s if a database is used tostore process engine data. If you are running faulttol erant process engines (that is, only one process engineis running at a particula r time), or if all process enginesrun on the same machine, you can use a file sy stem forprocess engine storage.For better reliability using database over file s ystem forcheckpoint storage is good option. taken. There is, however, some other internal informationstored by the engine. You can specify that this informationis stored in the file system (the default) or in a databasebased on your need.For some systems, using a file system for sto rage may besufficient. However, some functionality is only availablewhen you use a database for storing information aboutservice state: 1. With a database for storage, fault-tolerant engines canrecover services up to a checkpoint. Without a database,running services cannot be recovered to their las tcheckpoint.(File based is not recommended for FT. Also, otherwise thefile shoul

you can use a file sy stem forprocess engine storage. With a database for storage. the wait and noti fyactivities cannot communicate across machines. Duplicate detection can only be done across multipleengines on different machine s if a database is used tostore process engine data. or if all process enginesrun on the same machine.d be on the local machine else the performancewill be poor because it is quite o bvious that file based istaking much longer than DB based checkpointing) 2. If you are running faulttol erant process engines (that is. . only one process engineis running at a particula r time).For better reliability using database over file s ystem forcheckpoint storage is good option. Without a database. Wait/Notify activities canbe used to pass data betw een services running on differentmachines. 3.