OpenEMM Technical Support Forum

Sorry, that last observation was tempered by some hours spent carefully following installation docs, with a couple of versions. I still do appreciate the generous gift of time spent on this by Agnitas. :) First time I tried to install OpenEMM I had the same issue. Eventually I solved restarting Ope...

Update: after figuring out what build-birt.properties etc. seemed to want in the nature of path to javac, we've arrived at: compile: [echo] Java Home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.275.b01-1.el8_3.x86_64/jre [echo] JAVA_HOME: /usr [echo] CATALINA_HOME: /opt/agnitas.com/software/tomcat [javac...

Sorry, that last observation was tempered by some hours spent carefully following installation docs, with a couple of versions.

I still do appreciate the generous gift of time spent on this by Agnitas.

One further observation: time is money, and time is being wasted here.

OpenEMM is an attractive product in many ways, possibly worth paying for, but as an introduction to how customer time might be spent this installation experience is not encouraging.

Unfortunately building the backend works but the corresponding other bits then fail to build. Buildfile: /home/openemm/frontend/build.xml checkForPropertiesFile: [echo] basedir: /home/openemm/frontend [echo] Using Java version 1.8 parseApplicationVersion: [echo] Building version: 19.10.000.000 [echo...

Or, perhaps it would be good to include the backend in the "obtain binaries" procedure?

The download process now leads to a single download with no indication that the binary on offer does not include everything necessary for an installation.

Greetings. I'm installing OpenEMM on a CentOS platform and am stuck at a complaint on restart: "/home/openemm/bin/backend.sh: No such file or directory." I see in other threads here a few others running into this problem, with advice to the effect of "see wiki for instructions on inst...