| Mattias Abrahamsson 2004-01-19, 2:55 pm |
| Hi all,
We are basing our infrastructure architecture on an edge server/http
server/was/portal server configuration without using the cloning features of
WAS. The topology we are aiming for is very similar to a multiple domain
topology
(http://www-3.ibm.com/software/webse...infocenter/inde
x.html) but without the clones for each domain. The reasons for this setup
are many (transaparent application upgrades without downtime, the ability to
switch modes from production to test on seperate servers, failover and
loadbalancing by edge components and more).
The only thing that is unclear and on which IBM (at least the persons I have
talked to) can't provide a good answer to is how to share information
between the portal instances (i.e. the application data for WPS in the
topology described in the link above).
I believe that at least the WMS database can and should be shared among the
portal instances since the user information needs to be shared among all
portal instances (the WMS database is really only another user repository,
exactly as LDAP or any custom repositories). This is how it is handled in a
cloned environment I beleive. Am I correct in my assumptions?
How can we setup the other databases and which should and can be shared
among instances? Do the WPS database store information that needs to be
shared among instances, likewise with the personalization databases. We have
no need or desire to share the WAS databases.
We understand that all portal instances sharing a database schema needs to
be the same level (e.g. 4.2) since different levels of the portal can
require schema changes. The downtime for a portal upgrade (from 4.2 to 5 for
an example) is acceptable.
Do anyone have any experience with a similar setup?
Thanks a advance!
Regards,
Mattias Abrahamsson
|