To meet prerequisites for installing the WAR file for WebLogic:
| 1. | Check that the Oracle/Sun Java JDK 1.6 or 1.7 is installed. |
| 2. | Check that the JAVA_HOME system environment variable points to the JDK. |
| 3. | Install the PostgreSQL, MySQL, Oracle, SQL Server, or DB2 database. |
| | The target database can be on a remote server. |
To install the WAR file for WebLogic:
| 1. | Extract all files in jasperreports-server-6.1-bin.zip into a top-level directory, such as C:Jaspersoft on Windows or /home/<user> on Linux. |
Unpacking the ZIP file creates the directory jasperreports-server-6.1-bin.
| 2. | Check that WebLogic is installed in the default location on your local machine. |
If WebLogic is not installed in the default location, or if you encounter problems using the buildomatic scripts, set up the database manually as described in step 10.
| 3. | (If you're using MySQL, you can skip this step.) Copy your JDBC driver to WebLogic. |
| a. | PostgreSQL example: Copy the JDBC jar from |
<js-install>/buildomatic/conf_source/db/postgresql/jdbc
to
<weblogic_home>/server/lib
| b. | TIBCO JDBC Oracle driver example: Copy ji-oracle-1.0.0-driver.jar from |
<js-install>/buildomatic/conf_source/db/oracle/jdbc
to
<weblogic_home>/server/lib
Note that the MySQL JDBC driver is included in recent versions of WebLogic.
| a. | Open the file <weblogic_home>/server/lib/jdbcdrivers.xml in a text editor. |
| b. | Add the correct settings for your database. The following example shows the settings for the TIBCO JDBC driver for Oracle. For DB2 or SQL Server, see Configuring TIBCO JDBC Driver Connections. |
| c. | Save the file |
| 5. | (If you're using MySQL, you can skip this step.) Set your WebLogic classpath for your database: |
| a. | Add the following line to your <weblogic_home>/bin/setDomainEnv.cmd/sh file: |
On Windows:
On Linux:
| b. | Save the file. |
| c. | Restart WebLogic using the startWebLogic.cmd/sh. |
| 6. | Copy the .properties file for your database: |
From — <js-install>/buildomatic/sample_conf/
To — <js-install>/buildomatic
| 7. | Rename the file you copied to default_master.properties file. |
| 8. | “Sample Values for the default_master.properties File” shows sample property values. |
| | When appServerType = skipAppServerCheck, buildomatic skips the application server type validation. Use this setting when installing JasperReports Server with WebLogic. Backslashes in appServerDir must be doubled, for example C:WLApplication_Server. Make sure there are no spaces in the appServerDir path. |
Sample Values for the default_master.properties File
Database
Sample Property Values
PostgreSQL
DB2
For DB2 8.x, change your deployed JDBC driver as described inLocating and Changing Buildomatic Configuration Files.
MySQL
Oracle
appServerType=skipAppServerCheckappServerDir=[path to WebLogic application server]sysUsername=systemsysPassword=passworddbUsername=jasperserverdbPassword=passworddbHost=hostname[/code]
Note that dbUsername must be the same as the Oracle user name.
SQL Server
If your application server runs on Java 1.5, change your deployed JDBC driver as described in Locating and Changing Buildomatic Configuration Files.
| 9. | Setup the database and optional sample databases using the buildomatic Ant scripts. Enter commands in the table below to call buildomatic Ant scripts: |
| | Exception: For DB2, skip this step and perform step 10) of this procedure. |
You call buildomatic Ant scripts from the command line using the following syntax:
Windows — js-ant <target-name>
Linux — ./js-ant <target-name>
| Commands | Description |
| cd <js-install>/buildomatic | Goes to the buildomatic directory. |
| js-ant create-js-db | Creates the jasperserver repository database |
| js-ant init-js-db-pro js-ant import-minimal-pro | Initializes database, loads core application data |
| js-ant create-sugarcrm-db js-ant create-foodmart-db | (Optional) Creates sample databases |
| js-ant load-sugarcrm-db js-ant load-foodmart-db | (Optional) Loads sample data into the sample databases |
| js-ant import-sample-data-pro | (Optional) Loads the demos that use the sample data |
| | On non-Linux Unix platforms, the js-ant commands may not be compatible with all shells. If you have errors, use the bash shell explicitly. For more information, see Bash Shell for Solaris, IBM AIX, HP UX and FreeBSD. |
| 10. | Add the database driver to your classpath. |
| 11. | In WebLogic, open an Administrative Console window and navigate to Services > Data Sources or Domain Configurations > Services > Data Sources. |
| 12. | Click New and then Generic Data Source for each of the data source columns in the following table, and enter the following values for a PostgreSQL database. You'll need to click Next after entering the database driver and after One-Phase Commit. |
| | To use a database other than PostgreSQL, configure the database connections using settings shown in Configuring Databases Using the Vendor's Driver. If you plan to use the sample databases (Foodmart and Sugar CRM), perform this step and the following step for each database. |
| Parameter Name | JasperReports Server | Foodmart Example | Sugar CRM Example |
|---|---|---|---|
| Name | JasperServerDataBase | FoodmartDataBase | SugarcrmDataBase |
| JNDI Name | JasperServerDataBase | FoodmartDataBase | SugarcrmDataBase |
| Database Type | PostgreSQL | ||
| Database Driver | PostgreSQL Driver Versions: using org.postgresql.Driver | ||
| Supports Global | Selected | ||
| One-Phase Commit | Selected | ||
| 13. | Set connection properties. Sample properties for a PostgreSQL database are: |
| Parameter Name | JasperReports Server | Foodmart Example | Sugar CRM Example |
|---|---|---|---|
| Database Name | jasperserver | foodmart | sugarcrm |
| Host Name | localhost | ||
| Port | 5432 | ||
| Database User Name | postgres | ||
| Password | postgres | ||
| Confirm Password | postgres | ||
| 14. | Test the database connection: |
| a. | For SugarCRM and Foodmart, use the default connections: |
jdbc:postgresql://localhost:5432/sugarcrm
jdbc:postgresql://localhost:5432/foodmart
| b. | Change the URL for the jasperserver database to: |
jdbc:postgresql://localhost:5432/jasperserver
| 15. | Select targets and ensure that AdminServer is set for all data sources. |
| 16. | In WebLogic, open an Administrative Console window and navigate to Services > Data Sources or Domain Configurations > Services > Data Sources |
| 17. | Select already created datasource (JasperServerDataBase, FoodmartDataBase, SugarcrmDataBase) |
| 18. | Select Connection Pool tab->change Maximum Capacity setting from 15 to 50 or more. |
| 19. | Click Save |
| 20. | Use the Java jar tool or an unzip tool to unpack the jasperserver-pro.war file. For example, using the Java jar tool, enter these commands to unpack the jasperserver-pro.war file to a folder: |
cd <js-install-dir>mkdir jasperserver-procd jasperserver-pro"%JAVA_HOME%/bin/jar" xvf ../jasperserver-pro.war[/code] |
| 21. | (If you're using WebLogic 12c, skip this step.) Search for conflicting JARs and delete them from the WAR file. If the following JARs are present in your WebLogic installation, you need to delete them from your JasperReports Server installation to avoid conflicts. To do this: |
| a. | Search your WebLogic installation for these files: |
jaxb-api-<ver>.jar
jaxb-impl-<ver>.jar
serializer-<ver>.jar
stax-api-<ver>.jar
xalan-<ver>.jar
xercesImpl-<ver>.jar
xml-apis-<ver>.jar
| b. | Change to the JasperReports Server WEB-INF/lib directory: |
cd <js-install>/jasperserver-pro/WEB-INF/lib
| c. | Delete any conflicting JARs, but save a copy of them to a temporary location. |
If you experience a problem with OLAP Views, you need these JARs for the workaround described in Troubleshooting Problems with OLAP Views.
| 22. | If you're using WebLogic 10.3.6, you need to replace xml-apis-1.3.04.jar with xml-apis-2.10.0.jar. If you're using WebLogic 10.3.5 or WebLogic 12c, skip this step. To update the JAR: |
| a. | Go to the WEB-INF/lib directory. |
| b. | Copy xml-apis-2.10.0.jar from <js-install>/buildomatic/install_resources/extra-jars |
| c. | Remove xml-apis-1.3.04.jar. |
| 23. | Update your Hibernate, Quartz, and Mail Server configuration: |
| a. | The buildomatic logic has already configured the hibernate.properties and js.quartz.properties files for your database type. So you can copy these files to the jasperserver-pro file as shown below. |
Copy from:
<js-install>/buildomatic/build_conf/default/webapp/WEB-INF/hibernate.properties
<js-install>/buildomatic/build_conf/default/webapp/WEB-INF/js.quartz.properties
To:
jasperserver-pro/WEB-INF
| b. | Edit the scheduler URI port value for WebLogic in the js.quartz.properties: |
Edit js.quartz.properties:
Set :
report.scheduler.web.deployment.uri=http://localhost:8080/jasperserver-pro
To:
report.scheduler.web.deployment.uri=http://localhost:7001/jasperserver-pro
| c. | If you want to configure JasperReports Server to automatically schedule and email reports, enter your mail server information in the js.quartz.properties file. Modify all report.scheduler.mail.sender.* properties as necessary for your mail server. |
| 24. | If your mail server requires authentication, edit the applicationContext-report-scheduling.xml file: |
| a. | Open the jasperserver-pro/WEB-INF/applicationContext-report-scheduling.xml file for editing and locate the reportSchedulerMailSender bean. |
| b. | Set the javaMailProperties key="mail.smtp.auth" value to true. |
| 25. | Now you can change to the jasperserver-pro folder and re-archive the jasperserver-pro.war file, using commands such as the following: |
| Commands | Description |
| cd ../.. | Changes to the jasperserver-pro folder |
| mv ../jasperserver-pro.war ../BAK-jasperserver-pro.war | Renames the original jasperserver-pro.war file. |
| "%JAVA_HOME%/bin/jar" cvf ../jasperserver-pro.war * | Re-archives the jasperserver-pro.war file. |
| cd .. mv jasperserver-pro BAK-jasperserver-pro | Renames the unneeded working folder to a backup location. |
| | You now have a jasperserver-pro.war file you can use for deploying to WebLogic. |
| 26. | Edit your WebLogic domain configuration file <wl-domain>/config/config.xml: |
| | <wl-domain> is the path of the domain within WebLogic that contains your JasperReports Server deployment. For example <weblogic>/samples/domains/wl_server. |
| a. | Locate the server and security-configuration elements, and insert the following parameters: |
| b. | Check that the stuck-thread-max-time element appears above the listen-address element before the closing </server> tag. |
| | In some cases, setting the stuck-thread-max-time may cause a schema validation error. In this case, you can try removing this line from the configuration file. |
| 27. | Edit the setdomainEnv file to force WebLogic to use the correct version of the Joda time library, which is shipped with JasperReports Server. By default, the Joda time library is in: |
<js-install>/buildomatic/conf_source/iePro/lib.
| • | Windows: Edit the setDomainEnv.bat file and add this line: |
set PATCH_CLASSPATH=${PATH TO NEW JODA LIBRARY}joda-time-2.3.jar
| • | Linux: Edit the setDomainEnv.sh file and add this line: |
export PATCH_CLASSPATH=${PATH TO NEW JODA LIBRARY}/joda-time-2.3.jar
| 28. | Set JVM options as described in Setting Java Properties. |
Deploy JasperReports Server to WebLogic:
| 1. | Enable the Lock & Edit button: |
| a. | Select the Preferences link at the top of the Admin console |
| b. | Scroll to the bottom of the User Preferences screen and deselect Automatically Acquire Lock and Activate Changes. |
| c. | Save. |
| 2. | In the Administrative Console, click the Lock & Edit button and navigate to Deployments. |
| 3. | On the Deployments page click the Install button. |
| 4. | Select the path to <js-install>. Click Next. |
| 5. | Leave the radio button selected for Install this deployment as an application. Click Next. |
| 6. | When prompted, enter the following parameter values: |
| Parameter Name | Example Value |
| Name | jasperserver-pro |
| Security | Custom Roles and Policies |
| Source accessibility | Use the defaults defined by the deployment's targets |
| 7. | Review your choices and click Finish. |
| 8. | Click Save. |
Recommended Comments
There are no comments to display.