APMaaS Synthetic Monitoring for Web and Mobile

Transcription

1 APMaaS Synthetic Monitoring for Web and Mobile Data Feed API Reference September 2014

2 Please direct questions about APMaaS Synthetic Monitoring or comments on this document to: APM Customer Support FrontLine Support Login Page: Copyright 2014 Compuware Corporation. All rights reserved. Unpublished rights reserved under the Copyright Laws of the United States. U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Compuware Corporation license agreement and as provided in DFARS (a) and (a) (1995), DFARS (c)(1)(ii) (OCT 1988), FAR (a) (1995), FAR , or FAR (ALT III), as applicable. Compuware Corporation. This product contains confidential information and trade secrets of Compuware Corporation. Disclosure is prohibited without the prior express written permission of Compuware Corporation. Use of this product is subject to the terms and conditions of the user's License Agreement with Compuware Corporation. Documentation may only be reproduced by Licensee for internal use. The content of this document may not be altered, modified or changed without the express written consent of Compuware Corporation. Compuware Corporation may change the content specified herein at any time, with or without notice. All current Compuware Corporation product documentation can be found at Adobe Reader is a registered trademark of Adobe Systems Incorporated in the United States and/or other countries. All other company and product names are trademarks or registered trademarks of their respective owners. Local Build: September 26, 2014, 8:25

3 Contents Contents Introduction Data Feed API Features and Notes Documentation Conventions Customer Support Information Chapter 1 Data Feed Options Which Data Feeds are Available? Which Data Feed Do I Need? How Do I Get the Data Feed I Need? Does the Data Feed Provide the Data I Need? Chapter 2 Data Feed Web Services OpenDataFeed Request OpenDataFeed Response OpenDataFeed2 Request OpenDataFeed3 Request GetResponseData Request GetResponseData Response Sample GetResponseData for Backbone Data Sample GetResponseData for Streaming Data GetErrorCodes Request GetErrorCodes Response CloseDataFeed Request CloseDataFeed Response Data Service Security Chapter 3 FTP Data Feeds Access FTP Data Feed Files FTP Data Feed File Information T File Layout Monitor File Layout Site File Layout LM File Layout

4 Contents TO File Layout LMO File Layout Appendix A Data Export Web Service Response SD Index

5 INTRODUCTION This document describes the details and use of the Application Programming Interface (API) that can be used to retrieve collected data sets from the Compuware APMaaS platform. APMaaS Synthetic Monitoring provides the raw data and associated data definitions that can be used to access the data feed performance data. Document Contents This document contains the following chapters: Data Feed Options [p. 9] Provides information about each of the available data feeds and helps you determine which to use. Data Feed Web Services [p. 15] Describes the methods available for retrieving the data. FTP Data Feeds [p. 35] Describes the FTP data feeds available for retrieving the data. Data Export Web Service Response SD [p. 41] Provides an example of the SD that can be downloaded for reference. Data Feed API Features and Notes The Data Feed API supports a broad range of available APMaaS Synthetic Monitoring data sets. The API includes support for discrimination between legacy UTA test measurements and newer BROWSER based test measurements through the inclusion of a browser type attribute which is associated at the test level of every acquired data sample. The API can emit an extended data set for MOBILE tests. The API supports a request mode for eliciting data sets which correspond to samples which have been reclassified as data cuts in the system. Data cut requests are supported across all available response models. Data cut information can be elicited for any series of cut events occurring within the last four days. The API supports a request mode to cause the data service to reinterpret the requested time range as a platform arrival time rather than the current interpretation as test acquisition time. 5

6 Introduction This allows clients greater flexibility for use cases which must take into account latencies within the Compuware APMaaS platform. A companion schema document for the response payload is available. Backward Compatibility of Responses Responses from the 4.0 and later versions of the service are not backward compatible with the earlier versions of the service. While many of the low level element attributes are preserved, many of the containing element names have changed. Specifically, the legacy element name TEST was specialized to better inform the response model being used: TTEST Indicates a Transaction Test Response element emanating from Backbone, Last Mile, Private Peer, or Mobile Systems. TTIMEGROUP Indicates a Transaction Test Time Group Response element emanating from Backbone-based transactions. STREAMTEST Indicates a Stream Test Response element emanating from Backbone Streaming System. DATACUT Indicates a Data Cut Sample element emanating from Backbone, Last Mile, Private Peer or Mobile Systems. MESSAGE Indicates a general purposes messaging element. Documentation Conventions The following font conventions are used throughout documentation: This font Bold Citation Documentation Conventions [p. 6] Fixed width Fixed width bold Fixed width italic Indicates Terms, commands, and references to names of screen controls and user interface elements. Emphasized text, inline citations, titles of external books or articles. Links to Internet resources and linked references to titles in Compuware documentation. Cited contents of text files, inline examples of code, command line inputs or system outputs. Also file and path names. User input in console commands. Place holders for values of strings, for example as in the command: cd directory_name 6

7 Introduction This font Menu Item Screen Code block Indicates Menu items. Text screen shots. Blocks of code or fragments of text files. Customer Support Information APM Community For information on Compuware products, go to the APM Community and click Support. You can review frequently asked questions, access the training resources in the APM University, and post a question or comment to the product forums. You must register and log in to access the Community. Corporate Website To access the Compuware website, go to The Compuware site provides a variety of product and support information. 7

8 Introduction 8

9 CHAPTER 1 Data Feed Options The APMaaS Synthetic Monitoring tools provide a variety of graphical displays that satisfy the reporting and analytical needs of most APMaaS Synthetic Monitoring customers. If you want to correlate your internal business data with APMaaS Synthetic Monitoring data, APMaaS Synthetic Monitoring provides several data feeds can be used to download your account data. Data feeds provide another way for you to access and structure their data. It can be difficult to determine which feed is best for meeting specific requirements. This document first discusses the two APMaaS Synthetic Monitoring data feeds (FTP and Web Services) and then provides a number of recommendations to help you determine which data feed is best for your purposes. Which Data Feeds are Available? APMaaS Synthetic Monitoring provides the following data feeds: Web Services FTP For a large volume (hundreds) of tests, downloads can approach over one gigabyte (1,000 MB) of data in a day, and the File Transfer Protocol (FTP) data feed provides the most efficient way to download this quantity of data from APMaaS Synthetic Monitoring. Most clients, however, download the results of only dozens of tests on average. For these clients, the Web Services data feed is the best way to download test data. Web Service Data Feed The Web Services data feed is the best way for obtaining most data from APMaaS Synthetic Monitoring. Customers can create batch programs to download test-level, page-level, and object-level data and to load that data into data warehouses to supplement business analytics and reporting. If you need support for creating programs to download data, contact Customer Support. Contact Customer Support to have your account enabled for the APMaaS Synthetic Monitoring Web Service data feeds. For more information, see Data Feed Web Services [p. 15]. 9

