Brio Overview
14
1 1 Overview of BRIO Tool Overview Brio BI tool supports web-based reporting, analysis, and querying of multiple data sources. Report files are created by developers and deployed to the Brio Server, where they may be accessed by direct http addressing or integrated within existing web applications. Users of the Brio Reporting system are stored in a repository database and placed within groups. Groups are then authorized to view/analyze/query reports.
Transcript of Brio Overview
11
Overview of BRIO Tool
Overview
Brio BI tool supports web-based reporting, analysis, and querying of
multiple data sources.
Report files are created by developers and deployed to the Brio
Server, where they may be accessed by direct http addressing or
integrated within existing web applications.
Users of the Brio Reporting system are stored in a repository
database and placed within groups. Groups are then authorized to
view/analyze/query reports.
2
BRIO Architecture
2
Components
Tomcat4.1
Web Server
Brio SQL SERVER Repository
Brio services
Administration Servlet
Job Manager ServletPersonal Page Servlet
Browse ServletiHTML Servlet
Data Access Servlet
PCS Internal Apps
WEB BROWSER
Administrator WEB BROWSER
User and DeveloperWEB BROWSER
User
Email,Printing,FTP
Brio Server
dbabcmsndbsrv.svc.db.com
Data sources
https://apps.pwm.pcb-ito.gto.intranet.db.com/AppsHome/
http:\\briportal\Hyperion\Browse\main
OCE
OCE
http:\\briportal\Hyperion\Browse\main
Data Access ServiceIntelligence ServiceSearch ServiceEvent ServiceCrawl Service
Session ManagerAuthorization serviceAuthentication serviceName ServicePublisher ServiceRepository Service
Win 2003 Enterprise with service pack 2
CMS – SQL
cms.svc.db.com
Commission SQL
dbabodssql.svc.db.com
Advent SQL
Prgdw.svc.db.com
MISSQL
pcsmis.svc.db.com
MAB UDB
dbabbatch.svc.db.com
OS FILE SYSTEM
NOTE: Services can be grouped as1.Data Access Service2.Intelligent Service3.Windows Service (Authorization & Authentication service)4.Super Services (all other services)
JDBC
3
Technical Architecture of AB Brio-US
3
The Brio application is categorized in three components.
1st Component – Web Server (Tomcat)
2nd Component – Applications (Brio)
3rd Component – Data (MS SQL server, Sybase, UDB, Other
Database systems (MS Access, Oracle, etc..)
Brio reports access the data from Various Data sources.
Technical Architecture of AB Brio-US
Plugins: To view various format reports
1.Excel (.xls),Lotus 1-2-3 (.wks),Tab delimited (.txt),HTML (.htm),Comma
delimited (.csv),JPEG (.jpg),PDF (.pdf)
2. bqy – Hyperion client (BRIO Insight)
(bqy - user can perform analysis, processing, or even data model changes,
depending on permission granted)
Brio Intelligence Clients includes
1. A web-based tool (Internet Explorer)
Users access the Reports via web Browser.
2. Desktop client/server applications (Explorer, Designer)
Windows based metadata modeling tool.
44
5
Tools and Technologies
Tools
5
Tool Name Purpose Brief Description
Brio 8 .5.0 Reporting
Brio reports serve as a web-based reporting mechanism for custom
web applications, such as the client portal.
Brio Explorer 8.5
Desktop Metadata
development tool
A client/server-based tool that delivers query, analysis, and
reporting capabilities
Brio Insight Plug
in 8.5.Rev1
Plug in for Opening BQY
files.
Need to install on Local machine to
open BQY files
Functional Architecture
NOTE:1.Scheduler can run reports for either BRIO Portal or Internal Apps2.Retention period for the reports can be defined and can very from 1 day to 1 year
7
Report consumers (Users)
This application generates the report which provides
various kinds of reports for various departments across
deutsche bank.
MIS Reports
Collateral Monitoring System
Compliance automation Reports
Commission system
Performance Reports
Gatekeeper Reports
Controlling reports
Middle Office reports
8
Report consumers (Users)
Most of the reports (Enterprise Reports) access data from UDB database (Feed for UDB is from various (mostly from Pershing,
ADP))
MIS Reports(Managerial Information System)
Access data from MS SQL Server MIS Database
CMS(Collateral Monitoring System)
Access data from MS SQL Server CMS Database
Compliance automation Reports
Access data from MS SQL Server Compliance Reporting Database
Commission system
Access data from MS SQL Server NSTARS Database
9
Report consumers (Users)
Performance Reports
Access data from Advent SQL Data Mart
Gatekeeper Reports
Access data from SYNTICKET Sybase Database
Controlling reports
Access data from Overrides.txt
Middle Office reports
Access data from ACH_Cash_Management.txt
Brio Portal Access (http://brioportal/Brio/) ( Approx. 80 Users)
Internal Apps Access (http://www.atlas.db.com/) ( Approx. 700 Users)
About 230 scheduled reports are available for ABCRD, ABMIS, Atlas,
Gatekeeper and about 260 Ad Hoc reports available for various PCS
applications and departments.
10
Report consumers (Users)
Important tables in UDB
VACCT_MAIN,VACCT_ADD-Main,
VPERPSN,VPERBAL,
VPERMAST,VPERSEC,
VRPTINST,VRPTDATA,
PARABASE,INDVBASE,
INDVBRKR,GEOSBASE,
BRKRBASE,BRKBU01,
STDDBASE,
BROKBASE,BUSEBASE.
Report consumers (Users)
For latest updated data Brio reports are always dependent on the various
data sources as mentioned above. If any of the data sources are not
updated with latest data on daily basis, then we need to re run the
associated job for getting updated data on the reports.
Major Differences between Internal Apps Access and Brio Portal Access
MIS Reports, Compliance Automation Reports and Collateral Monitoring
System Reports can only be accessed via Internal Apps because Java
front-end in Internal Apps filters and passes the appropriate parameters.
Reports in Internal Apps are granted at the folder level whereas in Brio
each report can be granted permission. In Internal Apps - user is entitled to
a folder or subfolder, he/she can see all reports under that folder or
subfolder. In Brio Portal, each report can be granted access selectively.
1111
12
Functionality
The Hyperion Enterprise Server, named nycpwmasp2740
communicates with web clients (browsers) and custom
applications running from web servers
They access the Hyperion Report Server either through the
Internal Apps Portal or the Hyperion web Portal directly. There
are currently about 700 Internal app and 80 Hyperion portal
users.
The Disaster Recovery server nycpwmasb2743.us.db.com is
configured identically to nycpwmasp2740 and is located in
the Harbor side NJ data center.
13
Brio Servers and location
Environment Server Name IP Location
Production
(Prod)
nycpwmasp27
40
10.164.107.61 Harbor side, NJ
Disaster
Recovery (DR)
nycpwmasb2743 10.164.192.85 Harbor side, NJ
Development/
User Acceptance
Test (Dev/UAT)
nycpbasp2414 10.152.39.32 Harbor side, NJ
14
Risks, Issues and Dependencies
No version control system. If need to restart Brio server, we have to depend on SA. Reports Design Documents are not available.
14
