Citrix MetaFrame XPe
Resource Manager
Summary Database Implementation
Agenda
Agenda
Customer Requirement Architecture
Operation
Customer Requirement
Currently, RM stores data for 48 hours
Resource Manager on MetaFrame XPe will only store
server, session and application metrics for up to 48 hours
Customer Requirement
Customer
Demand
Customers require data older than 48 hours.
Customers want to be able to bill users/departments
for computing time.
Summary db - Architecture
Summary Database
1 Summary Database per farm.
Can be the same machine as the Persistent
Store (although a different database).
Same databases supported as for the PS
(except Access).
Summary Database
Oracle 8i or 9i,
SQL Versions 7 or 2000
Summary db - Architecture
Database Connection Server
1 Database Connection Server per farm.
DSN connection to database owned solely
by this machine.
Solves scalability issues encountered in
CRMS.
Locate the DCS close to the Summary
Summary Database
Summary db - Architecture
Database Connection
Summary db - Architecture
Resource Manager Server
Each server to be monitored must have
Resource Manager loaded.
Summarized data sent to the DCS server
once a day (or on request) as a flat text file.
DCS then writes data to the Summary db
Summary Database
Summary db - Architecture
Summary db - Operation
Resource Manager Server
Data for selected metrics, summarized in
memory
Written to a flat text file once an hour
Files written to
Program Files\Citrix\Citrix Resource
Manager\SummaryFiles.
Summary db - Operation
Resource Manager Server
Session, process appmetrics and events are
always stored.
Server metrics can be collected at user
Summary db - Operation
Data Collection
A schedule is set from the UI for when data
Summary db - Operation
Data Collection
RMSummaryDBSS on each server sends
Summary db - Operation
Data Collection
This then gets put in a queue on the DCS
Summary db - Operation
Data Collection
First 4 machines told “Send me your log file
Summary db - Operation
Data Collection
Summary db - Operation
Data Collection
Once a servers’ summary file has been sent,
a copy is kept as backup
As a new process starts or session starts, a
new log file is started
Summary db - Operation
Data Collection
Both files are kept until the DCS confirms
that it has received and processed that server’s file
Summary db - Operation
Data Collection
Both files are kept until the DCS confirms
that it has received and processed that server’s file
The first file is then deleted
Summary db - Operation
Data Collection
If no confirmation is received, both files are
sent on the next file request and another log file started.
3
Summary db - Operation
Writing data to the Summary db
Once the first file is received the DCS will
start writing the information to the Summary Database server.
This is a multi-threaded process, more than
Summary db - Operation
Note:
The summary database is not automatically
created on install as the Local Database is.
The administrator must first create the
database on the database server
Following this, the DSN must be created on
Summary db - Operation
Writing data to the Summary db
On the initial connection 5 stored
procedures are loaded into the database.
ADDMETRIC
ADDSESSION
ADDPROCESS
ADDAPPMETRIC
Summary db - Operation
Writing data to the Summary db
Once the connection has been made, the
DCS parses the text file and passes the arguments onto the stored procedures.
The stored procedure acts on the parameters
that it is given and invokes the appropriate stored procedure
ADO is the interface to connect to the stored
Summary db - Operation
Writing data to the Summary db
The RM service is structured so that when
Summary db - Operation
Purging the Summary Database
Data in the Summary db is split into 4
categories
Metrics
Session and Process (Billed)
Session and Process (Not – Billed)
Summary db - Operation
Purging the Summary Database
Each category has its own user definable
retention period
This can be indefinite
Data is purged at midnight every day (night?)
The purging is achieved by the relevant
Summary db – User Interface
Summary db – User Interface
Summary db – User Interface
Summary db – User Interface
Summary db – User Interface
Summary db – User Interface
Summary db – User Interface
Summary db – Billing
Billing overview
Billing reports are based on the information
Summary db - Billing
Billing overview
Summary db - Billing
Billing overview
Summary db - Billing
Billing overview
Summary db - Billing
Billing overview
Summary db - Billing
Billing overview
Summary db - Billing
Billing overview
2 methods of billing on the collected data:
By Cost Center
Summary db - Billing
Billing overview
Summary db - Billing
Bill by Cost Center
Each Cost center selected will have 1
Summary db - Billing
Billing overview
Summary db - Billing
Bill by selected Domain
Summary db - Billing
Summary Database
Time Zones
Summary db – Time Zones
Summary db - Billing
All times recorded in UTC with a bias
UTC is essentially GMT
The bias is the offset of the time zone that
the server is in.
Summary db - Billing
UTC Format
DD-MMM-YYY hh:mm:ss +- hh:mm
This gives a standard convention to displaying
times and also gives indication as to where in the world a server is.
Server usage reports run for the hours
between 9:00 and 5:00 will calculate that time local to the server.
User summary reports display the time local to
the CMC the report was run on.
Process Summary reports show the time local
