Hi Saheed,
If it is java -jar <path_and_filename> server
The program will only prompt for configuring only the server and wait for the clients to be started
Sounds good, but you haven't specified what "configuring the server" means to you. So you are probably right, but there are no guarantees.
clients to be started with the following :java -jar <path_and_filename> and then it requests for the clients configuration(i.e port number and db path).
If a networked client is starting up, all it needs to know is how to connect to the server. This might be as simple as just configuring the hostname / IP address of the server if you are using RMI. For Sockets you will probably have to configure the port number as well (you could set up a fixed port if you wanted to, but I personally think this is not a nice solution). Similarly you can set up a port number for an RMI solution, but RMI already has a default port (1099), so it is not necessary (but again, I personally think allowing the port number to be configured is a nice feature for RMI). But there should never be a need for the networked client to know the path to the database on the server.
If the command is java -jar <path_and_filename> alone It would just prompt for the db path name and connect locally.
Yep, this sounds perfect.
Regards, Andrew