Report templates can be specified as a file name or a resource name. If the templates are referenced using a file name, a 'templateFile' parameter must be included in the request URL, e.g.,
http://localhost/servlet PDFService?templateFile=template1.srt
If the file name is not a full path, the directory specified in the 'templateDir' parameter is used as the location of the file. Otherwise, the full path is used to load the template file.
Alternatively, a template can also be specified as a resource name. A resource is loaded using the Java class loading mechanism. The resource is loaded using the CLASSPATH in the same way as a class file. Therefore, a resource file could be loaded from the local file system, or a JAR file.
http://localhost/servlet/PDFService?templateResource=/reports/template1.srt.
If any query used in a report requires user parameters, the parameter values must be encoded in the request URL as HTTP parameters. All parameters specified on the URL are passed to the query engine as the parameters for the queries. Assuming a parameter called 'state' is defined in the query, the request URL must specify the parameter as follows:
http://localhost/servlet/PDFService?templateFile=template1.srt&state=ny
If parameters are required, the request URL must contain the parameter specification as shown above. The servlet does not prompt for the parameter values. If the parameter values need to be entered by users at runtime, the application must create its own HTML interface to get the parameters and pass the parameters to the servlet as part of the URL.
The goal overall of data virtualization is agile business, and we really need to put business at the center of this whole discussion. You know we are not really interested in building pretty architecture pictures here. The goal is to really enable a fast incremental business value driven evolution of the organization and so we ask what role therefore does enterprise architecture and information management play in that? How can we make that iterative agility as much as possible self-service enabled by the business people. You want pervasive business intelligence at the edges of the organization, not all centralized.
The idea is virtualized access to information as a service, and we will explore what that means architecturally, but the idea is you want to be able to deliver the right information to the right person or persons at the right time and not make that very complex or difficult to do. In this context, enterprise architecture is evolving more away from just being a set of boxes that represent well here is my IT or infrastructure architecture, here is my messaging architecture, here is my information architecture, my business process architecture, and application and solution architecture.
Copyright © 2024, InetSoft Technology Corp.
