APMaaS Synthetic Monitoring for Web & Mobile ... - … Synthetic Monitoring for Web & Mobile ......

APMaaS Synthetic Monitoring for Web &MobileData Feed API Reference

October 2013

http://www.compuware.com/

Please direct questions about APMaaS Synthetic Monitoring or comments on this document to:

APM Customer SupportFrontLine Support Login Page:

http://go.compuware.com

Copyright © 2013 Compuware Corporation. All rights reserved. Unpublished rights reserved under the Copyright Laws of theUnited States.

U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth inCompuware Corporation license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.Compuware Corporation.

This product contains confidential information and trade secrets of Compuware Corporation. Disclosure is prohibited withoutthe prior express written permission of Compuware Corporation. Use of this product is subject to the terms and conditions of theuser'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, modifiedor changed without the express written consent of Compuware Corporation. Compuware Corporation may change the contentspecified herein at any time, with or without notice. All current Compuware Corporation product documentation can be found athttp://go.compuware.com.

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 19, 2013, 8:44



Contents

5Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Data Feed API Features and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Customer Support Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9Chapter 1 ∙ Data Feed Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Which Data Feeds are Available? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10Which Data Feed do I Need? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11How Do I Get the Data Feed I Need? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Does the Data Feed Provide the Data I Need? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15Chapter 2 ∙ Data Feed Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15DataExport Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Access to the Data Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Data Services API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16OpenDataFeed Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16OpenDataFeed Request Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20OpenDataFeed Response Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20OpenDataFeed Response Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21OpenDataFeed2 Request Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24OpenDataFeed3 Request Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27GetResponseData Request Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27GetResponseData Response Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Sample GetResponseData Streaming Response Message . . . . . . . . . . . . . . . . . . . .29CloseDataFeed Request Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29CloseDataFeed Response Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29GetErrorCodes Request Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29GetErrorCodes Response Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Data Service Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31Chapter 3 ∙ FTP Data Feeds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Access FTP Data Feed Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31FTP Data Feed File Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3APMaaS Synthetic Monitoring for Web & Mobile Data Feed API Reference

Contents

32T File Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Monitor File Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Site File Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34LM File Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34TO File Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35LMO File Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

37Appendix A ∙ Data Export Web Service 4.0 Response XSD . . . . . . . . . . . . . . . . . .

47Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APMaaS Synthetic Monitoring for Web & Mobile Data Feed API Reference4

Contents

I N T R O D U C T I O N

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 canbe used to access the data feed performance data.

Data Feed API Features and NotesThe Data Feed API supports a broad range of available APMaaS Synthetic Monitoring datasets.The API includes support for discrimination between legacy UTA test measurements and newerBROWSER based test measurements through the inclusion of a browser type attribute whichis 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 whichhave been reclassified as “data cuts” in the system. Data cut requests are supported across allavailable response models.Data cut information can be elicited for any series of cut events occurring within the last fourdays.The API supports a request mode to cause the data service to reinterpret the requested timerange as a platform arrival time rather than the current interpretation as test acquisition time.This allows clients greater flexibility for use cases which must take into account latencies withinthe Compuware APMaaS testing 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 theearlier 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 nameTEST was specialized to better inform the response model being used:


TXTEST

Indicates a Transaction Test Response element emanating from Backbone, Last Mile,Private Peer, or Mobile Systems

TXTIMEGROUP

Indicates a Transaction Test Time Group Response element emanating fromBackbone-based transactions.

STREAMTEST

Indicates a Stream Test Response element emanating from Backbone Streaming SystemDATACUT

Indicates a Data Cut Sample element emanating from Backbone, Last Mile, Private Peeror Mobile Systems

MESSAGE

Indicates a general purposes messaging element

Documentation ConventionsThe following font conventions are used throughout documentation:

IndicatesThis font

Terms, commands, and references to names of screen controls and userinterface elements.

Bold

Emphasized text, inline citations, titles of external books or articles.Citation

Links to Internet resources and linked references to titles in Compuwaredocumentation.

DocumentationConventions [p. 6]

Cited contents of text files, inline examples of code, command line inputs orsystem outputs. Also file and path names.

Fixed width

User input in console commands.Fixed width bold

Place holders for values of strings, for example as in the command:Fixed width italic

cd directory_name

Menu items.Menu ➤ Item

Text screen shots.Screen

Blocks of code or fragments of text files.Code block

Customer Support Information

FrontLine Support Website

You can access information for Compuware products via our FrontLine support site. You canreview frequently asked questions, read or download documentation, access product fixes, ore-mail your questions or comments. The first time you access FrontLine, you are required to


Introduction

register and obtain a password. Registration is free. To access FrontLine, log in tohttp://go.compuware.com. Select your product from the Product Support dropdown list.

Contacting Customer Support

Phone• USA and Canada: 1-800-538-7822 or 1-313-227-5444.

• All other countries: Contact your local Compuware office. Contact information isavailable at http://go.compuware.com.

WebYou can report issues via the Report and Track Calls tab on the FrontLine home page.

NOTEPlease report all high-priority issues by phone.

APM CommunityYou can find product documentation, forums with product experts, product fixes and moreinformation at the Compuware APM Community. You must register and login to accessthe Community.

[email protected]

MailCustomer SupportCompuware CorporationOne Campus MartiusDetroit, MI 48226-5099

Corporate Website

To access the Compuware website, go to http://www.compuware.com. The Compuware siteprovides a variety of product and support information.


Introduction



https://apmcommunity.compuware.com/community/display/PUB/Community+Home

mailto:[email protected]

http://www.compuware.com


Introduction

C H A P T E R 1

Data Feed Options

