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; } } }

Use OD to track file modification

Joost

Hi,

Just got working with TeamSite and OpenDeploy a month ago. One thing I'd like to report on is file modification. I already figured out that using iwrlog does a similar thing on files in workarea's. But I'm interested in when the files were deployed (as that is what visitors of the site see).

One (very complicated) way of doing this is by looking in OD logs. Is there an easier way?

Tanx!

Joost

Find more posts tagged with

Comments

Michael

HI Joost,

If this is a requirement then you might want to consider options such as:
- if your deployments are triggered via a workflow then adding an external task to your workflow after the deployment which logs the deployment of the files.
- if you are not using a workflow you might instead use a Deploy N Run script (DNR) which is executed after the successful execution of the deployment and logs which files were deployed.

Either of these processes could write out a simple text or xml log file of your design. Or perhaps you would like to add the latest deployment date/time as an extended attribute to your piece of content.

Hope these ideas are of assistance.

Cheers
Michael

Joost

Tanx! I'll look into that DNR script as we manually deploy over here.

BTW: that's not an existing script is it?

Edited by Joost on 08/15/03 03:18 AM (server time).

sample_input_file.txt

Adam Stoller

If you're using OpenDeploy 5.6.0 (recommend installing SP1) - you can enable event-reporting, which stores information like this into a DB, from which you could create a custom script to query as per your needs.

Chapter 12 of the OpenDeploy 5.6 Reference Manual covers the reporting DB's schema (though make sure to check release notes for SPs to verify if any additional / changed information is available)

Also, Chapter 7 in the OpenDeploy 5.6 Administrator's Guide covers the reporting mechanism and recommends that, for production-use purposes, that you supply your own production-strength DB in place of the one included in the distribution which is primarily for demonstration / proof-of-concept purposes.

--fish
(Interwoven Senior Technical Consultant)

Edited by ghoti on 08/15/03 03:25 AM (server time).

Michael

Sorry, not it is not an existing script -- just an idea off the top of my head.

If you are using OD 5.6.0 then I would run with ghoti's suggestion -- it is always nicer to leverage off existing functionality and avoid creating more pools of data and work for yourself Smiley Happy

Joost

Got OD 5.5, so I guess I'll look into making our own script...

Migrateduser

You may want to see how difficult it is to upgrade. OD 5.5 is over a year old now, and there are lots of bug fixes and improvements. Newer versions of OD on the sender side talk to older versions of the receiver, and older versions of TeamSite, so you need not upgrade everything at once.

Just some food for thought.

lissa

sample_input_file.zip

Migrateduser

...and the OD 5.6 installer takes care of the upgrade process from 5.5.1 automagically... ;-)

Note that if you upgrade the Base Server to 5.6, you must also upgrade the Admin software to 5.6 (which you would do anyway to pick up the new reporting feature.) As Lissa points out, the receivers can remain at 5.5.1 (or 5.0.1 if you have those too.)

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com