David Ghedini – Page 11 – Tomcat, PostgreSQL, and GIS

Install GlassFish 3.1 on CentOS or RHEL

Posted on January 11, 2013 | by David Ghedini | Leave a Comment

Install GlassFish 3.1 on CentOS or RHEL
Published (Last updated 11/01/2013 05:28 AM)
Permalink https://davidghedini.com/pg/entry/install_glassfish_3_1_on
This post will cover installing GlassFish 3.1 on CentOS or RHEL.

We’ll also see how to run GlassFish as a service, how to access the Admin Console, and how to run GlassFish under a minimally privileged user.

GlassFish 3.1 is the latest release and is available as GlassFish Server Open Source Edition 3.1 (free) and Oracle GlassFish Server 3.1 (supported and requires paid subscription).

I installed both using the same process below.

The procedure is the same as with 3.0.1 with some minor changes.

If you do not already have the Java Development Kit (JDK) installed on your machine, you will need to download and install the required JDK for your platform.

If you do have the JDK installed, you can skip to: Step 2: Download and Install the GlassFish 3.1 Server:

Step 1: Install the JDK

You can download the JDK here: http://www.oracle.com/technetwork/java/javase/downloads/index.html

I’m using the latest, which is JDK 6, update 24. The JDK is specific to 32 and 64 bit versions.

My CentOS box is 64 bit, so I’ll need: jdk-6u24-linux-x64.bin.

If you are on 32 bit, you’ll need: jdk-6u24-linux-i586.bin

Download the appropriate JDK and save it to a directory. I’m saving it to /root.

Move (mv) or copy (cp) the file to the /opt directory:

[root@sv2 ~]# mv jdk-6u24-linux-x64.bin /opt/jdk-6u24-linux-x64.bin

1	[root@sv2 ~]# mv jdk-6u24-linux-x64.bin /opt/jdk-6u24-linux-x64.bin

Create the directory /usr/java.

[root@sv2 ~]# mkdir /usr/java

1	[root@sv2 ~]# mkdir /usr/java

Change to the /usr/java directory we created and install the JDK using ‘sh /opt/jdk-6u24-linux-x64.bin’

[root@sv2 ~]# cd /usr/java
[root@sv2 java]# sh /opt/jdk-6u24-linux-x64.bin

1 2	[root@sv2 ~]# cd /usr/java [root@sv2 java]# sh /opt/jdk-6u24-linux-x64.bin

Set the JAVA_HOME path. This is where we installed the JDK above.

To do this for your current session, you can issue the following:

[root@sv2 java]# JAVA_HOME=/usr/java/jdk1.6.0_24
[root@sv2 java]# export JAVA_HOME
[root@sv2 java]# PATH=$JAVA_HOME/bin:$PATH
[root@sv2 java]# export PATH

[root@sv2 java]# JAVA_HOME=/usr/java/jdk1.6.0_24

[root@sv2 java]# export JAVA_HOME

[root@sv2 java]# PATH=$JAVA_HOME/bin:$PATH

[root@sv2 java]# export PATH

To set the JAVA_HOME for users, we add this to the user ~/.bashrc or ~/.bash_profile of the user. We can also add it /etc/profile and then source it to give to all users.

JAVA_HOME=/usr/java/jdk1.6.0_24 
export JAVA_HOME 
PATH=$JAVA_HOME/bin:$PATH 
export PATH

JAVA_HOME=/usr/java/jdk1.6.0_24

export JAVA_HOME

PATH=$JAVA_HOME/bin:$PATH

export PATH

Once you have added the above to ~/.bash_profile or ~/.bashrc, you should log out, then log back in and check that the JAVA_HOME is set correctly.

[root@sv2 ~]#  echo $JAVA_HOME
/usr/java/jdk1.6.0_24

1 2	[root@sv2 ~]# echo $JAVA_HOME /usr/java/jdk1.6.0_24

Step 2: Download and Install the GlassFish 3.1 Server:

You can download both the GlassFish Server Open Source Edition 3.1 and Oracle GlassFish Server 3.1 at http://glassfish.java.net/

Once you have downloaded the desired file, move (mv) or copy (cp) the file to /usr/share/glassfish-3.1.zip (or /usr/share/ogs-3.1.zip for Oracle GlassFish).

[root@sv2 ~]# mv glassfish-3.1.zip /usr/share/glassfish-3.1.zip

