PRODUCTS
PARALLEL CRYSTAL
   LATEST DEVELOPMENTS
   ARCHITECTURE
   DOCUMENTATION
   WEB PORTAL SERVERS
   ACTIVE X
SAFFRON PDF PROJECT
RESOURCES
   SAMPLE CODE
   FAQs

Allaire JRun and Parallel Crystal Sample Source Code

General Configuration Notes (readme)

Extract zip file into the root directory of a disk drive on the Alaire JRun™ server machine. It will automatically create a folder, named JRunSample.

This demo is set up to work with jdk1.2 or higher and JRun 3.0.

NOTE: If you have extracted this sample to a directory other than C:, it is necessary that you copy the sample.config file to the C:\JRunSample directory or this sample will not be able to find it and will use its default settings.

Open up the <path_to_JRunSample>\sample.config file, and make the following changes:

• Make sure that the value for outputDir correctly matches the path to where you have installed the JRun server.
  
• Replace localhost in the value for outputURL with your machine's full DNS name. Make sure that the rest of outputURL is correctly mapped by the HTTP server to JRun's default-app folder with "/Pcre" appended to it.
  
• Replace the server name value with the full DNS name of the PCRE server machine.
  
• Make sure that the value for DORfile.location states the correct path of the
  <path_to_JRunSample>\DORDataFile.dat file.
  
• If you are accessing a password protected database, modify the user name and password.
  
  

If the JRun server and the Parallel Crystal Report server are running on separate machines, the PCREJavaClient.jar file should be copied to a folder on the JRun server machine.

The <path_to_JRunSample>\Pcre folder and its contents must be copied to the appropriate folder under the JRun Home directory (<path_to_JRun>\servers\default\default-app ).

Move the <path_to_JRunSample>\Bike_DB.rpt, Box.rpt, and ReportLog.rpt files to the <path_to_MobileApps>\Pcre\SampleReports folder on the report server machine.

Using the JMC, configure the classpath of the Admin Server to contain
<path_to_mobileapps>/pcre/jars/pcrejavaclient.jar, <path_to_JRunSample>/sample_ejb.jar, <path_to_JRunSample>/sample_util.jar, and <path_to_jrunsample>/reporttag.jar. You will need to use short file names in the classpath. For example, if you installed Parallel Crystal in the Program Files directory, you will need to specify the file name as c:\progra~1\mobileapps\pcre\jars\pcrejavaclient.jar.

To generate reports in Microsoft Word or Excel, the MIME type mappings need to be configured. Open up the JRun Management Console (JMC), and in the left pane of the JMC, select machine_name > JRun_server_name > Web Applications > application_name > MIME Type Mappings > edit. Enter the following information:

Click "update" and then restart the server.

Microsoft® Access database setup

Generating the log report requires a ODBC setting of a DSN named ReportLog, connected to the MS Access File <path_to_JRunSample>\ReportLog.mdb

Bike_DB.rpt report requires an JRun server machine ODBC setting of a DSN named BikeData, connected to the following MS Access File: <path_to_JRun Sample>\bike.mdb . The BikeData data source is used to demonstrate DOR reporting where the data is passed from the JRun server to the report server.
More detailed instructions on setting up Microsoft Access ODBC drivers (Running an SQL Script).

Oracle® database setup

Open an SQL connection to your database and log on as "scott" with password "tiger" and run the SQL script in the file <path_to_JRunSample>\BikeData.sql.
More detailed instructions on setting up Microsoft Access ODBC drivers (Running an SQL Script).

EJB Configuration Notes

This demo contains a ready-to-deploy EJB jar file called sample_ejb.jar. The <path_to_JRunSample>\deploy.properties and the <path_to_JRunSample>\sample_ejb.jar files must be copied to the deploy directory under your JRun server. To deploy the bean using the JRun Management

Console, select machine_name > JRun_server_name, and click on "Enterprise JavaBeans". In the right pane, click on "deploy". Select the sample_ejb.jar file in the deploy directory of your server, and click "deploy." After the bean has been successfully deployed, restart your server.

NorthWind Demo

The NorthWind Demo is a more complex set of reports, implemented through EJB only. These reports require an ODBC DSN on the report server connected to the Northwind.mdb Access database. Northwind.mdb is located in the <path_to_JRunSample> folder and should be copied to the report server machine.

Running the Demo

To run the demo, start the JRun server and make sure that the sample_ejb.jar deployed properly. Start the Parallel Crystal Report server. Start your browser and point to http://<JRun server DNS name>:8100/Pcre/index.html. Note that the JRun web server is case sensitive, so type the url exactly as shown.

Performance Enhancements

Disabling JSP page compilation
Before performing the following steps, you will need to run all of the demos so that all of the JSPs are compiled. Instead, you may use JRun's jsp compiler tool to compile all of the pages at one time. More information about the tool can be found in JRun's documentation.

To explicitly disable JSP page compilation, use the JMC to modify the JRun servlet that handles JSP pages.

You make this setting at the Web application level so that you can enable or disable compilation for individual Web applications. Use the following procedure to disable JSP compilation:

1. In the JMC, select the server-name > Web Applications > app-name > Servlet URL mappings property. (The corresponding form will open in the right side of the JMC.)
   
2. In the form, click the edit button to open the edit dialog box.
   
3. Under the Virtual Path/Extension column, enter *.jsp.
   
4. Under Servlet Invoked, enter jsprt.
   

The jsprt servlet will now be used to handle every request to a JSP page. This servlet does not check for the existence of the JSP page but instead looks only for the corresponding .class files. Therefore, in a deployed Web application, you do not need to actually deploy the JSP pages. Because JSP files are source code files, you can omit your source code from deployed applications. (Excerpt from "Developing Applications with JRun")

A minor improvement in performance may also be achieved by turning off logging in the JMC.