Migration tips

When migrating an application from the Genero Desktop Client to the Genero Web Client, you may encounter issues. Here are some tips for when you encounter migration issues.

Configuration issues
Rendering issues
Application issues
Network issues

Configuration issues

The GAS is likely serving several types of applications, which might use different versions of the Genero Business Development Language and different databases. You need to tell the GAS in which environment your application will be running. This is done through a configuration file.

If you already have your application configured for GDC-HTTP, you simply need to enable the rendering for GWC.

Example of configuration for a GDC application:

<APPLICATION Id="my-app" Parent="defaultgdc">
  <EXECUTION>
    <PATH>$(res.path.fgldir.demo)</PATH>
    <MODULE>demo.42r</MODULE>
  </EXECUTION>
</APPLICATION>

To allow GWC rendering, simply replace defaultgdc by defaultgwc:

<APPLICATION Id="my-app" Parent="defaultgwc">
  <EXECUTION>
    <MODULE>demo.42r</MODULE>
  </EXECUTION>
</APPLICATION>

The first time you configure an application for GWC, see the Quick Start topic to configure your execution environment, the database access and the resource deployment (pictures, reports, and so on).

If the application fails to start, check the Genero Application Server logs to see what happened. Check the dispatcher log first, then check the session log. To get the session number, click on gtree and have a look at the application url or view the html source page.

Example Log Entry:

/wa/sua/7e26fadb0c9f6939c65702fc9a1ff2a4/0

The session number is 7e26fadb0c9f6939c65702fc9a1ff2a4.

To debug the configuration, see the Using the Debugger topic to assist you in setting up a console. With a console, the GAS does not launch the application, but instead launches a console with the application environment set up. You can then compare the environment variables to your GDC working environment, you can run command lines to check and update your environment variables, and you can even display the application on the GDC by changing the FGLSERVER variable and verify that the application runs properly with GDC.

Rendering issues

Graphical widgets that are not rendered properly or displayed with a different style are considered rendering issues. Examples of rendering issues include misalignments, 4st colors not applied, and widgets that are rendered when they should not.

When you encounter a rendering issue:

First check in gtree (equivalent of GDC debug tree for GWC) to verify that all resources files (.4ad, .4st, and so on) are loaded properly and that the widgets attributes are correctly set.
Use Firebug on FireFox or Developer Tools for Internet Explorer to check:

That the resources files (.css, .js, and so on) are accessible and not displaying a 404 error message.
That the html is properly generated. For example, check whether the color for the edit is set or is missing in the generated page.

Application issues

Application issues are behavior related. Most of the time you need to contact your local support center. But you can first check for:

Relevant messages in the logs
JavaScript™ errors

If clues are provided in either the logs or in the errors, try to build a simple test program that replicates the issue and contact your local support center.

If your application involves a Rich Text version of a textedit widget, review the migration note regarding Rich Text editing and the differences between the Genero Desktop Client and the Genero Web Client.

Network issues

Once the migration is almost done and you are in load tests phase, you might encounter sporadic disconnections. Carefully read the chapters on GAS installation for your web server and verify the web servers and GAS timeouts are compatible. You can also have a look at:

Web server log (error/access log)
The Genero Application Server logs
Network sniffer (like wireshark)