sbirney

Hi, take a look at the filterInvocationInterceptor in applicationContext-security.xml. It maps URL patterns to which roles are required, so if you want to use custom roles instead of ROLE_USER, you should update this to give appropriate access. Sam

This post got me wondering if there was a bug, so I tried some experiments with it. The last post is correct, that the mondrian cache is flushed with the following line of code, which is what the "Flush OLAP Cache" button does: mondrian.rolap.CachePool.instance().flush(); However, JPivot keeps its own (smaller) session based cache, so logging out after flushing the cache is necessary to clear your session if you have already loaded a particular analysis view in the current http session. And, as alluded to in another post, if aggregate tables are used, they might hide changes to base data. For example, I changed sales_fact_1997 in foodmart by multiplying unit_sales by 2, then I flushed the cache and logged out, but did not see the changes until I went back and disabled aggregate tables (and then flushing the cache and logging out again). If you are using aggregate tables, the proper thing to do would be to rebuild or update those when the underlying data has been updated. HTH, Sam

Hello, in applicationContext-security.xml, there is a bean called authenticationProcessingFilter, which handles the login page. It has a property called "defaultTargetUrl", whose value you can change to the URL for showing reports. Sam

I believe this is a bug with Spring webflow on some OS, and the workaround is to change hostname. Please see this post: http://www.jasperforge.org/index.php?option=com_joomlaboard&func=view&id=26919&catid=10

IE6 is notoriously slow at handling JavaScript, which is used somewhat in the JasperServer pages. I would not expect a factor of 10 though, is there a chance you have a slower network connection or other factors on the computer with IE6? Are some pages relatively slower than others? If you can identify a specific part of a specific page that is slow we may have a better chance of helping...

I looked further into the drill-through issue for parent-child hierachies, and it seems that the underlying problem is that mondrian generates a single SQL statement for drill-through. In the case of parent-child hierarchies without closure tables, there may be many SQL queries required, and JPivot would have to run these to collect all the child data. I filed a bug tracker on mondrian's sourceforge page.

i will post if i figure out the drill down problem, hopefully i can look at that in detail next week. for the XML/A JasperReport, look at the included sample- /analysis/reports/FoodmartSalesMondrianReport

hi tiger, thanks for the foodmart example, this will help us find the bug and fix it much quicker. as for the password changing feature, try setting this property to true in jasperserver-servlet.xml, then a link should appear on the login page- <property name="allowUserPasswordChange" value="false"/> sam

hi zxhjia, I noticed there was no way to turn on debugging to see the SQL statements for drill-through, which would have helped you in this case, so I added it and it will be in the next version of JasperSoft (2.0.1) coming out soon. I think your reasoning is probably correct, there may be a bug. Will you post the MDX you used to show this problem in foodmart? That will be very helpful because I have a foodmart database I can test and debug with. thanks, sam

hello. is there an error in the log when clicking to drill through on the third row of data? If so, please post it. If there is no error in the log, it is more likely to be about the data, but it could be a subtle bug. I wonder if it is coincidence that the one with negative numbers is showing empty on drill through. Maybe you could post the definition for this Expense measure from your schema xml file?

I think there should be a better solution for production usage, but if you are just trying it out, what if you put the DB2 license jars in a CLASSPATH environment variable?

Definitely. Performance will be better with tables or materialized views if the query is complicated or has lots of data...

I'm not sure if I understand your question. Using the JasperServer UI to make an OLAP connection is pretty easy. The hard part is designing your schema. Try using the JasperAnalysis Workbench for that: http://www.jasperforge.org/index.php?option=com_joomlaboard&Itemid=215&func=view&id=25164&catid=10

I'm not sure if I understand your question. Using the JasperServer UI to make an OLAP connection is pretty easy. The hard part is designing your schema. Try using the JasperAnalysis Workbench for that: http://www.jasperforge.org/index.php?option=com_joomlaboard&Itemid=215&func=view&id=25164&catid=10

