Deploying and running workspaces
On the Deployment & Batch Run tab of a workspace, you create deployment configurations for workspaces, deploy the configurations, and run workspaces. You can select which server group to use, change default database connection mappings, manage run parameters, and view deployment and batch run history.
Before a workspace can process data, you must deploy it.
When you deploy a workspace, you create a deployment configuration and send the workspace, with all of its component configurations, to the Streams server, where it is compiled into a Streams application.
The deployment configuration allows you to select a server group and to change default data source mappings. Your changed mappings apply only within the deployment configuration and do not affect the global, default mappings for the server group.
When a workspace is successfully deployed on the Streams server, you can select a saved deployment configuration to run it.
Deployment configurations
Deployment configurations allow you to select the Streams server where the workspace processes data. You can also change the default data source mappings.
Opportunity Detection 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.
Using different deployment configurations, you can test components against new data sources, test new components, test edits to existing components, and build new 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.
For best performance, you would normally run only a single workspace on a production server group.
Data source mapping
Default mappings of data sources and database tables are set when server groups are configured. When you create a deployment configuration, you can change these mappings.
These changes apply only within the deployment configuration; they do not affect the default mappings for the server group.
For example, you might want to use one set of State and Outcome tables with the Test server group in one workspace, and another set of State and Outcome tables with the Test server group in another workspace. You can do this by changing the connector or the database connection on the Data Source Mapping tab of the Details panel for the deployment configuration.
Server group availability
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.
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.
Creating a deployment configuration
Running a workspace
Fields on the Deployment Configuration & Batch Run page
About batch files
Copyright IBM Corporation 2013. All Rights Reserved.