IBM Bluemix Workshop version 3

IBM Bluemix – Hands On Workshop

10.1
IBM Bluemix
Hands On Workshop
Nguyen Tai Dzung (Dũng)
Cloud Solution Architect + Bluemix Evangelist
IBM Clouds and Ecosystem Development
Email:
dzungnt@vn.ibm.com
ntaidung@gmail.com
Please register:
https://bluemix.net
https://hub.jazz.net

Contents
1. Module 1 – IBM Bluemix Overview
2. Module 2 – Tour of IBM Bluemix
3. Module 3 – First Deploy
 Exercise – First Deploy Exercises (Bluemix UI, CF CLI and Eclipse)
4. Module 4 – DevOps Services
 Exercise – Bluemix integration with DevOps Services
5. Module 5 – Create your application
 Exercise – Your first Node.js application
6. Module 6 – Services
 Exercise – Adding a service to an application
7. Module 7 – How it works
 Exercise – Specifying a buildpack when deploying an application
8. Module 8: Containers

Contents
9. MobileFirst on Bluemix
10. Big Data on Bluemix
11. Internet of Things (IoT)

Course overview
Welcome to Getting Started with IBM Bluemix
5 © Copyright IBM Corporation 2015

Prerequisite skills and software
•To complete this course successfully, you should understand:
 Basics of application development
 How to use the command line to do basic programming tasks
•You’ll need the following software and accounts:
 IBM Bluemix registration: A 30-day trial is available
 Eclipse: We’ll show you how to do that
 Cloud Foundry Command Line Interface
 Node.js runtime
 An IBM Bluemix account
 An IBM Bluemix DevOps Services account

Course learning objectives
• Understand the basics of the IBM Bluemix platform
• Understand the basics of cloud computing and how to maximize the value of cloud
development
• Learn how to integrate Bluemix into your own development process
• Learn the importance of designing an application to run on a cloud platform, such as IBM
Bluemix
• Understand the different runtime options for deploying an application

Module 1: IBM Bluemix overview
Basics of the IBM cloud platform as a service
© Copyright IBM Corporation 20158

IBM® Bluemix™: IBM’s cloud platform
Bluemix service categories
Developer experience
•Rapidly deploy and scale
applications in any language.
•Compose applications quickly with
useful APIs and services and avoid
tedious backend configuration.
•Realize fast time-to-value with
simplicity, flexibility, and clear
documentation.
Enterprise capability
•Securely integrate with existing
on-premises data and systems.
•Choose from flexible deployment
models.
•Manage the full application
lifecycle with DevOps.
•Develop and deploy on a
platform built on a foundation of
open technology.
Built on a foundation of open technology
Build, run, scale, manage, integrate, and secure applications in the cloud.
•DevOps
•Big data
•Mobile
•Watson
•Business analytics
•Database
•Web and application
•Security
•Internet of Things
•Cloud integration
•API management and
integration

So what is Bluemix?
10
Bluemix is an open-standards, cloud-based platform for
building, running, and managing applications.
Build your apps, your way
Use the most prominent
compute technologies to
power your app: Cloud
Foundry, Docker, OpenStack.
Extend apps with services
A catalog of IBM, third party,
and open source services
allow the developer to stitch
an application together
quickly.
Scale more than just
instances
Development, monitoring,
deployment, and logging tools
allow the developer to run
and manage the entire
application.
Layered Security
IBM secures the platform and
infrastructure and provides you
with the tools to secure your
apps.
Deploy and manage hybrid
apps seamlessly
Get a seamless dev and
management experience across
a number of hybrid
implementations options.
Flexible Pricing
Try compute options and
services for free and, when
you’re ready, pay only for what
you use. Pay as you go and
subscription models offer
choice and flexibility.
Coming Summer 2015

Addressing many types of use cases
•Extend existing applications
- Add user experience such as mobile, social
- Add new capabilities integrating other services and APIs
- Do rapid experimentation for new capabilities
•API-enable applications
- Scalable API layer on top of existing services
- Simplify how composite service capabilities are exposed
through APIs
•New applications
- Systems of Engagement
- Different state management models
- Twelve-factor applications
Backend Systems and
Integration
API Creation and
Management New Channels and
Opportunities

Bluemix structure

How does Bluemix work?
Bluemix is underlined by three key open compute technologies: Cloud Foundry, Docker, and
OpenStack.
It extends each of these with a growing number of services, robust DevOps tooling,
integration capabilities, and a seamless developer experience.
13
Flexible Compute Options to Run Apps / Services
Instant Runtimes Containers Virtual Machines
Platform Deployment Options that Meet Your Workload Requirements
Bluemix
Public
Bluemix
Dedicated
Bluemix
Local*
DevOps
Tooling Your Own Hosted Apps / Services
Integration
and API
Mgmt
Powered by IBM SoftLayer In Your Data Center
+ + +
+ +
+ Always focused on what’s next
Catalog of Services that Extend Apps’ Functionality
Web Data Mobile AnalyticsCognitive IoT Security Yours
+
*Bluemix Local coming Summer

More openness and choice than ever before
14
Bluemix is anything but locked down. You choose how you build, deploy, and
manage your apps. Bluemix takes care of the rest.
Compute
Choose the level of
infrastructure
abstraction based on
your app’s
architectural needs.
Dev Tooling
From editors to source
code management to
continuous delivery, you
can use Bluemix’
powerful tooling or
easily bring your own.
Location
Deploy apps to Bluemix
Public (in a growing
number of geos), your
own dedicated cloud
Bluemix, or one that runs
within your data center
(Local*).
Services
Pick from a catalog of
IBM, third party, open
source, or your own
services to extend your
apps.
IBM
Third Party
Open Source
Yours
*Bluemix Local coming Summer 2

Bluemix offers different compute models to “run your
code”
Cloud Foundry
application
Docker container Virtual machine
Consistent experience:
• Common service binding and consumption model
• Common user ID and permissions model
• Ability to hook into common routing layer
expanding
Level of
abstraction
Flexibility
15
Reference: Bluemix Instant Runtimes, Containers or Virtual Machines?

A PaaS helps developers focus on what’s most
important to them: The application
• Bluemix eliminates and
dramatically simplifies
various tasks:
• OS patching
• OS security hardening
• Deployment
• Load-balancing
• Scaling
• Health management
Networking
Storage
Servers
Virtualization
O/S
Middleware
Runtime
Data
Applications
Traditional
On-Premises
Networking
Storage
Servers
Virtualization
O/S
Middleware
Runtime
Data
Applications
Platform
as a Service
Networking
Storage
Servers
Virtualization
O/S
Middleware
Runtime
Data
Applications
Software
as a Service
Networking
Storage
Servers
Virtualization
Middleware
Runtime
Data
Applications
Infrastructure
as a Service
O/S
Vendor Manages in CloudClient Manages
Standardization; OPEX savings; faster time to value
Customization; higher costs; slower time to value

Bluemix: foundational concepts
Account – Anchor point for billing
UserUserUser
Organizations
•Enables team collaboration
Organizations
•Enables team collaboration
Organizations – enables team collaboration
Spaces
• Logical grouping of apps and service instances
• per-user permissions
Spaces
• per-user permissions
Spaces
• Per-user permissions
Space
Apps Space
VMs
Space
Containers
SpaceService
instances

So what’s a Region ?
us-south
https://console.ng.bluemix.
net
https://api.ng.bluemix.net
eu-gb
https://console.eu-
gb.bluemix.net
https://api.eu-gb.bluemix.net
- Dedicated cloud Foundry Installation & services
- Maximum isolation from entities in other regions
18 Hands on Workshop - © Copyright IBM Corporation 2015
au-syd
https://console.au-
syd.bluemix.net
https://api.au-
syd.bluemix.net

Building increasingly flexible deployment models
Public Dedicated On-premises

Module 2: The Bluemix tour
Demo of the Bluemix interface

Bluemis Tours…

Module 3: Boilerplate applications
Deploying your first application

Boilerplates
•Provide a fast way to get an application stated
•Package of sample application code and services

Exercise 3a: Deploy your first application

Accessing sample code
•Sample code for the application is available to download after a runtime or
boilerplate has been deployed.
1.Click
2.Click

Command-line interface
• Bluemix uses the Cloud Foundry command-line interface (CLI): cf
•cf help provides help page showing all the commands
•cf help <command> provides help for specific command
cf l login cf ds delete service
cf t target space or organization cf bs bind service to application
cf a list apps in current space cf st start app
cf app
display status for specific app
in current space
cf sp stop app
cf p push (deploy or update) app cf d delete app
cf s show service info cf scale scale app
cf cs
create service cf logs tail or show logs for app

Sample cf commands
To log in to Bluemix:
cf l –a https://api.ng.bluemix.net -u <email> -p <password> -o <email> -s dev
cf l –a https://api.eu-gb.bluemix.net -u <email> -p <password> -o <email> -s
dev
This command will log in to Bluemix, set the organization to the user’s own organization, and
the space to dev
To check what space you are logged into or to change the space:
cf t
cf t -s test
The first option prints the current target organization and space.
The second option switches to the test space.
To check what spaces exist in an organization:
cf spaces
Displays the spaces available in the current organization.
cf space dev
Displays information about the dev space in the current organization.

Exercise 3b: Deploy then update an
application using the Command Line
Interface

Eclipse plug-in for Bluemix
• Available in the Eclipse marketplace
• Enables developers to develop in Eclipse and then deploy to Bluemix
 Java and JavaScript are supported
Servers view Right click Bluemix
Select Add and
Remove …
Select available app
Click Add to deploy
to Bluemix

Define your Bluemix server connection in Eclipse
• In Eclipse preferences, select Server then Runtime Environments.
• Add a server definition for each Bluemix space that you want to deploy
to.

Adding additional Bluemix regions to Eclipse
1. Click Manage Cloud from the Add Bluemix Account dialog box.
2. Click Add to add an additional Bluemix cloud
3. Enter the details of the Bluemix region by providing the name and endpoint URL
4. Click Finish.
For more information about region endpoint URLs, see:
https://www.ng.bluemix.net/docs/#overview/overview.html#ov_intro__reg

Environment Variables
•Bluemix sets environment variables when deploying an application to
inform the application about the environment it is running in.
 Application may need to use this information to set configuration – such as
the hostname and port to listen for incoming requests.
 VCAP_APP_HOST – specifies the hostname on which your application should
listen
 VCAP_APP_PORT – specifies the port number on which your application
should listen
•You can also define custom environment variables to provide configuration
to your application

Manifest file
• Allows you to specify the parameters for an application deployment
• manifest.yml file is used at deploy time if found in directory application
is being pushed from
---
applications:
- name: Myphpmyadmin
memory: 128M
instances: 1
host: Myphpmyadmin
path: .
buildpack: https://github.com/dmikusa-pivotal/cf-php-build-pack.git
services:
- mysql_BlueMixLab
---
applications:
- name: bluemix-todo-node
host: bluemix-todo-node-${random-word}
command: node app.js
memory: 128M
services:
- todo-db
http://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html

.cfignore
•When you push an application all content of the current directory and all
sub directories are pushed to the server – this is not the behavior you
always want
•.cfignore allows control of what is sent to the server by listing the files and
directories you do not want to send to the server
•Sample .cfignore file:
.git
node_modules
tmp
lib-src

Exercise 3c: Working with Eclipse and
Bluemix

Summary
• Bluemix provides a number of options for developing applications
giving you the ability to integrate Bluemix into the developer tools of
your choice
• Bluemix provides starter packs to get you up and running quickly
• Start applications from scratch

Module 4: DevOps and Bluemix
Overview of DevOps services and app development

IBM Bluemix DevOps services
An open, integrated rapid development experience that scales
• A Premier DevOps service for IBM Cloud
platform
 Promotes incremental frictionless adoption of
DevOps services for Bluemix
• An integrated developer experience
 End-to-end DevOps solution in the cloud for
developing applications
 Integrated task tracking, agile planning,
source control with autodeploy
 Complementary mobile quality and
application performance monitoring
 Use your favorite tools or work from the web
IDE
 Free public and fee-based private projects
• Scalable, secure, enterprise-ready
 Runs on SoftLayer infrastructure

DevOps Services available today

Exercise 4a: IBM Bluemix integration
with DevOps services

Get productive with Bluemix DevOps services in
minutes
• Register at www.jazzhub.com
• Answer a few questions
 Which Source Code Management
(SCM) - Git, GitHub, Jazz SCM?
 Do you want your project to be
public or private?
 Do you want to practice agile
software development?
 Do you want to deploy on IBM
Bluemix?
• Start coding

Collaborate seamlessly on public or private
projects
• Easily invite team members
• Access from anywhere
• Built for collaboration from the ground up
• Choose who sees your project and how you engage with broader
communities
Invite other people to
your project
Enter a comma
separated list of
email addresses

43
Agile development in the cloud is easy with
Bluemix DevOps services
• Built-in agile process support
• Work items to track and plan project activities
• Agile tools for the product backlog, releases, and sprints
• Dashboard charts for project status

Choose how you code with Bluemix DevOps
services
• Browser-based integrated
development environment
• Full support for local
development with Eclipse
or Visual Studio
• Built-in support for Jazz
Source Control
• Hosted Git repository
• Got GitHub? No problem

Live Sync for Node.js
• Enables Node.JS code changes
to be pushed live without the
need to redeploy the application
• Available in IBM Bluemix
DevOps services as the Live Edit
feature
(Chrome browser only for debug)
• Available on Microsoft Windows
and Applied OS X platforms from
the command line using the Live
Sync CLI

Exercise 4b: Working in DevOps Services

Leverage the power of social coding
Public Private
With public projects, it’s easy to learn and share work with a broader
audience.

Summary
• IBM Bluemix DevOps Services:
 Provides an online set of tooling to plan, manage, develop, and deploy
your application
 Can use the build in code repository or choose to use Git Hub
 Allows developers to collaborate on a project
 Allows developers to work online or locally on the same project

Module 5: Cloud development and the
new IT
Maximizing the value of Bluemix

Challenges and expectations
• Time to market for new applications is
to long
• Speed and innovation are needed to
capture new business opportunities
• Remove blockage from IT deployment
• Competitive threat from new ”on the
web born” companies
• Clients want to enter the API economy.
Need environment to share or sell
software assets they build/own
• Reduce operational cost and limit capital
investments and remove the need to
manage and procure assets and services
Developers’ expectations:Client business challenges:

Bluemix can fit into a software development
process, but will it deliver the promised value?
Initiation
Planning
Requirements
Analysis
Design
Development
Integration
System Test
Deployment
Operation and
Maintenance

What does it take to deliver the promised value?
• User-centered design
• Agile methodology
• DevOps processes and tooling
• Architect for cloud
Microservices
Architecture

User-centered design
Hills: who, what,WOW
Sponsored users: design for
real users, not for imagined
needs
Playbacks: collaborate to tell
a great story

Agile methodology
Agile principles
The Agile Manifesto is based on 12 principles:
•Customer satisfaction by rapid delivery of useful software
•Welcome changing requirements, even late in development
•Working software is delivered frequently
•Close, daily cooperation between business people and
developers
•Projects are built around motivated individuals, who should
be trusted
•Face-to-face conversation is the best form of
communication (co-location)
•Working software is the principal measure of progress
•Sustainable development, able to maintain a constant pace
•Continuous attention to technical excellence and good
design
•Simplicity—the art of maximizing the amount of work not
done—is essential
•Self-organizing teams
•Regular adaptation to changing circumstance
Agile practices
Agile development is supported by several concrete
practices, covering areas such as requirements, design,
modeling, coding, testing, project management, process,
and quality. Some notable agile practices include:
• Acceptance test-driven development (ATDD)
• Agile modeling
• Backlogs (product and sprint)
• Behavior-driven development (BDD)
• Cross-functional team
• Continuous integration (CI)
• Domain-driven design (DDD)
• Information radiators (scrum board, task board, visual
management board, burndown chart)
• Iterative and incremental development (IID)
• Pair programming
• Planning poker
• Refactoring
• Scrum events (sprint planning, daily scrum, sprint review, and
retrospective)
• Test-driven development (TDD)
• Agile testing
• Timeboxing
• Use case
• User story
• Story-driven modeling
• Retrospective
• Velocity tracking
From Wikipedia:

DevOps
Goals
The specific goals of a DevOps approach span the entire delivery
pipeline.They include improved deployment frequency, which can lead to
faster time to market, lower failure rate of new releases, shortened lead
time between fixes, and faster mean time to recovery in the event of a
new release crashing or otherwise disabling the current system.
Simple processes become increasingly programmable and dynamic, using
a DevOps approach,which aims to maximize the predictability, efficiency,
security, and maintainability of operational processes.Very often,
automation supports this objective.
Adoption
The adoption of DevOps is being driven by factors such as:
• Use of agile and other development processes and methodologies
• Demand for an increased rate of production releases from application and business
unit stakeholders
• Wide availability of virtualized and cloud infrastructure from internal and external
providers
• Increased usage of data center automation and configuration management tools
FromWikipedia:

Bluemix unified DevOps experience (roadmap)

Application architecture
Feeds
Pub/sub
Task
Task
Backend Cache
Backend
Web
Web
Web

