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.

1
 BRIO Architecture
NOTE: Services can be grouped as
1.Data Access Service
Administrator https://apps.pwm.pcb-ito.gto.intranet.db.com/AppsHome/

2.Intelligent Service WEB BROWSER WEB BROWSER

3.Windows Service (Authorization &
WEB BROWSER
Authentication service)
User and Developer User
4.Super Services (all other services)

http:\\briportal\Hyperion\Browse\main http:\\briportal\Hyperion\Browse\main CMS – SQL

PCS Internal Apps
cms.svc.db.com

Job Manager Servlet

Administration
Personal Page Servlet Data Access Servlet Commission
Servlet
Browse Servlet SQL
iHTML Servlet
dbabodssql.svc.db.com

Brio services
Data Access Service Session Manager
Brio Server Intelligence Service Authorization service
Authentication service
Advent SQL
Search Service
Name Service Prgdw.svc.db.com
Event Service
Crawl Service Publisher Service
Repository Service
Win 2003 OCE
Enterprise with Components MISSQL
pcsmis.svc.db.com
service pack 2
Tomcat4.1 OS FILE Data sources
Web Server SYSTEM
MAB UDB
dbabbatch.svc.db.com

JDBC

OCE
Brio SQL SERVER
Email,Printing,FTP 2
Repository

dbabcmsndbsrv.svc.db.com
 Technical Architecture of AB Brio-US

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.

3
 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.

4
 Tools and Technologies

 Tools
Tool Name Purpose Brief Description
Brio reports serve as a web-based
reporting mechanism for custom
Brio 8 .5.0 Reporting
web applications, such as the
client portal.
Desktop A client/server-based tool that
Brio Explorer
Metadata delivers query, analysis, and
8.5
development tool reporting capabilities
Plug in for
Brio Insight Plug Need to install on Local machine to
Opening BQY
in 8.5.Rev1 files. open BQY files

5
 Functional Architecture

NOTE:
1.Scheduler can run reports for
either BRIO Portal or Internal Apps
2.Retention period for the reports
can be defined and can very from 1
day to 1 year
 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

7
 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

8
 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.
9
 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.

10
 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.

11
 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.

12
 Brio Servers and location

Environment Server Name IP Location

Production nycpwmasp27 10.164.107.61 Harbor side, NJ

(Prod) 40

Disaster nycpwmasb2743 10.164.192.85 Harbor side, NJ

Recovery (DR)

Development/Us nycpbasp2414 10.152.39.32 Harbor side, NJ

er Acceptance
Test (Dev/UAT)

13
 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