Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

This are the activities involved in support and maintenance:


is what we do in the Support and Maintenance phase:


Handling hosting incidents



Tip: The support and maintenance tasks discussed here are subjected to the WSO2 Managed Cloud Policy and Service Level Agreement.


Send weekly status updates

WSO2 sends weekly status update emails to the customer with the following information:

  • A summary of the hosting-related JIRAs raised for the Managed Cloud.
  • A summary of the maintenance tasks done during the current week.
  • A summary of the maintenance work scheduled for the next week, including any scheduled downtimes.

Handle issues in the system

If an unplanned interruption that affects the availability, quality, or performance of the services managed by the WSO2 Managed Cloud team occurs, we call it a hosting incident. A hosting incident might occur in deployment, upgradingupgrade, maintenance, network configuration, startup, stopping, monitoring, and performance, and it it has to be within the parameters scope of the Managed Cloud's deployment architecture.

The diagram below depicts the hosting incident handling process.

Image Removed 

Maintaining servers

<coming up soon>

Managing tasks

<coming up soon>shows how WSO2 handles a hosting incident from its initiation to closure:

Image Added

Diagram: WSO2 incident-handling process

How to report a hosting incident

Note that the customer needs to either raise a support JIRA through  the support Website  or call the phone support numbers to report a hosting incident. As you need to be a WSO2 production support customer to receive WSO2 Managed Cloud services, we assume you already have a support account in the WSO2 support system. If not, please talk to your account's manager at WSO2.

 The steps below explain how to use the support Website to raise a hosting incident. 

  1. Log in to the support system at

  2. Click the Create button in the top menu bar of the support Website.
    Image Added
  3. Select your project from the list of available projects, and s elect the Issue Type as Hosting.
    Image Added 

  4. Fill in the rest of the issue details. Please include the following contact details in the description field so that WSO2 can contact you if required.

    • Name

    • Email address

    • Telephone number (country code, area code, number, and extension)
  5. Once done, click Create to create an incident JIRA. 


Tip: Also see WSO2 Managed Cloud Production Support Guidelines .

Manage tasks

A task is an action item that either the customer or WSO2 needs to perform to ensure that certain objectives are met. For example, the WSO2 Managed Cloud team may create a task for the customer to provide details on their production environment.

The task-handling process is similar to our incident-handling process as shown in the following diagram:

Image Added

Diagram: WSO2 task-handling process

Manage deployment artifacts

A deployment artifact is a program, config change, patch etc. that the customer or WSO2 deploys to the Managed Cloud, either manually or via automated scripts.  Both the customer and WSO2 need to follow the below best practices to minimize the possibility of new artifact deployments causing issues in the Cloud setup:

  • Ensure that all deployment artifacts go through the complete application management lifecycle (ALM) before being deployed in the production servers.
  • Ensure that all the artifacts are properly tested. If additional testing and development need to be done to an artifact, the customer can request development support from WSO2.

Manage upgrades and migrations

In case of a WSO2 product migration or an upgrade that is either suggested by WSO2 or the customer, WSO2 first carries out an effort estimation. If there are no customizations done to the WSO2 products, then the upgrade or migration can be straightforward. If not, the customer and the WSO2 account manager together are to decide how to handle the upgrade or migration of customer-specific data and any custom codes.  Any WSO2 product customization, done by either the customer or WSO2, does not belong to WSO2. The ownership of any custom code is with the customer.

Apply WSO2 security patches

Given below is the WSO2 security patch application process.

Image Added

Note that the non-production environment where the security patches are first tested on must be shared with WSO2 by the customer beforehand. 

Applying monthly security updates is a m andatory operation. WSO2 Operations team takes every possible measure to ensure a smooth update with ideally no downtime. WSO2 expects your cooperation towards this task. If you do not wish to have updates installed or wish delay them, please send an email to with the reason.