Writing DNR output to OpenDeploy log

OD 6.0.2 SP1 - RedHat EL 3.0
TeamSite 6.1 Linux

I am trying to grab the output of the make_toolkit.ipl command being run as a DNR script. I searched the forum and looked at the files in the examples and solutions directories, but have been unable to get anything I write to show up. I tried to just call a dummy perl script and dummy unix script writing without success. What am I doing wrong?

Example Perl Script
#!/usr/bin/perl -w

print STDERR "Built ContentCenter ERR\n";
print STDOUT "Built ContentCenter OUT\n";

Example Unix Script
#!/bin/bash

echo "Building Content Center"

Find more posts tagged with

Comments

Adam Stoller

DNR output doesn't go to the OD log as far as I know. The only thing that gets captured by the log is the XML snippet to indicate failure.
The DNR script itself is responsible for tracking the result of any commands it runs.
In the case of maike_toolkit.ipl I believe you can check the exit status.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

brandon1

How about just redirecting the stdout and stderr of the script on the command line:

script.ipl 1>logFile.log 2>&1

Then if needed you can read the output.

Current Project: TS 6.1
Environment: Windows

Adam Stoller

You can always redirect the output of the sub-script to parse the output - but one hopes that the sub-script or program returns reasonable status information in its exit status so you don't have to write code to parse text which can easily change from version to version.

None of this, however, gets the information into the OD logfile which is a programmatically named and managed logfile by OD.
You *could* perhaps figure out what the name of the logfile is and attempt to append information into the logfile, but doing so may disrupt the flow of data being pumped into that logfile by OD itself - so it's not clear that the end result would be "pleasing" and/or consistant across runs.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Bill Klish

Yeah, checking the exit status is fine. What I was struggling with is, if I am kicking the OD script off in the GUI, I have no easy way to see what the problem of the failure was without sshing to the box and looking at an output file, or to send an email, both of which seem like a lot of effort for something that should be possible. If a user could just browse through the OD log files available in the GUI, it would be simple to find a solve the problem.

This limitation has been around for many versions of OpenDeploy. Are there any plans to add this capability?

Adam Stoller

I don't know - check with Support - I *think* there's an open FR for this - but I'm not sure.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

Feature Request 24647.

Todd Scallan
Sr. Dir. Product Mgt.
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com