Our environment will have multiple TDI servers running on one machine. Each server will, of course, run with its own solution directory.
Each of these server also needs its own system store. The easiest approach seems to use a Derby System Store in embedded mode where, if I understand correctly, one thread within the server's JVM is dedicated to providing access to the store.
Is it true that the configuration shown below in solution.properties will cause the TDISysStore directory to be created WITHIN the solution directory - so that each TDI server will have its own, private store?
Thanks, Avery
## Location of the database (embedded mode) - Cloudscape 10 com.ibm.di.store.database=TDISysStore com.ibm.di.store.jdbc.driver=org.apache.derby.jdbc.EmbeddedDriver com.ibm.di.store.jdbc.urlprefix=jdbc:derby: com.ibm.di.store.jdbc.user=APP {protect}-com.ibm.di.store.jdbc.password=APP
You are right - TDISysStore should get created in the solution folder. Multiple Servers could coexist at the same time as long as the y use separate solution folders and Derby in embedded mode.
I run multiple TDI versions and they all share the same networked SysStore (Derby) -- I just have to make sure it's TDI 7 that starts the server, so I get the latest Derby release (10.2).
I'm just saying...
-Eddie :)
On Jul 1, 9:35 am, Deyan Popov <deyan.po...@gmail.com> wrote:
> You are right - TDISysStore should get created in the solution folder. > Multiple Servers could coexist at the same time as long as the y use > separate solution folders and Derby in embedded mode.
You are right Eddie - in network mode they would share the same Derby database by default and in embedded mode each has its own database. But of course with little tweaking you can make each have its own Derby network server listening on a different port and using a separate folder.
|
