Fidessa

Overview

The io.Connect Fidessa Adapter provides integration between Fidessa and your interop-enabled apps in order to produce a more efficient financial desktop. Automatic data synchronization eliminates the risk of copy/paste errors and dramatically reduces task completion times. The Fidessa Adapter uses the Fidessa WebSocket API specification.

When the Fidessa Adapter is running, the Fidessa Tracking Groups and the io.Connect Channels are synchronized automatically. Each Fidessa Tracking Group is mapped to a respective io.Connect Channel. This means that when a user clicks an instrument in a Fidessa app, all interop-enabled apps that are on the respective Channel will also start showing data about the clicked instrument and vice versa.

For example, you can have a Fidessa app showing real-time market data about instruments and an in-house data chart app that shows detailed information about an instrument. The chart app is specifically designed for the needs of your company and you want to integrate it with the Fidessa apps. Your development team needs to write only a few lines of code in order to interop-enable the chart app and modify it to work with the io.Connect Channels.

The Fidessa Adapter can be used together with the Bloomberg Adapter in order to achieve data synchronization between Fidessa, Bloomberg and all your interop-enabled apps.

Requirements

The Fidessa Adapter works with all versions of the Fidessa "Managed Enterprise" Trading Platform that support the WebSocket API:

v2018.2.25 and up;
v2019.8.5 and up;
v2020.2.1 and up;

Deployment

The Fidessa Adapter is available as a platform component that can be installed via the io.Connect seed project and can also be delivered as a standalone bundle in the form of an archived (ZIP) file which you can add to your existing deployment. The Fidessa Adapter can be deployed locally or on a cloud server and is platform-independent — the same build output is used for io.Connect Desktop and io.Connect Browser deployments. The only difference is how the adapter is registered and configured on each platform.

9.0 Version Stream

If you are still using the io.Connect Desktop 9.0 version stream, the Fidessa Adapter can be delivered as part of the io.Connect Desktop installer or as a standalone bundle depending on your deployment approach.

Bundle Content

The Fidessa Adapter bundle contains the web app files for the Fidessa Adapter itself, as well as a simple Fidessa Simulator for development and testing purposes:

.
├── adapter/
│   ├── bundle.css                      # Styles for the login UI (used when automatic login is disabled).
│   ├── custom-configs.json             # Configuration file which you can modify with custom settings.
│   ├── custom-login-flow.js            # Script you can use as a starting point if using custom credential flows.
│   ├── fidessa-connector.umd.js        # Minified UMD file for the Fidessa Adapter.
│   ├── fidessa-connector.umd.js.map    # Source map file for the Fidessa Adapter. Remove this for production environments.
│   ├── index.html                      # Host page that loads the Fidessa Adapter.
│   ├── preload-scripts/                # Compatibility preload script for legacy platform environments
│   │                                   # (unnecessary for the io.Connect Desktop 9.0 and 10.0 version streams).
│   └── version.txt                     # Contains the Fidessa Adapter version string.
└── simulator/
    ├── index.html                      # Web UI for sending test messages to the Fidessa Adapter.
    └── server.cjs                      # Fidessa Simulator Node.js WebSocket server.

io.Connect Desktop

To deploy the Fidessa Adapter in io.Connect Desktop:

Install the Fidessa Adapter component via the io.Connect seed project.
Modify the Fidessa Adapter app definition to provide relevant settings for the Fidessa Adapter. Use the "customProperties" top-level key to provide any custom settings for the Fidessa Adapter:

{
    "name": "FidessaAdapter",
    "title": "Fidessa Adapter",
    "type": "window",
    "hidden": true,
    "autoStart": true,
    "service": true,
    "allowMultiple": false,
    "details": {
        "url": "https://my-fidessa-adapter/index.html"
    },
    // Custom settings for the Fidessa Adapter. Can also be set via the `custom-configs.json` file.
    "customProperties": {
        "wsUrl": "ws://localhost:80/ITP/",
        "reconnectPeriod": "3000(5), 30000"
    }
}

⚠️ Note that if you are using auto injection for the @interopio/desktop library, you must also use auto initialization and set the channels and appManager properties of the autoInit object to true. The Fidessa Adapter requires access to the io.Connect Channels in order to synchronize them with the Fidessa Tracking Groups and to the App Management API in order to retrieve any custom settings specified in the app definition.

ℹ️ For more details on the available configuration settings for the Fidessa Adapter, see the Configuration section.

Configure the io.Connect Channels via the system.json system configuration file of io.Connect Desktop in order to map the Fidessa Tracking Groups to the respective io.Connect Channels and provide any custom settings for the shape of the update object used by the Fidessa Adapter for updating the io.Connect Channel contexts.

ℹ️ For more details on configuring the io.Connect Channels, see the Tracking Groups section.

ℹ️ For more details on the Channel context shape and using mapping services, see the Mapping Services section.

9.0 Version Stream

If you are still using the io.Connect Desktop 9.0 version stream:

For step 1, install the Fidessa Adapter via your personalized installer, or add it to your existing deployment if you are using a bundle deployment.
For step 3, use the channels.json Channels configuration file of io.Connect Desktop instead of the system.json file to configure the io.Connect Channels.

io.Connect Browser

To deploy the Fidessa Adapter in io.Connect Browser:

Serve the contents of the /adapter directory from a web server accessible to the end users.
Create an app definition for the Fidessa Adapter to include it in the io.Connect environment. Use the customProperties top-level key to provide any custom settings for the Fidessa Adapter:

import IOBrowserPlatform from "@interopio/browser-platform";

