Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Map
Process
Web Client
In an HTML 4.0 compliant browser, InfoView provides the option to
create a new Web Intelligence Document. Once the new Web
Intelligence Document button is selected from the toolbar, client side
JavaScript requests a new page: new.do (Java).
This process flow details the Java-based InfoView configured for
HTML.
Web Server
A 3rd party Web Server, typically Internet Information Server (IIS) or
Tomcat Apache, the Web Server, logs the request and forwards it to the
Web Application Server.
Page 2 of 38
Web Application Server
The Web Application Server is a collection of files written by Business
Objects in either Java or ASP.Net. The selected solution is determined
by the choice of Web Server as Microsofts Internet Information Server
supports ASP.Net and Tomcat Apache processes Java pages.
Tools
HTTPAnalyzer
HTTP Analyzer is a sniffer tool that monitors and inspects
HTTP/HTTPS traffic in real time. It displays a wide range of
information, including: header, content, cookies, query strings, post
data, request and response stream, and redirection URLs.
http://www.httpanalyzer.com
Web Server
Most vendors provide a set of monitoring tools for their Web Servers.
Both Internet Information Services (IIS) and Apache Tomcat provide
log files as a means to capture their respective workloads, though the
level of detail and options differs.
Internet Information Server Log File Location
[Install Path]\System32\Logs\
Page 3 of 38
By default, new log files created daily, though the size, occurrence and
details recorded are configurable through the IIS Manager.
Apache Tomcat Logs File Location
[Install Path]\Program Files\Business Objects\Tomcat\Logs
The Administration utility allows the Administrator to set the level in
addition to the location of the log files.
Page 4 of 38
Config
Page 5 of 38
Step: 2
Map
Process
Tools
Page 6 of 38
Step: 3
Map
Process
Tools
Page 7 of 38
SQL Statements executed against the server in addition to a range
of information related to duration, i/o, deadlocks and locking.
Step: 4
Map
Process
Page 8 of 38
Step: 5
Map
Process
Tools
HTTPAnalyzer
HTTP Analyzer is a sniffer tool that allows you to monitor and inspect
HTTP/HTTPS traffic in real-time. It displays a wide range of
information, including: header, content, cookies, query strings, post data,
request and response stream, redirection URLs and more.
http://www.httpanalyzer.com
Page 9 of 38
Step: 6
Map
Process
Page 10 of 38
;UnivName=beach&lang=en
Tools
HTTPAnalyzer
HTTP Analyzer is a sniffer tool that allows you to monitor and inspect
HTTP/HTTPS traffic in real-time. It can trace and display wide range
of information, including header, content, cookies, query strings, post
data, request and response stream, redirection URLs and more.
http://www.httpanalyzer.com
Step: 7
Map
Process
To fulfill the request for a list of objects and classes related to the
selected Universe, the Report engine is invoked and a Web
Intelligence Session created.
Report Engine
To create and later work with a report, an instance of the Report
Page 11 of 38
Engine is required. Created from the Enterprise Session, the Report
Engine is reused during the lifetime of the Enterprise Session (also
known as a Logon Session or User Session). The Enterprise session
was established when the Web Client first logged into InfoView. The
Enterprise session contains a range of user and security settings.
The Report Engine creates a proxy SDK Document Instance after
locating the Web Intelligence Server(s) through the SDK or OCA
library. It is upon creating the SDK Document Instance that the Web
Intelligence Session is created.
Web Intelligence Session
A Web Intelligence Session (also known as a Cadenza Session or
Document Session) is initialized. Created specifically for that
document, the session is not be reused.
The Web Intelligence Session is used for:
Creating and managing temporary folders (on the Web
Intelligence Server)
Storing local copies of Web Intelligence Document (WID) files
Storing Universes
Considered a child session, A Web Intelligence Session inherits user
and security settings from its parent Enterprise Session. The Central
Management Server stores session information pertaining to the
session in the repository and the license count is incremented.
Once the web Intelligence session has been established, then the list of
Universes can be retrieved. The Web Intelligence Report Server calls
on the Query Technique (QT) component to generate a SQL statement
that will be used to retrieve metadata, including its location in the
Input File Repository. The Connection Server (also a part of the
Report Server) executes the statement.
Tools
Page 12 of 38
In a pipe delimited format, the Classic BO Trace is used to record in
explicit detail, the operations of the Web Intelligence Report Server.
Once the tracing levels have been set, the trace will identify a range of
operations including working with sub components and creating and
opening files.
Working with this trace requires a BO_Trace.ini file to be created.
Three optional environment variables can also be set:
Environment Variables
BO_TRACE_CONFIGDIR = c:\mypath
BO_TRACE_CONFIGFILE=c:\mypath\BO_TRACE.INI
BO_TRACE_LOGDIR= C:\MyLogFolder
BO_TRACE.INI
active=true;
important=<<; (options are <<,<=,==,>=,>> where << logs
informational lines to >> which is critical/error lines)
size=10000;
keep=true;
Page 13 of 38
Step: 8
Map
Process
Page 14 of 38
Tools
Configuration
Page 15 of 38
Step: 9
A list of available objects for the given Universe back to the Web
Application Server (Web Intelligence SDK).
Map
Process
Using the Universe files from the session folder, the Web Intelligence
Report Server extracts classes and objects into a set of temporary files
before returning the list of objects to entry.jsp.
Tools
Page 16 of 38
Optionally, three environment variables can also be set:
Environment Variables
BO_TRACE_CONFIGDIR = c:\mypath
BO_TRACE_CONFIGFILE=c:\mypath\BO_TRACE.INI
BO_TRACE_LOGDIR= C:\MyLogFolder
BO_TRACE.INI
active=true;
important=<<; (options are <<,<=,==,>=,>> where << logs
informational lines to >> which is critical/error lines)
size=10000;
keep=true;
Page 17 of 38
Step: 10
Map
Process
Tools
HTTPAnalyzer
HTTP Analyzer is a sniffer tool that monitors and inspects
HTTP/HTTPS traffic in real time. It displays a wide range of
information, including: header, content, cookies, query strings, post
data, request and response stream, and redirection URLs.
http://www.httpanalyzer.com
Page 18 of 38
Step: 11
Map
Process
In the Web Client, once Universe objects are selected and report
formatting decided, the document must first be populated before it
can be saved.
InfoView provides a refresh button which submits the values to Web
Intelligence Report Server by calling apply.jsp.
The example below shows a small subset of the posted content
including WOMqueryobs which corresponds to Data Provider
entries in the private session folder in the Web Intelligence Report
Server
WOMqueryobjs=%5BDS0.DO6%2CDS0.DO2%5D&
WOMqueryAtt=%5B-1%2C-1%2Ctrue%2C0%2Ctrue%5D&
WOMqueryfilters=%5Btrue%2C%5B%5D%5D&
Page 19 of 38
WOMquerycontexts=%5B%5D&
WOMdoc=%5Bundefined%2Ctrue%2C%5B%245%2450%2440%244132%246
%244%245255%244255%244202%246%2444%2448.26%24411.682%2440%2
440.79%2440.79%2440.79%2440.79%244%245%245%244text%
Tools
Page 20 of 38
HTTPAnalyzer
HTTP Analyzer is a sniffer tool that monitors and inspects
HTTP/HTTPS traffic in real time. It can trace and display wide range
of information, including header, content, cookies, query strings, post
data, request and response stream, and redirection URLs.
http://www.httpanalyzer.com
Step: 12
Map
Process
Tools
Page 21 of 38
processes in a folder called wicdztrace.
With configurable tracing levels, the trace identifies a range of
operations including working with sub components, creating and
opening files. Errors in the workflow can be easily found as they are
marked with |E|.
Working with this trace requires a BO_Trace.ini file to be created.
Optionally, three environment variables can also be set:
Environment Variables
BO_TRACE_CONFIGDIR = c:\mypath
BO_TRACE_CONFIGFILE=c:\mypath\BO_TRACE.INI
BO_TRACE_LOGDIR= C:\MyLogFolder
BO_TRACE.INI
active=true;
important=<<; (options are <<,<=,==,>=,>> where << logs
informational lines to >> which is critical/error lines)
size=10000;
keep=true;
Page 22 of 38
Step: 13
Map
Process
Using the temporary files contained session folder and values passed
from the Web Application Server, the Web Intelligence Report Server
delegates the stages of initialization, retrieving and rendering to
different components and their sub components.
The following illustrates the flow of information in the Web
Intelligence Server. Each of the components and sub components, are
part of the Web Intelligence Report Server:
Page 23 of 38
WiReportServer
(communication, orchestration)
Query spec
(xml)
Report spec
(xml)
Cube
DP 8 Calculator
(orchestrate
data fetching)
QF
RepEng
(page rendering in xml)
Facilitate communication
between RepEng and
Calculator using iterators
Report output
(xml)
9
Dico
4
2
10
DP : Data provider
QT
CS
(generate SQL)
(execute SQL)
QF : Query facility
QT : Query technique
CS : Connection server
RepEng : Report Engine
Page 24 of 38
9) The data is returned to the Report Engine where the output is
rendered as XML (this includes the styles from the Report
Specification along with the embedded database values
10) The Report Output is cached on the Web Intelligence Report
Server
Tools
Page 25 of 38
RegMon
Capturing both reads and writes to the registry, this monitoring tool
from Sysinternals displays the name of the process, time of access and
value requested or written.
http://www.Sysinternals.com
Database Vender Tools
The vendors database solution may also come with its own tracing
utilities. For example, Microsoft provides a utility called Profiler.
Capturing the server, Profiler displays the SQL Statements executed
against the server in addition to a range of metrics including statement
duration, i/o, deadlocks and locking
Step: 14
Map
Process
The Web Application Server renders the report as HTML and passes
the contents to Report.jsp in the Web Application Server.
Page 26 of 38
Step: 15
Map
Process
Tools
HTTPAnalyzer
HTTP Analyzer is a sniffer tool that monitors and inspects
HTTP/HTTPS traffic in real time. It displays a wide range of
information, including: header, content, cookies, query strings, post
data, request and response stream, and redirection URLs.
http://www.httpanalyzer.com
Page 27 of 38
Step: 16
The Web Client works with the result set and clicks the save
button to save the report.
Map
Process
Page 28 of 38
Tools
HTTPAnalyzer
HTTP Analyzer is a sniffer tool that allows you to monitor and inspect
HTTP/HTTPS traffic in real time. It can trace and display wide range
of information, including header, content, cookies, query strings, post
data, request and response stream, redirection URLs and more.
http://www.httpanalyzer.com
Step: 17
Map
Process
Page 29 of 38
name=North+America+Sales&description=&keywords=&folderId
=2794&categories=&personalCategories=&refreshOnOpen=false
&permanentRegionalFormatting=false
Values passed via the query string
processSave.jsp?iViewerID=1&sEntry=we000900001134fc44625
0&iReport=0&sPageMode=Page&sReportMode=Viewing&iPage
=1&zoom=100&isInteractive=false&ViewType=H&isNew=true&
repotype=&doctype=wid&forceViewType=&mode=full&overwrit
e=true
Tools
Page 30 of 38
Step: 18
Map
Process
Page 31 of 38
DocumentVariable (leaf)
Description
Data insuring integrity of the file.
Description
Used by Cube.
DataSource objects: names and
hierarchies are contained in the
document.
Description and data coming from
DataProviders or queries.
Main C3 document version (currently
2.0) and a string tag cdzDocument.
Document properties: some flags
including autoSynchronize=on/off.
List of anonymous formulas found in
document reports. (User may set a
formula without giving name.
List of variables, tokenized form,
also called serial form (format is
locale independant).
Page 32 of 38
DocumentVariable_Data
Domain for variables having custom
(leaf)
sort.
DATASOURCES (C3 sub-node)
Description
DataSource objects: names, hierarchies
contained in the document.
Number of DataSources, last key id (for
key generation).
For each DataSource (DS):
DSKey(DS0, DS1, DSn)
DS type (QT) and universe connection
string=Repold=12;UnivId=)
Hierarchies contained by the DS:
DS0.DH5
Database connection
string=4;ODBC17;SQLServer
Others DS info such as: repold, name, long
name, comments
DS properties: max =rowfetched,
maxfetchtime
Database (DB) date format, DB number
format, DB decimal separator,
maxOperandsForInList.
Flag: allowMultiSelectContext.
Description
Data from DataProviders.
Name of the DataProvider used in the
document. In case of multiple Data
Providers there will be several storage
nodes: DP0, DP1.
Page 33 of 38
Description (leaf)
DPManager (leaf)
SynchroManager (leaf)f
.wid version.
List of the Data Providers.
For each synchronization: name, key
and source objects.
SynchroManager_Data
For each synchronization object having
(leaf)
custom sort: domain (similar to
DocumentVariable_Data).
DPO (DATAPROVIDERS sub-node)
Description
Description
Page 34 of 38
CDZ (node)
SESSION (CDZ sub-node)
_PROPERTIES (leaf)
MDPWORKFLOWINFOS
(leaf)
Description
Used by Drill engine.
Drill Infos such as Drill Setting, and per
report: Report_Id, Drill_Bar. Per
Drill_Block: Block_Id and
Drill_Hierarchies. Per
Drill_Hierarchies: Dim_Key and
Hier_Key. Drill_Dimensions. Query
filters, Drill parameters.
Page 35 of 38
Node and/or leave name
RE (node)
DOCSPEC (leaf)
Tools
Description
Used by Repeng.
XML of the Report Specification and
formula tokenized form. Also called
serial form (cube team).
Page 36 of 38
Step: 19
Map
Process
The Input FRS location, name and unique identifier for the Web
Intelligence document are updated in the System Repository.
Tools
Page 37 of 38
Step: 20
Map
Process
Tools
Page 38 of 38