Tag: IBM

Revisiting Whats up, Watson – Using Watson’s Question and Answer with Bluemix – Part 2

In this I revisit the Bluemix app based on Watson’s Question and Answer service which I had posted in my earlier article “Whats up Watson? Using IBM Watson with Bluemix, NodeExpress – Part 1“. In this post I removed some redundant code and also added some additional checks to the Jade templates to handle responses to “focusless”  questions viz. Am I…? or “Is X contagious?”

You can run the app at Whatsup Watson?

The code can be forked and cloned from Devops at Whatsup

The code is also available at GitHub at Whatsup

The section below briefly describes the details of the implementation of the WhatsupWatson app

A) app.js

In the app.js module the VCAP environment is parsed to get the credentials to use the Watson Question and Answer service as shown below

if (process.env.VCAP_SERVICES) {
  var VCAP_SERVICES = JSON.parse(process.env.VCAP_SERVICES);
  // retrieve the credential information from VCAP_SERVICES for Watson QAAPI
  hostname   = VCAP_SERVICES["question_and_answer"][0].name;               
  passwd = VCAP_SERVICES["question_and_answer"][0].credentials.password; 
  username = VCAP_SERVICES["question_and_answer"][0].credentials.username; 
  watson_url = VCAP_SERVICES["question_and_answer"][0].credentials.url;
}

There different ways of asking Watson questions. Watson’s response will vary depending on the options and parameters that are used to POST the question to Watson. This app uses a route for each ‘question type’ and option. These are

a. Simple Synchronous Query: Post a simple synchronous query to Watson

This is the simplest query that we can pose to Watson. Here we need to just include the text of the question and the also a Sync Timeout. The Sync Timeout denotes the time client will wait for responses from the Watson service

// Ask Watson a simple synchronous query
app.get('/question',question.list);
app.post('/simplesync',simplesync.list);

b. Evidence based question: Ask Watson to respond to evidence given to it

Ask Watson for responses based on evidence given like medical conditions etc.

// Ask Watson for responses based on evidence provided
app.get('/evidence',evidence.list);
app.post('/evidencereq',evidencereq.list);

c. Request for a specified set of answers to a question: Ask Watson to give a specified number of responses to a question

// Ask Watson to provide specified number of responses to a query
app.get('/items',items.list);
app.post('/itemsreq',itemsreq.list);

d. Get a formatted response to a question: Ask Watson to format the response to the question

// Get a formatted response from Watson for a query
app.get('/format',format.list);
app.post('/formatreq',formatreq.list);

To get started with Watson we would need to connect the Bluemix app to the Watson’s QAAPI as a service by parsing the environment variable. This is shown below

B) simplesync.js



The code in simplesync.js, evidencereq.js, itemsreq.js,formatreq.js are similar. The modules construct the question in the format required. The details of the implementation of simplesync.js is included below a. The Watson’s corpus will be set to ‘healthcare’


parts = url.parse(watson_url +'/v1/question/healthcare');




b. The POST headers are set


// Set the required headers for posting the REST query to Watson
headers = {'Content-Type'  :'application/json',
                  'X-synctimeout' : syncTimeout,
                  'Authorization' : "Basic " + new Buffer(username+":"+passwd).toString("base64")};




c. The POST request options are set 


// Create the request options to POST our question to Watson
var options = {host: parts.hostname,
port: 443,
path: parts.pathname,
method: 'POST',
headers: headers,
rejectUnauthorized: false, // ignore certificates
requestCert: true,
agent: false};


The question that is to be asked of Watson needs to be formatted appropriately based on the input received in the appropriate form (for e.g. simplesync.jade)


// Get the values from the form
var syncTimeout = req.body.timeout;
var query = req.body.query;
// create the Question text to ask Watson
var question = {question : {questionText :query }};
var evidence = {"evidenceRequest":{"items":1,"profile":"yes"}};
// Set the POST body and send to Watson
req.write(JSON.stringify(question));
req.write("\n\n");
req.end();


Now you POST the Question to Watson and receive the stream of response using Node.js’ .on(‘data’,) & .on(‘end’) shown below


var req = https.request(options, function(result) {
result.setEncoding('utf-8');
// Retrieve and return the result back to the client
result.on(“data”, function(chunk) {
output += chunk;
});

result.on('end', function(chunk) {		  
           var answers = JSON.parse(output);
			      results = answers[0];
			      res.render(
					 'answer', {
                      "results":results
                                        
			   });
			
});


The results are parsed and formatted displayed using Jade. For the Jade templates I have used a combination of Jade and in-line HTML tags.


Included below is the part of the jade template with in-line HTML tagging


c) answer.jade


mplementation details of WhatsupWatsonapp


The section below briefly describes the details of the implementation of the WhatsupWatson app


A) app.js


In the app.js module the VCAP environment is parsed to get the credentials to use the Watson Question and Answer service as shown below


if (process.env.VCAP_SERVICES) {
  var VCAP_SERVICES = JSON.parse(process.env.VCAP_SERVICES);
  // retrieve the credential information from VCAP_SERVICES for Watson QAAPI
  hostname   = VCAP_SERVICES["question_and_answer"][0].name;               
  passwd = VCAP_SERVICES["question_and_answer"][0].credentials.password; 
  username = VCAP_SERVICES["question_and_answer"][0].credentials.username; 
  watson_url = VCAP_SERVICES["question_and_answer"][0].credentials.url;
}



There different ways of asking Watson questions. Watson’s response will vary depending on the options and parameters that are used to POST the question to Watson. This app uses a route for each ‘question type’ and option. These are


a. Simple Synchronous Query: Post a simple synchronous query to Watson


This is the simplest query that we can pose to Watson. Here we need to just include the text of the question and the also a Sync Timeout. The Sync Timeout denotes the time client will wait for responses from the Watson service


// Ask Watson a simple synchronous query
app.get('/question',question.list);
app.post('/simplesync',simplesync.list);


b. Evidence based question: Ask Watson to respond to evidence given to it


Ask Watson for responses based on evidence given like medical conditions etc.


// Ask Watson for responses based on evidence provided
app.get('/evidence',evidence.list);
app.post('/evidencereq',evidencereq.list);



c. Request for a specified set of answers to a question: Ask Watson to give a specified number of responses to a question


// Ask Watson to provide specified number of responses to a query
app.get('/items',items.list);
app.post('/itemsreq',itemsreq.list);



d. Get a formatted response to a question: Ask Watson to format the response to the question


// Get a formatted response from Watson for a query
app.get('/format',format.list);
app.post('/formatreq',formatreq.list);


To get started with Watson we would need to connect the Bluemix app to the Watson’s QAAPI as a service by parsing the environment variable. This is shown below


B) simplesync.js




The code in simplesync.js, evidencereq.js, itemsreq.js,formatreq.js are similar. The modules construct the question in the format required. The details of the implementation of simplesync.js is included below a. The Watson’s corpus will be set to ‘healthcare’


parts = url.parse(watson_url +'/v1/question/healthcare');




b. The POST headers are set


// Set the required headers for posting the REST query to Watson
headers = {'Content-Type'  :'application/json',
                  'X-synctimeout' : syncTimeout,
                  'Authorization' : "Basic " + new Buffer(username+":"+passwd).toString("base64")};




c. The POST request options are set 


// Create the request options to POST our question to Watson
var options = {host: parts.hostname,
port: 443,
path: parts.pathname,
method: 'POST',
headers: headers,
rejectUnauthorized: false, // ignore certificates
requestCert: true,
agent: false};


The question that is to be asked of Watson needs to be formatted appropriately based on the input received in the appropriate form (for e.g. simplesync.jade)


// Get the values from the form
var syncTimeout = req.body.timeout;
var query = req.body.query;
// create the Question text to ask Watson
var question = {question : {questionText :query }};
var evidence = {"evidenceRequest":{"items":1,"profile":"yes"}};
// Set the POST body and send to Watson
req.write(JSON.stringify(question));
req.write("\n\n");
req.end();


Now you POST the Question to Watson and receive the stream of response using Node.js’ .on(‘data’,) & .on(‘end’) shown below


var req = https.request(options, function(result) {
result.setEncoding('utf-8');
// Retrieve and return the result back to the client
result.on(“data”, function(chunk) {
output += chunk;
});

result.on('end', function(chunk) {		  
           var answers = JSON.parse(output);
			      results = answers[0];
			      res.render(
					 'answer', {
                      "results":results
                                        
			   });
			
});


The results are parsed and formatted displayed using Jade. For the Jade templates I have used a combination of Jade and in-line HTML tags.


Included below is the part of the jade template with in-line HTML tagging


c) answer.jade


if results.question.qclasslist
    for result in results.question.qclasslist
      p <font color="blueviolet">  Value   = <font color="black "> #{result.value} </font> 
  if results.question.focuslist
    p <font color="blueviolet">  Focuslist  </font> = <font color="black "> #{results.question.focuslist[0].value} </font>
  if latlist
    p <font color="blueviolet">  Latlist  </font> = <font color="black "> #{results.question.latlist[0].value} </font>



Disclaimer: This article represents the author’s viewpoint only and doesn’t necessarily represent IBM’s positions, strategies or opinions



Find me on Google+


	


	



			
				


			

			
Rock N’ Roll with Bluemix, Cloudant & NodeExpress
		
	
	

		
Published as a tutorial in IBM Cloudant – Bluemix tutorial and demos


In this post I create a  cloud application that is based on Bluemix, Cloudant DB and NodeExpress.  NodeExpress is used to perform DB operations on  CloudantDB


The code can be forked from Devops from bluemix-cloudant-exp. You can also clone the code from Github from bluemix-cloudant-exp


The following NodeExpress routes are created for performing the basic database operations


    

  1. a) Displaying the list of books
    2. 

  2. b) Adding a book
    3. 

  3. c) Updating a book and
    4. 

  4. d) Deleting a book
    5. 



1


 


Push the app to Bluemix


a) Push the app to Bluemix using

cf push bluemix-cloudant -p . -m 512M


b) In the Bluemix dashboard add the Cloudant service.


c) Double click the CloudantNoSQLDB


9


and then click the ‘Launch’ button. This will bring the WebSQL based version of Cloudant DB


10


c) Next click the link bluemix-cloudant.mybluemix.net


11


This will start the Webserver and also populate the database.


e) This can be seen in the Cloudant Dashboard for the ‘test’ database which has 3 records shown below

12

The setup for these routes in the NodeExpress are as follows


app.get('/', routes.index);

app.get('/booklist', booklist.list);

app.get('/newbook', newbook.list);

app.post('/addbook',addbook.list);

app.get('/changebook', changebook.list);

app.post('/updatebook', updatebook.list);

app.get('/rembook', rembook.list);

app.post('/deletebook',deletebook.list);




Setting up the environment for Cloudant’s PouchDB


The first thing is to setup the environment for Cloudant’s Pouch DB by parsing the process.env environment variables as shown below


//Parse the process.env for the port and host that we've been assigned

if (process.env.VCAP_SERVICES) {

// Running on Bluemix. Parse the port and host that we've been assigned.

var env = JSON.parse(process.env.VCAP_SERVICES);

var host = process.env.VCAP_APP_HOST;

var port = process.env.VCAP_APP_PORT;

console.log('VCAP_SERVICES: %s', process.env.VCAP_SERVICES);

// Also parse Cloudant settings.

var cloudant = env['cloudantNoSQLDB'][0]['credentials'];

}

var db = new pouchdb('books'),

remote =cloudant.url + '/books';

opts = {

continuous: true

};

// Replicate the DB to remote

console.log(remote);

db.replicate.to(remote, opts);

db.replicate.from(remote, opts);


Displaying the list of books


Cloudant responds to DB queries as JSON messages. Hence to display the list of books the fields of each document is stored as an array and then displayed using the Jade table in booklist.jade  This is shown below


    

  1. a) booklist.js
    2. 



var docs = db.allDocs(function(err, response) {

val = response.total_rows;

var details = "";

j=0;

var booklist = new Array(val);

for(i=0; i < val; i++) {

db.get(response.rows[i].id, function (err,doc){

j++;

booklist[j] = new Array(3);

booklist[j][0] = doc._id;

booklist[j][1] = doc.Title;

booklist[j][2] = doc.author;

details= details + JSON.stringify(doc.Title) + "  " +  JSON.stringify(doc.author) + "\n";

// Kludge because of Node.js asynchronous handling. To be fixed - T V Ganesh

if(j == val) {

res.render('booklist', {

"booklist" : booklist

});

}

}); // End db.get

} //End for

}); // End db.allDocs


    

  1. b) booklist.jade
    2. 



The jade template simply displays the each booklist as a row in a table


block content

h1= "Display the list of books"

p

strong DocId  Title   Author

table

each book, i in booklist

tr

td #{book}

p

p

a(href='/') Home


2


Adding a book 

To add a book the book details are obtained using the newbook.jade which display a form

block content

h1= "Add a book"

form#formAddBook(name="addbook",method="post",action="/addbook")

input#inputBookTitle(type="text", placeholder="Title", name="title")

