Administator Activities
The Administrator defines:
- Queries and query Parameters
- Users and user Privileges
- Target Datasources
- Query Groups and Rules
- Portlets Containers to group queries&text objects
The normal flow when defining a new query is:
- Obtain the plain SQL statement and identify parameters
- If the target datasource is not already defined, define it (make sure the jdbc driver is in your servlet engine path)
- If new queries are needed to retrieve list of values (LOV) - in order to dynamically build parameter value lists - define them
- Define the query and the query parameters
- Modify user privileges in order to let users to execute the query
Follow the Quick Start link to learn how to share database content in a few screenshots.
A detailed manual for Administrators is available: download the Art Admin Manual pdf from the download area
ART Query
An ART query is composed by two parts:
- Header and Statement (SQL): The header contains query properties like Name, Type, Group, Description, Target database, Statement etc. The Type flag states if the output is tabular, crosstab, chart etc. The Statement is a plain SQL text where some parameters values (in the WHERE part) are substituted by labels. An xml-style syntax can be used to create dynamic SQL code.
- Parameters: Before executing a query, users are prompted to enter query parameters. The values could be string, integer, number, date or values picked from a dynamic pop-up list.
What do you need to plug a SQL query in Art?
Just substitute parameters with labels and paste the SQL code:
SELECT COL1, COL2
FROM MYTABLE
WHERE COL3 LIKE #param#
To create SQL queries, you can use your preferred query tool (Tora, Toad, SQL Analyzer, dbcat, etc.).
ART Text Object
A Text Object is an html fragment that can be edited by authorized users via a WYSIWYG web-based editor. It is used mainly to provide descriptive sections in portlets containers, but you can easily find how to use it as a simple CMS.
ART Portlets Container
A Query or a Text Object can be considered as a portlet, i.e. an independent embeddable frame. The ART Portlets Container allows to group portlets within a single page - simulating a JSR-168 style portal. This permits to quickly group result sets and display metrics in a single screenshot.
How difficult is to create a portlets container to embed some existing queries/graphs?
Just get the Id of the queries and type:
<PORTLETCONTAINER>
<COLUMN>
<PORTLET>
<TITLE>A Title</TITLE>
<OBJECTID>2</OBJECTID>
</PORTLET>
<PORTLET>
<TITLE>A Title</TITLE>
<ONLOAD>false</ONLOAD>
<OBJECTID>3</OBJECTID>
</PORTLET>
</COLUMN>
<COLUMN>
<PORTLET>
<TITLE>A Title</TITLE>
<REFRESH>30</REFRESH>
<OBJECTID>4</OBJECTID>
</PORTLET>
</COLUMN>
</PORTLETCONTAINER>
This will create a two columns portlets container, with two queries on the left column and one in the right column. The latter autorefreshes its content each 30 seconds, while the second starts minimized.
|
ART