Prerequisites

Blueprint is a client-hosted product and requires hosting on a server. The following prerequisites will need to be applied to support this product.

Environment Segregation

If using more than one instance of the product it is recommended to have full environment segregation, which typically means only one instance of the Blueprint solution on one host server. Similarly, connecting Blueprint to the environment of iManage (if applicable) or the database most relevant to it (production to production, development to development and so on).

Account Configuration

There are various accounts required for usage within the Blueprint product. These are listed here.

Hosting Principal

We require creation of a dedicated principal per environment under which the applications and services within this solution will run. Typically, this would be named to clearly convey its intended usage, but this will vary based on internal conventions. A recommended convention would be SVC_BLUEPRINT_<ENV> as the UserPrincipalName (UPN). The credentials for this account should be shared securely with Tiger Eye upon commencement of solution deployment, along with the Entra User Id of this account. This account will additionally be used for performing background auditing operations on Blueprint entities, so must be discoverable through the organisation Entra IAM.

iManage Configuration

Relevant only if connecting Blueprint to an iManage Document Store.

There will be a prerequisite to configure the target iManage instance(s) to authorise connections to these. For purposes of the prerequisites for this document, the following would be needed:

·         A virtual account would be needed set as NRTADMIN (Tier 1 for http://cloudimanage.com ) for the source and KM libraries of each iManage instance being connected.

·         A dedicated library created for storage of Knowledge documents – this would typically be a library called KM with a top-level folder named according to the specific Blueprint instance.

Hosting Server & Configuration

We recommend that the Blueprint solution is hosted on a dedicated server. The applications run background services and need to be able to consume resources dynamically to cater for spikes in demand.

Database Configuration

This product requires a database for storage of transactional data managed by the application. It is strongly recommended that this is on a separate server to the Blueprint solution.

Network Configuration

This product requires access to certain external services as part of its execution. These will need to be configured to be accessible from your host server.

Server & Software Dependencies

The following configuration will need to be performed on the host server:

·         IIS features enabled

·         WebSocket support enabled

·         Secondary VHD mounted (persistent) to a drive letter

The product depends on the following software packages to be installed on the host machine.

·         Dotnet http://ASP.NET Hosting Runtime (Hosting Bundle – Version 8)