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

Processing large payloads with the esb script mediator iteratively

Overview WSO2 ESB uses Rhino engine to execute JavaScripts. Rhino engine converts the script to a method inside a Java class. Therefore, when processing large JSON data volumes, the code length must be less than 65536 characters, since the Script mediator converts the payload into a Java object. However, you can use the following alternative options to process large JSON data volumes. The script mediator which is used in ESB is powered by the Rhino engine. Therefore, when processing large JSON data volumes, the code length must be less than 65536 characters which is a limitation in the script mediator being used in the esb versions less than 5.0.0. In ESB 5.0.0 there is a higher capability to process larger payloads using script mediator. In order to process such large payloads we can follow the below two approaches. 1. Replace the javascript tranformation logic using java code by writing a custom mediator. [1] 2. Break down the large payload and execute them as sections using
Post a Comment
Read more

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"                      class
1 comment
Read more

Exposing a SOAP service as a REST API

In this post i will be explaining how we can transform a SOAP based backend to receive requests in a restful manner through the WSO2 API Cloud. Steps. First log into the WSO2 Cloud and navigate to the API Cloud. In the API cloud select the option to add a new API. We will be creating an API to demonstrate an invocation to the backend soap service ws.cdyne.com/phoneverify/phoneverify.asmx?wsdl Give a name, context and version to the API and add a resource name with a GET Method. The resource name can be anything which you like since we will invoke the actual service usiing a custom sequence. Mention the URI template as indicated in the below screenshot. Next go to the implement tab. And select the endpoint type as HTTP/SOAP Endpoint and specify the endpoint as http://ws.cdyne.com/phoneverify/phoneverify.asmx. There is an important step we need to do here. We need to set the SOAP version for this request. In order to do that we need to select the advanced option for the e
2 comments
Read more