Configuring CMI

Before a task-provider integration can be used, CMI must be configured for the integration.

About this task

Depending on the policy model that you use to manage development projects, you configure branch types and VOBs for CMI (if you use base VersionVault) or streams and project VOBs (if you use UCM). The procedure that follows explains both cases.

Procedure

Create a list of the data types and VOBs that are to participate in the integration:
- For base VersionVault, branch types and VOBs
- For UCM, streams and project VOBs (PVOBs)
Depending on the policy model that you use to manage development projects, do a or b:
1. For base VersionVault, configure the VOBs, creating attribute types for the CMI context, tasks, and task providers:
```
cleartool mkattype -vtype string CC_CMI_CONTEXT
cleartool mkattype -vtype string CC_CMI_TASK
cleartool mkattype -vtype string CC_CMI_PROVIDERS
```
2. For UCM, configure the PVOBs, creating an attribute type for the task providers:
```
cleartool mkattype -vtype string CC_CMI_PROVIDERS
```
If more than one replica is intended to use the integration, use the -shared option to establish the type in the replicas:
```
cleartool mkattype -shared -vtype ...
```
If you create the attribute types in an administrative VOB, use the cptype command to create local copies of the types in all client VOB families that are to participate in the integration. You must copy the types at the site that masters the global type. For example,
```
cleartool cptype -nc attype:CC_CMI_PROVIDERS@\adminvob CC_CMI_TASK@\clientvob 
```
Configure the VOB (base VersionVault) or PVOB (UCM) using the mkcmprovider command. Refer to the reference page for details.
Use the mkcmprovider command to configure the branch types (base VersionVault) or streams (UCM) that are to participate in the integration. Note that it is unnecessary to configure the integration for every stream because child streams inherit their parent streams' configuration.

Example

In this example, CM provider is configured with values that are specified on the command line:

cleartool mkcmprovider -replica original@/var/tmp/myvob -version v1_0 -description "CMI RTC provider" -type cmrtc -connection baseUrl:https://hostname.com/:9443/ccm RTCPROV

The configuration information can be specified in a data file:

cleartool mkcmprovider -vob /var/tmp/myvob -data prov-info-file RTCPROV

where prov-info-file contains the following information

type=cmrtc
version=v1_0
description=CMI RTC Provider
connection.baseUrl=http://hostname.com:9443/ccm

This example shows the configuration of a stream:

cleartool mkcmprovider -stream intStream1 -context "queryUri:<query uri=""> -enable true -options activityFormat:ACT_%task-id_%stream-name,validate:true RTCPROV