const config = {
    licenseKey: "my-license-key",
    applications: {
        local: [
            {
                name: "FidessaAdapter",
                title: "Fidessa Adapter",
                type: "window",
                details: {
                    url: "https://my-fidessa-adapter/index.html"
                },
                // Custom settings for the Fidessa Adapter. Can also be set via the `custom-configs.json` file.
                customProperties: {
                    wsUrl: "ws://fidessa-host:port/ITP/",
                    reconnectPeriodInBrowser: "2000(5)"
                }
            }
        ]
    }
};

const { io } = await IOBrowserPlatform(config);

ℹ️ For more details on the available configuration settings for the Fidessa Adapter, see the Configuration section.

Configure the io.Connect Channels when initializing the @interopio/browser-platform library in your Main app in order to map the Fidessa Tracking Groups to the respective io.Connect Channels and provide any custom settings for the shape of the update object used by the Fidessa Adapter for updating the io.Connect Channel contexts.

ℹ️ For more details on configuring the io.Connect Channels, see the Tracking Groups section.

ℹ️ For more details on the Channel context shape and using mapping services, see the Mapping Services section.

Web Browser

The Fidessa Adapter can also run in a standalone web browser, outside the io.Connect environment. When running in a web browser, the adapter can connect to the io.Connect Desktop or the io.Connect Browser platform.

To deploy the Fidessa Adapter in a web browser and connect it to an io.Connect platform:

Serve the contents of the /adapter directory from a web server accessible to the end users.
Use the custom-configs.json file to provide the connection details and any custom settings for the Fidessa Adapter:

{
    // Settings for connecting to the io.Connect platform.
    "ioConfig": {
        "gateway": {
            // WebSocket URL of the io.Connect Gateway.
            "ws": "ws://localhost:8385"
        },
        // Valid credentials for authenticating with the io.Connect Gateway.
        "auth": {
            "username": "my-username",
            "password": "my-password"
        }
    },
    // Custom settings for the Fidessa Adapter.
    "adapterConfig": {
        "wsUrl": "ws://fidessa-host:port/ITP/",
        "reconnectPeriodInBrowser": "2000(5)"
    }
}

⚠️ Note that you can also use a custom login flow instead of storing the credentials in a configuration file.

ℹ️ For more details on the available configuration settings for the Fidessa Adapter, see the Configuration section.

Configure the io.Connect Channels in the respective platform in order to map the Fidessa Tracking Groups to the respective io.Connect Channels and provide any custom settings for the shape of the update object used by the Fidessa Adapter for updating the io.Connect Channel contexts.

ℹ️ For more details on configuring the io.Connect Channels, see the Tracking Groups section.

ℹ️ For more details on the Channel context shape and using mapping services, see the Mapping Services section.

Fidessa Simulator

The Fidessa Simulator distributed with the Fidessa Adapter bundle is a mock WebSocket server that emulates the Fidessa WebSocket API. It's intended for development and testing environments where a real Fidessa installation isn't available.

The simulator consists of a Node.js WebSocket server (default HTTP port: 9999, default WebSocket port: 9393) and a web UI for sending test messages to the Fidessa Adapter, which are registered in the io.Connect environment via the respective app definitions included in the Fidessa Adapter bundle.

Changelog

2.0

2.2.0
Release date: 11.06.2026
New Features

Added Channel context key aliases ("aliases" property in the "fidessaGroup" object) that allow mapping standard context key names ("instrument", "client", "order", "instrumentList", "clientList", "orderList") to custom names in the Channel context data. Supports both simple string aliases and per-direction objects with separate "read" and "write" keys.

Added the option to disable inbound channel reading by setting "readDataFieldPath" to null. This disables reading from a Channel for that group, enabling one-way data flow from Fidessa to the io.Connect Channel.

Added the option to disable outbound channel writing by setting "writeDataFieldPath" to null. This disables writing Fidessa updates to a Channel for that group, enabling one-way data flow from the io.Connect Channel to Fidessa.

Added a "disableCache" configuration property that bypasses the bidirectional de-duplication cache so each update is forwarded unconditionally.

Added ID path configuration for instruments, clients, and orders ("instrumentIdPath", "clientIdPath", and "orderIdPath" properties in the "fidessaGroup" object in the io.Connect Channels configuration) that specifies the paths to instrument, client, and order identifiers in the Channel context.

The app definition customProperties key is now read in io.Connect Browser as well (previously supported only for io.Connect Desktop).

Improvements & Bug Fixes

The Fidessa Adapter now uses the setPaths() method of the Shared Contexts API to write Channel data directly to the specified path, eliminating a redundant read on each Fidessa update.

The "contextPrefix" configuration property has been removed. Use Channel Context Key Aliases for customizing the Channel context key names.

The "instrumentIdPath", "clientIdPath", and "orderIdPath" configuration properties have been moved to the io.Connect Channel configuration configuration.

2.1.2
Release date: 12.05.2026
Improvements & Bug Fixes

Updated dependencies to address vulnerabilities.

Included SBOM (Software Bill of Materials) in the package.

2.1.1
Release date: 08.05.2026
Improvements & Bug Fixes

Fixed an issue related to parsing fidessaGroup metadata from the Channel configuration.

2.1.0
Release date: 06.04.2026
Improvements & Bug Fixes

Added a Fidessa Simulator service.

Fixed an issue related to extracting the Fidessa Adapter configuration from the app definition.

1.0

1.0.0
Release date: 29.01.2026
New Features

Bidirectional synchronization of Fidessa Tracking Groups and io.Connect Channels.

Support for instrument, client, and order context types.

Configurable reconnection with back-off strategy.

Integration with external mapping service multi-symbology enrichment of instrument data.

Configurable context prefix for Channel data.

Bloomberg Adapter reconnection support.

Throttled Channel updates to avoid flooding the Fidessa WebSocket.

Application Adapters Documentation

Fidessa