10 Chapter 1 Data Feed Options FTP Data Feed Use the FTP data feed to obtain large amounts of data at once from the Compuware APMaaS platform. For users that have dozens of tests and large test volume (for example, service providers and ad networks), FTP is the preferred method for application integration at the customer premises. Many tests can generate up to a gigabyte of data, and files are created every hour by scheduled scripts. As with Web Services, this amount of data requires planning and management by technical personnel. Contact Customer Support to set up your FTP account. For more information, see FTP Data Feeds [p. 35]. ed Reports and Alerts While these are not really data feeds, for many users it is critically important to receive an ed report that is already aggregated, processed, and summarized. reports are sent directly to the customer and can be set up in the Compuware APMaaS platform portals. Similarly, ed alerts do not require any processing by the user. Their use is described in the online help. If you need a custom or enhanced report, contact your Account Manager. ML Data Feed For users interested in programming or integrating small subsets of certain Last Mile data via an HTTPS (or HTTP) connection, the ML data feed can be used. NOTE The ML Data Feed is targeted for deprecation, to be replaced by the Web Services Data Feed. At this time, most customers would already be better served by the Web Services Data Feed. Which Data Feed Do I Need? Data feed selection depends on a number of factors, but the key factors are the total number of tests and the target application. You can receive an aggregated weekly summary report of a dozen tests in Microsoft Excel format and reports are perfect for this. Additionally, if you have a dedicated analytics team and want to correlate the test measurements with a web user analytics system, a daily batch pull using a Web Service data feed is the best option. Audience Function # of Tests Target Application or Format Data Feed Recommendation Business SLA reports Under 10 Excel, PDF, HTML, CSV Report Business Aggregated Any Excel, PDF, HTML, CSV Report Business Daily Test Results Under 20 Excel, PDF, HTML, CSV Report Technical Aggregated for Smart Phones Any HTML Report Technical Daily test results Any Analytics or Dashboards Web Services 10

11 Chapter 1 Data Feed Options Audience Function # of Tests Target Application or Format Data Feed Recommendation Technical Daily Batch Load Any Data Warehouse Web Services Technical Hourly Batch Load Over 20 Data Warehouse FTP or Web Services Any Receive Alerts Any Alert How Do I Get the Data Feed I Need? Once you have determined the data feed to use, there are a number of different processes you need to follow, depending on the feed you want. Data Feed Web Services FTP How to get it Have your Compuware account activated first by Customer Support to access this feed. Open a ticket with Customer Support to set up your FTP account. Does the Data Feed Provide the Data I Need? The level of detail is used to determine which data feed to use. Not all data feeds include the same level of detail. For instance, the Last Mile web service includes most, but not all, types of Backbone data. Use the following matrix to determine the data feed to use. Data Source Data Type Web Services FTP Backbone Summary [p. 12] Page [p. 12] W3C [p. 12] Object [p. 12] All [p. 13] Data Cut [p. 13] Streaming (Backbone) Summary [p. 12] Page [p. 12] Object [p. 12] All (for Streaming only) [p. 13] Data Cut [p. 13] Last Mile Summary [p. 12] Page [p. 12] 11

12 Chapter 1 Data Feed Options Data Source Data Type Web Services FTP W3C [p. 12] Object [p. 12] All [p. 13] Data Cut [p. 13] Private Peer Summary [p. 12] Page [p. 12] * W3C [p. 12] Object [p. 12] All [p. 13] Data Cut [p. 13] Mobile Summary [p. 12] Page [p. 12] * W3C [p. 12] Object [p. 12] All [p. 13] Data Cut [p. 13] Classic RUM (previously known as Browser RUM) Raw [p. 13] Chart [p. 13] Geo [p. 13] *Does not include Private Peer extended data attributes. Data Types The data types referenced in the table above are described below: Summary Raw data for each test specified over the time frame requested. Page Raw data for each test for each page in the test over the time frame requested. The hourly page summary rolls up the data by test id, hour, node, and page. W3C Provides information for the W3C performance metrics collected for Backbone, Last Mile, Private Peer, and Mobile. Object Provides information for each object in the test, ordered by test id, timestamp, node, page sequence, and object sequence. NOTE: You cannot aggregate up to test results due to problems around HTTP concurrent connections, compression, and other technical issues. 12

13 Chapter 1 Data Feed Options All Includes Summary, Page, Object, plus Host and Connection data. All (for Streaming only) Includes Summary plus Event, Trace, and Meta data. Data Cut Specific data sets for cut events occurring in the last 4 days. Raw Provides raw Classic RUM (previously known as Browser RUM) data. Chart Provides aggregated Classic RUM (previously known as Browser RUM) data. Geo Provides geographically-based Classic RUM (previously known as Browser RUM) data. 13

14 Chapter 1 Data Feed Options 14

15 CHAPTER 2 Data Feed Web Services The following functions are supported by the Data Feed Web Services interface: Request OpenDataFeed Request [p. 16] OpenDataFeed2 Request [p. 22] OpenDataFeed3 Request [p. 24] GetResponseData Request [p. 27] GetErrorCodes Request [p. 33] CloseDataFeed Request [p. 34] Results Initializes client data feed session based on a set of input parameters. A token in returned to the client for subsequent data pickup. Initializes client data feed session based on a set of input parameters. A token in returned to the client for subsequent data pickup. This interface supports the specification of a mode of operation using relative rather than absolute time windows. Initializes client data feed session based on a set of input parameters. A token in returned to the client for subsequent data pickup. This interface supports the specification of a mode of operation using ARRIVAL time rather than TEST time windows. Get next chunk of data for current feed session. Explicitly expires the current feed session. Exports the raw error code definitions. A session starts with one of the three OpenDataFeed requests. After a successful response completes the handshake, a GetResponseData request starts the actual data transfer. A successful GetResponseData response includes an ML file containing the data payload. A CloseDataFeed request starts the termination of the session after the requested data is transferred. With a successful CloseDataFeed response, the session is completed. The following diagram illustrates how a typical session proceeds. 15

