Cloud Blog

All posts by Dmitry Sotnikov

Dmitry Sotnikov is Vice President of Cloud solutions at WSO2.

Prior to WSO2, Dmitry worked at Quest Software (now part of Dell) as Director of Cloud Solutions, and later co-founded Jelastic PaaS and led Jelastic’s sales, marketing, customer and partner relationships. Dmitry has been a featured speaker at multiple industry events including Microsoft TechEd, VMware VMWorld, Parallels Summit, Quest Innovate, and Technology Experts Conference (TEC).

API Gateway Default Ports are now 80/443

When WSO2 API Cloud launched initially, by default API Gateway was exposing APIs on ports 8280 and 8243. For customers with firewalls blocking these ports, this led to calls failing with { "error": "no response from server" }.

The workaround that we had for this was using Custom URL functionality – which changed both the Gateway URL and ports.

Now we made things even better, and no workarounds are required anymore:

From now on, default network ports for API Gateway are the standard port 80 for HTTP and port 443 for HTTPS – so things just work with no extra configuration required:

Default ports in WSO2 API Cloud

Note: for backward compatibility we will keep the old ports 8280 and 8243 also available for another couple of weeks. However, as we will be decommissioning their support in the future, all customers are advised to switch to ports 80/443.

Try the new functionality in WSO2 API Cloud now!

API Cloud Interactive Tutorial

Too busy to read documentation or watch videos? No worries, WSO2 API Cloud now has interactive step-by-step tutorial that leads you through publishing your first API (based on the countries data from the World Bank) and invoking it from API Store:

Interactive walkthrough tutorial for WSO2 API Cloud

Friendly callouts tell you where to click and what to type – so within a couple of minutes you get a pretty good understanding on how API design, publishing, and subscriptions work!

If this is the first time you log into API Cloud, the tutorial will start automatically.

Already have an account? No worries, you can always start the tutorial manually from Documentation menu:

Documentation - API Cloud Walkthrough menu

Your first published API is just a few minutes away! Sign up for a free trial or log into your existing WSO2 Cloud account, and give it a try!

[Video] Setting up custom URL for API Store and Gateway

Your company URL is an important part of your developer community experience. There are two scenarios in which subscribers see URLs and both are supported by WSO2 API Cloud:

  • The URL under which the API Store (developer portal) is available,
  • Gateway URL that is the base URL for your APIs.

Customizing them follows the same pattern:

  1. Map CNAME record for your custom URL to API Cloud custom DNS endpoint: customdns.api.cloud.wso2.com,
  2. Configure API Cloud to accept these URLs and upload SSL certificates.

We have created a quick video that shows the entire configuration process including creating CNAME records and obtaining SSL certificates:

If you prefer to read a step-by-step tutorial, you can find it here.

Start your free WSO2 API Cloud trial today.

Custom API Publisher Info for Your APIs

Your subscribers need to know who is behind the APIs that they consume. Depending on your scenario, you might want to set the API owner information to the individual who published the API, a particular team in your company, or just the company itself. WSO2 API Cloud lets you easily implement any of these approaches.

By default, API Store will display the internal name of the individual who published the API:

Annotated-publisher-as-individual

To change it to your team name or company name, simply provide the proper name at the last step of API editing wizard:

Provide API owner information

Once you publish the API with the owner information filled in, API Store starts reflecting the new owner information in the user interface:

Customized API business owner

This is just one of the ways you can control your branding and the way your subscribers see your company.

See also this post on changing API Store styles, logos, and URLs.

Get your free 2 week API Cloud trial today!

The Power of Mediators: API Call Transformation and Orchestration

Sometimes you are lucky and the backend web services match exactly your desired public API design. But what if they do not? What if you need to change formats on the fly? Or do XSLT transformation? Or orchestrate multiple backend services called and joined into a single API?

Fear not! WSO2 API Cloud comes with a powerful mediation engine that can transform and orchestrate API calls on the fly.

You can create your mediation sequences and apply them on the fly both on the way to the backend (In Flow) and back to the invoker (Out Flow):

