reporting published files

Does anyone know how to return a list of published files for a particular branch/directory? as well as a list for all branches?

Find more posts tagged with

Comments

tvaughan

When you say 'published', I assume you just mean files that have been cut into an EDITION, right?

Or do you mean files that have been deployed to some remote server via OpenDeploy?

If you mean 'those that are cut in an edition', couldn't you just use the command 'find' a la:
find your branch/EDITION/number -type f -print

If you want to do it in a GUI, wrap that command in a custom CGI.

If by publish, you mean 'those files deployed via OpenDeploy', it'd depend on how you're deploying now. Give us more info, and we can be more helpful.

Tom

mogoo

look into the command iwlist ...does this do what you're looking for?
maureen

Adam Stoller

Does anyone know how to return a list of published files for a particular branch/directory? as well as a list for all branches?

[tvaughn]... couldn't you just use the command 'find' ...

[mogoo]... look into the command iwlist ...

Assuming we are talking about creating a TeamSite edition - the command you probably want is iwcmp.

find will find every single file in the edition - with no distinction made between those files that were in the previous edition from those that are new to this edition - not likely to be what is desired.

iwlist is for displaying lists of areas within TeamSite like all the sub-branches of /default/main [one level], or all the workareas on a given branch that the indicated user has write access for, etc. This is good for getting a list of the edition names for a branch so you can figure out what you want to compare with what, but other than that, I don't think this is what is being looked for.

iwcmp on the other hand is used to produce a list of differences between any two TeamSite areas - in this case - some previous edition and the latest edition you just created:

iwcmp /default/main/.../EDITION/ed_006 /default/main/.../EDITION/ed_007
f       x+      newfile2
f       f+      newfile1
-       f       newfile4

Which means:
- newfile2 existed in ed_006 but was deleted in ed_007
- newfile1 existed in ed_006 but was modified in ed_007
- newfile4 did not exist in ed_006 but was new in ed_007

If I understood the question correctly - this is probably what was being looked for.

To do this for all branches, you would simply have to recurse through the branches, get a list of the last two editions for each branch (unless you're using explicitly named editions), and then run the iwcmp CLT to generate the list of what changed as of the latest edition.

(I should mention that I'm assuming you want to do this as a scripted process - the TeamSite GUI has File > Compare Any which does the same thing for you, one area at a time)

--fish
(Interwoven Senior Technical Consultant)

Edited by ghoti on 11/16/02 09:55 AM (server time).

skilbur

Thank you for all this information. We are looking to do both. Return the amount of files that were published in the last edition, but we are also looking to find out total number of files published through OpenDeploy. Is there any easy way to do this, or do we have to parse through the log file!?

Thanks,

Chris

Adam Stoller

For OpenDeploy, you should parse the log files - but not the ones that are written out. Look in the manuals about using Deploy-and-Run scripts to parse the in-memory XML logs.

There are some examples under the IWODHOME/solutions/ directory.

--fish
(Interwoven Senior Technical Consultant)

skilbur

Thank you!

skilbur

Hi,

It doesn't look like the IWXML functions are returning anything. Take a look at my code. When I run this script, it doesn't return anything.

Adam Stoller

There appears to have been a communications snafu here. The XML log returned by OpenDeploy on STDIN is for DNR scripts run from *within* the deployment - not for CGI programs run externally to the deployment.

What I would suggest as a quick-fix (because that's all I have time for right now :-) is this:

(a) create a DNR script that runs on the source after deployment, that performs the processing of the XML log data and writes it out into a format you want into a file on the local [TeamSite / Base Server] machine.

(b) Have your CGI script look for that file and read it in and display it.

You might want to have some sort of 'touch' file to let the CGI script know when the file is finished being written.

You'll probably have to have the CGI script poll the location of the file to wait until its written before trying to read it.

Hope that helps...

--fish
(Interwoven Senior Technical Consultant)