error with iwjobc

Why would you have *wft* called from iwjobc? You need to call a workflow specification file which will be an XML file. Workflow specification file is an actual instance of any workflow in action. It has the XML tags tht you have in wft file with their available values to the instantiator.
To see the structure of this XML file, run a workflow with Debug mode *ON* and that will create an XML file for you on your server.

Hope this helps!

Akshat Pramod Sharma
Interwoven Inc.

Thanks , i got it , but how can I give Vpath dynamically.

Nagaraj Samisetty

What exactly are you trying to accomplish?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

So, why do you require a vpath here? Please refer to the Command Line Tools guide for detials on iwjobc CLT. It has few examples also about its usage.

Thanks.

Akshat Pramod Sharma
Interwoven Inc.

How can I give areavpath. areavpath is not static , it has to take dynamically.
ex.
<usertask name="update" owner="nagaraj"
description="updates the files integration"
start="t">
<areavpath v="/default/main/Nationwide/Test/Project2/WORKAREA/workarea1"/>
<successors>
<successorset description="push files for approve">
<succ v="Submit"/>
</successorset>
</successors>
</usertask>

I want to give this one dynamically
<areavpath v="/default/main/Nationwide/Test/Project2/WORKAREA/workarea1"/>

Nagaraj Samisetty

Edited by snrguptha on 10/17/02 03:39 PM (server time).

If you want to use iwjobc rather than execute a wft through the GUI, you have to wrap a script around it and then you can make it dynamic. You have to build the XML job spec, or use some sort of template for it and substitute your workarea to produce a static XML file, then run iwjobc on it.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Edited by Smitty77 on 10/17/02 03:46 PM (server time).

mogoo

I think you could get the workarea with the following?...
<areavpath v="__TAG__(iw_workarea);"/>

If you are this unfamiliar with how to create workflows, you might consider going through the tutorial. Look in the Workflow Developer's Guide for instructions on the Tutorial.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

If you get a workflow specification file, then it already has the value of workarea and other variables as per the kick off of a workflow.

I am assuming you are confusing a WFT file to be a Workflow Specification file. Actually, a specification file is nothing but an instance of a running workflow.

To explain in more details, a wft file is a workflow template for all the tasks that you need a workflow to perform. In this file you can specify all varibales and also have it set for user input output. Once a workflow is instantiated, it refers to a instance of a wft file. Now this instance has the actual values derieved from TeamSite GUI as per the environment of the user instantiating it.

iwjobc CLT needs this instance file. *NOT* the wft file.

As I suggested earlier, you could see the structure of this specfiication/instance file if you run any Workflow in a DEBUG mode.

I strongly recommend that as per Dave's suggestion, you please indicate what actually are you trying to accomplish. Since you asked a very specific question about iwjobc, I assumed you would already know the basic architecture of the Workflow system. But now I have a feeling that you are confusing between a wft file and and xml(the specification file) file.

Thanks!

Akshat Pramod Sharma
Interwoven Inc.

I got it, that means we can't start a workflow from Command Line. so we have to start intially workflow from GUI to get specification file , am I right.

Nagaraj Samisetty

Edited by snrguptha on 10/17/02 04:10 PM (server time).

Not really. If you have that instance file already created (which you could create manually as an xml file i fyou know the structure of that file), then you can use iwjobc anytime.

Also, I was suggesting to run a workflow in debug mode to just have a look at the instance file it creates so that you know for your refrence how the structure looks like.

Hope that helps!

Akshat Pramod Sharma
Interwoven Inc.

This is my workflow XML. I have to change areavpath. In my workflow areavpath is going to change oftenly. So how can I change areavpath dynamicall through CLT.

<?xml version="1.0" standalone="no"?>
<!DOCTYPE workflow SYSTEM "../iwwf.dtd">


<workflow name="nagaraj_workflow"
owner="__TAG__('iw_user');"
creator="__TAG__('iw_user');"
description="__TAG__('iw_desc');">

