Cloud Blog

Category Archives: Integration Cloud

WSO2 Integration Cloud Launched

We have just launched WSO2 Integration Cloud Beta. This is a service that lets you host your:

  • Cloud-to-Cloud and Cloud-to-On-Premises integration projects based on WSO2 Enterprise Service Bus (ESB) and Data Services Server (DSS),
  • Proxy services,
  • API backends developed using the integration technologies, JAX-RS, JAX-WS, or Java microservices (MSF4J),
  • Java and PHP applications,
  • MySQL databases.

You can VPN your projects to your network or leave them on the internet. You can make the service URLs public (including your custom URLs) or hide them from the internet and only access them from other services and API gateway.

We have also published documentation and tutorials to help you get started.

The service is based on WSO2 App Cloud and inherits its functionality: if you had your projects and databases in App Cloud – they have all been safely migrated to Integration Cloud.

The service is currently in free beta but will launch commercially shortly – we are literally putting in place the last changes required to make it happen.

Try WSO2 Integration Cloud today and let us know what you think via blog comments or Support menu inside the service!

Adding more backend instances

In WSO2 Integration Cloud (formerly known as App Cloud), you can now easily add more instances to your applications and API backends. More instances mean both better performance and higher availability in case of failures.

To scale up your application, simply:

1. Click the application that you want to scale up,

2. On the application overview screen, in the Replicas section, click the Scale Deployment button:


3. Set the number of instances you want and click the Update button:


4. In the app’s overview, you can now see the additional instances and are able to click View Logs for any of them and see what is happening in this particular instance:

Application with two replicas

This feature is available both in trial and commercial accounts.

Whenever you hit the limit, there is a link that allows you to file a support case to get the limit increased.

Monitoring Resource Consumption

Integration Cloud is a great supplement to API Cloud providing scalable hosted environment in which you can host integration projects, backend services, and data services that your APIs need.

Today we are happy to announce a new feature that we have just added – Operational Dashboard that gives you current and historical information on the memory and CPU consumption of your code.

To access the charts, simply go inside your application and click Operational Dashboard – you will get charts for both RAM and CPU over the period of time that you select:


If your system is overloaded, you can then go back to the application settings and add more instances or pick a larger container size.


ESB-as-a-Service now available in App Cloud

You can now host your proxy services and integration projects right within WSO2 Integration Cloud (formerly known as App Cloud).

To do that, simply:

1. Export your WSO2 ESB project as a CAR file from WSO2 Dev Studio.

2. In WSO2 App Cloud, click Create Application.

3. Select WSO2 ESB Composite Application as the type:


4. Give it a name and upload the CAR file.

See our documentation for details: Deploy a Sample Integration Application.

Lock down access to services

WSO2 Integration Cloud (also formerly known as App Cloud) is frequently used in conjunction with API Cloud to provide backend microservices or integration proxy service implementation.

For such backend services, you need a way to cut off external traffic so that they are only accessible within WSO2 Integration Cloud and API Cloud but not to the public internet.

Today we are releasing an Integration Cloud feature that lets you selectively open or close public internet access to your applications.

To hide your application from the internet, simply:

1. Open the application in WSO2 Integration Cloud.

2. On the left-hand menu, click Settings.

3. On the Exposure Level tab, click Private:

Public private networking for applications

Once you click the Update button, the application will no longer be accessible from the internet. You will only be able to access it within WSO2 Integration Cloud and WSO2 API Cloud using the *.wso2apps.local URL.

What’s new in App Cloud

We’ve been busy improving WSO2 Integration Cloud (formerly also known as App Cloud), so in case you have not tried it lately, here is a quick summary of what we have rolled out recently.

Custom URL and Default Version

