WebRun Node - to run script

 4 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Dave Curtis
Veteran Member
Posts: 136
Veteran Member

    We are trying to transition our Process Flows to replace the System Command nodes with WebRun nodes instead.

    Where we have a System Command set to run Korn shell script to process an FTP we need to replace it with a WebRun to run the cgi-lawson/jobrun.exe program to submit the script.

    We created a token for the script and set the WebRun node with the following Post string;

    FUNC=run&USER=User&JOB=JobName&PROD=appProdline&OUT=xml&WAIT=TRUE

    We can not get the script to run.  We have tried different users, made sure the users have access to the token that was created for the job and just can not get the job to run.

    Anyone have experience with the WebRun submitting a job to run a script?  Any tips on what we might be missing?

    Kyle Jorgensen
    Veteran Member
    Posts: 122
    Veteran Member
      Does the script run if you submit the job via Portal?
      I don't think you need the "PROD" option in the WebRun post string. I just checked some of ours and that option isn't in any of them.
      The product line is associated with the job (an user can't have 2 jobs with the same name in an environment).
      Dave Curtis
      Veteran Member
      Posts: 136
      Veteran Member
        When I submit it via Portal I get the same error as I see in the Work Unit log in process flow

        Error: Unable to find job record: job owner = Username job name = JobName

        I am told that my username has been granted access to the token but I still can not get it to run so is a token the correct method?


        Kyle Jorgensen
        Veteran Member
        Posts: 122
        Veteran Member
          Sounds like the problem is external to ProcessFlow. Once it's working from portal, the WebRun node should work too.

          As for troubleshooting the "Unable to find job record:..." error; query the JOBSTEP table in GEN to see if you can find it there. That's the table that stores jobs and their parameters. Maybe delete/re-add the job?
          Dave Curtis
          Veteran Member
          Posts: 136
          Veteran Member
            The issue ended up being that the job def was not there. The token had been created but not the job itself.

            Thanks for the help.