We are announcing the retirement of the Watson Document Conversion (DCS) and Watson Retrieve and Rank (R&R) services. Current users can take advantage of the evolved capabilities in these services by switching to Watson Discovery.
Today, we're proud and excited to announce the general availability of the IBM Lift CLI. Over a short amount of time, our users migrated tens of terabytes to our enterprise cloud data warehouse service, Db2 Warehouse on Cloud. In the meantime, our engineering team has been working hard putting in the final touches and even cranked out a couple of new features.
Do you have a modernized WebSphere application in your business running on your on-premise infrastructure? If you’ve migrated your old application code to the present-day WebSphere Application Server (WAS) version and updated your development environments / delivery pipelines to modern practices, it’s time to move your application to the WebSphere Application Server as a Service. In the last blog entry, we explained how you can modernize your existing WebSphere applications with minimal changes and migrate them to the cloud, lowering your costs and simplifying maintenance. This blog entry, we'll cover how to iteratively moving core pieces of compute-based business logic to cloud-based services.
Do you have existing monolithic Java/JEE applications running on WebSphere Application Server? Is your application comprised of multiple business functionalities, but it’s packaged as a single application? Are there performance bottlenecks that you are not able to resolve because the application does not scale well? If you answered yes to any of these questions, read this post to learn how you can refactor your existing monolithic WebSphere application into a microservices-based application.
In our last post, we took high-level view of our process for moving WebSphere applications to the cloud. In this entry, we'll look closely at the tools that help you with the first step, modernizing your existing WebSphere application.
Earlier this year, the wsk api command was introduced as the replacement for the wsk api-experimental command. The wsk api-experimental command is now deprecated and will be withdrawn at the end of July, 2017. On August 1st, all APIs created with the wsk api-experimental command will be removed.
Unless you are a start-up, you have existing applications. While sometimes you build net new apps, other times you may lift and shift an application to the cloud or simply leave it where it is and leverage services from the cloud, like Watson. Bluemix provides a suite of services and tools to help you from various entry points
Using Azure Android Push Documentation as a starting point, this blog will guide you through the steps to migrate your existing Azure push notification enabled Android application to use Push Notifications on Bluemix.