|
A good reporting tool has pre-defined integration kits with popular platforms like Siebel, Baan, SAP and people-soft. The reporting tool should be quickly configurable in terms of report designs, connections, security/authentication, data model up-dation (in the reporting tool)
Reporting Server Data Base Connectivity
Native Data Base connectivity
This is simplest of all-the connectivity to the native database, like MS reporting services connecting to MS-SQL Server.
Change data base connection information at run time OR view time.
There are two ways to set-up a database connection. One is that you set it up before you start processing OR at the time of system configuration. All the reports you run, assume this database connection and look for the data sources through that database connection. However, sometime the reports are accessing different data sources from different databases and the setting-up of database connection (OR changing them) is built in the report itself. As the report is running, it changes its connection. For example- you are running a query which first picks up the data from sales database and then from products database, to generate a query result of ‘product-wise sales’.
Enterprise Reporting Connectivity to OLAP servers
Enterprise reporting uses different data sources and OLAP is one of them. Some reporting tools have got ways to leverage the OLAP server connections. For example, they share common OLAP Analysis functions.
Native Reporting connectivity to standard ERP and CRM applications
This feature has some pre-set (pre-defined) database connections to the standard enterprise packages, which includes the database connections and data source definition.
Java Beans connectivity
|
