Configure web applications for third-party portal

What do you need to configure for applications you want to embed in a third-party portal?

One of the ways of deploying Genero applications is using a third-party application portal to embed your Genero web applications inside the portal functionality. Here the user has a list of applications to choose from. The user can select an application to run (only one application may be active at a time), and the application is rendered in the portal.

Your Genero applications will be executed in the Genero Browser Client (GBC). The GBC uses an inline frame (iframe) that allows it to be embedded within the portal. For more information on how the GBC runs applications within a portal, see Genero Browser Client User Guide.

The configuration you need to render applications in a portal is different to a standard application configuration. It takes the form of a main application and may include sibling applications. Follow the steps to configure your applications for a portal, and see the sample configuration in Embedded web applications.

Begin the configuration with an APPLICATION node.

This defines the main application configuration.
To the main APPLICATION element, add the attribute and value: SinglePageApplications="TRUE".
This setting is required to allow Genero applications run in the context of Single Page applications within the portal web page.
To the EXECUTION element, add elements that define the main application, such as the PATH, MODULE, and so on.
The EXECUTION elements defined for the runtime environment of the main application, apart from the MODULE, may be omitted for the sibling applications. Thus, all the applications will be executed in the same FGLRUN environment.
To the EXECUTION element, add an APPLICATIONS element.
This element is required to define the sibling applications. The GAS will check if there is an APPLICATIONS node and if the SinglePageApplications attribute is set to TRUE; otherwise, a configuration error is returned.
Within the APPLICATIONS element, add an APPLICATION (for embedded apps) element for each application you want to configure.
- Each application must contain an application Id attribute and value, for example <APPLICATION Id="sib1">.
  
  Important:
  The Id must be a unique name in the context of the applications defined in the configuration file.
- A PATH element defines the application path. If no PATH is defined, the PATH from the main application will be used.
- A MODULE element defines the name of the executable file. If a MODULE is not defined, the app id will be used as the module name.
- A PARAMETERS element defines parameters that go on the command line when the application is started.

Embedded web applications

<?xml version="1.0" encoding="UTF-8"?>
  <APPLICATION Parent="defaultgwc" SinglePageApplications="TRUE"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation="http://www.4js.com/ns/gas/5.00/cfextwa.xsd">
     <EXECUTION>
        <PATH>C:\Users\fg\gas3694</PATH>
        <MODULE>main</MODULE>
        <APPLICATIONS>
           <APPLICATION Id="sib1">
              <PATH>C:\Users\fg\gas3694</PATH>
              <MODULE>sibling1</MODULE>
           </APPLICATION>
           <APPLICATION Id="sib2">
              <PATH>C:\Users\fg\gas3694</PATH>
              <MODULE>sibling2</MODULE>
           </APPLICATION>
        </APPLICATIONS>
     </EXECUTION>
     <AUTO_LOGOUT Using="cpn.wa.autologout"/>
     <UA_OUTPUT>
       <PROXY>$(res.uaproxy.cmd)</PROXY>
       <PUBLIC_IMAGEPATH>$(res.public.resources)</PUBLIC_IMAGEPATH>
       <GBC>gwc-dev</GBC>
       <TIMEOUT> Using="cpn.wa.timeout"</TIMEOUT>
     </UA_OUTPUT>
     <END_URL>http://www.4js.com</END_URL>
  </APPLICATION>