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

OD Questions- Pl help

Jenni

Hi All,

Thanks in advance. Here are few questions reg. OD. Please try to help me by answering them.

1. I am trying to deploy 3 files (A,B,C)to folders F1,F2,F3. Is there a way, I could get the information that each file has been deployed to the target without using the "system generated log files" ? My aim is to write a log on the status for each file once it is attempted to be deployed to the target. Is that possible or not.

2. Can we invoke script A before deployment and (script B and script C) after deployment?

Thanks!
Jenni

Find more posts tagged with

Comments

janhavi

Yes you can do that , this can be done by putting the scripts inside dnrDeployment tag. You can also use dnrFile, dnrDir etc depending upon the requirement.

For more information go through OD pdf.

Regards,
Janvi
Teamsite 6.1

Jenni

Thanks for the reply. Can any one help me out with question 1?

Thanks!
Jenni

nipper

First, how is your deployment kicked off ? If it is in the WF, you can also run scripts in the WF before you run the deployment. DNR is not the only choice you have.

That being said, DNR has a number of options of when and where the scripts are executed, the can certainly be run before or after the files are transferred. Yes you can also have more than 1 DNR script.

I am on a project that has a deployment, runs a DNR to build a bunch of metadata files, which excutes a 2nd deployment, which runs a DNS ro email success, then finally the 1st deployment completes and yet another DNR for email

Jenni

Thanks for reply. Could you please comment on question 1?

Thanks!
Jenni

nipper

A DNR that sends out an email listing the files that have successfully been deployed ?

janhavi

Thanks for reply. Could you please comment on question 1?

Thanks!
Jenni

Yes Jeeni , for your first question also you can use dnrDeployment provided you are using OD scripts to deploy your content.
dnrDeployment will act as a trigger,
eg -dnrDeploymentJob location="source" when="after" state="success">
script .../>
/dnrDeploymentJob>

In script you can write a code which sends mail to a particular emailid giving confirmation of the deployment etc

Regards,
Janvi

Jenni

Hi,

Here my issue is not sending email. If I am deploying 20 files and in that 11 files are deployed and 9 are not deployed. How can I know the list of success and failed files list to write in my own log file(without using auto generated logs).

Thanks!
Jenni

ISCBorisB

Hi,

Here my issue is not sending email. If I am deploying 20 files and in that 11 files are deployed and 9 are not deployed. How can I know the list of success and failed files list to write in my own log file(without using auto generated logs).

Thanks!
Jenni

To achieve that you'd have to parse OD Deployment log within your DNR code. Fortunately, IWOV provides Perl library to
do just that, IWXML.pm. Run perldoc on it, you'll see IWXML::GetSucceededFiles, IWXML::GetFailedFiles methods and the like.

[thread=20429]This[/thread] thread (along with few more) contains usage discussion and few code samples. Please note that
your 20 = 11 + 9 Scenario is considered a successful Deployment by OD - just a consideration for DNR triggering. If your
requirements call for "All or none" deployment you should configure a transactional one.

Jenni

Hi,

Thanks for the reply.

What do you mean by 'All or none'? My understanding is if there is any failure none of the files will be deployed. So that means either 20 files will be deployed or none. Is there any tag to use for making sure all 20 files are deployed to the server(single server with different directories) or fails if any single file fails to deploy(we should know the reason also)?

Thanks!
Jenni

ISCBorisB

Hi,

Thanks for the reply.

What do you mean by 'All or none'? My understanding is if there is any failure none of the files will be deployed. So that means either 20 files will be deployed or none. Is there any tag to use for making sure all 20 files are deployed to the server(single server with different directories) or fails if any single file fails to deploy(we should know the reason also)?

Thanks!
Jenni

Yes, there is. <deployment transactional="yes">

Default is "no" and 11+9 is a perfectly good deployment - for all OD cares. If that's the case, return code is set to 9 - completed with errors.
Obviously transactional deployment can never terminate with RC 9.

Jenni

Yes, there is. <deployment transactional="yes">

so are you saying that we could use transactional='yes' even for single server?

OD Admin 6.0.2 143 page
Transactional deployments are particularly useful where a number of recipient targets must have their Web sites synchronized with each other.

- Here we have only one recipient target.

-Jenni

ISCBorisB

so are you saying that we could use transactional='yes' even for single server?

OD Admin 6.0.2 143 page
Transactional deployments are particularly useful where a number of recipient targets must have their Web sites synchronized with each other.

- Here we have only one recipient target.

-Jenni

Please refer to the manual. Transactional status has nothing whatever to do to the number of servers involved, it can be base-base deployment just as well.

It is "particularly useful" when you have to maintain Deployment integrity. Just like any other transaction, OD Transaction means "All or none".
Transactional operation is either completed 100% and transaction is commited or transaction is aborted and system is rolled-back to it's
pre-transaction state like it never happened

Adam Stoller

so are you saying that we could use transactional='yes' even for single server?

