Difference between revisions of "Information Systems:Web Orders doesn't start"

From uniWIKI
Jump to navigation Jump to search
m
m
 
Line 4: Line 4:
 
* If the issue is more grave, check the WebSmart (Apache) jobs: <code>WRKSBSJOB SBS(QHTTPSVR)</code> and confirm that the instance isn't running, then troubleshoot by looking at the spooled files for the web server user i.e. <code>WRKSPLF QTMHHTTP</code> and checking for errors. Check QSYSOPR message queue also.
 
* If the issue is more grave, check the WebSmart (Apache) jobs: <code>WRKSBSJOB SBS(QHTTPSVR)</code> and confirm that the instance isn't running, then troubleshoot by looking at the spooled files for the web server user i.e. <code>WRKSPLF QTMHHTTP</code> and checking for errors. Check QSYSOPR message queue also.
   
[[http://bart.unipharm.local:2001/HTTPAdmin Manage the web instances of Apache (http://bart.unipharm.local:2001/HTTPAdmin)]]
+
[http://bart.unipharm.local:2001/HTTPAdmin Manage the web instances of Apache (http://bart.unipharm.local:2001/HTTPAdmin)]
   
 
[[Category: Web Orders]]
 
[[Category: Web Orders]]

Latest revision as of 12:29, 1 June 2020

If Web Orders doesn't start:

  • Most common problem is the backup took too long. Check the batch jobs, especially if there are also complaints about delayed cycle counts and printouts not working. Specifically, issue a: WRKJOBQ QBA* and check if QBATCH is in HLD (held) status. If so, issue a 6 to release it.
  • If the issue is more grave, check the WebSmart (Apache) jobs: WRKSBSJOB SBS(QHTTPSVR) and confirm that the instance isn't running, then troubleshoot by looking at the spooled files for the web server user i.e. WRKSPLF QTMHHTTP and checking for errors. Check QSYSOPR message queue also.
Manage the web instances of Apache (http://bart.unipharm.local:2001/HTTPAdmin)