API Cloud mediation sequences

API Cloud’s mediation engine is built on industry-fastest enterprise service bus (ESB) engine and supports amazing variety of mediators that you can use as building blocks for your sequences: https://docs.wso2.com/display/ESB490/Mediators

WSO2 Developer Studio can then be used to build your sequences:

Sample mediator sequence

And then you simply upload the sequences to the gateway and select which of them you want used in your APIs.

There are a couple tutorials that we published to illustrate the process:

Using Property Mediator to turn YQL-based Yahoo Weather API into nice REST format:

This is the step-by-step tutorial if you want to follow along: https://docs.wso2.com/display/APICloud/Change+the+Default+Mediation+Flow+of+API+Requests

And here is another one on turning a SOAP backend into a proper JSON REST frontend API.

Here’s the full list of mediators supported and links to detailed documentation:

Category

Name

Description

Core Call Invoke a service in non blocking synchronous manner

Sequence

Inserts a reference to a sequence

Drop

Drops a message

Enrich

Enriches a message

Property

Sets or remove properties associated with the message

Log

Logs a message

Filter

Filter

Filters a message using XPath, if-else kind of logic

Validate Validates XML messages against a specified schema.

Switch

Filters messages using XPath, switch logic

Conditional Router

Implements complex routing rules (Header based routing, content based routing and other rules)

Transform

XSLT

Performs XSLT transformations on the XML payload

FastXSLT Performs XSLT transformations on the message stream

URLRewrite

Modifies and rewrites URLs or URL fragments

XQuery Performs XQuery transformation

Header

Sets or removes SOAP headers

Fault (also called Makefault)

Create SOAP Faults

PayloadFactory Transforms or replaces message content in between the client and the backend server

Advanced

Cache

Evaluates messages based on whether the same message came to the ESB

ForEach Splits a message into a number of different messages by finding matching elements in an XPath expression of the original message.

Clone

Clones a message

Iterate

Splits a message

Aggregate

Combines a message

Callout

Blocks web services calls

Transaction

Executes a set of mediators transactionally

DBReport

Writes data to database

DBLookup

Retrieves information from database

Entitlement

Evaluates user actions against a XACML policy

Extension

Class

Creates and executes a custom mediator

Script

Executes a mediator written in Scripting language

Start your free API Cloud trial now!

Meet WSO2 Cloud Team at WSO2Con US

WSO2Con-US-2015

In less than 2 weeks, we are hosting our main event of the year in the US – the annual WSO2Con in San Francisco, November 2-4. Along with the sister conferences in Europe and Asia, this is the main opportunities for us to meet the community of WSO2 users and partners, share roadmaps, and exchange ideas.

A lot of the WSO2 Cloud team members will be there and there are a lot of great sessions in the agenda.

There is a great session from our cloud technical leads: Amila and Chamith – on how we do DevOps for both public and managed cloud customers:

Amila-Chamith

Myself and Imesh will talk about private cloud deployments, Kubernetes, Docker, and application PaaS technologies from WSO2:

Dmitry-Imesh

I will cover WSO2 Cloud roadmap:

Dmitry

Imesh demonstrate multi-cloud container deployments:

Imesh

Lakmal talk about the results of the recent big data in the cloud hackathon:

Lakmal

And finally Amila and Chamith provide details on cloud high availability and automation:

Amila-Chamith-2

Plus, there will be many sessions on IoT, API Management, Integration, Security, and other hot topics of IT today.

There are still tickets available, so buy yours today, and we will see you in San Francisco the first week of November!

Prototype API in JavaScript in 2 Minutes

Successful companies try things fast, get feedback and iterate – and successful API programs are no exception.

WSO2 API Cloud makes prototyping a new API and running it by your users to collect feedback extremely easy.

All you need to do is:

  1. Define your API: list REST resources and parameters (either in our New API wizard or by importing or editing Swagger definition),
  2. Provide API definition

  3. On the second step of the wizard, pick the Prototype option and Inline to get JavaScript editor displayed with stub implementation in it,
  4. 2-inline-Javascript-prototype

  5. Modify the stub for each HTTP method you need to implement with your custom JavaScript code.
  6. 3-JavaScript-implementation-with-xml-output

  7. Deploy the prototype to your API store: your developers will start seeing the API, be able to invoke it, provide feedback, and so on.

