Jump to content
We've recently updated our Privacy Statement, available here ×

marianol

Members
  • Posts

    729
  • Joined

  • Last visited

 Content Type 

Profiles

Forum

Events

Featured Visualizations

Knowledge Base

Documentation (PDF Downloads)

Blog

Documentation (Test Area)

Documentation

Dr. Jaspersoft Webinar Series

Downloads

Posts posted by marianol

  1. Can you show how are you connecting to RDS? And how the infrastructure looks like on AWS, did you use the provided Cloud Formation Templates?
    An elastic IP is not required to connect to RDS, I think that the issue you are running into has to do with the network infrastructure you have setup.

    Are you using VPC? Are you using the internal IPs in your security group?

  2. Wow, lots of questions :)

    #1) For performance related questions this wiki page is always a good start http://community.jaspersoft.com/wiki/jasperreports-server-performance-reference

    That will give you an overview on where the bottlenecks will be for a specific use case. Since there are so many moving parts (query time, fetch time, report execution, fill and export, etc) is not easy as you need to use instance X for X amount of users.

    Note that in AWS new generation instance types (like m4) have more processing power per vCPU than older generations (m2) for me the bible is this site http://www.ec2instances.info/ note the difference in ECU.  One EC2 Compute Unit (ECU) provides the equivalent CPU capacity of a 1.0-1.2 GHz 2007 Opteron or 2007 Xeon processor.

    The server is loaded by concurrent report executions. i.e. a user looking at an already executed report will have minimal impact, while a user generating a dashboard with 4 dashlets will be executing 4 reports simultaneously.

    As a basic rule of the thumb, you can use the 100:10:1 rule; for each 100 named users you can expect 10 concurrent users from wich you can expect 1 concurrent report execution at any given time. Of course, this is also broad, you should tailor that to your use case.
    Based on the little info I have I think an m3.large will become memory bound in your case since you only have 7.5GB available and I'm assuming you are running the regular AMI where JRS and the repo DB are in the same box. 
    Look into the Cloud Formation Templates for clustering here http://community.jaspersoft.com/jaspersoft-aws/launch that show Launching Jaspersoft with the repository DB on RDS. Since this will offload some resources from the AMI. I do recommend for convenience using the cluster deployment even if you use only one machine :)

    Regarding Dev & Tes, you are correct you should create CF templates for your environments and spin those off and on when needed. Use the ones in the link above as a reference. Is much better to automate those things, AWS have really good API's for managing this automation https://aws.amazon.com/cloudformation/

    Hope this helps :)

  3. The " An error has occurred. Please contact your system administrator. (5321)" is a very generic erros that is normally shown where there are security issues.

    Check the jasperserver.log, there you should find more meaningful explanation on what is going on. The default log file is WEB-INFlogsjasperserver.log.

  4. Re: #4 and the problems you caused, that is bacause your JasperServer can no longer access the repository, go to /webapps/jasperserver-pro/META-INF/context.xml and change the password for the jdbc/jasperserver JNDI connection properies in that XML file and restart the server :)

     

  5. Hi Rohit, "suggest the improvements" is a tall order, not sure you are going to get any help unless you are more specific about the improvents you need.

    Also I suggest you add the report to dropbox or something and link to it for download, makes the question more readable.

  6. You need to change the JNDI connection to the repo, that is defined in <TOMCAT>/webapps/jasperserver-pro/META-INF/context.xml

    There look for the JNDI connection called jdbc/jasperserver and change the password to the new one

        <Resource name="jdbc/jasperserver" auth="Container" type="javax.sql.DataSource"
            maxActive="100" maxIdle="30" maxWait="10000"
            username="postgres" password="postgres"
            driverClassName="org.postgresql.Driver"
            accessToUnderlyingConnectionAllowed = "true"
            validationQuery="SELECT 1"
            testOnBorrow="true"
            url="jdbc:postgresql://localhost:5432/jasperserver"
            factory="com.jaspersoft.jasperserver.tomcat.jndi.JSBasicDataSourceFactory"
             />
  7. You will need to check on the Fishbowl docs how to set that up since that is specific for how that product has embedded Jasper Reports and which version of Jasper Reports they use. Based on the link below they use an old version so you will need to set JSS in compatibility mode (in the JSS Property dialog) for that particular version

    https://www.fishbowlinventory.com/wiki/IReport

  8. That is because you have /n and your line separator may be different check System.getProperty("line.separator")

    In this cases I prefer to use styled test. You can do this, replce the "/n" with breaks <br>:

    myText.replace("n", "<br>");

    And then In the properties window of the text Field select "html" in the “Markup” drop down (see screenshot below). Also remember to select "Stretch with Overflow" so the txt field will stretch when the text is long.

    These are the markup options you have for your reference, check the JasperReports Doc Samples:

    • none - The content of the text element is plain text. There is nothing to be processed. This is the default value.
    • styled - The content of the text element is styled text, the JasperReports proprietary XML type of markup text. It overrides the deprecated isStyledText attribute. (See the Styled text sample)
    • html - The content of the text element is Hyper Text Markup Language
    • rtf - The content of the text element is Rich Text Format
     
    Screenshot2016-04-2510_20_47.png.129ef3f7f06b1f367a8526f5e105475c.png
  9. For 6.0.1 you need to follow the same instrucctions as for 5.x versions check this article http://community.jaspersoft.com/wiki/how-modify-jasperreports-server-561-default-html5-color-palette Remembet that this will affect all Adhoc Charts since it is a server level setting.

    Starting in 6.2 Jaspersfot added the posibility to change/control those color at the AdHoc level per chart, so upgrading will probably be best :) You can find more info about this in the 6.2 Documentation and also in the What's New in Jaspersoft 6.2 Page. Take a look at this video for a demo

×
×
  • Create New...