Posts tagged REST
Times Up! — Deciding What to Do As Standard Maintenance Ends with DataPower

We’re now at the end of standard maintenance on several DataPower SOA appliances. And that probably means most companies who haven’t yet upgraded are buying extended support, because you don’t just replace appliances for important applications — you test and deploy over many months so that you don’t put the business at risk. If you’re in this situation, use the next 1-2 years wisely to rightsize DataPower, and break the vicious spending cycle.

When it comes to appliances, many companies buy excess capacity up front to support several years of growth. Often it’s because they don’t want to be forced to do an early upgrade or add-on purchase. Most are convinced they will use the extra capacity for other projects. And this is the vicious cycle. Companies end up putting applications on DataPower that just don’t belong there. DataPower is great as an XSLT acceleration engine, but that’s mostly it, and that “data power” comes at a big cost. Don’t keep loading up DataPower. Start to evaluate which applications don’t belong there, and start to implement your rightsizing program now. Then, buy the right size of DataPower for what’s left.

Reevaluate all new projects and see what can be moved to another platform before you put it on DataPower. Any integration across a firewall or across divisions can probably be done using an API gateway. The right API gateway will have native wire-speed integration with DataPower that makes it easy to add it to a DataPower deployment, migrate workloads, or add functionality to other deployments.

Finally, build out your roadmap for migrating existing functionality that can or should be run on other platforms, either during release cycles for the applications or as part of a larger initiative. Some of the more common reasons for moving to an API gateway are:

  • A move to virtualization or an outsourcing strategy. DataPower isn’t designed to run on a third-party virtualized infrastructure such as VMware or Amazon AWS.
  • A need to support cloud and mobility. DataPower supports XML. It’s not good at supporting the new world of JSON and REST.
  • Productivity. DataPower requires developers to code in XSLT. A modern API gateway is a highly graphical environment, where developers configure, not code.
  • Native support for Java or JavaScript. DataPower doesn’t support either.
  • Antivirus protection and security concerns. DataPower requires an ICAP connection to add anti-virus protection, which adds an extra network “hop” and a delayed response. The right API gateway supports antivirus in-process and a host of security measures for hardening access from outside the firewall.
  • Identity bridging. DataPower does not directly support bridging OAuth, Oracle Identity Management, CA SiteMinder, or even Tivoli as well as a quality API gateway that delivers federated identity management and single sign-on (SSO) across the old and new channels.

So build your roadmap now. Start by identifying the strengths and weaknesses of DataPower and evaluate each application it supports. Get advice from others who have used API gateways with DataPower. Use some of the money that had once been earmarked for extended support — and extra capacity — to work on new projects that make a difference to the business.

 

Give ‘em the Keys: How Essent Unlocks Information for its Customers

When the leading producer of sustainable energy in the Netherlands, Essent, chose to enable internet and mobile-app services for its users, they quickly realized an API gateway was a must.

But what was wrong with the security applications they’d been using to manage their web services all along?

Plenty. The company couldn’t provide web services for its customer-facing portals, its security applications weren’t robust, they didn’t have SAML 2.0 support, and maintaining their environment wasn’t as cost-effective as it could’ve been. They knew they needed a web services API, capabilities around REST, XML, SOAP, and data handling, and the ability to integrate their enterprise service bus using XML over JMS.

In short, they knew that an API gateway would be the starting point for unlocking information for their customers.

And today, Essent’s reaping the benefits.

Essent’s customers can now manage their utility contracts online using the Customer Self-Service Portal, which contains 140 web services and offers end-to-end self-service capabilities.

Essent’s customers can download mobile applications from the iTunes App Store and Google Play, log onto the company’s back-end systems, and retrieve and modify their information — all within an environment secured by an API gateway.

And the innovations just won’t stop. An API gateway is giving Essent the ability to develop groundbreaking, previously unfeasible services. Customers will soon be able to:

  • Access their accounts via Facebook or Twitter
  • Pay their bills via the domestic banking community’s iDEAL payment method
  • Optimize their energy use by sharing smart-meter data directly with Essent via the internet

Discover now how you can take a cue from this innovative organization and bring the fruits of their API-gateway journey into your enterprise. Download the case study today!