1	[root@sv2 ~]# mv glassfish-3.1.zip /usr/share/glassfish-3.1.zip

Change to the /usr/share directory and unzip the file:

[root@sv2 ~]# cd /usr/share
[root@sv2 share]# unzip -q glassfish-3.1.zip

1 2	[root@sv2 ~]# cd /usr/share [root@sv2 share]# unzip -q glassfish-3.1.zip

The unzip will create the following directory: /usr/share/glassfish3

Note: Both GlassFish editions will create the same directory when unzipped: glassfish3

Step 3: Running GlassFish as a Service.

To run GlassFish as a service and enable start up at boot, we’ll now create a Start/Stop/Restart script.

We’ll create the script as /etc/init.d/glassfish, make the script executable, and then add our new glassfish service to chkconfig.

Create our glassfish script:

[root@sv2 ~]# cd /etc/init.d
[root@sv2 init.d]# vi glassfish

1 2	[root@sv2 ~]# cd /etc/init.d [root@sv2 init.d]# vi glassfish

#!/bin/bash
# description: Glassfish Start Stop Restart
# processname: glassfish
# chkconfig: 234 20 80
JAVA_HOME=/usr/java/jdk1.6.0_24
export JAVA_HOME
PATH=$JAVA_HOME/bin:$PATH
export PATH
GLASSFISH_HOME=/usr/share/glassfish3/glassfish

case $1 in
start)
sh $GLASSFISH_HOME/bin/asadmin start-domain domain1
;;
stop)
sh $GLASSFISH_HOME/bin/asadmin stop-domain domain1
;;
restart)
sh $GLASSFISH_HOME/bin/asadmin stop-domain domain1
sh $GLASSFISH_HOME/bin/asadmin start-domain domain1
;;
esac
exit 0

#!/bin/bash

# description: Glassfish Start Stop Restart

# processname: glassfish

# chkconfig: 234 20 80

JAVA_HOME=/usr/java/jdk1.6.0_24

export JAVA_HOME

PATH=$JAVA_HOME/bin:$PATH

export PATH

GLASSFISH_HOME=/usr/share/glassfish3/glassfish

case $1 in

start)

sh $GLASSFISH_HOME/bin/asadmin start-domain domain1

;;

stop)

sh $GLASSFISH_HOME/bin/asadmin stop-domain domain1

;;

restart)

sh $GLASSFISH_HOME/bin/asadmin stop-domain domain1

sh $GLASSFISH_HOME/bin/asadmin start-domain domain1

;;

esac

exit 0

If you do not set the JAVA_HOME and PATH in the GlassFish script, when you attempt to start the GlassFish server it will complain it cannot find Java with the following:

error: /usr/share/glassfish3/glassfish/bin/asadmin: line 19: exec: java: not found

Now, make the script executable and add it to our chkconfig so it starts at boot.

[root@sv2 init.d]# chmod 755 glassfish
[root@sv2 init.d]# chkconfig --add glassfish
[root@sv2 init.d]# chkconfig --level 234 glassfish on

[root@sv2 init.d]# chmod 755 glassfish

[root@sv2 init.d]# chkconfig --add glassfish

[root@sv2 init.d]# chkconfig --level 234 glassfish on

We should now be able to Start, Stop, and Restart GlassFish as a service.

Start GlassFish:

[root@sv2 init.d]# service glassfish start
Waiting for domain1 to start .........
Successfully started the domain : domain1
domain  Location: /usr/share/glassfish3/glassfish/domains/domain1
Log File: /usr/share/glassfish3/glassfish/domains/domain1/logs/server.log
Admin Port: 4848
Command start-domain executed successfully.

[root@sv2 init.d]# service glassfish start

Waiting for domain1 to start .........

Successfully started the domain : domain1

domain Location: /usr/share/glassfish3/glassfish/domains/domain1

Log File: /usr/share/glassfish3/glassfish/domains/domain1/logs/server.log

Admin Port: 4848

Command start-domain executed successfully.

Stop GlassFish:

[root@sv2 init.d]# service glassfish stop
Waiting for the domain to stop ....
Command stop-domain executed successfully.

[root@sv2 init.d]# service glassfish stop

Waiting for the domain to stop ....

Command stop-domain executed successfully.

Step 4: Check Homepage.

You should now see the GlassFish default home page at http://youdomain.com:8080 or http://YourIP:8080

If you do not see the home page, check the logs and insure that port 8080 is open and available.