<template_script><![CDATA[
# Import routines from library
use TeamSite::Usertask qw(
cleanup_paths
get_names_from_file
get_mail_cmd
make_branchpathlist
);

sub set_area{
my($btag, $watag) = @_;
my($avpath, $bpath, $wapath, $skip);
my($iwbpath, $iwwapath) = (__VALUE__("iw_branch"),
__VALUE__("iw_workarea"));
if ((length($iwbpath)) > 0 && (length($iwwapath)) > 0){
$bpath = $iwbpath;
($wapath = $iwwapath) =~ s|^\s*/.* Smiley Indifferent

|;
$wapath =~ s|/\s*$||;
return("$wapath", "$iwbpath", "$wapath", "TRUE");
}
($bpath, $wapath, $avpath) = cleanup_paths(__VALUE__("$btag"),
__VALUE__("$watag"));
return("$avpath", "$bpath", "$wapath", "FALSE");
}

my($area_vpath, $branch_path, $work_area, $skip_branch) =
set_area("branch_path", "work_area");

#======================================================================
# JOB FORM DATA CAPTURE
#---------------------------------------------------------------------
# This section capture the necessary data on the job creation form in
# order to dynamically assemble a workflow.
#======================================================================
sub debug{
TAG_info(
iw_output_file => "<input type='text' value='C:\\foo.xml'>",
iw_debug_mode =>
"<input type='radio' value='true'>True</input>" .
"<input type='radio' value='false'>False</input>",
);
}
#======================================================================
# Uncomment following line if you wish to enable workflow debugging.
#======================================================================
&debug;

#======================================================================
# Set some variables for later use
#======================================================================
use TeamSite::Config;
my $iwhome = TeamSite::Config::iwgethome();
my $iwmount = TeamSite::Config::iwgetmount();
my @submit_file = ();
if (__ELEM__('iw_file')){
@submit_file = map {
TeamSite::CGI_lite::escape_html_data($_);
} sort map {
s|\\|/|g;
s/^\Q$area_path\E//;
$_;
} __VALUE__('iw_file');
}

if ($skip_branch eq "FALSE"){
my($branch_menu) = make_branchpathlist("$iwhome");
TAG_info(
branch_path =>
[ html => "$branch_menu",
label => 'Select Branch',
is_required => 'true',
],

work_area =>
[ html => "<input type='text'></input>",
label => 'Enter Workarea',
valid_input => 'wa_validator($_, 0)',
error_msg => q{'wa_validator($_, 1)'},
is_required => 'true',
],
);

sub wa_validator{
my($wa, $error) = @_;
my($branch) = __VALUE__('branch_path');
my($avpath);
(undef, undef, $avpath) = cleanup_paths("$branch", "$wa");
if (! -d "$iwmount$avpath"){
return(0) if (!$error);
return("Invalid path: '$iwmount$avpath'");
}
return(1);
}
}

#=====================================================================
# Create XML Job Specification
#=====================================================================
]]></template_script>



<usertask name="update" owner="nagaraj"
description="updates the files integration"
start="t">
<areavpath v="__TAG__('iw_workarea');"/>
<successors>
<successorset description="push files for approve">
<succ v="Submit"/>
</successorset>
</successors>
</usertask>
<externaltask name="Submit"
owner="nagaraj"
description="Submit the WorkArea to the Staging"
start="f">

__INSERT__("<areavpath v='$area_vpath'/>");
<successors>
<successorset description="publishing Edition">
<succ v="Edition"/>
</successorset>
</successors>

<command v="c:/iw-home/iw-perl/bin/iwperl c:/iw-home/custom/bin/nw/submit.ipl" />
<activation>
<or>
<pred v="update" />
</or>
</activation>
</externaltask>
<externaltask name="Edition"
owner="nagaraj"
description="Publishing Edition"
start="f">
__INSERT__("<areavpath v='$area_vpath'/>");

<successors>
<successorset description="Upadating the Workarea in Test Branch">
<succ v="Test"/>
</successorset>
</successors>
<command v="c:/iw-home/iw-perl/bin/iwperl c:/iw-home/custom/bin/nw/Edition.ipl" />
<activation>
<or>
<pred v="Submit" />
</or>
</activation>
</externaltask>

<externaltask name="Test"
owner="nagaraj"
description="Updating workarea in Test"
start="f">
__INSERT__("<areavpath v='$area_vpath'/>");

<successors>
<successorset description="creating workarea in Intcurrent branch">
<succ v="IntCurrentwa"/>
</successorset>
</successors>
<command v="c:/iw-home/iw-perl/bin/iwperl c:/iw-home/custom/bin/nw/workarea.ipl" />
<activation>
<or>
<pred v="Edition" />
</or>
</activation>
</externaltask>

