Deploying to Resin 4.0.62
This topic introduces how to deploy Logi JReport Server to Resin. The example directory paths listed below are based on Unix. The instructions are applicable to both Unix and Windows installations; however, the format of the paths for Windows would use the Windows format, that is,
C:\JReport\Server instead of
It is assumed that:
- Resin 4.0.62 is installed in the
- The Logi JReport Server WAR file jreport.war is located in the
/opt/JReport/Server/bin/distributedirectory. To create the WAR file refer to the instructions in Building a WAR/EAR File to Include a Self-contained Logi JReport Server.
To deploy Logi JReport Server to Resin 4.0.62:
- Generate the password.
- Modify resin.properties in
/opt/resin/conf. Set remote_admin_enable to true and add the generated password.
- Enable the commands that allow administrators and programmers perform debugging and monitoring tasks on remote Resin server using command line.
By default these commands are disabled. Enabling the command requires ManagerService be registered in resin.xml file. Since the default resin.xml already includes a <resin:AdminAuthenticator> with a <resin:import>, you can just reuse the admin configuration from the /resin-admin page.
- Start Resin 4.0.62 by running the resin.sh start script in
- Log onto the Resin 4.0.62 Administration Console with the specified user name and password using the URL
- In the deploy tab, select Browse to select the file jreport.war. In the Name text box, type in jreport. Then select Deploy.
- Access Logi JReport Server using the following URLs:
If you run into problems when using Logi JReport Server in Resin, send the log files of Logi JReport Server to firstname.lastname@example.org. The following procedure illustrates how to generate the log files:
- Modify the file resin.sh in
/opt/resin/binby adding -Dlogall=true after the reporthome definition:
"$JAVA" $JAVA_OPTS \
-classpath "$RESIN_CLASSPATH" -Dreporthome=/opt/JReport/Server \
- Run the modified resin.sh to start Resin.
- After reproducing the problem, send email@example.com the log files in
The Resin log files may also help to identify the problem. The most useful one is /opt/Resin/server/default/log/server.log.