Congratulations on reaching public beta stage. First impressions are very favourable.
To put the following comments in context I've only tried tcServer on my local (Windows) dev box so far and am in the process of attempting to replicate the functionality I have with some Tomcat 6.0.18 instances behind an Apache httpd server configured for sticky session handling. I used the "Spring Source" directory structure since this seems identical to what I have on my previous Tomcat instances (the single binaries with separate instances).
I downloaded JDK 1.6.0_13 for the purpose of running tcServer and followed the "Getting Started" guide. It seems that a "server" version of the JRE is required (this is not the default on installation) to start each tcServer Windows service but I don't think this is mentioned in the guide. For expediency I simply copied the "client" directory of my installed JDK to a "server" directory - assuredly not the correct approach but I was keen to get on with getting tcServer up and running.
I'm not quite sure what the process of creating data sources in the AMS Server GUI actually does behind the scenes. I guess I was expecting some new <Resource> elements to appear in the context.xml files of my tcServer instances as I have in my previous Tomcat instances. However, "pushing" the changes from the GUI out to the instance did not have this effect and my app refused to run due to being unable to find its data sources. Manually copying those tags to context.xml (and putting the ubiquitous classes12.zip into the lib directory to provide me with an Oracle data source) does the trick. I suspect this is not the right way but it works for now. Am I missing something?
As a bit of an aside the default port used for the AMS Agent (2144) seems to be used by iTunes on Windows - not an issue for most servers but might delay people slightly on local dev machines
Overall I'm very impressed so far.