RMI Demos
This topic describes the demo RMI programs that Report Server provides in <install_root>\help\samples\APIRemoteServer.
- RemoteAPIDemoFileService.java
                                                    
 Using remote Report Server demo.
- RemoteAPIDemoPublishRpt.java 
                                                    
 Scheduling reports to version/disk/email demo.
- RemoteAPIDemoRunAndExportReport.java
                                                    
 Running and exporting reports to other formats demo.
- RemoteAPIDemoRunReportWithTimeout.java
                                                    
 Marking a running report as a large report by setting the timeout value and returning the large report information demo.
Remember to do the following before running the preceding demos:
- Modify the file server.properties in the <install_root>\bindirectory to set the property server.rmiserver.enable to true.
- Add -Djrs.rmi.auth_file="%authFileName%"to the command line that starts the program you want.
- You need to set the classpath environment variable. Append the following jar files to the class path that compile and run applications which call the Server API: <install_root>\lib\JRESServlets.jar;<install_root>\lib\JREngine.jar;<install_root>\lib\jakarta.servlet-api-4.0.4.jar;<install_root>\lib\log4j-core-2.17.1.jar;<install_root>\lib\log4j-api-2.17.2.jar;<install_root>\lib\sac-1.3.jar;
                                                 In the second week of December 2021, a Log4j vulnerability was announced that may affect some customers using our products. Resolving/mitigating this issue is a high priority! We will continue to issue information to help you with this vulnerability. For more information, see Statement on Log4j and Log4Net Vulnerabilities.
In the second week of December 2021, a Log4j vulnerability was announced that may affect some customers using our products. Resolving/mitigating this issue is a high priority! We will continue to issue information to help you with this vulnerability. For more information, see Statement on Log4j and Log4Net Vulnerabilities.
 Previous Topic
Previous Topic
 Back to top
Back to top