Our 9x flows worked fine. All of our syscommand nodes used the "su" syntax on a windows server:
su -p password username -c "my command here"
for example
su -p ABCD1234 lawsonuser -c "\\\\server\\sharename\\command.ba" (all backslashes are doubled because they need to be "escaped" first)
Problem 1: IPA no longer allows the "su" as part of syscommand -the documentation says it's no longer supported -I have tried running my syscommands with "su" and it says "cannot run program "su""
Problem 2: When I choose "run program directly", it errors with "cannot find the file specified" -have tried the default configuration -have tried my own configuration specifying my own username and password -I have confirmed the runnability of the command from the desktop of the lawson server
Problem 3: When I choose "run cmd.exe (windows only)", it errors with bad username/password -I have tried everything above with different users and configurations
Also: I have tried shell, kornshell...all errors
Help?
That's about as clunky as what I'm considering: xp_cmdshell. That's right, I said "xp_cmdshell". Getting my sql dba's to give my lawson user access so that I can run my command scripts through the SQL server node.
I'm still looking for an actual solution or for someone who is actually able to utilize the syscommand node in IPA. I would like to know their settings and configurations.