input#inputBookAuthor(type="text", placeholder="Author", name="author")

button#btnSubmit(type="submit") submit

a(href='/') Home


With the values obtained from the form above a document is inserted into the books database as follows


// Get our form values. These rely on the "name" attributes

var Title = req.body.title;

var Author = req.body.author;

db.put({

author: Author,

Title : Title,

}, Title, function (err, response) {

console.log(err || response);

if (err) {

// If it failed, return error

res.send("There was a problem adding the information to the database.");

}

else {

// Redirect to booklist - Display booklist

res.location("booklist");

// And forward to success page

res.redirect("booklist");

}

});


Note: When inserting a document into the books database the docid for the document is set to be the same as the book Title itself


7


4


Updating a book


To update a document we need to input the document id. Also the document to be updated should use the “_rev” field which is obtained when we get the document. The values to be input are taken with the changeuser form


block content


h1= "Update a book"

form#formUpdateBook(name="addbook",method="post",action="/updatebook")

input#inputDocId(type="text", placeholder="DocId", name="docid")

input#inputBookTitle(type="text", placeholder="Title", name="title")

input#inputBookAuthor(type="text", placeholder="Author", name="author")

button#btnSubmit(type="submit") submit

a(href='/') Home


The values obtained are used to populate the document as follows


db.get(DocId, function(err, response) {

db.put({

_id: DocId,

_rev: response._rev,

author: Author,

Title : Title,

}, function(err, response) {

if (err) {

// If it failed, return error

res.send("There was a problem updating the information to the database.");

}

else {

// If it worked, redirect to display books

res.location("booklist");

// And forward to success page

res.redirect("booklist");

}

});

});


6


5


Deleting a document


To delete a document we need the document id which is taken with the rembook.jade form


block content

h1= "Delete a book"

form#formDeleteBook(name="addbook",method="post",action="/deletebook")

input#DocId(type="text", placeholder="DocId", name="docid")

button#btnSubmit(type="submit") submit

a(href='/') Home


//Deleting document book1

db.get(DocId, function(err, doc) {

db.remove(doc, function(err, response) {

if (err) {

// If it failed, return error

res.send("There was a problem removing the information to the database.");

}

else {

// Redirect to booklist

res.location("booklist");

// And forward to success page

res.redirect("booklist");

}

console.log(err || response);

});

});


In the diagram below docid ‘book3’ is deleted


13


8


Important tips


    

  1. If you run into issues while create a Jade template then do the following
    2. 



npm install jade --g


You can check your jade template for correctness using


jade <name of jade template>


If the response is ‘rendered <name of jade template>.html’ then the template is fine.


    

  1. If there are problems with deploying the application or if the application crashes you check the cf logs as follows for the issue
    2. 



cf logs <name of application> --recent



As mentioned the  code can be forked from Devops from bluemix-cloudant-exp. You can also clone the code from Github from bluemix-cloudant-exp


Disclaimer: This article represents the author’s viewpoint only and doesn’t necessarily represent IBM’s positions, strategies or opinions




See also


1. Brewing a potion with Bluemix, PostgreSQL & Node.js in the cloud

2. A Bluemix recipe with MongoDB and Node.js

3. Spicing up IBM Bluemix with MongoDB and NodeExpress

4. A Cloud Medley with IBM’s Bluemix, Cloudant and Node.js

Find me on Google+

	


	



			
				


			

			
Spicing up a IBM Bluemix cloud  app with MongoDB and NodeExpress
		
	
	

		
In this post I highlight the rudiments for a creating a cloud application on IBM’s PaaS offering Bluemix, using MongoDB and NodeExpress.   Clearly Bluemix allows one to fire up a cloud application with a NoSQL database in a matter of  a few hours which makes it really attractive. The NodeExpress  application was initially created using Enide Studio for Node.js  with a local Mongodb server running on my desktop. (Please see my post Elements of CRUD with Node Express and MongoDB) Once you have ironed out the issues in this local application you are ready to deploy on IBM Bluemix.


The code for this Bluemix application can be forked from bluemix-mongo from IBM Devops.


You can also clone the code from GitHub at bluemix-mongo


Here are the key changes that need to be made for running the NodeExpress Webserver with MongoDB as the backend DB


1) Webserver : Setup the port and host for the Webserver.


    

  1. app.js
    2. 



var port = (process.env.VCAP_APP_PORT || 1337);

var host = (process.env.VCAP_APP_HOST || '0.0.0.0');

var app = express();

