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

submittask

getnaren

I am not able to submit the files to staging and deploy.
its generating the html files in the required folder..whats wrong with this wft?

Find more posts tagged with

Comments

Nidhi_Agrawal

I think ur workflow is waiting for approval to submit the files in staging area.
Just click on workflow and see in "All jobs".
If there is your job to be approved.
If yes then click on approve and then chk in the STAGING AREA.

Nidhi..

GroupListing.rptdesign

kaalraa

Naren,

Could you please attach your workflow.... as i dont think submittask needs any kind of approval. There must be something else... which is stopping the files to be submitted.

~ aks

getnaren

Here is the work flow

jbonifaci

First off, there should be no reason for your Unlock_1 or Unlock_2 tasks, as the submittask should take care of that.

Secondly, I noticed in your submittask you have both unlock='t' and skiplocked='t'. I'm not sure how these work together, but it seems to me that this is somewhat conflicting. I would remove skiplocked from the task. You also have both override='t' and skipconflicts='t'. Once again, I'm not sure how these work together, but it seems to be that this is also conflicting. I would remove skipconflicts from the task.

What exactly are you seeing? Is your workflow completing without the files getting submitted? Or is it getting stuck on a particular task?

~Jeff

kaalraa

Naren,

As what Jeff is saying... also stands same for me. Just do the changes mentioned and revert if you still get any issues. I hope you won't.

~ aks

getnaren

Jeff, I removed them

<submittask name='g1.submit'
owner='appadmin'
unlock='t'
override='t'
description='Submit to Staging'>

and still the files are not making to staging and front end server

I have generated news.html in news folder...same should move to staging and then publish out

jbonifaci

Ok, well, answer my other question then. What is happening in the workflow? Is it getting stuck on any of the external tasks?

~Jeff

getnaren

yes...its not making it to submittask

jbonifaci

Ok, where is it getting stuck then? On which task? If it's getting stuck on an external task, then you need to troubleshoot what is going wrong with that task.

~Jeff

getnaren

I saw the job....for some reasons files are not attached...

I have this code;

<externaltask name='Unlock_0'
owner='appadmin'
description='unlocking files'
start='t'>

<areavpath v='/default/main/www/WORKAREA/MANUAL'/>

<successors>
<successorset description='Done'>
<succ v='g1.generate'/>
</successorset>
</successors>
<command v='/Interwoven/TeamSite/local/bin/unlock.ipl'/>

<template_script>
<![CDATA[
if (__ELEM__('iw_file') != 0)
{
__INSERT__("<files>\n");
for (my $i=0; $i < __ELEM__('iw_file'); ++$i)
{
__INSERT__("<file path='__TAG__(iw_file[$i]);' comment=''/>\n");
}
__INSERT__("</files>\n");
}
]]>
</template_script>

</externaltask>

jbonifaci

I tried your task out and it generated fine for me. What is being output in the job spec for this task? Try turning on workflow debugging and see.

Is /default/main/www/WORKAREA/MANUAL the correct branch/workarea path?

Also, how are you kicking off the workflow? Are you checking modified files and then hitting submit, or what are you doing?

~Jeff

getnaren

g1.generate calls an ipl...hich generates html file usning iwgen I use tt_data

In my previous post...I had attached the workflow...i am attaching ipl file also

I see the jobs que as no files attached

my available_template.cfg has this

<template_file name='Submit and Publish Selected Files for news and research' path='/Interwoven/TeamSite/local/agg_data/config/wft/news_research_wf.wft'>
<command_list>
<command value='tt_data' />
<command value='tt_deletedcr' />
<command value='submit' />
<command value='all' include='no' />
</command_list>
<role_list>
<role value='all' include='yes' allusers='yes'/>
</role_list>
<branch_list>
<branch value="www" include="yes" />
<branch value="all" include="no" />
</branch_list>
</template_file>

Edited by getnaren on 12/16/05 11:06 AM (server time).

report_and_data.zip

jbonifaci

The attachment does not have your ipl in it. All it contains is:

filter valve model#FRS23H5AS

