OpenDeploy variables for DnR, yet?

I found a thread from 2004 (http://devnet.interwoven.com/forums_vb/showthread.php?t=9511) that said there weren't any OpenDeploy variables that could be passed to a dnr script. I was wondering if that had changed with any of the later releases of OD.

I have a dnr (perl) script that sends an email to me if a deployment fails. We are using transactional deployments, so I am using dnrDeploymentJob. I would like to easily include the name of the deployment in the email, and I was hoping that OpenDeploy might keep the deployment name or somekind of ID for the deployment in a variable that I could pull into the script.

If there isn't a variable, does anybody have any suggestions on how I can pull it from the odbase log? I don't think there is anything in the manifest that i could pull out using IWXML::GetLogDataFromSTDIN() that would provide the actual deployment name. I have only found arrays for success, fail and deleted files.

Any suggestions would be greatly appreciated.

Thank you,
Carey

Find more posts tagged with

Comments

Adam Stoller

I found a thread from 2004 (http://devnet.interwoven.com/forums_vb/showthread.php?t=9511) that said there weren't any OpenDeploy variables that could be passed to a dnr script. I was wondering if that had changed with any of the later releases of OD.

I have a dnr (perl) script that sends an email to me if a deployment fails. We are using transactional deployments, so I am using dnrDeploymentJob. I would like to easily include the name of the deployment in the email, and I was hoping that OpenDeploy might keep the deployment name or somekind of ID for the deployment in a variable that I could pull into the script.

If there isn't a variable, does anybody have any suggestions on how I can pull it from the odbase log? I don't think there is anything in the manifest that i could pull out using IWXML::GetLogDataFromSTDIN() that would provide the actual deployment name. I have only found arrays for success, fail and deleted files.

Any suggestions would be greatly appreciated.

Thank you,
Carey

You could try having your DNR script dump the complete in-memory log data to a temporary file and look through it to see if you can find the information you want. If you do - then you just have to write your own parsing routines to extract that information from the in-memory log within your DNR script (i.e. IWXML.pm doesn't provide a routine for it, so you have to do it yourself).

Alternatively - you could pass the information on the command line of your DNR script - and just need to make sure that you pass the actual name of the deployment when you do so.

carey

You could try having your DNR script dump the complete in-memory log data to a temporary file and look through it to see if you can find the information you want. If you do - then you just have to write your own parsing routines to extract that information from the in-memory log within your DNR script (i.e. IWXML.pm doesn't provide a routine for it, so you have to do it yourself).

Unfortunately, I haven't found anything in the manifest files that contain the deployment name, and if I remember correctly the manifest data is all that is found in the in-memory log data. Isn't that correct?

Alternatively - you could pass the information on the command line of your DNR script - and just need to make sure that you pass the actual name of the deployment when you do so.

Good Point. My concern was needing a separate script for each deployment. I didn't think about passing it "manually" to the script.

Thanks for the suggestion.

sampledb_eventtest.rptdesign

Adam Stoller

Unfortunately, I haven't found anything in the manifest files that contain the deployment name, and if I remember correctly the manifest data is all that is found in the in-memory log data. Isn't that correct?

I believe it depends on how the server is configured:

<!ATTLIST dnrProperties 
      allowDnrExecution            (yes|no)        "yes" 
      infoStreamFormat             (log|manifest)  "log" 
      >

The above snippet (from the manual / DTD - would seem to indicate that the default is to use "log" format as opposed to "manifest" format - and therefore I believe there might be additional information -- again, if you dump it out you can see what's there ... though if passing it as a parameter works for you ...

John742

What type of DNR script are you using? Does not simpily adding a OD param as a CMD argument for the DNR script not work, since you should already know the name of the OD deployment prior to it being executed? I know I have done this in the past.

carey

....Does not simpily adding a OD param as a CMD argument for the DNR script not work, since you should already know the name of the OD deployment prior to it being executed? I know I have done this in the past.

Yes. Ghoti suggested that and I acknowledge it. I have setup my scripts to do that and I'm good-to-go.
Thanks.

Now I have another issue concerning executing scripts on the target FROM the source, but I'm going to search the forum before I start a thread about it.