Skip to end of metadata
Go to start of metadata

Use case description

  1. Some physical units generate data.
  2. Data is put into a JMS Queue.
  3. Consumers of the data
    1. Web application
      1. Admin of physical units.
      2. Live queries
    2. Application for providing reports on the data.
  4. User should only have one username and password for authentication.
  5. Users are only allowed to see data for her own units.
  6. It should be possible to download a report from the web application.
  7. Creating new reports may require experts/developers/dbas, but it should not be necessary to restart the web application to get hold of a new report.
  • Let's assume we want to use a commercial tool to do data mining and reporting.
  • Use an off-the-shelf BI/reporting tool to generate reports.
MS SQL Server

  • Reporting Services (or SSRS)
    • a 'tweaked' version of Visual Studio to make creating/developing/editing these reports much easier. That version of visual studio is called SQL Server Business Intelligence Design Studio (or BIDS).
  • Analysis Services

How to maintain a duplicated version of the master data

Alt 1 - DB vendor way
  • Use RDBMS functionality to duplicate data from one database to another.
    • On update/insert
    • Scheduled sync (e.g. nightly)
Alternative 2 - the developer way
  • Polyglot persistence

Integrate reports in web app

  • How easy is it to fetch the reports from the commercial tool from the web application?
  • Can the two data models diverge or is that a problem?
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.