Deploying Server to Resin 4.0.65
This topic describes how you can deploy Logi Report Server to Resin.
In the example we use directory paths based on Unix. The instructions are applicable to both Unix and Windows installations. However, the format of the paths for Windows should use the Windows format, that is,
C:\LogiReport\Server instead of
- You installed Resin 4.0.65 in the
- The Logi Report Server WAR file jreport.war is in the
/opt/LogiReport/Server/bin/distributedirectory. To create the WAR file, refer to the instructions in Building a WAR/EAR File to Include a Self-contained Logi Report Server.
To deploy Logi Report Server to Resin 4.0.65:
- 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. 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.65 by running the resin.sh start script in
- Log onto the Resin 4.0.65 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 jreport. Then select Deploy.
- Access Logi Report Server using the following URLs:
If you run into problems when using Logi Report Server in Resin, send the log files of Logi Report Server to [email protected]. 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 \
org.resin.Main "[email protected]"
- Run the modified resin.sh to start Resin.
- After reproducing the problem, send [email protected] 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.