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)
iwjobc CLT
Sid1
Hi,
I am trying to kickstart a workflow using 'iwjobc' CLT, but encoutering some problems.
1) Am I using the correct CLT ?
2) Do you have some example or can tell me the syntax for using this command line ?
Thanks!
Find more posts tagged with
Comments
Sid1
Hi,
I am trying to use the iwjobc for a wft file, and get the following error when executed from command line :
\Program Files\Interwoven\TeamSite\local\config\wft\wfb>iwjobc -i CMS.wft
junk after document element at line 271
ERROR:00001: Failure in operation
Where line 271 is actually a blnak line after the following line :
270)<workflow name = "Scenario1" owner = "__INSERT__($sOwner);" creator = "__TAG__('iw_user');" description = "__INSERT__($uDescription);">
271)
272) <submittask name = "Staging" owner = "__INSERT__($sOwner);" start = "f" unlock = "t" override = "f" skiplocked = "f" description = "__INSERT__($uDescription);" savecomments = "t" skipconflicts = "f">
I am using TS6.5 on Win2K platform.
Thanks!
Adam Stoller
iwjobc only processes job description files - not workflow templates.
job description files are pure XML - with no imbedded Perl functions
__INSERT__(), __TAG__(), __VALUE__(), and __ELEM__() are all Perl functions and therefore cannot exist within a job description file.
On the other hand - since you're on TS6.5 - you should be able to make use of iwwft_compile.ipl (try running perldoc on IWHOME/bin/iwwft_compile.ipl for more detailed information).
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
Migrateduser
Ghoti is right on -- iwjobc operates on XML specifications, either from STDIN or a valid XML job spec file. If you were to look at the debug output of any parsed WFT file, you'll see the XML that iwjobc expects to read.
Dave
Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K