Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

server/alone command line

 
Norbert Hasselberg
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think , i have understand the issues regarding standanlone/remote mode.
But one think ...
When i am in standalone mode , all works on the local machine on ONE database file. what is , when i start the appl. again, so that runs two appl. on the machine ? For me , that means we have a conflict in accessing
the database file.
Do i have something missunderstand, or should i ignore such case ??
 
Michael Couck
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Norbert,
Most people interpreted the specification like this: Network architecture:
STAND ALONE : GUI => DATA MANAGER => DATABASE FILE
SERVER MODE : GUI => SERVER => DATA MANAGER => DATABASE FILE
This is the easiest configuration I think. In stand alone mode you just leave out the server code, and have an instance of the data manager in the GUI. If you wish to run the GUI in server mode, then you need to start a server, and then start the gui, so two applications running in two JVM's. They can be on the same machine. If you want to run the GUI in stand alone mode, then you start the GUI application, so only one application running. Then you need to have some functions to open the database file from the GUI.
Hope this helps
Michael
 
Stephen Galbraith
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
For me , that means we have a conflict in accessing
the database file.

that's right it would!
But you don't have to worry about it - it says in the destructions that only one JVM will access the database file at a time. So no issue!
Steve
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic