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

Launch Ant Script from WFM URLTASK

arjun_pallam

We are trying to launch a ant script that would build the EAR file.

Can we launch the ant script from the WFM URLTASK ?.

If so, what are the parameters we need to pass.

Or can we launch the ant script from the WFM ExternalTASK?.

what is the syntax for the command variable that can be used

If we cannot launch, what are other options

Find more posts tagged with

Comments

Rick Poulin

Given how little information you've provided, the best answer I can give is "yes, you can do that".

In terms of parameters, I expect it would be much the same as when you do it manually. You'd probably need to set the context to a particular directory and then specify the full path to the ant executable and perhaps even the build script. Beyond that, you'd have to provide more detail if you want a more specific answer.

Adam Stoller

You will probably also need to set some Environment variables - especially if doing a "standard" External Task.

Simplest thing to do is write a script to run the ant script that you can run from both the command line and the workflow - and have it dump a sorted list of all the environment variables (with their values) into a log file. If the script doesn't work when run from the workflow look carefully at that log file to figure out what environment variables you need to explicitly set within the script so that it will work when initiated from the workflow.

acserverconfig_copy.xml

arjun_pallam

We are developing a work flow model which would launch a exisintg ant script(build.xml) to build the WAR and EAR file.

for example:

We created a workflow model which has an external task to use the command variable to

The command variable is give the value /opt/iw/TeamSite/tools/ant/bin/ant -f {PATH}build.xml

{PATH} has an actual value in the command.

It was mentioned above - "Setting the context to a particular directory" - should the above mentioned command variable value given is enough?. or additional detail has to be provided.

Arjun

Rick Poulin

It seems like your understanding of your (presumably custom) ANT build is a little limited. The gist of the topic so far is that we can't tell you what context your ANT script depends on; that's for you to figure out.

If I read that wrong and you're calling an OOTB ANT script, then specify which one.