Datasnap.Win.MConnect.TDispatchConnection.ServerName
Delphi
property ServerName: string read FServerName write SetServerName;
C++
__property System::UnicodeString ServerName = {read=FServerName, write=SetServerName};
Properties
| Type | Visibility | Source | Unit | Parent |
|---|---|---|---|---|
| property | published | Datasnap.Win.MConnect.pas Datasnap.Win.MConnect.hpp |
Datasnap.Win.MConnect | TDispatchConnection |
Description
Specifies the name of the application server with which to connect.
Use ServerName to specify the name of the application server to which the client application should connect. At design time, the Object Inspector provides a drop-down list of all available servers if one of the following conditions is met:
For DCOM and OLEnterprise connections, the servers must be registered in the system Registry.
For Socket connections, ScktSrvr.exe must be running on the server machine.
For Web connections, the connection component must have an URL for locating httpsrvr.dll.
If ServerName specifies a valid name for a registered application server, setting ServerName sets the ServerGUID property to the GUID that corresponds to the named application server.
Note: Either ServerName or ServerGUID must be provided so that the dispatch connection can create and communicate with the appropriate server COM object. This is true even for connections that are not formed using DCOM, because the remote data module on the application server is always implemented as a COM object. Using ServerGUID rather than ServerName to identify the application server is more robust because it does not require the application server to be registered on the client system when using a COM-based connection.