Hi Johnny,
If I understand your the first part of your email correctly, you try - with
the http server as a front-end, to serve up multiple instance.
E.g.
www.site1.org to deliver instance1 (with its specific ports), and
www.site2.org to deliver instance2 (with its specific ports).
If that is what you want to achieve, please have a look at the various
configuration documents of the http server. But in general, serving
multiple instances when having set different ports per instance is easily
done. You don't need to do anything else beyond the setting of the ports
and configuring the http server.
Your second part of your email is about serving specific applications to
the specific customers through the front end (again if I understand it
correctly). For this you do not need to multiple instances. There is a
feature called multi-tenancy which enables you to define access to that
specific application while sharing the underlying supporting components.
In a multi-tenancy setup you can define as a database entry which tenant is
associated to the specific application. Truth be told, I haven't seen this
in action so I cannot share such experience.
If you need to serve data/content to the unknown user (anonymous or open
access), you undertake additional steps. But again, you don't need multiple
instances for this. Unless other requirements dictate otherwise, of course.
Best regard,
Pierre Smits
*ORRTIZ.COM <
http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
Locked