The APMaaS Synthetic Monitoring monitoring tools provide a variety of graphical displaysthat 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 accountdata.Data feeds provide another way for you to access and structure their data. It can be trickydetermining which feed is best for specific requirements. This document first discusses the twoAPMaaS Synthetic Monitoring data feeds (FTP and Web Services) and then provides a numberof 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 wayto 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 Servicesdata 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 SyntheticMonitoring.Customers can create batch programs to download test-level, page-level, and object-level dataand to load that data into data warehouses to supplement business analytics and reporting. Ifyou need support for creating programs to download data, contact APMaaS Synthetic MonitoringProfessional Services.Contact Customer Support to have your account enabled for the APMaaS Synthetic MonitoringWeb Service data feeds.


FTP Data Feed

Use the FTP data feed to obtain large amounts of data at once from the Compuware APMaaSplatform. For users that have dozens of tests and large test volume (for example, service providersand ad networks), FTP is the preferred method for application integration at the customerpremises. Many tests can generate up to a gigabyte of data, and files are created every hour byscheduled scripts. As with Web Services, this amount of data requires planning and managementby technical personnel.Contact Customer Support to set up your FTP account.

Emailed Reports and Alerts

While these are not really data feeds, for many users it is critically important to receive anemailed report that is already aggregated, processed, and summarized. Email reports are sentdirectly to the customer and can be set up in the APMaaS Synthetic Monitoring portals. Similarly,emailed alerts do not require any processing by the user. Their use is described in the onlinehelp.If you need a custom or enhanced report, contact your Account Manager.

XML Data Feed

For users interested in programming or integrating small subsets of certain Last Mile data viaan HTTPS (or HTTP) connection, the XML data feed can be used.

NOTEThe XML 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 oftests and the target application. You may wish to receive an aggregated weekly summary reportof a dozen tests in Microsoft Excel format and Email reports are perfect for this. On the otherhand, if you have a dedicated analytics team and a desire to correlate test measurements with aweb user analytics system, a daily batch pull using a Web Service data feed is the best option.

Data FeedRecommendation

Target Applicationor Format

Number of TestsFunctionAudience

Email ReportExcel, PDF, HTML,CSV

Under 10SLA reportsBusiness


AnyAggregatedBusiness


Under 20Daily Test ResultsBusiness

Email ReportHTMLAnyAggregated forSmart Phones

Technical


Chapter 1 ∙ Data Feed Options

Data FeedRecommendation

Target Applicationor Format

Number of TestsFunctionAudience

Web ServicesAnalytics orDashboards

AnyDaily test resultsTechnical

Web ServicesData WarehouseAnyDaily Batch LoadTechnical

FTP or WebServices

Data WarehouseOver 20Hourly Batch LoadTechnical

Alert EmailEmailAnyReceive AlertsAny

How Do I Get the Data Feed I Need?Once you have determined which data feed you are interested in, there are a number of differentprocesses you need to follow, depending on the feed you want.

How to get itData Feed

Have your Compuware account activated first byCustomer Support to access this feed.

Web Services

Open a ticket with Client Services to get your FTPaccount set up.

FTP

Does the Data Feed Provide the Data I Need?The level of detail you need may determine which data feed to use since not all data feedsinclude all levels of detail. For instance, the Last Mile web service includes most, but not all,types of Backbone data. Use the following matrix to determine which feed is available for youto use.

FTPWeb ServicesData TypeData Source

XSummaryBackbone

XXPage

XObject

XAll

XDatacut

XSummaryStreaming (Backbone)

XXPage

XObject

XAll

XDatacut

XSummaryLast Mile



FTPWeb ServicesData TypeData Source

XXPage

XObject

XAll

XDatacut

XSummaryPrivate Peer

X 1XPage

XObject

XAll

XDatacut

XSummaryMobile

X 1XPage

XObject

XAll

XDatacut

XRawActual

XChart

XGeo

The following table provides more detail on the data feed chart shown above:

DescriptionData Type

Raw data for each test specified over the time frame requested.Summary

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.

Page

Every object in the test is provided, ordered by test id, timestamp, node, pagesequence, and object sequence. NOTE: You cannot aggregate up to test results

Object

due to problems around HTTP concurrent connections, compression, and othertechnical issues.

Includes Summary, Page, Object, plus Host and Connection data.All

Includes Summary plus Event, Trace, and Meta data.All (for Streaming only)

Specific data sets for cut events occurring in the last 4 days.Data Cut

Provides raw Actual dataRaw

Provides aggregated Actual data.Chart

1 No Private Peer extended data attributes



DescriptionData Type

Provides geographically-based Actual data.Geo



C H A P T E R 2

Data Feed Web Services

DataExport ServicesThe following functions are supported by the Data Feed Web Services interface:

ResultsRequest

Initializes client data feed session based on a set ofinput parameters. A token in returned to the clientfor subsequent data pickup.

OpenDataFeed

Initializes client data feed session based on a set ofinput parameters. A token in returned to the client

OpenDataFeed2

for subsequent data pickup. This interface supportsthe specification of a mode of operation usingrelative rather than absolute time windows.

Initializes client data feed session based on a set ofinput parameters. A token in returned to the client

OpenDataFeed3

for subsequent data pickup. This interface supportsthe specification of a mode of operation usingARRIVAL time rather than TEST time windows.

Get next chunk of data for current feed session.GetResponseData

Explicitly expires current feed sessionCloseDataFeed

Exports raw error code definitionsGetErrorCodes

A session is begun with one of the three supported OpenDataFeed requests. After a successfulresponse completes the handshake, a GetResponseData request starts the actual data transfer.A successful GetResponseData response includes an XML file containing the data payload. ACloseDataFeed request starts the termination of the session after the desired data is transferred.With a successful CloseDataFeed response the session is completed.The following diagram illustrates how a typical session proceeds.


GPN Data ServicesClient

OpenDataFeed()Status /

SessionToken

GetResponseData()Status /DataSet

GetResponseData()Status /DataSet

GetResponseData()Status

(No more data)

CloseDataFeed()

Status

Loop

Access to the Data ServiceUse the following URLs to access the production specifications for the DataExport service.

Production Urlhttp://gpn.webservice.gomez.com/DataExportService50/GpnDataExportService.asmx

Production WSDLhttp://gpn.webservice.gomez.com/DataExportService50/GpnDataExportService.asmx?WSDL

Production XSDhttp://gpn.webservice.gomez.com/DataExportService50/xsd/GpnDataExportService50.xsd

Data Services APIThe following section outlines specific interfaces to the Data Services API.

OpenDataFeed SessionThe OpenDataFeed web service method initializes a data feed session based on a number ofuser-defined criteria. A data feed session always exports a homogeneous dataset based on theMonitorClassDesignator and DataDesignator specified when the session is initialized.

OpenDataFeed Request Message DetailsThe request message includes parameters and validation criteria.

DescriptionParameters

APMaaS Synthetic Monitoring account username.sUsername

APMaaS Synthetic Monitoring account passwordsPassword


Chapter 2 ∙ Data Feed Web Services

http://gpn.webservice.gomez.com/DataExportService50/GpnDataExportService.asmx

http://gpn.webservice.gomez.com/DataExportService50/GpnDataExportService.asmx?WSDL

http://gpn.webservice.gomez.com/DataExportService50/xsd/GpnDataExportService50.xsd


Requested set of APMaaS Synthetic Monitoring Monitor/Testreference Identifiers. This set will be cross referenced against the

iMonitorIdSet

MonitorClassDesignator and only requested monitors meetingthe specified class criteria will be returned.

NOTEThe set of APMaaS Synthetic Monitoring monitor identifiers availableto an account may be elicited via use of the Account ManagementService.

Requested set of APMaaS Synthetic Monitoring Site referenceIdentifiers. Empty set denotes all sites.

iSiteIdSet


Specifies the type of data to be exported in the dataset based on thecommon class of tests. Supported values are as follows:

sMonitorClassDesignator

UTATXData sets based on transaction tests running on UTA agents

BROWSERTXData sets based on transaction tests running on browser agents.Note that this is a shared schema with UTA.

STREAMData sets based on streaming test running on stream agents.

PRIVATEERData sets based on tests running on Private Peer Network

LASTMILEData sets based on tests running on Last Mile Network

MOBILEData sets based on tests running on Mobile Network

Specifies the levels of data in the dataset returned to the client for thetype of data specified with the sMonitorClassDesignatorparameter. Supported values are as follows:

sDataDesignator

ALLReturns all levels of data available.

OBJECTReturns SUMMARY, PAGE, and OBJECT level data. Mobiledatasets will also include MOBILEEXT level data.

PAGEReturns SUMMARY and PAGE level data. Mobile datasetswill also include MOBILEEXT level data.




SUMMARYReturns SUMMARY level data. Mobile datasets will alsoinclude MOBILEEXT level data.

TIMEGROUPReturns aggregation data over specified time window, up to 24hours. (see following parameter descriptions).

Specifies the starting time boundary for the dataset. The format is:sStartTimeYYYY-MM-DD HH:MM:SS

Specifies the ending time boundary for the dataset. The format is:sEndTimeYYYY-MM-DD HH:MM:SS

Specifies how the dataset will be ordered. Supported values are asfollows:

sOrderDesignator

TIMEOrders data by time.

SITEOrders data by site.

MONITOROrders data by monitor class

Supported Combinations

Together, the sDataDesignator and sMonitorClassDesignator values define what will beincluded in the retrieved dataset. The supported combinations are listed in the following table.

DataSet RetrievedsMonitorClassDesignatorsDataDesignator

Summary, page, object, host, andconnection-level.

UTATXALL


BROWSERTX

Summary, event, metadata, andtrace-level.

STREAM


PRIVATE PEER


LASTMILE

Summary, page, object, host, connection,and mobileext-level.

MOBILE

Summary, page, and object level only.UTATXOBJECT

Summary, page, and object level only.BROWSERTX

Summary, page, and object level only.PRIVATE PEER



DataSet RetrievedsMonitorClassDesignatorsDataDesignator

Summary, page, and object level only.LASTMILE

Summary, page, object, andmobileext-level.

MOBILE

Summary and page-level only.UTATXPAGE

Summary and page-level only.BROWSERTX

Summary and page-level only.PRIVATE PEER

Summary and page-level only.LASTMILE

Summary, page, and mobileext-level.MOBILE

Summary-level only.UTATXSUMMARY

Summary-level only.BROWSERTX

Summary-level only.STREAM

Summary-level only.PRIVATE PEER

Summary-level only.LASTMILE

Summary-level only.MOBILE

Up to 24 hours of aggregated data.UTATXTIMEGROUP

Up to 24 hours of aggregated data.BROWSERTX

Validation Criteria

In the following table are descriptions of the validation criteria for the OpenDataFeed request.

DescriptionValidation Criteria

The supplied username is valid for the active APMaaS SyntheticMonitoring account.

Username

The supplied password is valid for the active APMaaS SyntheticMonitoring account.

Password

The set of Monitor IDs is valid for the active APMaaS SyntheticMonitoring account.

MonitorIdSet

The set of Site IDs is valid for the active APMaaS SyntheticMonitoring account.

SiteIdSet

The time window start boundary is valid.StartTime

The time window end boundary is valid.EndTime

The sMonitorClassDesignator value is valid.MonitorClassDesignator

The sDataDesignator value is valid.DataDesignator

The sOrderDesignator value is valid.OrderDesignator

The volume of data does not exceed account constraintsData Volume




The request frequency does not exceed account constraintsFrequency

The request concurrency does not exceed account constraintsConcurrency

OpenDataFeed Response MessageThe OpenDataFeed web service method returns an xml 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.

Sample of a Successful Response Message<?xml version="1.0" encoding="utf-8" ?>

<GpnOpenUtaDataFeedResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns="http://gomeznetworks.com/webservices/">

<Status>

<eStatus>STATUS_SUCCESS</eStatus>

<sErrorMessage />

</Status>

<GPNGlobalConstraints MaxDataRequestsPerHourPerSession="60"

MaxTotalSessions="50" />

<GPNAccountConstraints MaxDataRecordsPerRequest="1000"

MaxConcurrentSessions="1"

MaxConcurrentRequests="1"

MaxRequestIntervalBeforeExpirationInMinutes="15" />

<SessionToken>c59754b7-3ed3-4878-a0e8-c352daa0b8a1</SessionToken>

<AcceptedMonitors>

<mid>1162690</mid>

</AcceptedMonitors>

<AcceptedSites>

<sid>101</sid>

</AcceptedSites>

</GpnOpenUtaDataFeedResponse>

Sample of an Unsuccessful Response Message<?xml version="1.0" encoding="utf-8" ?>

<GpnOpenUtaDataFeedResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"


xmlns="http://gomeznetworks.com/webservices/">

<Status>

<eStatus>STATUS_FAILED</eStatus>

<sErrorMessage>INVALID ORDER DESIGNATOR SPECIFIED.

MUST BE (TIME | MONITOR | SITE)</sErrorMessage>

</Status>

</GpnOpenUtaDataFeedResponse>

OpenDataFeed Response Message DetailsThe following table summarizes the elements and attributes in the XML response returned bythis web service. Refer to the WSDL for the complete definition of this XML response.



DescriptionData Element/AttributeContainer Element

OpenDataFeedResponse

Contains STATUS_SUCCESS orSTATUS_FAILED

eStatusStatus

Contains an error message ifSTATUS_FAILED

sErrorMessage

Maximum number of data requests that canbe made per hour within a given session is60

MaxDataRequestsPerHourPerSessionGPNGlobalConstraints

Maximum number of sessions which canhandled by the service is 32

MaxTotalSessions

Maximum number of data records which maybe obtained per GetResponseData request is1000

MaxDataRecordsPerRequestGPNAccountConstraints

Maximum number of concurrent sessionswhich will be serviced is 1

MaxConcurrentSessions

Maximum number of concurrent requestswhich can be made within the context of agiven session is 1

MaxConcurrentRequests

Maximum amount of time which can elapsebetween calls to "GetResponseData" before

MaxRequestIntervalBeforeExpirationInMinutes

a session may be expired by the system is 15minutes

Session Identifier which is used in subsequentcalls to GetResponseData and CloseDataFeed

SessionToken

Contains the time the request was receivedin GMT

CurrentTime

Contains a list of APMaaS SyntheticMonitoring monitor identifiers which have

AcceptedMonitors

been validated by the system against aspecified account

Contains a list of APMaaS SyntheticMonitoring site identifiers which have been

AcceptedSites

validated by the system against a specifiedaccount

OpenDataFeed2 Request Message DetailsThis represents an alternate version of a OpenDataFeed request, asking for the last N samplesrelative to the current time.Web method for initializing the UTA data feed session based on a number of user-definedcriteria. A data feed session always exports a homogeneous dataset based on the specified



sMonitorClassDesignator and the sDataDesignator tags provides when the session isinitialized.The request message includes parameters and validation criteria, as described in the followingtables.





iMonitorIdSet

sMonitorClassDesignator and only requested monitors meetingthe specified class criteria will be returned.



iSiteIdSet











sDataDesignator









Indicates a window based on the last N test samples relative to thecurrent time. A value of 1 will spec a data export session which always

sLastN

returns the last test acquired relative to the current time. Thisparameter can contain any value up to cap enforced by theMaxDataRecordsPerRequest constraint. Any values specified forthis parameter which exceed this constraint will be set to theconstraint. Ignored when sDataDesignator is TIMEGROUP.

Specifies the starting time boundary for the dataset. The format is:YYYY-MM-DD HH:MM:SS

sStartTime

Specifies the ending time boundary for the dataset. The format is:YYYY-MM-DD HH:MM:SS

sEndTime


sOrderDesignator




Validation Criteria



Username


Password





MonitorIdSet


SiteIdSet









OpenDataFeed3 Request Message DetailsThis represents an alternate version of a OpenDataFeed request using an ARRIVAL versusTEST TIME Filter Interpretation.Web method for initializing the UTA data feed session based on a number of user-definedcriteria. A data feed session always exports a homogeneous dataset based on the specifiedsMonitorClassDesignator and the sDataDesignator tags provides when the session isinitialized.





iMonitorIdSet

sMonitorClassDesignator and only requested monitors meetingthe specified class criteria will be returned.



iSiteIdSet














sDataDesignator






Indicates a window based on the last N test samples relative to thecurrent time. A value of 1 will spec a data export session which always

sLastN

returns the last test acquired relative to the current time. Thisparameter can contain any value up to cap enforced by theMaxDataRecordsPerRequest constraint. Any values specified forthis parameter which exceed this constraint will be set to theconstraint. Ignored when sDataDesignator is TIMEGROUP.




Specifies the starting time boundary for the dataset. The format is:sStartTimeYYYY-MM-DD HH:MM:SS

Specifies the ending time boundary for the dataset. The format is:sEndTimeYYYY-MM-DD HH:MM:SS


sOrderDesignator




Designation indicating how the time filters and modes are to beapplied. Supported values are as follows:

sTimeDesignator

TESTTIME_ABSOLUTETime range filter to be applied relative to the time samples wereacquired by remote agents. This is the current default mode ofoperation for legacy versions of the service.

TESTTIME_RELATIVETime range filter is unused and sLastN must be specified. ThesLastN parameter is interpreted as last N samples relative tothe time samples were acquired by remote agents.

ARRIVAL_ABSOLUTETime range filter to be applied relative to the time samplesarrived at the central data repositories. This is a new mode ofoperation.

ARRIVAL_RELATIVETime range filter is unused and sLastN must be specified. ThesLastN parameter is interpreted as last N samples relative tothe time samples arrived at the central data repositories.

Validation Criteria



Username


Password


MonitorIdSet


SiteIdSet









The sTimeDesignator values are valid.Time Designator




GetResponseData Request Message DetailsThis web method returns the next chunk of the dataset for a specified transaction from eachsite. Range, content, and volume of data will be based on constraints setup when the sessionwas opened with one of the OpenDataFeed web methods and the standard system and accountlevel constraints.


Unique Identifier issued by the initial OpenDataFeed call for thesession.

sSessionToken

Validation Criteria


The sSessionToken value is validSession Token




GetResponseData Response Message DetailsThis Web method returns an XML message containing:

• Status of operation

• Number of data records returned

• XML subdocument containing

• Type of data returned

• APMaaS Synthetic Monitoring Performance Dataset



DescriptionData Element/AttributeContainerElement

GetResponseData


eStatusStatus

Contains an error message if STATUS_FAILEDsErrorMessage

Contains the number of records exported in thecurrent response

NumRecords

Contains the performance data subdocument(see XSD)

XmlDocument

Indicates the "type" of performance dataexported in the current request. This will reflect

MonitorDesignatorGpnResponseData

the MonitorClassDesignatorvalue specified inthe initialization call to the OpenDataFeedservice.

Top level container for test informationTestRefer to XSD for further details

Sample GetResponseData Streaming Response MessageFor a streaming data type, the a successful call to the GetResponseData web service methodreturns an XML message similar the following:

Sample of a Successful Response Message<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"


xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<soap:Body>

<GetResponseDataResponse xmlns="http://gomeznetworks.com/webservices/">

<GpnResponseData>

<Status>

<eStatus>STATUS_SUCCESS</eStatus>

<sErrorMessage/>

</Status>

<NumRecords>177</NumRecords>

<CurrentTime>2013-01-15 17:49:54</CurrentTime>

<XmlDocument>

<GpnResponseData xmlns="">

<MonitorDesignator MonitorClassDesignator="STREAM"/>

<STREAMTEST mid="150240" sid="886"

ttime="2012-12-27T10:17:32.467+00:00"

pseq="-1" sseq="0"

stime="2012-12-27T10:18:51.03+00:00"

errrsyscode="0" errrawcode="0" ip="165.254.6.25"

url="http://www.mycompany.com/mychannel/tr4.5.2.swf"

durinms="59357" fps="-1" endtype="EXPIRED"

bps="1228753" dnsoffset="258" dnstime="97"

connoffset="355" conntime="8" initbuftime="87"

rebuftime="-1" rebufcnt="0" initplytime="1"

spt="693" plycnt="2" initialdatareceivetime="243">

<EVENT sevt_id="0" name="CONNECT_START" offset="355"/>

<EVENT sevt_id="1" name="CONNECT_END" offset="363"/>

</STREAMTEST>

</GpnResponseData>

</XmlDocument>



</GpnResponseData>

</GetResponseDataResponse>

</soap:Body>

</soap:Envelope>

CloseDataFeed Request Message DetailsWeb method for closing an active data feed session. Calling this method causes expiration ofthe Virtual Session Token.


Unique Identifier issued by the initial OpenDataFeed call for thesession.

sSessionToken

CloseDataFeed Response Message DetailsWeb method returns an XML message containing the status of operation.


CloseDataFeed


eStatusStatus


sErrorMessage

GetErrorCodes Request Message DetailsGetErrorCodes is a web method for exporting raw error codes and definitions.


n/a

GetErrorCodes Response Message DetailsGetErrorCodes returns an xml message containing all of the Test Response Error Codes anddefinitions.


GetErrorCodes


eStatusStatus


sErrorMessage

Contains the error code numberErrorNumErrorCodes

Contains short error descriptiontext

Description



Data Service SecurityAll interactions with the Data Services require authentication by user name and password orvia issued session tokens.All credentials presented to the service must be successful authenticated by the service as:

• Being a valid APMaaS Synthetic Monitoring user in good standing.

• Being explicit configured as having access and proper entitlements to the API.



C H A P T E R 3

FTP Data Feeds

The FTP data feed is the preferred method of downloading large amounts of data from theCompuware APMaaS platform for integration with customer applications.

Access FTP Data Feed FilesFollow this procedure to access the FTP data feed files in your FTP account directory.

Before You Begin

To start receiving an FTP Data Feed, you need to do two things:

• Create tests using the APMaaS Portal or GPN Portal

• Obtain an FTP data feed login from Customer Support

After you obtain your FTP data feed login, you automatically receive test results in your FTPaccount directory.

1. Open Windows Explorer.2. In the Address field enter: ftp://ftp.gomez.com/

3. From the menu, select File ➤ Login As.The Log On As dialog box is displayed.

4. Enter your FTP data feed credentials in the User name and Password fields and click LogOn.

5. Depending on the tests you have set up in your APMaaS Synthetic Monitoring account,APMaaS Synthetic Monitoring will have deposited one or more FTP data feed files in yourFTP account directory. For more information, see FTP Data Feed File Information [p. 31].

FTP Data Feed File InformationEach FTP data feed is a .zip file containing one or more files with names in the followingformat:[t|to|lm|lmo|monitor|site]-year-month-day_hour-minute.*


ftp://ftp.gomez.com/

Data SourceData Feed Type

UTAT

UTA object-level2TO

Last MileLM

Last Mile object-level2LMO

Monitor test dataMonitor

Node (site) test dataSite

All of the .zip files contain at least one text file that contains test result data. The .zip file forthe T data feed contains these additional files:

T fileContains test result data.

Monitor fileContains monitor-specific information.

Site fileContains site-specific information.

Each text file in the data feed is in pipe-separated (|) value format. Each value is encased indouble quotes since many values contain commas and spaces.

T File LayoutFTP data feed T files contain UTA test data.Each text file in the data feed is in pipe-separated (|) value format. Each value is encased indouble quotes since many values contain commas and spaces.

DescriptionField

Unique test identifiermonitor_id

Test time in GMTtesttime

Node where the test ransite_id

Response time in milliseconds. Sum all the troresponsetimes for agiven seqno in this file to obtain the mrresponsetime. This field isNULL, if the test fails.

mrresponsetime

Page number of the testseqno

"0" if success; error code, if failurestatus

Response time in milliseconds of the page. Sum all thetroresponsetimes for a given seqno in this file to obtain themrresponsetime. This field is NULL, if the test fails.

troresponsetime

URL of the page testedurl

2 This data feed required special setup through Customer Support.


Chapter 3 ∙ FTP Data Feeds

DescriptionField

Name of the node where the test ranname

Always "0"RealURLFlag

Monitor File LayoutThis file lists test (monitor) data.Each text file in the data feed is in pipe-separated (|) value format. Each value is encased indouble quotes since many values contain commas and spaces.

DescriptionField

Unique test identifierMonitor_id

Description of the testDescription

TRANSACTION (for UTA Agent)Class

If class=MONITOR then URL of the test: otherwise, NULLURL

1 if page objects are downloaded, 0 otherwiseComponentFlag

ACTIVE, INACTIVE, or DELETEStatus

Interval that the test runs in number of milliseconds. For example,frequency=3600 means that the test runs once every hour.

Frequency

Date when the test was created.CreateDate

Date when the test was last changed.ModDate

Site File LayoutThis file lists node (site) data.Each text file in the data feed is in pipe-separated (|) value format. Each value is encased indouble quotes since many values contain commas and spaces.

DescriptionField

Unique node identifiersite_id

Name of the nodename

ACTIVE, INACTIVE, or DELETEStatus

Internet Service Provider of the data center nodebackbone

City of the data center nodeCity

State of the data center nodeState

Country code of the data center nodeCountryCode

IP address of the data center nodeipaddress



LM File LayoutThis file contains Last Mile test data.Each text file in the data feed is in pipe-separated (|) value format. Each value is encased indouble quotes since many values contain commas and spaces.

DescriptionField

Unique test identifiermgbmonitor_id


Response time in milliseconds; NULL, if test failsmrresponsetime

Page number of the testseqno

"0" if success; error code if failurestatus

Response time in milliseconds of the page. Sum all thetroresponsetimes for a given seqno in this file to obtain themrresponsetime. This field is NULL, if the test fails.

troresponsetime

URL of the page testedurl

Name of the node where the test ranname

IP address of the urlIP

Unique identifier of the Last Mile computerLMA_id

Region of the Last Mile computerLMA_REGION_NAME

Internet Service Provider of the Last Mile computerLMA_ISP_NAME

IP address of the Last Mile computerLMA_IP_ADDRESS

Average throughput in bits per second of the Last Mile machineavgthruput

Total bytes downloaded; "0" if test failscompbytes

TO File LayoutThe TO file contains Backbone UTA object-level test data.This data feed requires special set up. Contact Customer Support to activate this data feed.Each text file in the data feed is in pipe-separated (|) value format. Each value is encased indouble quotes since many values contain commas and spaces.

DescriptionField



Unique node identifier of the site where the test ransite_id

Name of the node where the test ransitename




DescriptionField

Page number of the testpageseqnum

GOOD if success; APMaaS Synthetic Monitoring error code if failurepagestatus

Response time in milliseconds of the page. Sum all thepageresponsetimes for a given seqno in this file to obtain themrresponsetime. This field is NULL, if the test fails.

pageresponsetime

URL of an object on the pageurl

HTTP return code of the objectcompReturnCode

Usually "0", but if the first object, the time in milliseconds to DNSconnect

compDNS

Time in milliseconds to connect to the objectcompConnect

Time in milliseconds to SSL connect to the objectcompSSL

Time in milliseconds to download the first byte of the objectcompFirstByte

Time in milliseconds to download the objectcompContent

IP address of the server hosting the objectcompIP

Sequence number of the object relative to the entire testobjseqnum

Sequence number of the host relative to the entire testhost_id

Sequence number of the connection relative to the entire testconnection_id

LMO File LayoutThe LMO file contains Last Mile object-level test data.This data feed requires special set up. Contact Customer Support to activate this data feed.Each text file in the data feed is in pipe-separated (|) value format. Each value is encased indouble quotes since many values contain commas and spaces.

DescriptionField



Unique node identifier of the site where the test ransite_id


Page number of the testpageseqnum

GOOD if success; error code if failurepagestatus

Response time in milliseconds of the page. Sum all thepageresponsetimes for a given seqno in this file to obtain themrresponsetime. This field is NULL, if the test fails.

pageresponsetime

URL of an object on the pageurl



DescriptionField

HTTP return code of the objectcompReturnCode

Usually "0", but if the first object, the time in milliseconds to DNSconnect

compDNS

Time in milliseconds to connect to the objectcompConnect

Time in milliseconds to SSL connect to the objectcompSSL

Time in milliseconds to download the first byte of the objectcompFirstByte

Time in milliseconds to download the objectcompContent

IP address of the server hosting the objectcompIP

Sequence number of the object relative to the entire testobjseqnum

Sequence number of the host relative to the entire testhost_id

Sequence number of the connection relative to the entire testconnection_id

Name of the region that the peer is located inpeer_region_name

ISP used by the peerpeer_isp_name

IP address of the peerpeer_ip_address

Average throughput in bits per second of the Last Mile machineavgthruput

Total bytes downloaded for the objectnumbytes



A P P E N D I X A

Data Export Web Service 4.0 Response XSD

<?xml version="1.0" encoding="utf-8"?>



<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">



<xs:element name="GpnResponseData" type="CGpnUniversalXmlDocResponse" nillable="true"/>

<xs:complexType name="CGpnUniversalXmlDocResponse">

<xs:sequence>



<xs:element name="Status" type="COpStatusData" minOccurs="0"/>



<xs:element name="NumRecords" type="xs:int"/>



<xs:element name="CurrentTime" type="xs:string" minOccurs="0"/>



<xs:element name="XmlDocument" type="XmlDocumentType" minOccurs="0"/>

</xs:sequence>

</xs:complexType>



<xs:complexType name="XmlDocumentType">

<xs:sequence minOccurs="0">

<xs:element name="GpnResponseData" type="GpnResponseDataType"/>

</xs:sequence>

</xs:complexType>

<!--

***************************************************

Response Data Payload Type

***************************************************

-->

<xs:complexType name="GpnResponseDataType">

<xs:sequence>



<xs:element name="MonitorDesignator" type="MonitorClassDesignatorType"/>



<xs:choice minOccurs="0" maxOccurs="unbounded">



<xs:element name="TXTEST" type="TxTestType"/>



<xs:element name="TXTIMEGROUP" type="TxTimegroupType"/>



<xs:element name="STREAMTEST" type="StreamTestType"/>



<xs:element name="SINGLEURLTEST" type="SingleUrlTestType"/>



<xs:element name="DATACUT" type="DataCutTestType"/>



<xs:element name="MESSAGE" type="MessageType" minOccurs="0"/>

</xs:choice>

</xs:sequence>

</xs:complexType>



<xs:complexType name="TxTimegroupType">

<xs:attribute name="monitor_id" type="xs:int" use="required"/>

<xs:attribute name="avail" type="xs:float" use="required"/>

<xs:attribute name="avgresp" type="xs:float" use="required"/>

<xs:attribute name="avgDNS" type="xs:float" use="required"/>

<xs:attribute name="avgConnect" type="xs:float" use="required"/>

<xs:attribute name="avgFirstByte" type="xs:float" use="required"/>

<xs:attribute name="avgContent" type="xs:float" use="required"/>

</xs:complexType>



<xs:complexType name="TxTestType">

<xs:sequence>



<xs:element name="MOBILEEXT" minOccurs="0" maxOccurs="1">

<xs:complexType>

<xs:attribute name="carrier">

<xs:simpleType>

<xs:restriction base="xs:string">

<xs:maxLength value="200"/>

</xs:restriction>

</xs:simpleType>

</xs:attribute>

<xs:attribute name="location">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>

<xs:attribute name="connspeed">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>

<xs:attribute name="conntype">

<xs:simpleType>



</xs:restriction>


Appendix A ∙ Data Export Web Service 4.0 Response XSD

</xs:simpleType>

</xs:attribute>

<xs:attribute name="signalstrength" type="xs:int"/>

</xs:complexType>

</xs:element>



<xs:element name="PAGE" minOccurs="0" maxOccurs="unbounded">

<xs:complexType>

<xs:sequence>



<xs:element name="OBJECT" minOccurs="0" maxOccurs="unbounded">

<xs:complexType>



<xs:attribute name="oseq" type="xs:int" use="required"/>



<xs:attribute name="hid" type="xs:int"/>



<xs:attribute name="connid" type="xs:int"/>



<xs:attribute name="rc" type="xs:int"/>



<xs:attribute name="ctype">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="rtime" type="xs:int"/>



<xs:attribute name="nbyte" type="xs:int"/>



<xs:attribute name="fbstart">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="fbtime" type="xs:int"/>



<xs:attribute name="contstart">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="conttime" type="xs:int"/>



<xs:attribute name="uhost">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="upage">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>

<xs:attribute name="uparam">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="redirobjid" type="xs:int"/>

<xs:attribute name="csum" type="xs:int"/>

</xs:complexType>

</xs:element>

</xs:sequence>



<xs:attribute name="pseq" type="xs:int" use="required"/>






<xs:attribute name="nobj" type="xs:int"/>



<xs:attribute name="rc200" type="xs:int"/>


-->



-->



-->




<xs:attribute name="rcnet" type="xs:int"/>



<xs:attribute name="rcint" type="xs:int"/>






<xs:attribute name="nhost" type="xs:int"/>



<xs:attribute name="nconn" type="xs:int"/>



<xs:attribute name="cmtext">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="cmstat" type="xs:int"/>



<xs:attribute name="tostat" type="xs:int"/>



<xs:attribute name="usstat" type="xs:int"/>



<xs:attribute name="blstat" type="xs:int"/>



<xs:attribute name="rtobjseq" type="xs:int"/>



<xs:attribute name="dnssum" type="xs:int"/>



<xs:attribute name="ndns" type="xs:int"/>



<xs:attribute name="nconn1" type="xs:int"/>

<!-- Sum of all SSL times (CONN.ssltime) for all the secure connections associated

<xs:attribute name="sslsum" type="xs:int"/>



<xs:attribute name="nssl" type="xs:int"/>



<xs:attribute name="fbsum" type="xs:int"/>



<xs:attribute name="nfb" type="xs:int"/>



<xs:attribute name="ncont" type="xs:int"/>



<xs:attribute name="ptime" type="xs:int"/>

</xs:complexType>

</xs:element>



<xs:element name="HOST" minOccurs="0" maxOccurs="unbounded">

<xs:complexType>

<xs:sequence>



<xs:element name="CONN" minOccurs="0" maxOccurs="unbounded">

<xs:complexType>



<xs:attribute name="connid" type="xs:int" use="required"/>



<xs:attribute name="page" type="xs:int"/>






<xs:attribute name="connstart">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="conntime" type="xs:int"/>



<xs:attribute name="sslstart">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="ssltime" type="xs:int"/>






<xs:attribute name="nerr" type="xs:int"/>




</xs:complexType>

</xs:element>

</xs:sequence>



<xs:attribute name="hid" type="xs:int" use="required"/>



<xs:attribute name="page" type="xs:int"/>