app.configure(function(){

app.set('port', port);


As seen above the host & port for the Webserver are obtained from the process.env variable.

2) Routes and Middleware

Setup the routes and invoke them appropriately in app.js

var express = require('express')

, routes = require('./routes')

, user = require('./routes/user')

, userlist = require('./routes/userlist')

, newuser = require('./routes/newuser')

, adduser = require('./routes/adduser')

, changeuser = require('./routes/changeuser')

, updateuser = require('./routes/updateuser')

, remuser = require('./routes/remuser')

, deleteuser = require('./routes/deleteuser')


app.get('/users', user.list);

app.get('/helloworld', routes.index);

app.get('/userlist', userlist.list);

app.get('/newuser', newuser.list);

app.post('/adduser',adduser.list);

app.get('/changeuser', changeuser.list);

app.post('/updateuser', updateuser.list);

app.get('/remuser', remuser.list);

app.post('/deleteuser',deleteuser.list);




3) Initialize MongoDB database: Create a set of 3 records when the Webserver starts as follows


if (process.env.VCAP_SERVICES) {

var env = JSON.parse(process.env.VCAP_SERVICES);

if (env['mongodb-2.2']) {

var mongo = env['mongodb-2.2'][0]['credentials'];

}

} else {

var mongo = {

"username" : "user1",

"password" : "secret",

"url" : "mongodb://user1:secret@localhost:27017/test"

}

}

var MongoClient = mongodb.MongoClient;

var db= MongoClient.connect(mongo.url, function(err, db) {

if(err) {

log("failed to connect to the database");

} else {

log("connected to database");

}

var collection = db.collection('phonebook');

//Clear DB and insert 3 records

remove(mycallback);

var user1 = { "FirstName" : "Tinniam", "LastName" : "Ganesh","Mobile": "916732177728" };

var user2 = { "FirstName" : "Darth", "LastName" : "Vader","Mobile": "6666699999" };

var user3 = { "FirstName" : "Bill", "LastName" : "Shakespeare","Mobile": "8342189991" };


    

  1. insert(user1,function(err,result){});
    2. 

  2. insert(user2,function(err,result){});
    3. 

  3. insert(user3,function(err,result){});
    4. 

  4. find().toArray(function(err, items) {
    5. 



});

});


3) Home Page: Setup up a Home page with the CRUD operations when the Bluemix cloud application’s route  for e.g. http://bluemix-mongo.mybluemix.net is clicked. This is shown below.


1


 


2


4) Display Users: To display the list of users the route /userlist is invoked. This function gets all the records from the collection and stores them into a toArray element, which is then used for rendering the list of uses with a ‘userlist.jade’ template


userlist.js

var MongoClient = mongodb.MongoClient;

var db= MongoClient.connect(mongo.url, function(err, db) {

if(err) {


    

  1. log(“Failed to connect to the database”);
    2. 



} else {


    

  1. log(“Connected to database”);
    2. 



}

var collection = db.collection(‘phonebook’);

//Get all records and display them


    

  1. find().toArray(function(err, items) {
    2. 

  2.    log(items);
    3. 

  3. render(‘userlist’, {
    4. 



“userlist” : items

});

});

});


    

  1. jade
    2. 



This template displays the list of users as a table. The code is shown below


extends layout

block content

h1= "Display the list of Users"

p

strong Firstname Lastname   Mobile

table

each user, i in userlist

tr

td #{user.FirstName}

td #{user.LastName}

td #{user.Mobile}

p

p

a(href='/') Home


Note: A link back to the Home page is included in here at the bottom.


7


 


5) Adding a User

There are 2 parts to this

a) Invoking the /newuser route to display the input form through the newuser.jade

b) Invoking the /adduser route to insert the values entered in the form. The changes are shown below

a) app.js

..

newuser = require('./routes/newuser')

adduser = require('./routes/adduser')

..

app.get('/newuser', newuser.list);

app.post('/adduser',adduser.list);




b) newuser.js

exports.list = function(req, res){


    

  1. render(‘newuser’, { title: ‘Add User’});
    2. 



};


The newuser jade displays the input form

c) newuser.jade

extends layout

block content

h1= "Add a User"

form#formAddUser(name="adduser",method="post",action="/adduser")

input#inputUserFirstName(type="text", placeholder="firstname", name="firstname")

input#inputUserLastName(type="text", placeholder="lastname", name="lastname")

input#inputUserLastName(type="text", placeholder="mobile", name="mobile")

