https://issues.apache.org/bugzilla/show_bug.cgi?id=50949
Summary: Allow configuration of service name, AJP port, server
port.
Product: Tomcat 7
Version: trunk
Platform: PC
Status: NEW
Severity: normal
Priority: P2
Component: Packaging
AssignedTo: dev@tomcat.apache.org
ReportedBy: guido.leend...@invantive.com
I am using Tomcat to deploy a software application. Some customers run Windows
and want Tomcat to run servlets.
For this, we use the installer provided on the site. In two situations, the
standard installer does not work well enough:
1. The customer wants two installations on the same server, and therefore needs
two services. For instance, one for development/test/acceptance and one for
production. This can be achieved but requires manual interaction instead of
just next, next, enter something finish.
2. The customer installs software for Sonicwall, also based on Tomcat. They
include the standard installer and just overwrite any current service name for
Tomcat 6 or 7.
To solve these deployment issues, I would like to be able to configure:
* The name and code of the Windows service to be created. For my own
installations, I can then use something different of the standard name. That
avoids that less intelligent installers hijack the service later, leading to a
service request to me.
* The port for AJP and server. Currently, you can enter the HTTP port. That is
very handy when for instance IIS is also running on the same machine. But when
two Tomcat instances are running, the AJP and server port in a standard
installation must also differ.
I have looked into res\tomcat.nsi. It seems to be responsible for the creation
of the service and files.
In trunk around line 202 and 306 I see that the service name and display name
are currently hardcoded. That would require some form of adaption.
The additional ports can probably be handled by Function configure.
I also saw that stuff is registered in the registry under SOFTWARE\Apache
Software Foundation\Tomcat\@VERSION_MAJOR_MINOR@. That probably would require
adaptation too to allow multiple installs without interfering them with each
other. I do not know to handle that.
For the two scenarios, I think I can ask one customer to invest some amount of
money, because in the long run it would save him the effort to learn
administrator to use tomcat*.exe with options such as //ms.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
