User: System administrator, Developer


- knowledge of ASP.NET

- intermediate knowledge/experience of Futurama


In the several installation directories of Futurama, a configuration file can be placed. Using this file the behavior of ASP.Net can be regulated. Depending on the kind of installation a number of sections with settings can be configured. This page offers an overview.




In the install directory of Futurama Website, Futurama Webservice, Futurama Export and Futurama Editor a configuration file can be placed. In these configuration files it is possible to regulate the behavior of ASP.Net. For example setting the authentication mode. Apart from these industry wide settings also a number of specific Futurama settings can be made in the configuration files. This can be done by adding a number of sections to the config file. Within these sections a number of settings can be defined that influence the behavior of Futurama.  These custom made settings can be read and used by the Futurama application. In this chapter these settings are described. More detailed information for each of the settings can be found in the subchapters.


The settings are applicable for Futurama version 4.3 and higher. In Futurama 4.2 and before another system of configuration was used. If a new Futurama version is used and these old settings are still in the configuration file, Futurama will automatically convert these old settings to the new structure. The conversion of these settings is described in the compatability paragraph. Futurama will also log information how old settings are converted to the new structure.

General structure

Within the element either a or a has to be included. Which section name is applicable depends on the configuration that is used. In the installation pages of the Futurama modules is explained which section name has to be used. Within this sectionGroup the different sections can be defined. Below an example of this configuration:

	<sectionGroup name="futuramaSettings">
		<section name="cache" type="ActuIT.Futurama.Config.CacheSection, ActuIT.Futurama.Engine, Version=, Culture=neutral, PublicKeyToken=null"/>
		<section name="debug" type="ActuIT.Futurama.Config.DebugSection, ActuIT.Futurama.Engine, Version=, Culture=neutral, PublicKeyToken=null"/>
		<section name="format" type="ActuIT.Futurama.Config.FormatSection, ActuIT.Futurama.Engine, Version=, Culture=neutral, PublicKeyToken=null"/>
		<section name="log" type="ActuIT.Futurama.Library.LogSection, ActuIT.Futurama.Library, Version=, Culture=neutral, PublicKeyToken=null"/>
		<section name="mapping" type="ActuIT.Futurama.Config.MappingSection, ActuIT.Futurama.Engine, Version=, Culture=neutral, PublicKeyToken=null"/>
		<section name="monitor" type="ActuIT.Futurama.Config.MonitorSection, ActuIT.Futurama.Engine, Version=, Culture=neutral, PublicKeyToken=null"/>
		<section name="performancelog" type="ActuIT.Futurama.Library.PerformanceLogSection, ActuIT.Futurama.Library, Version=, Culture=neutral, PublicKeyToken=null" />
		<section name="recording" type="ActuIT.Futurama.Config.RecordingSection, ActuIT.Futurama.Engine, Version=, Culture=neutral, PublicKeyToken=null"/>
		<section name="render" type="ActuIT.Futurama.Config.RenderingSection, ActuIT.Futurama.Engine, Version=, Culture=neutral, PublicKeyToken=null"/>
		<section name="vision" type="ActuIT.Futurama.Config.VisionSection, ActuIT.Futurama.Engine, Version=, Culture=neutral, PublicKeyToken=null"/>

Next to this code, within the configuration element a futuramaSettings or a visionSettings element has to be included (the element name is the same name as the sectionGroup name mentioned above. Within this futuramaSettings or a visionSettings element for each of the sesctions that are defined within the sectionGroup the specific settings can be chosen.


Mentioned below the different sections that can be included in the configuration file. Not all of these settings are applicable for each Futurama installation. In the installation chapters of the Futurama modules is described which sections cabn be used to determine the behavior of Futurama for the specific installation. The following sections are available:

- Cache: Contains settings that define whether and how Futurama stores sessions and results in memory

- Calculation: Contains settings that can be used to speed up calculations by using compiled code

- Debug: Contains settings that are relevant for the developer/tester of a Futurama application, such as the use of Futurama Insight

- Format: Contains settings that define how Futurama presents results such as amounts and dates

- IdentityProvider: Contains settings that define an external identity provider which is used to determine the access to a webpage

- Log: Contains settings that define whether and how Futurama logs errors, warnings and other messages

- Mail: Contains settings, such as the SMTPServer, that are used by Vision when sending automatic e-mails

- Mapping: Contains settings that define the location of (standard-)documents for Futurama applications

- Monitor: Contains settings that define the logging of actions that are performed during sessions by the user of the application

- PerformanceLog: Contains settings that define whether Futurama logs warnings during page loading and/or load balancing

- Rendering: The render section allows the configuration of an XSLT file that allows Futurama to generate customized HTML from an intermediate language called FICO

- Security: Contains settings for additional security settings in Futurama

- Server: Contains settings for Futurama Server/Batch mode

- Vision: Contains settings that define the connection with Futurama Vision

- WebAPI: Settings to use Futurama Web API


If you have any questions about this subject or if you want to provide us feedback please send us an e-mail.

Updated: 2021-01-25