Step 5: Access GlassFish Admin Console.

You should now be able to access the GlassFish Admin Console at:

http://yourdomain.com:4848 or http://yourip:4848

On accessing the GlassFish Admin Console for the first time, you will find that no user name or password is required.

Previous to 3.1, a default password ‘adminadmin’ was used.

You can set (or change) the admin password within the GlassFish Admin console.

1. Click “Domain” on the tree.

2. Click the Administrator Password tab.

3. Enter and confirm your password and click Save.

4. Note that the “Logout” button now appears at top right.

The first password save will create a file,.asadminpass, in the home directory of the user you are running the service under.

Alternatively, you can set the admin password via the CLI using.

[root@sv2 bin]# $GLASSFISH_HOME/bin/asadmin change-admin-password
Enter admin user name [default: admin]&gt;
Enter admin password&gt;
Enter new admin password&gt;
Enter new admin password again&gt;

Command change-admin-password executed successfully.
[root@sv2 bin]#

[root@sv2 bin]# $GLASSFISH_HOME/bin/asadmin change-admin-password

Enter admin user name [default: admin]>

Enter admin password>

Enter new admin password>

Enter new admin password again>

Command change-admin-password executed successfully.

[root@sv2 bin]#

Step 6: Running GlassFish with Minimally Privileged (non-root) User.

Since I am installing this on my development machine, I am running GlassFish as root above.

In production, you will want to run GlassFish as a non-root user with minimal privileges.

To do this, we can need to the following.

1. Create the user, glassfish, who will own the files.

Create the new group, glassfish, and add the user glassfish to the group:

[root@sv2 ~]# groupadd glassfish
[root@sv2 ~]# useradd -s /bin/bash -g glassfish glassfish

1 2	[root@sv2 ~]# groupadd glassfish [root@sv2 ~]# useradd -s /bin/bash -g glassfish glassfish

2. Change ownership of the GlassFish files to the user glassfish we created.

We’ll change ownership of the files under /usr/share/glassfish3 from root to the user glassfish we created above:

[root@sv2 ~]# chown -Rf glassfish.glassfish /usr/share/glassfish3/

1	[root@sv2 ~]# chown -Rf glassfish.glassfish /usr/share/glassfish3/

3. Update our glassfish script.

Finally, we update the glassfish start/stop/restart script we created above so we su to user glassfish:

#!/bin/bash
# description: Glassfish Start Stop Restart
# processname: glassfish
# chkconfig: 234 20 80
JAVA_HOME=/usr/java/jdk1.6.0_24
export JAVA_HOME
PATH=$JAVA_HOME/bin:$PATH
export PATH
GLASSFISH_HOME=/usr/share/glassfish3/glassfish
GLASSFISH_USER=glassfish

case $1 in
start)
su $GLASSFISH_USER -c "$GLASSFISH_HOME/bin/asadmin start-domain domain1"
;;
stop)
su $GLASSFISH_USER -c "$GLASSFISH_HOME/bin/asadmin stop-domain domain1"
;;
restart)
su $GLASSFISH_USER -c "$GLASSFISH_HOME/bin/asadmin stop-domain domain1"
su $GLASSFISH_USER -c "$GLASSFISH_HOME/bin/asadmin start-domain domain1"
;;
esac
exit 0

#!/bin/bash

# description: Glassfish Start Stop Restart

# processname: glassfish

# chkconfig: 234 20 80

JAVA_HOME=/usr/java/jdk1.6.0_24

export JAVA_HOME

PATH=$JAVA_HOME/bin:$PATH

export PATH

GLASSFISH_HOME=/usr/share/glassfish3/glassfish

GLASSFISH_USER=glassfish

case $1 in

start)

su $GLASSFISH_USER -c "$GLASSFISH_HOME/bin/asadmin start-domain domain1"

;;

stop)

su $GLASSFISH_USER -c "$GLASSFISH_HOME/bin/asadmin stop-domain domain1"

;;

restart)

su $GLASSFISH_USER -c "$GLASSFISH_HOME/bin/asadmin stop-domain domain1"

su $GLASSFISH_USER -c "$GLASSFISH_HOME/bin/asadmin start-domain domain1"

;;

esac

exit 0

Step 7: Running GlassFish on Port 80 as Non-Root User.

To run services below port 1024 as user other than root, you will need to use port forwarding.

You can do this by adding the following to your IP tables:

