CA Technologies, a provider of software for the application economy, has added RAML support to the latest release of the CA API Developer Portal. Interactive documentation and an API Explorer entry can now be generated using a RAML API description file. Other key features added to the latest version of the platform include SOAP support and SoapUI integration.
The CA API Developer Portal is an enterprise-focused solution for exposing backend systems as APIs and providing developers with tools to build applications from those APIs. Enterprises can use the platform to create tools for developers such as interactive API documentation, localized developer portals, integrated explorer for testing API functionality, API client libraries, single sign-on (SSO), social login capabilities, and more.
CA API Developer Portal 3.1 now features RAML support, SOAP support, and SoapUI integration. The platform allows users to create interactive API documentation from industry-standard WADL files, which now includes RAML. In addition, the CA API Developer Portal now supports SOAP; users can publish and manage SOAP services using the Portal without having to publish SOAP services on the API Gateway beforehand. Another new feature added to the platform is a plugin that allows developers to directly access Portal WADLs and WSDLs from within SoapUI.
ProgrammableWeb reached out to Dana Crane, senior product manager at CA Technologies, who provided additional information about CA API Developer Portal 3.1. Crane told ProgrammableWeb that CA Technologies has always had a policy of being both vendor-agnostic and standards-based. This is because companies today are working with a wide range of APIs and definition formats, some of which are accepted standards (like SOAP), and some of which are emerging (like RAML).
Regarding SOAP support, Crane explained that prior versions of the CA API Developer Portal required that SOAP services had to be published on the API Gateway first before they could be used in the Portal. This two-step process was causing a bottleneck for customers because many had only a few Gateway administrators with API publishing authorization. Allowing users to publish and manage SOAP services directly from the Portal eliminated this bottleneck.
Regarding RAML, Crane explained that “there are many emerging API definitions, but when we looked at RAML, we saw a format that’s (almost) human-readable, and strongly supports defining virtual APIs through request/response pairs and examples. This simplifies the creation of sandboxes using mock APIs, either directly on the API Gateway, or through other CA applications like CA Service Virtualization or VAPI.”
Crane further explained that before the release of CA API Developer Portal 3.1, most customers exposed their pre-built APIs. The addition of RAML support to the platform allows customers to utilize an API format that promotes mocking first; getting input from developers and partners and then building APIs that meet customers’ requirements.
There are quite a few API description languages available today including API Blueprint, I/O Docs, RAML, and Swagger. CA Technologies plans on adding Swagger support to CA API Management products and services, including Portals and Gateways, in the near future.
“Security and adaptability are critical elements when it comes to delivering new apps and services to the market in a timely manner. API Management solutions, like those from CA, give organizations the tools and resources they require to transform their closed businesses into open enterprises based on agile apps,” said Crane. “This allows them to move as nimbly and quickly as their smaller, more disruptive competitors because their enterprise resources can now be made widely available on emerging platforms, and across a range of new devices — all of which can help address new markets.”
Disclosure: MuleSoft, parent company to ProgrammableWeb, is a competitor to the company mentioned in this article.