We have tested that JasperAnalysis is I18N compatible, using a variety of different locales. but there are a few things to check on the data side: 1. your database should be created using UTF-8 encoding: CREATE DATABASE foo WITH ENCODING 'UTF8'; 2. with MySQL, this should also be reflected in the jdbc url, I'm not sure if this applies to postgres: jdbc:mysql://localhost/ji_i18n?useUnicode=true&characterEncoding=UTF-8 3. you must have the appropriate font in your browser. (I think you have this already if you see any umlauts, but just wanted to mention it)

you can try using these two lines in your mondrian.properties for the workbench: mondrian.foodmart.jdbcURL=jdbc:mysql://localhost:3307/foodmart3?user=root&password =XXX mondrian.jdbcDrivers=com.mysql.jdbc.Driver or, even easier, you can just set your JDBC connection settings in the workbench, under the Tools menu, then click Preferences. This is what I did, without editting mondrian properties. Once you use the schema in JS, you will need to create the metadata for a datasource and connection, as described in the user guide.

I'm afraid I can't speak to MS AS 2000 because I haven't tried it yet. But I do think the double-quoted uri is some configuration issue, rather than an issue in the code, since I ran into it when my server was not configured correctly, and then it went away and everything was working. Also, I can tell you that we have not modified any of the JPivot code which deals with XML/A, so perhaps if you have it working with a JPivot tag, then the error is with the XmlaConnection in your metadata repository, so make sure the Catalog, Provider, etc. are as Sherman mentioned, or whatever corresponds to the values in your JPivot tag that is working. Hope this helps some, wish I had more info, please post if you figure something out.

A few weeks ago I set up JA with MSAS 2005 and it did work. I ran into this same error where it said the Discover method was invalid for this URI. It turned out to be that I had not configured MSAS just right. I think it was because I was using msxisapi.dll instead of msmdpump.dll and it looks like you are doing the same thing. I went back and reconfigured the IIS virtual directory from scratch, being careful to follow these instructions EXACTLY: http://www.microsoft.com/technet/prodtechnol/sql/2005/httpasws.mspx Notice there is no mention of msxisapi.dll in this page, which apparently was only needed for MSAS 2000. The only extra step I had to do was to add a role to the Adventure Works database that gave permission for the guest user that I set up for anonymous access in IIS. I have not tried MSAS 2000, but I believe you still need to use the msmdpump.dll with that setup.

Try testing that your analysis services is set up correctly by hitting the url in your browser (use firefox because IE will display its own error page) and you should see something like this Code: <soap:Envelope xmlns:«»soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <soap:Fault xmlns="http://schemas.xmlsoap.org/soap/envelope/"> <faultcode>XMLAnalysisError.0xc10e0002</faultcode> <faultstring>Parser: The syntax for 'GET' is incorrect.</faultstring> <detail> <Error ErrorCode="3238920194" Description="Parser: The syntax for 'GET' is incorrect." Source="Unknown" HelpFile=""/> </detail> </soap:Fault> </soap:Body> </soap:Envelope>

There must be some error in the schema file... I would suggest loading it in the Workbench, which is the best way to edit schema files, and should give better error messages.

The snapshot of source on the SVN server hasn't been updated yet to be current with the 1.2.1 release of JasperServer. It should still compile, not sure why you are getting that error, but how about if you try getting and compiling the latest source download from: http://sourceforge.net/project/showfiles.php?group_id=162962&package_id=195243&release_id=498862

Hello, are you sure there is no error in jasperserver.log? Usually there is a stack trace in that file. If not, I would suggest trying to make the schema and query as simple as possible until they work, and then you can use the JPivot UI to edit the queries. The version of JPivot that ships with JapserServer is a compatible version, so at least that is not the problem.

datasources.xml is not used by JI. All the configuration for XML/A datasources is done by creating a XMLA Definition in the repository on the server. Then you can connect to this from iReport, or from an XMLA Connection on the same or another JI server. I'm not too knowledgeable about connecting with iReport, but I have tested this for the XMLA Connection method.

Hello, this is a relatively new feature, so it hasn't been well documented yet. The datasource in the XML/A connection must match the name of the catalog, so try Provider=Mondrian;DataSource=olapschema; if your catalog is named 'olapschema'. hope this helps.

I think I have seen this error when mysql is not running. Test if you can login to mysql directly, it needs to be started first. Sam