Ideas on why jasperstarter isn't working on deployment server

Scriptcase 8 Discussion
#1

Does anyone have advice configuring a linux server to run JasperStarter?

It works well on my Windows based development system, but I’ve spend a day researching and trying to get it working on the production server.

I get return code 127 from the PHP exec() function.
I’ve set all permissions on the JasperStarter folder to 777.
I’ve used the fully qualified path to jasperstarter.
Apache is not chrooted to the best of my evaluating.
PHP safe mode is not on.
In php.ini, user_dir and disable_functions have no value.

Commands like ‘ls’ work.

I’m out of ideas.
Thanks
Ed

#2

Solved, I hope this helps someone else.
First, I admit, I’m not very experienced with linux.

The error indicated inability to locate a file. I was able to get jasperstarter to run in the cli after I installed JAVA, created $JAVA_PATH pointing to the JAVA install location, added $JAVA_PATH and the JasperStarter path to $PATH.

However, it still didn’t work from the web page. I discovered Apache ran under a different user than my cli session and confirmed the $PATH and $JAVA_PATH were not set. I never did figure out were to set those variables so Apache would see them.

My success came after I modified the jasperstarter file to fully qualify java and the jasperstarter.jar file.

Since JasperReports is my only JAVA component in my ScriptCase project, I’m OK with this approach. However, I will still pursue a linux expert to get to the right solution.
Ed