The Server tab in the Project Details dialog
|
Reference |
Deploying Client/Server Projects |
|
|
The Server settings determine how the Client and Server executables communicate with each other.
Within the Project Details dialog, the Server tab presents the following options:
The Server tab in the Project Details dialog
|
Item |
Description |
|
Generate Client & Server Executables |
When enabled, generates a Server executable and executables for each Client UI. If this option is disabled, a standalone executable is generated. |
|
Protocol |
This is the "transport" that the Clients and Server communicate via. Use HTTP if you intend to connect Clients over the Internet, otherwise TCP/IP provides better performance for private networks. |
|
Formatting |
Use Binary for best performance and security. The SOAP/XML option is available for advanced development. |
|
Server Filename |
The name of the Server Executable and the folder where it will be generated. By default it uses the project name as part of the file name. |
|
Server Name |
This is either the IP Address or DNS Name of the Server PC. This tells the Client executables how to locate the Server. |
|
Port Number |
This is the TCP/IP port that the Server executable uses to accept connections from the Client UIs. |
To create the executables, select the Compile Executable option from the Tools menu: if you have not previously supplied a license key for this project, you will be prompted to enter one. Once accepted, Stardraw Control will compile the Server and Client executables, and will save them in the folders specified by the Server and Client properties.
A single Server executable will be generated, and one Client executable will be generated for each Client UI in your project.
Note
If you are connecting Clients over the Internet, ensure that the firewall at the Server is configured to allow inbound TCP/IP traffic on the specified port, and at the Client to allow outbound traffic. Whilst port 80 is typically used for HTTP, this may conflict with IIS Internet Information Services: the web server built into Microsoft Windows. or other web services running on your Server.
Simply copy the Server executable to the server PC, and double-click it to run.
The Server executable runs as a normal Windows process, but does not display any visible windows. For this reason, it is not visible in the Windows Taskbar or in the list of open programs you can cycle through using Alt+Tab keyboard combination.
To verify that it is running, right-click an empty space on the Windows Taskbar and select Task Manager: the Server executable should be visible in the list of processes.
Tip
To ensure that the Server executable runs automatically when the server PC is restarted and Windows starts, you may need to configure the server to automatically log into a user account, and place a shortcut to the Server executable in the user's Startup folder.
Client executables are installed in the same way for Client/Server as they are for Standalone projects.
Each Client executable may be installed onto as many client PCs as you like; you are free to distribute these amongst your client PCs in any combination you require: the only limitation is the total number of clients running at any one time. The licensing model for Client/Server is explained below.
The client PC must have unobstructed network access to the server PC, whether that be via a private network or the Internet. You should ensure that your firewall, if present, is configured according to the Port Number specified in the Server settings.
Tip
Before installing your Client or Server executables, you may want to run through our Pre-Launch Checklist to ensure a smooth deployment.
A Client/Server License determines the maximum number of Clients that can be connected to the Server at any one time. There is no distinction between different Client UIs either: it is simply the total number of concurrent, or simultaneous connections to the Server.
When you purchase an unlock code for a Client/Server project, the Server executable, when generated, will contain that maximum number. Whenever a Client executable starts it attempts to connect to the Server: as long as the number of connections has not been exceeded, the Server will allow the Client to connect and function as normal.
If however the number of simultaneous connections exceeds the licensed number, the Client executable will be refused a connection.
If for some reason a client PC is shut down, or a Client executable is terminated, that connection is released and becomes available for another Client to connect.
Please refer to the Stardraw
Pricing
online guide for more information on Client/Server
Licensing.