Author Topic: Find datasource(s) associated with a package  (Read 450 times)

Offline kulkarni

  • Senior Member
  • ****
  • Posts: 54
  • Forum Citizenship: +0/-0
Find datasource(s) associated with a package
« on: 08 May 2010 12:49:35 am »
Is there a way to identify the datasources associated with a package?  We are trying to come up with a matrix of it (package and its datasources).  I am running short on ideas to achieve it without SDK.  Hence posted it in SDK forum.

I'd appreciate any guidance (SDK or non-SDK).  Thank you.

Offline kulkarni

  • Senior Member
  • ****
  • Posts: 54
  • Forum Citizenship: +0/-0
Re: Find datasource(s) associated with a package
« Reply #1 on: 19 May 2010 10:52:50 pm »
Checking to see if anyone has ideas to implement this?

Offline xiska

  • Full Member
  • ***
  • Posts: 41
  • Forum Citizenship: +3/-0
Re: Find datasource(s) associated with a package
« Reply #2 on: 12 Jun 2010 03:14:40 pm »
Hi

There are two ways to do that. But they depending on your requirements: online or offline, with history or without.
Please remember that the datasourcename is not fixed. It can be overwritten depending on the user.

1. SDK: get the model definition of a package, parse this xml, extract the data sources and display them. This can display the history and can be used as a portlet also known as a extended application.

2. The Framework manager model is a big xml file. Write a xslt file to transform one or more model.xml file into a html file. To do this you need a xsl parser like saxon. This is the ofline version without history.

Other ways are cm Queries which needs to be exported as xml ...

My recommendation: use #1. Take the basicnav.jsp and rewrite it to your needs. Then use it like a portal tab.

Have fun.

Offline kulkarni

  • Senior Member
  • ****
  • Posts: 54
  • Forum Citizenship: +0/-0
Re: Find datasource(s) associated with a package
« Reply #3 on: 16 Jun 2010 12:07:59 am »
Currently, I am attempting to do approach #2.  Trying to gather several xml files spread over different folders and then using xslt to extract info.  I am not pleased with this approach though.

Can you explain little bit more on appraoch #1?  I am not aware of SDK methods to extract package xml from content store.  Any guidance on this is appreciated.

Thank you.