http://www.applianceblog.com/mainforums/register.php

http://www.applianceblog.com/mainforums/forumdisplay.php?f=37

That aside, am I correct in assuming that when you look at the job, it is stuck on the g1.generate task? If so, that likely means there is a problem with your command. Is the external script even being executed? Taking a look at your commands, you should probably be including the path to iwperl for each of the commands. It appears that your iw-home directory is /Interwoven/TeamSite? If so, you would probably want something like this:

<command v='/Interwoven/TeamSite/iw-perl/bin/iwperl /Interwoven/TeamSite/bin/agg_news_research_gen.ipl'/>

Add some logging to your perl script(s) to see if they are even being executed. I'm guessing your issues are with your external tasks. Either they are not being called correctly, or they are not calling back to the task correctly when they have completed. Do some debugging on your tasks and if you are still having problems, post what you did and what you are seeing that is wrong.

~Jeff

Adam Stoller

Assumptions

This is a Unix (Solaris?) installation of TeamSite
We're dealing with 6.5, though I don't believe it matters too much in this case
All externaltask scripts are executable (755, 775, or 777 mode bit settings) and all begin with: #!/Interwoven/TeamSite/iw-perl/bin/iwperl
The user appadmin is able to login with at least the editor role
There is at least one pre-selected file prior to this workflow being kicked off (or it's kicked off with tt_data)

All of that aside, I still see at least three ...
Problems with the workflow

Two start tasks: Unlock_0 and Unlock_1. While it is legal to have multiple start tasks, it's rarely needed and in this case - I believe it is a mistake, especially since the second start task (Unlock_1) is declared to have a predecessor (g1.generate)
The command for www File Deploy appears to be: "/Interwoven/TeamSite/iw-perl/bin/iwperl/Interwoven/TeamSite/bin/agg_www_deploy.ipl"i.e. - there's no space after iwperl - in fact, you shouldn't need the /Interwoven/TeamSite/iw-perl/bin/iwperl bit on Unix anyway - as long as that is in the #! line of the script and the script is executable (see assumptions above)
The same problem applies to the command for Deployment error

Suggestions

Remove the start="t" from Unlock_1 (or, as already suggested, remove Unlock_1 [and Unlock_2] altogether)
Remove the path to iwperl in the command line for www File Deploy and Deployment error tasks
Remove all activation clauses - those are only needed for workflows with concurrent tasks, you don't have any, so it just makes the workflow more complex looking without adding value (and potentially causing problems)

Then see if it works.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

getnaren

Ghoti,

I removed Unlock_1 and Unlock_2
Removed the path to iwperl in the command line for www File Deploy and Deployment error tasks
Removed all activation clauses

I have attached the modified workflow

now on staging the folder creates, but I dont see html file inside...its empty. I saw the deployment logs and it shows (this is few parts of log)

deployment=.G1_deployment1479140519.G1_deployment.g1_location
file_list=/tmp/1479140164933.lst
area=/iwmnt/default/main/www/STAGING
local_directory=.
user=cntown
dir_perm=0555
group=cntgrp
file_perm=0444
ignore_acls

Directories deployed : 0 Files deployed : 1 Links deployed : 0
Directories failed : 0 Files failed : 0 Links failed : 0
Directories deleted : 0 Files deleted : 0 Links deleted : 0

not sure what else could be causing this

Adam Stoller

One remaining mistake is:<externaltask name='www File Deploy'
owner='appadmin'
unlock='t'
override='t'
description='Deploying files for www'>as unlock and override are not attributes of an externaltask, however, this shouldn't be causing any problems (I believe they are silently ignored).

As for your deployment - well - you need to see what /tmp/1479140164933.lst contains. If it doesn't contain the correct file entry (relative to the source area and path elements) then you need to look at how you generate the file. The deployment does seem to indicate that 1 file was deployed though - so perhaps you're looking in the wrong place for it? Have you checked the OD logs or manifest (.mf) file to see what they say was deployed?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

getnaren

Thnaks Ghoti,

I got it working.