PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 03/24/2017 3:04 PM by  TimC
Webrun to submit job not working
 19 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Terry P
Private
Private
Veteran Member
(612 points)
Veteran Member
Posts:234


Send Message:

--
04/24/2013 7:03 PM
    I have a simple flow to submit a job PO120. We are running on a Windows server. I have tried  using both my userid with and without the domain - both give the same result. Listed below is the Post String and the log that indicates it ran successfully - but it doesn't. Any clues on what is going on? I never see the job in the job log in Portal even.

    FUNC=run&USER=4JLSFDEV\pickering&JOB=PO120&OUT=text&WAIT=true


    Started on server: Apr 24, 2013 3:22:05 PM PDT

    Process started: DesignerTest - 04/24/2013 15:22:06.670

    Activity started: Start  (Runtime Id: START1)

    Starting Execution of Activities .....
    Variables in Process : DesignerTest Workunit : 258, ActivityType=START, ActivityName=Start, ActivityId=START1 Date:04/24/2013 Time:15:22:06.680
    oWorkUnit(Type=String) = 258
    oCatValue(Type=String) =
    appProdline(Type=String) = DEV
    ccsProdline(Type=String) = LOGAN
    _service(Type=String) = DesignerTest
    _user(Type=String) =
    oCatKey(Type=String) =
    appsKey(Type=String) =
    appsValue(Type=String) =
    oProcessId(Type=String) = 258
    mailServer(Type=String) = smtp.lane.edu
    LAWDIR(Type=String) = D:\lawdev\law
    GENDIR(Type=String) = D:\lawdev\gen

    Activity completed: Start

    Activity started: WebRun4350  (Runtime Id: WEBRN2)
    Executing WebRun Activity  WebRun4350.....
    (LHC) Posting to URL lltdev.4j.lane.edu:443/cgi-lawson/jobrun.exe
    Executed WebRun Activity WebRun4350 Found success string "
    Activity completed: WebRun4350

    Activity started: End  (Runtime Id: END3)
    Executing Stop Activity .....
    Activity completed: End
    Process completed - 04/24/2013 15:22:07.074

    Flow ran successfully
    Information code: 0
    Return message:

    Finished: Apr 24, 2013 3:22:07 PM PDT


    David Williams
    Private
    Private
    Veteran Member
    (3076 points)
    Veteran Member
    Posts:1036


    Send Message:

    --
    04/25/2013 7:31 AM
    Did you check the job log listing for the ProcessFlow user (pfuser or lawson)?
    David Williams
    Terry P
    Private
    Private
    Veteran Member
    (612 points)
    Veteran Member
    Posts:234


    Send Message:

    --
    04/25/2013 9:40 AM
    Nothing under lawson or weblaw. Did not see a user pfuser
    David Williams
    Private
    Private
    Veteran Member
    (3076 points)
    Veteran Member
    Posts:1036


    Send Message:

    --
    04/25/2013 10:19 AM
    So, I'm going to assume the Web Program in your WebRun is cgi-lawson/jobrun.exe

    I don't know if you're running into a security setting that won't allow your ProcessFlow user submit another user's job? Have you checked the security logs?
    David Williams
    John Henley
    Private
    Private
    Senior Member
    (9650 points)
    Senior Member
    Posts:3234


    Send Message:

    --
    04/25/2013 10:39 AM
    The webrun is a little picky on Windows servers
    What option do you have the Check the 'Content Type'?
    Make sure it's set to the first one (blank).
    Thanks for using the LawsonGuru.com forums!
    John
    John Henley
    Private
    Private
    Senior Member
    (9650 points)
    Senior Member
    Posts:3234


    Send Message:

    --
    04/25/2013 10:40 AM
    Also, the user should be the ssop username (i.e. whatever is used to login to Portal, typically without the domain).
    Thanks for using the LawsonGuru.com forums!
    John
    Terry P
    Private
    Private
    Veteran Member
    (612 points)
    Veteran Member
    Posts:234


    Send Message:

    --
    04/25/2013 10:51 AM
    Made sure the content type was checked. Made sure it was just my username. And yes jobrun is the default. I can run jobs manually from Portal. I can run Process Flows.

    We are a Infor Managed Services, so I am unfamiliar with tracking down the log files. Can you point me to where and the name to look in?
    John Henley
    Private
    Private
    Senior Member
    (9650 points)
    Senior Member
    Posts:3234


    Send Message:

    --
    04/25/2013 11:47 AM
    Sorry, I don't think my instruction regarding content type was very clear--what content type do you have it set to?
    Thanks for using the LawsonGuru.com forums!
    John
    John Henley
    Private
    Private
    Senior Member
    (9650 points)
    Senior Member
    Posts:3234


    Send Message:

    --
    04/25/2013 11:48 AM
    Also, you're just trying to get it running first from the designer, correct?
    Thanks for using the LawsonGuru.com forums!
    John
    Terry P
    Private
    Private
    Veteran Member
    (612 points)
    Veteran Member
    Posts:234


    Send Message:

    --
    04/25/2013 12:26 PM
    I set the content type to "text/plain".

    And yes, I'm just trying to run from PF Designer and running on the server.
    John Henley
    Private
    Private
    Senior Member
    (9650 points)
    Senior Member
    Posts:3234


    Send Message:

    --
    04/25/2013 2:31 PM
    Change the content type from text/plain to the blank (first) option.
    Thanks for using the LawsonGuru.com forums!
    John
    Terry P
    Private
    Private
    Veteran Member
    (612 points)
    Veteran Member
    Posts:234


    Send Message:

    --
    04/25/2013 4:27 PM
    That is what I had originally. Changed it back and it still doesn't work.
    Kyle Jorgensen
    Programmer/Analyst
    WoodmenLife
    Veteran Member
    (314 points)
    Veteran Member
    Posts:116


    Send Message:

    --
    05/01/2013 6:22 PM
    Did you ever find a solution?
    Check these:
    1. Make sure the job's name on PO120 is actually "PO120" (per your post string)
    2. Make sure the correct user is in your post string
    3. Try changing the "OUT" parameter on your post string to "xml"; and then put "63" in the Success String Field. "63" equates to "Normal Completion". With this setup you can use the "nodename_success" output variable to see if the job completed normally (it's a boolean; it will be true if the SuccessString was found in the node's result). If it didn't, examine the "nodename_result" variable.
    4. Depending on your setup, the jobs submitted via WebRun are likely submitted as the user 'lawson'. Be sure that user has security to the program.
    5. You can use the job scheduler via LID to determine the disposition of the submitted job. If you're unfamiliar with the command it's "jobschd". Check for completed and waiting jobs for all users.

    Hope this helps.

    -Kyle Jorgensen
    Woodmen of the World
    Kyle Jorgensen
    Programmer/Analyst
    WoodmenLife
    Veteran Member
    (314 points)
    Veteran Member
    Posts:116


    Send Message:

    --
    05/01/2013 6:23 PM
    OK...the value for SuccessString didn't come through right on my last post.

    Let's try this:
    63 
    Terry P
    Private
    Private
    Veteran Member
    (612 points)
    Veteran Member
    Posts:234


    Send Message:

    --
    05/01/2013 7:01 PM
    What is really strange is it works by using the browser to submit the job:

    https://lltdev.4j.lane.edu/cgi-lawson/jobrun.exe?FUNC=run&USER=pickering&JOB=PO120&OUT=text


    gives the following output:


    Job has been submitted. prtfilepath=D:\lawdev\law/print/4JLSFDEV_pickering/po120/1 prtfilename=PO120.prt printer,description test,test


    I tried some of your suggestions and it doesn't work still. Nothing shows up in LID either.
    Terry P
    Private
    Private
    Veteran Member
    (612 points)
    Veteran Member
    Posts:234


    Send Message:

    --
    05/09/2013 1:28 PM
    Finally tracked down the problem. When running locally, there was no problem. When run on the server I kept getting a security error about the job queue. Found that no matter what user you use, when running on the server it runs under the user listed in the bpm.properties file - which in our case was "Lawson". The user Lawson had a different job queue in LAUA then everone else. I changed it to what all our uses used and everything works fine now. I did not investigate WHY or WHAT the differences were. But it works now.
    TimC
    Systems Analyst
    Private
    Veteran Member
    (220 points)
    Veteran Member
    Posts:84


    Send Message:

    --
    02/02/2017 12:58 PM
    Hello,
    Getting the error: Return message: Connection null, type "WebRun", not found in configuration "main"
    How do I configure this in the configuration set, Main?
    David Williams
    Private
    Private
    Veteran Member
    (3076 points)
    Veteran Member
    Posts:1036


    Send Message:

    --
    02/02/2017 1:06 PM
    Just duplicate the settings from Infor Lawson to the Web (Web Run Connection) tab in your Main Configuration.
    David Williams
    TimC
    Systems Analyst
    Private
    Veteran Member
    (220 points)
    Veteran Member
    Posts:84


    Send Message:

    --
    02/02/2017 3:14 PM
    NVM. Researched a KB article here:
    https://www.inforxtreme.com/espublic/EN/AnswerLinkDotNet/SoHo/Solutions/SoHoViewSolutionC.aspx?SolutionID=1670959&kb_is_archived=0&kb_accessed_from=KBSearchResult
    TimC
    Systems Analyst
    Private
    Veteran Member
    (220 points)
    Veteran Member
    Posts:84


    Send Message:

    --
    03/24/2017 3:04 PM
    INFOR had me change the pointer for the WebRun to run is as AGS vs CGI

    /lawson-ios/action/SubmitJob?jobName=&jobOwner=&startDate=&startTime=&jobQueue=&displayOldFormat=true&OUT=XML
    You are not authorized to post a reply.