[root@sv2 ~]# iptables -t nat -A PREROUTING -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 8080
[root@sv2 ~]# iptables -t nat -A PREROUTING -p udp -m udp --dport 80 -j REDIRECT --to-ports 8080

1 2	[root@sv2 ~]# iptables -t nat -A PREROUTING -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 8080 [root@sv2 ~]# iptables -t nat -A PREROUTING -p udp -m udp --dport 80 -j REDIRECT --to-ports 8080

JasperReportsIntegration 2.0.0 Beta on JBoss 7

Posted on March 6, 2012 | by David Ghedini | Leave a Comment

Dietmar Aust / Opal Consulting have released JasperReportsIntegration 2.0.0 Beta for testing.

You can see the announcement here

It is has some amazing new features, is updated for JasperReports 4.7.0, and has a new deployment model.

Most importantly, the new version allows you to easily run JasperReportsIntegration on JBoss 🙂

If you don’t have JBoss 7.1.1 installed, you can follow my tutorial here:

One important note – it did not work for me with JDK 1.7 but worked wonderfully with JDK 1.6

The zip file contains the required items for deployment on JBoss as well as items for Oracle (/sql directory) and Apex (/apex directory), it also contains some scripts to run in standalone mode as well as Jetty.

1. Create a directory under /usr/share to be the home for under JasperReportsIntegration

[root@dev2 ~]# mkdir /usr/share/JasperReportsIntegration

1	[root@dev2 ~]# mkdir /usr/share/JasperReportsIntegration

2. Change to the new directory:

[root@dev2 ~]# cd /usr/share/JasperReportsIntegration

1	[root@dev2 ~]# cd /usr/share/JasperReportsIntegration

3. Download the kit from Opal:

Or use wget:

[root@dev2 JasperReportsIntegration]# wget http://www.opal-consulting.de/downloads/free_tools/JasperReportsIntegration/2.0.0/JasperReportsIntegration-2.0.0.0.zip
--2012-08-07 03:43:35--  http://www.opal-

consulting.de/downloads/free_tools/JasperReportsIntegration/2.0.0/JasperReportsIntegration-2.0.0.0.zip
Resolving www.opal-consulting.de... 213.185.81.187
Connecting to www.opal-consulting.de|213.185.81.187|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 82738852 (79M) [application/zip]
Saving to: `JasperReportsIntegration-2.0.0.0.zip'

100%[======================================&gt;] 82,738,852  2.26M/s   in 37s

2012-08-07 03:44:12 (2.13 MB/s) - `JasperReportsIntegration-2.0.0.0.zip' saved [82738852/82738852]

[root@dev2 JasperReportsIntegration]# wget http://www.opal-consulting.de/downloads/free_tools/JasperReportsIntegration/2.0.0/JasperReportsIntegration-2.0.0.0.zip

--2012-08-07 03:43:35-- http://www.opal-

consulting.de/downloads/free_tools/JasperReportsIntegration/2.0.0/JasperReportsIntegration-2.0.0.0.zip

Resolving www.opal-consulting.de... 213.185.81.187

Connecting to www.opal-consulting.de|213.185.81.187|:80... connected.

HTTP request sent, awaiting response... 200 OK

Length: 82738852 (79M) [application/zip]

Saving to: `JasperReportsIntegration-2.0.0.0.zip'

100%[======================================>] 82,738,852 2.26M/s in 37s

2012-08-07 03:44:12 (2.13 MB/s) - `JasperReportsIntegration-2.0.0.0.zip' saved [82738852/82738852]

3. unzip it.

[root@dev2 JasperReportsIntegration]# unzip -q JasperReportsIntegration-2.0.0.0.zip

1	[root@dev2 JasperReportsIntegration]# unzip -q JasperReportsIntegration-2.0.0.0.zip

4. Your directory will look like this:

