How to troubleshoot unexpected introspection results of a MongoDB datasource?

How to troubleshoot unexpected introspection results of a MongoDB datasource?

book

Article ID: KB0076788

calendar_today

Updated On:

Products Versions
TIBCO Data Virtualization All supported versions

Description

Scenario:
Introspection of MongoDB in the TIBCO Data Virtualization (TDV) server may result in an unexpected format, such as the use of different delimiters or names referenced in the MongoDB objects.
 

Issue/Introduction

How to troubleshoot unexpected introspection results of a MongoDB datasource?

Resolution

Before contacting TIBCO Support, check your TDV install for the presence of any .rsd files.  These optional files are MongoDB table/view schema files that are utilized by the MongoDB driver to override connection behavior to MongoDB.  They are not native to TDV, these files are normally intentionally created and utilized by MongoDB consumers.  One way these files could unknowingly be created would be from a user who enables  the 'GenerateSchemaFiles' flag in \packages\MongoDB_1\conf\MongoDB_properties.yaml.


The .rsd files could exist in any directory that is referred to by the "Location" attribute setting you see in the "Connections" tab of your MongoDB datasource when opened in our Studio.  If the "Location" field is blank, any present .rsd files could also be active by existing in your /bin directory because that is likely to be the current working directory where the TDV jvm is started. 

If any .rsd files are found, you can then continue to troubleshoot the effects by (temporarily) removing these files, or by altering the "Location" attribute to redirect its path to any empty directory in order to deactivate the use of the .rsd files.