Back to Contents

The Application URI

To access an application, you specify the necessary information in the browser's address bar by entering in the appropriate application URI. 

Topics

URI Syntax

The syntax of a URI follows the standards described in the RFC 2616. A list of example URIs is provided below.

http[s]://
  {
    web-server[:web-server-port]
      [
        /directory [...]
        /script-directory
        /connector
      ]
    |
    app-server[:app-server-port]
  }
  /scope
  /action
  /group
  /
    {
      web-application-id
    }
  [
    ?
    parameter=parameter-value
      [
        &
        parameter=parameter-value
      ]
      [...]
  ]
Note: https is slower than http due to encryption.

Explanation of syntax options

Option Data Type Explanation  Valid Values
web-server STRING Name or IP address of the Web Server.  
web-server-port INTEGER Port on which the Web Server listens.  
directory STRING Any directory or virtual directory on the Web Server.  
script-directory STRING The script directory.  
connector STRING The name of the connector.  fglccgi, fglccgi.exe, fglcisapi.dll 
app-server STRING Name or IP address of the Application Server.  
app-server-port INTEGER Port on which the Application Server listens.  
scope STRING Scope we are working on.  wa, ja, ws
action STRING Action requested of the Application Server.  r
group STRING Application Group defined in as.xcf  
web-application-id  STRING Web Application identifier.  
parameter STRING Parameter to communicate to the Application Server.  Arg, UserAgent
parameter-value STRING Parameter value.  

Back to the top

URI Examples

Example 1 - Connection through CGI connector

Calls the "myApp" application through the "myWebServer" Web Server, using the CGI connector:

http://myWebServer/cgi-bin/fglccgi/wa/r/myApp
Note: On Windows platforms, when connecting via a Web server, you must include the extension when calling fglccgi.exe, as shown in the following URL: 
http://myWebServer/cgi-bin/fglccgi.exe/wa/r/myApp

Example 2 - Connection through isapi connector

Calls the "myApp" application through the "myWindowsWebServer" Web Server, running IIS, using the ISAPI connector:

http://myWindowsWebServer/scripts/fglcisapi.dll/wa/r/myApp

Example 3 - Direct connection to gasd

Calls the "myApp" application on the "myApplicationServer" Application Server, listening to port 6394:

http://myApplicationServer:6394/wa/r/myApp

Example 4 - Connection using a group

Calls the "myApp" application defined in group "demo" through the "myWebServer" Web Server, 

http://myWebServer/cgi-bin/fglccgi/wa/r/demo/myApp

Example 5 - Starting applications with arguments

Calls the "myApp" application with arguments, through the "myWebServer" Web Server:

http://myWebServer/cgi-bin/fglccgi/wa/r/myApp?Arg=Val1&Arg=Val2

Notes:

  1. A question mark (?) follows the application name.
  2. Val1 is the value of the first argument and Val2 is the value of the second argument.
  3. Each argument is separated by an ampersand (&).

For more details on arguments configuration see the PARAMETERS section.

Example 6 -  Calling Desktop application

Calls the "appid" application from the Genero Desktop Client monitor using a http connection.

http://appserver:6394/ja/r/appid

A call to the same application using the GDCAX use the URL with "wa" not "ja".

http://appserver:6394/wa/r/appid

Example 7 - Calling a Web Service application

To get the WSDL for a specified service:

http://appserver:6394/ws/r/appid/service?WSDL

To access the Web service: 

http://appserver:6394/ws/r/appid/service

If the Web service uses a group: 

http://appserver:6394/ws/r/groupid/appid/service

Access through a webserver (apache for example): 

http://webserver/cgi-bin/fglccgi/ws/r/appid/service

Back to the top