webMethods API Cloud Service Description

1.0 Service Specification

webMethods API Cloud
Latest Version: webMethods API Cloud
Base Operating System: Ubuntu Linux 14.04
Infrastructure Services: Amazon Web Services
Delivery Method: Web application – (PaaS, public)
Data Storage Location EMEA (Ireland)
Service Tier: Tenant
Production Term: 12 months minimum
Support: Included, see details below
Standard Maintenance Window: Wednesday 0:00-3:00am PST
Payment: Invoice
Renewal: Upon payment of renewal term
Retention of data: Inclusive (30 days post subscription expiration)
Restoration after subscription expiration: Upon payment of renewal term
Publication Date of Service Description October 1, 2015

2.0 Introduction to webMethods API Cloud

webMethods API Cloud is a cloud native Software AG hosted and operated application that allows customers to expose API documentation to external developers and business partners, and provides self-service capabilities for user onboarding and management.

Common Application Uses

webMethods API Cloud allows customers to create an external facing API catalog to expose descriptions of APIs to 3rd party developers and B2B partners. Besides hosting the API documentation, the API cloud also features developer onboarding, API testing and collaboration functionalities, and usage reporting. Administrators can directly import APIs into API cloud or publish them from an on-premises CentraSite environment.

3.0 Service Description

License Metric: Tenant The licensing metric for API Cloud is tenant-based. Customers can license multiple tenants. Tenants are entirely separated from other tenants. Each tenant allows for dedicated user management, customizations, data and other operational aspects. There are no limits for the number of APIs or onboarded users.

4.0 Third-Party Infrastructure, Software & Components

The Software AG Cloud Services provided hereunder may utilize software code owned or provided by third-party licensors as set forth for each then-current version under: The respective Third-Party Code may be subject to a separate Third-Party License as set forth in the then-current version of the above document. The underlying third-party code terms & conditions require usage of the software in strict accordance with the Agreement and such license. Furthermore, the named Third-Party Code is protected by copyright law and international treaties.

5.0 Software AG’s Standard Support Services

Software AG webMethods API Cloud standard support services consist of:
Phone/web support during regular business hours for your company's support hub
Product/service updates
Access to Empower ( Empower is designed to help you quickly resolve problems or questions, and features these areas:
Knowledge Center: Search for knowledge base articles, early warnings, and fixes, technical papers, and your company's support incidents.
Products & Documentation: Contains product documentation, the Software Download Center (which enables customers to download Software AG products), product version availability information, early product announcements, and product upgrades.
Contact Support: Includes eService, which offers the ability to submit new support incidents online, attach diagnostic information, and check the status of existing requests.
Seven (7) authorized technical contacts

Service Expectations

The following support severities are used for classifying issues. These classifications ensure consistent treatment of issues handled by Software AG Global Support Services. Software AG Global Support Services will determine the appropriate severity level and action timelines according to the following table, and customer-specific contract provisions.
Severity Level Crisis Critical Standard
Definition Customer’s problem has a severe business impact, e.g. production down. Customer is unable to use the Services, resulting in a major impact on customer’s operations. Work cannot reasonably continue. Customer’s problem has a significant business impact; however, operations can continue in a restricted fashion. The Services are usable but severely limited. There is no acceptable workaround available. Customer is experiencing a significant loss of service. Customer’s problem has some business impact. The Services are usable and causes only minor inconvenience. It may be a minor Error, documentation Error, or incorrect operation of the application, which does not significantly impede the operation of a system.
Reaction time 1 Hour: call-back or electronic reply 4 Business Hours: call-back or electronic reply 1 Business Day: call-back or electronic reply
Reporting(timeframe) daily reporting (unless otherwise agreed with Software AG Global Support on a case-by-case basis) as agreed with Software AG Global Support Services on a case-by-case basis as agreed with Software AG Global Support Services on a case-by-case basis
Reaction measure customer is provided with a timeline for Error Correction customer is provided with a timeline for Error Correction information about publication date of the Services release that will solve the issue

indication that changes/ enhancements are being handled in accordance with Software AG's strategy
It is recommended that crisis requests be reported by phone to obtain best possible service in crisis situations.

Service Availability
Subject to standard availability of the infrastructure provider, the infrastructure servers will run 24x7 production operation except for standard maintenance windows set forth in the Service Specification above and mutually planned maintenance windows for cause (“Infrastructure Availability Hours”).

Based on the average availability of the infrastructure provider, webMethods API Cloud is expected to be available for remote access 99.5% of the Infrastructure Availability Hours in accordance with the infrastructure provider’s standards measured in 5 minute intervals, as defined below, each calendar month, excluding Excused Outages as defined below (“Service Availability”). Downtime as a result of any causes beyond the control of Software AG or that are not reasonably foreseeable by Software AG, including, without limitation by any of the events noted below are excluded from the Service Availability calculations (collectively, “Excused Outages”):

• Customer environment issues affecting connectivity or interfering with the Software AG Cloud Services including without limitation, Customer’s telecommunications connection or any other Customer software or equipment, Customer’s firewall software, hardware or security settings, Customer’s configuration of anti-virus software or anti-spyware or malware software, or operator error of Customer;
• any third party software, hardware, or telecommunication failures, including Internet slow-downs or failures;
• force majeure events, including, without limitation fire, flood, earthquake, elements of nature or acts of God; third party labor disruptions, acts of war, terrorism, riots, civil disorders, rebellions or revolutions; quarantines, embargoes and other similar governmental action; or any other similar cause beyond the reasonable control of Software AG;
• issues related to third party domain name system (DNS) errors or failures;
• scheduled maintenance of the respective Software AG Cloud Service, conducted on a regular basis as set forth in the Service Description; and
• emergency maintenance of the respective Software AG Cloud Service, not to exceed four (4) hours in any month. In the event Software AG fails to achieve the average Service Availability, Software AG will use commercially reasonable efforts to correct the interruption as promptly as practicable. In the event of continuous outages in excess of 2 business days and not caused by Excused Outages (the “Excess Outage Period“), Software AG agrees, upon Customers written request received during the Excess Outage Period or no later than 5 business days thereafter, to extend the service term by the total number of Excess Outage Period days that have occurred during the original term or any renewal term. The foregoing is Customer’s sole and exclusive remedy and states Software AG’s entire liability arising out of any Excess Outage Period. In the event an Excess Outage Period occurs in two consecutive months during the term of Customer’s order, Customer may – instead of prolongation of the term by such Excess Outage Periods - terminate its order within thirty (30) days of the end of the second consecutive month, without further obligation and receive a prorated refund of any pre-paid, unused fees. The refund will constitute Customer’s sole and exclusive remedy and Software AG’s sole and exclusive liability for Excess Outage Periods.

6.0 Tenant Backup and Snapshot

The customer environment (also referred to as Tenant) will be backed up daily (each back up will be stored for 7 days), weekly (each back up will be stored for 4 weeks) and monthly (each back up will be stored for 1 month). The Tenant snapshots shall provide the customer the ability to “revert” to stored snapshots with respect to functionality, data and state of the Tenant when the snapshot was created.