Forum Discussion

ahooper's avatar
ahooper
Frequent Visitor
11 years ago

ready-api.log and ready-api-errors.log paths

Hi all,

I'm using Ready API 1.2.2 on a Linux system and am having trouble over-riding the log file output path when calling testrunner.sh.

 

We have installed to /opt/SmartBear/ReadyAP-1.2.2, and unless I make the bin/ subdirectory of that path writeable by the user (not a good idea!) I cannot even launch the GUI. Starting testrunner.sh has the same issue. If I temporarily make bin/ writeable, I can launch the GUI, run tests, etc.

 

Even if installed into a user's home directory, we'd prefer for logs not to be created in the same dir as the binaries. How can we set:

a) a system-wide log path, and/or

b) a log path for the user concerned (presumably by editing via ~/soapui-settings.xml)

?

 

Thanks,

Ashley

3 Replies

  • WaikatoUni's avatar
    WaikatoUni
    New Contributor
    11 years ago

    We really want to know the answer to this one. Having bin/ writeable by the user running testrunner.sh is absolutely not ideal.

  • Armageddonsoft's avatar
    Armageddonsoft
    Contributor
    11 years ago

    You should be able to change the path in the soaui-log4j.xml file in the \bin folder. Change the File param value to include the desired path.

    • WaikatoUni's avatar
      WaikatoUni
      New Contributor
      11 years ago

      Thanks for your reply. Changing paths in soapui-log4j.xml is not a solution to this problem. It allows only changing of selected log files (which doesn't include error.log) and furthermore, even having changed the paths in soapui-log4j.xml, ReadyAPI still requires WRITE access to our bin directory to even start.

       

      Normally, the purpose of keeping binary and/or executable files in a bin/ subdirectory (or its Program Files equivalent on Windows) is precisely so that program code can be separated from variable files. It would be great to see ReadyAPI respect this long-established convention.