Prototypes can also have versions so you can iterate on your prototypes as your vision evolves, and then substitute the implementation with real backend.

Here’s a video of the whole process – it literally takes less than 2 minutes!

And here’s the detailed tutorial.

Sign up for your free trial of WSO2 API Cloud now, and happy API programs!

99.99% – WSO2 Managed Cloud SLA Goes to Four Nines

99.99 - Guaranteed Uptime for WSO2 Managed CloudWSO2 Managed Cloud – our dedicated hosting offering – just got an upgrade. From now on, all Managed Cloud customers get financially backed 99.99% guaranteed uptime.

This is, of course, in addition to formal SLA on support ticket responses and all other niceties of the service:

  • Available for any combination of WSO2 products,
  • Run in the region of your choice on dedicated virtual machines not shared with any other customers,
  • WSO2 engineers set up the environment including the virtual machines, WSO2 products, and networking,
  • Can be set up to have network connectivity with your on-premise datacenter,
  • Deployment can be customized for your specific needs,
  • Can be combined with professional services including consultancy, development, and QuickStart,
  • Includes full devops service including 24*7 monitoring, regular backups, and product updates,
  • Priced as a fixed monthly fee.

You can find full updated SLA for WSO2 Managed Cloud at: http://wso2.com/cloud/managed/sla.

Fill out the form at the right side of the SLA page to get more information and sign up!

[NEW] API Cloud Custom URL for API Store and Gateway

API programs are key to building the ecosystem around your technology. Your developer portal and APIs represent who you are to your partners and customers. This is why branding is very important part of API efforts.

Branding for API programs consist of:

  1. Your own custom URLs for developer portal and APIs,
  2. Your logos, style, look and feel of the developer portal.

With the addition of custom URL functionality, WSO2 API Cloud now supports both kinds of customization.

1. Custom URL

By default, API Store for your subscribers gets a URL that looks like https://api.cloud.wso2.com/store/?tenant=[your organization id], and the APIs themselves start with https://gateway.api.cloud.wso2.com:8243/t/[your organization id]/.

My guess, is that instead, you would like a fully branded experience with API Store being available at something like http://developers.mycompany.com and APIs at http://apis.mycompany.com.

Now all you need to do get there is:

  1. Come up with the nice URLs for both the API Store and the API gateway (and purchase the domain if you have not done so),
  2. Purchase SSL certificates for both domains (this is required because both portal and APIs themselves need to be accessed via HTTPS),
  3. In your domain registrar’s DNS panel, create CNAME records pointing to customdns.api.cloud.wso2.com for APIs themselves, and customdns.api.cloud.wso2.com for the developer portal,
  4. In WSO2 API Cloud, click the Custom URL menu and follow the configuration wizard.

Application overview page in WSO2 App Cloud

You can find detailed instructions in this tutorial: Customize the API Store and Gateway URLs.

2. Custom styles

Obviously, URL is just your first step. You also want the API store itself to be branded with your own corporate logos and styles.

This is as easy as taking our sample store theme, substituting the logos and any other graphics you want changed, and making proper changes to the CSS files.

Here’s a quick demo of the process:

And a link for step-by-step tutorial: Customize the API Store Theme.

Sign-up for a free trial of WSO2 API Cloud today!

[Video] Analyzing API Statistics and Blocking Rogue Subscribers

WSO2 API Cloud has all you need for successful API program. This means that besides just publishing your APIs and opening subscriber portal, you need to have detailed analytics reports to see the actual subscriber behavior and be able to block the subscriptions that do not comply with your policies.

We have published a couple of quick demos to show how this works.

Some of our out-of-box API analytics reports:

And here’s a quick video of how individual subscription can be easily located and suspended:

Start your free API Cloud trial today!

Categories

Recent Posts

Most Popular Posts