Skip to main content

WSO2 Cloud

Introduction

WSO2 Cloud consists of three commercial cloud offerings namely the API cloud, Integration Cloud and the Identity Cloud.

WSO2 Integration Cloud

WSO2 Integration Cloud is a public hosted version of the powerful, 100% open-source WSO2 Enterprise Integrator. It allows you to host your cloud-to-cloud, cloud-to-on-premise integrations and API backends on a scalable cloud platform

WSO2 API Cloud

WSO2 API Cloud is an enterprise-ready, self-service platform that enables you to expose business capabilities as managed APIs and leverage off-the-shelf potential for advertising and selling business APIs. The API Cloud supports all aspects of an API’s lifecycle, from its creation to publication and retirement.
The API Cloud is based on WSO2 API Manager, WSO2’s complete solution for designing and publishing APIs and managing a developer community. [2]

WSO2 Identity Cloud

WSO2 Identity Cloud leverages the functionality of WSO2 Identity Server’s identity and access management (IAM) capabilities. This is an enterprise-ready service that enables you to set up your applications for single sign-on and connect them to your LDAP user store.

Getting Started with WSO2 Cloud

To get started with WSO2 Cloud you can create your free trial account, it’s pretty simple. You can go to this link and create an account providing your email address and get started with the cloud. https://cloudmgt.cloud.wso2.com/cloudmgt. Once you are registered you can log in to the WSO2 Cloud and select the suitable Cloud type.
So now you can get started enjoying the benefits of cloud computing. You will be able to understand about the cloud further by following my upcoming blog posts. If you have any questions regarding the WSO2 Cloud and the services it offers you can contact the WSO2 cloud team at cloud@wso2.com or visit out website http://wso2.com/cloud/ and we would be glad to be of assistance to you.

References

[1] https://docs.wso2.com/display/IntegrationCloud/Introduction
[2] https://docs.wso2.com/display/APICloud/Introduction
[3] http://wso2.com/cloud/

Comments

  1. funexcryptoMarch 17, 2024 at 10:46 PM

    Experience top-tier server with our Amsterdam data center! Harness robust infrastructure for seamless operations and data security.

    ReplyDelete

Post a Comment

Popular posts from this blog

Invoking external endpoints using the call mediator in wso2 api manager

Introduction In API Manager if you need to do any service chaining use cases the call mediator comes in handy. If you need to use the response received by invoking one endpoint and then use it to invoke another endpoint you can use the call mediator in API Manager. The call mediator behaves in a synchronous manner. Hence, mediation pauses after the service invocation and resumes from the next mediator in the sequence when the response is received. You can read more about the call mediator in the wso2 esb documentation [1] . In api manager 1.10.0 the call mediator works in the blocking mode. Prerequisite Before we can use the call mediator in API Manager 1.10.0 we need to make the following changes to some configs. We need to comment the jms transport sender in axis2_blocking_client.xml found in the location APIM_HOME/repository/conf/axis2. This will resolve the jms sender initialization issues.   <!--transportSender name="jms"        ...
1 comment
Read more

Adding error sequence to a custom sequence

In my previous posi i explained how to call an endpoint using the call mediator. Usually when errors are thrown from the call mediator we can handle them using a custom sequence. When call mediators fails the execution stops hence handling errors is very essential. For this post I will be modifying the same sequence which i created in the blog post [1] The change which we need to do is we need to modify the sequence definition to map with the error sequence as shown below. You can find the modified sequence here . <sequence xmlns="http://ws.apache.org/ns/synapse" name="countrySequenceWithError" onError="countryErrorSequence"> <property name="uri.var.countryCode" expression="$url:countryCode"/> <property name="REST_URL_POSTFIX" scope="axis2" action="remove"/>     <call blocking="true">         <endpoint>             <http method="get" uri-temp...
2 comments
Read more

Adding custom error messages within a custom sequence in API Manager

Overview You can add custom error messages for an API by following the post [1] but when the error is thrown inside the custom in or out sequence we add as the mediation extension this custom error sequence which we specify for the API does not get invoked. Therefore we need to specify the error sequence seperately for the custom sequence. This blog will explain how to carry out this use case. Let's get started To demonstrate this I will be using the call mediator inside the custom sequence. Since when an invalid endpoint is invoked with the call mediator it would generate an error in the API Manager which would be received inside our custom sequence. 1) You can follow my previous tutorial [2] to get a better understanding and configurations needed to use the call mediator using wso2 api manager 1.10.0. Create the API as mentioned in the sequence above and subscribe and generate keys for the API in the store. 2) Now what we are going to do is, we are going to provide an ...
Post a Comment
Read more