You are very correct here, especially with the complex setup and usage of Workflow, and I was making several more tacit assumptions. First things first. The Advanced Troubleshooting Guide in Advantage has a section on troubleshooting Workflow (I wrote it), and while it isn’t exhaustive, the techniques there can solve many of setup problems users encounter. BTW, that was written when 6.0.1 was current. As Mark mentioned above, running the configurator while the server isn’t running is an EXCELLENT test because it will verify the connections to the broker and the DB. Again, with 6.0.1 and older (maybe newer), the installer will attempt to start workflow as a service in Windows. However, since the config isn’t right, only a few javaw processes will start. If possible, it’s good to make sure there are no javaw processes running when you start the Workflow Config.
Specifically, with the HTML inbox, assuming the login screen shows up, here are a few other things to check:
–username and password are correct
–project name is supplied
–server is supplied as <server>:<port>
–Workflow.war file is EXACTLY the same version as the workflow server (including fix levels)
The tough 200/OK occurs when the user gets a valid login screen and then, upon submitting the login info, gets the 200/OK. Assuming everything in the advanced troubleshooting guide and the above have been checked, then I’d look into using Tomcat or something similar.
I haven’t used it in 6.1 or later, but in 6.0.1 and prior versions, the embedded engine would swallow most of the useful debug messages–making troubleshooting difficult. Please let me know if this has changed since then. For a small shop with a low-load system where the built in client works, it is fine.