- Start your hsqldb server from command line
- java -cp hsqldb-1.8.0.10.jar org.hsqldb.Server -database
\ - Start MySQL Migration Toolkit
- Choose direct migration
- Choose as Source a generic jdbc
- Enter “org.hsqldb.jdbcDriver” as classname
- Enter “jdbc:hsqldb:hsql://localhost” as connection string
- Enter “sa” as username and leave password empty
- click next
- Configure your mysql connection
- click next
- choose public as schema
- click next several time till screen “object creation options”
- choose “create script file..” instead of “create objects online”
- click next several time till screen “data mapping options”
- choose “create script file..” instead of “transfer data online”
- click next several time till screen “Summary”
- click finish
1/6/15
Migrating HSQLDB to MySQL
1/2/15
10+ Free Open Source BPM Platforms
10+ Free Open Source BPM Platforms
- Improvement and control of processes
- Services interaction
- Productivity and agility of the company
How to design and develop an interactive Cockpit or Dashboard in SpagoBI?
How to design and develop an interactive Cockpit or Dashboard in SpagoBI?
- A document of Type “Document Composite” and Engine “Document Composition Engine”.Notes: Make sure the engine has been configured in “Resources->Engines Management page. It can be configured while installing SpagoBI 3.4 (latest version) from windows installer.
- The XML file to design/develop the view and navigation of our cockpit. This is an xml template that we can write only by hand now but in future it will be written by wizard.
This tag defines the style html that will be designed with the div which will contain the document. Pay attention to values of top, width and height: they can be written in % or in pixel. SpagoBI recommends the pixel mode because it is more precise and make better use of the available space. Everything we write in this tag, will become the style of final tag.
Indicates the beginning of the list of parameters of the recorded document. In this section we must define all the input/output parameters of the document.
For every parameter, we need to define:
* the label by which the parameter is saved into SpagoBI (the url in detail document section).
* the type of the parameter: IN if is an input parameter, OUT if is an output parameter (by which the document refresh others documents).
* thedefault_value: is a value that the engine pass to the document if is not found explicitly in the url.
Indicates possible links with other documents. And for each document linked, we would need to define:
* the label of document linked
* the label of parameter linked
Notes: This tag can be repeated in case there are more than one input parameter for other documents in the page. With this example, if the user clicks on the report, it will refresh the chart with label “BC_SC_ByProdCat” updating the parameter ‘ProdCatType’ with the value clicked.
In SpagoBI 3.1, it is possible to cross navigate on external document setting by a typeCross attribute (EXTERNAL or INTERNAL). It means that now the composite document is very open. By default the cross type is internal.
Example:
Create a SpagoBI document as below:
Locate the template file and save the document. And finally execute the document to play with our interactive cockpit.
Others clarifications:
- All documents referred in the template must exist and be registered in SpagoBI.
- Each document will update the other, must include the tag in the template for the cross navigation. In fact the same document can be run stand-alone (and will have a normal cross navigation) or can be run in a document composed, and in this way will update the documents on the page without launch new ones. We can find my next blog on “How to develop linkable documents in SpagoBI?”.
- We can change the view of composed document by modifying the style tag of each document tag.
- When we save the document, click on cancel button in the following screen otherwise all the input parameters defined in template will be added under section “DOCUMENT ANALYTICAL DRIVER DETAILS”.
SpagoBIMobileEngine: Bringing Business Intelligence to mobile devices
SpagoBIMobileEngine: Bringing Business Intelligence to mobile devices
- Mobile Table: gives a tabular layout to data loaded from the associated dataset
- Mobile Chart: displays Sencha-Touch charts over dataset data
- Mobile Cockpit: composes charts and reports in a single layout, within the possibility for each document to interact with the others, passing them parameters
- Create an analytical document with the following required information:
- Label: the label of the document
- Name: Name of the document.
- Type: Mobile Report
- Engine: Mobile Report Engine
- Data Source: your data source, e.g. foodmart.
- Dataset: locate the dataset for which you would like to develop table.Notes: Make sure the engine has been configured. This is configured by default with version 3.4.
- Locate and upload the document template (.xml) file.
This tag is used to show title on the chart, we can change the style tag to change the visibility of the title on page.
This is start of the table column tag. We can have more than one columns depending upon our requirements.
Column header is the header of column and value is the dataset field name.
Use the following tag in case you would like to link this chart to another document (cross navigation).
Here the document references the target document label and for each parameter, it is necessary to define the name (url) of the target parameter and the type of it.
The type can assume next values:
CATEGORY: pass the category’s value selected.
SERIE: pass the serie’s value selected.
ABSOLUTE: pass the constant defined into the value property.
RELATIVE: pass the value of the parameter presents in the request with the name defined in the same property.
3. Save and execute the document.
Develop Mobile Chart
Please follow the steps below to develop mobile table:
- Create an analytical document with the following required information:
- Label: the label of the document.
- Name: Name of the document.
- Type: Mobile Chart
- Engine: Mobile Chart Engine
- Data Source: your data source, e.g. foodmart.
- Dataset: locate the dataset for which you would like to develop table.Notes: Make sure the engine has been configured. This is configured by default with version 3.4.
- Locate and upload the document template (.xml) file.
Details on the document template
Bar Chart
The width and height of the chart, we can have this value either in pixel or, percentage.
Please follow the steps below to develop mobile table:
- Create an analytical document with the following required information:
- Label: the label of the document.
- Name: Name of the document.
- Type: Mobile Cockpit
- Engine: Mobile Cockpit EngineNotes: Make sure the engine has been configured. This is configured by default with version 3.4.
- Locate and upload the document template (.xml) file.
Configure the title of the document.
This is the start of the document tag. There is a block for every document that we would like to view/present in our cockpit/dashboard. We can add as many document tags as we need depending upon our views requirements. There is no limit and so we can create a composite document with 2,3,4,6, … sub-documents and everyone can shows different layout. The only limit is our common sense, because see too many documents can create confusion rather than help the data analysis.
Label defines the label by which the document is saved into SapgoBI.
This is the configuration of the input parameters, urlName is the label by which the parameter is saved into SpagoBI (the url in detail document section) and defaultValue is a value that the engine pass to the document if is not found explicitly in the url.
3. Save and execute the document to show the composed view.
Others clarifications:
In case the documents have cross navigation defined separately, the composed document will be shown as interactive, we do not need to define it in Cockpit. This should be defined in separate document with the following tags:
Here the document references the target document label and for each parameter, it is necessary to define the name (url) of the target parameter and the type of it.
The type can assume next values:
CATEGORY: pass the category’s value selected.
SERIE: pass the serie’s value selected.
ABSOLUTE: pass the constant defined into the value property.
RELATIVE: pass the value of the parameter presents in the request with the name defined in the same property.
Attachments & References
- SpagoBIMobile uses Sencha touch chart for rendering the charts, so please refer document on Sencha website i.e.http://www.sencha.com/products/touch/charts for details.
- SpagoBI Wiki, http://www.spagoworld.org/xwiki/bin/view/SpagoBI/MobileBI
- Enclosed please find sample document template for Mobile Table, Bar chart, Pie Chart, Line Chart and Cockpit at http://paxcel.net/blog/wp-content/uploads/2012/06/SpagoBI.rar

