Configuration

Settings

Within the configuration element the next code has to be included:

<configSections>
	<sectionGroup name="futuramaSettings">
		<section name="vision" type="ActuIT.Futurama.Config.VisionSection, ActuIT.Futurama.Engine,Version=1.0.0.0, Culture=neutral, PublicKeyToken=null"/>
	</sectionGroup>
</configSections>

Next to this code, also within the configuration element the next code has to be included:

<futuramaSettings>
	<vision password="testpw" username="testuser" token="testtoken" connected="true">
		<endpoint name="HttpBinding_IVision" contract="ActuIT.Futurama.Vision.IVisionService" bindingConfiguration="HttpBinding_IVision" 
		binding="basicHttpBinding" address="http://server/site/Services/VisionService.svc">
			<basicHttpBinding name="HttpBinding_IVision" maxReceivedMessagesize="1048576000"/>
		</endpoint>
	</vision>
</futuramaSettings>

The futuramaSettings element is the general part for more configuration settings. Within this element the vision element is set.

Explanation

Within the vision element some attributes can be set. Below the possible values of these attributes.

connected

To configure a connection with Vision, the value of this attribute must set to 'true'. The endpoint address 'http://server/site/Services/VisionService.svc' is the address to the VisionService.svc-file. Replace the 'server/site' part of the default url to the location of your VisionService. See 'Installation Futurama Vision Management Site' for the installation of the Management Site and the configuring of the url.

username/password (Futurama 19.02 +)

From Futurama 19.02 it is possible to secure the Vision Webservices (see this page). Securing is possible by using Forms Authentication or by using Windows Authentication. In the situation of Forms Authentication you need to supply the password when requesting a Vision Reference. The recommended way to do that is by using Windows authentication. If you request a Vision instance on a remote server you can also use a username and password. This will be passed to the Vision webservice as an attribute. Only use the username and password when using an HTTPS connection.

token (Futurama 25.01 +)

From Futurama 25.01 it is possible to secure the Vision Webservices using a token instead of username/password. To do this, a specific Forms user can be created in the Management Site with a generated token. This way the connection can be made more secure and the users for Webservice calls are separated from the users that can log in to the Management Site.

Configuring Futurama Vision with wsHttp binding

Introduction

You can apply a wsHttp binding to the connection from Futurama HTML to Futurama Vision. To do that you must apply the following sample settings to both sides of the connection. The server side is the Futurama Vision Management Site that is used. And the client side is the Futurama HTML or Futurama Editor that connects to Futurama Vision.

Sample config for Vision Management Site

<!-- in <system.serviceModel><services>-->
<service name="ActuIT.Futurama.Vision.WCF.VisionService">
    <endpoint contract="ActuIT.Futurama.Vision.WCF.IVisionService" bindingConfiguration="Binding_IVisionService" binding="wsHttpBinding" address="">
        <identity>
            <userPrincipalName value="username"/>
        </identity>
    </endpoint>      
</service>
<!-- in <system.serviceModel><services><bindings>-->
<wsHttpBinding>
	<binding name="Binding_IVisionService" maxReceivedMessagesize="1048756" receiveTimeout="00:01:00">
		<reliableSession enabled="false" ordered="false" inactivityTimeout="00:10:00"/>
		<security mode="Message">
			<message establishSecurityContext="false"/>
		</security>
	</binding>
</wsHttpBinding>

Sample config for Futurama HTML or Futurama Editor

Note: in the following sample you need to replace address by the address of the Vision Management installation.

<!-- in <futuramaSettings> -->
<vision connected="true">
	<endpoint name="HttpBinding_IVision" contract="ActuIT.Futurama.Vision.IVisionService" bindingConfiguration="HttpBinding_IVision" binding="wsHttpBinding" address="http://address/Services/VisionService.svc">
		<identity>
			<userPrincipalName value="username"/>
		</identity>
	</endpoint>
	<wsHttpBinding name="HttpBinding_IVision" maxReceivedMessageSize="1048576000" receiveTimeout="00:01:00">
		<reliableSession enabled="false" ordered="false" inactivityTimeout="00:10:00"/>
		<security mode="Message">
			<message establishSecurityContext="false"/>
		</security>
	</wsHttpBinding>
	<behavior name="myBehavior">
	</behavior>
</vision>