Johnny Kewl wrote:
Hi Jacob..... thanks
There is tons of literature on it, but boy its like looking for a
needle in a hay stack actually finding one that clearly uses all this
technology
Portal Architecture is heavily used by teaching institutions to solve a
number of speciffic problems (not always successfully i might add).
When a company has 10 different web sites all with different styles and
layouts for various legacy reasons and they cant be change, a portal can
bring all sites into it, one site per tab, with a consistent corporate
image.
When workflow of your staff involves interacting with multiple different
systems, (ie logging in and out of different systems). A portal can wrap
the systems, provide single sign on (using a number of different
mechanisms) and present each step of the workflow on a single page, or
over a series of pages.
In a big company, When workflow of your staff crosses software/websites
from different departments (who do their own programming and want to do
things "their way" and dont work together for political reasons) you can
make them simply write portlets, and let the portal team control how the
departments applications look and feel and work.
I could go on for quite some time but I don't have time to write an
essay, these are probably some of the most important benefits. If you
are a small company the concept of a portlet is still helpful but not as
useful as to a big company with a large number of sites.
-jacob
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
