All the resources in the resource tree are controlled by versions. A version is the fundamental unit in the resource tree.
Your resources might be changed over time. JReport Enterprise Server uses a versioning system to create and manage the resources that may have changed their contents and properties owing to updates that may have been issued on them.
All the resources in the resource tree have versions. A great portion of the resource management tasks are done by managing the resource versions.
The versions in JReport Enterprise Server fall into the following three major categories accordingly:
- Report Version
The version of a report file.- Catalog Version
The version of a report catalog file.- Result Version
The version of a report result file.
The report result can be generated and maintained in two places - the resource tree and the built-in version folder.
When you schedule to publish a report to versioning system, you can choose an archive location to generate the report result. You can generate the report result to the built-in version folder, or to the My Reports folder or the Public Reports folder in the resource tree.
The report results generated in the resource tree are stand-alone results, and can have their own versions, while those generated in the built-in version folder can only be bound with their respective reports.
JReport Enterprise Server uses archive policy to control the resource versions. You can control whether to use multiple versions for the specific resource, also, you can set the maximum version amount to be listed in the version table.
Archived policy can be applied to a single resource individually or to many resources in a folder as a whole.
Normally, report result versions are created when the user runs reports in the Advanced Run or Schedule mode. However, to create a new version for a report resource or catalog resource, you have to deploy a report or catalog respectively from outside JReport Enterprise Server, and then make the old and the new share one common resource node.
When you are making more than one versions share one resource node, you are creating new versions for that resource node. The way to put archive versions under an existing resource node is very simple - just make the path and name of the version that you are creating or deploying conform with that of the resource node.
There are three types of resources in JReport Enterprise Server, which are report resource, catalog resource, and report result resource.
The ways to create versions for report resource and catalog resource are completely the same.
To create a new version for a report resource, you will have to deploy a report from outside JReport Enterprise Server,
- Log on to JReport Enterprise Server, locate the folder that contains the report resource for which you want to create a new version.
- Click Deploy.
- Choose Local Deploy or Remote Deploy according to your specific case.
- Type the name of the resource node for which you are to create new version in the Resource Name box. The name you provide must be exactly the same as the original resource node name.
- Fill up the relevant information to deploy a report.
- Click Submit when you finish. The report will be added to the resource tree, and serve as a version of that resource.
Reference Note:
For assistance on how to deploy resource from local or remote computer, please refer to User Guide | Administrating JReport Enterprise Server | Resource Management | Deploying Resources
The report result can reside in two places - the resource tree and the built-in version folder.
The report result in the resource tree is a stand-alone result and serves as a resource node, hosting its own versions, while those generated in the built-in version folder can only be bound with their respective reports.
There are two approaches to create a report result version,
Advanced Run:
- Log on to JReport Enterprise Server, locate the folder that contains the report for which you are creating result versions.
- Click the corresponding AdvancedRun link in the Control column.
- On the Archive tab, check Auto archive after running to expand the Auto archive policy of result doc options.
- To generate report result version in the built-in folder, select Build-in Version Folder.
To generate report result version under a stand-alone resource node in the resource tree, select My folder or Public folder, and then provide the path and resource name information in the corresponding box.- Finish other relevant information according to your own case, and then click Submit. The report result will be generated to the corresponding location.
Schedule:
- Log on to JReport Enterprise Server, locate the folder that contains the report for which you are creating result versions.
- Click the corresponding Schedule link in the Control column.
- On the Publish tab, click the To Version tab, check the Publish to Versioning System option.
- Set archive location options.
To generate report result version in the built-in folder, select Build-in Version Folder.
To generate report result version under a stand-alone resource node in the resource tree, select My folder or Public folder, and then provide the path and resource name information in the corresponding box.- Finish other relevant information according to your own case, and then click Submit. The report result will be generated to the corresponding location when the scheduled task is completed.
Notes:
The resource path and name refers to that in the resource tree, for instance, /foldername/filename.
For the Public folder option, the first slash mark (/) refers to the Public Reports folder in the resource tree, and the folder name (foldername) refers to a folder that actually exists in the resource tree.
For the My folder option, the first slash mark (/) refers to the My Reports folder in the resource tree, and the folder name (foldername) refers to a folder that actually exists in the resource tree.
Please note, to generate report result version under an existing stand-alone resource node in the resource tree, say, create a new version for a resource node, please provide the path and name of the existing resource for the Public folder or My folder option.
To view the version information, locate the folder that contains the expected resource, and then click the corresponding Versions link in the Control column.
A report type resource hosts two types of version - report version and report result version (built-in version folder).
The versions that a resource hosts are organized in the version table. You can remove any versions after selecting them in the version table.
Relevant information about the versions that a resource hosts, such as the version date, version number, version properties, and so on, is collected and represented in table form, which is called version table.
You can perform operations such as sorting and viewing properties, output files, and parameters in a version table.
The columns that compose a version table are described as below:
Report/Catalog Version Table
Column Description Control Provides the properties link for the users to view the properties of the version. Version Date Shows the data and time when the version is generated. Number Shows the serial ID that identifies a version in the version table. Result Version Table
Column Description Control Provides the properties link for the users to view the properties of the version. Version Date Shows the data and time when the version is generated. Number Shows the serial ID that identifies a version in the version table. Output Shows the output file formats and provides links to the output files. Parameter File Shows the parameter file names and provides links to the parameters. Creator Shows the ID of the user who creates the version.
Archive policy can be applied to a single resource individually or to many resources in a folder as a whole. It can also be applied when you run (Advanced Mode) or schedule a report.
If there is no archive policy specified for a resource, the resource will inherit the archive policy from its parent object. If afterward you specify archive policy for that resource, the new archive policy will override that of the parent object.
Archive policy includes settings for controlling whether to use multiple versions for the specific resource, and the maximum version amount to be listed in the version table.
Archive as a new version
Specifies whether to use multiple versions for the specific resource. Available only for the resources in the resource tree.Max result version amount
Specifies the maximum version amount to be listed in the version table. The default value is 0, which means the version amount is unlimited.To apply archive policy to the resource in the resource tree, please refer to the table below:
If you want to Then do Result Apply archive policy to a folder
- Locate the folder that contains the folder for which you want to set archive policy, click the corresponding Properties link.
- Set the archive policy, and then click Submit.
The archive policy will be applied to all of the folder content.
Note: This not includes the resources whose archive policies are applied individually.Apply archive policy to a resource
- Locate the folder that contains the resource for which you want to set archive policy, click the corresponding Properties link.
- Set the archive policy, and then click Submit.
The archive policy will be applied to the resource, overriding its inherited archive policy.
Note: If you leave the Apply Archive Policy option unchecked, the resource will inherit the archive policy from its parent object, say, the folder it resides in.Apply archive policy when running a task in Advanced mode
- Locate the folder that contains the resource you want to run, click the corresponding AdvancedRun link.
- On the Archive tab, check the Auto archive after running option.
- Finish other relevant information, make sure the result location is set to the resource tree folder.
- Set the archive policy, and then click Submit.
You are actually applying the archive policy to a result type resource. The archive policy will be applied to the resource.
Note: If you leave the Apply Archive Policy option unchecked, the resource will use its old archive policy or inherit the archive policy from its parent object, say, the folder it resides in, when no archive policy is set for it.Apply archive policy when scheduling a task
- Locate the folder that contains the resource you want to schedule, click the corresponding Schedule link.
- On the Publish tab, click the To Version sub-tab, check the Publish to Versioning System option.
- Finish other relevant information, make sure the result location is set to resource tree folder.
- Set the archive policy, and then click Submit.
You are actually applying the archive policy to a result type resource. The archive policy will be applied to the resource.
Note: If you leave the Apply Archive Policy option unchecked, the resource will use its old archive policy or inherit the archive policy from its parent object, say, the folder it resides in, when no archive policy is set for it.The above table applies to the resource in the resource tree only. The versions in the built-in version are controlled by its own archive policy.
To apply archive policy to the built-in version table, please refer to the table below:
If you want to Then do Apply archive policy to a built-in version table
- Locate the folder that contains the resource (report type) which you want to set archive policy for its result version table, click the corresponding Versions link.
- On the Result Versions tab, check the Max version amount option.
- Set the archive policy, and then click Submit.
Apply archive policy when running a task in Advanced mode
- Locate the folder that contains the resource you want to run, click the corresponding AdvancedRun link.
- On the Archive tab, check the Auto archive after running option.
- Finish other relevant information, make sure the result location is set to the built-in version folder.
- Set the archive policy, and then click Submit.
Apply archive policy when scheduling a task
- Locate the folder that contains the resource you want to schedule, click the corresponding Schedule link.
- On the Publish tab, click the To Version sub-tab, check the Publish to Versioning System option.
- Finish other relevant information, make sure the result location is set to the built-in version folder
- Set the archive policy, and then click Submit.