Home

Welcome to the JR PrintServer wiki!

Take a quick start with these FAQs:

What is the JR PrintServer?

It's a web application to be deploy to a servlet container or an application server like Apache Tomcat or Oracle WebLogic.

What's the purpose of the JR PrintServer?

It allows you to connect from Oracle APEX and/or PL/SQL and use the JasperReports Library to create sophisticated reports and deliver these reports back to to the Oracle database for downloading to the user's browser or further processing.

What are the differences and/or advantages compared to other integrations of JasperReports with APEX?

The JR PrintServer uses APEX's native interface to connect to a PrintServer. So, the processing is much more secure and greatly simplified.

Here's the procedure for the JR PrintServer:

1. The query to get the report's data is executed by APEX inside the APEX session.
2. The data along with some additional information (report name and so on) is send to the JR PrintServer.
3. The JR PrintServer executes the report and creates the result document.
   Note: The JR Print Server does not have to open any connection to do his work.
4. The report document is send back to APEX.
   And we're done!

Now, let's compare this to the procedure of other integrations:

1. The schema's username and password is send to the integration application together with additional information (report name and so on).
   Or, as any alternative, the schema's username and password is store together with integration application.
2. The application opens a new JDBC database connection (or get one from a pool) and executes some queries.
   Note: These queries are executed in a session environment that may be quite different from the originating one.
3. With the execution of those queries the report's data is send to the integration application.
4. The report executes and the result document will be created.
5. The report document is send back to APEX.