Thanks for the response Eddie,
Certainly is food for thought on your suggestion.
However I wanted to share a recent enough example of someone who took some time to try and document the process of installing the required prerequesites, Tomcat and war files to complete a community install for 6.2 etc...
For reference, I'm also gonna make reference to url link: Alfresco 6.2 community Install
Given it's possible that this document might help but it's likely that issues will come up with this walkthru such as
- this might only work with a very specific OS distro/build
- If someone doesn't use the correct JRE build since the newer OS distros might have newer version of JRE so it's possible due to newer jre build that some serverlet components might not work because of deprecated code as often JRE can potentially update their code and the aflresco might require specific version of JRE (I'm suspecting it might matter)
- Also just as much depending on a persons choice of DB used for setup, there is also specific version of java db connector and the parameter strings which may not always work properly (again some because of code deprecation)
I'm sure there's more things to add to this list but it's really intended to make a point and help to encourage vendor to make it easier. In the older 5.x days, It was simply a bin installer and a script walkthru which made it easy enough for almost anyone with a little knowledge to successfully get things running quickly. I've previously recommended the community edition to other before for 5.x because of it's simplicity to deploy however 6.2, standalone install is no longer that easy and some people I know don't want to just test PoC with the container platform. So it goes without saying,
Other suggestions as food for thought and maybe this could be for Aflresco themselves to consider in providing a prebuilt VM appliance (many vendors do this) already setup with the necessary stuff to allow someone to use for either just for community use purpose or providing to prospective customers who are evaluating the product based on small on premise build vs. container. Again this is merely feedback perspective but, it might be a good stepping stone
In my own experience, I know running the container version is much easier to deploy but having a reasonably robust document or even webinar like video demo showing customers a walkthrough on how it's done and some of the important caveats or point of interest to ensure a higher percentage of success as I'm sure some will shy away in trying alternate product.