Configure for the Web client

In the Display section of the Genero Configuration Management dialog, select the Use Application Server radio button. You can then edit the following fields:

Use Application Server

Select which GAS configuration to use. To add a new GAS configuration, click the Edit icon and enter details using the Genero Application Server Management dialog.

Application Type

Select Universal Agent to use the Genero Browser Client.

Select Web Application to use an earlier version of the Genero Web Client.

If you select Web Application, the Theme combobox box is activated and you can select from the available clients. You must be connected to a GAS that supports it; see the GAS documentation for the version you are using. To use the default client, leave the Theme combobox empty.

Browser

Specify the browser to use. If the Browser field is empty, the default browser is used.

If you select Browser, the Options field is activated and you can specify the options for starting the browser. For example, to start a Chrome browser in Incognito mode, enter "--incognito".

Important:

To set the --incognito option on MacOS, set the Browser field to "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome". If that option is not available, set it to "/Applications/Google Chrome.app".

In the GAS Connection Details section:

Host

Specify the IP address or the network name of the server you are connecting to when running an application with the GAS.

To connect to a GAS standalone dispatcher using a direct connection, specify the IP address or the network name of the Application Server (the one where the compiler resides). If the GAS standalone dispatcher is local, you can leave this field blank.

To connect through a web server, specify the IP address or the network name of the web server.

Port

Specify either the port of the GAS (for a direct connection to the GAS standalone dispatcher) or of the web server.

Important:

Changing the port number in the GAS Connection Details section does not automatically change the port number used when the GAS standalone dispatcher is launched!

If you are launching the GAS standalone dispatcher from Genero Studio, you must either modify the GAS configuration file to have the GAS listen at the same port, or you can add a startup script option to launch the standalone dispatcher at the proper port

If you modify the GAS configuration file, the change will impact all users of the GAS. By default, the GAS configuration file is named as.xcf, and the port number where the GAS listens for connections is the sum of the values of TCP_BASE_PORT and TCP_PORT_OFFSET. For more information about specifying the listening port for the GAS, see the Genero Application Server User Guide.

To launch the standalone GAS with a port number that differs from that in the GAS configuration file, add this option in the Start script options field, where XX is the port offset from 6300:

-E res.ic.port.offset=XX

For example, if you set the port value to "6399", you could start the httpdispatcher with the offset value of "99".

Connector

Leave blank if you are using a direct connection to a GAS standalone dispatcher. This is common in development environments.

For a Web server, enter the alias configured for your dispatcher in your GAS installation (often, gas). See the configuration topics in the Genero Application Server User Guide for more information on configuring your dispatcher.

Secure protocol

The selection of this checkbox impacts the URL used when launching an application.

• When selected, the protocol is "https".
• When not selected, the protocol is "http".

If the following error is raised when the secure protocol is selected, it indicates an issue on the server side with the SSL certificate.

SSL handshake has failed. Verify that you have a valid certificate

If you do not have access to the server to fix this, you will need to contact the system administrator. If the issue is not fixed, you will not be able to start the application from Studio.

Tip: Debugging an application that you cannot start from Genero Studio

If the failure of the SSL handshake means you cannot start your application from Genero Studio, you can still use Genero Studio to debug the application. You must start the application outside of Genero Studio; for example, by starting the application directly from a browser tab. With the application started, you find the application's process Id (PID). Once you have the PID, you can debug a running program by attaching to the running process.

In the GAS Configuration Details section:

Installation directory

Directory where the GAS is installed locally.

Use start script

The check box specifies whether to use the startup script to launch the GAS. When checked, the field specifies which start script to be launched when this configuration is used. The GAS standalone dispatcher: httpdispatch can be specified here to launch httpdispatch. httpdispatch can be used as the GAS script. In versions prior to 2.50, set the environment by specifying -p <GASDIR> in the Start script options field. Alternatively, call a script that calls . ./envas before calling httpdispatch, such as:

. ./envas 
httpdispatch

For GAS versions prior to 2.30, set the path for gasd instead of for httpdispatch.

Note:

The start script is only used when no GAS is found on the host at the port specified. The start script is not called even if the GAS to be launched from start script is different from the one already launched.

Start script options

Specify any options to be used with the start script. See GAS standalone dispatcher: httpdispatch for httpdispatch options. For more information on script parameters, see the Genero Application Server User Guide.

In the Application Details section:

Application group

The name of the Application Group defined in the GAS as.xcf file. Enter the value _default for the group to use the default configuration file, unless you have an explicit group to specify.

Application directory

The directory of the Application Group, the same path as the one referred to in the as.xcf file. If using the default application, the corresponding directory (usually GAS installation directory/app) has to be entered in the Group Directory field.

Parent application

The identifier of the parent GWC application; if no identifier is given, the default GWC application will be used.

Services group

The name of the Web Services Group defined in the GAS as.xcf file. Enter the value _default for the group to use the default configuration file, unless you have an explicit group to specify.

Services directory

The directory of the Web Services Group, the same path as the one referred to in the as.xcf file. If using the default application, the corresponding directory (usually GAS installation directory/app) has to be entered in the Group Directory field.

Parent service

The identifier of the parent Web Services application; if no identifier is given, the default Web Service application will be used.

<protocol>://<host>:<port>/<connector>/<application_type>/r/<application_name>

• protocol is either "http" or "https", depending on the value of the Secure protocol option.
• application_type is either "ua" or "wa", depending on the value of the Application type option.
• application_name depends on the executed application in project manager.
• Other values depend on the GAS configuration parameters.

• Host: <Automatic>
• Port: 6394
• Application group: mygroup
• Group directory: c:\work
• Parent application: defaultgwc

In this configuration, GAS applications will be run using the GAS located on the current computer at port "6394". The group "mygroup" in the as.xcf file points to the directory "c:\work"; the corresponding fields in the GWC configuration dialog are filled with the same information.