DSJ Server Quick Start

This section tells you how to start and stop the DSJ server, and introduces the DSJ server console window and administration frame.

Starting the DSJ server

Run dsjserver.bat in the install directory to start the DSJ server console.

The final "waiting for connection" message indicates that the server is now active and waiting for connections. If this message (or the server console) does not appear, see Troubleshooting.

Testing the DSJ server

Test the server by attempting run a Java application through a DSJ client. Running the client on a different machine is a more thorough test, but for starters you can try the client from the same machine. If you used the both option during the DSJ install, a client is installed in the same directory as the server. See DSJ Client Quick Start for information on configuring and running the client.

To make testing easier, JBuilderÆs Welcome application is pre-loaded into DSJ when installed. It doesnÆt do much, but when the application appears, you know that DSJ is working.

Setting DSJ server preferences

The DSJ server should operate as installed with its default preferences. To change these settings, choose Server|Preferences to open the DSJ server Preferences dialog box.

Each option in the dialog box corresponds directly to a property in the dsj.properties file. For more information on these properties, see dsj.properties Server Reference.

In this dialog box, you can set:

• The directories where the DSJ server looks for particular files.

  Label	Property	Directory contains
  Installed JREs	JREDirectories	Subdirectories which contain JREs
  Applications	AppFileDirectory	.app files which describe the installed applications
  Database	DatabaseDirectory	The DSJ package database files
  Users	UserManagerDatabaseDirectory	users.txt and group files
  Servers	ServerManagerDatabaseDirectory	server group files

• An option to either allow an unlimited number of connections, or to set a maximum. This corresponds to the LimitConnections and MaximumConnections properties.
• The port number used by DSJ for client/server communication. This reflects the Port property.

Administering the DSJ server

Administration functions are contained in the administration frame. To open the administration frame, choose Server|Administer... from the server console menu.

Each functional category is on a separate tabbed page.

• The Applications page lets you add, remove, or edit the applications installed on the DSJ server. See Managing applications.
• The JREs page lets you add, remove, or edit Java Runtime Environments that are available for download to clients so that they can run installed applications in a required JRE that the client does not have locally. See Using multiple JREs.
• The Users page lets you add, remove, or edit user names and their passwords. See Using multiple JREs.
• The Access Groups page lets you add, remove, or edit access groups. Access groups allow you to create groups of users, and to combine both user name and physical IP address security (so that an application can only be accessed by certain users in certain locations). See Access Group files.
• The Server Groups page lets you add, remove, or edit server groups, which simplify the deployment of applications on multiple servers. See Server groups.
• The Packages page lists the packages in the DSJ package database and lets you manually remove packages and coalesce the database. (Packages are added by adding applications.) See Managing packages.

Restarting and terminating the DSJ server

At some point, you may want to restart the server. This will cause the server to reinitialize itself, reading in any new installed applications or JREs. For details on what the server does at startup, see DSJ server startup.

To restart the server, choose Server|Restart... from the server console menu. Because restarting the server creates a stacked process stub, it is recommended that you only restart the server a certain number of times. This settings is controlled by the serverÆs MaximumRestarts property (see MaximumRestarts). If you have exceeded this limit, a reminder dialog box appears.

The dialog box is informational only; the server will attempt to Restart anyway. At some point--like the next time you want to restart--you should terminate the server and manually restart it.

To terminate the DSJ server, choose File|Exit from the server console menu.

Whether you Exit or Restart, if there are active connections, a dialog box appears:

You have the option of waiting for the connections to disconnect gracefully, or you can click OK to exit or restart immediately. Disconnecting an active connection will cause the client to attempt to reconnect with another server that serves the same application. This happens automatically without the userÆs knowledge, unless the reconnect attempt fails.