[root@dev2 JasperReportsIntegration]# ls -l
total 80944
drwxr-xr-x 2 root root     4096 Aug  6 17:49 apex
drwxr-xr-x 2 root root     4096 Aug  6 17:49 bin
drwxr-xr-x 2 root root     4096 Aug  7 05:30 conf
-rw-r--r-- 1 root root      204 Aug  6 17:49 deployJasperReportsIntegration.cmd
-rw-r--r-- 1 root root      178 Aug  6 17:49 deployJasperReportsIntegration.sh
drwxr-xr-x 3 root root     4096 Aug  6 17:49 doc
-rw-r--r-- 1 root root      341 Aug  6 17:49 Index.html
-rw-r--r-- 1 root root 82738852 Aug  6 19:57 JasperReportsIntegration-2.0.0.0.zip
drwxr-xr-x 3 root root     4096 Aug  6 17:49 jetty
drwxr-xr-x 2 root root     4096 Aug  6 17:49 lib
drwxr-xr-x 2 root root     4096 Aug  6 17:48 logs
drwxr-xr-x 5 root root     4096 Aug  7 05:33 reports
drwxr-xr-x 5 root root     4096 Aug  6 17:49 sql
-rw-r--r-- 1 root root      793 Aug  6 17:49 startJasperReportsIntegration.cmd
-rw-r--r-- 1 root root      772 Aug  6 17:49 startJasperReportsIntegration.sh
drwxr-xr-x 2 root root     4096 Aug  6 17:49 webapp

[root@dev2 JasperReportsIntegration]# ls -l

total 80944

drwxr-xr-x 2 root root 4096 Aug 6 17:49 apex

drwxr-xr-x 2 root root 4096 Aug 6 17:49 bin

drwxr-xr-x 2 root root 4096 Aug 7 05:30 conf

-rw-r--r-- 1 root root 204 Aug 6 17:49 deployJasperReportsIntegration.cmd

-rw-r--r-- 1 root root 178 Aug 6 17:49 deployJasperReportsIntegration.sh

drwxr-xr-x 3 root root 4096 Aug 6 17:49 doc

-rw-r--r-- 1 root root 341 Aug 6 17:49 Index.html

-rw-r--r-- 1 root root 82738852 Aug 6 19:57 JasperReportsIntegration-2.0.0.0.zip

drwxr-xr-x 3 root root 4096 Aug 6 17:49 jetty

drwxr-xr-x 2 root root 4096 Aug 6 17:49 lib

drwxr-xr-x 2 root root 4096 Aug 6 17:48 logs

drwxr-xr-x 5 root root 4096 Aug 7 05:33 reports

drwxr-xr-x 5 root root 4096 Aug 6 17:49 sql

-rw-r--r-- 1 root root 793 Aug 6 17:49 startJasperReportsIntegration.cmd

-rw-r--r-- 1 root root 772 Aug 6 17:49 startJasperReportsIntegration.sh

drwxr-xr-x 2 root root 4096 Aug 6 17:49 webapp

5. Change to the webapp directory and locate JasperReportsIntegration.war:

[root@dev2 JasperReportsIntegration]# cd webapp
[root@dev2 JasperReportsIntegration]# ls -l
total 66508
-rw-r--r-- 1 root root 68028460 Aug  6 17:49 JasperReportsIntegration.war
[root@dev2 webapp]#

[root@dev2 JasperReportsIntegration]# cd webapp

[root@dev2 JasperReportsIntegration]# ls -l

total 66508

-rw-r--r-- 1 root root 68028460 Aug 6 17:49 JasperReportsIntegration.war

[root@dev2 webapp]#

6. Move the JasperReportsIntegration.war to JBOSS_HOME/standalone/deployments

In my case /usr/share/jboss-as/standalone/deployments:

[root@dev2 webapp]# mv JasperReportsIntegration.war  /usr/share/jboss-as/standalone/deployments/JasperReportsIntegration.war

1	[root@dev2 webapp]# mv JasperReportsIntegration.war /usr/share/jboss-as/standalone/deployments/JasperReportsIntegration.war

7. Once you have moved the WAR, delete the webapp directory along with the following:

[root@dev2 JasperReportsIntegration]# rm -rf webapp/
[root@dev2 JasperReportsIntegration]# rm -rf jetty/
[root@dev2 JasperReportsIntegration]# rm -rf apex/
[root@dev2 JasperReportsIntegration]# rm -rf sql/
[root@dev2 JasperReportsIntegration]# rm -f deployJasperReportsIntegration.cmd
[root@dev2 JasperReportsIntegration]# rm -f deployJasperReportsIntegration.sh
[root@dev2 JasperReportsIntegration]# rm -f startJasperReportsIntegration.sh 
[root@dev2 JasperReportsIntegration]# rm -f startJasperReportsIntegration.cmd
[root@dev2 JasperReportsIntegration]# rm -f JasperReportsIntegration-2.0.0.0.zip

