Timeout for Webrun

I don't know that you can change the WAIT=TRUE timeout; I usually add a query against the Logan Queued Job table to check to see if the job is still running. If it is, I route the flow to the new Wait node for 2 minutes and then loop back to the query.

In the same boat, now! We have been using the Web Program = cgi-lawson/jobrun.exe, Success String = 63 and Post String = FUNC=RUN&USER=jobowner&JOB=PO135&OUT=XML&WAIT=true
, and it's worked for us. The"WAIT = TRUE" works and looks for the success string. However were told the jobrun.exe will no longer be supported and we should move to the - Web Program = "lawson-ios/action/SubmitJob?jobName=PO135&jobOwner=domain\owner&startDate=&startTime=&jobQueue=&displayOldFormat=true&OUT=XML". This does not except a wait parameter. So sticking with the former method. You can find an incident on Infor KB for this.

I should have mentioned that we are still on LSF 9.0.1 and LM 10.0.6 currently. So this means the wait=true works for us as long as the job runs less than around 5 minutes. Beyond that IPA thinks the job failed due to no response and then follows the failure logic in the process flow.

 

I do like the query against the QUEUEDJOB table. The only downside is that our version of IPA doesn't have the WAIT node, but I can probably figure something else out for that. I may as well start building along that direction anyway if Infor is moving away from Webrun and towards the Web Program.

When are they getting rid of jobrun.exe? I'm on 10.0.4 and it still works for me.

Jobrun, I'm just told they will no longer be supporting it.
Look at the KB and the JT status is still in “candidate for development”. “JT-787297”

To resolve this, perform the following steps:
1. Login to the WebSphere Administration (WAS) Console
2. Select Servers
3. Select Application Servers
4. Choose the Application server name
5. Access the Web server plug-in properties
6. Verify the current setting for Read/Write timeout and change as necessary
7. Regenerate and Propagate the web server plug-in after making any changes
8. Restart the web server
Note: This setting will need to be set high enough to accommodate the longest Data, Transaction, or Drill call that will be
run on your system. Most users will need to set this to at least 1800 (30 minutes).

Take a look at the following discussion: https://www.lawsonguru.co...aft=17070&afpg=1  related to this same topic.

 

 

 

Kyle,

Thank you for the steps.

I apologize up front as we are hosted so most of the server side stuff is out of my reach. Does this need to be done on a specific server (LFS, LM, etc.)? I'm not sure if each server has its own WAS service or if there is a single that all feed into.

 

Alexrs,

Thank you for that link. My search is not delivering any results for lawsonguru.com.