Using IPA To Execute A Command On A Remote Non-Lawson Server

ewingm

Scenario:   Our IPA Developer is creating a flow that queries data from the Lawson server that will be imported into another Application that is hosted on a remote Windows server.    The Developer would like to include a node in the flow that issues a command that will execute a command on the remote server to import the data into the application.   We are looking at the 'syscmd' node to accomplish this.   I have the following questions:

- Can the "syscmd"  node be used to execute commands on remote non-Lawson servers?   Or, is it limited to running commands on the LSF and/or Landmark servers? 

- Can the "Sys Cmd" tab in the Configuration screens be setup to access remote non-Lawson servers?

- If a "syscmd" node is setup to execute a script file that is local to the Landmark/IPA server,  does the "Sys Cmd" Configuration need to be specified?

 

Any recommendations?

 

russel-cornelson

Good afternoon Michael,



The System Command node, can only "Execute" commands on the Landmark server it is executing on OR a Lawson System Foundation server. It leverages the security delivered with LSF/Landmark to authenticate and gain access to the command line through the RMI server.



I quoted "Execute" because where there is a will, there is often a way.



If this was me trying to achieve this on a test system here, the first thing I would try is use the System Command node to locally execute a PowerShell script on the Landmark server itself.



Something like this:



Invoke-Command -ComputerName <servername> -ScriptBlock {

E:

cd IBMWebSphereAppServerprofileslandmarkin

serverStatus.bat server1

Write-Host "done"

}





When executing this from MY PC; against my test Landmark Server it returns:

PS C:Users
cornelson> Invoke-Command -ComputerName usspvwipa1 -ScriptBlock {

>> E:

>> cd IBMWebSphereAppServerprofileslandmarkin

>> .serverStatus.bat server1

>> Write-Host "done"

>> }

ADMU0116I: Tool information is being logged in file

E:IBMWebSphereAppServerprofileslandmarklogsserver1serverStatus.log

ADMU0128I: Starting tool with the landmark profile

ADMU0500I: Retrieving server status for server1

ADMU0508I: The Application Server "server1" is STARTED

done

PS C:Users
cornelson>









NOTES:



1. You may need to enable remote powershell on the destination non-infor server.

docs.microsoft.com/.../enable-psremoting



2. You may need to configure Landmark Grid to execute as a domain account that has access to both the Landmark Server, and the non-Infor server. When I execute this script from my PC it executes as myself using my windows network credentials.



3. The script block ... each successive command is on a new line between the brackets { }, this is the equivalent to using command1 && command2 && command3 in the system command node.





Hope this helps.

--Russel Cornelson, Principal Technical Support Analyst for Infor Process Automation