Testing database script installation

Question

From the documentation 
 
 On Verint-hosted instances of Verint Community, each enabled plugin gets a custom schema and a connection string which provides access only to that schema. This helps to prevent conflicts between different plugins within access to the database and prevents plugins from accessing the Verint Community schema which is not an extensibility point. 
 On self-hosted instances of Verint Community, Environment Configuration must be setup to provide plugins with connection strings manually. ISqlServerConnectedPlugins in self-hosted environments without corresponding connection strings defined in the Plugin Connection Strings section of environment configuration will not be initialized and an exception will be logged identifying the missing environment configuration. Even when self-hosting, it is recommended to create unique schemas for each plugin and set that schema as the default schema for plugin-specific logins for each database-connected plugin. 
 
 1) In local development i.e. self hosted how can you emulate having a different schema? 
 2) If we get a copy of a client solution so we can have a local test environment, how do we configure the Environment strings to match the schema that as auto assigned to the plugin in SaaS?

Brian Dooley · Accepted Answer

These are the permissions you'll need to assign to the user: ALTER USER [{NewUser}] WITH DEFAULT_SCHEMA = [{pluginSchema.Schema}];

GRANT SELECT ON SCHEMA::[Api] TO [{NewUser}]; -- To access the permissions view

GRANT SELECT, INSERT, UPDATE, DELETE, EXECUTE, ALTER ON SCHEMA::[{pluginSchema.Schema}] TO [{NewUser}];

GRANT CREATE TABLE, CREATE VIEW, CREATE FUNCTION, CREATE PROCEDURE, CREATE TYPE, CREATE SYNONYM TO [{NewUser}];

Michael Monteleone · Answer

1) Please see details in Environment Configuratin regarding "Plugin Connection Strings". 
 For example, you can add the following to your environmental configuration, either via the json configuration or even via a .env override. 
 "PluginConnectionStrings": {
 "My.Name.Space.MySqlServerConnectedPlugin, My.Assembly": "MY_CONNECTION_STRING"
} 
 2) I'm not quite sure I follow the question. If you have a local environment, you can provide any connection string for that plugin's connection string.

Testing database script installation

Top Replies