You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Elif Guner <el...@gmail.com> on 2006/11/23 23:04:19 UTC
multiple portals
Hi,
I've read the threads on hosting multiple portals. I have a couple of
questions regarding the same subject.First of all, if I am to use
subsites, is it possible to have different roles for each subsite? For
example different admin/manager/guest per subsite 1 and different ones
for subsite 2? (I couldn't find an answer on this one)
Secodly, instead of using subsites, is it all right to have portals'
data in different folders and define new roles for each folder? (for
example define admin1 and this role can only access folder1 with admin
privileges). Depending on which url is requested the user will be
redirected to the folder in which the portal data is contained.
Thanks in advance,
Elif
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: multiple portals
Posted by dee factorial <de...@gmail.com>.
has this solution been implemented yet, if not how can I implement it,
I've read the documentation
http://portals.apache.org/jetspeed-2/guides/guide-profiler.html
http://svn.apache.org/repos/asf/portals/jetspeed-2/trunk/design-docs/src/profiler/J2-page-manager-profiling.sxw
http://donaghy.blogspot.com/2006_09_01_donaghy_archive.html#115717649154931733
is there anymore documentation on the subsites ?
my usecase sinario is I have two websites, lets call them http://one.com and
http://two.com I would have one.com point to subsite and two.com point to
two.com the userbase would be for both websites but the user would see
whichever homepage they originaly requested ie, if they went to one.com they
would see the subsite homepage if they went to two.com they would see
subsite2 homepage. but they would only have to register once on either
website to get access to both. each website would have its own template and
set of psml files.
It would also be nice to still retain all of the profiling features of a
full blown jetspeed website like the users/roles/groups.
Is it currently possible to implement this with the current J2-dev version
of jetspeed. if not what do I have to learn or where do I have to look to
implement it myself.
Thanks,
Dominique
On 11/28/06, Elif Guner <el...@gmail.com> wrote:
>
> Hi David,
>
> In my case it is like http://somecompany.com, http://somecompany2.com,
> http://somecompany3.com
> I'm wondering if you'd consider this situation as well?
>
> Thanks...
> Elif
>
>
>
>
> On 11/28/06, David Sean Taylor <da...@bluesunrise.com> wrote:
> > Bhaskar wrote:
> > >
> > > Hi David,
> > >
> > > Can you bit explain, how this mapping to be done, like
> > > http://employees.somecompany.com/jetspeed/ -> maps to employee-subsite
> > > http://customers.somecompany.com/jetspeed/ -> maps to customer-subsite
> > > http://partners.somecompany.com/jetspeed/ -> maps to partner-subsite
> > >
> > > I looked at the documentation, didn't get it through.
> > >
> > This mapping does not currently exist. I was proposing writing and
> > contributing a new profile resolver based on the host string.
> > The idea is we would have a new profiling rule that used this resolver
> > as its first criteria. It could parse the host up, find the substring up
> > to the first ".", and use that to map to a subsite. Thus all requests
> > going to employees.* would then map to the "employee" subsite.
> > I would combine this with role-based declarative security, so that
> > customers would get access denied exceptions if they tried to access a
> > URL for employees, for example.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> > For additional commands, e-mail: jetspeed-user-help@portals.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
Re: multiple portals
Posted by Elif Guner <el...@gmail.com>.
Hi David,
In my case it is like http://somecompany.com, http://somecompany2.com,
http://somecompany3.com
I'm wondering if you'd consider this situation as well?
Thanks...
Elif
On 11/28/06, David Sean Taylor <da...@bluesunrise.com> wrote:
> Bhaskar wrote:
> >
> > Hi David,
> >
> > Can you bit explain, how this mapping to be done, like
> > http://employees.somecompany.com/jetspeed/ -> maps to employee-subsite
> > http://customers.somecompany.com/jetspeed/ -> maps to customer-subsite
> > http://partners.somecompany.com/jetspeed/ -> maps to partner-subsite
> >
> > I looked at the documentation, didn't get it through.
> >
> This mapping does not currently exist. I was proposing writing and
> contributing a new profile resolver based on the host string.
> The idea is we would have a new profiling rule that used this resolver
> as its first criteria. It could parse the host up, find the substring up
> to the first ".", and use that to map to a subsite. Thus all requests
> going to employees.* would then map to the "employee" subsite.
> I would combine this with role-based declarative security, so that
> customers would get access denied exceptions if they tried to access a
> URL for employees, for example.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: multiple portals
Posted by Frank Stalherm <ma...@goodgulf.net>.
Hi David,
two questions:
Why would you limit this to the sub domain?
Am I right in assuming that I could implement such a resolver and add it
to the resolvers in assembly/profiler.xml?
Thanks,
Frank
David Sean Taylor wrote:
> Bhaskar wrote:
>>
>> Hi David,
>>
>> Can you bit explain, how this mapping to be done, like
>> http://employees.somecompany.com/jetspeed/ -> maps to employee-subsite
>> http://customers.somecompany.com/jetspeed/ -> maps to customer-subsite
>> http://partners.somecompany.com/jetspeed/ -> maps to partner-subsite
>>
>> I looked at the documentation, didn't get it through.
>>
> This mapping does not currently exist. I was proposing writing and
> contributing a new profile resolver based on the host string.
> The idea is we would have a new profiling rule that used this resolver
> as its first criteria. It could parse the host up, find the substring
> up to the first ".", and use that to map to a subsite. Thus all
> requests going to employees.* would then map to the "employee" subsite.
> I would combine this with role-based declarative security, so that
> customers would get access denied exceptions if they tried to access a
> URL for employees, for example.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: multiple portals
Posted by David Sean Taylor <da...@bluesunrise.com>.
Bhaskar wrote:
>
> Hi David,
>
> Can you bit explain, how this mapping to be done, like
> http://employees.somecompany.com/jetspeed/ -> maps to employee-subsite
> http://customers.somecompany.com/jetspeed/ -> maps to customer-subsite
> http://partners.somecompany.com/jetspeed/ -> maps to partner-subsite
>
> I looked at the documentation, didn't get it through.
>
This mapping does not currently exist. I was proposing writing and
contributing a new profile resolver based on the host string.
The idea is we would have a new profiling rule that used this resolver
as its first criteria. It could parse the host up, find the substring up
to the first ".", and use that to map to a subsite. Thus all requests
going to employees.* would then map to the "employee" subsite.
I would combine this with role-based declarative security, so that
customers would get access denied exceptions if they tried to access a
URL for employees, for example.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
RE: multiple portals
Posted by Bhaskar <br...@platformexchange.com>.
Hi David,
Can you bit explain, how this mapping to be done, like
http://employees.somecompany.com/jetspeed/ -> maps to employee-subsite
http://customers.somecompany.com/jetspeed/ -> maps to customer-subsite
http://partners.somecompany.com/jetspeed/ -> maps to partner-subsite
I looked at the documentation, didn't get it through.
Thanks
Bhaskar
-----Original Message-----
From: David Sean Taylor [mailto:david@bluesunrise.com]
Sent: Tuesday, November 28, 2006 1:06 PM
To: Jetspeed Users List
Subject: Re: multiple portals
Elif Guner wrote:
> Thanks a lot David... I have one more simple question (might be a
> silly one after all that explanation of yours) regarding subsites.
> What I understand is that an anonymous user is first directed to the
> root. He's directed to the subsite depending on the profiling rule on
> that particular user's role, is that right? (So in order to forward
> his request to the subsite he must be logged in? Or using the
> subsite-role-fallback-home rule can I also map anonymous users to a
> subsite?)
> Would it be possible to implement my own profiling rule which
> redirects users to subsites depending on the requested URL? Is there
> any tutorials on how to write a profile rule?
>
No tutorials available on this subject that i know of.
Your use case reminds me of a profiling rule based on the host I've been
thinking about. Sorry if Im going off topic, but something like:
http://employees.somecompany.com/jetspeed/ -> maps to employee-subsite
http://customers.somecompany.com/jetspeed/ -> maps to customer-subsite
http://partners.somecompany.com/jetspeed/ -> maps to partner-subsite
I think this would work regardless of if you are logged on or not.
We don't yet have a resolver to parse the host, a general resolver to
look at the host should be easy enough
assume you have read the docs here:
http://portals.apache.org/jetspeed-2/guides/guide-profiler.html
Just had a look myself. The docs are not up-to-date. Philip contributed
an IP address resolver that is not documented here
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: multiple portals
Posted by David Sean Taylor <da...@bluesunrise.com>.
Elif Guner wrote:
> Thanks a lot David... I have one more simple question (might be a
> silly one after all that explanation of yours) regarding subsites.
> What I understand is that an anonymous user is first directed to the
> root. He's directed to the subsite depending on the profiling rule on
> that particular user's role, is that right? (So in order to forward
> his request to the subsite he must be logged in? Or using the
> subsite-role-fallback-home rule can I also map anonymous users to a
> subsite?)
> Would it be possible to implement my own profiling rule which
> redirects users to subsites depending on the requested URL? Is there
> any tutorials on how to write a profile rule?
>
No tutorials available on this subject that i know of.
Your use case reminds me of a profiling rule based on the host I've been
thinking about. Sorry if Im going off topic, but something like:
http://employees.somecompany.com/jetspeed/ -> maps to employee-subsite
http://customers.somecompany.com/jetspeed/ -> maps to customer-subsite
http://partners.somecompany.com/jetspeed/ -> maps to partner-subsite
I think this would work regardless of if you are logged on or not.
We don't yet have a resolver to parse the host, a general resolver to
look at the host should be easy enough
assume you have read the docs here:
http://portals.apache.org/jetspeed-2/guides/guide-profiler.html
Just had a look myself. The docs are not up-to-date. Philip contributed
an IP address resolver that is not documented here
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: multiple portals
Posted by Elif Guner <el...@gmail.com>.
Thanks a lot David... I have one more simple question (might be a
silly one after all that explanation of yours) regarding subsites.
What I understand is that an anonymous user is first directed to the
root. He's directed to the subsite depending on the profiling rule on
that particular user's role, is that right? (So in order to forward
his request to the subsite he must be logged in? Or using the
subsite-role-fallback-home rule can I also map anonymous users to a
subsite?)
Would it be possible to implement my own profiling rule which
redirects users to subsites depending on the requested URL? Is there
any tutorials on how to write a profile rule?
Thanks again...
Elif
On 11/26/06, David Sean Taylor <da...@bluesunrise.com> wrote:
> Elif Guner wrote:
> > Hi,
> >
> > I've read the threads on hosting multiple portals. I have a couple of
> > questions regarding the same subject.First of all, if I am to use
> > subsites, is it possible to have different roles for each subsite? For
> > example different admin/manager/guest per subsite 1 and different ones
> > for subsite 2? (I couldn't find an answer on this one)
>
> No, that isn't possible currently. I do like that idea though.
> It reminds me that in a future release I'd like to see subsites
> associated with domains, and then domains are associated with different
> roles, users.
>
> There are two sample subsite profiling rules that come with the portal
> Look at these for examples of how to use a profile to map users to
> different subsites. The subsite-role-fallback-home rule is a
> role-fallback rule that maps users to always lookoff the "subsite-root"
> subsite.
>
> >
> > Secodly, instead of using subsites, is it all right to have portals'
> > data in different folders and define new roles for each folder? (for
> > example define admin1 and this role can only access folder1 with admin
> > privileges). Depending on which url is requested the user will be
> > redirected to the folder in which the portal data is contained.
> >
>
> You can achieve some of the effects by using roles.
> With a role-fallback profiling rule, the visibility of pages are
> expanded. By using page security constraints, you can limit the
> visibility of pages.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: multiple portals
Posted by David Sean Taylor <da...@bluesunrise.com>.
Elif Guner wrote:
> Hi,
>
> I've read the threads on hosting multiple portals. I have a couple of
> questions regarding the same subject.First of all, if I am to use
> subsites, is it possible to have different roles for each subsite? For
> example different admin/manager/guest per subsite 1 and different ones
> for subsite 2? (I couldn't find an answer on this one)
No, that isn't possible currently. I do like that idea though.
It reminds me that in a future release I'd like to see subsites
associated with domains, and then domains are associated with different
roles, users.
There are two sample subsite profiling rules that come with the portal
Look at these for examples of how to use a profile to map users to
different subsites. The subsite-role-fallback-home rule is a
role-fallback rule that maps users to always lookoff the "subsite-root"
subsite.
>
> Secodly, instead of using subsites, is it all right to have portals'
> data in different folders and define new roles for each folder? (for
> example define admin1 and this role can only access folder1 with admin
> privileges). Depending on which url is requested the user will be
> redirected to the folder in which the portal data is contained.
>
You can achieve some of the effects by using roles.
With a role-fallback profiling rule, the visibility of pages are
expanded. By using page security constraints, you can limit the
visibility of pages.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org