Community

Services Changes with Bluemix General Availability

Share this post:

As you’ve probably heard by now, we are very excited to announce that the Bluemix platform is now officially available as a commercial offering. As part of this announcement we’ve introduced new IBM and 3rd party services, updated our UI and docs and perhaps most importantly, introduced pricing.

You can read all about that announcement on the Bluemix blog.

In addition to these platform changes, many of our services are going through changes as well, and some of these changes may require actions from you. Some examples of this include:

    -Some beta services need to be replaced by their GA counterparts
    -Some beta services require you to move the SDK or data to the GA version
    -Certain services are being transitioned into new services

If no special instructions are included in this post, it means no action is needed from you at this time.

If you are currently using the beta services require migrations, you will see both beta and GA versions at GA. Although you will not be able to create new instances using the beta version/obsolete services once we go GA. We are including a two week grace period for the migration and transition, and we will delete most beta services on July 15th. SQL database service will be deleted on July 30th. (Special instructions for database services are provided below).

Here’s the entire list of impacted services and what you need to do if you are using these services today.

Mobile Data

You need to move to the GA version of the SDK. Here are two blog posts about the steps you need to take.
/blogs/bluemix/2014/06/25/whats-new-mobile-cloud-june/
/blogs/bluemix/2014/06/25/migrating-mobile-cloud-client-applications-beta/

Mobile Quality Assurance

The existing MQA beta is also coming to a conclusion. You can read more about the implications of this change and ask questions in our Q&A on this topic: https://developer.ibm.com/answers/questions/15904/ibm-mobile-quality-assurance-open-beta-is-ending-soon/

Single Sign On

If you are using our existing SSO service, it will be migrating to a new service and configuration model. You will need to unbind your current instance and re-bind to the new one. You can find detailed instructions for how to make this change here: https://idaas.ng.bluemix.net/idaas/doc/sso_migration.jsp

Monitoring and Analytics

We have introduced new Log Analysis capabilities to the Monitoring and Analytics add-on in the Bluemix Beta. The Monitoring and Analytics add-on will replace the existing Log Analysis service you are using to manage Liberty and Node.js runtimes.

Please be aware that the look and feel of this new Log Analysis solution will be different and you will need to re-create your current searches to take advantage of the new features.

Required Actions

    1. At this time, the Log Analysis service remains bound to your applications. It has been made private and cannot be bound to any new applications. The Monitoring and Analytics add-on with log analytics capabilities is now available in the Bluemix beta; please transition your runtimes to this add-on as soon as possible. Note that your runtimes cannot be bound to both the Log Analysis service and Monitoring and Analytics add-on at the same time.
    2. On July 15th, only the Monitoring and Analytics add-on will be available in Bluemix. The existing Log Analysis service will be removed. At this point you have to bind your runtimes to the Monitoring and Analytics add-on if you have not already.
    3. Follow the instructions below to bind to the new add-on

Instructions for switching from the current LogAnalysis service to the new Monitoring and Analytics:

Node.js Instructions Liberty Instructions
Unbind the LogAnalysis service from your application Unbind the LogAnalysis service from your application
Create an instance of the Monitoring andcAnalytics add-on Create an instance of the Monitoring andcAnalytics add-on
Bind the Monitoring and Analytics add-on to your application Bind the Monitoring and Analytics add-on to your application
Install the Node.js-SCALA Data collector using the following command:
npm install loganalysis
Re-push your application
Add the following line of code in the start script of your Node.js application:
require(‘loganalysis’);
Re-push your application

Other Information

We are implementing this change to provide you with more capabilities to help better manage your development and operations efforts. Benefits of these changes include:

    1. With a single add-on, you get both monitoring and log analysis capabilities to better detect and diagnose application problems

    2. Get more value out of your log analysis solution with the following additional capabilities:
    · A consolidated view of the performance and availability of your applications based on monitoring metrics and logs.
    · The ability to search and visualize log data with out of the box support for applications on Liberty and Node.js runtimes.

Please be aware that the look and feel of this new Log Analysis solution will be different and you will need to re-create your current searches to take advantage of the new features.

Rules

Rules is being upgraded to a new version. You will be required to unbind the current service instance and create a new one. Once the new instance is provisioned, you can bind this instance to your application and redeploy your rule Apps. You will need to update your Rule Execution Service Configuration in the Rule Designer IDE with the new Riles service endpoint and credentials. The Rules service will still be in beta.

Cloud Integration and Cast Iron Live

The Cloud Integration and Cast Iron tabs will now become one and the same. As all the work you have performed during the Beta stage resides on the Cast Iron servers, only one small change is needed at this time.

To the support the workload entailed by transitioning from Beta to GA, we will be migrating all backend orchestrations to production level tenants. As a result, all secure connectors previously created will need to be recreated in the GA environment.

Moving forward you will be able to use the “Create Integration” option from the Cloud Integration tile in order to log into either the Cast Iron live Evaluation or Production console.

Analytics Warehouse (previously called Blu Acceleration)

