Citrix Meta Frame XPe Resource Manager Summary Database

Citrix Meta. Frame XPe Resource Manager Summary Database Implementation Historical Reporting and Billing

Agenda n Customer Requirement n Architecture n Operation n User Interface n Availability n Hands on

Customer Requirement Currently, RM stores data for 48 hours n Resource Manager on Meta. Frame XPe will only store server, session and application metrics for up to 48 hours n Data store, RMLocal. Database, local to every server n No central repository of data

Customer Requirement Customer Demand n n n Customers require data older than 48 hours. Customers want to be able to bill users/departments for computing time. This functionality was in CRMS 1. 0 b, but not in RM.

Summary Database Architecture

Summary db - Architecture Summary Database n n n 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

Summary db - Architecture Summary Database Oracle 8 i or 9 i, SQL Versions 7 or 2000

Summary db - Architecture Database Connection Server n n 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 Database.

Summary db - Architecture Database Connection Server Summary Database

Summary db - Architecture Resource Manager Server n n n 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 server.

Summary db - Architecture Resource Manager Servers IMA event Bus Database Connection Server Summary Database

Summary Database Operation

Summary db - Operation Resource Manager Server n Data for selected metrics, summarized in memory n Written to a flat text file once an hour n Files written to l n Program FilesCitrix Resource ManagerSummary. Files. This is all done by RMMonitor. SS

Summary db - Operation Resource Manager Server n n Session, process appmetrics and events are always stored. Server metrics can be collected at user definable times of day

Summary db - Operation Data Collection n A schedule is set from the UI for when data collection should occur.

Summary db - Operation Data Collection n RMSummary. DBSS on each server sends “time for me to send my log file”

Summary db - Operation Data Collection n This then gets put in a queue on the DCS Server 1 Server 2 Server 3 Server 4 Server 5 Server 6 Server 7

Summary db - Operation Data Collection n First 4 machines told “Send me your log file now” Server 1 Server 2 Server 3 Server 4 Server 5 Server 6 Server 7

Summary db - Operation Data Collection n As the files arrive the next message is sent

Summary db - Operation Data Collection n n 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 1 2

Summary db - Operation Data Collection n Both files are kept until the DCS confirms that it has received and processed that server’s file 1 2

Summary db - Operation Data Collection n n Both files are kept until the DCS confirms that it has received and processed that server’s file The first file is then deleted 2

Summary db - Operation Data Collection n If no confirmation is received, both files are sent on the next file request and another log file started. 1 2 3

Summary db - Operation Writing data to the Summary db n n 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 one file may be being written at any time.

Summary db - Operation Note: n n n 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 the DCS

Summary db - Operation Writing data to the Summary db n On the initial connection 5 stored procedures are loaded into the database. l ADDMETRIC l ADDSESSION l ADDPROCESS l ADDAPPMETRIC l ADDEVENT

Summary db - Operation Writing data to the Summary db n n n 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 procedures

Summary db - Operation Writing data to the Summary db n The RM service is structured so that when no imports are taking place the DSN is freed up

Summary db - Operation Purging the Summary Database n Data in the Summary db is split into 4 categories l Metrics l Session and Process (Billed) l Session and Process (Not – Billed) l Events

Summary db - Operation Purging the Summary Database n Each category has its own user definable retention period n This can be indefinite n Data is purged at midnight every day (night? ) n The purging is achieved by the relevant stored procedures being invoked by the DCS

Summary Database User Interface

Summary db – User Interface Several Additions have been made to the Resource Manager User Interface:

Summary db – User Interface Process Summary:

Summary db – User Interface User Summary:

Summary db – User Interface Server Summary:

Summary db – User Interface Summary Database:

Summary db – User Interface Summary Database:

Summary db – User Interface Summary Database:

Summary Database Billing

Summary db – Billing overview n Billing reports are based on the information stored in the summary database

Summary db - Billing overview n Configure Fees

Summary db - Billing overview n Define cost Centers

Summary db - Billing overview n Add new cost centers

Summary db - Billing overview n Add list of names

Summary db - Billing overview n Edit Cost Center

Summary db - Billing overview n 2 methods of billing on the collected data: l By Cost Center l By Domain

Summary db - Billing overview n Billing reports by cost center

Summary db - Billing Bill by Cost Center n Each Cost center selected will have 1 distinct billing report created for it

Summary db - Billing overview n Billing reports by Domain

Summary db - Billing Bill by selected Domain n 1 report generated for entire list of users

Summary db - Billing Report Options

Summary Database Time Zones What about different time zones?

Summary db – Time Zones If you have a farm spanning different continents, what time should be stored?

Summary db - Billing All times recorded in UTC with a bias n n n UTC is essentially GMT The bias is the offset of the time zone that the server is in. E. g. . FTL = -5, SLC = -7, Paris = +1 etc

Summary db - Billing UTC Format n DD-MMM-YYY hh: mm: ss +- hh: mm n This gives a standard convention to displaying times and also gives indication as to where in the world a server is. n Server usage reports run for the hours between 9: 00 and 5: 00 will calculate that time local to the server. n User summary reports display the time local to the CMC the report was run on. n Process Summary reports show the time local to the CMC.