Quick Start

In order to get you up and running in the shortest amount of time I have included the Jetty J2EE server in the download.

This is really useful for checking out the integration, for test and development environments. Typically in production environments, you would rather deploy it in your J2EE server of choice, i.e. Weblogic, Glassfish, Tomcat, OC4J, etc. If you want to do that, follow the regular installation procedure here.

1. Download the files

You can download the files from here and unzip them.

2. Configure your database access

Edit the file conf/application.properties and configure the data source default to connect to your Oracle schema (change the parts in bold to point to the Oracle schema you want to connect to):

#====================================================================
# JDBC datasource configuration
# http://www.orafaq.com/wiki/JDBC#Thin_driver
#====================================================================
[datasource:default]
name=default
url=jdbc:oracle:thin:@192.168.2.114:1521:XE
username=HR
password=hr_password

3. Deploy the JasperReportsIntegration.war file

This step has only to be executed once, the J2EE application is deployed on the Jetty J2EE server initially.

On Unix / Linux:

On the command line enter the following commands:

On Windows:

4. Start the J2EE server

On Unix / Linux:

On the command line enter the following command:

On Windows:

5. Test the server

After 30seconds you can access the server. By default I will start it on port 8090. If you need a different port, just change it in the script startJasperReportsIntegration.

6. Installation of database objects

Now that we have the J2EE application working, we can install the PL/SQL API in the database. The database objects required for the integration will be installed into each application schema that you want to use with the integration. 

The installation instructions will refer to the application schema (in which you install the software) as [application schema]. The password for the application schema will be referred to as [application schema password].

Thus when I use an instruction like sqlplus [application schema]/[application schema password]@[database] please replace that with the actual values of your local installation. For example, if you want to install the integration kit into the schema HR with the password hr1 into your local XE instance (having a TNS entry named xe) then this instruction translates to:

sqlplus hr/hr1@xe

6.1 Database installation (SYS)

First of all we need to grant the required privileges to the Oracle user who will own the packages for the integration.

  1. Extract the downloaded zip file.
  2. Open a command shell:
    • e.g. on Windows: Start > Execute : cmd
  3. Go to the subdirectory sql (of where you extracted the file):
    • cd sql
  4. Connect as SYS to the local instance (using sqlplus)
    • sqlplus "sys/[sys password]@[database] as sysdba"
  5. Run the installation script (and pass the name of the target application schema as a parameter)
    • @sys_install.sql [application schema]
  6. [optional] If you are installing on an Oracle Release 11.0 and higher, you have to grant the required network privileges to the application schema. 
    • The  script sys_install_acl.sql allows access to the local machine on port 80 to port 10000. Please adapt the script to suit your needs, especially if the J2EE server is running on a different machine.
    • @sys_install_acl.sql [application schema]

6.2 Database installation (Application Schema)

  1. Open a command shell:
    • e.g. on Windows: Start > Execute : cmd
  2. Go to the subdirectory sql (of where you extracted the file):
    • cd sql
  3. Connect as the application schema to the local instance (using sqlplus)
    • sqlplus [application schema]/[application schema password]@[database]
  4. Run the installation script
    • @user_install.sql

7. Installation of the test application

The test application will allow for basic testing of the integration with all relevant parts. Install the application file apex\f121_JasperReportsIntegration-Test_x.x.x.x.sql into your workspace.