Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Opendeploy 551 problem
GodBlessMe
Hi. I am running the following Od command from within a workflow external task. The following code is in an ipl that is called from the external task. I am using od551.
my $odcmd = "/app/teamsite/OpenDeployNG/bin/iwodstart wfDeployment -inst $$ -k filelist=$filelist -k area=$area -k targetArea='/content/$destination' -k useNode='appserver'";
chop($odResult = `$odcmd`);
print LOG "OD :$odResult\n";
my $error = $@ ;
## Incorporate logging statements here in case Opendeploy fails..
if ($odResult =~ /Status: Completed/)
{
$task->CallBack(0, "Deployed files to Preview App Server");
}
else
{
$task->CallBack(1, "OpenDeploy Failed");
print LOG "Error Occured while deploying files to AppServer: $error\n";
}
The problem i am facing is the external task is not executing the command at all... I've put some logging statements to see if it is going inside the ipl.....Its executing the ipl but not running the od command... I've tried executing the same command from telnet command prompt. it is working fine and deploying the content.
The weird part is its not creating the od log file when i execute this command from wf.
Any help in this regard is highly appreciated...
I am on a Solaris box/TS552.
Thanks.
Find more posts tagged with
Comments
GodBlessMe
Anyone please?
The error code the ipl returning is 35584..
Thanks
Adam Stoller
You're printing out the 'result' of running the
$odcmd
- but you're not actually printing out the value of $odcmd to the logfile - best to do that too so you can verify that the command you are running looks like what you think it does.
Also - you want to set the value of
$error
to
$?
not
$@
and then use
$error
as your conditional. If you're going to run a regex on
$odResult
, I think you'd need to include the
s
modifier after the closing
/
of the regex to treat the entire contents as a single line.
Not sure if the above will resolve your problem, but perhaps it will start you in the right direction...
--fish
(Interwoven Senior Technical Consultant)
PageOUTImageDynamic.dur.zip
GodBlessMe
The command runs perfectly fine from the telnet prompt. But when i run it as an external task from a workflow it is not doing anything. I guess there is an issue with Solaris JRE Patches..
Any help in this regard is highly appreciated.
rwinterpacht
A few dumb questions:
1. Are all the scripts executable (+x)?
2. If so, who owns the scripts?
3. To be clear, you have an externaltask, which points to an ipl file. That ipl file then calls another script to call OD?
4. Have you tried this:
a. Turn debugging on in your workflow
b. See the external task that is passed to the wf engine.
c. Copy/paste the ext task from the debug browser window right into a console and execute it. (Don't forget to take care of the addn'l arguments: jobid, taskid, vpath, files, and comment out the callback in the ext task)
d. Do you set a task var and call the callback method in the externaltask?
Any chance you can attach the wft and all related scripts?
Thanks,
Raf Winterpacht
GodBlessMe
1. Are all the scripts executable (+x)?
I' ve done chmod 777 on all my scritps.
2. If so, who owns the scripts?
I own the scripts.
3. To be clear, you have an externaltask, which points to an ipl file. That ipl file then calls another script to call OD?
Yes. The ipl calls odhome/bin/iwodstart with parameters.
4. Have you tried this:
a. Turn debugging on in your workflow
b. See the external task that is passed to the wf engine.
c. Copy/paste the ext task from the debug browser window right into a console and execute it. (Don't forget to take care of the addn'l arguments: jobid, taskid, vpath, files, and comment out the callback in the ext task)
d. Do you set a task var and call the callback method in the externaltask?
The problem is the iwodstart command is not getting executed due to some JRE patch version mismatches. I think after we apply the necessary patches the problem should be solved.
Thanks
rwinterpacht
That doesn't make alot of sense if it still works from the telnet prompt. It's puzzling. I'd still be interested in seeing the wft file and relevant ipl scripts.
Thanks,
Raf Winterpacht
rwinterpacht
Another quick note, if you suspect that it's JRE, spit out all the ENV variables when it's run from the workflow, and compare them to the ENV variables when you run it via command prompt. Could there be conflicts?
Thanks,
Raf Winterpacht
GodBlessMe
OD 551 requires that JRE 131 should be on the Base. When I installed JRE131 and pointed to it, OD is working just fine from the workflow.....
Thanks
Migrateduser
Fyi, you shouldn't need to install a JRE for use with OD, since it comes bundled in the OpenDeployNG/jre directory.
Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e:
tscallan@interwoven.com
Migrateduser
You might want to upgrade to OD5.5.2 SP1, there is a known issue with OD5.5.1 script. The iwodstart script come with OD 5.5.1 just simply doesn't work. My workaround is to write a perl script to invoke the opendeploy java api directly.
Adam Stoller
You might want to upgrade to OD5.5.2 SP1,
That should be 5.5.1 and I believe the current SP for it is SP3. Better would be to upgrade to OpenDeploy 5.6 SP1.
My workaround is to write a perl script to invoke the opendeploy java api directly.
Are you talking about problems with iwodstart on Unix?
On Windows - yes, there are some problems running the iwodstart.bat from within a workflow script - but Is there some reason (other than not knowing about it) that you didn't use
IWODHOME
/solutions/perl/iwodstart.ipl
? It was created primarily because the iwodstart.bat didn't return proper exit values on Windows NT (it actually worked on Windows 2000 from the command line at least).
--fish
(Interwoven Senior Technical Consultant)