nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Extended attribute not getting set

ashish_7800

We are using Teamsite 6.7 SP2,

We are trying to set an extended attribute during generation on the output file using -

my $setAnalyticFileCommand11 = "e:/teamsite/iw-home/bin/iwextattr -s analyticsFile11=analyticsFile1 $outputFile";
`$setAnalyticFileCommand11`;

This was working in Teamsite 6.5 but after the upgrade its not working. But if we regenerate the file again it works, on the second attemp.

Any suggestion ? has anything changed in teamsite 6.7 SP2.

Find more posts tagged with

Comments

nipper

How are you setting it ? In the TPL ?

There are inherent problems with that, what if it is a new file and the setEA happens before the file exists ? What if it tries to write the EA when the file is open for save ?

Can you do it in a WF step instead ?

kumar123

We are using Teamsite 6.7 SP2,

We are trying to set an extended attribute during generation on the output file using -

my $setAnalyticFileCommand11 = "e:/teamsite/iw-home/bin/iwextattr -s analyticsFile11=analyticsFile1 $outputFile";
`$setAnalyticFileCommand11`;

This was working in Teamsite 6.5 but after the upgrade its not working. But if we regenerate the file again it works, on the second attemp.

Any suggestion ? has anything changed in teamsite 6.7 SP2.

Did you find anything in the logs. iwtrace.log or iwevents.log

ashish_7800

Thanks for your respnse, but as i mentioned the same code was working with Teasmite 6.5 and also there are no entries in iwtrace or iwevents log files.

Moving the extended attribute in a workflow will the last option as it would require lot of changes. ( Also i want to know why was it working in earlier version of teamsite )

Where else should i look for more pointers ?

Adam Stoller

Thanks for your respnse, but as i mentioned the same code was working with Teasmite 6.5 and also there are no entries in iwtrace or iwevents log files.

Moving the extended attribute in a workflow will the last option as it would require lot of changes. ( Also i want to know why was it working in earlier version of teamsite )

Where else should i look for more pointers ?

I suggest you beef up debugging / logging in your code so that you can better determine what is [not] happening and why:

my $setAnalyticFileCommand11 = "e:/teamsite/iw-home/bin/iwextattr -s analyticsFile11=analyticsFile1 $outputFile";
warn("CMD: $setAnalyticFileCommand11\n"); [color=red]# replace with custom logging function
if (! -e $outputFile) {
    warn("'$outputFile' does not exist [yet]"); # replace with custom logging function
}
my $results = qx([/color]$setAnalyticFileCommand11 2>&1);
warn("Results: $results\n"); [color=red]# replace with custom logging function[/color]

The output from the above should help.

ashish_7800

Thanks goti,

I tried that and the output file does not exit when the clt tries to set the extended attribute, I can use some mechanism to create the output file (using touch etc) before setting the extended attribute, but i want to understand why was it working with Teamsite 6.5 sp2. ( what has changed )

Adam Stoller

Thanks goti,

I tried that and the output file does not exit when the clt tries to set the extended attribute, I can use some mechanism to create the output file (using touch etc) before setting the extended attribute, but i want to understand why was it working with Teamsite 6.5 sp2. ( what has changed )

It would appear (based solely on your evidence) that what changed was the timing of the creation of the output file. But that's just a guess based on what you've indicated.

AlternatingColorInCrosstab.rptdesign

nipper

Go back and read post number 2.

This approach is, by definition, unstable.

You were probably lucky in 6.5 that it worked, or no one tried a new file and checked to see if the EA was set or not. (IMHO a more likely possibility).

You can either try to live with it, or design a better approach

Frederik

Rather by coincidence I found that the recent KB article 63330 talks about this.

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=63330

quoting:
When you try to set extended attributes through tpl file during page generation process, is failing for first time as the file is completely created until tpl ends.
...
The following FR is also logged for this.TS-8304 - Setting extended attributes through tpl file during page generation process.

The KB is not explicit about which TS versions this started breaking with, but I suppose we can conclude it's somewhere between 6.5 and 6.7...

sample.zip

Adam Stoller

Rather by coincidence I found that the recent KB article 63330 talks about this.

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=63330

quoting:
When you try to set extended attributes through tpl file during page generation process, is failing for first time as the file is completely created until tpl ends.
...
The following FR is also logged for this.TS-8304 - Setting extended attributes through tpl file during page generation process.

The KB is not explicit about which TS versions this started breaking with, but I suppose we can conclude it's somewhere between 6.5 and 6.7...

That might be - I seem to recall (perhaps in 5.5.2 or 6.5) that the primary output file was created at the beginning of the PT process, such that one could set the EAs, etc, on the output file at any point in the page generation process. If that behavior did change (which is certainly possible), it would explain the behavior being experienced.

oduiubo

Any suggestion ? has anything changed in teamsite 6.7 SP2.

I found similar issue, but I decided just slightly change logic. If I cannot set immediately attributes to the generated file (probably file does not exists yet) I went to AJAX. When generate process finished (and generation process completed file will exists for sure) I insert in body tag attribute onload and call other script which is set external attributes to the file.
Yes, it is an additional script but it is working.
You can use different approach like open new ostream and flash your generated file there and in main window just show link on the generated file. When you are going to close this an additional ostream file suppose to be created and you will have ability set external attribute on that file.
Personally I prefer second method because you can provide some extra information about generated file and if necessarily you can put link with workflow instantiation.

bestFitLineInBarChartWithStringAxis.rptdesign