[root@dev2 JasperReportsIntegration]# rm -rf webapp/

[root@dev2 JasperReportsIntegration]# rm -rf jetty/

[root@dev2 JasperReportsIntegration]# rm -rf apex/

[root@dev2 JasperReportsIntegration]# rm -rf sql/

[root@dev2 JasperReportsIntegration]# rm -f deployJasperReportsIntegration.cmd

[root@dev2 JasperReportsIntegration]# rm -f deployJasperReportsIntegration.sh

[root@dev2 JasperReportsIntegration]# rm -f startJasperReportsIntegration.sh

[root@dev2 JasperReportsIntegration]# rm -f startJasperReportsIntegration.cmd

[root@dev2 JasperReportsIntegration]# rm -f JasperReportsIntegration-2.0.0.0.zip

4. You should now be left with the following:

[root@dev2 JasperReportsIntegration]# ls
bin  conf  doc  Index.html  lib  logs  reports

1 2	[root@dev2 JasperReportsIntegration]# ls bin conf doc Index.html lib logs reports

If you are running under the user jboss, change ownership of the logs directory at /usr/share/JasperReportsIntegration/logs to the user jboss

[root@dev2 JasperReportsIntegration]# chown -Rf jboss.jboss /usr/share/JasperReportsIntegration/logs

1	[root@dev2 JasperReportsIntegration]# chown -Rf jboss.jboss /usr/share/JasperReportsIntegration/logs

5. Change to the conf directory, where you will find application.properties and log4jproperties:

[root@dev2 JasperReportsIntegration]# cd conf
[root@dev2 conf]# ls
application.properties  log4j.properties

[root@dev2 JasperReportsIntegration]# cd conf

[root@dev2 conf]# ls

application.properties log4j.properties

6. The application.properties will look as below:

Change the data sources to your own.

Note that one of the verification tests later will look for a data source with the name ‘default’, so may want to leave one named as ‘default’.

#====================================================================
# Application properties (global)
#====================================================================
[application]
jndiPrefix=java:comp/env/jdbc/

#====================================================================
# 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=my_oracle_user
password=my_oracle_user_pwd

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

#====================================================================
# Direct printing
#====================================================================
[directPrinting]
isEnabled=true

# for debugging purposes does it make sense to display the 
# print dialog ON THE SERVER before printing. You can even cancel the 
# request through the print dialog
# DONT do that in production!!!
displayPrintDialog=false

#====================================================================
## Syntax for specifying properties: 
## http://commons.apache.org/configuration/userguide/howto_basicfeatures.html#Basic_features_and_AbstractConfiguration
#====================================================================

#====================================================================

# Application properties (global)

#====================================================================

[application]

jndiPrefix=java:comp/env/jdbc/

#====================================================================

# 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=my_oracle_user

password=my_oracle_user_pwd

#====================================================================

# JDBC datasource configuration

# http://www.orafaq.com/wiki/JDBC#Thin_driver

#====================================================================

[datasource:test]

name=test

url=jdbc:oracle:thin:@192.168.2.114:1521:XE

username=my_oracle_user

password=my_oracle_user_pwd

#====================================================================

# Direct printing

#====================================================================

[directPrinting]

isEnabled=true

# for debugging purposes does it make sense to display the

# print dialog ON THE SERVER before printing. You can even cancel the

# request through the print dialog

# DONT do that in production!!!

displayPrintDialog=false

#====================================================================

## Syntax for specifying properties:

## http://commons.apache.org/configuration/userguide/howto_basicfeatures.html#Basic_features_and_AbstractConfiguration

#====================================================================

7. Placing OC_JASPER_CONFIG_HOME into the path of JBoss.

Where you place the path to OC_JASPER_CONFIG_HOME depends on the user you running JBoss under.

If you are running JBoss under the user jboss, you need to add the path to OC_JASPER_CONFIG_HOME to the .bash_profile of user jboss.

If you are running JBoss under the user root, you need to add the path to OC_JASPER_CONFIG_HOME to the .bash_profile of the user root.

If you simply place the path into the Jboss init script (JBOSS_HOME/bin/jboss-as-standalone.sh) or into your jboss script under /etc/init.d, it will throw the following error as JBoss will look for the application.properties file under ../JasperReportsIntegration.war-xxx/conf/application.properties:

