CM Scenario to Configure and Discover Integration

STATUS: WORKING DRAFT This is a working draft of the scenario. It's contents are expected to change.

In other scenario definitions, it focuses on an established configuration to enable the day-to-day flow. This scenario identifies what is needed to take the simpliest amount of information (server URL) and discover the services available to enable the integrations.

Scenario

A scenario without roles:

1. AP tool presents a dialog to collect CM server URL
   1. If need, user auth is challenged
2. If a collection of choices is returned (This can anything: Projects, Teams, Container DBs, Instance DBs)
   1. User selects an item
   2. If another collection is returned, repeat step #2.1, if not next step
3. At a final point some indication of "configuration complete" should be established
   1. A CM system configuration document is received, which may define URLs and level of service support

Pre-conditions:

• An external change management system, with known server URL
• An AP tool requesting to integrate with a CM system

Post-conditions:

• An AP tool is configured to operate against a CM system utilizing open services.

Alternatives:

• Quick setup and no need to discover, where the AP tool know the full URL already - email invitations, etc.
• Other solutions to trigger completeness of setup

Potential Response Document:

 <cm:servicedescription>
  <cm:context>
      <cm:uri>/workitems</cm:uri>
       <cm:handler>changerequest</cm:handler> 
  </cm:context>
  <cm:context>
      <cm:uri>/types</cm:uri>
       <cm:handler>changerequest-types</cm:handler> 
  </cm:context>
 </cm:servicedescription>

Resources

• CM system
• AP tool