mail Notification hlp-notify users when pgs chng

Here is the situation: We have a single branch for our intranet. Several workareas (corresponding to each department) submit content to a single staging area. Each workarea has its own corresponding sub-directory where their html is kept. One of the sub-directories is used for disseminating Web and App development standards. Various people modify this site when standards/best practices change. I want to notify all Developers (email distribution list) anytime this site changes.
Current procedure: at 4pm daily, a windows scheduled task kicks off a bat file that:
1-publishes a new edition
2-deploys the diffs to the prod HTTP servers, and
3-kicks off a custom datadeploy of all metadata.
We are not using Workflow in our deployment procedures nor the OD Scheduler.

I was thinking of creating an additional scheduled task that parses the OD log files, looks to see if any content was deployed in the "standards" subdirectory, if so pull that line and write to a txt file, use the txt to compose an email and ship out to my distribution list.

Is there an easier was to accomplish this. Possibly from the teamsite side?
If I do need to write something to parse the OD log file, it makes it difficult because each deploy appends info to the bottom of the file. I may have to check date as well.

The overall goal is to have a group of people notified every time the "standards" site is updated so it is their responsibility to check it and make sure it does not effect their apps/pages

(Currently on TS 5.5.2, OD5.5.1, DD 5.6)

-Thanks
Chris Papandria
eGovernment
Oakland County, MI

Find more posts tagged with

Comments

Migrateduser

If you upgrade to OD 5.6, you can turn on the reporting feature and then have a SQL query pull out the list of files from the reports database.

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

PSUwin

Hi,
I think that instead of trying to parse the OD log file, that you could more easily parse the OD Manifest log. The file is in the OD log directory with the same naming scheme as the deployment logs with the addition suffix of .mf (at least on our Solaris system). Here's a sample of the contents of this file:

<?xml version="1.0" encoding="UTF-8"?>
<iwodManifest type="transfer">
<profile srcPlatform="UNIX" srcDir="/default/main/Branch1/DE/Public/EDITION/ed_0054" trgPlatform="UNIX"
trgDir="/compub/TTPORTAL/app_web/TTPORTAL/DE"/>
<item path="Contact_Us/Asia_Pacific_long.html" type="FILE" reason="src-is-newer" action="UPDATE" status="COMPLETED" statusDetail="" srcDir="/default/main/Branch1/DE/Public/EDITION/ed_0054/TTPORTAL/DE" trgDir="/compub/TTPORTAL/app_web/TTPORTAL/DE"/>
<item path="Products/R106" type="DIRECTORY" reason="missing-in-src" action="DELETE" status="COMPLETED" statusDetail=""
srcDir="/default/main/Branch1/DE/Public/EDITION/ed_0054/TTPORTAL/DE" trgDir="/compub/TTPORTAL/app_web/TTPORTAL/DE"/>
<item path="Products/R108" type="DIRECTORY" reason="missing-in-dest" action="NEW" status="COMPLETED" statusDetail="" srcDir="/default/main/Branch1/DE/Public/EDITION/ed_0054/TTPORTAL/DE" trgDir="/compub/TTPORTAL/app_web/TTPORTAL/DE"/>
</iwodManifest>

Besides less to parse through, the other advantage of the manifest file is that it is OVER-WRITTEN with each deployment, so you don't have to worry about finding the "right" entries.

You could probably have your parse/mail script called as a DnR AFTER the deployment only on SUCCESS. (The only question re: doing this is whether the manifest is written in time to be "seen" by the DnR script.

Migrateduser

Note that the manifest assumes you are using OpenDeploy 5.6.

Note also that this info can be parsed via the in-memory log facility; i.e., it is piped to the DNR process via STDIN.

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