About deployment configurations

Before you can run a workspace to process data, you create a deployment configuration for it and then deploy it.

When you deploy a configuration, the workspace is compiled into a Streams application and sent with all of its component logic to the Streams server.

When a workspace is successfully deployed on the Streams server, you can select and run a saved deployment configuration to run the workspace.

Each workspace has its own configuration deployment, and multiple configuration deployments can be running simultaneously.

Server group availability in deployment configurations

Opportunity Detect environments typically include at least one test server group and one production server group. For any workspace, you can create a deployment configuration for each server group configured in your system.

The server groups available for selection in a deployment configuration are those that are not yet mapped in any deployment configuration for the workspace you are working with. You can use a server group only once for each workspace, but you can use the same server group in deployment configurations for different workspaces.

For best performance, you would normally run only a single workspace on a production server group.

Option to use different configurations for test and production

Using different deployment configurations, you can test components against new data sources, test new components, and test edits to existing components without affecting the production environment.

For example, you can create a deployment configuration that allows you to deploy a workspace to the test server group to test it, and you can create another configuration that allows you to deploy the workspace to the production server group for production runs. By changing data source mappings, you can separate the test data from the production data in your State History and Outcome tables.

Required permissions

The permissions assigned to a user determine which server groups they can access when creating a deployment configuration, as follows.

A user with the Run for testing permission sees only server groups designated for test usage. The built-in OpDetectTestDesigner role has this permission.
A user with the Run for production permission sees only server groups designated for production usage. The built-in OpDetectProductionDesigner role has this permission.
To have access to both test and production server groups, a user must have both of the permissions listed above. The built-in OpDetectAdmin role has both of these permissions.

In addition, your system administrator may also create custom roles that include the required permissions.

Redeployment requirement when data sources change

If you add or change fields in a data source or data source connector, you must redeploy any workspaces with data source connectors that use the changed data source.