In I/O Data Server settings you will find a window containing a list of Transports which
are available for Server project data communications. This window can then be used for inserting the transport criteria to use for Server and Client data communication. Once the Server has been started up, it will provide the end points according to the transports which have been enabled in the project.
The Clients (any Client) can then use the preferred transport, or one that is the most
suitable for the application type being used, independently from the data model being
By using the I/O Data Server Settings tab, you can enter, delete or edit the transports
available to the Data Server so that they can be used by clients wishing to connect.
This operations are done using the "Add Transport" or "Edit Transport" window:
This window allows you to choose and configure the Transport you wish to add to the
Projects are designed with the "net.pipe" transport for default. This transport is the one
used in the local application for connecting the Client to the Server if not specified
otherwise. This means that the visualization Clients assigned with Tags defined in
graphical screen objects in the Server will connect using the local net.pipe transport.
This transport is one of the those provided by Microsoft WCF (Windows Communication
Foundation) and uses local memory to ensure maximum performances.
This transport is for 'local' use only and therefore does not consent to network
connectivity. If you need to use network connectivity you must enter one of the other
|Attention! "net.pipe" is a local transport that entails the Client and the Server run
within the same session. This transport cannot be used if the Client project and
the Server project run on different machines.
When using a Terminal Server or a Remote Desktop, the net.pipe transport may
require user login with an appropriate access level.
To enable remote Clients to connect to the Server a network transport must be
configured in the Server.
There are several network transports each one of which differs in aspect according to
how they performance or provide security. It is therefore the project engineer to decide
which transport to use for their architecture as required or in function with client needs.
The order with which they are used, for instance when a tag connects to a display, is as
If only a few of the transports have been enabled, the first available in the project will be
used. If none of the transport have been configured, the first one in the Server's
configuration file will be used.