You can find docs biserver-ce\tomcat\webapps\pentaho\docs\ Changing the Java VM Memory Limits If you are running out of memory even though your server has a lot of RAM, you probably need to increase the resources allocated to the JRE instance that runs the Pentaho software you're trying to improve performance on. Adjusting the memory limit is an easy configuration change to make, but the instructions differ depending on the client tool or Web application server you're using. Refer only to the sections below that apply to your situation. Note: If you are running multiple Pentaho programs concurrently, the sum of their JVM maximum memory limits must not exceed the available RAM minus system overhead. Increasing Memory Limits on Microsoft Windows with a Graphical Installation By default, Tomcat has a relatively low memory allotment. This can cause out-of-memory errors in the BA Server fromtime to time. The below instructions will explain how to increase the mem
In this week I integrate one of the most useful feature i.e. CAS (Single Sign on) with the help my collegue and online user community . So with my boss’ blessing, I decided to document what I had to do to make this work in the spirit of giving back to the community. Plus with the rising awareness of the benefits of BI even for small to medium corporations, I have no doubt that this information would be useful for someone somewhere. The need 1) CAS Server 2) Pentaho BI 3.x server (Community Edition) 3) Install certificate IMPLEMENTATION OF CAS CLIENT IN PENTAHO BI SERVER 1) \biserver-ce\pentaho-solutions\system\applicationContext-spring-security.xml make changes in applicationContext file for CAS Client. and add following jars in biserver-ce\tomcat\webapps\pentaho\WEB-INF\lib folder 1) spring-security-cas-client-2.0.5.RELEASE.jar 2) cas-client-core-3.1.10.jar After added jars and configuration in applicationContext file then install certificate step-1) download
I had created lots of reports and published on Pentaho BI server. One day my Technical team told me our database server is going to changed. I am really very get tense now I have to change database details in every report that is very hectic and silly work. So that time I have in mind "Don't hardcode host names, use JNDI", my best friend google always help me & found two blogs that really very help to configure JNDI (in Pentaho called as Pentaho Datasources). JDNI is a technique to hold database connections outside of the report definition. By holding this information in a central spot, you only have to change one place and all your reports get updated. The JNDI stored connection information is stored on the computer where your report runs. This also allows you to have separate definitions based on where the report runs. Your report designer can access a local copy of your production database, while your production server uses the real database server.
Comments
Post a Comment