Previous Topic  Next Topic

Applying the Implementations of the Dashboard Listener API

Dashboard Listener API defines the start and end events of adding and deleting library components for users to get dashboard related information at the event and to use the information in their own application.

Event types

• The start action of adding a library component
• The end action of adding a library component
• The start action of deleting a library component
• The end action of deleting a library component

Basic information

• Catalog information
• Dashboard information
• Library component information

For detailed usages about the Dashboard Listener API, refer to the com.jinfonet.web.modules.dashboard package in the Logi Report Javadoc. You can also refer to the sample implementation file DashboardListenerDemo.java in <install_root>\help\samples\APIDashboardListener for additional information.

Applying the Dashboard Listener API

Different uses should have different implementations of the Dashboard Listener API. The implementations can be managed on the Logi Report Server console by administrators. After a new implementation is imported to the server and enabled, it will be able to take effect immediately without restarting the server.

In addition, after an implementation is uploaded to Logi Report Server, you can apply it in the URL which is used for running dashboards. The URL way has higher priority than the enabled implementation in the server console.

To import and enable an implementation in the Logi Report Server console:

1. In the Logi Report Server console, point to Administration on the system toolbar, select Other > Dashboard Listeners from the drop-down menu. Report Server displays the Dashboard Listeners page.

   

2. Select New Dashboard Listener.
3. In the New Dashboard Listener dialog box, select the Browse button to locate the implementation file which could be a zip or a jar file. Then select Next.
4. From the Class Name drop-down list, choose a class name which is defined in the implementation file.

   

5. Select beside the Target box, then in the Select Target dialog box specify the target dashboards you would like the implementation to apply to: all dashboard including the unsaved ones, the newly created dashboards that have not been saved, or dashboards in the specified folders.

   

6. Select OK and the specified dashboards will be listed in the Target box.

   When all dashboards have been added, the button will be disabled. Later if you want to change the dashboards, you need to first delete the <All dashboards> item and then add other dashboards. To remove unwanted dashboards from the Target box, select them and then select .

7. In the Description text box, you can type a description for the implementation.
8. Select the Enabled check box to make the implementation enabled.
9. Select Finish and the registered class will take effect right away.

The registered implementation class is added in the class table on the Dashboard Listener page which consists of the following columns.

In the class table, the system admin can perform the following on the implementations:

• To sort the table by certain column, select on the column name.
• To modify the target value of an implementation, select it, then select Properties on the toolbar or right-click and then select Properties from the shortcut menu. Then in the displayed dialog box, modify the target dashboards as required.
• To enable implementations that are not enabled, select them, then select Enable on the toolbar or right-click and then select Enable from the shortcut menu.
• To disable implementations that are enabled, select them, then select Disable on the toolbar or right-click and then select Disable from the shortcut menu.
• To delete implementations, select them, then select Delete on the toolbar or right-click and then select Delete from the shortcut menu.

To apply an implementation via URL:

To apply the dashboard listener via URL, append the key-value pair jrd_dsh_listener=PackageName.ClassName in the URL which is used for running dashboards.

For example, if you want your implemented class TestListener to take effect on a new created dashboard (not the target defined in the server console), you can define it in the URL. Such URL will not affect the setting in the server console.

http://localhost:8888/dashboard/app/entry/run.jsp?jrs.authorization=YWRtaW46YWRtaW4%3D&jrd_dsh_listener=com.jinfonet.TestListener&jrd_resext={"active":0,"reslst":[{"name":"/USERFOLDERPATH/admin/Dashboard 1.dsh","ver":-1}]}

Previous Topic  Next Topic