16 Chapter 2 Data Feed Web Services Access to the Data Service Use the following URLs to access the production specifications for the Data Export service. Production URL Production WSDL Production SD OpenDataFeed Request The OpenDataFeed web service method initializes a data feed session based on a number of user-defined criteria. A data feed session always exports a homogeneous dataset based on the MonitorClassDesignator and DataDesignator specified when the session is initialized. Use an OpenDataFeed request to open a session: Parameters susername spassword imonitoridset The account username. The account password Requested set of the Compuware APMaaS platform Monitor/Test reference Identifiers. This set will be cross-referenced with the MonitorClassDesignator and only the requested monitors meeting the specified class criteria will be returned. 16

17 Chapter 2 Data Feed Web Services Parameters NOTE Use the Account Management API to retrieve the Compuware APMaaS platform monitor identifiers available to your account. isiteidset Requested set of the Compuware APMaaS platform Site reference Identifiers. Empty set denotes all sites. NOTE Use the Account Management API to retrieve the Compuware APMaaS platform monitor identifiers available to your account. smonitorclassdesignator sdatadesignator sstarttime Specifies the type of data to be exported in the dataset based on the common class of tests. Supported values are as follows: UTAT Data sets based on transaction tests running on UTA agents BROWSERT Data sets based on transaction tests running on browser agents. Note that this is a shared schema with UTA. STREAM Data sets based on streaming test running on stream agents. PRIVATEER Data sets based on tests running on Private Peer Network LASTMILE Data sets based on tests running on Last Mile Network MOBILE Data sets based on tests running on Mobile Network Specifies the levels of data in the dataset returned to the client for the type of data specified with the smonitorclassdesignator parameter. Supported values are as follows: ALL Returns all levels of data available. OBJECT Returns SUMMARY, PAGE, and OBJECT level data. Mobile datasets will also include MOBILEET level data. PAGE Returns SUMMARY and PAGE level data. Mobile datasets will also include MOBILEET level data. SUMMARY Returns SUMMARY level data. Mobile datasets will also include MOBILEET level data. TIMEGROUP Returns aggregation data over specified time window, up to 24 hours. (see following parameter descriptions). Specifies the starting time boundary for the dataset. The format is: 17

18 Chapter 2 Data Feed Web Services Parameters YYYY-MM-DD HH:MM:SS sendtime sorderdesignator Specifies the ending time boundary for the dataset. The format is: YYYY-MM-DD HH:MM:SS Specifies how the dataset will be ordered. Supported values are as follows: TIME Orders data by time. SITE Orders data by site. MONITOR Orders data by monitor class Supported Combinations Together, the sdatadesignator and smonitorclassdesignator values define what will be included in the retrieved dataset. The supported combinations are listed in the following table. sdatadesignator ALL OBJECT PAGE smonitorclassdesignator UTAT BROWSERT STREAM PRIVATE PEER LASTMILE MOBILE UTAT BROWSERT PRIVATE PEER LASTMILE MOBILE UTAT BROWSERT PRIVATE PEER DataSet Retrieved Summary, page, object, host, and connection-level. Summary, page, object, host, and connection-level. Summary, event, metadata, and trace-level. Summary, page, object, host, and connection-level. Summary, page, object, host, and connection-level. Summary, page, object, host, connection, and mobileext-level. Summary, page, and object level only. Summary, page, and object level only. Summary, page, and object level only. Summary, page, and object level only. Summary, page, object, and mobileext-level. Summary and page-level only. Summary and page-level only. Summary and page-level only. 18

19 Chapter 2 Data Feed Web Services sdatadesignator SUMMARY TIMEGROUP smonitorclassdesignator LASTMILE MOBILE UTAT BROWSERT STREAM PRIVATE PEER LASTMILE MOBILE UTAT BROWSERT DataSet Retrieved Summary and page-level only. Summary, page, and mobileext-level. Summary-level only. Summary-level only. Summary-level only. Summary-level only. Summary-level only. Summary-level only. Up to 24 hours of aggregated data. Up to 24 hours of aggregated data. Validation Criteria In the following table are descriptions of the validation criteria for the OpenDataFeed request. Validation Criteria Username Password MonitorIdSet SiteIdSet StartTime EndTime MonitorClassDesignator DataDesignator OrderDesignator Data Volume Frequency Concurrency The supplied username is valid for the account. The supplied password is valid for the account. The set of Monitor IDs is valid for the account. The set of Site IDs is valid for the account. The time window start boundary is valid. The time window end boundary is valid. The smonitorclassdesignator value is valid. The sdatadesignator value is valid. The sorderdesignator value is valid. The volume of data does not exceed the account constraints The request frequency does not exceed the account constraints The request concurrency does not exceed the account constraints Response Example <soap:envelope xmlns:soap=" xmlns:xsi=" xmlns:xsd=" <soap:body> <OpenDataFeedResponse xmlns=" <GpnOpenUtaDataFeedResponse> <Status> <estatus>status_success</estatus> <serrormessage/> </Status> <GPNGlobalConstraints MaxDataRequestsPerHourPerSession="60" MaxTotalSessions="4096"/> 19

20 Chapter 2 Data Feed Web Services <GPNAccountConstraints MaxDataRecordsPerRequest="100" MaxConcurrentSessions="100" MaxConcurrentRequests="1" MaxRequestIntervalBeforeExpirationInMinutes="15"/> <CurrentTime> :49:54</CurrentTime> <SessionToken>39eb9e7d-c0cb-4e62-a806-46cd112e1d8c</SessionToken> <AcceptedMonitors> <mid>331608</mid> </AcceptedMonitors> <AcceptedSites> <sid>5</sid> <sid>6</sid> <sid>316</sid> <sid>777</sid> <sid>834</sid> <sid>835</sid> <sid>836</sid> <sid>837</sid> <sid>843</sid> <sid>844</sid> <sid>845</sid> <sid>846</sid> <sid>847</sid> <sid>848</sid> <sid>849</sid> <sid>850</sid> <sid>851</sid> <sid>852</sid> <sid>855</sid> <sid>856</sid> <sid>857</sid> <sid>858</sid> <sid>860</sid> <sid>861</sid> <sid>862</sid> <sid>864</sid> <sid>865</sid> <sid>866</sid> <sid>867</sid> <sid>868</sid> <sid>871</sid> <sid>872</sid> <sid>873</sid> <sid>880</sid> <sid>881</sid> <sid>884</sid> <sid>885</sid> <sid>886</sid> <sid>887</sid> <sid>888</sid> <sid>889</sid> <sid>9100</sid> </AcceptedSites> </GpnOpenUtaDataFeedResponse> </OpenDataFeedResponse> </soap:body> </soap:envelope> OpenDataFeed Response The OpenDataFeed web service method returns an ML message containing the following: The status of the operation. The set of global operational constraints. The set of account specific operational constraints. The session Identifier. The set of validated monitor identifiers. The set of validated site identifiers. Successful Response Message Example <?xml version="1.0" encoding="utf-8"?> <GpnOpenUtaDataFeedResponse xmlns:xsd=" xmlns:xsi=" xmlns=" <Status> <estatus>status_success</estatus> <serrormessage /> 20

