DataSnap WebBroker Application Wizard
Go Up to Creating a DataSnap Server
File > New > Other > Delphi Projects > DataSnap Server > DataSnap WebBroker Application
The DataSnap WebBroker Wizard provides an easy way to implement a Server application using both the WebBroker and DataSnap technologies. Regardless of the options you select, it creates a Unit that contains a TDSServer component and a TDSHTTPWebDispatcher component. All the additional components are connected to the TDSServer, having the Server property set to the name of the TDSServer component. The communication protocol between the Server and the Client applications is HTTP.
The WebBroker technology is used to send the Server response in HTML format.
The following table lists the options in the DataSnap WebBroker Application wizard.
| Item | Description |
|---|---|
|
INSAPI/NSAPI Dynamic Link Library |
ISAPI and NSAPI Web server applications are shared objects that are loaded by the Web server. Client request information is passed to the DLL as a structure and evaluated by TISAPIApplication. Each request message is handled in a separate execution thread. When you select this type of application, the library header of the project files and the required entries are added to the uses list. Also, the clause of the project file is exported. |
|
CGI Stand-alone executable |
A CGI stand-alone Web server application is a console application that receives client request information on standard input and passes the results back to the server on standard output. This data is evaluated by TCGIApplication. Each request message is handled by a separate instance of the application. In Delphi, selecting this type of application adds the required entries to the uses clause of the project file and adds the appropriate $APPTYPE directive to the source. |
|
Web App Debugger executable |
The Web Application Debugger provides an easy way to monitor HTTP requests, responses, and response times. The Web Application Debugger takes the place of the Web server. Once you have debugged your application, you can convert it to one of the other types of Web application and install it with a commercial Web server. |
|
Class Name |
When you select the Web App Debugger, you must specify a Class Name for the debugger executable. This is simply a name used by the Web App Debugger to refer to your application. Most developers use the application’s name as the Class Name. |
|
Support HTTP Authentication |
If you select this option, a TDSHTTPServiceAuthenticationManager component is placed on the Server form. The TDSHTTPWebDispatcher component uses the TDSHTTPServiceAuthenticationManager as the AuthenticationManager to allow the implementation of HTTP user authentication for the DataSnap Server. The implementation consists in implementing the HTTPAuthenticate property. When Authentication is selected, the client needs to provide the DataSnap user name and password as SQL connection properties. |
|
Add Server Methods Class |
Select this option to add a TDSServerClass component to the Server form and to allow defining a class on the Server that will expose the Server methods to the Client applications. |
|
Ancestor |
This option allows you to specify the ancestor for your Server class. Choose TDSServerModule to expose the data sets from the Server to the Client applications. Choose TDataModule if you want to use nonvisual components in your Server class. Choose TComponent if you want to entirely implement the Server class. |
|
Include sample methods |
If you select this option, the ServerMethodsUnit will contain the implementation of a simple method called EchoString, which returns the Value given as a parameter. |