Not just designate which version of the application you want to be invoked by default, but also map a custom URL that you own (such as to it.

This was when you roll out a new release and want your users to switch to it, all you need to do is set that new version as default, and all the traffic will be routed to it:


See documentation for details.

Endpoint Information for Apps

We made endpoint information for application more useful.

For Java, PHP, and Jaggery, it is still just the URL (with the context to which you deployed):

Web app endpoint

For Java Microservices, we show the URL of the Swagger API definition for the exposed interface:

Microservices Swagger Endpoint

For Data Services, it is the WSDL definition of the exposed SOAP endpoint:

Data Services SOAP endpoint

Bulk Variable Upload

Instead of providing environment variable for your application one by one, you can upload them all as a JSON file:

JSON variables upload

Search by Tags

If you use tags for your applications or their versions (for example, tier:frontend), you can now search by them in the App Cloud home page with the tag: prefix (for example, tag:tier:frontend).

Faster Containers, More Options

We updated runtimes to the latest version (redeploy your applications to take advantage of them):

  • MSF4J 2.0.0 runtime for Microservices applications
  • WSO2AS 6.0.0 M3 runtime for Java Web applications
  • WSO2AS 6.0.0 M3 runtime for Jaggery applications

We changed Java runtimes to Alpine images to improve the start-up time and increase efficiency.

We added more container size options:

  • 128MB RAM and 0.1x vCPU
  • 256MB RAM and 0.2x vCPU
  • 512MB RAM and 0.3x vCPU
  • 1024MB RAM and 0.5x vCPU

If your project needs more resources just click the Support menu and let us know the details.

Tweaked Trial Limitations

We used to have a limit of 3 applications per free trial account. Now you can create any number of applications as long as you keep only 3 of them running. If your project needs more – just click the Support menu and let us know the details.

New Documentation

Check out the new features in WSO2 Integration Cloud today and let us know what you think!



May 31 Webinar on WSO2 Cloud Latest News and Roadmap

On Tuesday, May 31, 2016, I will be giving a webinar on the current state and future directions of WSO2 Cloud – our shared cloud service.

Cloud roadmap webinar sm

I will be demoing and talking about the latest updates to both API Cloud (to which we are finally adding API Monetization capabilities!) and Integration Cloud (that got a complete revamp, is now based on the docker/Kubernetes architecture, no longer has compatibility limitations, and besides Java also includes microservices and PHP).

I will also talk about the future roadmap including our Identity Cloud and Integration Cloud plans.

And I will be very happy to answer any questions that you have. This is a great opportunity for us to talk to learn more from each other.

Please register at the webinar page to reserve your spot: WSO2 Cloud Platform: Vision and Roadmap

App Cloud: New, Shiny, Docker-based

Today I am excited to announce that we have launched new generation of our application hosting platform – WSO2 Integration Cloud (also formerly known as App Cloud).

Unlike the earlier generation of the platform, new version is based on container (docker and Kubernetes) technology rather than WSO2 Application Server-based in-JVM multutenancy that we had earlier. This gives two huge benefits that our customers have been demanding:

  • Great application compatibility: your application gets a Tomcat, or Apache server, or WSO2 App Server container and is not sharing it with others, and thus does not have to conform to various security policies,
  • Broader runtime choice: with the new architecture it becomes easier for us to expand to a bigger set of supported runtimes. Besides Tomcat/WSO2 App Server-based Java, we already are offering microservices (MSF4J), and PHP, with more to come in the future.

App Cloud - New App Creation

Below is a quick FAQ about the launch:

What Can I Do With the New Integration Cloud?

Integration Cloud is application hosting platform, so you can:

  • Upload your Java (WAR package), PHP or MSF4J application from your file system or URL,
  • Get it running in selected runtime,
  • Scale up and down by changing the number of containers,
  • Upload new versions,
  • Create MySQL databases and store data there,
  • Create, store, copy, and modify environment variables.

When Will It Become Available?

It is available effective now.

How Do I Try It?


  1. Go to WSO2 Integration Cloud page and sign-up if you do not have an account yet, or Sign In (top right menu item).
  2. Pick Integration Cloud on the index page.

Is the Old App Cloud Still Available?

Yes, if you still have your application and data inside the old App Cloud, you can get to it by clicking the corresponding link at the top banner in the new App Cloud.

We will keep the old App Cloud running in parallel to the new App Cloud until May 15, 2016 – so please make sure that you migrate everything by the end of the month.

How Much Does It Cost?

WSO2 Integration Cloud is in free beta.

How Do I Provide Feedback or Get Help?

Click the Support menu inside App Cloud and we will get back to you!

Try the new WSO2 Integration Cloud today and let us know what you think!

Adding Administrators to Your WSO2 Cloud Organization

We have added the ability to invite more administrators to your organization in WSO2 Cloud.

This way you delegate all the permissions that are there in WSO2 Cloud including all possible configuration rights, billing, and ability to invite new team members.

To add another administrator:

1. Click the Members menu:

Members menu

2. In the Members screen, click the Invite Members button.

3. In the Member List box, type the email addresses of the users you want to invite,

4. From the Member Roles drop-down list, select Common / Admin:

Pick admin role

5. Click the Invite button.

The users you invite, will receive an email with one-time link that they will need to click to join your organization and get administrative permissions.

Try it yourself in WSO2 Cloud today.

Your own JAX-RS as an OAuth Web API in Minutes!

UPDATE: This is an outdated post. WSO2 App Cloud has been since then replaced with WSO2 Integration Cloud and App Server in it with Tomcat. General principals still apply and JAX-RS is a supported backend implementation in the Integration Cloud. Click Support inside the Integration Cloud UI if you need help.

We’ll be using WSO2 Application server in Cloud to host a secured JaxRS service. A future post will explain how to do it with Tomcat, but this post is written for WSO2 App Server.

After writing the JAX-RS service we are going to protect it using OAuth with several clicks. Then you’ll be able to,

  1. Access to the back-end JAX-RS service will be OAuth protected
  2. Advertise the API in an API store for the world to see
  3. Access to the back-end JAX-RS service will be throttled
  4. Allow people to subscribe to these APIs

This is the high-level diagram,

Step 1 – Adding security to the JAX-RS service in App Cloud

Step 2 – Expose it as an OAuth protected API

Step 1 – Adding security to the JAX-RS service in App Cloud

Here I am going to add security to my JAX-RS service by introducing the following lines to the web.xml. As you can see this is plain Tomcat based security. And you have not defined a Realm here. I will explain what happens to the realm below.



Now only the people in admin role can call this service. If you are familiar with Tomcat security, the question is: where is the realm and is the role coming from? It is coming from the Cloud user store.


We have simplified a lot of security related details in WSO2 Application Server. Now let’s try to invoke it using a REST Client.

 curl -v -H   
 "Authorization: Basic Base64_encoded_String_of_your_Username:Password  

The trickiest part is figuring out the username. The “@” sign in the email address must be replaced with a “.”  and the tenant domain must be appended with the “@” sign. == becomes ==&gt;  

Here “perftest” is my tenant domain name.

Next, remember to turn off “http” from transports.

Step 2 – Expose it as an OAuth protected API from API Cloud

Now go into API Cloud and publish the JAX-RS as a service.

Add the proper resource URL patterns and end points. In my case I am going to add “customerservice/customers/{id}” as the url pattern and endpoint of the service as the endpoint. In my case, it is something as follows,

Give the username/password to access it.

Screen Shot 2015-08-24 at 1.49.35 PM

Woala you are done! Now you have an API in the store, that is accessible the whole wide world!


Recent Posts

Most Popular Posts