button#btnSubmit(type="submit") submit

p

p

a(href='/') Home


3


d) adduser.js


The adduser.js gets the mongo url from the process.env.VCAP_SERVICES and  setups up the connection to the DB and inserts the values received in the ‘newuser.jade’ form into the database


exports.list = function(req, res) {

if (process.env.VCAP_SERVICES) {

var env = JSON.parse(process.env.VCAP_SERVICES);

if (env['mongodb-2.2']) {

var mongo = env['mongodb-2.2'][0]['credentials'];

}

} else {

var mongo = {

"username" : "user1",

"password" : "secret",

"url" : "mongodb://user1:secret@localhost:27017/test"

}

}

// Set up the DB connection

var MongoClient = mongodb.MongoClient;

var db= MongoClient.connect(mongo.url, function(err, db) {

if(err) {


    

  1. log(“Failed to connect to the database”);
    2. 



} else {


    

  1. log(“Connected to database”);
    2. 



}

// Get our form values. These rely on the “name” attributes

var FirstName = req.body.firstname;

var LastName = req.body.lastname;

var Mobile = req.body.mobile;

// Set our collection

var collection = db.collection(‘phonebook’);

// Insert the record into the DB


    

  1. insert({
    2. 



“FirstName” : FirstName,

“LastName” : LastName,

“Mobile” : Mobile

}, function (err, doc) {

if (err) {

// If it failed, return error


    

  1. send(“There was a problem adding the information to the database.”);
    2. 



}

else {

// Redirect to userlist – Display users


    

  1. location(“userlist”);
    2. 



// And forward to success page


    

  1. redirect(“userlist”);
    2. 



}

});

});


If the insert is successful the userlist page is displayed with the new user


4


6) Updating a User & Deleting a User: Updating and Deleting users follow the same format as Adding a user.


7) index.jade The Home page is built using index.jade with a hyperlink invoking the route for each database operation

extends layout

block content

h1= title

p Welcome to #{title}

ul

li

a(href='/userlist') Display list of users

li

a(href='/newuser') Add a user

li

a(href='/changeuser') Update a user

li

a(href='/remuser') Delete a user


Tip: “Return of the Jade“i : Getting the jade template right is truly an art as Jade is extremely finicky about spaces, tabs, indents and outdents(???). Creating the Jade template had me run into circles. I found out that you can debug the jade template individually by executing


C:> npm install jade -g"

and then  running

C:> jade <template name>



from the command prompt. If the result of the command is “rendered <template name>.html” then you are in luck and you can incorporate this jade template into your views folder for e.g.


C: >jade index.jade

rendered index.html


8) Push changes to Bluemix: Once the changes have been made push the changes on to Bluemix with ‘cf’ as follows


cf login -a https://api.ng.bluemix.net

cf push bluemix-mongo -p . -m 512M

cf create-service mongodb 100 mongodb01

cf bind-service bluemix-mongo mongodb01


 


The last 2 commands can also be performed through the Bluemix dashboard in which you add the mongodb service to your Node.js app/


8) Files and Logs: In the Bluemix dashboard you can check your logs in the Files and Logs


5


 


6


Important tip: Finally if the application fails to start when you  push the application with ‘cf’ for e.g.


cf push <app name> -p . -m 512M

....

.....

----> Writing a custom .npmrc to circumvent npm bugs

----> Installing dependencies

----> Caching node_modules directory for future builds

----> Cleaning up node-gyp and npm artifacts

----> No Procfile found; Adding npm start to new Procfile

----> Building runtime environment

----> Checking and configuring service extensions

----> Uploading droplet (7.6M)

of 1 instances running, 1 down

of 1 instances running, 1 down

of 1 instances running, 1 down

of 1 instances running, 1 down

or if  it crashes when you click a link then your debugging friend is


cf logs <app name > — recent

This will dump the error that was encountered either while the application was being started of why the application crashed.


You can fork this Bluemix application from bluemix-mongo at  IBM Devops or from GitHub at bluemix-mongo


Disclaimer: This article represents the author’s viewpoint only and doesn’t necessarily represent IBM’s positions, strategies or opinions


You may also like

1. Brewing a potion with Bluemix, PostgreSQL & Node.js in the cloud

2. A Bluemix recipe with MongoDB and Node.js

3. A Cloud Medley with IBM’s Bluemix, Cloudant and Node.js

4. Rock N’ Roll with Bluemix, Cloudant & NodeExpress




Find me on Google+