We are senior students in the University of Alabama's MIS program.
We are currently working on a feasibility assessment of Activiti's features for enterprise integration for a company that we are contracted.
Our problem is that we are unable to connect to Activiti from a local machine to the server that has Activiti on it.
We have the server's IP address and are attempting to establish a jdbc connection via the information provided in the Activiti user guide.
On the server machine:
We have successfully installed Apache Tomcat 7.0, Activiti, and PostgreSQL.
We have Activiti connected to PostgreSQL as a standalone database and not in-memory, therefore, our data is preserved even when we close Activiti.
We have the demo settings set to false and changed db.properties to
db=postgres
jdbc.driver=org.postgresql.Driver
jdbc.url=jdbc
ostgresql://localhost:5432/activiti
jdbc.username=
jdbc.password=
We have the same setup on the local machine as the server machine.
We have used square brackets around the server's IP address.
We have tried Google and the user guide to help understand the problem and we have not found any answers.
We are currently working on a feasibility assessment of Activiti's features for enterprise integration for a company that we are contracted.
Our problem is that we are unable to connect to Activiti from a local machine to the server that has Activiti on it.
We have the server's IP address and are attempting to establish a jdbc connection via the information provided in the Activiti user guide.
On the server machine:
We have successfully installed Apache Tomcat 7.0, Activiti, and PostgreSQL.
We have Activiti connected to PostgreSQL as a standalone database and not in-memory, therefore, our data is preserved even when we close Activiti.
We have the demo settings set to false and changed db.properties to
db=postgres
jdbc.driver=org.postgresql.Driver
jdbc.url=jdbc
ostgresql://localhost:5432/activitijdbc.username=
jdbc.password=
We have the same setup on the local machine as the server machine.
We have used square brackets around the server's IP address.
We have tried Google and the user guide to help understand the problem and we have not found any answers.
