JDataStore Server user interface
The JDataStore Server is a feature of JBuilder Professional and Enterprise.
JDataStore Server menu
Choose one of the following commands for more information:
JDataStore Server tabs
Choose one of the following tabs for more information:
File|Startup (JDataStore Server)
Restarts the server process after it has been stopped with
File|Shutdown. This menu item is disabled if the server is already
running.
File|Shutdown (JDataStore Server)
Stops the server thread (in a controlled manner) so that server
properties can be changed. This menu item is disabled if the server is
not running.
File|JDataStore Explorer (JDataStore Server)
Launches the JDataStore Explorer.
File|Exit (JDataStore Server)
Stops the server thread (in a controlled manner) and closes the
JDataStore Server.
Help|Contents (JDataStore Server)
Opens this help document.
Help|About (JDataStore Server)
Displays information about the JDataStore Server.
Users tab (JDataStore Server)
Contains a table which lists the following information about each user connected to a database via this instance of the JDataStore Server:
- User Name - the name of the user
- IP Address - the IP address of the user
- Host Name - the host name of the user
- Database - the database to which the user is connected
- Connected since - the time that this connection was established
- Remote port - the port the user is using to connect to to the JDataStore Server
The user table is updated immediately as each connection is added or dropped.
Events tab (JDataStore Server)
The Events tab shows the contents of the JDataStore Server's status logs. Status logs are persisted by being written to a file, therefore, they will show events from previous instances of the JDataStore Server. Each line in the status log contains the following, separated by commas:
- Event (connect, disconnect, etc.)
- User - the user associated with this event
- Database - the database associated with this event
- Time - the date and time of the event
The events tab is updated immediately as each connection is added or dropped.
Databases tab (JDataStore Server)
The Databases tab shows the filename of each database opened via the JDataStore Server. For each database there is also a User Count count, which indicates the number of users connected to that database. This information is updated immediately as each connection is added or dropped.
At the bottom of the Databases tab, there is a Show locks button. This button will be enabled if there are any open databases visible in the table. When you click on Show locks, a dialog is opened, and a dump of any open locks for the selected database is displayed in that dialog. Note that this dump shows any open locks at the time you clicked the button, and it will not update as other locks are opened or closed. The user must click on the dialog's Refresh button or launch another instance of the dialog to get the latest information.
Options tab (JDataStore Server)
The Options tab lets the user view and specify JDataStore Server options. If the JDataStore Server is running, these options are disabled. The server must be shut down in order to modify the options. The next time the server is launched it will use the current option settings. The options which can be set via this tab are:
Options: Port (JDataStore Server)
Specifies the TCP port number for communications between the JDataStore
Server and remote JDataStore JDBC clients. The default is 2508.
This menu item is disabled when the JDataStore Server is running. Choose
File|Shutdown to stop the server thread.
Options: Temp directory (JDataStore Server)
Specifies the directory used by the query engine for temporary files. By
default the directory that contains each JDataStore file is used.
This menu item is disabled when the JDataStore Server is running. Choose
File|Shutdown to stop the server thread.
Options: Status log directory (JDataStore Server)
Specifies the directory where JDataStore Server status logs will be written.
This menu item is disabled when the JDataStore Server is running. Choose File|Shutdown to stop the server thread.