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

deployNRun - running script on target not working

deja

I'm running a Windows2000-to-Windows2000 deployment using OpenDeploy 5.5.1. The actual deployment is running perfectly, but I'm struggling to execute a post-deploy script on my target (which happens to be my laptop). The logs tell me that the script worked OK, but when I check I can see that this is not really the case.

To illustrate, here is the <deployment> node of my Deployment Configuration XML:

<deployment transactional="yes">
<execDeploymentTask useDefinition="owners_wls_deploy">
<deployNRun>
<dnrDeployment location="target" when="after" state="success">
<script cmd="command_line_redeploy.cmd" async="no" where="B:\user_projects\domains\TestDomain\stage" />
</dnrDeployment>
</deployNRun>
</execDeploymentTask>
<execDeploymentTask useDefinition="owners_static_deploy" />
</deployment>

The purpose of this is to run a Weblogic-specific command to activate my newly-pushed JSP files on a cluster of servers. The command_line_redeploy.cmd batch script, which sits in B:\user_projects\domains\TestDomain\stage\ on my laptop, works like a champ when I run it locally from the command prompt. I get the exact behavior that I expect. However, when I run it as part of my deployment, using the snippet above, nothing happens. The log file on my receiver/laptop tells me that all is well, however:

(2) id=0 server: Executed script [command_line_redeploy.cmd] where [B:/user_projects/domains/TestDomain/stage] as [] succeeded

In order to debug this a little further, I decided to pipe the output from my .cmd script to a simple text file, which in theory should let me know what OpenDeploy is up to. I changed the <deployment> node of my Deployment Configuration XML to be more like:

<script cmd="command_line_redeploy.cmd >> c:\temp\odlog.txt" async="no" where="B:\user_projects\domains\TestDomain\stage" />

When I run the script, as expected, I get the output in c:\temp\odlog.txt on my laptop - this proves that the script is there and accessible. However, instead of a list of Weblogic Deployer output, odlog.txt contains a single line representing the directory in which to run the script, and the content of the command_line_redeploy.cmd script itself:

B:\user_projects\domains\TestDomain\stage>java weblogic.Deployer -adminurl t3://localhost:9999 -username test -password testtest -name test_ear -targets testwebapp@TestAppCluster -verbose -redeploy testwebapp\index.jsp

So, basically, OpenDeploy is finding the script, is reading the contents of the file, but does not seem to execute those contents.

Hopefully this is clear enough. This is my first experience with OpenDeploy, but I've pored over the documentation and had a fresh set of eyes look at my script and I have no idea why it would not work (or, more accurately, only kinda work). I've got a follow-on question, but really need this to work before I can move on.

Any help is greatly appreciated! Thanks.

Find more posts tagged with

Comments

jbonifaci

What happens if you just use:

<script cmd="B:\user_projects\domains\TestDomain\stage\command_line_redeploy.cmd" async="no" />

~Jeff

test_visibility.rptdesign

deja

Unfortunately, the results are pretty much the same - no execution of the script, and the log file shows a slightly different output (indicating that the script is being 'executed' in c:\, not the specific directory in which it lives):

C:\>java weblogic.Deployer -adminurl t3://localhost:9999 -username test -password testtest -name test_ear -targets testwebapp@TestAppCluster -verbose -redeploy testwebapp\index.jsp

Interestingly, I just tried to add a couple of more lines to the .cmd script file, and these seem to execute fine. Admittedly, they're just ECHO commands, but they seem to indicate that maybe the problem is specific to executing Java commands:

C:\>echo testing 1
testing 1

C:\>java weblogic.Deployer -adminurl t3://localhost:9999 -username test -password testtest -name test_ear -targets testwebapp@TestAppCluster -verbose -redeploy testwebapp\index.jsp

C:\>echo testing 2
testing 2

I've verified that both my system PATH & CLASSPATH variables are setup correctly to run Java and this specific script by just opening a new command prompt and running the .cmd script directly. It seems really weird to me, also, that if the invocation of Java was failing then there would be no message to indicate this...

Thanks for the speedy reply, Jeff.

jbonifaci

Well, the script could be failing and OD will see this as a success. If the script returns anything other than:
<response code="-2"/>\nOD assumes it ran successfully. I would add some additional logging into your script to see if it is actually running and what is going on.

~Jeff

deja

Ah, that is a good distinction - thank you. I didn't realize that -2 would not be returned if the script did not run 100%, but it makes sense.

In testing a little further, it turns out that just running "java" from within my file works, and it seems to have a specific problem with the weblogic.Deployer command. Keeping that in mind, I guess that this forum doesn't seem to be the most logical place to continue this discussion - it seems to be a problem with invoking a Weblogic tool (maybe the user's CLASSPATH is taking precendence, or maybe I need to logoff and back on again to have my new CLASSPATH kick-in: stranger things have happened with Windows).

