Version: 20.06+

User: System administrator/Developer


- not applicable


Working with internal instances of Futurama Webservice.



From version 20.06 onwards, it is possible to connect to local Futurama webservices directly without actually installing these separately on your webserver. Futurama applications in each mode (Website, Webservice, Console etc.) can call 'internal' instances of Futurama Webservice that are not configured in IIS. 

This feature is currently only available for 'traditional' Futurama webservices that use GetWebServiceResult as request. Custom wsdl and/or rest webservices are not supported yet.


An internal instance of Futurama Webservice is created automatically if the URL parameter of the WebReference object does not contain a physical url, but the text "[INTERNAL]". In that case, the main application instance creates an internal separate sub instance for the Futurama WebService application. 

By using the "[INTERNAL::configPath=xxx]" text, the path to an external web.config can be configured which is used for the sub Futurama WebService instance. This separate web.config can contain different config parameters for logging, mapping etc.  

In case the configPath parameter is omitted, the web.config of the main Futurama application instance is used by the sub Futurama WebService instance as well.


  • multiple external instances can be configured for different web service applications.
  • the URL property can also be the result of a formula, for example a RequestParameter() to a config parameter. In that case, a System Administrator can configure the location of the external web.config.
  • The document, name and folder parameter of the webservice are included in the GetWebServiceResult request as usual; the rootPath property can be configured in the (separate or not) web.config.
  • The Futurama version that is used, is the Futurama version of the main application. So make sure that the version of the Futurama document of the internal instance is the same version. If the version is older, the internal instance document will be converted in memory to the same version of the main application. If the version is newer, an error will occur.


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

Updated: 2020-07-02