Hi Ron,
Thanks a lot for the clarification. When we customize the
theme and portal page layout in the jet-speed, all that is Jetspeed specific.
If I have to move the application to another portal server , I need to do there
for that portal server.
Thanks,
Alok
-----Original Message-----
From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Sent: Monday, July 06, 2009 5:49 AM
To: Jetspeed Users List
Subject: Re: Can I have each portlet in different war
Alok Jain wrote:
> Hi Ron,
> Can you please tell me one thing. In my case I am going to package
> the portlets in different war files as per the features. So my question is
> 1) when I deploy these war files in the portal server, do I need SSO
> integration if
> I need to authenticate user in all of the WARs. Assuming all the war files
> are deployed in the same tomcat.
>
No. We have our application broken up into many war files (webapps) for
ease of development but they are all part of one unified portal and
authentication is done at the portal level. If the portlet needs to know
anything about the current user, it can get the session context from
Jetspeed and find out all about the user or find out that the session is
still anonymous if the user has not logged in.
Portlet webapps are never called directly from a browser. They are
called by Jetspeed as it tries to assemble a page for a user who has
made a request. If the portlet has any interest in the profile of the
user on whose behalf the request is being made it has to ask Jetspeed.
If the portlet wants to know any information that was in the request
from the browser, it has to ask Jetspeed.
> 2) when I deploy these war files in the portal server, do I need SSO
> integration if
> I need to authenticate user in all of the WARs. Assuming all the war files
> are deployed in different tomcat servers.
>
>
Not likely. I can not think how SSO could be used in this case but I am
sure that there is some odd-ball situation.
There are a number of better ways to do this. You can use Web Services
or other remoting methods to scale your app onto more than one server.
There is also Web Services for Portlets. We are using Web Services in
one of our current portals.
The authentication for the Web Service is done as the request level in
this case (portlet on server A is permitted to call web service X on
server B). The inter-service communication must use messages that
contain enough information for the service to know what the caller wants
(get me customer 100010's last order). The service does not need to know
on whose behalf the portlet is requesting the info. In my example it
could be customer 100010 who is logged in or it could be the a customer
service rep or accounting department using the portal.
> Thanks,
> Alok.
>
>
> -----Original Message-----
> From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
> Sent: Sunday, July 05, 2009 4:51 PM
> To: Jetspeed Users List
> Subject: Re: Can I have each portlet in different war
>
> The web pages in a portal contains a selection of portlets regardless
> of how you package up the webapps and once you are connected to a
> session you share the authentication and authorization for your session.
> The portal page is selected based on your profile. The content of the
> page is assembled by Jetspeed based on your PSML files.
>
> SSO is used to gain access to other people's web sites.
>
> Ron
>
>
> Alok Jain wrote:
>
>> Hi,
>> Thanks for the reply. Also can you please confirm that I need to
>> integrate SSO like CAS with Jetspeed for the
>> Seamless authentication of the users across all the web-apps.
>>
>>
>> Thanks,
>> Alok
>>
>> -----Original Message-----
>> From: Ate Douma [mailto:a...@douma.nu]
>> Sent: Thursday, July 02, 2009 12:50 AM
>> To: Jetspeed Users List
>> Subject: Re: Can I have each portlet in different war
>>
>> Alok Jain wrote:
>>
>>
>>> Hi,
>>> Can I have each portlet packaged in a different WAR and
>>> deployed in the same portal server.
>>>
>>>
>> Sure, no problem.
>> The portal maintains a registry through which webapp (WAR) a portlet is
>> deployed.
>> One think to keep in mind however is that portlets bundled in one webapp do
>> have the advantage that they can share the same servlet session
>> and portlet session (APPLICATION_SCOPE). If you don't need that, deploying
>> all of them in separate webapps gives you the benefit of a very
>> fine-grained release/deployment life-cycle.
>>
>>
>>
>>> Thanks,
>>> Alok.
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
>> For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
>> For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
> For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
> For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
