portals-jetspeed-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Sean Taylor <da...@bluesunrise.com>
Subject Re: portlet entity Editor
Date Wed, 07 Nov 2007 19:00:10 GMT

On Nov 7, 2007, at 8:30 AM, Mansour wrote:

> David Sean Taylor wrote:
>> On Nov 4, 2007, at 11:40 PM, Mansour wrote:
>>> Oops, the mail went to the public list. Not any private info yet.  
>>> We can discuss this publicly and get more inputs from other users.
>> OK
>>> Mansour wrote:
>>>> David, thank you for your help in this. I decided to exclude the  
>>>> public mailing list form my reply in order to feel free in  
>>>> giving info about what I am trying to do. Your last reply  
>>>> resolved big part of the problem, and I just need to make sure  
>>>> that I understand everything. Taking a real life example will  
>>>> help a lot.
>>>> Let's say I need to write a portlet "application" that contains  
>>>> few reports for a hotel system:
>>>> 1- moth to date (MTD) revenue.
>>>> 2-YTD revenue.
>>>> 3- sales.
>>>> 4- expenses.
>>>> 5- report of empty rooms.
>>>> 6-report of rooms to be cleaned.
>>>> 7-rooms need maintenance.
>>>> ...
>>>> This portlet application is to be hosted for few hotels on one  
>>>> "single" portal server.
>>>> For each hotel, I need to create an instance. And I need to set  
>>>> the DB connection and credentials and it should not be changed  
>>>> by any one else.
>> When you say instance, I think that term is confusing.
>> Basically you need a 1-1 relationship between a hotel and connection.
> The term instance is used in other portlet containers.
>>>> When the user logs in , she has the choice to add this instance  
>>>> to here page. She can add more than one instance and customize  
>>>> them. For example, a revenue manager may add an instance and  
>>>> using the edit mode she can configure this instance to show the  
>>>> YTD revenue report. She may add another instance and configure  
>>>> it to show the sales as well. The revenue manager has access to  
>>>> any type of report she wants. The cleaning person in the hotel  
>>>> should not view the expenses. She should only see the rooms to  
>>>> be cleaned and may be maintenances. The maintenance guy should  
>>>> not have access to the reports of empty rooms.
>>>> In this case I will create the number of reports I need (using  
>>>> BIRT and eclipse) and wrap them in a portlet application. and  
>>>> deploy it. Then I will customize the DB connection for each  
>>>> hotel in the global preference ??  so no one can change it. Am I  
>>>> right ?
>> Yes, that is correct.
> Great so, how can I do this for multiple hotel. I mean in the  
> global preferences there's only one DB connection string. As I  
> mentioned earlier I will create only one package and then  
> instantiate instances or entities. You said I need a 1-1  
> relationship hotel-connection ! What do you mean? And how?

I was talking about using the SSO component with the code example  
shown in the previous email
But when I say 1-1 relationship, I mean you add a SSO Record for each  
hotel, and then look up the connection string using the hotel name as  
a key

  credentials = sso.getCredentials(getSubject(), hotelName);

To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org

View raw message