Server configuration parameters

System Command user and System Command password

In some releases of Infor ProcessFlow, the System Command user and password could be used in some execution modes to run a command as a user. This allowed the user to log in as the user of the machine itself, not the web user. These execution modes are not available in Infor Process Automation.

If you are converting an Infor ProcessFlow flow that included either of the execution modes, Run shell as System Command user (Unix) or Run shell as System Command user with password (Windows), it is likely that you will need to perform post-conversion manual steps. Detailed information is available in the Lawson Knowledge Base article, "System Command Activity Node: Converting from ProcessFlow to Infor Process Automation."

Once you are using Infor Process Automation, the System Command node will use the "Lawson" user except in the following situations:

• If Execution mode is set to "run shell as system command user (Unix only)," the System Command node uses the Run As user, and will result in an error if Run As user is blank.

• If the command string contains **Username**, then **Username** is replaced with the username specified in the System Command connection, and will result in an error if the System Command user name is blank.

System Command timeout

The System Command timeout parameter specifies the amount of time, in seconds, that the System Command activity will wait for new output from the system command, before timing out and throwing an error. The timeout prevents a command from hanging the flow indefinitely. The default of 30 seconds should be sufficient to allow most programs to run, but the value may need to be increased if executed commands run longer than 30 seconds without producing output, or if they run longer than 30 seconds and redirect their output to a file. The server must be restarted for any changes made using pfserv config to take effect.