html name from dcr

Hi All,

I am using IW 6.5 on solaris server.
I need to identify the all the htmls generated from a particular dcr in TS.

Any idea how can that be done?

TIA

Find more posts tagged with

Comments

jbonifaci

It's not going to be easy. You're going to need to recursively search through all of the generated files in the workarea and look at the following EAs:

TeamSite/Templating/PrimaryDCR
TeamSite/Templating/PrimaryDocumentType
TeamSite/Templating/PrimaryPT

If you want to make it easier for future implementations, you'll want to add something to your tpls to add/update an EA on the DCR any time a page is generated. Something like TeamSite/Templating/GeneratedPages or whatever you come up with.

~Jeff

chart.zip

Migrateduser

Otherwise, you could enforce a policy such that anyone who wants to generate a page from this DCT needs to do so through workflow. This way, your workflow can write to a file which basically catalogs all of the generated pages. Oh, you'll also need to enforce a policy that they go through workflow for deletes, also.

This is more of a long-term plan -- Jeff's suggestion works with less programming / customization but is far less performant at run-time.

prash_sape

Hi again..

TeamSite/Templating/PrimaryDCR
TeamSite/Templating/PrimaryDocumentType
TeamSite/Templating/PrimaryPT

I can see the above EAs for the html generated but using what command I can get it through the bash prompt?

Migrateduser

iwextattr -g [attribute name] [vpath]

... will get you the specified attribute name on a given file. The -l option lists all attributes on a given file. What Jeff is saying is that you would need to iterate through ALL files that you want to search and run this command to find the associated DCR.

Dave

prash_sape

Thanks friends, its working perfectly fine.

Adam Stoller

iwextattr -g [attribute name] [vpath]

... will get you the specified attribute name on a given file. The -l option lists all attributes on a given file. What Jeff is saying is that you would need to iterate through ALL files that you want to search and run this command to find the associated DCR.

Dave

If you want to do a bit of parsing on the results instead of calling iwextattr twice per generated file (once for TeamSite/Templating/PrimayDCR and once for TeamSite/Templating/PrimaryDataType) - you could use iwextattr -l -r PrimaryD vpath-to-file - or if you like it in XML format - iwextattr -l -x -r PrimaryD vpath-to-file - making only one call to iwextattr per file tends to be more efficient.

coloredbycate.JPG