net.sf.jasperreports.engine.JRRuntimeException: File /usr/share/jboss-as/standalone/tmp/vfs/temp38167c0517128991/JasperReportsIntegration.war-d170f314ce444645/conf/application.properties not found.
	de.oc.integration.jasper.webapp.AppContext.loadApplicationProperties(AppContext.java:144)
	de.oc.integration.jasper.webapp.ReportWrapper.service(ReportWrapper.java:152)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

net.sf.jasperreports.engine.JRRuntimeException: File /usr/share/jboss-as/standalone/tmp/vfs/temp38167c0517128991/JasperReportsIntegration.war-d170f314ce444645/conf/application.properties not found.

de.oc.integration.jasper.webapp.AppContext.loadApplicationProperties(AppContext.java:144)

de.oc.integration.jasper.webapp.ReportWrapper.service(ReportWrapper.java:152)

javax.servlet.http.HttpServlet.service(HttpServlet.java:847)

So, add the following to the .bash_profile of the user your running jboss under (jboss or root):

OC_JASPER_CONFIG_HOME=/usr/share/JasperReportsIntegration  
export OC_JASPER_CONFIG_HOME

1 2	OC_JASPER_CONFIG_HOME=/usr/share/JasperReportsIntegration export OC_JASPER_CONFIG_HOME

Along with JAVA_HOME and bin paths (and any others you have), your jboss (or root) user bash_profile would look something like:

JAVA_HOME=/usr/java/jdk1.6.0_33
export JAVA_HOME
PATH=$JAVA_HOME/bin:$PATH
export PATH
OC_JASPER_CONFIG_HOME=/usr/share/JasperReportsIntegration
export OC_JASPER_CONFIG_HOME

JAVA_HOME=/usr/java/jdk1.6.0_33

export JAVA_HOME

PATH=$JAVA_HOME/bin:$PATH

export PATH

OC_JASPER_CONFIG_HOME=/usr/share/JasperReportsIntegration

export OC_JASPER_CONFIG_HOME

8. Install the SQL into the user schema

This bit has not changed.

Connect to your database server and change directories to the location you uploaded the /sql directory.

Connect to SQL*Plus as the required user and run @user_install.sql

[root@or2 JRI2]# cd sql
[root@or2 sql]# ls
sys_install_acl.sql  sys_remove.sql    user_remove.sql  xlib_jasperreports
sys_install.log      user_install.log  xlib_base        xlib_status.sql
sys_install.sql      user_install.sql  xlib_http        xlib_status_sys.sql
[root@or2 sql]# sqlplus /nolog

SQL*Plus: Release 11.2.0.3.0 Production on Mon Aug 6 20:39:01 2012

Copyright (c) 1982, 2011, Oracle.  All rights reserved.

SQL&gt; connect soctt/tiger
Connected.
SQL&gt; @user_install.sql

[root@or2 JRI2]# cd sql

[root@or2 sql]# ls

sys_install_acl.sql sys_remove.sql user_remove.sql xlib_jasperreports

sys_install.log user_install.log xlib_base xlib_status.sql

sys_install.sql user_install.sql xlib_http xlib_status_sys.sql

[root@or2 sql]# sqlplus /nolog

SQL*Plus: Release 11.2.0.3.0 Production on Mon Aug 6 20:39:01 2012

SQL> connect soctt/tiger

Connected.

SQL> @user_install.sql

Make sure it compiles with no errors.

9. Install the f860_JasperIntegrationTest_2.0.0.0.sql Application

Import the f860_JasperIntegrationTest_2.0.0.0.sql into your work space.

The new testing application has some new features as you can see below.

10. Verify your installation.

In the screenshot below, you can see I did not use the name ‘default’ for any of my data sources.

11. Test your reports.

Among other new features, there is now a “Save File on Server” option. This allows you to save the generated report on the file system of the application server (jboss). You need to supply the full OS path. One additional note, if you are running as user jboss you will only be able to save into directories owned by jboss (or made available to user jboss). If you are running a root, of course, you can save anywhere on the server.

There is the file, fromapp.pdf, saved to server in above screen shot.

[root@dev2 jboss]# ls -l
total 8
-rw-rw-r-- 1 jboss jboss 2153 Aug  7 06:48 fromapp.pdf

[root@dev2 jboss]# ls -l

total 8

-rw-rw-r-- 1 jboss jboss 2153 Aug 7 06:48 fromapp.pdf

Cool beans. Hoping to learn a lot more about this

Official Installation Guide