how to trigger process flow using a different job scheduler (ex. ESP)

Conrad -

There are a number of trigger options for a process flow and some are based upon your licensing.

Typically, interface files like AP520 are triggered on a demand-driven basis using the BCI Scan File client - BCI trigger is configured to look in a certain directory for the input file and then it triggers a process flow for the interface (like AP520).

A custom trigger can also be used with the Lawson API - the "WFWK.1" method if you will - you can trigger a process flow with a URL. This method is typically used when integrating third-party non-Lawson systems, such as embedding the trigger under a web form in some other application someplace.

There are still yet several other options, including PFI/LPA nuances, but thought these 2 might be most relevant for you.

Feel free to add some more detail and/or send an email with more info and I can point you in the right direction.

Rob

Conrad - If you are just trying to launch a batch program (AP520), then you should be able to use jqsubmit or wtsubmit.  The two utilities do the same thing.  The only difference is that jqsubmit immediately returns to the command prompt, while wtsubmit waits until the job completes (or fails) before returning to the command prompt.

Good Luck!

Kelly

Conrad -

IF you just want to kick off a batch job from PFI, then you can also use the cgi programs within Lawson to do so via a URL call ("jobrun.exe" is an example) from the Web Run node. You can add "Wait" syntax to the command, so that the flow waits until the job completes before moving to the next node within a flow. The wtsubmit program will also work within a PFI (per above) but that requires the Integrator license to use the System Command.

Keep in mind there are also timeout values that might need to be tweaked in Websphere (web run) or pfserv config (sys cmd), should the batch jobs run too long (outside the parameters of the default timeout values) causing a PFI run time failure. Once you reset the timeout parameters to accommodate the longer jobs, life is good.

Anyhow, I've seen it done (and have done it) both ways in a variety of scenarios using PFI.

Good luck with your project!

Rob

Conrad -

IF you just want to kick off a batch job from PFI, then you can also use the cgi programs within Lawson to do so via a URL call ("jobrun.exe" is an example) from the Web Run node. You can add "Wait" syntax to the command, so that the flow waits until the job completes before moving to the next node within a flow. The wtsubmit program will also work within a PFI (per above) but that requires the Integrator license to use the System Command.

Keep in mind there are also timeout values that might need to be tweaked in Websphere (web run) or pfserv config (sys cmd), should the batch jobs run too long (outside the parameters of the default timeout values) causing a PFI run time failure. Once you reset the timeout parameters to accommodate the longer jobs, life is good.

Anyhow, I've seen it done (and have done it) both ways in a variety of scenarios using PFI.

Good luck with your project!

Rob