Versions Compared

Old Version 5

changes.mady.by.user Former user

Saved on

compared with

New Version 6

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column

The superuser admin can configure server-wide global data. One common use is for forms deployed from a development/test form server to a production form server. You often need information such as Urls URLs configured one way in your dev/test environment and another way in your production envirionmentenvironment. For example, a database in the dev/test environment might be located at http://mytest:1024/database/listManagers and in your production environment at http://myprod:1044/database/listManagers.

 makes deployment from dev/test to production easier by enabling you to configure global data variables. For example, rather than hard-coding the Url URL to your database server you can write the Url URL using a template such as {dbUrl}/database/listManagers. Then define variable dbUrl one way in dev/test and another way in production.

To see all the places where templates can be used, refer to the chapter Templatized Strings.

Column

On This Page:

Table of Contents

Setting Global Data

...

in _data properties file

To define your server-wide global data:

...

Info

Parameters defined in the _data.properties file can be retrieved using _data.getParameter in rules. Dynamic Labels, Help or Hints is an example showing how you can set the value of control labels, help and hints dynamically in a rule.

Setting Global Data

...

in Configuration Files

Properties listed in the  _data.properties can be overridden with properties prefixed by frevvo._data.<property name> in the following configuration files:. Note the syntax for the properties has a dot before and after the _data.

  • If you are using the frevvo tomcat bundle, you can add the frevvo._data properties in the:
    • <frevvo-home>/tomcat/conf/catalina/localhost/frevvo.xml - this is the easier and recommended location as this file is located outside the frevvo.war.
    • the web.xml file in the frevvo.war - this file is located in the frevvo.war file - the frevvo.war must be unzipped, the changes made and then rezipped. The modified frevvo.war must then be dropped into the <frevvo-home>\tomcat\webapps directory.
    • frevvo-config.properties - this file is typically created by the System Administrator to override parameters in a container web.xml file. This is most often used when the container is not tomcat.

...

It is easier to create property files with the frevvo._data.servername property dbURL parameters pointing to the correct locations outside of the databases. for each environment.

This paramter in the frevvo.xml file would look like this:

Code Block
<Parameter name="frevvo._data.dbURL" value="http://<server>:<port>/database/listManagers" override="false" />

The same parameter in the web.xml file would look like this:

Code Block
<context-param>  
    <param-name>frevvo._data.dbURL</param-name> 
    <param-value>http://<server>:<port>/database/listManagers</param-value> 
</context-param>

The same parameter in the frevvo-config.properties file would look like this:

Code Block
frevvo._data.dbURL=http://<server>:<port>

As mentioned above, you can write the URL using a template such as {dbURLl}/database/listManagers. Then define the variable dbURL for the development, UAT and Production environments in the properties file you are using..