J2EE Report Generation

This article continues the explanation of how to take advantage of InetSoft's JSP tag libary for integrating reports into your Web application.

demo
Read how InetSoft saves money and resources with deployment flexibility.


The Create Tag

The next tag needs to be the 'create' tag. This tag specifies the report that will be embedded in the JSP. It also handles the generation of the report and serves all of the resources required by the report.

There cannot be any HTML content or JSP tags that generate content before this tag. The create tag handles serving images and static files such as cascading style sheets and JavaScript files. If there is any content before this tag, it will be included in the resource file and will corrupt it. If you require that there be content before the create tag, you must specify the resourceUri attribute. This attribute should be set to the URL of a Servlet Repository deployed in the same web application. The Servlet Repository and the JSP tag library share the same resources and report server, so there is very little additional overhead.

In WebLogic, there also cannot be any characters (i.e., new lines) outside of JSP tags before the create tag. WebLogic will print these characters to the output stream, corrupting the image file. Setting the resourceUri attribute will solve this problem.

The create tag has two required attributes, reportId and name. The reportId attribute is a unique string that identifies all subsequent tags as referring to this report. This allows you to include more than one report in a single JSP page. The reportId need only be unique within the JSP, not within the entire web application. The name attribute is the name of the replet as it is registered in the Replet Repository. The name should include all folders in its path, separated by a forward slash (/).

The create tag also has one optional parameter, processPage. This attribute determines the behavior of the JSP if the report is not yet available. If processPage is set to false, the remainder of the JSP is not processed and the text “Loading Report...” is displayed. If processPage is set to true, the JSP is processed and the content included in the body of the subsequent report tags is displayed in place of the report element.

<sree:create reportId="myReport" name="My Folder/My Report" processPage="true"/>

The Parameter Tag

The create tag can also contain parameter tags. These tags pass report parameters to the report. The parameter tag has three required attributes: name, value, and type. The name attribute specifies the name of the parameter, the value attribute specifies the value of the parameter, and the type attribute specifies the data type of the parameter value. The allowed parameter types are listed in Appendix C: Tag Library Reference. If the type is “date”, you also need to include the format attribute. The format attribute specifies the format in which the value is being passed and should use the format specified in java.text.SimpleDateFormat.

 <sree:create reportId="report1" name="A Report" processPage="false">
 <sree:parameter name="State" value="NY" type="string"/> 
 <sree:parameter name="Order Date" value="2003-05-01"    type="date" format="yyyy-MM-dd"/>
 </sree:create>

If a report parameter has the same name as a JSP request parameter, it will be passed to the report without having to include a parameter tag. Using a parameter tag in this case will override the value of the JSP parameter.

More Articles About Report Generation

Analytic Tools for Government - It's driving a lot of decisions that the government has to make, hard decisions. And we want to make sure they are the right decisions because they are going to impact our future. We are also working with a lot of states who are working on tax compliance solutions. For instance, I read where over the past fifteen years a combination of five states were able to collect $1.5B more because of good analytics. With modern analytic tools, they were able to identify non-compliant tax filers. I know that as a taxpayer, myself, I am happy that they are going after those non-compliant filers because that way everybody pays their fair share and it keeps the tax burden on the rest of us lower...

Bring Dashboards and Reporting to Your Big Data - InetSoft's Style Intelligence drops into an existing Apache Spark installation. This bring-the-software-to-the-data approach eliminates costly big data movement for analytics and reporting. Style Intelligence can also be deployed with its own built-in Spark cluster. In this case, only minimal expertise in Spark is required. The cluster is mostly configured and administered by Style Intelligence behind the scenes to maximize data processing and mashup performance...

Drawbacks of JD Edwards' Dashboards - While JD Edwards' dashboards provide valuable insights and facilitate decision-making, they also come with certain drawbacks that users should be aware of: Limited Customization Options: One of the main drawbacks of JD Edwards' dashboards is the limited customization options available to users. While they offer pre-built templates and layouts, users often find it challenging to tailor the dashboards to their specific needs and preferences. This lack of flexibility can be frustrating for businesses that require highly customized reporting and analysis. Complexity: JD Edwards' dashboards can be complex to set up and configure, especially for users who are not familiar with the software's architecture and functionality. Configuring data sources, defining metrics, and designing intuitive visualizations may require significant time and effort, particularly for organizations with complex data structures and workflows...

Evaluate InetSoft's Big Data Dashboard Tool - Are you looking for good big data dashboard tools? InetSoft's pioneering dashboard reporting application makes producing great-looking web-based reports and dashboards easy with a drag-and-drop designer and the ability to connect to all types of big data sources. View a demo and try interactive examples...

KPIs in Customer Service Centers - FC Resolution Rate The FC Resolution Rate is broadly known as the First-Contact Resolution, and it is the percentage on which the team of customer care executives resolves a particular issue presented by the customers. In this case, any of the multiple channels can come into play like email, live chat, or phone call. AR Time The full form of AR is Average Reply, and it is the time taken on average by a service representative to address and clarify a customer's problem. An experienced service representative generally has a low AR time compared to novice ones. Ticket Volume The Ticket Volume is one of the vital dashboard analytics among the customer service centers. It also has a relation with the service representative for the number of tickets present in his support queue in a given period...

Predictive Analytics at Work - How do we get to this point? What's going on in the background? Essentially it's predictive analytics at work. To simply the situation, there's a scoring mechanism, real time scoring going on in the background as Sarah is talking to Michael. At the outset when Michael makes contact with the insurance company, he tells them he damaged the front bumper of his car when we veered off the road. Based on information about Michael, his history, and customers similar to him, there's a 78% chance that Sarah can fast track the claim, that is legitimate, that there are no questions around this particular claim...

Previous: JSP Tags for Embedding Reports