mmflynn

Jaspersoft BI for Amazon Web Services requires very little systems management. Despite its greatly reduced need for administrative intervention, on occasion you may need to connect to the server's file system to retrieve log files, upload licenses, edit configuration files, or run commands from a console interface. There are a variety of utilities you can use to accomplish these tasks. This article demonstrates file transfer using a third-party utility for Microsoft Windows called WinSCP. Command line interactions are shown using the AWS console "Connect from your browser" feature. These two utilities were chosen because they are the easy to explain and use for their use cases. You may be familiar with and prefer other methods, such as PuTTY, ssh command line utilities, and so on. File TransferThis section demonstrates an easy way to move files back and forth between the Linux server running JasperReports Server on AWS and your local computer. (Note: The client computer for this example runs Microsoft Windows.) File transfer use cases include: Uploading a Jaspersoft license file from your local computer to JasperReports ServerDownloading log files for troubleshootingUploading database drivers, custom data source files, and so onRequirementsThe public IP address or hostname of the AWS server instance running JasperReports ServerThe Public key name associated with the server instanceThe path to the Private key file that works with the Public key mentioned aboveA file transfer utility such as WinSCPImportant: If using WinSCP, the Private key file must be converted to the .ppk file format. Use the Puttygen "import key" utility to convert from .pem to .ppk file formats. See Dealing with Private Keys in Other Formats for more information.Login username: ec2-userSteps to Transfer FilesRun the WinSCP application from the Windows Start menu.Click New. Use the following values:Host Name (or IP address)Port number: 22User name: ec2-userPassword: leave blankPrivate key file: navigate to the Private key fileProtocol: SFTPClick Save. The default session name will follow the standard user@host, e.g., ec2-user@bdsandbox7. You can change it if you want. Click OK.Click Login to connect. Your local file system appears in the left panel and the remote AWS computer appears in the right. You can now easily copy files back and forth between systems. WinSCP ExtrasEditing Files with WinSCPYou can double-click and edit text files directly from the WinSCP interface. A copy of the file will be downloaded and opened in a text editor. When you save the file, it will be copied back to the server. Command Line Interactions with WinSCPWinSCP includes a Commands menu. From it you can click Open Terminal, which allows you to run a single command at a time, or Open in PuTTY, which opens a full command line console if you have PuTTY installed. Command Line InteractionsThe AWS console provides a command line utility that runs in a Java-enabled Web browser window. It is documented on the AWS web site. Command line interactions use cases include: Starting, stopping, restarting or checking the status of JasperReports ServerRunning any Linux commandRequirementsAccess to the AWS ConsoleThe path to the Private key file that works with the Public key used by your server instanceSteps to Open a Command Line Window from the AWS ConsoleLogin to the AWS console, e.g.: https://<yourOrganization>.signin.aws.amazon.com/console From the AWS Console Home page, click EC2Click Instances from the side bar or Running Instances from the top level summaryLocate your instance and right-click itFrom the Instance Management pop-up menu, click ConnectThe Public DNS and Private Key name will be entered for you. Complete the following:User name: ec2-userPrivate key path: enter the path to the Private key file that works with the Public Key named on-screen.Click Launch SSH ClientWhen prompted to run the application named com.mindbright.application.MindTerm, click RunIf prompted to add the server's fingerprint to the cache, click YesYou can now run any Linux commandFor More InformationAWS Documentation: Getting a Key Pair AWS Documentation: Getting Started with Amazon EC2 Linux Instances, Step 3: Connect to Your InstanceJaspersoft Community Article: How to Produce Clean Log Files for TroubleshootingJaspersoft Community Article: Applying Your Jaspersoft Product License(s)

