System Command on S3 Configuration in the Cloud

unknown

We are in the Cloud.  Initially, I created an S3 configuration to do some IPD testing until support created the S3 configuration.  I put in a few of the parameters to do some testing of SQL, AGS, DME, and Resource Queries nodes using my ID.  I built the JDBC with one of the SQL users with datareader access to the S3 databases LSLMDB, LSCUSTOMDB, LSGENDB, LMIPADB, and MSCM databases.  I put my ID, password, and the portal URL in the webrun connection.  I put in the GENDIR and LAWDIR in the system command.  Support did not create the configuration from scratch like I thought would happen but put in the URL, Lawson ID, and password in the system command on the configuration I created.  After support updated the S3 configuration I built, I tried to run system commands.  I have run a variety of commands with the S3 configuration.  The ones which work are ls, listusermap, and laservstatus.  Ones which fail are count gen, count logan, count lsapps, importdb, and rngdbdump.  I tried all 3 product lines since it appears that system commands without product lines work.  What is the proper way to have the S3 configuration built in the Cloud?

0911060553270289.pdf

russel-cornelson

In my opinion the proper way to configure IPA to use the System Command remotely against the LSF server is the same for on-prem as it is for cloud.



Step 1 - Configure PFI's Java processes to run as a known user -- KB 1896334

Without doing this, which ever user own's the java process for RMI on the LSF server is the user executing commands.



Step 2 - Set your environment variables before running your command.

A Remote System Command node is like opening a cmd.exe on your LSF Server and executing the exact command you provide it. This is not a LID session that sets environment variables, and the command may not be in your path variable thus will fail.



System command: cd D:lsfdirectory && enter.cmd && count lsapps



Step 3 - If you are getting a "Security Violation" that means you are getting to LSF and you do not have the appropriate LSF security to run the command you are executing. Talk to your security admin to get the appropriate security added to the user running RMI from step 1.







Some of these steps are different if you are on UNIX machine; example I think step 1 may not work on unix as that is started/stopped differently. But for unix clients most of the time the rmi is already running as a user that can be granted security. Running a System Command and returning "whoami" would help with that, along with "pwd" to determine your home directory. Obviously for step 2 - it would be easier to ". cv ENVIRONMENT && count dataarea"