<externaltask name="IntCurrentwa"
owner="nagaraj"
description="Updating workarea in Test"
start="f">
__INSERT__("<areavpath v='$area_vpath'/>");

<successors>
<successorset description="Wating for Approval in Intcorrentstate">
<succ v="IntCurrentsub"/>
</successorset>
</successors>
<command v="c:/iw-home/iw-perl/bin/iwperl c:/iw-home/custom/bin/nw/workarea_intcurrent.ipl" />
<activation>
<or>
<pred v="Test" />
</or>
</activation>
</externaltask>

<externaltask name="IntCurrentsub"
owner="nagaraj"
description="Updating workarea in Test"
start="f">
__INSERT__("<areavpath v='$area_vpath'/>");

<successors>
<successorset description="Wating for Approval in Intcorrentstate">
<succ v="End"/>
</successorset>
</successors>
<command v="c:/iw-home/iw-perl/bin/iwperl c:/iw-home/custom/bin/nw/submit.ipl" />
<activation>
<or>
<pred v="IntCurrentwa" />
</or>
</activation>
</externaltask>

<endtask name='End'>
<activation>
<pred v='IntCurrentsub'/>
</activation>
</endtask>

</workflow>

Nagaraj Samisetty

Edited by snrguptha on 10/18/02 08:31 AM (server time).

If you start a workflow while a workarea is being displayed (for example, with Assign or Submit) then the areavpath for that workarea will be passed in. Look at any of the workflows in the iw-home/local/config/default directory and see how they get the areavpath form the GCI parameters. You've obviously copied much of your code from another workflow, but you somehow missed that part.

Brinko Kobrin
Interwoven Staff Engineer

sorry I pasted wrong one. this is one my specification file.
<?xml version="1.0" standalone="no"?>
<!DOCTYPE workflow SYSTEM "../iwwf.dtd">


<workflow name="nagaraj_workflow"
owner="bald\nagaraj"
creator="bald\nagaraj"
description="d">



<usertask name="update" owner="nagaraj"
description="updates the files integration"
start="t">
<areavpath v="/default/main/Nationwide/Test/Project1/WORKAREA/workarea1"/>
<successors>
<successorset description="push files for approve">
<succ v="Submit"/>
</successorset>
</successors>
</usertask>
<externaltask name="Submit"
owner="nagaraj"
description="Submit the WorkArea to the Staging"
start="f">

<areavpath v='/default/main/Nationwide/Test/Project1/WORKAREA/workarea1'/>
<successors>
<successorset description="publishing Edition">
<succ v="Edition"/>
</successorset>
</successors>

<command v="c:/iw-home/iw-perl/bin/iwperl c:/iw-home/custom/bin/nw/submit.ipl" />
<activation>
<or>
<pred v="update" />
</or>
</activation>
</externaltask>
<externaltask name="Edition"
owner="nagaraj"
description="Publishing Edition"
start="f">
<areavpath v='/default/main/Nationwide/Test/Project1/WORKAREA/workarea1'/>

<successors>
<successorset description="Upadating the Workarea in Test Branch">
<succ v="Test"/>
</successorset>
</successors>
<command v="c:/iw-home/iw-perl/bin/iwperl c:/iw-home/custom/bin/nw/Edition.ipl" />
<activation>
<or>
<pred v="Submit" />
</or>
</activation>
</externaltask>

<externaltask name="Test"
owner="nagaraj"
description="Updating workarea in Test"
start="f">
<areavpath v='/default/main/Nationwide/Test/Project1/WORKAREA/workarea1'/>

<successors>
<successorset description="creating workarea in Intcurrent branch">
<succ v="IntCurrentwa"/>
</successorset>
</successors>
<command v="c:/iw-home/iw-perl/bin/iwperl c:/iw-home/custom/bin/nw/workarea.ipl" />
<activation>
<or>
<pred v="Edition" />
</or>
</activation>
</externaltask>

<externaltask name="IntCurrentwa"
owner="nagaraj"
description="Updating workarea in Test"
start="f">
<areavpath v='/default/main/Nationwide/Test/Project1/WORKAREA/workarea1'/>

