> From: André Warnier [mailto:a...@ice-sa.com]
> Subject: Re: TLS configuration with multiple web apps
> Maybe also to point out a side-effect of multiple connectors
> (and/or multiple tomcats) :
> it also means that each site/application would need a different
> port numbe
Maybe also to point out a side-effect of multiple connectors (and/or multiple tomcats) :
it also means that each site/application would need a different port number also.
Jamie wrote:
Hi Mark
Thanks for the clarification. Makes sense. Since ISP's are typically
cost sensitive, each instance s
Hi Mark
Thanks for the clarification. Makes sense. Since ISP's are typically
cost sensitive, each instance should consume a minimal amount of
resources.. i.e. memory footprint, etc. Is there alot extra overhead in
the architecture you describe?
Jamie
On 2010/08/30 6:02 PM, Mark Thomas wrote
> From: Mark Thomas [mailto:ma...@apache.org]
> Subject: Re: TLS configuration with multiple web apps
> To do what you want to do sounds like you'll need one
> connector per webapp which equates to one service +
> connector + engine + host per web app.
Or perhaps one Tomc
On 30/08/2010 16:58, Jamie wrote:
> Hi There
>
> Our deployment of Tomcat has several web applications, each with their
> own cert store. Each web app has a GUI for creating cert requests and
> importing certs. we need to configure Tomcat's TLS capability such that
> it will authenticate with each
