how to get the list of dashboards that are connecting to OSISoft PI connector in spotfire library

[Shreyam Dasgupta]

how to get the list of dashboards that are connecting to OSISoft PI connector in spotfire library

[Rob Mefford]

Dear Shreyam, I have reviewed your question and concluded we need more information to be able to better understand and answer your question. Can you provide the context for which you are going to use this list? If you can you review these 'Quick Tips on Asking Community Questions': https://community.spotfire.com/wiki/quick-tips-asking-community-questions and share more details? Thanks!"

Rob

[Fredrik Rosell]

Hello,

Adding to what Rob wrote before (if you still looking for information, clarification of the use case would definitely help), here's some suggestions I had started putting together some time ago and just stumbled upon.   

Maybe you are using the OSIsoft PI custom data source (as documented here: https://community.spotfire.com/s/article/Getting-Data-into-TIBCO-Spotfire-from-OSIsoft-PI-Asset-Framework-and-Event-Frames)? For a custom data source like this, I'm not aware of any easy solution. One option could be to do a Library Export of analysis files and grep for SpotfirePS.Framework.OSI. Another possible option for this use case could be to use Spotfire Application Profiler but that would depend on your account being able to open every analysis file in Spotfire Analyst. You can read more about that that tool here: https://docs.tibco.com/pub/spotfire/general/TIB_sfire_applicationprofiler_TechNote.pdf

An alternative to the custom data source mentioned above is to use the PI JDBC driver that OSIsoft provides, together with TIBCO Spotfire Information Services. If that's what you are using, you can use the Library Search to get the information. This is the easy solution so I'll start by describing that below.  

Using Library Search

===================

1. In TIBCO Spotfire Analyst, go to Tools menu > Library Administration.

2. For your search, you can now use the following two search options

* item_type:dxp - this searches for dxp (analysis / dashboard) files

* depends_on(item_id::THE_ID_OF_YOUR_PI_DATASOURCE) - this locates all items that depend on a specific element, such as a data source.

So, for this you need to get the ID of your PI Data Source(s), replacing THE_ID_OF_YOUR_PI_DATASOURCE in the example above. That ID is a GUID, and should look something like 5c74aa11-1116-4e91-8e9b-5b5600bb0f91. There are multiple ways to get it - one easy way is to simply right click on the data source in Information Designer and select "Copy ID".  

Now, combining the search expressions to search for all dxp files that depend on the PI Data Source, the final search expression could look like something like this:

depends_on(item_id::5c74aa11-1116-4e91-8e9b-5b5600bb0f91) item_type:dxp 

(Make sure that you are in the root of the Library when searching to search the entire Library)

Note: The Analyst manual contains detailed documentation, including lots of examples, of Library Search - see 

https://docs.tibco.com/pub/sfire-analyst/latest/doc/html/en-US/TIB_sfire-analyst_UsersGuide/index.htm#t=lib%2Flib_searching_the_library.htm

Using Library Export and grep for SpotfirePS.Framework.OSI

======================================================

1. Do a Library export of the parts of the Library you are interested in (if you have a large Library/large files, consider splitting this to get something more managble), exporting only the analysis files, (e.g. if exporting from the Library Administration tool, select "item of type: Analysis Files").

2. Move the export to your local machine (or where ever you want to perform the following steps) 

3. dxp files are in fact zip files, so do a bulk unzip of all the content in the export.

4. What we are primarily interested in now is the file AnalysisDocument.xml in each of those unzipped dxp files. Using your grep tool of choice, search for "SpotfirePS.Framework.OSI", which should give you the analyses that are using the OSISoft PI connector in some way. 

Note: note the the export should contain a file named meta-data.xml which provides some meta data information about the analysis files - ID, title, created by etc - which might be useful depending on your use case.