21 Chapter 2 Data Feed Web Services </Status> <GPNGlobalConstraints MaxDataRequestsPerHourPerSession="60" MaxTotalSessions="50" /> <GPNAccountConstraints MaxDataRecordsPerRequest="1000" MaxConcurrentSessions="1" MaxConcurrentRequests="1" MaxRequestIntervalBeforeExpirationInMinutes="15" /> <CurrentTime> :49:54</CurrentTime> <SessionToken>c59754b7-3ed a0e8-c352daa0b8a1</SessionToken> <AcceptedMonitors> <mid> </mid> </AcceptedMonitors> <AcceptedSites> <sid>101</sid> </AcceptedSites> </GpnOpenUtaDataFeedResponse> Unsuccessful Response Message Example <?xml version="1.0" encoding="utf-8"?> <GpnOpenUtaDataFeedResponse xmlns:xsd=" xmlns:xsi=" xmlns=" <Status> <estatus>status_failed</estatus> <serrormessage>invalid ORDER DESIGNATOR SPECIFIED. MUST BE (TIME MONITOR SITE)</sErrorMessage> </Status> </GpnOpenUtaDataFeedResponse> The following table summarizes the elements and attributes in the ML response returned by this web service. Refer to the WSDL for the complete definition of this ML response. Container Element OpenDataFeedResponse Status GPNGlobalConstraints Data Element/Attribute estatus serrormessage MaxDataRequestsPerHourPerSession MaxTotalSessions Either STATUS_SUCCESS or STATUS_FAILED. Contains an error message if STATUS_FAILED. The maximum number of data requests that can be made per hour within a given session is 60. The maximum number of sessions that can be handled by the service is 32. GPNAccountConstraints MaxDataRecordsPerRequest MaxConcurrentSessions MaxConcurrentRequests The maximum number of data records that can be obtained per GetResponseData request is The maximum number of concurrent sessions that will be serviced is 1. The maximum number of concurrent requests that can be made within the context of a given session is 1. MaxRequestIntervalBeforeExpirationInMinutes The maximum amount of time that can elapse between calls to "GetResponseData" before 21

22 Chapter 2 Data Feed Web Services Container Element Data Element/Attribute CurrentTime SessionToken AcceptedMonitors AcceptedSites a session may be expired by the system is 15 minutes. Contains the time the request was received in GMT. The ssession Identifier that is used in subsequent calls to GetResponseData and CloseDataFeed. Contains a list of the Compuware APMaaS platform monitor identifiers that have been validated by the system for a specified account. Contains a list of the Compuware APMaaS platform site identifiers that have been validated by the system for a specified account. OpenDataFeed2 Request This represents an alternate version of an OpenDataFeed request, asking for the last N samples relative to the current time. Web method for initializing the UTA data feed session based on a number of user-defined criteria. A data feed session always exports a homogeneous dataset based on the specified smonitorclassdesignator and the sdatadesignator tags provides when the session is initialized. The request message includes parameters and validation criteria, as described in the following tables. Parameters susername spassword imonitoridset The account username. The account password Requested set of Compuware APMaaS platform Monitor/Test reference Identifiers. This set will be cross-referenced against the smonitorclassdesignator and only requested monitors meeting the specified class criteria will be returned. NOTE Use the Account Management API to retrieve the Compuware APMaaS platform monitor identifiers available to your account. isiteidset Requested set of Compuware APMaaS platform Site reference Identifiers. Empty set denotes all sites. 22

23 Chapter 2 Data Feed Web Services Parameters NOTE Use the Account Management API to retrieve the Compuware APMaaS platform monitor identifiers available to your account. smonitorclassdesignator sdatadesignator slastn Specifies the type of data to be exported in the dataset based on the common class of tests. Supported values are as follows: UTAT Data sets based on transaction tests running on UTA agents BROWSERT Data sets based on transaction tests running on browser agents. Note that this is a shared schema with UTA. STREAM Data sets based on streaming test running on stream agents. PRIVATEER Data sets based on tests running on Private Peer Network LASTMILE Data sets based on tests running on Last Mile Network MOBILE Data sets based on tests running on Mobile Network Specifies the levels of data in the dataset returned to the client for the type of data specified with the smonitorclassdesignator parameter. Supported values are as follows: ALL Returns all levels of data available. OBJECT Returns SUMMARY, PAGE, and OBJECT level data. Mobile datasets will also include MOBILEET level data. PAGE Returns SUMMARY and PAGE level data. Mobile datasets will also include MOBILEET level data. SUMMARY Returns SUMMARY level data. Mobile datasets will also include MOBILEET level data. TIMEGROUP Returns aggregation data over specified time window, up to 24 hours. (see following parameter descriptions). Indicates a window based on the last N test samples relative to the current time. A value of 1 will spec a data export session which always returns the last test acquired relative to the current time. This parameter can contain any value up to cap enforced by the MaxDataRecordsPerRequest constraint. Any values specified for this parameter which exceed this constraint will be set to the constraint. Ignored when sdatadesignator is TIMEGROUP. 23

24 Chapter 2 Data Feed Web Services Parameters sstarttime sendtime sorderdesignator Specifies the starting time boundary for the dataset. The format is: YYYY-MM-DD HH:MM:SS Specifies the ending time boundary for the dataset. The format is: YYYY-MM-DD HH:MM:SS Specifies how the dataset will be ordered. Supported values are as follows: TIME Orders data by time. SITE Orders data by site. MONITOR Orders data by monitor class Validation Criteria Validation Criteria Username Password MonitorIdSet SiteIdSet StartTime EndTime MonitorClassDesignator DataDesignator OrderDesignator Data Volume Frequency Concurrency The supplied username is valid for the account. The supplied password is valid for the account. The set of Monitor IDs is valid for the account. The set of Site IDs is valid for the account. The time window start boundary is valid. The time window end boundary is valid. The smonitorclassdesignator value is valid. The sdatadesignator value is valid. The sorderdesignator value is valid. The volume of data does not exceed account constraints The request frequency does not exceed account constraints The request concurrency does not exceed account constraints OpenDataFeed3 Request This represents an alternate version of an OpenDataFeed request using an ARRIVAL versus TEST TIME Filter Interpretation. Web method for initializing the UTA data feed session based on a number of user-defined criteria. A data feed session always exports a homogeneous dataset based on the specified smonitorclassdesignator and the sdatadesignator tags provides when the session is initialized. 24

25 Chapter 2 Data Feed Web Services Parameters susername spassword imonitoridset The account username. The account password Requested set of the Compuware APMaaS platform Monitor/Test reference Identifiers. This set will be cross-referenced against the smonitorclassdesignator and only requested monitors meeting the specified class criteria will be returned. NOTE Use the Account Management API to retrieve the Compuware APMaaS platform monitor identifiers available to your account. isiteidset Requested set of the Compuware APMaaS platform Site reference Identifiers. Empty set denotes all sites. NOTE Use the Account Management API to retrieve the Compuware APMaaS platform monitor identifiers available to your account. smonitorclassdesignator sdatadesignator Specifies the type of data to be exported in the dataset based on the common class of tests. Supported values are as follows: UTAT Data sets based on transaction tests running on UTA agents BROWSERT Data sets based on transaction tests running on browser agents. Note that this is a shared schema with UTA. STREAM Data sets based on streaming test running on stream agents. PRIVATEER Data sets based on tests running on Private Peer Network LASTMILE Data sets based on tests running on Last Mile Network MOBILE Data sets based on tests running on Mobile Network Specifies the levels of data in the dataset returned to the client for the type of data specified with the smonitorclassdesignator parameter. Supported values are as follows: ALL Returns all levels of data available. OBJECT Returns SUMMARY, PAGE, and OBJECT level data. Mobile datasets will also include MOBILEET level data. PAGE Returns SUMMARY and PAGE level data. Mobile datasets will also include MOBILEET level data. 25

26 Chapter 2 Data Feed Web Services Parameters SUMMARY Returns SUMMARY level data. Mobile datasets will also include MOBILEET level data. TIMEGROUP Returns aggregation data over specified time window, up to 24 hours. (see following parameter descriptions). slastn sstarttime sendtime sorderdesignator stimedesignator Indicates a window based on the last N test samples relative to the current time. A value of 1 will spec a data export session which always returns the last test acquired relative to the current time. This parameter can contain any value up to cap enforced by the MaxDataRecordsPerRequest constraint. Any values specified for this parameter which exceed this constraint will be set to the constraint. Ignored when sdatadesignator is TIMEGROUP. Specifies the starting time boundary for the dataset. The format is: YYYY-MM-DD HH:MM:SS Specifies the ending time boundary for the dataset. The format is: YYYY-MM-DD HH:MM:SS Specifies how the dataset will be ordered. Supported values are as follows: TIME Orders data by time. SITE Orders data by site. MONITOR Orders data by monitor class Designation indicating how the time filters and modes are to be applied. Supported values are as follows: TESTTIME_ABSOLUTE Time range filter to be applied relative to the time samples were acquired by remote agents. This is the current default mode of operation for legacy versions of the service. TESTTIME_RELATIVE Time range filter is unused and slastn must be specified. The slastn parameter is interpreted as last N samples relative to the time samples were acquired by remote agents. ARRIVAL_ABSOLUTE Time range filter to be applied relative to the time samples arrived at the central data repositories. This is a new mode of operation. ARRIVAL_RELATIVE Time range filter is unused and slastn must be specified. The slastn parameter is interpreted as last N samples relative to the time samples arrived at the central data repositories. 26

27 Chapter 2 Data Feed Web Services Validation Criteria Validation Criteria Username Password MonitorIdSet SiteIdSet StartTime EndTime MonitorClassDesignator DataDesignator OrderDesignator Time Designator Data Volume Frequency Concurrency The supplied username is valid for the account. The supplied password is valid for the account. The set of Monitor IDs is valid for the account. The set of Site IDs is valid for the account. The time window start boundary is valid. The time window end boundary is valid. The smonitorclassdesignator value is valid. The sdatadesignator value is valid. The sorderdesignator value is valid. The stimedesignator values are valid. The volume of data does not exceed account constraints. The request frequency does not exceed account constraints. The request concurrency does not exceed account constraints. GetResponseData Request This web method returns the next chunk of the dataset for a specified transaction from each site. Range, content, and volume of data are based on constraints setup when the session was opened with one of the OpenDataFeed web methods and the standard system and account level constraints. Parameters ssessiontoken Unique Identifier issued by the initial OpenDataFeed call for the session. Request Example <soapenv:envelope xmlns:soapenv=" xmlns:web=" <soapenv:header/> <soapenv:body> <web:getresponsedata> <!--Optional:--> <web:ssessiontoken>39eb9e7d-c0cb-4e62-a806-46cd112e1d8c</web:ssessiontoken> </web:getresponsedata> </soapenv:body> </soapenv:envelope> 27

28 Chapter 2 Data Feed Web Services Validation Criteria Validation Criteria Session Token Data Volume Frequency Concurrency The ssessiontoken value is valid. The volume of data does not exceed account constraints. The request frequency does not exceed account constraints. The request concurrency does not exceed account constraints. GetResponseData Response This Web method returns an ML message containing: Status of operation Number of data records returned ML subdocument containing Type of data returned APMaaS Synthetic Monitoring Performance Dataset Container Element GetResponseDataResponse Status GpnResponseData Data Element/Attribute estatus serrormessage NumRecords Availability mldocument CurrentTime MonitorDesignator Contains STATUS_SUCCESS or STATUS_FAILED Contains an error message if STATUS_FAILED Contains the number of records exported in the current response The availability of the monitors in the current response. Contains the performance data subdocument (see SD) Contains the time the request was received in GMT. Indicates the "type" of performance data exported in the current request. This reflects the MonitorClassDesignatorvalue specified in the initialization call to the OpenDataFeed service: UTAT BROWSERT STREAM PRIVATE PEER 28

29 Chapter 2 Data Feed Web Services Container Element Data Element/Attribute Test Streamtest LASTMILE MOBILE For more information, see OpenDataFeed Request [p. 16]. Top level container for test information Refer to the SD for further details. For more information, see Data Export Web Service Response SD [p. 41]. Top level container for streaming test information. Refer to the SD for further details. For more information, see Data Export Web Service Response SD [p. 41]. Sample GetResponseData for Backbone Data For backbone data, a successful call to the GetResponseData web service method returns an ML message similar the following: Sample of a Successful Response Message <soap:envelope xmlns:soap=" xmlns:xsi=" xmlns:xsd=" <soap:body> <GetResponseDataResponse xmlns=" <GpnResponseData> <Status> <estatus>status_success</estatus> <serrormessage/> </Status> <NumRecords>2</NumRecords> <CurrentTime> :05:43</CurrentTime> <mldocument> <GpnResponseData xmlns=""> <MonitorDesignator MonitorClassDesignator="UTAT"/> <TTEST mid="331606" sid="884" ttime=" :05:30.447" sname="tpnts10 - Boston, MA - Savvis" rtime="5853" tpt="2" tps="1" tpf="1" tot="27" tos="27" tof="0" nbyte="478513" browsertype="ff35" sipv6ready="0" testipv6pref="ipv6_preferred"> <PAGE pseq="0" rtime="2001" nobj="15" rc200="15" rc300="2" rc400="0" rc500="0" rcnet="0" rcint="0" nbyte="403817" nhost="7" nconn="9" tostat="0" usstat="0" blstat="0" rtobjseq="2" dnssum="107" ndns="7" connsum="536" nconn1="13" sslsum="383" nssl="8" fbsum="896" nfb="17" contsum="593" ncont="17" ptime="1060"> <OBJECT oseq="0" hid="0" connid="0" rc="301" ctype="text/html; charset=utf-8" rtime="62" nbyte="219" fbstart=" :05:31.587" fbtime="62" contstart=" :05:31.647" conttime="0" uhost=" upage="/" redirobjid="1" spdy="0"/> <OBJECT oseq="1" hid="1" connid="1" rc="302" ctype="text/html; charset=utf-8" rtime="51" nbyte="231" fbstart=" :05:31.683" fbtime="51" contstart=" :05:31.737" conttime="0" uhost=" upage="/" redirobjid="2" spdy="0"/> <OBJECT oseq="2" hid="1" connid="2" rc="200" ctype="text/html; charset=utf-8" rtime="193" nbyte="39776" fbstart=" :05:32.043" fbtime="104" contstart=" :05:32.147" conttime="89" uhost=" upage="/" uparam="?gws_rd=ssl" spdy="0"/> <OBJECT oseq="3" hid="2" connid="3" rc="200" ctype="application/ocsp-response" rtime="64" nbyte="463" fbstart=" :05:31.863" fbtime="64" contstart=" :05:31.927" conttime="0" uhost=" upage="/ocsp" spdy="0"/> <OBJECT oseq="4" hid="3" connid="4" rc="200" ctype="application/ocsp-response" rtime="34" nbyte="1454" fbstart=" :05:32.003" fbtime="34" contstart=" :05:32.037" conttime="0" uhost=" upage="/" spdy="0"/> <OBJECT oseq="5" hid="1" connid="2" rc="200" ctype="image/jpeg" rtime="73" nbyte="14022" fbstart=" :05:32.340" fbtime="44" contstart=" :05:32.387" conttime="29" uhost=" upage="/images/srpr/logo11w.png" spdy="0"/> 29

30 Chapter 2 Data Feed Web Services <OBJECT oseq="6" hid="4" connid="5" rc="200" ctype="image/jpeg" rtime="142" nbyte="53898" fbstart=" :05:32.537" fbtime="47" contstart=" :05:32.583" conttime="95" uhost=" upage="/gb/images/v1_2e png" spdy="0"/> <OBJECT oseq="7" hid="1" connid="6" rc="200" ctype="image/png" rtime="131" nbyte="127552" fbstart=" :05:32.407" fbtime="34" contstart=" :05:32.440" conttime="97" uhost=" upage="/xjs/_/js/k=xjs.s.en_us.w-mwpchq9os.o/rs=aitrshenadbs4va" spdy="0"/> <OBJECT oseq="8" hid="2" connid="3" rc="200" ctype="application/ocsp-response" rtime="64" nbyte="463" fbstart=" :05:32.440" fbtime="64" contstart=" :05:32.503" conttime="0" uhost=" upage="/ocsp" spdy="0"/> <OBJECT oseq="9" hid="2" connid="3" rc="200" ctype="application/ocsp-response" rtime="65" nbyte="463" fbstart=" :05:32.503" fbtime="65" contstart=" :05:32.570" conttime="0" uhost=" upage="/ocsp" spdy="0"/> <OBJECT oseq="10" hid="5" connid="9" rc="200" ctype="image/png" rtime="143" nbyte="51781" fbstart=" :05:32.793" fbtime="48" contstart=" :05:32.843" conttime="95" uhost=" upage="/og/_/js/k=og.og.en_us.ss4npnikgpg.o/rs=aitrs1si444-phs352npq" spdy="0"/> <OBJECT oseq="11" hid="1" connid="6" rc="200" ctype="image/png" rtime="82" nbyte="11614" fbstart=" :05:32.793" fbtime="81" contstart=" :05:32.877" conttime="1" uhost=" upage="/extern_chrome/59debdbe0c85d78b.js" uparam="?bav=on.2,or.r_qf." spdy="0"/> <OBJECT oseq="12" hid="1" connid="2" rc="200" ctype="image/jpeg" rtime="31" nbyte="387" fbstart=" :05:32.793" fbtime="30" contstart=" :05:32.823" conttime="1" uhost=" upage="/textinputassistant/tia.png" spdy="0"/> <OBJECT oseq="13" hid="1" connid="2" rc="200" ctype="image/png" rtime="118" nbyte="37046" fbstart=" :05:32.827" fbtime="30" contstart=" :05:32.857" conttime="88" uhost=" upage="/xjs/_/js/k=xjs.s.en_us.w-mwpchq9os.o/rs=aitn5lhenadbs4va" spdy="0"/> <OBJECT oseq="14" hid="6" connid="12" rc="200" ctype="image/png" rtime="145" nbyte="48234" fbstart=" :05:33.207" fbtime="48" contstart=" :05:33.257" conttime="97" uhost=" upage="/_/scs/abc-static/_/js/rs=aitrstpppu6cr-g/cb=gapi.loaded_0" spdy="0"/> <OBJECT oseq="15" hid="1" connid="6" rc="200" ctype="image/jpeg" rtime="43" nbyte="16214" fbstart=" :05:33.430" fbtime="42" contstart=" :05:33.470" conttime="1" uhost=" upage="/images/nav_logo195.png" spdy="0"/> <OBJECT oseq="16" hid="1" connid="2" rc="204" ctype="text/html; charset=utf-8" rtime="48" nbyte="0" fbstart=" :05:33.430" fbtime="48" contstart=" :05:33.477" conttime="0" uhost=" upage="/gen_204" uparam="?v=3&s=webhp&action=xjsls.96,prt.96" spdy="0"/> </PAGE> <PAGE pseq="1" rtime="3852" nobj="12" rc200="12" rc300="0" rc400="0" rc500="0" rcnet="0" rcint="0" nbyte="74696" nhost="1" nconn="2" tostat="0" usstat="1" blstat="0" rtobjseq="17" dnssum="0" ndns="0" connsum="0" nconn1="0" sslsum="0" nssl="0" fbsum="676" nfb="12" contsum="290" ncont="12" ptime="1029"> <OBJECT oseq="17" hid="1" connid="6" rc="200" ctype="application/json" rtime="71" nbyte="653" fbstart=" :05:34.410" fbtime="70" contstart=" :05:34.480" conttime="1" uhost=" upage="/s" uparam="?gs_rn=52&gs_ri=psy-ab&cp=1&psi=tlgdvpobygsz7igqbq " spdy="0"> <OBJECT oseq="18" hid="1" connid="6" rc="204" ctype="text/html; charset=utf-8" rtime="47" nbyte="0" fbstart=" :05:34.517" fbtime="47" contstart=" :05:34.563" conttime="0" uhost=" upage="/gen_204" uparam="?atyp=i&ct=1&cad=1&rsm=6&ei=tlgdvp2jc&zx=14504" spdy="0"> <OBJECT oseq="19" hid="1" connid="6" rc="200" ctype="application/json" rtime="69" nbyte="715" fbstart=" :05:34.947" fbtime="67" contstart=" :05:35.013" conttime="2" uhost=" upage="/s" uparam="?gs_rn=52&gs_ri=psy-ab&psi=tlgbygsz7igqbq " spdy="0"> <OBJECT oseq="20" hid="1" connid="6" rc="200" ctype="application/json" rtime="65" nbyte="742" fbstart=" :05:35.443" fbtime="64" contstart=" :05:35.507" conttime="1" uhost=" upage="/s" uparam="?gs_rn=52&gs_ri=psy-ab&psi=tlgdvpsz7igqbq " spdy="0"> <OBJECT oseq="21" hid="1" connid="6" rc="200" ctype="application/json" rtime="90" nbyte="533" fbstart=" :05:35.983" fbtime="66" contstart=" :05:36.050" conttime="24" uhost=" upage="/s" uparam="?gs_rn=52&psi=tlgdvp2jcjobygsz7igqbq " spdy="0"> <OBJECT oseq="22" hid="1" connid="6" rc="200" ctype="application/json" rtime="69" nbyte="602" fbstart=" :05:36.113" fbtime="67" contstart=" :05:36.180" conttime="2" uhost=" upage="/s" uparam="?gs_rn=52&gs_ri=psy-ab&psi=p2jcjobygsz7igqbq " spdy="0"> <OBJECT oseq="23" hid="1" connid="6" rc="200" ctype="application/json" rtime="310" nbyte="39430" fbstart=" :05:36.507" fbtime="56" contstart=" :05:36.563" conttime="254" uhost=" upage="/s" uparam="?gs_rn=52&gs_ri=psy-ab&psi=tlgdvp2jcjoby7igqbq " spdy="0"> <OBJECT oseq="24" hid="1" connid="2" rc="200" ctype="application/json" rtime="62" nbyte="772" fbstart=" :05:36.597" fbtime="59" contstart=" :05:36.657" conttime="3" uhost=" upage="/s" uparam="?gs_rn=52&gs_ri=psy-ab&psi=tlgdobygsz7igqbq " spdy="0"> <OBJECT oseq="25" hid="1" connid="6" rc="200" ctype="image/png" rtime="31" nbyte="30710" fbstart=" :05:37.173" fbtime="30" contstart=" :05:37.203" conttime="1" uhost=" upage="/xjs/_/js/k=xjs.s.en_us.w-mwpchq9os.o/rs=aitr6r4axoebn5lhenadbs4va" spdy="0"> <OBJECT oseq="26" hid="1" connid="2" rc="204" ctype="text/html; charset=utf-8" rtime="46" nbyte="0" fbstart=" :05:37.180" fbtime="46" contstart=" :05:37.227" conttime="0" uhost=" upage="/gen_204" uparam="?v=3&s=web&rt=prt.235" spdy="0"> <OBJECT oseq="27" hid="1" connid="6" rc="200" ctype="application/json" rtime="60" nbyte="539" fbstart=" :05:37.677" fbtime="58" contstart=" :05:37.733" conttime="2" uhost=" upage="/s" 30

