This topic describes how you can deploy Logi Report Server to Resin 4.0.66.
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
- You installed Resin 4.0.66 in the
- The Logi Report Server WAR file jreport.war is in the
/opt/LogiReport/Server/bin/distributedirectory. 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.66:
- 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 to perform debugging and monitoring tasks on the remote Resin server using command line.
By default, these commands are disabled. To enable them, register ManagerService in the 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 by running the resin.sh start script in
- Sign in to the Resin Administration Console with the specified username and password using the URL
- In the deploy tab, select Browse to select the file jreport.war.
- In the Name text box, type jreport.
- Select Deploy.
- Access Logi Report Server using the following URLs:
If you run into problems when using Logi Report Server in Resin, you may have to send the log files of Logi Report Server to Customer Service. 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/LogiReport/Server \
- Run the modified resin.sh to start Resin.
- After reproducing the problem, send the log files in
reporthome/logsto Customer Service.
The Resin log files may also help identify the problem. The most useful one is /opt/Resin/server/default/log/server.log.