The idea to disable the catalog schema is not good at all. This is why you get the error with XMLA DataSource cannot be found. Try to use the binary from download and re-install it.
If I use the JPivot XMLA support in Mondrian it properly runs and I'm able to see the simple pivot table. If I hit http://localhost:8083/mondrian/xmla in the browser directly it says GET isn't supported as it should I suppose.
Thanks for the help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Connecting to Mondrian, an open-source OLAP (Online Analytical Processing) server, involves several steps to ensure seamless integration with your data sources and client applications. First, you'll need to install Mondrian on a compatible server environment, such as Apache Tomcat. Once installed tex9.net Nintendo, configure the Mondrian properties file to define the connection parameters to your database, specifying details like the JDBC URL, database driver, username, and password. Next, you'll create an XML schema file that outlines the structure of your OLAP cube, including dimensions, measures, and hierarchies.
Last edit: santinofreeplay 2024-06-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Connecting to Mondrian involves engaging with the revolutionary artistic vision of Piet Mondrian, a pioneer of abstract art and the De Stijl movement. His work is characterized by bold, geometric compositions featuring primary colors, straight lines, and a grid-like structure, reflecting his pursuit of universal harmony and balance. Embracing Mondrian's principles invites a deeper exploration of abstraction and minimalism, whether in visual art, design, or architecture. His approach transcends aesthetics, offering a framework for interpreting order in a seemingly chaotic world. Whether through creating art inspired by his style or analyzing his masterpieces Visit Website, connecting to Mondrian is a journey into the essence of modernism.
Last edit: carputech 2024-11-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It looks like the issue may be with how the provider is surfacing the schema definitions, since Excel is very particular about catalogs and data source names. I ran into a similar challenge when validating outputs from a cube connection against external references, like checking a dataset that included the saltgrass menu with prices, and the key was making sure the schema entries were exposed consistently. You might want to double-check the data source definitions and try another XMLA client besides JPivot to confirm whether the problem is in the provider itself or in how Excel interprets the connection.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello there, I tried to use the OLEDB provider to talk to a Mondrian cube,
the example one FoodMart. I'm getting two kinds of problems:
If I use the default binary version of the provider, Excel 2013
complains about not being able to find tables in the data source.
Then I built from source and disabled the line:
//SCHEMA_ENTRY( DBSCHEMA_CATALOGS , ....
After this point I get further by making an XMLA call, but it always comes
back with an error saying that the XMLA DataSource cannot be found.
I can confirm that I can open and browse the mondrian cube using JPivot
XMLA, like this:
http://localhost:8083/mondrian/testpage.jsp?query=xmla
Any ideas?
The idea to disable the catalog schema is not good at all. This is why you get the error with XMLA DataSource cannot be found. Try to use the binary from download and re-install it.
There is a page here describing how to connect
http://sourceforge.net/p/xmlaconnect/wiki/Mondrian:%20Create%20Connection/
In your case the location should be
http://localhost:8083/mondrian/xmla
and there is no need for user/password.
Questions:
Hi thanks for the quick response!
For example, I have this configuration in xmla.jsp:
<jp:xmlaquery id="user-content-query01" uri="http://localhost:8083/mondrian/xmla" datasource="Provider=Mondrian;DataSource=MondrianFoodMart;" catalog="FoodMart"></jp:xmlaquery>
If I use the JPivot XMLA support in Mondrian it properly runs and I'm able to see the simple pivot table. If I hit http://localhost:8083/mondrian/xmla in the browser directly it says GET isn't supported as it should I suppose.
Thanks for the help!
Sorry the xmla.jsp config never came out I guess because it looks like html sourceforge ate it. Here it is without the html tags:
id="query01"
uri="http://localhost:8083/mondrian/xmla"
dataSource="Provider=Mondrian;DataSource=MondrianFoodMart;"
catalog="FoodMart"
I got it to work! I upgraded to Mondrian 3.4 and it's working now without issues. Thanks for the help.
Connecting to Mondrian, an open-source OLAP (Online Analytical Processing) server, involves several steps to ensure seamless integration with your data sources and client applications. First, you'll need to install Mondrian on a compatible server environment, such as Apache Tomcat. Once installed tex9.net Nintendo, configure the Mondrian properties file to define the connection parameters to your database, specifying details like the JDBC URL, database driver, username, and password. Next, you'll create an XML schema file that outlines the structure of your OLAP cube, including dimensions, measures, and hierarchies.
Last edit: santinofreeplay 2024-06-30
Connecting to Mondrian involves engaging with the revolutionary artistic vision of Piet Mondrian, a pioneer of abstract art and the De Stijl movement. His work is characterized by bold, geometric compositions featuring primary colors, straight lines, and a grid-like structure, reflecting his pursuit of universal harmony and balance. Embracing Mondrian's principles invites a deeper exploration of abstraction and minimalism, whether in visual art, design, or architecture. His approach transcends aesthetics, offering a framework for interpreting order in a seemingly chaotic world. Whether through creating art inspired by his style or analyzing his masterpieces Visit Website, connecting to Mondrian is a journey into the essence of modernism.
Last edit: carputech 2024-11-26
It looks like the issue may be with how the provider is surfacing the schema definitions, since Excel is very particular about catalogs and data source names. I ran into a similar challenge when validating outputs from a cube connection against external references, like checking a dataset that included the saltgrass menu with prices, and the key was making sure the schema entries were exposed consistently. You might want to double-check the data source definitions and try another XMLA client besides JPivot to confirm whether the problem is in the provider itself or in how Excel interprets the connection.