Server Reference Guide > Server Reference Guide > HTTP Routing > How HTTP Routing Works > Clients
Was this helpful?
Clients
Clients using HTTP routing must call the Initiate method directly to supply the necessary credentials in the flags parameter. The Connect method does not support HTTP routing. After the Initiate call, the client's Call4GL calls work transparently the same way over HTTP routing as they would over DCOM routing.
The parameters of the RemoteServer System Class Initiate method are used with HTTP Routing as follows:
Image
Specifies an arbitrary string that gets passed to your gatekeeper application to use however it chooses. The default configuration for the HTTP Gatekeeper provided in the %II_SYSTEM%\ingres\orjava\Gatekeeper2 and %II_SYSTEM%\ingres\ordotnet\Gatekeeper2 directories expects that this parameter will contain the registered application name (AkaName) for the application to be initiated.
Flags
Specifies optional credential strings. For more information, see How You Can Pass Credentials.
Location
Specifies the URL of your gatekeeper application (for example, https://myserver/httpapp2/OpenROADGatekeeper.ashx)
Routing
Specifies the string http activates HTTP routing
Type
Is ignored when using HTTP routing
Last modified date: 12/20/2023