If you are a consumer of the BLUAcceleration service please note that a new, upgraded version of this service called Analytics Warehouse has been introduced. The beta version of the service has been discontinued and all existing instances of the BLUAcceleration service will be de-activated on July 15.

Migration Instructions

    -The service has been renamed – from BLU Acceleration to Analytics Warehouse
    -The OpenBeta plan has been discontinued and a paid Small plan with a free-tier has been introduced
    -To use the GA version of the service you will need to provision new instances of the Analytics Warehouse service
    -Data and instances will not be automatically migrated from Beta to GA. Please load data into the GA instances directly.
    -Extract any data you require from the beta instances of the service before July 15 as the beta instances will not be accessible thereafter
    -Applications connecting to beta instances of the service will need to be unbound and bound to the GA instances
    -Any new instances of the service you provision will have new database names, schema names, and user credentials, therefore be sure to update your applications with the new connection and schema information provided in the VCAP_services.

If you require any assistance in transitioning to the GA version of Analytics Warehouse service, you may post in the developer community or contact us at IM_Cloud_DevOps@wwpdl.vnet.ibm.com

SQL Database

As we move to GA the current SQLDB Open Beta program will come to an end. Existing SQLDB databases on the Open Beta program will be deactivated on July 15, 2014, and deleted 2 weeks later.

Migration Instructions

Old services instances will be discontinued, users need to create new service instances. So no unbind/rebind, but entirely new databases. Unfortunately there currently is no easy way for customers to export their data from databases of the existing open_beta plan. Users need to contact IBM if they want their data migrated. For simple cases users can use a sample program to export a table at a time, available in JazzHub here: https://hub.jazz.net/project/pvanrun/SQLDBCSVExport/overview and then import into the new database using the CSV import in the SQLDB Console

Additional Information

There will be a GA SQL Database service with a Small Plan in the Bluemix catalog, which is comparable to the Open Beta service. We encourage you to try out this new SQL Database service. It allows for free databases up to 2GB in size with 1 GB of memory and a maximum of 20 connections per database. It also scales to support larger volumes, available for a monthly fee. For further details on the Small Plan and to get started see this link. We’re committed to making your transition easy, so please contact us with any questions regarding the new SQL Database at IM_Cloud_DevOps@wwpdl.vnet.ibm.com

Cloudant NoSQL DB (previously called Cloudant JSONDB)

As we move to GA the current Cloudant JSONDB Open Beta program will come to an end. The existing Cloudant JSONDB databases will continue to be accessed on Cloudant.com. There will be a GA Cloudant NoSQL Database service with a Shared Plan in the Bluemix catalog, which is comparable to the Open Beta service. We encourage you to try out this new Cloudant NoSQL Database service. It allows for free databases: up to 2 Gigabytes, no more that 10,000 Heavy API calls and no more than 50,000 Light API calls. It also scales to support larger volumes, available for a monthly fee. For further details on the Shared Plan and to get started see this link. We’re committed to making your transition easy, so please contact us with any questions regarding the new Cloudant NoSQL Database at IM_Cloud_DevOps@wwpdl.vnet.ibm.com

Migration Instructions

    -To use the GA version of the service you will need to provision new instances
    -Data and instances will not be automatically migrated from Beta to GA. Please load data into the GA instances directly.
    -Extract any data you require from the beta instances of the service from cloudant.com directly
    -Applications connecting to beta instances of the service will need to be unbound and bound to the GA instances
    -Any new instances of the service you provision will have new database names, schema names, and user credentials, therefore be sure to update your applications with the new connection and schema information provided in the VCAP_services.

Time Series Database

As we move to GA the current Time Series Database Open Beta service will come to an end, and existing databases will be deactivated on July 15, 2014. Kindly extract any data you require from the beta instances of the service before July 15 as the beta instances will not be accessible thereafter. There will be a GA version of the Time Series Database service with a Small Plan in the Bluemix catalog, which is comparable to the Open Beta service.

Migration Instructions

Applications connecting to beta instances of the service will need to be unbound and bound to the GA instances.
Any new instances of the service you provision will have new database names, url, and user credentials, therefore be sure to update your applications with the information provided in the VCAP_SERVICES.

If you require any assistance in transitioning to the GA version of TimeSeries Database service, you may post in the developer community or contact us at IM_Cloud_DevOps@wwpdl.vnet.ibm.com.

More stories
May 7, 2019

We’ve Moved! The IBM Cloud Blog Has a New URL

In an effort better integrate the IBM Cloud Blog with the IBM Cloud web experience, we have migrated the blog to a new URL: www.ibm.com/cloud/blog.

Continue reading

April 30, 2019

Introducing IBM Analytics Engine v1.2 and Announcing the Deprecation of IBM Analytics Engine v1.0

We are excited to inform you about the new version of IBM Analytics Engine v1.2 that will be available starting May 15, 2019. Along with this release, Analytics Engine v1.0 will be retired.

Continue reading

April 23, 2019

Announcing the Deprecation of the Watson Machine Learning JSON Token Authentication Service

We’d like to inform you about the deprecation of the Watson Machine Learning JSON Token Authentication service. This method of authentication will be retired on May 30, 2019.

Continue reading