Cannot start localhost:8080/jbpm-console (jBPM5, JBOSS7)

[lisalipsky]

Hey everyone. I'm new to jbpm and jboss so I find myself lost in all the settings and configuration.

I downloaded jbpm-5.3.0.Final-installer-full.zip and followed the instructions ant install.demo. It seems to install succesfully. Running ant start.demo also seem to be successful but I cannot access localhost:8080/jbpm-console. I cannot even acces localhost:8080 and I have no other applications using the port when I'm running this app. I did a search in this forum however, there are several things I don't understand and would like some clarifications:-

1. The thread here mentioned something about jbpm-gwt-console-server.war.deployed and jbpm-gwt-console.war.deployed files in jboss-as-7.0.2.Final/standalone/deployments folder. I do not have those. What will cause these files to be generated?
2. Where can I find the server log file? I can't seem to locate it within the jboss-as-7.0.2.Final folder.
3. I tried localhost:9092 and it gave me a version mismatch error. Is this related to my issue?

I completely have no prior knowledge to this application so am grateful for any guidance and advise. Thanks in advance.

[swiderski.maciej]

*.deployed files are created by JBoss AS7 upon deployment, what you could do is to create these files manually for wach war file in deployments directory but instead of deployed make it dodeploy, for instance jbpm-gwt-console.war.dodeploy and if server is not running start it. AS7 should pick it up and deploy all the apps.

Server log can be found in jboss-as-7.0.2.Final/standalone/log

HTH

[lisalipsky]

Thanks for your reply, Maciej. I've created the *.dodeployed files manually as suggested but the jbpm-console still won't start. I couldn't get the localhost:8080 running at all.

In my jboss-as-7.0.2.Final/standalone folder I only have configuration, deployments and lib folder. I can't seem to locate where is my log folder.

Any further advise and guidance is much appreciated.

[lisalipsky]

I managed to get it working after several installation attempts. Upon successful deployment, the log folder also appeared.