anchor.diff:  |Maximum number of attempts any non-CIS ID generator will take to generate a single SNOMED CT identifier, if exceeded it throws an exception.
   |===
   
  +Example for using the built-in service with random ids using the index as the source:
  +
   --------------------------
   snomed:
     ...
     ids:
  -    strategy : CIS
  +    service: EMBEDDED
  +    source: INDEX
  +    strategy : RANDOM
  +    cisBaseUrl : <cis_host_and_port>
  +    cisContextRoot : api
  +    cisUserName : <your-cis-username>
  +    cisPassword : <your-cis-password>
  +    cisClientSoftwareKey : Snow Owl dev. deployment
  +    cisNumberOfPollTries : 1
  +    cisTimeBetweenPollTries : 1000
  +    cisMaxConnections: 100
  +  ...
  +--------------------------
  +
  +
  +Example for using IHTSDO's external CIS service:
  +
  +--------------------------
  +snomed:
  +  ...
  +  ids:
  +    service : CIS
       cisBaseUrl : <cis_host_and_port>
       cisContextRoot : api
       cisUserName : <your-cis-username>
  
positive.code: |Default
  |Description
  
  |strategy
  |INDEX
  |`EMBEDDED`, `CIS` - The source of the ID generation.
  
  |cisBaseUrl
  |
  
negative.code: 
  ==== SNOMED CT Component Identifier Configuration
  
  Snow Owl's SNOMED CT identifier service an be configured to be either using the built-in or IHTSDO's external Component Identifier Service (CIS).  The configuration needs to be placed within the *snomed/ids* section.
  If omitted, then default configuration will be used, which is the built-in (embedded) service based on the index store allocating ids in a sequential fashion.
  
  [cols="3*", options="header"]
  |===
  