Checking DNR execution - ideas?

System

Hi All -
This is a bit of a repost from several months ago, but I'm now working on it, so it's worth a new look. This is all taking place on Solaris, with OpenDeploy 6.02, patched up to current.

We're planning on doing some Content-Provisioning-like development, where we're using dnr scripts to control some environment and application configuration on remote servers.

So far, we've:
got the OD configurations set up to allow dnr execution ,
tested out the execution of scripts on the target,
using parameter substition from within the GUI,
and we've tested using the response code="-2" to force deployment failure.

All's going pretty well.

What we're interested in is a 'next step' in dnr execution, where we test the success of executing a dnr and then perform some processing based on the test. For example; if we call a dnr script to create a new Tomcat instance, we'd like to go run a test to see that the instance was actually created.

What we do with the results of the test can vary, but most likely the results will be used to control a workflow's branching.

So, taking the above example a bit further:
Let's say a TeamSite workflow task calls an OpenDeploy config that executes a dnr on a remote machine, creating a new Tomcat instance.
We'd then like to verify that the instance has been created correctly and feed that information back to the TeamSite workflow and the workflow would continue on to it's next step.
If a problem with the Tomcat instance creation is detected, that information would also be related back to the workflow, which would then branch off into an error routine in which the correct people are notified and any additional cleanup tasks might take place before trying again.

We're working through a set of ways that the above might take place, but would greatly appreciate any input that others have, either from practical experience or from from a theoretical standpoint.

Ideas, anyone?

I'll try to post updates on our progress also!

Many thanks,
Wally Box
Nike, Inc.