Configuring Advanced Server Settings
Administrators can also customize some advanced settings of Logi JReport Server, for example they can enable the server to do security check upon all requests, enable end users to specify time condition for scheduled report tasks, customize timeout time for user sessions and temporary files and so on.
To configure the advanced server settings, on the Logi JReport Administration page select Configuration on the system toolbar and select Advanced from the drop-down menu to open the Configuration - Advanced page. Then customize the options on the page according to your requirements and save them. After making any changes on the page, you need to restart Logi JReport Server so as to make the changes take effect.
The following table details the options on the page.
|No Security Check||Specifies whether the server responds to all the requests without security checking.|
|Enable "Publish to Versioning System" for Background Tasks View||Specifies whether to generate the hyperlink Publish to Versioning System in the view page when you run a report on the Logi JReport Console page. Select this hyperlink to save the report result as a version.|
|Keep Connection Alive||Specifies whether to keep the connection alive. By default, this option is checked. When connections are established to the Logi JReport Server at runtime, you can choose either to keep the connections alive or to close them. If you uncheck this option, the connection will be disconnected once the HTTP request has been responded to. That is, web browser will not hold the open connection.|
|Prompt Message When Server Task Queue Is Full||If checked, a message will be prompted asking you either to place the task in the waiting queue or to cancel it when a task cannot be run in Logi JReport Server immediately due to the task queue being fully occupied.|
|Prompt Message When Page Report Studio Action Queue Is Full||If checked, a message will be prompted asking you either to place the action in the waiting queue or to cancel it when an action cannot be performed in Page Report Studio immediately due to the action queue being fully occupied, or simply showing that no more action can be held at the moment when the waiting queue is full.|
|Enable Multiple Users to Login Using the Same User Name||Specifies whether multiple sessions created by one user can exist simultaneously. By default, this option is checked and one user can log onto Logi JReport Server repeatedly without having to terminate former sessions until the session number reaches the number permitted by the license. If this option is unchecked, only the newly created session will be active, and all the other former sessions created by the same user will be terminated by the server automatically.|
|Enable Resources from Real Paths||Specifies whether to enable getting resources from real paths.|
|Enable Task Duration||Specifies whether to enable the task-level timeout mechanism on Logi JReport Server.|
|Enable Linked Catalog||Enables to predefine a linked catalog at server level for the My Components, Public Components, My Reports and Public Reports folders to inherit. After a linked catalog is specified here, these folders can inherit the linked catalog from the server level once their Enable Linked Catalog property is enabled.
|Role Based Authorization||Specifies whether to activate the role based security in replace of the default applied security of setting permissions for users, groups and roles. In the role based security, permissions are defined on roles only, and users and groups are mapped to roles.
If this option is checked, the option Permission Setting UI Displays will be hidden since it applies to the default applied security.
|Permission Setting UI Displays||Controls whether to display user, role or group permissions in the resource permission setting UI.|
|Advanced Password||Specifies whether to apply advanced password rule on Logi JReport Server. When this option is enabled, when setting password on Logi JReport Server, a complex one which matches the rule specified below is required. However, this rule doesn't affect administrator's changing and setting password for other users.
|Permission Algorithm||Specifies an algorithm for calculating a user, role or group's permission.
For information about the permission accumulation algorithm and the user permission replacement algorithm, see server.permission.algorithm.
|Show Resource Name Extension||Specifies whether to show the resource name extension in the resource tree.
|User Session Timeout||Specifies the time limit for a user to gain access to Logi JReport Server.
Generally speaking, if several users attempt to gain access to Logi JReport Server at the same time and among them, a user is unable to send requests to Logi JReport Server for a period of time, the server will then log it out after timeout. The default session timeout is 500 hours.
|Time Limit Before Moving to Background||Specifies the maximum time for running a report. If a report is so large that Logi JReport Server cannot run it within the time specified here, it will be put into the Background Tasks page and the server will go on running the report there. If you want to stop running the report, select the report by selecting in the row and then delete it from the Background Tasks tab.|
|Status Refresh Interval||Specifies task duration check frequency. By default, Logi JReport Server checks task duration every 30 seconds. This value can also be reset by the task.duration.check_cycle property in the server.properties file. Note that the value must be an integer greater than 0.
The option is available when the option Enable Task Duration in this page is checked.
|Temporary Files Life||Specifies the length of the period to keep the temp files for after they have been generated. By default it is 24 hours. Temp files are deleted 24 hours after they have been generated.|
|Engine Priority||Specifies the priority of the engine in CPU usage when multiple tasks are running on your machine. It can be one of the following: Lowest Priority, Low Priority, Normal Priority, High Priority, and Highest Priority.
On the condition that multiple tasks are running on your machine, you can decide your engine's priority in CPU usage by choosing one of them. For example, if you choose Low Priority, Logi JReport Engine will share a comparatively small part of the CPU usage when it is running. Whereas, if you choose High Priority, Logi JReport Engine will occupy more CPU usage. This choice provides you with greater flexibility in adjusting the engine's utilization of the CPU according to your requirement. Of course, the higher the priority, the faster the performance.