Lesson 6: Configure operation behavior (CCM)

In this lesson, you will learn how to configure preconditions for operations in a Change and Configuration Management project area. Preconditions provide you with a way to enforce best practices in your organization by requiring that a condition be true before allowing members to perform an operation.

1. Start the EWM client for Eclipse IDE by clicking Start > All Programs > EWM Client > EWM. Select a directory to use as your local workspace. Close the Welcome page to get to the Workbench. In the Team Artifacts view, click the Create Repository Connection link or right-click in the Team Artifacts view and select New > Jazz Repository Connection. Enter the URI of the change and configuration management repository in the Location URI field. For example: https://hostname.example.com:9443/ccm. Enter Bert’s user ID and password. Clear Remember my password and Automatically log in at startup. Click Finish.
2. In the Team Artifacts view, right-click the repository connection and select Manage Connected Project Areas. Select the Customization Tutorial Project (Change Management) project area. Click Finish.
   The project area is now displayed in the Team Artifacts view.
3. Expand the project area, then expand Source Control. Notice that a default project area stream and component exist. To create a stream for the team area, right-click Source Control and select New > Stream.
4. Enter a name such as Admin UI stream. The default owner of the stream is the team area. In the Components section, click New. Enter a name such as admin-component. Click OK. Click Save to save the stream.
   
5. Log out. Right-click the repository connection and select Properties. On the Jazz Repository Connection page, replace Bert’s User ID and Password entries with Hal’s. Click OK to log on as Hal.
6. Under Source Control, right-click Admin UI stream and select New > Repository Workspace.
   

7. Enter a name, such as Hal’s Admin UI stream Workspace. Click Finish. In the Load Repository Workspace window, click Finish.
8. If the Pending Changes view is not already open, click Window > Show View > Other. Select Jazz Source Control > Pending Changes. Open the Navigator view by clicking Window > Show View > Other > General > Navigator.
9. In the Navigator view, right-click and select New > Project. Select General project. Click Next. Enter a name, such as Sample project. Click Finish. Right-click the project and select Team > Share Project. Select Jazz Source Control. Click Next. Expand the team area stream and select admin-component.
   

   Click Finish to add the project to the admin-component component. Click Pending Changes. Expand the component. The new project is shown in the Outgoing folder.

   

   Right-click Outgoing and select Deliver to deliver the project to the stream. Because the stream is owned by the team area, and Hal's role in the team area has permission to deliver, he can deliver his change set to the stream.

10. Log out. Log on as Bert. Right-click the Customization Tutorial Project (Change Management) project area and select Open to open it. Click the Process Configuration tab. Expand Team Configuration. Click Operation Behavior. In the grid, scroll to the Source Control section. You can set preconditions and follow-up actions for each role. Click the Deliver (client) cell for the Intern role.
    

    Select Preconditions and follow-up actions are configured for this operation. In the Preconditions section, click Add. Select Require Work Items and Comments. In the Constraints list, select an associated work item to require that users associate a work item with every change set that they deliver. This is a good practice because it ensures that there is a history of why you made the change. Because work items include links to the change sets with which they are associated, this practice also provides an easy way to find all changes that are made to fix a defect or implement an enhancement. Click Save to save the project area.

11. Log out. Log on as Hal. In the Navigator view, right-click Sample project and select New > Other. Expand General and select File. Enter a name, such as Readme.txt, then click Finish. Save the file. Click the Pending Changes view. Expand the Unresolved folder to see the files that you have changed but not yet checked in. Right-click Unresolved and select Check-in all to add the change to your repository workspace. The Unresolved folder goes away and the change set moves to the Outgoing folder. Expand the Outgoing folder. Right-click Outgoing and select Deliver. The following message displays in the Team Advisor view.
    
12. To associate a work item with the change set, right-click Enter a Comment in the Outgoing folder in the Pending Changes view and select Related Artifacts > Associate Work Item. At the bottom of the Select Work Items window, click Create work item. Enter a name in the Summary field. Select Task as the type. Select the Admin UI category in the Filed Against field. Select Hal as the owner. Click OK.
    

    Notice that the work item name has taken the place of Enter a comment in the Outgoing folder. Right-click it and select Deliver again. Now that the precondition has been met, the deliver operation succeeds.