Integrate with Self-Service Analytics and Agentic Intelligence

Contents[Hide]

1. Overview

If you also have them installed, Custom Analytics version 26.2 and higher can integrate with Logi Composer, now Simba Self-Service Analytics, and with Simba Agentic Intelligence.

Once an administrator has configured them, users registered in both modules can access functionality from the other module.

2. Configuration settings

A System Administrator can set the following configuration settings found in the Logi Composer Integration category. Click to show the Advanced Settings in the toolbar to see them:

Base URL – Set this to the URL for Self-Service Analytics (Logi Composer), e.g., https://composer.example.com/composer/, or to the Composer/Discovery subpath of Simba Agentic Intelligence, e.g., https://simba.example.com/discovery/.
Client ID and Client Secret – Obtain and set these by registering this module as a trusted access client in the other module. You can use the Swagger UI built into Self-Service Analytics (e.g., /composer/swagger-ui.html) or Simba Agentic Intelligence (e.g., /discovery/swagger-ui.html) to use the trusted-access-client API endpoints to create a client while logged in as administrator, then copy the values of client_id and client_secret in the response.

Important

If the other module is deployed to a different domain or origin, you must enable CORS (cross-origin resource sharing) in its configuration to allow access to browser-based functionality.

3. Composer data provider

When creating a Custom Analytics data connector, you can set the Data Provider to Composer to access Self-Service Analytics or Agentic Intelligence data sources. If you upgraded from a previous version of Logi Symphony with an existing Visual Data Discovery data connector, it should be set to this provider automatically.

The Address setting of this data connector should point to the OData API endpoint for Self-Service Analytics (Logi Composer), e.g., https://composer.example.com/composer/api/sources/odata/, or for the Composer/Discovery subpath of Simba Agentic Intelligence, e.g., https://simba.example.com/discovery/api/sources/odata/.

Next, choose an Authentication method:

Trusted Access – This option relies on the trusted access client configuration described above to allow each user that exists in both modules to access data with their corresponding access rights. The User Name setting is used for discovering available data structures as the specified user, but data access instead occurs for each user separately.
Basic HTTP – This option logs into the other module with the specified credentials regardless of the user logged into this module. This option does not require additional configuration as a trusted access client.

4. Self-Service Analytics content

If Logi Composer is configured, when editing a dashboard, report, or other view, you can click Components in the toolbar and choose Logi Composer to add Self-Service Analytics content.

Using the Properties window, you can choose either some existing content to display or allow viewers to create their own new self-service dashboard or report.

5. Simba Intelligence chat

If the Logi Composer path of Simba Agentic Intelligence is configured as described above, you can enable the Simba Intellignce chatbot to be accessible to viewers of a dashboard, report, or other view.

While editing the view and with nothing selected on the canvas, open the Properties window for the view and enable Simba Intelligence Chat. You can then optionally narrow down the list of data sources available to chatbot users by clicking + next to Chat Sources and selecting specific sources.

In view mode, users can now click Chat in the toolbar, or right-click or long-tap a blank part of the canvas to access it from the context menu.

6. EDC service

To enable Simba Self-Service Analytics (Logi Composer) or Agentic Intelligence to access data cube data from Custom Analytics, install and configure the Composer Connector service for Dundas BI, also known as an EDC service.

If Custom Analytics is installed directly on Windows, relaunch the Deployment Application and click Extras to find the option Add EDC Service.
If Custom Analytics is installed directly on Linux, relaunch the Deployment Wizard and choose the option Add EDC Service.
When deployed on Kubernetes, use the EDC section of properties in the Helm chart.

Ensure the Consul URL setting corresponds to the Consul service running in your deployment of Self-Service Analytics or Agentic Intelligence.

Take note of the service port you chose for the EDC service. Once it is deployed and running, configure Self-Service Analytics or Agentic Intelligence:

Register it as a new connector server, with the Server URL pointed to the Custom Analytics server at that port number or to the EDC container (see "Register a New Connector Server").
Define a new connector for that connector server (see "Define a New Connector").
Now you can create a new connection to use in your sources: enter a Custom Analytics Username and Password in the new connection. To optionally impersonate another user, enter the username and password of a Custom Analytics administrator, then enter the other username into the optional Impersonate Account setting.

Because the parameters have changed, existing connections for Managed Dashboards & Reports from Logi Symphony before version 26.2 will need to be replaced as described above.

Custom Analytics Support

Documentation