JasperReports Server can connect to just about any data source. JasperReports Server comes standard with connection wizards for JDBC, JNDI, and Bean (Java bean) data sources. Jaspersoft also offers an extensible environment for including custom data sources in screens etc. Check the JasperServer Users Guide for details. Acquire the Database Driver PackageJasperReports Server redistributes a Postgres database driver. If you need to connect to another database, you will need to acquire the appropriate driver and add it the application server's classpath. Here are some links that may assist. Check with your DBA to ensure you are using the correct driver. MySQL driver: http://dev.mysql.com/downloads/connector/j/ jTDS driver for SQL Server and Sybase: http://jtds.sourceforge.net/ Microsoft SQL Server: http://msdn.microsoft.com/en-us/data/aa937724.aspx Oracle: http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html PostgreSQL: http://jdbc.postgresql.org/ Pervasive: http://www.pervasivedb.com/psqlv11/Pages/Default.aspxExtract the downloaded files to an easily accessed location. For example, c:jdbc or /usr/share. Locate the actual driver name. You will copy it to the classpath in the next step. Sample driver names include: MySQL: mysql-connector-java-5.1.18-bin.jar jTDS: jtds-1.2.2.jar Microsoft SQL Server: sqljdbc4.jar (for JDK 1.6/6.0), sqljdbc.jar (JDK 1.5/5.0) Oracle: ojdbc14.jar, ojdbc6.jar PostgreSQL: postgresql-8.1-407.jdbc3.jar Pervasive: jpscs.jar, pvjdbc2.jar, and pvjdbc2x.jarCopy the Driver to the ClasspathYou need to copy the driver (the .jar file) to the classpath. In general it's best to copy the driver to the application server's shared library location. Refer to your application server documentation for exact locations. Sample locations include: Tomcat5: commonlib (for example: C:/Program Files ( x86)/jasperreports-server-4.0/apache-tomcat/lib ) Tomcat6: lib ( for example: /var/lib/tomcat6/lib ) JBoss5: serveralllibOptional JNDI ConfigurationYou can define a JNDI connection in your application server. The database drivers must be in the application server's shared library classpath (see the previous section). The technique you use to define the JNDI connection will vary by application server. For Tomcat, you can define the JNDI connection within JasperReports Server by editing /webapps/jasperserver-pro/META-INF/context.xml. Use the sample configurations as a guide. Restart JasperReports ServerRestart the application server. If you installed JasperReports Server using the Windows installer, there is a shortcut in the start menu to restart it. Define the Data Source in JasperReports Server Log into JasperServer's web site. http://localhost:8080/jasperserver-pro Go to View | Repository. Click the second icon called Add Resource and select Data Source. Choose a data source type and click next. Provide any Name, Label, and Description. If you selected the JDBC connection type, you will typically enter values such as these samples:MySQL Connector/J driver: com.mysql.jdbc.Driver url: jdbc:mysql://localhost:3306/sakilajTDS (for Microsoft SQL Server) driver: net.sourceforge.jtds.jdbc.Driver url: jdbc:jtds:sqlserver://host:1433/yourDatabase url: jdbc:jtds:sqlserver://host:1433/yourDatabase;intance=yourInstanceMicrosoft SQL Server driver: com.microsoft.sqlserver.jdbc.SQLServerDriver url: jdbc:sqlserver://host:1433;databaseName=yourDatabaseOracle (thin driver) driver: oracle.jdbc.OracleDriver or oracle.jdbc.driver.OracleDriver url: jdbc:oracle:thin:@host:1521:your_db_instance_name example url: jdbc:oracle:thin:@remotehost:1521:orcl example url: jdbc:oracle:thin:@localhost:1521:xePostgreSQL driver: org.postgresql.Driver url: jdbc:postgresql://host:5432/yourDatabasePervasive driver: com.pervasive.jdbc.v2.Driver url: jdbc:pervasive://localhost:1583/DEMODATATroubleshootingIf it doesn't succeed, save anyway and restart the JasperReports Server and watch for any exceptions.