<successors>
<successorset description="Wating for Approval in Intcorrentstate">
<succ v="IntCurrentsub"/>
</successorset>
</successors>
<command v="c:/iw-home/iw-perl/bin/iwperl c:/iw-home/custom/bin/nw/workarea_intcurrent.ipl" />
<activation>
<or>
<pred v="Test" />
</or>
</activation>
</externaltask>

<externaltask name="IntCurrentsub"
owner="nagaraj"
description="Updating workarea in Test"
start="f">
<areavpath v='/default/main/Nationwide/Test/Project1/WORKAREA/workarea1'/>

<successors>
<successorset description="Wating for Approval in Intcorrentstate">
<succ v="End"/>
</successorset>
</successors>
<command v="c:/iw-home/iw-perl/bin/iwperl c:/iw-home/custom/bin/nw/submit.ipl" />
<activation>
<or>
<pred v="IntCurrentwa" />
</or>
</activation>
</externaltask>

<endtask name='End'>
<activation>
<pred v='IntCurrentsub'/>
</activation>
</endtask>

</workflow>

Nagaraj Samisetty

So....

What is the problem you are trying to solve???

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

james1

In TS4.x, you could use command-line parameter substitution with iwjobc. i.e., if you invoked:


iwjobc jobspecification.xml arg1 arg2 arg3

then you could use the strings "$1", "$2", and "$3" in your job specification, and they would be replaced with "arg1", "arg2", and "arg3", respectively.

This feature has been eliminated, I assume since you can do this and much much more with workflow templates. I don't know if the feature is still present in TS5.0, but it is not present in TS5.5.2.

-- James

--
James H Koh
Interwoven Engineering

The other one was better!

This one is not really a workflow template, it is a complete job spec. It does not have a dynamic component. Everytime it is run it will do exactly the same thing because all of the values are hard-coded.

If you don't understand the difference between a workflow template and a job spec, I suggest that you read the beginning of the Workflow Developer's Manual. It explains the basic concepts behind the Workflow system.

Brinko Kobrin
Interwoven Staff Engineer

jimE

In your workflow set areavpath="MYVARIABLE", then generate xml, run an external task which changes any occurance of MYVARIABLE to the dynamic areavpath,
then iwjobc.

Adam Stoller

I used to have need to do something like this (haven't in a while though) - and what I did is create what I called a "template workflow" - as opposed to a "workflow template" - in which I did things like:

<area_vpath v="__AREA__"/>

And then I had I had a simple perl script (iwjobcpp.ipl) that took as command line arguments:
1. the name of the template workflow to be processed
2. any number of "key=value" pairs

It then used a simple loop and substitution to swap out all the key/value pairs, wrote the result to a temporary file and then called iwjobc and iwinvokejob on the results.

It would now be a little easier since you could just call iwjobc -i (which takes care of the invoke part).

You can't use the my $foo = __AREA__ thing inside the template workflow because the resultant file has to be pure-XML - no-Perl.

I generated the template workflow by going through the steps already outlined in earlier responses - created a model workflow template for what I wanted, ran it once in debug mode to dump a job description file out, and then replaced the hard-coded values that I wanted to be able to change with unlikely-to-be-confused keys (e.g. __AREA__ rather than just AREA)
The script might be floating around on the support site somewhere - but if it isn't, it shouldn't be that difficult to re-construct.

(James: despite the usage for iwjobc in the old days, the substitutions didn't seem to work)

--fish
(Interwoven Senior Technical Consultant)

jimE

I am attempting to do iwjobc from my client machine, but get no server found

we are using 5.0.1 build 5463

my command line is:
iwjobc -s svkralabwork9 tempxml3.xml

any idea what I'm doing wrong?

Bug147071_pre60SP1_engr_fix.zip

james1

There are 5.0.x versions of iwjobc where the "-s" flag does not work on Windows. Are you on Windows?

Off the top of my head, I don't know what versions have it fixed. My guess: Probably 5.0.1 and 5.0.2 both have service packs that fix iwjobc. I believe that it is fixed in 5.5.0 and beyond.

-- James

--
James H Koh
Interwoven Engineering

Ottawa_IWOV

I am also getting the No Server Found error and we ar on TS 5.5.2. I need to get this working ASAP

Lucas Cochrane
lcochrane@dc.com