The DashXML framework provides a method for creating dashboards that combine Yellowfin content and custom items without the need for programming. The dashboards are configured in a single XML document that describes each element on each tab as a widget. All layout and styling can be achieved via customised CSS.
DashXML is designed to be implemented by a highly advanced user. This user would either be a developer, or someone with a strong technical background.
In order to implement a DashXML solution the user would require the following technical skills as a minimum:
Implementation | Skills | Description |
---|---|---|
Basic |
| This implementation would use reports (tables, charts, multi-charts, maps) called from a Yellowfin instance, with custom images and styling applied. This would not include the use of advanced CustomHTML widgets that use custom JavaScript, only purely HTML. |
Basic + Custom Widgets |
| This implementation would use reports (tables, charts, multi-charts, maps) called from a Yellowfin instance, with custom images and styling applied. This could also include the use of advanced CustomHTML widgets that use custom JavaScript and HTML. CustomHTML widgets can be used to pass Yellowfin report results through to other visualisation libraries. |
Basic + Third Party Security |
| This implementation would use reports (tables, charts, multi-charts, maps) called from a Yellowfin instance, with custom images and styling applied. This could also include the use of a Java Servlet Filter to apply source filters based on external user credentials, while still running reporting content as the nominated Yellowfin user (from the web.xml file). |
No user security is offered out-of-the-box with DashXML. Third party user security can be implemented using a Java Servlet Filter. This can test access for a user for a given dashboard, apply appropriate source filters for that user, and run the reports as the nominated user specified in the web.xml file.
Source filter can be passed for a particular session to enable row-level security. Source filters will need to be defined in the Yellowfin interface, and then referenced within the DashXML.
DashXML does not replicate all functionality found in the Yellowfin interface. Some of the functions that can't be replicated within DashXML include:
Edit your Yellowfin web.xml file.
Navigate to \Yellowfin\appserver\webapps\ROOT\WEB-INF\
and edit the web.xml file. You will need to uncomment the following section in order to enable Web Services.
Update your file from this:
| To this:
|
Save your changes.
Yellowfin Tomcat | Separate Tomcat |
---|---|
Copy the DashXML folder (from your downloaded zip) into your \Yellowfin\appserver\webapps\ directory. You should now have both a ROOT and DashXML directory sitting within webapps . | Copy the DashXML folder (from your downloaded zip) into your \Tomcat\webapps\ directory. You will now have a DashXML directory sitting within webapps. |
\webapps\DashXML\WEB-INF\
and edit the web.xml file. You will need to make three changes to this file, in order for DashXML to be able to connect to your Yellowfin instance.Set your Yellowfin URL.
<init-param> <param-name>PathToServer</param-name> <param-value>http://server-name:7171</param-value> <!-- update to Yellowfin server --> </init-param> |
Set your Yellowfin username.
<init-param> <param-name>Username</param-name> <param-value>admin@yellowfin.com.au</param-value> <!-- update to Yellowfin username --> </init-param> |
Set your Yellowfin password.
<init-param> <param-name>Password</param-name> <param-value>test</param-value> <!-- update to Yellowfin password --> </init-param> |
Explore the elements available in DashXML here: