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
<build> <plugins> <plugin> <groupId>org.zeroturnaround</groupId> <artifactId>jrebel-maven-plugin</artifactId> <executions> <execution> <id>generate-rebel-xml</id> <phase>process-resources</phase> <goals> <goal>generate</goal> </goals> </execution> </executions> </plugin> <!– A simple Jetty test server at http://localhost:8080/activiti-webapp-rest can be launched with the Maven goal jetty:run and stopped with jetty:stop –> <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>maven-jetty-plugin</artifactId> <version>6.1.24</version> <configuration> <connectors> <connector implementation="org.mortbay.jetty.nio.SelectChannelConnector"> <port>8081</port> <maxIdleTime>60000</maxIdleTime> </connector> </connectors> <stopPort>9955</stopPort> <stopKey>activiti-webapp-rest</stopKey> <!– Redeploy every x seconds if changes are detected, 0 for no automatic redeployment –> <scanIntervalSeconds>0</scanIntervalSeconds> <!– make sure Jetty also finds the widgetset –> <webAppConfig> <contextPath>/activiti-rest</contextPath> <baseResource implementation="org.mortbay.resource.ResourceCollection"> <resourcesAsCSV>src/main/webapp</resourcesAsCSV> </baseResource> </webAppConfig> </configuration> </plugin> </plugins> <pluginManagement> <plugins> <!–This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.–> <plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</artifactId> <version>1.0.0</version> <configuration> <lifecycleMappingMetadata> <pluginExecutions> <pluginExecution> <pluginExecutionFilter> <groupId> org.zeroturnaround </groupId> <artifactId> jrebel-maven-plugin </artifactId> <versionRange> [1.0.7,) </versionRange> <goals> <goal>generate</goal> </goals> </pluginExecutionFilter> <action> <ignore></ignore> </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata> </configuration> </plugin> </plugins> </pluginManagement> </build>
<!– A simple Jetty test server at http://localhost:8080/activiti-webapp-explorer2 can be launched with the Maven goal jetty:run and stopped with jetty:stop –> <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>maven-jetty-plugin</artifactId> <version>6.1.24</version> <configuration> <stopPort>9966</stopPort> <stopKey>activiti-webapp-explorer2</stopKey> <!– Redeploy every x seconds if changes are detected, 0 for no automatic redeployment –> <scanIntervalSeconds>0</scanIntervalSeconds> <!– make sure Jetty also finds the widgetset –> <webAppConfig> <contextPath>/activiti-explorer2</contextPath> <baseResource implementation="org.mortbay.resource.ResourceCollection"> <!– Workaround for Maven/Jetty issue http://jira.codehaus.org/browse/JETTY-680 –> <!– <resources>src/main/webapp,${project.build.directory}/${project.build.finalName}</resources> –> <resourcesAsCSV>src/main/webapp</resourcesAsCSV> </baseResource> </webAppConfig> </configuration> </plugin> </plugins> <pluginManagement> <plugins> <!–This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself. –> <plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</artifactId> <version>1.0.0</version> <configuration> <lifecycleMappingMetadata> <pluginExecutions> <pluginExecution> <pluginExecutionFilter> <groupId> org.zeroturnaround </groupId> <artifactId> jrebel-maven-plugin </artifactId> <versionRange> [1.0.7,) </versionRange> <goals> <goal>generate</goal> </goals> </pluginExecutionFilter> <action> <ignore></ignore> </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata> </configuration> </plugin> </plugins> </pluginManagement> </build>
<!– Running example processes –> <dependency> <groupId>org.codehaus.groovy</groupId> <artifactId>groovy-all</artifactId> </dependency>
<!– Testing –> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <scope>test</scope> </dependency> <dependency> <groupId>com.google.gwt</groupId> <artifactId>gwt-servlet</artifactId> </dependency> <!– Vaadin addons –> <!– Must be defined both in activiti-explorer and activiti-webapp-explorer, as otherwise the gwt compiler won't find it –> <dependency> <groupId>org.vaadin.addons</groupId> <artifactId>dcharts-widget</artifactId> <version>0.10.0</version> </dependency>