Data source configuration element properties
Open the Properties view in Document Studio and select a Data source configuration element. The Properties view displays these available properties for data source configurations.
General properties
In the All properties tab, these properties are at the top level, in the Metadata, and in the sections.
| Type | Value | Description |
|---|---|---|
| Tag | String | Tag name for the element. This property cannot be edited. |
| Name | String | The name of the element. |
| Description | String | A summary or note about this element. |
| Assignment | String | The variable assignments that are done in the element. |
| Condition | String | A script that can apply variables or attributes as conditions on the element. |
Data properties
In the All properties tab, expand Formatting to set these properties.
| Type | Value | Description |
|---|---|---|
| Target data source | String | Data source to be configured. |
| Inherited data configuration | String | Name of the data source, which is used for configuring the Target data source property. |
Dynamic configuration properties
| Type | Value | Description |
|---|---|---|
| URI | File path | The path to the data source resource. |
| Username | String | Username to log in into the data source
application. If authentication errors are there and the Ignore data source
configuration errors property is set to true, the document-style
report generation continues. If authentication errors are there and the Ignore data
source configuration errors property is set to false, the
document-style report generation cancels. For more information about the Ignore data
source configuration errors property, see .
For more information about how usernames and passwords are stored, see Security considerations for IBM Engineering Lifecycle Optimization - Publishing. |
| Password | String | Password to log in into the data source
application. If authentication errors are there and the Ignore data source
configuration errors property is set to true, the document-style
report generation continues. If authentication errors are there and the Ignore data
source configuration errors property is set to false, the
document-style report generation cancels. For more information about the Ignore data
source configuration errors property, see .
For more information about how usernames and passwords are stored, see Security considerations for IBM Engineering Lifecycle Optimization - Publishing. |
| Authentication Method | auto, basic, form, oauth, oauth-oslc,smart-card, ssl-certificate, Kerberos-SPNEGO | Default value:
auto
The authentication type for connecting to the data source. If no authentication type is specified, each type is tested until the correct type is found. This type is cached as the authentication type setting for future connections within a current document-style report generation. For subsequent document-style report generation, even when running in the same Launcher or Document Studio instance, the initial auto connection repeats the process by testing each type to find and cache the correct type. If authentication errors are there and the Ignore data source configuration errors property is set to true, the document-style report generation continues. If authentication errors are there and the Ignore data source configuration errors property is set to false, the document-style report generation cancels. For more information about the Ignore data source configuration errors property, see Runtime metadata properties reference. |
| Command | String | A script to run when the output is generated. |
| Ignored | true, false | Default value: false Set to true to exclude a template from generating when you are running multiple templates from one document specification. |
| Accept header | image/jpeg, text/html, application/xml, */* | A specific type of resource that is retrieved from the data source. |
| Extra headers | String | Enter a POX (Plain Old XML) link, for example
<http://jazz.net/ns/profile#POX>;
rel="profile" Tip: If document-style report generation fails, for example, reporting from IBM Engineering Requirements Management DOORS® Next to
as
template, try setting a placeholder dummy value, such as
RemovePOX.Credentials are inherited from a parent data source with POX profile header. If you don't want the inherited data source to use a POX header, you must set a placeholder value. Otherwise, the POX profile header is used as part of the inheritance. |
| Configuration context | Configuration context | Add the Configuration context header during data request. |