Skip to main content

Brainspace

Brainspace Integration Requirements

Relativity® Integration for versions 9.7+ & 10.x+ (including RelativityOne cloud)

The Relativity® Plus connector requires only Relativity® API access via port 443 (https) and only works with Relativity® versions 9.7 and newer. In Brainspace 6.7 you could use the Relativity® Connector on datasets originally built with the Relativity® Connector, as long as the “Use Legacy Names” toggle is on.

Relativity® Integration for versions 9.2 – 9.7 (on-prem deployments only)

Brainspace integrates with older versions of Relativity® using our legacy Relativity® connector. This connector requires access to the Relativity® REST API (https) and direct SQL access (TCP 1433) using Brainspace legacy Relativity® connector.

Brainspace’s legacy Relativity® connector uses the RSAPI service to determine user access permissions to assigned workspaces, and MS-SQL access for high-speed ingestion and sync of Brainspace data back to Relativity®. The Brainspace Relativity® plugin respects the Relativity® ACLs (access control list) for data streaming and overlay back to Relativity® – Workspace access and updates will only occur with proper user authentication credentials.

Integrating with a Single Relativity® SQL Instance

  • Brainspace utilizes TCP port 1433 (by default; please indicate if you are using a non-standard SQL port) to access the Relativity® MS-SQL database for integration.

Integrating with Multiple/Distributed Relativity® SQL Instances

  • If using Static ports – Configure each SQL instance with the same port (typically 1433).

  • If using Dynamic ports – The MS SQL Browser Service must be configured (typically port 1434 UDP) for Brainspace to determine the actual port in use for each SQL instance. The full range of dynamic ports in use must be allowed through the firewall from the Brainspace Application server to each Relativity® SQL instance.

The Relativity® MS-SQL instance must be configured and available prior to Brainspace installation. This account must have EDDSDBO user rights. If unable to use EDDSDBO account, the provided account permissions will need to either be added manually or a script written to automatically update the “brainspace” user to all new workspaces.

  • Server Role = public

  • For Workspaces to be used with Brainspace, the database user needs db_datareader, db_datawriter, db_ddladmin and roles

  • For the main EDDS database, the database user needs db_datareader. For enhanced security, a custom role providing read only access to the Case and ResourceServer tables may be used.

  • For additional security, set the minimum required column access in Relativity® EDDS db:

    • Case ArtifactId

    • Case ServerId

    • ResourceServer ArtifactId

    • ResourceServer Name

      • The MS-SQL account must be configured on all SQL instances in a distributed SQL environment.

In this section: