<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kagura BI</title><link>https://arran4.github.io/kagura-original/</link><description>Recent content on Kagura BI</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 04 Mar 2026 00:58:36 +0000</lastBuildDate><atom:link href="https://arran4.github.io/kagura-original/index.xml" rel="self" type="application/rss+xml"/><item><title>Architecture</title><link>https://arran4.github.io/kagura-original/docs/architecture/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/architecture/</guid><description>Architecture Architecture Jan 09, 2014Cloud editor* Library first
Components* Kagura API / Report Core* Core components* Storage Providers
Parameter Types
Connectors &amp;amp; Freemarker
Configuration Model
Helper Components* The &amp;ldquo;Export Handler&amp;rdquo; Authentication Providers &amp;amp; Model
Karaf* Camel / CXF routes Bundle
Assembly
Features
Example Authrest
Javascript / Jetty
Resources
Rest-API
Library first Kagura is a library first. Which means it was designed to be modular and self contained. It also provides minimal constraints in the way that you can use it, and is intended to be embedded into a larger scale application, such as some of the example components demonstrate.</description></item><item><title>As a Library</title><link>https://arran4.github.io/kagura-original/docs/as_a_library/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/as_a_library/</guid><description>As a Library As a LibraryUpdated Jan 16, 2014*
As a Library Jan 16, 2014Cloud editor
Kagura has several &amp;ldquo;library&amp;rdquo; components you have 2 &amp;ldquo;compulsory parts&amp;rdquo;:
Report Storage Provider
Reports Core
And some optional components:
Authentication Providers
REST API Interfaces
Misc Helpers
Reports Core; is the part we are interested in if we want to generate output for a front end. It&amp;rsquo;s the work horse. Report Storage Providers; is required in-order to provide a list of reports, and the report contents.</description></item><item><title>Authentication Providers</title><link>https://arran4.github.io/kagura-original/docs/authentication_providers/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/authentication_providers/</guid><description>Authentication Providers Building a basic JNDI/JDBC reportUpdated Jan 21, 2014*
Building a basic JNDI/JDBC report Jan 21, 2014Cloud editor
To build a report you need to create a file called: reports//reportconf.yaml . Where is an unique identifier for your reports. Before you continue you will have to ensure you have setup users.
For this report, we are going give it the report id: TheAnswers. Create a file called:
reports/TheAnswers/reportconf.yaml Data source selection Then you need to choose your data type.</description></item><item><title>Building a basic JNDI JDBC report</title><link>https://arran4.github.io/kagura-original/docs/building_a_basic_jndi_jdbc_report/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/building_a_basic_jndi_jdbc_report/</guid><description>Building a basic JNDI JDBC report Maven RedeploymentUpdated Jan 10, 2014*
Maven Redeployment Jan 10, 2014Cloud editor
This is more involved process however it&amp;rsquo;s basically the Karaf Deployment but allows you to take the project entirely out of the Kagura project directory, which is useful if you want to keep your reports in some form of SCM. (Highly recommended.)
I have an example project setup athttps://github.com/arranubels/kagura-custom-assembly
We will check this out and get the container started.</description></item><item><title>Configurations</title><link>https://arran4.github.io/kagura-original/docs/configurations/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/configurations/</guid><description>Configurations Kagura is flexible enough to be used in various configurations, here are a couple of use cases I can think of: As a stand alone reports web service
This is primarily what comes to mind when people think of using something like Kagura. Kagura has 2 ways of operating out-of-the-box as a fully functional web service;
As a Tomee compatible war file As a Jetty + Karaf (OSGI) service These are straight forwards to get started with, see the getting started guide.</description></item><item><title>Introduction</title><link>https://arran4.github.io/kagura-original/docs/introduction/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/introduction/</guid><description>Introduction Kagura is an open source project created by base2Services. It is a flexible simple reporting platform that allows reports to be delivered in a speedy manner, without cumbersome designer UIs intended for a less technical market.
This page contains more information on the project.
[Screenshots](https://kagura.atlassian.net/wiki/spaces/KGR/pages/491543) [Configurations](https://kagura.atlassian.net/wiki/spaces/KGR/pages/491527) [Use Cases](https://kagura.atlassian.net/wiki/spaces/KGR/pages/491529) [Architecture](https://kagura.atlassian.net/wiki/spaces/KGR/pages/491540) [Getting Started](https://kagura.atlassian.net/wiki/spaces/KGR/pages/491542) [Documentation](https://kagura.atlassian.net/wiki/spaces/KGR/pages/491534) [Quick reference](https://kagura.atlassian.net/wiki/spaces/KGR/pages/491532) Aim
The aim of Kagura is to produce a simple and fast reporting framework, which can be used widely and customised heavily.</description></item><item><title>JDBC Report Template</title><link>https://arran4.github.io/kagura-original/docs/jdbc_report_template/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/jdbc_report_template/</guid><description>JDBC Report Template JDBC Report Template reports/TheAnswers/reportconf.yaml type: &amp;ldquo;JDBC&amp;rdquo; classLoaderPath: &amp;ldquo;com.mysql.jdbc.Driver&amp;rdquo; jdbc: &amp;ldquo;jdbc:mysql://localhost:3306/test&amp;rdquo; username: &amp;ldquo;test&amp;rdquo; password: &amp;ldquo;test&amp;rdquo; sql: &amp;ldquo;SELECT id, question, answer FROM Answers &amp;lt;@where&amp;gt; &amp;lt;@clause render=param.questionQuery?has_content&amp;gt; question=${method.value(param.questionQuery)} /@clause /@where &amp;lt;@limit /&amp;gt;&amp;rdquo; columns:
name: question label: Question name: answer label: Answer extraOptions: reportName: &amp;ldquo;The Answers&amp;rdquo; directory: &amp;ldquo;Folder 1&amp;rdquo; description: &amp;ldquo;This is a sample report&amp;rdquo; image: &amp;ldquo;http://jentrata.org/images/jentrata.png&amp;quot; paramConfig: { type: String, id: questionQuery, name: &amp;ldquo;Question to search for&amp;rdquo;, help: &amp;ldquo;Leave blank for any&amp;rdquo;, placeholder: &amp;ldquo;None&amp;rdquo; }</description></item><item><title>JNDI JDBC Freemarker Report</title><link>https://arran4.github.io/kagura-original/docs/jndi_jdbc_freemarker_report/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/jndi_jdbc_freemarker_report/</guid><description>JNDI JDBC Freemarker Report JNDI/JDBC Freemarker ReportUpdated Jan 21, 2014*
JNDI/JDBC Freemarker Report Jan 21, 2014Cloud editor
This is the most likely type of report you will require. It&amp;rsquo;s a report which takes it&amp;rsquo;s data from a data source such as MySQL and returns the output. (Not all reports do this.) Prerequisites For this to work you need several things:
What parameters you are going to use, and how to query them</description></item><item><title>Kagura js</title><link>https://arran4.github.io/kagura-original/docs/kagura_js/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/kagura_js/</guid><description>Kagura js Kagura.jsUpdated Feb 21, 2014*
Kagura.js Feb 21, 2014Cloud editor
Kagura.js is a javascript file which is the driving force of the example javascript web page, which you can use as a basis for your reporting front end. Or you can write something yourself. Or go half way and use the kagura.js javascript file and hire a web designer to make a nicer front end for you your site.</description></item><item><title>Karaf</title><link>https://arran4.github.io/kagura-original/docs/karaf/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/karaf/</guid><description>Karaf KarafUpdated Feb 11, 2014*
Karaf Feb 11, 2014Cloud editor
The Kagura Karaf container is designed to work out of the box, with an accompanying HTTP server for the presentation layer. Out of the box Kagura&amp;rsquo;s karaf container provides the core Kagura reporting REST services. It comes with an example &amp;ldquo;Authentication REST&amp;rdquo; backend. This is a sample REST end point for if you were to use REST configuration. The true power in the Kagura REST container is the flexible container that it runs in, allowing live changes to parameters for instance.</description></item><item><title>Karaf Deployment</title><link>https://arran4.github.io/kagura-original/docs/karaf_deployment/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/karaf_deployment/</guid><description>Karaf Deployment Karaf Deployment
First we need to checkout the code: git clone https://github.com/base2Services/kagura.git cd kagura mvn compile package install
Open up another terminal:
In terminal 1, we are going to start the Jetty service, this is where we host the Terminal 1 cd example/javascript mvn org.mortbay.jetty:jetty-maven-plugin:8.1.12.v20130726:run
Press ^C to end it.
In terminal 2, we are going to start the Camel service which provides the REST backend. All calls the the rest services are routed through Jetty to prevent cross domain scripting issues.</description></item><item><title>Library</title><link>https://arran4.github.io/kagura-original/docs/library/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/library/</guid><description>Library Library
See As a Library</description></item><item><title>Maven Deployment</title><link>https://arran4.github.io/kagura-original/docs/maven_deployment/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/maven_deployment/</guid><description>Maven Deployment Maven Deployment
First we need to checkout the code: Terminal 1 git clone https://github.com/base2Services/kagura.git cd kagura mvn compile package install
Open up another terminal:
In terminal 1, we are going to start the Jetty service, this is where we host the Terminal 1 cd example/javascript mvn org.mortbay.jetty:jetty-maven-plugin:8.1.12.v20130726:run
Press ^C to end it.
In terminal 2, we are going to start the Camel service which provides the REST backend. All calls the the rest services are routed through Jetty to prevent cross domain scripting issues.</description></item><item><title>Report Providers</title><link>https://arran4.github.io/kagura-original/docs/report_providers/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/report_providers/</guid><description>Report Providers Authentication ProvidersUpdated Feb 12, 2014*
Authentication Providers Feb 12, 2014Cloud editor
Authentications providers are an optional component or base component provided by the reporting-core. They are designed for 2 purposes:
Mapping Reports to Users (via groups)
Restricting the users of the system to users who are allowed to access the product
There are a couple of existing Authentication providers, and planned Authentication providers: (As of 1.4)
Authentication Provider The file Authentication provider expects to see 2 files in the reports directory: users.</description></item><item><title>REST API</title><link>https://arran4.github.io/kagura-original/docs/rest_api/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/rest_api/</guid><description>REST API Report ProvidersPublished Feb 14, 2014*
Report Providers Feb 14, 2014Cloud editor
Report Providers are a tool used to return the report data, they are fairly straightforwards.
Report providers:
Report Provider Currently (1.4) the only supported mechanism for storing a file. It provides a report from a configuration as follows:
/reportconf.yaml or /reportconf.json
It depends on the com.base2.kagura.reportloc configuration option for the location. More information can be found here: Building a basic JNDI/JDBC report</description></item><item><title>Screenshots</title><link>https://arran4.github.io/kagura-original/docs/screenshots/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/screenshots/</guid><description>Screenshots Screenshots
Please note, as the nature of Kagura is more of a library, but provides example service and presentation (web) layers. These screenshots do not dictate the final look of the site and users are encouraged to modify the end site to match their requirements. Version 1.2
The login screen
The welcome page:
List of reports:
A sample page. Remember we recommend you customise this.
A sample of a report configuration &amp;amp; directory structure.</description></item><item><title>Setting up File Authentication</title><link>https://arran4.github.io/kagura-original/docs/setting_up_file_authentication/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/setting_up_file_authentication/</guid><description>Setting up File Authentication Setting up File Authentication Provider user and groups
There are a couple of Authentication providers one is the &amp;ldquo;File Authentication Provider&amp;rdquo; which is a simple file based authentication. This particular one does not employ encryption. It&amp;rsquo;s designed for demo sites. I would suggest using another authentication provider. The setup is simple, you create 2 files in the reports/ directory,
users.yaml groups.yaml Users can&amp;rsquo;t have direct access to reports, they have be placed in a group in-order to access the reports.</description></item><item><title>Use Cases</title><link>https://arran4.github.io/kagura-original/docs/use_cases/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/use_cases/</guid><description>Use Cases Use Cases
Where would you use Kagura:
When you need a reporting web service that is quick to deploy and more developer friendly than existing frameworks When you need something that you can customize as all levels When you need something you can embed into your application or run separately, with no changes required to port your reports across When you need a report service which you can run in a stateless environment</description></item><item><title>War Deployment</title><link>https://arran4.github.io/kagura-original/docs/war_deployment/</link><pubDate>Wed, 04 Mar 2026 00:58:36 +0000</pubDate><guid>https://arran4.github.io/kagura-original/docs/war_deployment/</guid><description>War Deployment War Deployment
Goto http://tomee.apache.org/downloads.html download the JaxRS version. As of writing we have developed the War file for version 1.6. % tar xf apache-tomee-1.6.0-jaxrs.tar.gz % ln -sf ~/.m2/repository/com/base2/kagura/war-rest/1.2/war-rest-1.2.war apache-tomee-jaxrs-1.6.0/webapps/ % cd apache-tomee-jaxrs-1.6.0 % ./bin/startup.sh
When it starts visit:
http://localhost:8080/war-rest-1.2/
Reports are embedded into the war.
I recommend you use JNDI, you can find out how to setup JNDI data sources in tomee here: http://tomee.apache.org/configuring-datasources.html.</description></item><item><title>Architecture</title><link>https://arran4.github.io/kagura-original/posts/architecture/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/architecture/</guid><description>Architecture Architecture Jan 09, 2014Cloud editor* Library first
Components* Kagura API / Report Core* Core components* Storage Providers
Parameter Types
Connectors &amp;amp; Freemarker
Configuration Model
Helper Components* The &amp;ldquo;Export Handler&amp;rdquo; Authentication Providers &amp;amp; Model
Karaf* Camel / CXF routes Bundle
Assembly
Features
Example Authrest
Javascript / Jetty
Resources
Rest-API
Library first Kagura is a library first. Which means it was designed to be modular and self contained. It also provides minimal constraints in the way that you can use it, and is intended to be embedded into a larger scale application, such as some of the example components demonstrate.</description></item><item><title>As a Library</title><link>https://arran4.github.io/kagura-original/posts/as_a_library/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/as_a_library/</guid><description>As a Library As a LibraryUpdated Jan 16, 2014* As a Library Jan 16, 2014Cloud editor
Kagura has several &amp;ldquo;library&amp;rdquo; components you have 2 &amp;ldquo;compulsory parts&amp;rdquo;:
Report Storage Provider
Reports Core
And some optional components:
Authentication Providers
REST API Interfaces
Misc Helpers
Reports Core; is the part we are interested in if we want to generate output for a front end. It&amp;rsquo;s the work horse. Report Storage Providers; is required in-order to provide a list of reports, and the report contents.</description></item><item><title>Authentication Providers</title><link>https://arran4.github.io/kagura-original/posts/authentication_providers/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/authentication_providers/</guid><description>Authentication Providers Building a basic JNDI/JDBC reportUpdated Jan 21, 2014* Building a basic JNDI/JDBC report Jan 21, 2014Cloud editor
To build a report you need to create a file called: reports//reportconf.yaml . Where is an unique identifier for your reports. Before you continue you will have to ensure you have setup users.
For this report, we are going give it the report id: TheAnswers. Create a file called:
reports/TheAnswers/reportconf.yaml Data source selection Then you need to choose your data type.</description></item><item><title>Building a basic JNDI JDBC report</title><link>https://arran4.github.io/kagura-original/posts/building_a_basic_jndi_jdbc_report/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/building_a_basic_jndi_jdbc_report/</guid><description>Building a basic JNDI JDBC report Maven RedeploymentUpdated Jan 10, 2014* Maven Redeployment Jan 10, 2014Cloud editor
This is more involved process however it&amp;rsquo;s basically the Karaf Deployment but allows you to take the project entirely out of the Kagura project directory, which is useful if you want to keep your reports in some form of SCM. (Highly recommended.)
I have an example project setup athttps://github.com/arranubels/kagura-custom-assembly
We will check this out and get the container started.</description></item><item><title>Configurations</title><link>https://arran4.github.io/kagura-original/posts/configurations/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/configurations/</guid><description>Configurations Kagura is flexible enough to be used in various configurations, here are a couple of use cases I can think of: As a stand alone reports web service
This is primarily what comes to mind when people think of using something like Kagura. Kagura has 2 ways of operating out-of-the-box as a fully functional web service;
As a Tomee compatible war file As a Jetty + Karaf (OSGI) service These are straight forwards to get started with, see the getting started guide.</description></item><item><title>Introduction</title><link>https://arran4.github.io/kagura-original/posts/introduction/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/introduction/</guid><description>Introduction Kagura is an open source project created by base2Services. It is a flexible simple reporting platform that allows reports to be delivered in a speedy manner, without cumbersome designer UIs intended for a less technical market.
This page contains more information on the project.
[Screenshots](https://kagura.atlassian.net/wiki/spaces/KGR/pages/491543) [Configurations](https://kagura.atlassian.net/wiki/spaces/KGR/pages/491527) [Use Cases](https://kagura.atlassian.net/wiki/spaces/KGR/pages/491529) [Architecture](https://kagura.atlassian.net/wiki/spaces/KGR/pages/491540) [Getting Started](https://kagura.atlassian.net/wiki/spaces/KGR/pages/491542) [Documentation](https://kagura.atlassian.net/wiki/spaces/KGR/pages/491534) [Quick reference](https://kagura.atlassian.net/wiki/spaces/KGR/pages/491532) Aim
The aim of Kagura is to produce a simple and fast reporting framework, which can be used widely and customised heavily.</description></item><item><title>JDBC Report Template</title><link>https://arran4.github.io/kagura-original/posts/jdbc_report_template/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/jdbc_report_template/</guid><description>JDBC Report Template JDBC Report Template reports/TheAnswers/reportconf.yaml type: &amp;ldquo;JDBC&amp;rdquo; classLoaderPath: &amp;ldquo;com.mysql.jdbc.Driver&amp;rdquo; jdbc: &amp;ldquo;jdbc:mysql://localhost:3306/test&amp;rdquo; username: &amp;ldquo;test&amp;rdquo; password: &amp;ldquo;test&amp;rdquo; sql: &amp;ldquo;SELECT id, question, answer FROM Answers &amp;lt;@where&amp;gt; &amp;lt;@clause render=param.questionQuery?has_content&amp;gt; question=${method.value(param.questionQuery)} /@clause /@where &amp;lt;@limit /&amp;gt;&amp;rdquo; columns:
name: question label: Question name: answer label: Answer extraOptions: reportName: &amp;ldquo;The Answers&amp;rdquo; directory: &amp;ldquo;Folder 1&amp;rdquo; description: &amp;ldquo;This is a sample report&amp;rdquo; image: &amp;ldquo;http://jentrata.org/images/jentrata.png&amp;quot; paramConfig: { type: String, id: questionQuery, name: &amp;ldquo;Question to search for&amp;rdquo;, help: &amp;ldquo;Leave blank for any&amp;rdquo;, placeholder: &amp;ldquo;None&amp;rdquo; }</description></item><item><title>JNDI JDBC Freemarker Report</title><link>https://arran4.github.io/kagura-original/posts/jndi_jdbc_freemarker_report/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/jndi_jdbc_freemarker_report/</guid><description>JNDI JDBC Freemarker Report JNDI/JDBC Freemarker ReportUpdated Jan 21, 2014* JNDI/JDBC Freemarker Report Jan 21, 2014Cloud editor
This is the most likely type of report you will require. It&amp;rsquo;s a report which takes it&amp;rsquo;s data from a data source such as MySQL and returns the output. (Not all reports do this.) Prerequisites For this to work you need several things:
What parameters you are going to use, and how to query them</description></item><item><title>Kagura js</title><link>https://arran4.github.io/kagura-original/posts/kagura_js/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/kagura_js/</guid><description>Kagura js Kagura.jsUpdated Feb 21, 2014* Kagura.js Feb 21, 2014Cloud editor
Kagura.js is a javascript file which is the driving force of the example javascript web page, which you can use as a basis for your reporting front end. Or you can write something yourself. Or go half way and use the kagura.js javascript file and hire a web designer to make a nicer front end for you your site.</description></item><item><title>Karaf</title><link>https://arran4.github.io/kagura-original/posts/karaf/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/karaf/</guid><description>Karaf KarafUpdated Feb 11, 2014* Karaf Feb 11, 2014Cloud editor
The Kagura Karaf container is designed to work out of the box, with an accompanying HTTP server for the presentation layer. Out of the box Kagura&amp;rsquo;s karaf container provides the core Kagura reporting REST services. It comes with an example &amp;ldquo;Authentication REST&amp;rdquo; backend. This is a sample REST end point for if you were to use REST configuration. The true power in the Kagura REST container is the flexible container that it runs in, allowing live changes to parameters for instance.</description></item><item><title>Karaf Deployment</title><link>https://arran4.github.io/kagura-original/posts/karaf_deployment/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/karaf_deployment/</guid><description>Karaf Deployment Karaf Deployment
First we need to checkout the code: git clone https://github.com/base2Services/kagura.git cd kagura mvn compile package install
Open up another terminal:
In terminal 1, we are going to start the Jetty service, this is where we host the Terminal 1 cd example/javascript mvn org.mortbay.jetty:jetty-maven-plugin:8.1.12.v20130726:run
Press ^C to end it.
In terminal 2, we are going to start the Camel service which provides the REST backend. All calls the the rest services are routed through Jetty to prevent cross domain scripting issues.</description></item><item><title>Library</title><link>https://arran4.github.io/kagura-original/posts/library/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/library/</guid><description>Library Library
See As a Library</description></item><item><title>Maven Deployment</title><link>https://arran4.github.io/kagura-original/posts/maven_deployment/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/maven_deployment/</guid><description>Maven Deployment Maven Deployment
First we need to checkout the code: Terminal 1 git clone https://github.com/base2Services/kagura.git cd kagura mvn compile package install
Open up another terminal:
In terminal 1, we are going to start the Jetty service, this is where we host the Terminal 1 cd example/javascript mvn org.mortbay.jetty:jetty-maven-plugin:8.1.12.v20130726:run
Press ^C to end it.
In terminal 2, we are going to start the Camel service which provides the REST backend. All calls the the rest services are routed through Jetty to prevent cross domain scripting issues.</description></item><item><title>Report Providers</title><link>https://arran4.github.io/kagura-original/posts/report_providers/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/report_providers/</guid><description>Report Providers Authentication ProvidersUpdated Feb 12, 2014* Authentication Providers Feb 12, 2014Cloud editor
Authentications providers are an optional component or base component provided by the reporting-core. They are designed for 2 purposes:
Mapping Reports to Users (via groups)
Restricting the users of the system to users who are allowed to access the product
There are a couple of existing Authentication providers, and planned Authentication providers: (As of 1.4)
Authentication Provider The file Authentication provider expects to see 2 files in the reports directory: users.</description></item><item><title>REST API</title><link>https://arran4.github.io/kagura-original/posts/rest_api/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/rest_api/</guid><description>REST API Report ProvidersPublished Feb 14, 2014* Report Providers Feb 14, 2014Cloud editor
Report Providers are a tool used to return the report data, they are fairly straightforwards.
Report providers:
Report Provider Currently (1.4) the only supported mechanism for storing a file. It provides a report from a configuration as follows:
/reportconf.yaml or /reportconf.json
It depends on the com.base2.kagura.reportloc configuration option for the location. More information can be found here: Building a basic JNDI/JDBC report</description></item><item><title>Screenshots</title><link>https://arran4.github.io/kagura-original/posts/screenshots/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/screenshots/</guid><description>Screenshots Screenshots
Please note, as the nature of Kagura is more of a library, but provides example service and presentation (web) layers. These screenshots do not dictate the final look of the site and users are encouraged to modify the end site to match their requirements. Version 1.2
The login screen
The welcome page:
List of reports:
A sample page. Remember we recommend you customise this.
A sample of a report configuration &amp;amp; directory structure.</description></item><item><title>Setting up File Authentication</title><link>https://arran4.github.io/kagura-original/posts/setting_up_file_authentication/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/setting_up_file_authentication/</guid><description>Setting up File Authentication Setting up File Authentication Provider user and groups
There are a couple of Authentication providers one is the &amp;ldquo;File Authentication Provider&amp;rdquo; which is a simple file based authentication. This particular one does not employ encryption. It&amp;rsquo;s designed for demo sites. I would suggest using another authentication provider. The setup is simple, you create 2 files in the reports/ directory,
users.yaml groups.yaml Users can&amp;rsquo;t have direct access to reports, they have be placed in a group in-order to access the reports.</description></item><item><title>Use Cases</title><link>https://arran4.github.io/kagura-original/posts/use_cases/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/use_cases/</guid><description>Use Cases Use Cases
Where would you use Kagura:
When you need a reporting web service that is quick to deploy and more developer friendly than existing frameworks When you need something that you can customize as all levels When you need something you can embed into your application or run separately, with no changes required to port your reports across When you need a report service which you can run in a stateless environment</description></item><item><title>War Deployment</title><link>https://arran4.github.io/kagura-original/posts/war_deployment/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://arran4.github.io/kagura-original/posts/war_deployment/</guid><description>War Deployment War Deployment
Goto http://tomee.apache.org/downloads.html download the JaxRS version. As of writing we have developed the War file for version 1.6. % tar xf apache-tomee-1.6.0-jaxrs.tar.gz % ln -sf ~/.m2/repository/com/base2/kagura/war-rest/1.2/war-rest-1.2.war apache-tomee-jaxrs-1.6.0/webapps/ % cd apache-tomee-jaxrs-1.6.0 % ./bin/startup.sh
When it starts visit:
http://localhost:8080/war-rest-1.2/
Reports are embedded into the war.
I recommend you use JNDI, you can find out how to setup JNDI data sources in tomee here: http://tomee.apache.org/configuring-datasources.html.</description></item></channel></rss>