Fidessa

The Fidessa Adapter can be configured via the custom-configs.json file distributed with the bundle, as well as via the "customProperties" top-level key in the Fidessa Adapter app definition file. The custom-configs.json file also contains settings for controlling the login flow and configuring the initialization of the io.Connect API and the connection to the io.Connect platform (necessary when the Fidessa Adapter is running outside the io.Connect environment).

The configuration settings are merged and applied in the following order:

1. Hardcoded default settings built into the Fidessa Adapter.
2. Settings from the "adapterConfig" top-level key in the custom-configs.json file are merged with the default settings (new settings are added, existing settings are overridden).
3. Settings from the "customProperties" top-level key in the Fidessa Adapter app definition file are retrieved via the io.Connect API after a connection to the platform has been established and are merged on top of the existing ones (new settings are added, existing settings are overridden).

The custom-configs.json file located in the /adapter folder of the Fidessa Adapter bundle provides static configuration retrieved before the Fidessa Adapter connects to the io.Connect platform. It contains settings for determining the login flow, for configuring the initialization of the io.Connect API and the connection to the io.Connect platform when the adapter is running outside the io.Connect environment, and for the Fidessa Adapter itself.

The custom-configs.json file has the following properties:

The following example demonstrates using the custom-configs.json file to provide settings for connecting to the io.Connect platform (e.g., when the Fidessa Adapter is running in a web browser outside the io.Connect environment, or when the Fidessa Adapter is running inside the io.Connect environment, but you need to provide custom connection settings) and settings for the Fidessa Adapter itself:

{
    // 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)"
    }
}

You can also use the "customProperties" object in the Fidessa Adapter app definition file to provide settings for the Fidessa Adapter. The settings specified in the app definition file will override the ones specified in the "adapterConfig" object in the custom-configs.json file.

The following example demonstrates using the "customProperties" object in the app definition file to provide 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, which will override the ones
    // specified in the `"adapterConfig"` object in the `custom-configs.json` file.
    "customProperties": {
        "reconnectPeriod": "3000(5), 30000"
    }
}

The "adapterConfig" object in the custom-configs.json file and the "customProperties" object in the Fidessa Adapter app definition file have the following properties:

Fidessa WebSocket

If for any reason the connection with the Fidessa WebSocket API is lost, the adapter will follow the instructions set in the "reconnectPeriod" property. By default, it will try to reconnect 5 times at a 2 second interval and after that, it will try to reconnect every 20 seconds.

When running inside io.Connect Browser or Chrome connected to io.Connect Desktop, the adapter uses the "reconnectPeriodInBrowser" property instead. By default, it will try to reconnect 5 times at a 2 second interval and then stop.

Bloomberg Reconnection

When the Fidessa Adapter is used together with the Bloomberg Adapter, it can automatically trigger Bloomberg reconnection attempts. On every genuine channel update received from an interop-enabled app, the adapter invokes the method specified by "bloombergReconnectMethod" (default: "T42.BBG.Reconnect") to ensure the Bloomberg Adapter is connected.

A cooldown mechanism prevents excessive calls: once a reconnection attempt has been made, the adapter waits for the duration specified by "bloombergReconnectCooldownTime" (default: 15 000 ms) before attempting again. If the Bloomberg reconnect method is not registered on the interop bus, the call is skipped silently.

The adapter supports three login flows, controlled by the "disableDirectLogin" and "exposeAPI" properties in custom-configs.json. The internal logic is: autoLogin = !disableDirectLogin && !exposeAPI.

Custom

This flow allows programmatic provisioning of credentials and gateway URL. The adapter dispatches a io.FA_CustomCredentialsFlow CustomEvent on window, and the custom logic handles the credential resolution.

The event detail payload contains:

The continueGWLogin(overrides) function accepts an object with these optional fields:

Example (custom-login-flow.js):

window.addEventListener("io.FA_CustomCredentialsFlow", async ({ detail: {
    log,
    continueGWLogin,
    credentialsConfig: currentCredentials
}}) => {
    log("Executing custom login flow", "info");

    const io = await continueGWLogin({
        ...currentCredentials,
        gwUrl: "ws://localhost:8385",
        username: "myUser",
        password: "myPassword",
    });
});

To activate the Custom Login Flow, set "exposeAPI": true in custom-configs.json and load your event listener script (e.g., custom-login-flow.js) before the adapter initializes.