Saving the path of the generated file in DCR

Is it possible to grab the path of a resultant file(JSP, HTML etc.) as soon as it is generated by a DCR and save its path in a hidden field of the same DCR?

Find more posts tagged with

Comments

Phanie

Is it possible to grab the path of a resultant file(JSP, HTML etc.) as soon as it is generated by a DCR and save its path in a hidden field of the same DCR?

what is your requirement and why do you want to go through this procedure.

--
Phanie

enthusiast

I am just looking a way to deploy the generated file path to the database table along with the corresponding dcr data.

nipper

Use an extended attribute. DD can automatically push the change out to the DB (assuming you are using DD) and this would be easier than changing a hidden field in the DCR.

Phanie

I am just looking a way to deploy the generated file path to the database table along with the corresponding dcr data.

If that is the scenario I guess you could work with the setting the EA and work on deploying the EA's to database, changing the dcr after you generated the page I am not sure if that is an ideal solution.

--
Phanie

enthusiast

Use an extended attribute. DD can automatically push the change out to the DB (assuming you are using DD) and this would be easier than changing a hidden field in the DCR.

Yes, I am using DD for Teamsite 6.5. Could you please provide some reference of where to look? I actually need to deploy the generated file path information to DB along with the file itself to the file system.

nipper

2 steps, read the TeamSite CLT manual about the command iwextattr - that will set an extended attribute on the file, you can view it by looking at the properties of the DCR in the TS GUI.

To deploy read the DD manual, looking for value-from-attribute field

enthusiast

2 steps, read the TeamSite CLT manual about the command iwextattr - that will set an extended attribute on the file, you can view it by looking at the properties of the DCR in the TS GUI.

To deploy read the DD manual, looking for value-from-attribute field

Just wondering that even if we set an extended attribute for the generated file how is it going to deploy the generated file path along with the dcr database deployment. Are you suggesting to apply the additional extended attribute to the dcr itself? How is it going to know the target path of the generated file?

nipper

Just wondering that even if we set an extended attribute for the generated file how is it going to deploy the generated file path along with the dcr database deployment. Are you suggesting to apply the additional extended attribute to the dcr itself? How is it going to know the target path of the generated file?

You need to write the logic (likely in the TPL) to add the path of the generated file as an EA on the DCR. You also need to more clearly set your requirements. As you stated, you want the DB to have Y:/default/main/branch/workarea/content/some/path/to/some/file.html Is that really what you want or do you need the path relative to the docroot ?

Phanie

Just wondering that even if we set an extended attribute for the generated file how is it going to deploy the generated file path along with the dcr database deployment.

Answer to this was answered by Andy already. Refer dd manual for deploying looking for value-from-attribute field

Are you suggesting to apply the additional extended attribute to the dcr itself? How is it going to know the target path of the generated file?

Andy already answered this question refer clt manual and follow wht are the necessary parameters to pass on.

request you to go through the referenced manuals one.
--
Phanie

enthusiast

You need to write the logic (likely in the TPL) to add the path of the generated file as an EA on the DCR. You also need to more clearly set your requirements. As you stated, you want the DB to have Y:/default/main/branch/workarea/content/some/path/to/some/file.html Is that really what you want or do you need the path relative to the docroot ?

Thanks that's what I thought. Appreciate your help.