OD Admin 6.0.2 143 page
Transactional deployments are particularly useful where a number of recipient targets must have their Web sites synchronized with each other.

- Here we have only one recipient target.

-Jenni

Yes - transactional is regarding the manner in which the entire deployment is processed - not the number of recipients that are targeted.

Got it?

jude_asanka

If you want files and folder information after deployment, you can get them from .mf files. That is also another XML file, then you can use a simple XML parser to filter the information you need.

If you need them before deployment. Then using similation mode. Then get the .mf file. Thereafter run in normal mode.

Jenni

Hi All,

Thanks soo much for the replies. I got a lot of information from all of you. The IWXML.pm module is good for getting successfull files list. How can I test the failed conditon while deploying(the output should parsed by IWXML)?

I tried to run my OD script by giving 1. incorrect node name 2. deleting folder on target machine 3. Specifying a non existing file(on source) in the file list. I could not able to get the failed condition. Please help me to get the failed condtion...

Thanks!
Jenni

ISCBorisB

Hi All,

Thanks soo much for the replies. I got a lot of information from all of you. The IWXML.pm module is good for getting successfull files list. How can I test the failed conditon while deploying(the output should parsed by IWXML)?

I tried to run my OD script by giving 1. incorrect node name 2. deleting folder on target machine 3. Specifying a non existing file(on source) in the file list. I could not able to get the failed condition. Please help me to get the failed condtion...

Thanks!
Jenni

Try to deploy to the existing directory that is NOT listed in the <allowedDirectories> Set

Jenni

Hi Boris,

Thanks for the reply. Yes I was able to achieve the failed condition for the entire directory/all files.

1. How can do the same for single file(For ex, single file failed in 10 files)?

2. The following script is not giving me the list of failed files. Could you tell me where I am going wrong.

Note: the same code gives the list of success files without any issue.

Thanks!
Jenni

[html]
#! C:/PROGRA~1/INTERW~1/TeamSite/iw-perl/bin/perl

use Config;

use lib "D:/iw-home/opendeploy/OpenDeployNG/solutions/perl";
use IWXML;

open(FILE, ">D:/iw-home/tmp/ama.log");

my($xml) = IWXML::GetLogDataFromSTDIN();

print FILE "XML: $xml\n";
my %hash = %{$xml};
my @keys = keys%hash;

my(@f_success) = $xml->GetSucceededFiles();
print FILE "f_success: @f_success\n";

my(@f_deleted) = $xml->GetSucceededDeletedFiles();
print FILE "f_deleted: @f_deleted\n";

my(@f_failed) = $xml->GetFailedFiles();
print FILE "f_deleted: @f_failed\n";

close FILE;[/html]

ISCBorisB

Have you run it on Target? If so, try on Source, see if lists differ - they may

Jenni

We are running the script on the source. It worked for success....don't know why it is not working for the failed condition?

I had edited the previous post for additional question (single file failure).

Thanks!
Jenni

ISCBorisB

We are running the script on the source. It worked for success....don't know why it is not working for the failed condition?

I had edited the previous post for additional question (single file failure).

Thanks!
Jenni

Code proper seems to be Ok.

Play with it using base-base Deployment (this way you do not have to bother with Target's Perl, Target Log access, etc...)
Check Source and Target OD Logs, run your script "on Source" and "on Target" both and compare results.
To have a Success/Failure Mix you can for example configure List Deployment with some entries having *not allowed* Path

Jenni

Code proper seems to be Ok.

Play with it using base-base Deployment (this way you do not have to bother with Target's Perl, Target Log access, etc...)
Check Source and Target OD Logs, run your script "on Source" and "on Target" both and compare results.
To have a Success/Failure Mix you can for example configure List Deployment with some entries having *not allowed* Path

Hi Boris,

1. Tried the check the output by running at the source and the target. Still the same issue. No information of the failed files.

2. I tried to mix up the the deployment of files as those in the allowed directories and non allowed directories. None of the files are making to the target. Here are the transactional directive values and their corresponding output.

a. transactional =yes --- Output -- Failed
b. transactional =no --- Output -- Completed with errors (but none of the files making to the target)

Thanks!
Jenni

Jenni

Hi All,

Any one, able to get the list of failed files for the deployment using GetFailedFiles() function?

Thanks,
Jenni

Adam Stoller

Hi All,

Any one, able to get the list of failed files for the deployment using GetFailedFiles() function?

Thanks,
Jenni

It used to work - the last time I had to deal with it. What you might do to debug the issue is write a simple DNR script that simply reads in STDIN and dumps the contents to a file - and then examine the output to see if failures are shown (of course you'd have to perform a deployment where some files fail to get deployed)

Note - a filelist deployment in which the filelist specifies non-existant files will not be a failure - the non-existant files are assumed to be deletion requests which may or may not get processed as such depending on the setting of doDeletes. You would have to probably create a multiple definition deployment in which one definition is targeted for an allowed directory, and the other is targeted for a non-allowed directory - and make sure that the deployment is non-transactional.