Previous Topic  Next Topic

Deploying Server to Resin 4.0.65

This topic describes how you can deploy Logi Report Server to Resin.

We use paths based on UNIX path name protocol in our example. The instruction applies to both UNIX and Windows installation. However, the path formats differ. For Windows it is in this format C:\LogiReport\Server instead of /opt/LogiReport/Server.

Assume that:

• You installed Resin 4.0.65 in the /opt/resin directory.
• The Logi Report Server WAR file jreport.war is in the /opt/LogiReport/Server/bin/distribute directory. To create the WAR file, see Building a WAR/EAR File to Include a Self-contained Logi Report Server.

To deploy Logi Report Server to Resin 4.0.65:

1. Generate the password.

   

2. Modify resin.properties in /opt/resin/conf. Set remote_admin_enable to true and add the generated password.

   

3. Enable the commands that allow administrators and programmers to perform debugging and monitoring tasks on the 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.

   

4. Start Resin 4.0.65 by running the resin.sh start script in /opt/resin/bin.
5. Sign in to the Resin 4.0.65 Administration Console with the specified username and password using the URL http://localhost:8080/resin-admin/index.php.
6. In the deploy tab, select Browse to select the file jreport.war. In the Name text box, type jreport. Then select Deploy.
7. Access Logi Report Server using the following URLs:

   http://localhost:8080/jreport/jrserver
http://localhost:8080/jreport/jinfonet/index.jsp

Back to top

Troubleshooting

If you run into problems when using Logi Report Server in Resin, send the log files of Logi Report Server to support@logianalytics.com. The following procedure illustrates how to generate the log files:

1. Modify the file resin.sh in /opt/resin/bin by adding -Dlogall=true after the reporthome definition:

   "$JAVA" $JAVA_OPTS \
    
   -classpath "$RESIN_CLASSPATH" -Dreporthome=/opt/LogiReport/Server \ 
   -Dlogall=true  \ 
   org.resin.Main "$@"

2. Run the modified resin.sh to start Resin.
3. After reproducing the problem, send support@logianalytics.com the log files in reporthome/logs.

   The Resin log files may also help to identify the problem. The most useful one is /opt/Resin/server/default/log/server.log.

Back to top

Previous Topic  Next Topic