Twelve-Factor app
(http://12factor.net)
In the modern era, software is commonly delivered as a service: called web apps, or software-as-a-service.
The twelve-factor app is a methodology for building software-as-a-service apps that:
• Use declarative formats for setup automation to minimize time and cost for new developers joining the project
• Have a clean contract with the underlying operating system, which offers maximum portability between
execution environments
• Are suitable for deployment on modern cloud platforms, obviating the need for servers and systems
administration
• Minimize divergence between development and production, enabling continuous deployment for maximum
agility
• Can scale up without significant changes to tooling, architecture, or development practices
The twelve-factor methodology can be applied to apps written in any programming language, and which use any
combination of backing services (database, queue, memory cache, etc).
I. Codebase
One codebase tracked in revision control, many deploys
II. Dependencies
Explicitly declare and isolate dependencies
III. Config
Store config in the environment
IV. Backing Services
Treat backing services as attached resources
V. Build, release, run
Strictly separate build and run stages
VI. Processes
Execute the app as one or more stateless processes
VII. Port binding
Export services via port binding
VIII. Concurrency
Scale out via the process model
IX. Disposability
Maximize robustness with fast startup and graceful shutdown
X. Dev/prod parity
Keep development, staging, and production as similar as possible
XI. Logs
Treat logs as event streams
XII. Admin processes
Run admin/management tasks as one-off processes

Exercise 5a: Creating a new project and
code repository

Best tools for the job
• Importance of having a good developer setup
• Lint tooling (static analysis is useful for code quality)
• Syntax highlighting, autocomplete, etc.
• Quality Assurance needs to be part of the development process
 Continuous testing during development
 Test tools such as Mocha, Chai, Sinon for JavaScript

Exercise 5b: Setting up for static analysis
and test-driven development

Test-driven development
•No code is written unless it is to pass a test.
•When one function calls another function, ensure that unit tests are not
duplicating tests done by the tests for the called function.
 Test frameworks provide spy functionality to verify functions are called
correctly rather than testing what the called function returns.
•Wherever possible, ensure tests cover problematic areas of the
implementation language.
 For example, with a JavaScript string vs number comparison,
“5” > “11” but 5 < 11 type coercion sometimes delivers the wrong comparison

Exercise 5c: Test-driven development

DevOps pipeline in Bluemix
IBM Bluemix DevOps Services can be configured to automatically run
tests and if the tests pass, the code is deployed to Bluemix.

Exercise 5d: Adding a REST API,
deploying to Bluemix, and setting up the
DevOps pipeline

Summary
• A modern cloud platform alone does not deliver the agility and speed
businesses require today.
• A modern approach to application creation is needed, which delivers:
 Innovation
 Agility
 Quality
 Best user experience
• This approach requires an appropriate design, methodology, set of
processes, tooling, and architecture to enable developers to deliver.
• Many companies are adopting a bimodal approach to manage existing
applications and enable innovative new applications to be created.

Module 6: Services
Using and adding services in IBM Bluemix

Using services in Bluemix
• Bluemix provides services that can be used by applications without
requiring you to manage the setup and operation of those services.
• Available services are listed in the catalog in the web UI and can also
be obtained by using the command cf marketplace.
• To use the service, you must bind the service to your application by
using web UI or the command cf bs.

Accessing a service
• When you bind a service to your application, Bluemix adds details
about the service to an environment variable VCAP_SERVICES.
• You can view the VCAP_SERVICES variable in the web UI.
• Applications should be able to parse the VCAP_SERVICES variable.
Click

Parsing VCAP_SERVICES
•Node
if (process.env.VCAP_SERVICES) {
var env = JSON.parse(process.env.VCAP_SERVICES);
var credentials = env['mysql-5.5'][0].credentials;
…
}
•Ruby
mysql_dbs = JSON.parse(ENV['VCAP_SERVICES'])["mysql-5.5"]
credentials = mysql_dbs.first["credentials"]
•Java
String vcap_services = System.getenv("VCAP_SERVICES");
if (vcap_services != null && vcap_services.length() > 0) {
JsonRootNode root = new JdomParser().parse(vcap_services);
JsonNode mysqlNode = root.getNode(”mysql-5.5");
JsonNode credentials = mysqlNode.getNode(0).getNode("credentials");
…
}
The Java buildpack parses the VCAP_SERVICES variable and can auto-configure bound
services. See the Bluemix Liberty for Java documentation.

Unit testing when services are used
• Do not include calls to remote systems in unit tests.
• Service APIs provide a contract between the service consumer and
service provider.
• Unit tests can ensure the code being tested is using the API correctly
according to the contract.
 We should assume that the service provider has also tested the service
and ensures it implements the contract that is defined by the API.
• Test frameworks provide capabilities to stub and mock external calls,
but ensure that the API is being called correctly when you run unit tests.
 These facilities are often called test doubles.

Exercise 6a: Adding a service to an
application

Become a service provider
•In additional to consuming services, you can create new services on
Bluemix
 Private services are available only to your organization
− cf cups biTestService -p "host, port, username, password”
− Specify the ‘properties’ you want to make available to applications binding to the
service
− You can update the properties if requires
 Public services, that can become an additional revenue stream, can only be
added through the IBM Cloud Marketplace

Exercise 6b
Creating a user-provided service

Summary
• The VCAP_SERVICES environment variable allows your application
to discover bound services and provides the information required to
access the service.
• Bluemix allows new services to be added through the IBM Cloud
Market Place.
• SoftLayer can be used to host services.
• User-provided services (private to an organization) can be created or
accessed the same way as a Bluemix provided service.

Module 7: How Cloud Foundry works
Cloud Foundry internals

An open platform as a service (PaaS). The system supports multiple
frameworks, multiple application infrastructure services, and deployment
to multiple clouds.
Cloud Foundry

Lots of languages, frameworks, and services
Multiple languages
• Ruby, Java, Scala, Node.js, Erlang, Python, PHP, etc.
Multiple frameworks
• Rails, Sinatra, Spring, Grails, Express, Lift, etc.
Multiple services
• MySQL, Postgres, MongoDB, Redis, RabbitMQ, etc.
Multiple clouds, Multiple IaaS environments
• Public cloud, microcloud, private cloud

Bluemix architecture

Cloud Foundry kernel internals

Design of a virtual machine (VM)

Cloud Foundry: application staging

Choosing the runtime for an application
•If you don’t specify a runtime when you deploy an application, Bluemix will
try to find a suitable runtime as follows:
1. Each predefined runtime has a position set and runtimes are tried in
ascending position order.
2. Bluemix asks each runtime, starting with runtime at position 1, if it can run
the application.
3. The first runtime that responds that it can run the application is used.
4. If no runtime can run the application, an error is returned.
•At deploy time, you can also specify the runtime to use.

Buildpacks
•Buildpacks provide the framework and runtime support for your
application.
•The buildpack determines whether they can run your application as part
of the auto detect mechanism that Bluemix uses when you push an
application.
•You can control which platform-provided buildpack your application
should use or specify an external buildpack to be used to run your
application: “Bring your own Buildpack.”

Specifying a buildpack
• Use the cf CLI to specify which buildpack to use when deploying your
application.
 Use the -b option with the command cf push
• You can specify the name of an internal buildpack or provide the URL
for an external buildpack.
•cf buildpacks shows the installed internal buildpacks that are
available:
• cf push myApp -b nodejs_buildpack
• cf push myApp -b https://github.com/dmikusa-pivotal/cf-php-build-pack.git

Exercise 7a: Specifying a buildpack when
deploying an application

Cloud Foundry: services

Module 8: Containers
Docker, virtual machines, and Dockerfiles

Docker containers and virtual machines (VMs)
Server Server
Host OS Host OS
Hypervisor Docker Engine
Guest
OS
Guest
OS
Guest
OS
Binaries
Libraries
Binaries
Libraries
Binaries
Libraries
Binaries
Libraries
Binaries Libraries
Appl
A
Appl
A
Appl
B
ApplB
ApplB
ApplB
ApplB
ApplB
ApplB
ApplA
ApplA
VM
Docker = Linux namespaces + cgroups + overlay file system + image format
Docker

Advantages to using containers
• High density: Because containers share the same operating system (OS) image and
middleware (when applicable), you can run more applications on a server.
 For example, if the full stack image required to run an application requires 1 GB, if you wanted to use a full VM, you’d 1
GB times the number of VMs. With LXC containers and AuFS, you can share the bulk of the 1 GB, and you can have
hundreds of containers and still use a little over 1 GB (assuming they are all running the same OS image).
• Fast start-up: Because containers might have several layers in common, only the new layers
need to be copied, dramatically reducing build/transfer/boot/load times.
 A full virtualized system usually takes about 10 minutes to start; LXC containers take seconds, and sometimes even less
than a second.
• Portability across environments: Deploying a consistent production environment is hard.
Even if you use tools like Chef and Puppet, there are always OS and library updates that
change between hosts and environments.
 Docker gives you the ability to snapshot the OS into a common image, and when combined with IBM’s patterns
technology, Docker makes it easy to deploy a collection of images comprising a given workload in another collection of
Docker hosts.
•Cloudy operations with Docker LXC outperform VM
• 48x server reboot, 1.5x server boot, 1.62x server
snapshot, etc.
•Docker LXC density potential compared to VMs
• 3x memory savings
• 26x CPU savings
• 3.22x smaller images in this test (note – image sizes can
vary based on required packages)
Manual VM Docker
Provision Time
Days
Minutes
Seconds / ms
Significant threat to virtualization
market
90

Docker’s components and functions
Container
Image
Repository
Dockerfile for
Container N
ImageN
Container Build
Engine
Server
Host OS
Linux Container + Docker Engine
ContainerA
ContainerB
ContainerN
Push new
Image to
Repository
Describes steps to build
the container
automatically from
source
Get N
…
Run N
Build N
Source Code
Repository
Build Store Run

Sample Dockerfile
• Dockerfile for WebSphere Liberty Profile:
FROM ubuntu:12.04
# add the files we require, jar + WLP files
ADD wlp-developers-extended-8.5.5.2.jar /root/
ADD wlp-developers-runtime-8.5.5.2.jar /root/
ADD JAXWSEJBSample.jar /root/
# install WLP
RUN apt-get update
RUN apt-get install -y default-jre
RUN java -jar /root/wlp-developers-runtime-8.5.5.2.jar --acceptLicense /root/
RUN java -jar /root/wlp-developers-extended-8.5.5.2.jar --acceptLicense /root/
RUN cd /root/wlp && java -jar ../JAXWSEJBSample.jar /root/wlp
EXPOSE 9080
CMD /root/wlp/bin/server run JAXWSEJBSample

Summary
• The advantages of containers:
 Containers and VMs allow you to easily bring applications to Bluemix.
 They provide a way to virtualize and partition physical infrastructure.
 They allow IaaS and PaaS to converge and be co-located.
 They support a large scale deployment with low latency.
 Containers provide portability across environments.

Module 9: Beyond the 30-day free trial
Freemium level of service

After the 30-day Bluemix trial
•After your 30-day trial ends, you will be asked to enter a credit card to
continue using Bluemix.
•You are still able to use Bluemix for free after you enter your credit card
details because there is a freemium level of service available:
 375 GB-hours are free every month—wow!
 Services have a free plan.
•Use the Pricing Sheet and price calculator to verify what you can run for
free each month.
•Use your account summary to check your monthly usage.
•Set notifications to advise when cost thresholds are being reached.

Use the Bluemix UI to manage your Freemium
usage
Dashboard
Pricing Calculator
Account Summary
and Notifications

© 2015 IBM Corporation
IBM Bluemix and Mobile
Redefining Mobile Platform for Developers
Nguyễn Tài Dũng
Cloud Solution Architect + Bluemix Evangelist
IBM Clouds and Ecosystem Development
Email: dzungnt@vn.ibm.com

© 2014 IBM Corporation98
Building Mobile Apps with Cloud
Services

99
IBM MobileFirst reduces your mobile
back-end effort so that you can focus on creating value
where it matters most – your customers’ experiences
Today, most organizations have no choice but to focus
mobile efforts
“under the surface”
Development
Engagement
Security
Operations
Development
Engagement
Security
Operations
The right mobile technologies enable you to deliver great apps

100
IBM MobileFirst Platform Foundation 7.1 – Component Overview

101
b
The MobileFirst platform provides flexibility for you to consume and
compose the capabilities you need – on premise or in the cloud
Quality Assurance
Application Scanning
On Premise or Private Cloud Modules
Application Scanning
Detect code security vulnerabilities at the time of
development
Quality Assurance
Collect beta test feedback, crashes and analyze
user sentiment
Foundation
Development environment, continuous delivery,
operations, security and integration
As Services in Bluemix
Cloud APIs
Cloudant NoSQL DB, Workflow, Business Analytics,
more
Foundation
Services in IBM Bluemix

102
The MobileFirst Platform is integrated into IBM Bluemix Cloud Services
Mobile
Application
Security
Mobile Quality
Assurance
Embeddable
Reporting
Cloudant
NoSQL DB
Cloud
Integration
Workflow
Business
Rules
Cloud
Storage for
mobile data
management
Security
to prevent
unauthorized
access to data
Integration
Connect with
APIs & Systems
of Record
Workflow
to automate
next actions
Analytics
for reporting
and insight

Mobile Cloud

104
Offline Mobile Cloud Application
Fat Clients with presentation and business logic processed
locally.
Data downloaded from backend when on WIFI /
Occasionally
Advantages: Well Integrated and can be Optimized for
Performance
Availability: even without network connectivity.
Disadvantages: No Portability, Complex Code.

105
All processing done online presentation layer at the client.
Many times assumes constant connectivity with backend
Advantages: Multiplatform, Direct and Instantaneous
Accessibility to better services.
Disadvantages: Excessive latency for real time responsiveness, no
access to device features, sometimes difficult to maintain sessions
for a long time.
Online Mobile Cloud Application

106
WHAT IS MOBILE CLOUD ?
• MC refers to an infrastructure where both the data storage and
data processing happen outside of the mobile device.
• Mobile cloud applications move the computing power and
data storage away from the mobile devices and into powerful
and centralized computing platforms located in clouds, which
are then accessed over the wireless connection based on a thin
native client.
• MOBILE CLOUD = MOBILE COMPUTING + CLOUD
COMPUTING

107
WHY DO WE NEED MOBILE CLOUD?
–Mobile devices face many resource challenges (battery
life, storage, bandwidth etc.)
–Cloud computing offers advantages to users by allowing
them to use infrastructure, platforms and software by
cloud providers at low cost and elastically in an on-
demand fashion.
–Mobile cloud computing provides mobile users with data
storage and processing services in clouds, obviating the
need to have a powerful device configuration (e.g. CPU
speed, memory capacity etc), as all resource-intensive
computing can be performed in the cloud.

108
Mobile Cloud: Enabling New Applications
Idea: Offload Computation to Cloud

109
IBM Mobile Offerings in Data and Push Services
Persistent cloud with ability to Notify on
Events or completion of processing
01010
10101
0101
110101
010001
01
0101
0
000111
000101
01
∆

Bluemix Mobile Backend
as a Service

Mobile and Bluemix MBaaS

Mobile and Push Notification

Push Notification

Bluemix Mobile Quality Assurance

Bluemix Mobile Quality Extensions

Deploying the
MobileFirst Server

MobileFirst
Platform
Server
Bluemix
Softlayer bare
metal
Linux instance
Bluemix
app
Bluemix
Services
MobileFirst
app
MobileFirst, Softlayer and Bluemix
Shared
Identity
Token
Adapters

Spectrum of mobile app development approaches
Web-Native Continuum
 HTML5, JS, and
CSS3 (full site or
m.site)
 Quicker and
cheaper way to
mobile
 Sub-optimal
experience
 HTML5, JS, and
CSS
 Usually
leverages
Cordova
 Downloadable,
app store
presence, push
capabilities
 Can use native
APIs
 As previous
 + more
responsive,
available offline
 Web + native
code
 Optimized user
experience with
native screens,
controls, and
navigation
 App fully
adjusted to OS
 Some screens
are multi-
platform when
makes sense
 App fully
adjusted to OS
 Best attainable
user experience
 Unique
development
effort per OS,
costly to maintain
HybridPure web Pure native
Mobile
web site
(browser
access)
Native
shell
enclosing
external
m.site
Pre-
packaged
HTML5
resources
HTML5 +
native UI
Mostly
native,
some
HTML5
screens
Pure
native

Studio provides authoring, visual design, simulation, and runtime
skins for hybrid apps

The Path to New Value with IBM Big Data & Analytics
Presenter: Nguyen Tai Dzung
Technical Consultant + Solution Architect
EcoD Team, IBM Vietnam
dzungnt@vn.ibm.com

The World of Big Data & Analytics Is Rapidly Expanding…

Mức lương trung bình mỗi năm: 116.414 USD (khoảng 2 tỷ 515 triệu đồng) …
Thực tế, “big data” đang là cụm từ “hot” nhất trong toàn bộ thế giới công nghệ hiện nay. Ý nghĩa của
“Big Data” (“Dữ liệu Lớn”) là khá rộng: thu thập những khối lượng dữ liệu khổng lồ (email, văn bản,
video, status Facebook…), xử lý các khối lượng dữ liệu này để tìm ra các thông tin có nghĩa giúp các
công ty, tổ chức có thể đưa ra các quyết định kinh doanh phù hợp hơn trong tương lai.
Với sự vươn lên mạnh mẽ của các mạng xã hội trong những năm qua cũng như của Internet of Thing
trong tương lai gần, “Big Data” chắc chắn sẽ còn tiếp tục “hot” trong vòng nhiều năm nữa.
Các công việc liên quan tới Big Data bao gồm cả các tác vụ phân tích, các loại cơ sở dữ liệu NoSQL
(không đi theo mô hình bảng quan hệ như thông thường do quá nhiều dữ liệu), Hadoop v…v…
Rất nhiều doanh nghiệp đang chạy theo trào lưu này: từ các công ty khởi nghiệp, các công ty dịch vụ
phần mềm cho đến các công ty thông thường. Bởi vậy mà Dice hiện đang có tới 35.000 đầu việc cho
Big Data, và thu nhập cho các công việc liên quan tới công nghệ này tăng tới 9,3% trong năm qua.
Nguồn bài viết: http://vieccntt.com/30-cong-nghe-lap-trinh-thu-nhap-25-ty-dong-moi-nam-p1.html
124
Big Data

Dữ liệu lớn (Big data) là thuật ngữ dùng để mô tả các bộ dữ liệu có kích thước rất lớn, khả năng phát
triển nhanh, và rất khó thu thập, lưu trữ, quản lý và phân tích với các công cụ thống kê hay ứng
dụng cơ sở dữ liệu truyền thống. Một số đặc trưng của Big Data bao gồm:
1. Volume (Dung lượng): Dung lượng của Big Data đang tăng lên mạnh mẽ
từng ngày từ các nguồn như thiết bị di động bao gồm video, hình ảnh,
con người tương tác trên các hệ thống(mạng xã hội, transaction từ bán lẻ …)
 Cứ mỗi 11 giây, một petabyte (~ một triệu GB) dữ liệu được tạo ra trên toàn
thế giới, tương đương với một đoạn video HD dài 13 năm.
 Facebook phải xử lý khoảng 500 TB dữ liệu mỗi ngày (forum, chat, hình ảnh)
 Wallmart – dữ liệu của họ đến từ các transactions
 Lợi ích thu được từ việc xử lý một khối lượng lớn dữ liệu chính là điểm thu hút chủ yếu của Big
Data, tuy nhiên cũng đặt ra nhiều khó khăn trong việc tìm ra những phương pháp, kỹ thuật để
xử lý khối lượng dữ liệu này.
2. Velocity (Tốc độ): với sự ra đời của các kỹ thuật, công cụ, ứng dụng lưu trữ,
nguồn dữ liệu liên tục được bổ sung với tốc độ nhanh chóng.
Tổ chức McKinsey Global ước tính lượng dữ liệu đang tăng trưởng với
tốc độ 40%/năm, và sẽ tăng 44 lần từ năm 2009 đến 2020.
125
Big Data Is All Data (1/2)
Data at Scale
Volume
Data in Motion
Velocity

Big Data Is All Data (2/2)
Data in Many
Forms
Variety
Data
Uncertainty
Veracity
3. Tính đa dạng (variety): Dữ liệu được thu thập từ nhiều nguồn
khác nhau, từ các thiết bị cảm biến, thiết bị di động, qua mạng xã hội
.v.v…
Các kiểu dữ liệu có cấu trúc, bán cấu trúc và không có cấu trúc tồn tại
dưới nhiều hình thức bao gồm hình ảnh, âm thanh, video, văn bản,
v.v…
4. Veracity (Độ chính xác): một trong những tính chất phức tạp
nhất của BigData là độ chính xác của dữ liệu.
Sự gia tăng mạnh mẽ tính tương tác và chia sẻ của người dùng Mobile
làm cho bức tranh xác định về độ tin cậy và độ chính xác của dữ liệu
ngày một khó khăn hơn.
 Bài toán phân tích và loại bỏ dữ liệu thiếu chính xác và nhiễu đang là
tính chất quan trọng của BigData. [2]
5. Giá trị (value): đây là đặc trưng quan trọng nhất của Big Data, đề
cập đến quá trình trích xuất các giá trị to lớn đang tiềm ẩn trong các
bộ dữ liệu khổng lồ.

Two types of big data
1. Data in Movement – Streams
Data following constantly through a network or other data transport
mechanism. Data persisted in memory on a temporary basis is also
persisted to be “in motion”.
 Twitter / Facebook comments
 Stock market data
 Sensors: Vital signs of a newly-born
2. Data at Rest – Oceans
Data is persisted in a physical medium and is considered
relatively static
 Collection of what has streamed
 Web logs, emails, social media
 Unstructured documents: forms, claims
 Structured data from disparate systems

Tools to address practical challenges managing Big Data
InfoSphere BigInsights for Hadoop
For data at rest
100% standard Hadoop
IBM Big SQL, BigSheets
Developer tools, Accelerators
Ease of use for all roles
InfoSphere Streams
For data in motion
Agile development environment
Sub-millisecond response
Live graph, streams debugger
Packaged adapters and toolkits
Geospatial Toolkit

Big Data & Analytics on Bluemix
https://ace.ng.bluemix.net/#/home
You can launch Big Data services and build applications in
minutes on Bluemix. Use only what you need.

IBM Cloudant
Innovator of “Database as a Service” (DBaaS)
JSON document database
For mobile, Web, & IoT apps that need:
Elastic scalability
High availability
Data model flexibility
Data mobility
Available as:
Fully managed DBaaS
On-premises private cloud
Hybrid architecture
Build More. Grow More.
Sleep More.

Hadoop là gì?
 Tóm tắt ngắn gọn về Hadoop:
1. Framework cho phép phát triển ứng dụng phân tán
2. Viết bằng Java, nhưng hỗ trỡ được C++, Python, Perl
3. Linux-based
4. Làm việc với khối lượng dữ liệu khổng lồ (tính bằng Petabyte).
5. Xử lý trong môi trường phân tán, dữ liệu lữu trữ ở nhiều phần cứng khác nhau,
yêu cầu xử lý đồng bộ.
 Hadoop có 2 thành phần:
1. Hadoop Distributed File System: lưu trữ phân tán
2. MapReduce: xử lý phân tán
 Hadoop có thể xử lý các ứng dụng có khối lượng dữ liệu lớn một cách nhanh chóng,
chính xác, hiệu quả cao bằng cách lưu và tính toán dữ liệu trên nhiều node một cách
độc lập. Cụ thể:
Dữ liệu được chia ra thành blocks lưu trữ trên rất nhiều DataNode, mỗi block có
nhiều bản sao lưu trên nhiều DataNode khác nhau, phòng khi một DataNode nào đó
có sự cố thì hệ thống vẫn hoạt động bình thường.

Hướng giải quyết của Hadoop...
 Quản lý file phân tán: Hadoop Distributed File System (HDFS) sẽ chia nhỏ dữ
liệu ra thành nhiều phần. Dữ liệu được quản lý một cách có hệ thống. Ý tưởng
được sử dụng ở đây là “di chuyển tính toán vào trong dữ liệu” thay vì “di
chuyển dữ liệu để tính toán” như cách thông thường.
 Các tiến trình hoạt động độc lập: MapReduce là mô hình tổ chức của Hadoop,
theo đó các node hoạt động một cách độc lập cao. Mặc dù giữa các node vẫn
có giao tiếp nhưng bị giới hạn một cách tối đa, do đó giảm thiểu rủi ro khi một
node bị lỗi.
 Khả năng mở rộng tự nhiên: nhiều chương trình được viết triên các hệ thống
phân tán khác ngoài Hadoop, mỗi lần mở rộng hệ thống từ 10 máy lên 100 hay
1000 máy thì đòi hỏi phải sửa đổi cấu trúc chương trình rất là nhiều. Cách thiết
kế của Hadoop giúp mở rộng chương trình một cách tự nhiên mà không cần
phải thay đổi nhiều hoặc thay đổi rất ít trong một vài trường hợp đặc biệt.

Hướng giải quyết của Hadoop...

More and more of the world’s activity is being expressed
digitally by billions of interconnected devices…
135
Smarter
cities
Smarter
vehicles
Smarter
home
Smarter
health
Smarter
factories
Smarter
transportatio
n
…providing businesses with the ability to learn more about their
operating environment, and identify and act with the potential to
create new value.

DATA
Unlocked from billions of connected devices
CLOUD
Standards based connectivity from anywhere
ENGAGEMENT
New revenue opportunities created from insights
Today 3 technology forces are converging
that are accelerating IoT

SilverHook Powerboats – develops app 40%
faster, enhancing racer and fan experience
“It changes the paradigm in a lot of different areas if we can develop this type
of technology at this speed. It gives other projects a benchmark to live up to.”
—Nigel Hook, president of SilverHook Powerboats
Solution components
Software
•IBM® Bluemix™
•IBM Internet of Things Foundation
The transformation: Powerboat racers and fans both needed real-
time insight into what was happening during races. With IBM®
Bluemix™ and IBM Internet of Things Foundation, the SilverHook
Powerboat team developed an application 40% faster, streaming
sensor data to the cloud and using analytics to deliver information
and alerts to racers. Partner company Virtual Eye also used the
data to create a rich 3-D visualization for fans.
Improves
decision-making and safety during the
race by providing critical data to
drivers
Enhances
fan experience of races with real-
time 3D data visualization
40% faster
application development process
MSP03109-USEN-00
Video:- https://www.youtube.com/watch?v=rpsjxnoNc-U

Intel® Edison Board
Small, Powerful & Adaptable Hardware
Dual-core Intel® Atom™ processor 500MHz
Integrated Wi-Fi*, Bluetooth® Low-Energy (LE)
• 32-bit Intel® Quark™ microcontroller at 100 MHz
• 1 GB of RAM, 4 GB of Storage
• 40 multiplexed GPIO interfaces with expansion board options for total
project design and flexibility
• Yocto Project* Linux*
Module 2 –The Intel Edison board

Expansion options
Partner
Expansion
Boards
Intel
Expansion Boards
Built to Order
Expansion
Boards

Intel® Edison
•70 pin connector
•Hirose DF40 Series
•Easy to build your own board
Intel currently offers 2 boards
•Breakout Board
•Arduino* expansion board
Intel extension Boards

Intel® Edison
Development
Board with Arduino*
•20 digital input/output pins including
•4 pins as PWM outputs
•6 analog inputs
•1 UART (RX/TX)
•1 I2C input connector
•1 ICSP 6-pin header (SPI)

Connect to your Edison
board
what are connectors/cables for ?
Device mode micro USB for :
• 5V power
• Arduino IDE
• Ethernet over USB
• Flash memory
Host / device mode switch
Micro USB for Serial
commands
to Edison via terminal/putty to :
• Flash firmware
• Configure Edison
• IP address
Standard size USB – Host mode for
•Mouse
•Keyboard
•webcam
Barrel (7V-15V) DC power
connector

Intel® Edison
Breakout Board
•I/O: array of through-hole solder points
•USB OTG with USB Micro (AB)
•Battery charger
•USB micro (B) [UART]
•DC power supply jack (7 to 15 VDC)

Partner Expansion
Boards

Collaborate.
Learn. Share.
Succeed.•Intel® Developer Zone is where developers are tapping
into everything they need to successfully bring their
connected ideas to life.
Software tools and testing equipment —
Code samples and how to guides —
Dev Kits, hardware, sensors and more —
Forums, online events and meet-ups —
Peer review and expert insights —
A global community —
software.intel.com/
iot

Module 3
Internet of Things
Foundation
147

IBM Internet of Things Foundation Service
Connect
Collect
Manage
Assemble
• Secure Device Registration
• Scalable Device Connectivity
• Device Management new!
• PAYG SaaS pricing
• Sandbox QuickStart service
• Powered by IBM MessageSight technology
Platform

IoT Zone on Bluemix an intro to
IoTF
IoT Zone in Bluemix https://bluemix.net/solutions/iot

IoT Foundation model
IBM IoT
Foundation
Connectivity Summary
IBM Internet of
Things
Foundation

Getting Started with IBM Bluemix
Hands-On Workshop
Module 3: First Deploy Exercises

Exercise 3: First Deploy Getting Started with IBM Bluemix
Copyright IBM Corporation 2013-2015. All rights reserved.
2
Table of Contents
Workshop overview..................................................................................................................................... 3

Exercise 3a: Deploy your first application................................................................................................... 3

Exercise 3b: Deploy and then update the application by using the CLI...................................................... 5

Exercise 3c: Working with Eclipse and Bluemix ....................................................................................... 13

3
Workshop overview
In this workshop, you will:
• Deploy a simple application from the Bluemix web interface.
• Use the cf command line to modify and deploy the application.
• Configure Eclipse so that you can create IBM Bluemix as a runtime in Eclipse
Exercise 3a: Deploy your first application
This exercise will show you how to deploy a simple application from the IBM Bluemix web
interface.
1. In a browser, navigate to one of the following regions:
• https://bluemix.net: This link should take you to your default location.
o https://console.ng.bluemix.net (Region: US South)
o https://console.eu-gb.bluemix.net (Region: United Kingdom)
o https://console.au-syd.bluemix.net (Region: Sydney)
2. Click LOG IN and then enter your login information on the IBM id page and click Sign in.
You should see your dashboard view:
3. Click CATALOG.

4
4. Select the Node.js Cloudant DB Web Starter from the Boilerplates section.
5. Enter a name for your application as shown above. The host name information is
automatically entered. The host name must be unique on Bluemix, so enter a name with
your company name or initials to make the name unique.
6. Click CREATE.
After a short while your application should be running. You can launch the application by clicking
on the route.

5
Exercise 3b: Deploy and then update the application by using the
CLI
In this exercise, you use the cf command-line interface (CLI) to work with Bluemix. You use this
tool in a terminal or command window on your workstation.
Use the same sample application that was used in exercise 3a.
1. Click Start Coding and then click Download Starter Code.
2. After the starter package is downloaded, move it to a directory on your workstation where
you want to work, such as the Bluemix directory in your Documents folder.
3. Extract the package by double-clicking or right-clicking and click Extract or Unarchive.
Do not delete the .zip file: you will need it in Exercise 3c.

6
4. Delete the deployed application so that you can deploy it from the command line. Click
the Overview page for the application, click the gear wheel in the application, and then
click Delete App.
5. Delete the service and the route with the application by selecting the checkbox in the
Services tab and the Routes tab:
6. Click OK to delete the application.
7. Open a command or terminal window and change the directory to the location where you
extracted the downloaded sample application. (The file package.json should be in your
current directory.)
8. Log in to Bluemix by issuing one of the following commands. Use the same region that
you used in the Bluemix web UI:
cf l -a https://api.ng.bluemix.net (Region: US South)
cf l -a https://api.eu-gb.bluemix.net (Region: United Kingdom)
cf l -a https://api.au-syd.bluemix.net (Region: Sydney)
9. Enter the email and password that you used to log in to the Bluemix web UI. If prompted,
select the organization and space that you want to work in.

7
10.Before you deploy the application, deploy a Cloudant database. View the available
services by running this command:
cf marketplace
11.In the list of services, find the cloudantNoSQLDB service.
12.Create the service by running this command:
cf cs cloudantNoSQLDB Shared BICloudant
• CloudantNoSQLDB is the name of the service from the cf marketplace command.
• Shared is the name of the service plan that you want to use from the cf
marketplace command.
• BICloudant is the name of the service instance that you want to use. Enter your
own name rather than BICloudant. You will use this new name when connecting
(binding) the service to the application.
13.Refresh your web UI to you see the deployed service.
14.Deploy the application.
Push the application to Bluemix by entering the following command. Change the application
name to your unique name:
cf push BI-MyFirstDeploy-3 -c "node app.js" -m 128M --no-manifest --no-start
• BI-myFirstDeploy-3 is the application name and host name.
• -c specifies the command to start the application.
• -m specifies the amount of memory to allocate to each application instance. The
default is 1 GB.

8
• --no-manifest instructs to CLI tool to ignore the supplied manifest, which will be
explained later.
• --no-start instructs to CLI tool not to automatically start the application.
Don’t want to allow the application to automatically start because it needs a database to run.
You must link the Cloudant database instance to the application before you start the
application.
15.Link the database and application by using the following command. Substitute the
application name and service instance names that you used previously:
cf bs BI-MyFirstDeploy-3 BICloudant
• BI-myFirstDeploy-3 is the application name used when the application is
deployed.
• BICloudant is the service instance name used when the service is deployed.
If you refresh the web UI, you see that the application and service are linked, but the
application is still stopped.
16.Start an application by running the following command. Substitute the name of your
application:
cf start BI-MyFirstDeploy-3
• BI-myFirstDeploy-3 is the application that you want to start.
If you refresh the web UI, you should see the application running. If not, you can start the
application from the Dashboard.
17.Launch the application by clicking on the route in the web UI

9
18.In a text editor, open the file app.js and modify the name of the file, the file description,
and the value (lines 306, 307 and 310):
• Line 306: Change the docName from 'sample_doc' to 'test_doc'
• Line 307: Change the docDesc from 'A sample Document' to 'A test Document'
• Line 310: Change the value from 'A sample Document' to 'A test Document'
Save the file when you’re finished editing.
When the application starts for the first time, it creates the sample document in the database.
We have just modified the code that creates the sample document in the database. The
document must be deleted from the database before you restart the application to allow the
database to be populated again.

10
19.In the Bluemix web UI, select the Cloudant Service instance and then start the Cloudant
Dashboard.
20.Launch the Cloudant console.
You should see a single database. Select the database:

11
21.Edit the database document.
22.Delete the document.
23.Confirm the deletion when prompted.
24.Redeploy the updated application with the push command. This time, you don’t need to
include the --no-start or memory parameter.
cf push BI-MyFirstDeploy-3 -c "node app.js" --no-manifest
25.After the application has restarted, test it to ensure that your changes are now running.

12
After the application is tested to confirm that the modified code is running, the application can be
deleted to release resources for the next exercise.
26.Delete the application and service and confirm the deletion when prompted by running
the following two commands:
Delete the application:
cf d BI-MyFirstDeploy-3 –r
• BI-myFirstDeploy-3 is the application name to be deleted.
• -r instructs Bluemix to also delete the routes attached to the application.
Delete the service:
cf ds BICloudant
• BICloudant is the name of the service instance to be deleted.
Confirm the deletion of the application and service.

13
Exercise 3c: Working with Eclipse and Bluemix
This exercise shows you how to work with Eclipse and Bluemix.
1. Launch Eclipse and switch to the JavaScript perspective. You should use a new
workspace, but this is not essential.
2. Configure Eclipse to use Bluemix as a server by opening Eclipse Preferences and
clicking Server > Runtime Environments.
3. Click Add. Then, select IBM Bluemix Runtime and select the Create a new local
server checkbox.

14
4. Click Next.
5. Select the appropriate URL to match the region that you have been using.
6. Enter your email and password, which are the credentials that you used to log into
Bluemix. Click Validate Account to ensure that all details are valid and then click Next.
7. Select the organization and space that you want to use and then click Finish. Click OK to
close the Preferences page.
If you want to work with multiple spaces in Eclipse, you must create multiple server
configurations.
8. Open the Servers view in Eclipse. If it’s not showing, click Window > Show View >
Servers.

15
Use the same application that you used in the last session. You should have the archive file
that you downloaded in the last exercise on your workstation. If not, deploy the Node.js
Cloudant Web Starter application from the Bluemix web UI, click View Guide, and then
download the starter application.
9. Import the starter application package to Eclipse by clicking File > Import.
10.In the Import dialog, click General > Existing Projects into Workspace.
11.Click Next. Then, select the downloaded Zip file and click Finish.

16
The project will be created.
Before JavaScript applications can be deployed to Bluemix by the plug-in, those applications
must be identified as a project suitable for Bluemix deployment by assigning a facet to the
project.
12.Right-click the project in the Project Explorer view and click Properties.
13.Click Project Facets > Convert to faceted form.

17
14.When you see the facets, select the Node.js Application facet. Click OK to close the
dialog.
15.Delete the manifest.yml file by right-clicking it and clicking Delete.
16.Deploy the application. Right-click IBM Bluemix. If you have multiple definitions in the
Servers view, select the server definition for the space that you want to deploy the
application to.

18
17.Click Add and Remove.
18.Select the cloudant_boilerplate_nodejs in the Available column and click Add to move
it to the Configured column.
19.Click Finish.
20.In the Deploy dialog, change the application name to something unique. Click Next.
Ensure that the URL contains a string that will be unique and then click Next.
21.On the Services selection window, click the Add a Service ( ) icon to add a service.

19
22.When the list of available services is shown, select the CloudantNoSQLDB service.
23.Click Finish and Finish again to close the application Deploy dialog.
The application is now being deployed to Bluemix. Eclipse should automatically switch to the
Console view where you see details of the deployment.

20
24.After the application is running, switch to the Server view and expand the Bluemix
server. You should see the application in the list. Start the application from Eclipse by
right-clicking the application in the Servers view and clicking Open Home Page.
Tip: In Eclipse, you can change the browser that’s used to start applications by clicking
Window > Web Browser and selecting your preferred browser.
25.Remove the sample document from the database to allow the application to create it
when the database launches. In the Bluemix web UI, select the Cloudant Service
instance and then launch the Cloudant Dashboard.
You should see a single database:
26.Select the database and then delete the document. Confirm the deletion.
27.In a text editor, open the file app.js:

21
28.Modify the name of the file, the file description and value (lines 306, 307, and 310) to
replace sample with test:
29.Save the changes by clicking File > Save.
Notice in the Server view that the state of the Bluemix server has changed to republish,
which means that an application has changed. However, the application has not yet been
published to Bluemix.
30.Select the cloudant_boilerplate_nodejs application in the Server view and right-click
and click Update and Restart.
31.After the application is restarted, test the application to ensure that the change is now
live.
After the project has been tested, the application can be deleted to release resources for
future exercises.

22
32.Right-click the project in the Explorer view and click Delete to delete the project. Delete
project contents on disk and then click OK.
You are asked whether you want to delete the cloudantNoSQLDB service. Select the
checkbox to delete the service. In the Bluemix web UI, confirm that the application and
server have been deleted.
Important: Deleting a project that is deployed through Eclipse also deletes it from Bluemix.

Hands-On Workshop
Module 4: Bluemix DevOps Services

Exercise 4: DevOps Services Getting Started with IBM Bluemix
Copyright IBM Corporation 2015. All rights reserved.
2
Table of Contents
Bluemix Hands-On Workshop.....................................................Error! Bookmark not defined.

Section 4- DevOps Services ....................................... Error! Bookmark not defined.

Exercise 4.a - Bluemix integration with DevOps Services ...............................................................3

Exercise 4.b – working in DevOps Services....................................................................................5

3
Exercise 4.a - Bluemix integration with DevOps Services
This exercise looks at how Bluemix and DevOps Services work together
Log into Bluemix http://bluemix.net, https://console.eu-gb.bluemix.net or
https://console/au-syd.bluemix.net and deploy the Node.js Cloudant DB Web Starter
boilerplate from the Catalog.
Once the application is running, select the Overview page then select ‘ADD GIT’ on the
Application Overview page
if prompted, add your DevOps Service details and select ‘Sign In’. Ensure you leave the
option to populate the repository selected then select ‘CONTINUE’
In the overview page you will now see the option to ‘EDIT CODE’
select ‘EDIT CODE’ – you should be taken into DevOps Services with the sample
application code imported and ready to work with.
Select ‘BUILD & DEPLOY’. The project has automatically been set up to deploy code
changes to Bluemix when they are pushed to the Git repository.
You can now modify the code and deploy to Bluemix from DevOps Services. To test this,
select the 'run stage'icon in the Build Stage section of the pipeline. You will see the
Build 'Queued', then 'Running' and finally 'Succeeded'. Once the build has complete a
deploy operation should be queued, then run. You should see the deployment running
then Success – to launch the application you can click on the route:

4
You can view logs and history for the build and deploy by clicking the links in the Build and
Deploy stages.

5
Exercise 4.b – working in DevOps Services
In DevOps Services switch to the ‘EDIT CODE’ section so we can edit the code.
Open the views/index.html file and scroll to line 16 to find the string that are displayed on
the welcome page of the app :
Change the line from 'Get Started' to 'Start now'
save the changes by selecting 'File' from the menu, then 'Save'

6
To get the changes pushed to Bluemix we need to commit the changes to the Git
repository.
To work with the Git repository switch into the Git section
The files that have local changes are shown in the Changed Files section (Note, when a
project is first added to DevOps Services some configuration files are updated
automatically - the first 2 files in the list)
Select the html file you just modified, add a commit message and then press ‘COMMIT’
The commit was made to the local branch – the builder works from the remote branch, so
we need to push out changes back to the remote. In the left hand column, expand the
‘PUSH’ dropdown and select ‘Push All’

7
If you quickly jump to the BUILD & DEPLOY screen you will see a build has automatically
been started, which will then be automatically deployed to Bluemix if successful.
Once the deploy has completed test the application to verify the code changes are now
running. You can launch the application by clicking on the link in the deploy stage:

8
Note: if a build fails you can click on the build in the builder and it will take you to a detailed
screen of build history, where you can get access to the logs, files and details of changes
included in the builds. This can help determine why the build failed.

Hands-On Workshop
Module 5: Maximizing the Value of Bluemix

Exercise 5: Maximizing the Value of Bluemix Getting Started with IBM Bluemix
2
Table of Contents
Workshop overview..................................................................................................................................... 3

Exercise 5a: Creating the project source code repository .......................................................................... 4

Exercise 5b: Setting up development tooling............................................................................................ 16

Exercise 5c: Test-driven development...................................................................................................... 23

Implement the divisibleBy function .................................................................................................... 23

Implement the convertToFizzBuzz function....................................................................................... 28

Implement convertRangeToFizzBuzz (introduces Sinon.JS) ............................................................ 31

Exercise 5d: Adding the REST API and deploying to Bluemix ................................................................. 34

Configure a DevOps pipeline to automatically test and deploy code................................................. 37

3
Workshop overview
This workshop will demonstrate an approach for developing applications by using principles
from agile development and using DevOps processes and tooling.
You’ll develop a REST API that will calculate the FizzBuzz result for a given range.
FizzBuzz is a children's numeracy game where any number divisible by 3 is replaced by the
word Fizz, any number divisible by 5 is replaced with the word Buzz, and any number divisible
by both 3 and 5 is replaced with the word FizzBuzz.
For example, for the range 1 .. 20, the response is:
1, 2, Fizz, 4, Buzz, Fizz, 7, 8, Fizz, Buzz, 11, Fizz, 13, 14,
FizzBuzz, 16, 17, Fizz, 19, Buzz
You will use Node.js as the runtime and use test-driven development practices to create the
solution.

4
Exercise 5a: Creating the project source code repository
Before you write any code, you must have the correct tooling and a source code repository. For
this exercise, you’ll use the Git service from IBM DevOps Services for Bluemix.
1. Log in to DevOps Services for Bluemix: http://hub.jazz.net.
2. From your MyProjects page, click CREATE PROJECT.
3. Create a Git repository on Bluemix:
a. Enter a project name.
b. Create a new repository.
c. Create a Git repo on Bluemix.

5
4. Select to initialize the repository
5.
If you want to share your project and make it searchable to the public, do not select the
Private Project checkbox.
6. If you want to use the Track and Plan tool to support agile methodology, add features for
Scrum development.
7. Select the checkbox to make the project a Bluemix project. Then, provide the details of
the Bluemix space that the application will be deployed to.

6
8. Click CREATE to create the project.
The code repository has been created, and you can create a new Eclipse project that is
based on the repository.
9. In DevOps Services console, select the Git URL link and copy the URL. Use Ctrl+C or
Cmd C.
10.Start Eclipse and then from the main menu, click File > Import.
11.From the Select dialog, click Git > Project from Git and then click Next.

7
12.In the Git dialog, select Clone URI and then click Next.
13.In the next dialog, paste the Git repository URL into the URI Location field. This will
automatically populate the Host and Repository path.
14.Enter your DevOps services user name and password. Optionally, select to store the Git
credentials in a secure store in Eclipse. You will need to provide additional information to
initialize the secure store if this is the first time that you store credentials.
15.Click Next.

8
Eclipse will query the Git repository and list the next branch that’s available. Because you
just created the repository, only the master branch exists.
16.Leave the master branch selected and click Next.
The local destination is then chosen. The default location is <user home
directory>/git/<project name>. Use suggested default location. If you want to
change it, you must remember the location because you will need it later in the exercise.
17.Click Next.

9
18.Select the wizard to import as a general project and then click Next.
19.In the Import Projects dialog, enter an Eclipse project name. Use the same name as the
DevOps service project name, but you can change if needed.
20.Click Finish.

10
You now have an Eclipse project linked to your DevOps services Git repository. To
complete the project setup, configure Eclipse to support JavaScript development.
21.Switch Eclipse to the JavaScript perspective:
a. Click Add Perspective at the top right of the Eclipse window.
b. Select JavaScript from the list.
22.Enable the NodeJS facet on the project:
a. Right-click the project name and click Properties.
b. In the Project Facet dialog, click Project Facets and then click Convert to
faceted form.

11
c. When you see the list of facets, click Node.js Application. Click OK.
Adding the facet automatically creates a sample application in the project.
d. Remove the app.js and package.json files. Right-click each file, click Delete,
and confirm the deletion.
The project shows that there are changes to the local copy of the project. These are the
Eclipse project setting files. Don't save these as part of the source code.
23.Add a navigator view to see all the files in the project:
a. Click Window > Show View and then click Navigator.

12
b. Right-click the project name in the Navigator view and click New > File.
c. Name the file .gitignore and then click Finish.
d. Add the following two lines to the .gitignore file:
Windows: Leave the slash as specified; do not change it to .settings:
.project
.settings/
The project still shows that there are changes. This occurs because the .gitignore file
is a new file that is not committed and pushed to the master branch on the Git server.

13
24.Commit and push the .gitignore file:
a. Right-click the project name and click Team > Commit.
b. In the Commit Changes dialog, enter a commit message and select the
.gitignore file. Then, click Commit and Push.
c. Close the confirmation dialog by clicking OK.
The project will no longer show that there are outstanding changes.
Finally, you should add a new window to access the command line. However, this is not
necessary. Instead, you can use a command window outside Eclipse, but it’s more
convenient to have everything in Eclipse because it provides a better working
environment.

14
25.Create a terminals view:
a. From the main menu, click Window > Show View and then click Other.
b. In the dialog, click Terminals > Terminals and then click OK.
c. In the Terminals window, drag the tab to split the bottom section of the screen to
allow concurrent viewing of the terminal and the problem views.
If a command prompt isn’t shown, click the Open Terminal icon to start a new
terminal. Use the default setting. On some platforms, this happens automatically.
Drag and release
when window
outlines show 2
windows

15

16
Exercise 5b: Setting up development tooling
Using appropriate developer tooling with features to automatically check for errors, provide code
assist, and so on can make you more productive and help identify possible problems.
You’ll use the new project that you created in the previous section.
The first step is to ensure the JavaScript tooling is enabled and the test framework is created.
1. Create the JavaScript project:
a. In the Terminals view, change to the directory that contains the project:
• Mac & Linux default: cd <user home>/git/<project name>
• Windows default: cd <user home>git<project name>
If you want to verify where your project is located, right-click the project name in the
Project Explorer view and then click Properties.
Note the project location on the Resources tab:

17
b. In the Terminals window, run the npm init command and answer the prompts:
• Name - provide a unique name for your project
• Version - 0.0.0
• Description - REST API to calculate FizzBuzz value for a given range
• Entry point - server.js
• Test command - node_modules/.bin/mocha
• Git repository - hit enter to accept the default value
• Keywords - can leave blank
• Author - enter your name
• License - hit enter to accept the default value
Windows: Use the forward slash (/) when specifying the test command.
If the Terminals window is too small, double-click the tab to enlarge it to a full screen.
Double-clicking again will return it to its original size and location.

18
c. To move the created files into Eclipse, right-click the project name in the Project
Explorer view and click Refresh or press F5.
d. If the wizard truncated the test script to mocha, open the package.json file in the
Eclipse editor and change it back to node_modules/.bin/mocha.
e. Tests are expected to be in a directory named test, so create a test directory:
i. Right-click the project name in the Project Explorer view and click New > Folder.
ii. Name the folder test and then click Finish.
f. To be able to run tests, install the Mocha framework:

19
i. In the Terminals view, enter npm install mocha --save-dev
ii. Select the project name in the Project Explorer and click Refresh the project in
Eclipse to display the new files.
g. Test that everything works as expected by running a test:
i. In the Terminals view, enter npm test
Note that the test framework ran even though there are no tests defined.
JSHint is a lint program for JavaScript. It provides static analysis of code. It’s a good
practice to have this running in your tooling. Many development teams also include it as
part of their automated test suite.
h. Run JSHint from Mocha:
i. In the Terminals view, enter the following command:
npm install mocha-jshint --save-dev
ii. Select the test directory of the project in the Project Explorer view and then right-
click and click New > File. Name the file jshint.test.js.
iii. In the file, enter the following content and then save the file by clicking File >
Save or use these commands:
Windows and Linux: Ctrl+S

20
Mac: Cmd+S:
require('mocha-jshint')();
iv. Rerun the tests by entering the following command in the Terminals view:
npm test
There are many errors from the imported modules in the node_modules directory. You
do not control this is code, so it should be excluded from tests.
i. Configure JSHint to ignore the files by using a .jshintignore file:
i. Create a .jshintignore file by right-clicking the project name in the Project
Explorer view and clicking New > File.
ii. Add the following content to the file:
node_modules
test
iii. In the Terminals view, rerun the tests: npm test
JSHint is now enabled in the test suite, but ideally the code editor should provide
feedback from the problems.
JSHint is included in Eclipse, but you must configure it.
j. Enable JSHint in Eclipse:
i. Right-click the project name in the Project Explorer view and click Properties.
ii. In the dialog, click JSHint.

21
iii. Click Add next to the Enable JSHint for these files and folders box.
iv. Accept the defaults as shown above and click OK.
v. Click Add next to the But exclude these files and folders from validation box.
vi. Click All files and then select in folder and add the node_modules folder. Select
the include all subfolders checkbox.
vii. Repeat the previous step to exclude the content of the test folder.
viii. Click OK to make the changes and close the dialog.

22
The project is now ready to implement the REST API, so now is a good time to commit
changes to the Git repository (repo).
There is some debate about whether dependencies should be checked in or re-fetched at
build time. To reduce the amount of traffic that you need to push to the Git repo for this
exercise, you will exclude the dependencies in node_modules.
k. Update the Git configuration and then commit and push changes to the Git repo:
I. Switch to the Navigator view to see files that start with a period ( . )
II. Double-click the .gitignore file to edit it and add the node_modules directory
to the file. Then, save the file: Ctrl+S or Cmd+S.
III. Right-click the project name and click Team > Commit. Click the link at the bottom
right of the dialog to open the Git Staging view.
IV. Drag the 4 files from the Unstaged Changes window to the Staged Changes
window. Then, enter a commit message.
V. Click Commit and Push.
VI. Verify that the commit completed successfully and then close the confirmation
dialog.

23
Exercise 5c: Test-driven development
Implement the divisibleBy function
To implement the divisibleBy funtion, you generate the first test that the implementation must
pass. Solving the problem requires a function to discover whether one number is divisible by
another number, so the first test will check whether 3 is divisible by 3.
Before you write the test, you’ll add another test framework: Chai. Chai is a behavior-driven
development (BDD) and test-driven development (TDD) assertion library for Node.js and a
browser that can be paired with any JavaScript testing framework. Chai provides the test
capability to say "I expect this to be true" or "this should be true."
Before you write a test, install Chai and then configure Mocha to use Chai:
1. Install and configure Chai:
a. In the Terminals view, enter the following command:
npm install chai --save-dev
b. Select the project name in Project Explorer and press F5 to refresh the Eclipse
project content.
c. Create a new file in the test folder named support.js and add the following
content:
var chai = require("chai");
global.expect = chai.expect;
d. Create a new file in the test folder named mocha.opts and add the following
content:
--require test/support
e. Save both files.
The files configure Mocha to use the expect functionality from Chai.
2. Create the first test:
a. Create a new file in the test folder named fizzbuzz.test.js by right-clicking
the test folder in the Project Explorer view and then click New > File.

IBM Bluemix Workshop version 3

IBM Bluemix Workshop version 3

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Andere mochten auch

Andere mochten auch (17)

Ähnlich wie IBM Bluemix Workshop version 3

Ähnlich wie IBM Bluemix Workshop version 3 (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

IBM Bluemix Workshop version 3