callback from a cgi task problem

I've a cgi task which takes some form data and then transitions the task. This is done in exactly the same way as I normally use for external tasks. The code works fine on a dev box but on a production box the code fails to transition the task.

Does any one know of any config issues when using the wftask callback function from a cgi script?

The script executes without error. the complete cgi is executed in its entirety. I've also place debug prints around the callbacks and the print before and after take place fine. No transition however.

I've printed the return values of the callbacks ie
($suc , $stufftask) = $task->CallBack(0, "Published");

$suc is empty (I'm expecting a 1)

I've printed out the task error object.
again the error object is empty.

What is happening ????

And here is the killer. if i run the callback code in a script from the command line (transitioning to 0 or 1 does not matter) the callback works fine. (I've even tries calling the .ipl script from the cgi task but to no avail the callback fails if it is the cgi running it)

For background we are running teamsite 5.5.2 on sun solaris. no service pack. the dev box is the same.

The script security is 775 (although I'm unsure what user runs the cgi script, can't need write surely ???)

My code is identical to:

#!/iw/iw-home/iw-perl/bin/iwperl

use CGI;

use TeamSite::WFtask;
use TeamSite::WFworkflow;

$page = new CGI; #Create CGI instance called page

$| = 1; # AutoFlush the buffer

#Set workflow stuff up

my $taskid = $page->param('task_id') ;
my $task = new TeamSite::WFtask($taskid);
my $wf_id = $task->GetWorkflowId();
my $workflow = new TeamSite::WFworkflow($wf_id);
my $area_vpath = $task->GetArea();
if (! $task->IsValid())
{
print " Task ID missing or invalid task! ";
}

if ($page->param('submited') eq "")
{

# some html ...form etc
}
else
{
# a query was submitted

if ($page->param('publish') eq "Reject")
{
#
#transition task

$task->CallBack(1, "Rejected");

# tried using the clt but same result
#system("/iw/iw-home/bin/iwcallback $taskid 1");

# print message

print " ";
print "Publication has been rejected and sent back to the
approver";
print " ";
print " ";
}
else
{
# set workflow variables pub_date, pub_time
$workflow->SetVariable("pub_date_var", $pub_date);
$workflow->SetVariable("pub_time_var", $pub_time);

$task->CallBack(0, "Published");

# print message

print " ";
print "Publication date and time Set";
print " ";
print " ";

}

}

print $page->endform;

print $page->end_html;

# end of morph_search_meta.cgi

Edited by Lee on 01/16/03 11:29 PM (server time).

Find more posts tagged with

Comments

Migrateduser

You say your dev system and production system are both running TeamSite 5.5.2 on Solaris, no service pack, but that the script works on one and not on the other. Are you running the same CGI script and the same WFT? It seems like there must be some difference. TeamSite is not clever enough to tell the difference between a production machine and a dev machine. Smiley Happy

I would run the CGI task and then look at both iwevents.log (to see if the transition event was reported) and at iw-webd/logs/errors.log to see if any errors were reported while executing your script.

Brinko Kobrin
Interwoven Staff Engineer

Lee

I've calmed down enough to reply now. I'd been on this problem a while and was feeling a little punchy......

Yes brinko I am running the same wft and cgi script on dev and production (why would i be going round the bend trying to work out why dev and production where behaving differently if i was running different scripts ??). yes the dev box and prod box are running the same ts version. (and if you are going to use those silly faces built from charachters put the nose in

The problem appears to be the user UI. The webserver it appears runs as UI when executing cgi scripts. On the dev box UI had permission to write comments to the task but on production for as yet still not understood reasons UI could not.
(a log under the directory where iwevents.log lives finally give up its secrets). we changed the way the wft called the cgi script to make use of the cgi wrapper (as far as i understand this allows the webserver to impersonate the task owner) and everything worked. (27 broken workflows mind you and some very angry users).

Can anyone explain how UI is meant to run the cgi, why the difference, why did the task object not report an error why the callback sucess variable did not show a failure, why the log of the problem did not appear in trace.log or error.log

thanks lee C

ps brinko sorry if I sound terse its just that i've live a season with this one

Adam Stoller

Can you verify that the "iwui" user exists in the IWHOME/conf/roles/master.uid file on both your TeamSite servers - and that the user exists as far as both servers are concerned (could be a NIS/YP/LDAP kind of thing where one system knows about the user and the other doesn't)?

From all accounts of what you said - there has to be *some* difference between the configurations of the two machines ... or ... some hard-coded value that works on one and not the other.

Things like this are often difficult (if not impossible) to resolve remotely because the answers usually are burried in the actual implementation and you have to be able to poke around a bit in order to find it.

I'm glad the iw_cgi_wrapper is working, but you might want to work with Interwoven Support to see if they can help you determine why (a) it wasn't needed on your dev server, or (b) why it is needed on your production server.

--fish
(Interwoven Senior Technical Consultant)