Mladen,
On 12/20/20 09:40, Mladen Turk wrote:
On 19/12/2020 00:16, Christopher Schultz wrote:
Mladen,
On 12/18/20 15:10, Mladen Turk wrote:
It can be used for various deployments.
Apache Tomcat can use catalina.bat directly
for running service ... more details at
https://github.com/mturk/svcbatch/blob/master/docs/examples/apachetomcat.md
I'd love to get some feedback from folks
that are using Apache Tomcat on Windows platform.
I don't generally use Windows, so I don't have a horse in this race,
but I'm curious as to the complaints against procrun versus what
SvcBatch provides. Can you give some examples of problems that
SvcBatch solves?
The major problem it solves is single point of configuration.
SvcBatch uses catalina.bat to run Tomcat, so there is no
need for additional configuration which Procrun saves in registry.
Gotcha. This is indeed a significant improvement IMO. Being able to more
easily script things is always good, and working with on-disk config
files is always easier (again, IMHO).
Also using GUI for configuration is unproductive
when there are many instances that need to be configured,
and particularly for servers versions that do not have GUI.
You can theoretically specify everything from the command-line but if
you want to change something you essentially have to delete the service
and re-create it unless you want to use the GUI. The recent addition of
being able to export the registry-based configuration to a script helps
significantly, but it's still putting the live config into the registry.
The process for SvcBatch seems to be fairly similar to that of procrun.
Nope. They are quite far apart.
Not really from a novice's perspective (i.e. mine). Perhaps from a
power-admin's perspective, SvcBatch is more powerful.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
