You can publish three types of resources from a remote computer. They are report sets, catalogs, and folders. Before they can be published you must create a zip file or tar file containing the resources to publish. If you want to publish resources from a remote machine to the server, use Publish to Remote Server.
To publish resources from a remote computer:
The Publish to Remote Server dialog is then displayed. See the dialog.
If you are publishing a folder in the cluster environment, it is recommended that you check the Map Shared Disk option for better performance.
Note: When publishing resources from a remote computer, the process is similar to that for a local publish. However, there are differences. They are:
%JAVAHOME%\bin\jar.exe -cvfM %DEST_JAR_FILE% %SOURCE_RESOURCES%
| Parameter | Description |
|---|---|
| %JAVAHOME% | The Java SDK install root. |
| %DEST_JAR_FILE% | The destination file path and file name. The .jar file will be generated to the path you specify here, using the file name you provide. |
| %SOURCE_RESOURCES% | The source file path and file name. Note that specifying a path for this parameter will cause the generated jar file to contain the same path information. For example, when you extract a jar file compressed using myReports\*.* for this parameter, the files will be extracted to a folder called myReports. JReport Enterprise Server is not able to import a compressed file which contains the path information, so do not specify a path for this parameter. |
To generate a jar file containing no path information, switch to the source folder, and then carry out the compression. For example,
C:\myReports>C:\j2sdk1.4.1_02\bin\jar -cvfM c:\temp\aa.jar.
The jar file will be generated to c:\temp, as aa.jar, compressing all the files in c:\myReports, and containing no path information.
Always use this method if the folder you are compressing contains report sets with Chinese, Korean, or Japanese names.