[Mondrian] Fwd: Re: xmla security header processing

Michele Rossi michele.rossi at gmail.com
Fri Jul 1 06:35:01 EDT 2011


hi Julian,
please find attached a more recent version of my xmla-over-olap4j work.
I've improved the connection pool management.
I now use one scheduled task to run "evict" on all the active pools.
It's better than using the default mechanism which would use a thread per
pool.

many thanks,
Michele

On 29 June 2011 17:51, Michele Rossi <michele.rossi at gmail.com> wrote:

> hi Julian,
> I've coded the connection pooling bit for the olap4j xmla servlet and I've
> tested it using Excel 2007.
>
> Basically I connect Excel 2007 to a local tomcat running the olap4j servlet
> and I configure the olap4j servlet to "talk" to another remote mondrian
> server using the XMLA Olap4j driver.
>
> Some of the pool parameters are configurable via the servlet configuration.
> You can change the "idle connections cleanup timeout"  (default is 5 mins)
> and the max number of connections to pool per user (default is 1)
>
> I had to create a map of "BasicDataSource" connection pools as it was the
> only way I could find to create authenticated connections correctly.
>
> I couldn't find any other way to tell the DBCP classes to group together
> internally connections made for the same user.
>
> I also had to create a "Delegating Olap Connection" because you need to
> return something that implements "OlapConnection" and at the same time does
> the right thing when you call "close" (returns the connection to the pool).
>
> I had a look at creating unit tests and that seems like a fairly
> substantial piece of work.
> The existing testing classes are based on the MondrianOlap4jServlet.
> I guess we should try to run all xmla tests against the new olap4j servlet
> too.
>
> Do you have any opinion on that?
>
> thanks,
> Michele
>
>
> On 22 June 2011 19:51, Julian Hyde <jhyde at pentaho.com> wrote:
>
>> **
>> Looks good. Please make sure there's a test for it (so we don't break it
>> accidentally).
>>
>>  ------------------------------
>> *From:* Michele Rossi [mailto:michele.rossi at gmail.com]
>> *Sent:* Wednesday, June 22, 2011 12:35 AM
>>
>> *To:* jhyde at pentaho.com; Mondrian developer mailing list
>> *Subject:* Re: [Mondrian] Fwd: Re: xmla security header processing
>>
>> hi Julian,
>> see below, thanks
>> Michele
>>
>>  <web-app>
>> <display-name>ARC XMLA Server</display-name>
>>
>> <servlet>
>> <servlet-name>xmla</servlet-name>
>> <servlet-class>mondrian.xmla.impl.Olap4jXmlaServlet</servlet-class>
>>  <init-param>
>>
>> <param-name>OlapDriverUsePreConfiguredDiscoverDatasourcesResponse</param-name>
>> <param-value>true</param-value>
>> </init-param>
>>  <init-param>
>> <param-name>OlapDriverDiscoverDatasources.dataSourceName</param-name>
>> <param-value>Proxy to Mondrian Foodmart</param-value>
>> </init-param>
>>  <init-param>
>>
>> <param-name>OlapDriverDiscoverDatasources.dataSourceDescription</param-name>
>> <param-value>Just a proxy to another mondrian xmla server</param-value>
>> </init-param>
>>  <init-param>
>> <param-name>OlapDriverDiscoverDatasources.url</param-name>
>> <param-value>http://192.168.151.88:6080/xmla/xmla</param-value>
>> </init-param>
>>  <init-param>
>> <param-name>OlapDriverDiscoverDatasources.dataSourceInfo</param-name>
>> <param-value>Proxy to Foodmart</param-value>
>> </init-param>
>>  <init-param>
>> <param-name>OlapDriverDiscoverDatasources.providerName</param-name>
>> <param-value>Proxy to mondrian xmla server</param-value>
>> </init-param>
>>  <init-param>
>> <param-name>OlapDriverDiscoverDatasources.providerType</param-name>
>> <param-value>TDP</param-value>
>> </init-param>
>>  <init-param>
>> <param-name>OlapDriverDiscoverDatasources.authenticationMode</param-name>
>> <param-value>Unauthenticated</param-value>
>> </init-param>
>>
>> [.........]
>>
>> On 21 June 2011 23:26, Julian Hyde <jhyde at pentaho.com> wrote:
>>
>>> **
>>> I could only see a boolean parameter:
>>>
>>> <init-param>
>>>
>>> <param-name>OlapDriverUsePreConfiguredDiscoverDatasourcesResponse</param-name>
>>>   <param-value>true</param-value>
>>> </init-param>
>>>
>>> Where's the XML?
>>>
>>>  Michele wrote:
>>>
>>> the configuration is in the web.xml, see attached screenshot.
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20110701/f897ecc3/attachment.html 


More information about the Mondrian mailing list