I am developing an application that should be as simple as possible to install for the end user. Although end users are likely to be experienced Linux users (or sales engineers), they don’t know anything about Tomcat, Jetty etc., and I don’t think they should.
So, I see 3 ways to deploy our applications. I must also say that this is the first application that I had to deploy with a web interface, so I have not come across this question before.
First you need to deploy the application to an existing web container. Since we are just deploying Suse or RedHat, this seems simple enough. However, we are small in the idea of using multiple applications in one web container. This makes it difficult to remove only one application.
The next option is to simply bundle Tomcat or Jetty and run startup / shutdown scripts in our unified web container.
Or 3rd, embed .. This will probably provide the same user interface as the second option.
I am curious what others are doing when faced with this problem in order to make it as possible as possible for the end user.
I almost ruled out deploying to an existing web container, because we often wanted to set limits on application resources and processor proximity, which, in my opinion, would affect all applications deployed to a web container / application server, and not just a specific application.
Thank.
Jason source
share