The real point of my script was to have Weblogic put the newly-deployed file(s) out onto the cluster as soon as they are copied. I would like to do something like this, but can't tell from the documentation of a simple way for OpenDeploy to identify each filename:

<dnrFile location="target" when="after" state="success" mask="\.jsp$">
<script cmd="command_line_redeploy.cmd -filename my/test/page.jsp" where="B:\user_projects\domains\TestDomain\stage\" async="yes" />
</dnrFile>

I'd love to know of a simple way to just substitute my/test/page.jsp above with the path/name of the file that has just been deployed - it seems like the information should be available somehow, but I can't see any way to get at it. It looks like post-processing the XML log that is generated to std out is a commonly-used approach, but that would be a hugely round-about way for me to do something relatively simple.

Thanks again.

reddyl

Use the OpenDeploy parameter substitution to get the deployed jsp filenames

OpenDeploy Configuration:
<script cmd="command_line_redeploy.cmd -filename ^jsp_file$" where="B:\user_projects\domains\TestDomain\stage\" async="yes" />

Need to run OpenDeploy command using:
iwodcmd start od_deployment.xml -k jsp_file="my/test/page.jsp"

deja

Sorry, I should have been more clear in my description of the problem. In order to use parameter substitution, I'd need to know which files were going to be deployed before I even invoked OpenDeploy - I was hoping that there was some way to have OpenDeploy identify the JSP files that it had just deployed so that I could feed them (one-at-a-time, or all-at-once) into my script.

For example, if I do an incremental deploy and it turns out that 7 JSPs have changed & are deployed, I'd need to be able to trap the names of those 7 files so that I could feed them into my script. It's a commonly used feature in Weblogic production environments to identify individual files that need to be redeployed, but I was wondering if OpenDeploy has a way to prepare the list.

reddyl

How are you invoking your deployments thought workflow's or a scheduled deployment that uses directory comparison of TeamSite areas.

deja

Currently, it's just a test deployment script that I'm running from the command-line on the OpenDeploy server. The deployment script is doing a last-modified datestamp comparison between a TeamSite staging area and a particular directory on my laptop. It deploys any files that are missing on my laptop, or that have been modified recently in the TeamSite directory.

Ultimately, the script will be triggered by a TeamSite workflow... I'm curious, would this affect the possible solution?

reddyl

If the deployment is triggered by the workflow externaltask then I would add the logic to get all the modified files from and pass it as a parameter. If not then you have to parse the in-memory log file to get the list of files deployed and then invoke your weblogic command to update the files.

jbonifaci

Just out of curiousity, what exactly is your script doing? Is it just copying the files again? If so, why not just use OpenDeploy for this?

deja

That makes a lot of sense, reddyl - I can just use TeamSite Workflow to get the list of files, rather than having to rely on OpenDeploy. It's great to get a definitive answer about the in-memory logfile, too, as I wasn't sure if this was the only OpenDeploy-centric way to do it.

Much appreciated - this is my first post to the forum and I'm very impressed by the quick responses. Thanks, all...

deja

Good question, jbonifaci.

Without getting into too much detail, I'm using WebLogic as my JSP-container and have three servers that exist in a cluster which need to have identical copies of each JSP. The industry-standard & BEA-preferred method of changing JSPs in a production system is to run a Weblogic deploy task that will automatically distribute the JSPs from a predetermined, single centralized location to each of the servers in the cluster. The key word is production - in our internal, development environments we can hot-deploy files to our hearts' content. Unfortunately, in a production environment you can go directly to the JSP's final resting place, swap it out with a different version and still see the old version on our website.

So, to answer your question, even if I used OpenDeploy to spread updated JSPs out to each server, I would have to run a script after-the-fact on each server to redeploy the files. The kicker is that the script can:

a) redeploy the whole web application - which takes 40+ minutes to happen, making it pretty useless for my needs
b) 'instantly' redeploy each file, one-by-one, by name - which is the info I was hoping that OpenDeploy could supply to my script

I really like the TeamSite Workflow approach that was suggested here, though, and I think this is the one that I'll pursue now unless anybody can think of a different mechanism.

I'm also going to look at one more approach, which is to use an Ant script to figure out the list of JSPs in my app and then deploy them one-at-a-time... this wouldn't be as elegant as knowing exactly which files have changed, but it might be an acceptable solution in comparison to a 40-minute WebLogic redeployment.

Thanks all... I'll post back when I make some progress, in case anybody else would benefit from the information.

deja

Just to put a proper end to this thread, I figured out a way to use Ant to determine the complete list of JSPs on my site and to redeploy them all to Weblogic's cluster automatically. It works in 14 seconds instead of 40 minutes, so I think I can run with this approach.

Thanks again to everybody who piped in on the thread - this one will result in a huge efficiency for my group.