3.2.2. Setting up a gadget server

3.2.2.1. Configuring security key
3.2.2.2. Configuring gadget proxy and concat

Virtual servers for gadget rendering

GateIn 3.5 recommends using two virtual hosts for security. If the gadget is running on a different domain than the container (the website that 'contains' the app), it is unable to interfere with the portal by modifying the code or cookies.

An example would hosting the portal from http://www.sample.com and the gadgets from http://www.samplemodules.com.

To do this, configure a parameter called gadgets.hostName. The value is the path/to/gadgetServer in GadgetRegisteryService:


<component>

  <key>org.exoplatform.application.gadget.GadgetRegistryService</key>

  <type>org.exoplatform.application.gadget.jcr.GadgetRegistryServiceImpl</type>

  <init-params>

    <value-param>

      <name>gadgets.hostName</name>

      <description>Gadget server url</description>

      <value>http://localhost:8080/GateInGadgetServer/gadgets/</value>

    </value-param>

  </init-params>

</component>

It is also possible to have multiple rendering servers. This helps to balance the rendering load across multiple servers.

When deploying on the same server, ensure the gadget initiates before anything that calls it (for example, the webapp GateInGadgets which uses org.exoplatform.application.gadget.GadgetRegister).