Configuring for discovery over OSLC Automation Session

TADDM can run Level 2, and some Level 3 discoveries by using OSLC.

To configure the discovery on scope sets provided by OSLC Execute Automation Service Providers, you must meet the following requirements:

You must have at least one installed and working OSLC Execute Automation Service Provider.
TADDM must be connected to OSLC Execute Automation Service Provider.

To run a discovery over OSLC Automation Session, complete the following steps:

Add access credentials of the product that you are integrating with to the access list. To do so, create a new access list entry of type “Integration”>”OSLC Automation”.
If you are integrating TADDM with ITM, provide ITM TEPS credentials. During the discovery, OSLC Automation access list entries and ITM access list entry type are used to ensure compatibility with earlier versions.
Check the discovery scope. The scope sets are created periodically by OSLCAutomationAgent. The new scope sets are listed in the Scope Sets tab. If you are integrating TADDM with ITM, one scope set per each ITM TEMS is created. You can run OSLCAutomationAgent manually by using the following command:
```
/taddm/dist/support/bin/runtopobuild.sh -a OSLCAutomationAgent
```
Configure discovery properties that allow using OSLC Automation Session. You can set the properties in the collation.properties file or in a new custom discovery profile.
- The collation.properties file:
```
com.ibm.cdb.session.prefer.OSLCAutomation=true
com.ibm.cdb.session.allow.OSLCAutomation=true
```
  The examples of scoped properties:
```
com.ibm.cdb.session.prefer.OSLCAutomation.9.222.222.124=false
com.ibm.cdb.session.prefer.OSLCAutomation.Level_3_Discovery=false
```
- Custom discovery profile. In Discovery Management Console, create a new discovery profile and configure the Platform Properties tab in the following way:
```
com.ibm.cdb.session.allow.OSLCAutomation=true
com.ibm.cdb.session.prefer.OSLCAutomation=true
```
Run a regular discovery of scopes created by OSLCAutomationAgent by choosing either of the following methods:
- The default L2, or L3 profile when the collation.properties file is configured to support OSLCAutomation Session.
- The new discovery profile with properly configured Platform Properties tab.