<xs:attribute name="dnsstart">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="dnstime" type="xs:int"/>






<xs:attribute name="nerr" type="xs:int"/>






<xs:attribute name="nconn" type="xs:int"/>



<xs:attribute name="ip">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>

</xs:complexType>

</xs:element>

</xs:sequence>



<xs:attribute name="mid" type="xs:int" use="required"/>



<xs:attribute name="sid" type="xs:int" use="required"/>



<xs:attribute name="ttime">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="sname" use="optional">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="popname" use="optional">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>






<xs:attribute name="tpt" type="xs:int"/>



<xs:attribute name="tps" type="xs:int"/>



<xs:attribute name="tpf" type="xs:int"/>



<xs:attribute name="tot" type="xs:int"/>



<xs:attribute name="tos" type="xs:int"/>



<xs:attribute name="tof" type="xs:int"/>






<xs:attribute name="browsertype">

<xs:simpleType>



<xs:pattern value="UTA|IE7|FF35"/>

</xs:restriction>

</xs:simpleType>

</xs:attribute>

</xs:complexType>



<xs:complexType name="DataCutTestType">



<xs:attribute name="cutdate">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>


/ Mobile) -->






<xs:attribute name="ttime">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>

</xs:complexType>



<xs:complexType name="MessageType">


/ Mobile) -->




<xs:attribute name="Msg" type="xs:string" use="required"/>

</xs:complexType>



<xs:complexType name="MonitorClassDesignatorType">

<xs:attribute name="MonitorClassDesignator">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>

</xs:complexType>



<xs:complexType name="StreamTestType">

<xs:sequence>



<xs:element name="EVENT" minOccurs="0" maxOccurs="unbounded">

<xs:complexType>

<xs:attribute name="sevt_id" type="xs:int" use="required"/>



<xs:attribute name="name">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="offset" type="xs:int"/>

</xs:complexType>

</xs:element>



<xs:element name="META" minOccurs="0" maxOccurs="unbounded">

<xs:complexType>



<xs:attribute name="metaseq" type="xs:int" use="required"/>



<xs:attribute name="smetakey">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="smetaval">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>

</xs:complexType>

</xs:element>



<xs:element name="TRACE" minOccurs="0" maxOccurs="unbounded">

<xs:complexType>



<xs:attribute name="hopnum" type="xs:int" use="required"/>




<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="host">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="delay" type="xs:int"/>

</xs:complexType>

</xs:element>

</xs:sequence>


/ Mobile) -->






<xs:attribute name="ttime" type="xs:dateTime" use="required"/>



<xs:attribute name="pseq" type="xs:int" use="required"/>



<xs:attribute name="sseq" type="xs:int" use="required"/>



<xs:attribute name="stime" type="xs:dateTime" use="required"/>



<xs:attribute name="errrsyscode" type="xs:int" use="required"/>



<xs:attribute name="errdesc">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="errrawcode" type="xs:int"/>



<xs:attribute name="sproto">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>




<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="url">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="durinms" type="xs:int"/>



<xs:attribute name="fps" type="xs:int"/>



<xs:attribute name="endtype">

<xs:simpleType>



<xs:pattern value="SUCCESS|EXPIRED|FAILED"/>

</xs:restriction>

</xs:simpleType>

</xs:attribute>

<xs:attribute name="bps" type="xs:int"/>



<xs:attribute name="stype">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="splat">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="sver">

<xs:simpleType>



</xs:restriction>

</xs:simpleType>

</xs:attribute>



<xs:attribute name="dnsoffset" type="xs:int"/>



<xs:attribute name="dnstime" type="xs:int"/>



<xs:attribute name="connoffset" type="xs:int"/>



<xs:attribute name="conntime" type="xs:int"/>



<xs:attribute name="initbuftime" type="xs:int"/>



<xs:attribute name="rebuftime" type="xs:int"/>



<xs:attribute name="rebufcnt" type="xs:int"/>



<xs:attribute name="initplytime" type="xs:int"/>



<xs:attribute name="spt" type="xs:int"/>



<xs:attribute name="initrebuftime" type="xs:int"/>



<xs:attribute name="plycnt" type="xs:int"/>

</xs:complexType>



<xs:complexType name="COpStatusData">

<xs:sequence>



<xs:element name="eStatus" type="StatusType"/>



<xs:element name="sErrorMessage" type="xs:string" minOccurs="0"/>

</xs:sequence>

</xs:complexType>

<xs:simpleType name="StatusType">




<xs:enumeration value="STATUS_SUCCESS"/>



<xs:enumeration value="STATUS_FAILED"/>

</xs:restriction>

</xs:simpleType>

</xs:schema>

Index

Aalerts 9

Bbackward compatibility 5

CCloseDataFeed

29request message 29response message 29

Customer Support6

contact information 6online support site 6

Ddata feed

9–11FTP 9obtaining 11selecting 10selection 11web service 9XML 9

DataExport Services 15

Eemailed reports 9

Ffeatures 5FTP data feed

31

FTP data feed (continued)access 31file information 31

FTP Data Feed32–35

LM file layout 34monitor file layout 33site file layout 33T file layout 32, 35TO file layout 34

GGetErrorCodes

29request message 29response message 29

GetResponseData27–28

request 27response 27streaming

28response 28

LLM file layout 34

Mmonitor file layout 33

OOpenDataFeed

16, 20request message 16response 20session 16


Index

OpenDataFeed221

request 21OpenDataFeed3

24request 24

options 9overview 5

Ssecurity 30site file layout 33

TT file layout 32, 35TO file layout 34

UURL 16

WWSDL 16

XXSD 16, 37


Index

APMaaS Synthetic Monitoring for Web & Mobile ... - … Synthetic Monitoring for Web & Mobile ......

Documents

Transcript of APMaaS Synthetic Monitoring for Web & Mobile ... - … Synthetic Monitoring for Web & Mobile ......