On April 3, 2015, we made the IBM API Management for Bluemix (APIm) service generally available (GA). This version will replace the Beta that you may be using presently. We will sunset the Beta service at the end of April, so there are a few items you will need to complete in order to move from the Beta service to the new and improved GA service! Those steps are provided below along with step numbers which correspond to the Getting Started with API Management tutorial.
Changes required before the end of April:
Provision a new API Management service instance from the Bluemix catalog. (Step 1) Note the new pricing models for the GA service. (Step 1.4)
Recreate your APIs and rate plans in the new API Management instance. (Step 2 & 3)
Republish your APIs to Bluemix. (Step 5)
Bind the published API to any of the apps that previously used the Beta APIs. (Step 6)
Test the API to ensure everything is working well. (Step 7)
Unbind your old APIs from your apps, and unpublish the old APIs from the Beta APIm service instance.
Delete the API Management beta service instance.
To differentiate the Beta provisioned organizations from those provisioned in the GA version, please note that an organization provisioned in the GA service will have the Bluemix space it was deployed from in parenthesis, whereas those provisioned from Beta will not. For example:
GA – email@example.com (dev)
Beta – firstname.lastname@example.org
If you have any questions while going through these changes, feel free to post on the Bluemix forum, using the tag: APIm-Bluemix.
The IBM Bluemix Container Service combines Docker and Kubernetes to deliver powerful tools, an intuitive user experiences, and built-in security and isolation to enable rapid delivery of applications all while leveraging Cloud Services including cognitive capabilities from Watson. The service launched initially in US South (Dallas) and EU Central (Frankfurt). As the IBM Cloud continues to expand our datacenter scope, the container service is expanding as well. The container service is now available in the Sydney and London regions.
Almost a year ago, when we first announced and released IBM Globalization Pipeline on Bluemix, we were looking to solve a simple problem facing Bluemix development teams wanting to expand into global markets -- how can Cloud dev teams translate their applications into different languages without impeding continuous delivery and disrupting DevOps?
In answer, we delivered Globalization Pipeline -- a Bluemix service that enables developers to integrate translation processes into their build and deploy infrastructure and translate their apps using machine translation. Think integration with IBM DevOps services, UrbanCode Deploy, Continuous Delivery, Maven, VS Code, and Atom, think Watson Language Translator, think client SDKs for dynamic app translation updates.
We’ve launched four new global data centers: two in London and one each in San Jose and Sydney. IBM is expanding its cloud footprint to meet enterprise demand—and upping our combined data center count to 59 across 19 countries. Get access to high performance and cognitive services Handling big data workloads with high performance is […]