This is the first post in a series on how to move your team towards the best long-term cloud platform adoption decision. Since adopting a cloud platform involves a significant commitment, and implies the confirmation that comes from previous work on one or more pilot projects, the primary goal of this series is to get you to the step of defining an appropriate cloud-based pilot project for your team.
With many traditional workloads moving to cloud-based infrastructures, now is the perfect time to assess your existing Java-based workloads and migrate them to WebSphere Application Server on IBM Bluemix. More commonly known as “WAS on Cloud”, this service provides a fully-configured, turn-key WebSphere-based application environment, supporting both Traditional WAS and Liberty applications. You use your same tried & true wsadmin automation scripts, same CI/CD techniques, but just point them at Bluemix instead of your own infrastructure! This post summarizes the steps from WAS to the cloud.
Instead of hard-coding or manually passing in environment variable parameters from the command-line, developers can dynamically and programmatically bind service instances to container instances on Bluemix using IBM Containers. This how-to shows you one way to access the bound service information when you need it prior to the main Docker executable starting.
We've recently published the beginning of the Big Data Actionable Architecture on Bluemix series, starting with secured hybrid data warehouses. This workshop series introduces you what Big Data and Analytics capabilities are, how Bluemix supports them, and then gets you hands-on with Bluemix in walking through a real-world use case.