IntroductionIn this article, we show how to set up a multi-tab landing page for users based on their roles and organizations, so that when a user logs in, we get something like the screenshot below: To get this example working, we assume that you have installed the sample Foodmart database. If you are not using the sample database, you can easily adapt this solution to your own test environment. This procedure works for JasperReports Server v4.5. Installation ProcedureDownload the resource packageFilesForTabstest.zip - commonJSTLScripts.jsp goes to the /jasperserver-pro/WEB-INF/jsp/modules directoryhome.jsp and homeForTabs.jsp go to the /jasperserver-pro/WEB-INF/jsp/modules/home directoryViewReport.jsp goes to the /jasperserver-pro/WEB-INF/jsp/modules/viewReport directorycontrol_tabSet.jsp goes to the /jasperserver-pro/WEB-INF/jsp/templates directory, which contains these files: DirectoryFile namePurposesuperuser_upload_to_themestabstest.zipa new theme that turns off menus and search boxes (works with 4.5 and below only)WEB-INF/jsp/modules/commonJSTLScripts.jspmodified to include a function to switch tabsWEB-INF/jsp/modules/homehome.jspmodified to include a tabbed home page WEB-INF/jsp/modules/homehomeForTabs.jspa new file that displays a tabbed view of reports or dashboards for the home pageWEB-INF/jsp/modules/viewReportViewReport.jspmodified to turn off the Back button so users do not inadvertently see the Repository Browser (not working or needed for Jaspersoft 5 and above)WEB-INF/templatescontrol_tabSet.jsp Place them in a working directory. Make backupsThe first thing is to back up the files we're about to overwrite. In a backups directory, copy these files over from the the web application's root directory: /jasperserver-pro/WEB-INF/jsp/modules/home/home.jsp/jasperserver-pro/WEB-INF/jsp/modules/commonJSTLScripts.jsp/jasperserver-pro/WEB-INF/jsp/modules/viewReport/ViewReport.jsp/jasperserver-pro/WEB-INF/jsp/templates/control_tabSet.jspCreate sample user with sample roleFor this example, you'll need to create a test user with the right role: Login as the superuserGo to "Manage -> Roles"Make sure that "Organization" is selected on the left-hand sideAdd the role, and label it ROLE_TABTEST; make sure it's this and that it's uppercase - it needs to match what we see in the home.jsp fileGo to "Manage -> Users"Make sure that "Organization" is selected on the left-hand sideAdd a new userAssign the role "ROLE_TABTEST" to that new userUpload the sample themeStill as the superuser, go to the repository, and browse to the organization's Themes folder, which you can find under /Organizations/Organization/Themes. Right-click on the Themes folder and choose the "Upload Theme" option, and upload the tabstest.zip file. Make sure to name that theme tabstest. The ViewReport.jsp file depends on that value to hide the back button. Stop the Tomcat serverNow you'll need to stop the Tomcat server do properly replace the JSP files and do some cleanup on the server-side files. Replace the JSP filesYou previously backed up some files we're going to overwrite, so now we're ready to put in our custom files. commonJSTLScripts.jsp goes to the /jasperserver-pro/WEB-INF/jsp/modules directoryhome.jsp and homeForTabs.jsp go to the /jasperserver-pro/WEB-INF/jsp/modules/home directoryViewReport.jsp goes to the /jasperserver-pro/WEB-INF/jsp/modules/viewReport directorycontrol_tabSet.jsp goes to the /jasperserver-pro/WEB-INF/jsp/templates directoryClear Cached JSPsWe'll also need to do a bit of clean-up on some server-side files. Tomcat processes JSP files first into JAVA files and then compiles them to CLASS files, which it stores in a working directory that it uses as a cache; this is a normal server optimization that saves Tomcat the trouble of having to compile a JSP file for every single request. So that we're sure that it's taking the latest JSP, we're going to have to clear out those files from the cache directory before we re-start Tomcat. Browse to the Tomcat root directory, and then find this subdirectory: /apache-tomcat/work/Catalina/localhost/jasperserver-proorgapachejsp. Under that directory, you'll find another subdirectory typically called WEB_002dINF; it may vary in your particular situation. Under that directory, you will find the JAVA and CLASS files that correspond to each JSP file; find them and then delete them. For example, under the /WEB_002dINF/jsp/modules/home directory, you'll find home_jsp.java and home_jsp.class; go ahead and delete these two files as well as all the other JSP files that you overwrote. Restart the serverYou are now ready to restart the server! If you've followed the instructions up to now, you should be able to restart the server and login as the test user you created earlier. When you login, you should also find that you've landed in the multi-tab landing page. Explanation of the different filesThe home.jsp fileWhen a user logs in, the server will process the home.jsp file (which is found in the /jasperserver-pro/WEB-INF/jsp/modules/home directory) to decide which JSP to serve up as the landing page for the user. <!-- ~ Copyright © 2005 - 2011 Jaspersoft Corporation. All rights reserved. ~ http://www.jaspersoft.com. ~ Licensed under commercial Jaspersoft Subscription License Agreement --%>;<%@ page contentType="text/html" %>;<%@ taglib uri="/spring" prefix="spring"%>;<%@ taglib uri="http://www.springframework.org/security/tags" prefix="authz"%><authz:authorize ifallgranted="ROLE_DEMO"> <jsp:include page="homeForDemo.jsp"> </jsp:include></authz:authorize><authz:authorize ifallgranted="ROLE_TABTEST|organization_1"> <jsp:include page="homeForTabs.jsp"> </jsp:include></authz:authorize><authz:authorize ifnotgranted="ROLE_DEMO"> <authz:authorize ifnotgranted="ROLE_TABTEST|organization_1"> <jsp:include page="homeForNonDemo.jsp"> </jsp:include> </authz:authorize></authz:authorize>[/code]If you compare it with the home.jsp that the product ships with, you'll notice the extra entries for the ROLE_TABTEST role; the entry is a rule that will serve up the homeForTest.jsp if the user has the "ROLE_TABTEST|organization_1" role assigned to them. This means that the role is specific to the organization, and is not a global role, like ROLE_SUPERUSER and ROLE_PORTLET. When creating the role, make sure to have the organization you want to create this role for properly selected! The homeForTabs.jspThis file will contain the references to the three reports or dashboards that show up in the three different tabs. If you are not working with the the sample reports and dashboards, all you have to do is replace the URL's parameter values with the ones that reference your own report or dashboard. You can define the three reports or dashboards to view here, within this Javascript function. All you have to do is replace the URL references that start with "˜flow.html' with the references to your own reports and dashboards. <script>function myFunct(var1) { var ifrm = document.getElementById('ifrm'); if (var1 == "opt1") { ifrm.setAttribute('src', 'flow.html?_flowId=dashboardRuntimeFlow&dashboardResource=/supermart/SupermartDashboard30&viewAsDashboardFrame=true'); } else if (var1 == "opt2") { ifrm.setAttribute('src', 'flow.html?_flowId=viewReportFlow&standAlone=true&_flowId=viewReportFlow&ParentFolderUri=%2Freports%2Fsamples&reportUnit=%2Freports%2Fsamples%2FEmployees&viewAsDashboardFrame=true'); } else if (var1 == "opt3") { ifrm.setAttribute('src', 'flow.html?_flowId=viewReportFlow&standAlone=true&_flowId=viewReportFlow&ParentFolderUri=%2Freports%2Fsamples&reportUnit=%2Freports%2Fsamples%2FAllAccounts&viewAsDashboardFrame=true'); }}</script>[/code]Further down, you'll find this JSP code that defines the tab labels and tab attribute names that the Javascript code above will use: <t:inserttemplate template="/WEB-INF/jsp/templates/control_tabSet.jsp"> <t:putattribute name="type" value="buttons"> <t:putattribute name="containerClass" value="horizontal"> <t:putlistattribute name="tabset"> <t:addlistattribute> <t:addattribute>opt1</t:addattribute> <t:addattribute>Dashboard 1</t:addattribute> <t:addattribute>selected</t:addattribute> </t:addlistattribute> <t:addlistattribute> <t:addattribute>opt2</t:addattribute> <t:addattribute>Dashboard 2</t:addattribute> </t:addlistattribute> <t:addlistattribute> <t:addattribute>opt3</t:addattribute> <t:addattribute>Dashboard 3</t:addattribute> </t:addlistattribute> </t:putlistattribute> </t:putattribute> </t:putattribute></t:inserttemplate>[/code]At the very bottom, you'll find the iframe tag, where you can populate the default tab to load in the src attribute: <t:putattribute name="bodyContent"><iframe frameborder="0" height="99%" hspace="0" id="ifrm" marginheight="0" marginwidth="0" scrolling="auto" src="flow.html?_flowId=dashboardRuntimeFlow&dashboardResource=/supermart/SupermartDashboard30&viewAsDashboardFrame=true" vspace="0" width="100%"></iframe></t:putattribute>[/code]The ViewReport.jsp fileThe customized ViewReport.jsp file contains extra code to hide the back button when the embed theme ("˜tabstest') is turned on. Notes This article was originally published for version 4.5, this continues to work in version 5.0 (except for the optional ViewReport.jsp, this wasn't tested). The theme won't work with 5.0 eitherIn the homeForTabs.jsp page you might get a security error if you sue the /path/like/this, you'll need to encode it with this tool to %2Fpath%2Flike%2FthisYou might consider modifying the theme (file container.css) to remove extra space at top of margin:.column.decorated.tabbed.showingToolBar > .content > .body { margin-top: 64px;}[/code]

Error: Packet for query is too large[toc on_off::hide=1] Caused by:com.mysql.jdbc.PacketTooBigException: Packet for query is too large (2257806 > 1048576). You can change this value on the server by setting the max_allowed_packet variable. CauseMySQL Server's default max_allowed_packet value is 1MB. You must increase the max_allowed_packet to meet the maximum file size of documents you want to store in the Jaspersoft repository. ResolutionTo determine how large to set the max_allowed_packet value: Run the largest report and export it to your desired file format (PDF, XLS, etc.). Save the file to disk to determine its file size. As the MySQL administrator, update the mysqld max_allowed_packet property.For example, if your largest exported file is 35 MB large, then make the following edit in my.ini. #SERVER SECTION [mysqld] max_allowed_packet = 35M Restart MySQL for this change to take effect.