31 Chapter 2 Data Feed Web Services uparam="?gs_rn=52&gs_ri=psy-ab&psi=tlgdvp2jcjobygsz7igqbq " spdy="0"> <OBJECT oseq="28" hid="1" connid="6" rc="204" ctype="text/html; charset=utf-8" rtime="46" nbyte="0" fbstart=" :05:38.217" fbtime="46" contstart=" :05:38.263" conttime="0" uhost=" upage="/gen_204" uparam="?atyp=i&ct=1&cad=1&q=compuware&oq=compuware&gs_l=hp.10" spdy="0"/> </PAGE> <HOST hid="0" page="0" dnsstart=" :05:31.477" dnstime="61" nbyte="219" nerr="0" nobj="0" nconn="1" ip="2607:f8b0:4004:0802:0000:0000:0000:1002" isipv6="1"> <CONN connid="0" page="0" rtime="110" connstart=" :05:31.537" conntime="48" nbyte="219" nerr="0" nobj="0"/> </HOST> <HOST hid="1" page="0" dnsstart=" :05:31.653" dnstime="2" nbyte="321538" nerr="0" nobj="20" nconn="4" ip="2607:f8b0:4009:0803:0000:0000:0000:1014" isipv6="1"> <CONN connid="1" page="0" rtime="81" connstart=" :05:31.653" conntime="30" nbyte="231" nerr="0" nobj="0"/> <CONN connid="2" page="0" rtime="5484" connstart=" :05:31.740" conntime="30" sslstart=" :05:31.770" ssltime="40" nbyte="92003" nerr="0" nobj="7"/> <CONN connid="6" page="0" rtime="5919" connstart=" :05:32.343" conntime="29" sslstart=" :05:32.373" ssltime="31" nbyte="229304" nerr="0" nobj="13"/> <CONN connid="10" page="0" rtime="60" connstart=" :05:32.797" conntime="29" sslstart=" :05:32.827" ssltime="30" nbyte="0" nerr="0" nobj="0"/> </HOST> <HOST hid="2" page="0" dnsstart=" :05:31.810" dnstime="2" nbyte="1389" nerr="0" nobj="3" nconn="2" ip="2607:f8b0:4004:0802:0000:0000:0000:1003" isipv6="1"> <CONN connid="3" page="0" rtime="756" connstart=" :05:31.813" conntime="48" nbyte="1389" nerr="0" nobj="3"/> <CONN connid="8" page="0" rtime="56" connstart=" :05:32.480" conntime="56" nbyte="0" nerr="0" nobj="0"/> </HOST> <HOST hid="3" page="0" dnsstart=" :05:31.937" dnstime="39" nbyte="1454" nerr="0" nobj="1" nconn="1" ip=" " isipv6="0"> <CONN connid="4" page="0" rtime="63" connstart=" :05:31.973" conntime="29" nbyte="1454" nerr="0" nobj="1"/> </HOST> <HOST hid="4" page="0" dnsstart=" :05:32.333" dnstime="1" nbyte="53898" nerr="0" nobj="1" nconn="2" ip="2607:f8b0:4004:0803:0000:0000:0000:1017" isipv6="1"> <CONN connid="5" page="0" rtime="343" connstart=" :05:32.333" conntime="47" sslstart=" :05:32.380" ssltime="58" nbyte="53898" nerr="0" nobj="1"/> <CONN connid="7" page="0" rtime="106" connstart=" :05:32.373" conntime="48" sslstart=" :05:32.423" ssltime="58" nbyte="0" nerr="0" nobj="0"/> </HOST> <HOST hid="5" page="0" dnsstart=" :05:32.537" dnstime="1" nbyte="51781" nerr="0" nobj="1" nconn="2" ip="2607:f8b0:4004:0803:0000:0000:0000:1018" isipv6="1"> <CONN connid="9" page="0" rtime="399" connstart=" :05:32.537" conntime="47" sslstart=" :05:32.587" ssltime="59" nbyte="51781" nerr="0" nobj="1"/> <CONN connid="11" page="0" rtime="96" connstart=" :05:32.797" conntime="47" sslstart=" :05:32.847" ssltime="48" nbyte="0" nerr="0" nobj="0"/> </HOST> <HOST hid="6" page="0" dnsstart=" :05:33.050" dnstime="1" nbyte="48234" nerr="0" nobj="1" nconn="1" ip="2607:f8b0:4004:0802:0000:0000:0000:1002" isipv6="1"> <CONN connid="12" page="0" rtime="301" connstart=" :05:33.053" conntime="48" sslstart=" :05:33.100" ssltime="59" nbyte="48234" nerr="0" nobj="1"/> </HOST> <W3CPAGE rootstepseq="0" w3cseq="0" navstart=" :05:31.447" fchstart="292" dlkstart="292" dlkend="292" constart="292" conend="292" reqstart="598" rspstart="702" rspend="791" domld="709" domint="841" dcldstart="862" dcldend="885" domcmpl="1964" ldstart="1964" ldend="1967" fchtime="0" dnstime="0" contime="0" reqtime="104" rsptime="89"/> </TTEST> <TTEST mid="331606" sid="887" ttime=" :11:42.720" sname="tpnts11 - Boston, MA - Savvis" rtime="6237" tpt="2" tps="1" tpf="1" tot="27" tos="27" tof="0" nbyte="480094" browsertype="ff35" sipv6ready="1" testipv6pref="ipv6_preferred"> <PAGE pseq="0" rtime="2381" nobj="15" rc200="15" rc300="2" rc400="0" rc500="0" rcnet="0" rcint="0" nbyte="404890" nhost="7" nconn="9" tostat="0" usstat="0" blstat="0" rtobjseq="2" dnssum="90" ndns="7" connsum="668" nconn1="13" sslsum="452" nssl="8" fbsum="1050" nfb="17" contsum="1355" ncont="17" ptime="951"> <OBJECT oseq="0" hid="0" connid="0" rc="301" rtime="62" nbyte="219" fbstart=" :11:43.313" fbtime="62" contstart=" :11:43.377" conttime="0" uhost=" upage="/" redirobjid="1" spdy="0"/> <OBJECT oseq="1" hid="1" connid="1" rc="302" rtime="50" nbyte="231" fbstart=" :11:43.413" fbtime="50" contstart=" :11:43.463" conttime="0" uhost=" upage="/" redirobjid="2" spdy="0"/> <OBJECT oseq="2" hid="1" connid="2" rc="200" rtime="182" nbyte="40954" fbstart=" :11:43.880" fbtime="110" contstart=" :11:43.990" conttime="72" uhost=" upage="/" uparam="?gws_rd=ssl" spdy="0"/> <OBJECT oseq="3" hid="2" connid="3" rc="200" rtime="68" nbyte="463" fbstart=" :11:43.597" fbtime="68" contstart=" :11:43.667" conttime="0" uhost=" upage="/ocsp" spdy="0"/> <OBJECT oseq="4" hid="3" connid="4" rc="200" rtime="87" nbyte="1454" fbstart=" :11:43.790" fbtime="87" contstart=" :11:43.877" conttime="0" uhost=" upage="/" spdy="0"/> <OBJECT oseq="5" hid="1" connid="2" rc="200" rtime="55" nbyte="14022" fbstart=" :11:44.200" fbtime="54" contstart=" :11:44.253" conttime="1" uhost=" upage="/images/srpr/logo11w.png" spdy="0"/> <OBJECT oseq="6" hid="4" connid="5" rc="200" rtime="234" nbyte="53898" fbstart=" :11:44.400" fbtime="56" contstart=" :11:44.457" conttime="178" uhost=" upage="/gb/images/v1_2e png" spdy="0"/> <OBJECT oseq="7" hid="1" connid="6" rc="200" rtime="151" nbyte="127552" fbstart=" :11:44.283" fbtime="33" contstart=" :11:44.317" conttime="118" uhost=" 31