OLAP connection Cube List empty
26 July, 2010
Here is a summary of what I am trying to do as far as OLAP is concerned:
I ran yellowfin on port 8088 on my machine and I started a tomcat which has mondrian olap running on port 8085. I can see my cubes and the data by directly logging on to the tomcat instance. I need some help in viewing the data from yellowfin.
Here are the steps that I have followed:
1. Creating a data source
Connection Method: XMLA OLAP
Database URL: http://localhost:8085/mondrian/xmla
Data Source: Provider=mondrian;
Catalog: /WEB-INF/queries/Devices.xml
Username: admin
Password: admin
2. Test the connection
It passes fine
3. Add view
Author a view Using: OLAP cube
Data source: MYOLAP
Cube: This list is empty !!!
Is there some kind of tracing I can enable to see what's going on the server. Please advise on how to resolve this.
I ran yellowfin on port 8088 on my machine and I started a tomcat which has mondrian olap running on port 8085. I can see my cubes and the data by directly logging on to the tomcat instance. I need some help in viewing the data from yellowfin.
Here are the steps that I have followed:
1. Creating a data source
Connection Method: XMLA OLAP
Database URL: http://localhost:8085/mondrian/xmla
Data Source: Provider=mondrian;
Catalog: /WEB-INF/queries/Devices.xml
Username: admin
Password: admin
2. Test the connection
It passes fine
3. Add view
Author a view Using: OLAP cube
Data source: MYOLAP
Cube: This list is empty !!!
Is there some kind of tracing I can enable to see what's going on the server. Please advise on how to resolve this.
I have installed Mondrian 2.1 and got a cube working in Yellowfin. I think the problem you're having may be in the name of the Data Source. You said you're using "Provider=mondrian;", I think you need to add "DataSource=xxx" to the end of it.
In my datasources.xml file (under mondrian/WEB-INF) I had to set up the source using Provider=Mondrian;DataSource=testsource;
and then use "Provider=Mondrian;DataSource=testsource;" as the data source name in yellowfin. For some reason it seems that the name must be in this format to get the XMLA connections working properly.
FWIW before I set the data source name above, I could connect ok to the mondrian instance and run the jpivot examples, but the xmla features didn't work properly.
Hope this helps you get it working.
In my datasources.xml file (under mondrian/WEB-INF) I had to set up the source using Provider=Mondrian;DataSource=testsource;
and then use "Provider=Mondrian;DataSource=testsource;" as the data source name in yellowfin. For some reason it seems that the name must be in this format to get the XMLA connections working properly.
FWIW before I set the data source name above, I could connect ok to the mondrian instance and run the jpivot examples, but the xmla features didn't work properly.
Hope this helps you get it working.
I've been trying to set up a datasource to a SAP BW 3.5 system in YellowFin. For this I use the standard XML/A interface of BW, which uses HTTP authentication. Creating the datasource in YellowFin works just fine, and I can set up a view without any problems. But when it comes to creating a report on the view, in the very last step (the preview) I get an error message about a processing error, and the java console displays a SOAPException down in the JPivot library (it actually says that it received an HTTP 401, so I guess that the final display doesn't pass the credentials)
Did I miss something on the way, or is this normal behaviour?
Did I miss something on the way, or is this normal behaviour?
The 401 Error being generated is due to some kind of HTTP authentication that is required for the XML/A connection. Yellowfin should be compatible with SAP BW XML/A connections.
This type of authentication is not required for other XML/A sources - you may want to see if it is possible to disable the authentication in the SAP XML/A provider.
This type of authentication is not required for other XML/A sources - you may want to see if it is possible to disable the authentication in the SAP XML/A provider.