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

External Task

kaalraa

Hi there,

I have workflow... which has an external task creating a dynamic workflow using WFconstructor.pm. In the dynamic part there is another external task to be used for calling another perl file with a parameter passed to it.

That particular perl code (.ipl) is not responding... i am using the word NOT responding bcoz it is not even rendering the first line of code written in it. Can anyone help or suggest .. is there anything a sort of registering an .ipl file or configuration in IWOV about an IPL file is being used.

I am asking this as all other external tasks calling from dynamic part as .pl are working fine, only .ipl file is NOT Smiley Sad

- AKs.... The Shadow

Find more posts tagged with

Comments

Migrateduser

Hmmm, seems like someone who refers to themselves as an "Interwoven Professional" and who has written such a complex workflow would know how to debug an externaltask's script. Did you seriously create those workflows and you don't have a clue how to debug a perl script?

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

jbonifaci

What happens when you compile the perl script? What happens when you run it from the command line with the appropriate workflow arguments?

kaalraa

Sometimes the most trivial of the problems can also create an issue esp when one is working against time.
As for the debugging of the external task... it is not about debugging the perl script... the debugging is done when the code executes and not before that...
If you can help... i would appreciate that... else i would let you do your work...

- AKs.... The Shadow

kaalraa

The task is getting complied and is executing without any issues from command line... when i try to put it in the workflow is where the problem starts... Not even the first line of code is getting executed.

- AKs.... The Shadow

nipper

how about the other question does the script compile ?

nipper

how is it being invoked ?

save your XML and run that exact command from a command line

Migrateduser

As for the debugging of the external task... it is not about debugging the perl script... the debugging is done when the code executes and not before that...

Huh? If it's not about debugging the perl script, then what else can it be about? If you screwed up your wprkflow template, you would have gotten an error of some kind, so it must be about debugging your script. Did you debug your script outside of the workflow? I will help you help yourself, but I won't do your job for you. It sort of sounds like that's what you're looking for.

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

jbonifaci

So what happens when you run it from the command line with the appropriate workflow arguments?

kaalraa

The external task is supposed to hit a URL and exit. It takes as parameter the URL to hit. When i run it from the command line giving it the nec arguments it completes without error and closes.

- AKs.... The Shadow

jbonifaci

Are you executing the exact command you have in your workflow? And when you do it manually the task transitions? Do you the path to iw-perl and the script fully qualified? If so, are there any differences in the environment variables present?

~Jeff

nipper

What is your first statment in the scritp ? Log to a new file ?

Make your script echo the parameters to a file and exit. Bag the URL

see what happens. Likely the JobID or TaskID is being consumed as well

This is debugging 101 (just cause I know Smitty will say that too)

kaalraa

I will help you help yourself, but I won't do your job for you. It sort of sounds like that's what you're looking for.

I don't want an Sr. Engineer who only tries to destruct the buildings constructed by other professionals. Hope to get some good professionals on devnet world... who are really here for suggestions and constructions.

- AKs.... The Shadow

nipper

try losing the attitude, providing some information for people to work with and then you
might get some help.

kaalraa

"....who has written such a complex workflow would know how to debug an externaltask's script. Did you seriously create those workflows...."

I know... to get help one has to get down. But when the person on other side tries to check about yours work calibre then definitely... there is something which is not desirable to the person asking for help.

- AKs.... The Shadow

jbonifaci

Well, in all fairness, Smitty does come across a bit harsh with some of his comments. Whether they are deserving or not, I won't comment on, but when addressed with harsh comments, people tend to reply with the like.

~Jeff

kaalraa

Anyways Jeff... no issues at all.... we all are working towards helping each others problem solving techniques.

Also as per your query about what happens whn all parameters passed on command line... I have already checked the same earlier and it closes the job without any problem.

(/abc.ipl param jobId taskId Area)... this is what i have passed on command line... and result is what was expected. The job flows through end

- AKs.... The Shadow

jbonifaci

I would recommend always using the full path to iw-perl and to the script within your external tasks. If you do that, I'm sure it will solve your problems. i.e.:

<iw-home>/iw-perl/bin/iwperl <iw-home>/<pathToScript>/<scriptName> <arg1> <arg2> ...~Jeff

ccprofessional

I have seen instances where the WF and external tasks are just fine, but WF engine fails to invoke the external task/script.

If I were you I would open a support case at the same time.

btw, What version of TS and SP? and is this on Windows or Solaris?

kaalraa

Jeff,

On doing the debugging part i have also tried to have the command to run like this as well.

/appl/iwov/iw-home/bin/iwperl /appl/iwov/iw-home/local/bin/production_direct/cache_flush.pl DEV

I hope you are also saying the same thing to be done

- AKs.... The Shadow

kaalraa

But this may be some of the instances... where in my case... it is not responding at all for the past 20-30 regular test cases. and thats why i am more concerned about this.

- AKs.... The Shadow

Migrateduser

I think you lost him by the time you got to "executing"...

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

Migrateduser

Do you write fortune cookies as a night job? Just curious.

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

kaalraa

Jeff,

Just curious to know... that why it has been recommended to use the perl compiler for every perl file when working with interwoven. As far as my understanding about IWOV is it has its own compiler and interpreter which manages all about a perl file.

Is it a known bug along with interwoven or just enhanced functionality.

Thanks for all your help and also to make you aware that my code executes with perl compiler BUT i have to change my .ipl file to .pl file. Don't know why sometimes things don't work in order which they should work.

- AKs.... The Shadow

nipper

you certainly don't understand how TeamSite uses Perl.

suggestions to use the compiler were to verify there are no syntax errors

Interwoven ships a version of Perl with TeamSIte, so that there is a
know good consistant version of TeamSite with all the appropriate modules
that are needed. IW changed the suffix to ipl and called it iwperl so that it
can co-exist with with versions of perl on the same system.