Q/A on the Modification of CIS Datasource Capabilities
Article ID: KB0081435
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | 7.0.0 and later |
Description
Where should I customize datasource capabilities?
There are 2 places in our server installation where custom changes can be made:
<install dir>/apps/dlm/<adapter type>/conf/<adapter name>.capabilities
or
<install dir>/conf/adapters/system/<adapter name>/<adapter name>_values.xml
Why are there two places to do this in my install?
<install dir>/apps/dlm/<adapter type>/conf/<adapter name>.capabilities
is the legacy path where user modifications could be made.
This is intended to be phased out in the future, tbd. It is still fully functional now.
<install dir>/conf/adapters/system/<adapter name>/<adapter name>_values.xml
is the 2nd generation preferred location. The configuration info is stored here in xml format.
Which method should I choose to make my changes?
Changes made in the 2nd-gen location survives upgrade/migration/patching and also be included in .car file exports.
This is the preferred location to make your changes.
Also, notice there is a path for every adapter you see in the Studio UI, when creating a new datasource.
You can target the exact adapter you want to modify.
Changes made in the legacy system are lost during major upgrades when you migrate to a new install.
Those changes are not carried out into the .car file export.
Patching of the install also causes the changes to the .capabilities files to be abandoned due to the versioning of these .capabilities files.
In addition, the various versioned .capabilities files can be confusing and could contribute to user error.
Why should I be bothered with the legacy system?
While troubleshooting and experimenting, it's easier to edit the line-by-line texts in the .capabilities files, rather than edit or compose new xml elements in the values .xml files. It's also easier to read through the .capabilities files if you are trying to research and test new capabilities that you want to develop yourself.
Once you arrive at a solution, then compose the xml elements needed for addition into the _values.xml file for permanence. You may consult Tibco DV support for assistance with the composure of the xml elements.
There are 2 places in our server installation where custom changes can be made:
<install dir>/apps/dlm/<adapter type>/conf/<adapter name>.capabilities
or
<install dir>/conf/adapters/system/<adapter name>/<adapter name>_values.xml
Why are there two places to do this in my install?
<install dir>/apps/dlm/<adapter type>/conf/<adapter name>.capabilities
is the legacy path where user modifications could be made.
This is intended to be phased out in the future, tbd. It is still fully functional now.
<install dir>/conf/adapters/system/<adapter name>/<adapter name>_values.xml
is the 2nd generation preferred location. The configuration info is stored here in xml format.
Which method should I choose to make my changes?
Changes made in the 2nd-gen location survives upgrade/migration/patching and also be included in .car file exports.
This is the preferred location to make your changes.
Also, notice there is a path for every adapter you see in the Studio UI, when creating a new datasource.
You can target the exact adapter you want to modify.
Changes made in the legacy system are lost during major upgrades when you migrate to a new install.
Those changes are not carried out into the .car file export.
Patching of the install also causes the changes to the .capabilities files to be abandoned due to the versioning of these .capabilities files.
In addition, the various versioned .capabilities files can be confusing and could contribute to user error.
Why should I be bothered with the legacy system?
While troubleshooting and experimenting, it's easier to edit the line-by-line texts in the .capabilities files, rather than edit or compose new xml elements in the values .xml files. It's also easier to read through the .capabilities files if you are trying to research and test new capabilities that you want to develop yourself.
Once you arrive at a solution, then compose the xml elements needed for addition into the _values.xml file for permanence. You may consult Tibco DV support for assistance with the composure of the xml elements.
Issue/Introduction
This document describes the modification of Tibco Data Virtualization (TDV) datasource capabilities.
Feedback
Yes
No
Powered by
