Skip to Content

What a simple SAP River / Weibo integration tells us about the enterprise software market in China

Yesterday I saw a tweet from Chip Rodgers who was returning from the SAPTechEd in Beijing.

Weibo is similar to Twitter but is largely focused on Chinese-speaking users.  As a measure of its size, one Weibo user has over 14 million followers. Only LadyGaga has more users on Twitter.

I was curious and created a user on Weibo. This act was more challenging than I expected since everything is in Chinese.   I then started to get interested in the Weibo API – unfortunately for me most of the pages were in Chinese.

I also found some other documentation in English. I was surprised to see that Weibo allows OAuth and Basic authentication, so I decided to try and see if I could get it to work.  Examples were based on curl, so it didn’t look that tough.

     curl -u user:password
I had a user and a password. All I needed was an “appkey”. To get an appkey, I had to register as a Weibo developer. After registering myself as a developer, I had to create an application to get an appkey.  After searching around, I finally got my appkey and tried it out. Success. I was getting cocky. What other experiments might be possible? I remembered an old blog that I had written about integrating Apache ESME into SAP’s OnDemand development platform River and decided to try the same with Weibo.

Here is the River action script that I used. 

var currInput = $CTX.getInput().getRecord();
default xml namespace =  $CTX.collection.getDefaultDataNamespace();
var inputXMLData = new XML(currInput.getData());
var productvalue = inputXMLData.Product.toString().replace(/\n/g,””);
var custname = inputXMLData.CustomerName.toString().replace(/\n/g,””);

var urlString2 = “‘”+custname+”‘+has+a+new+product++'”+productvalue+”‘”;

var request2 = $UTILS.http.createRequest(urlString2, “POST”);
request2.addHeader(“Authorization”,”Basic aGlyc2NoLmRpY2tAZ21haWwuY29tOkFsYZZZZTIzJA==”);
var response2 = $UTILS.http.sendRequest(request2);
$“response code is “+ response2.getResponseCode());
$“6 is ” + response2.getBody().split(“\n”).join(“”));


Note: You need to encrypt the “username:password” using Base64. Here is the site that I used to encrypt my authentication details. 


I was fascinated by the idea that there was a whole group of users that many Western (non-Chinese) enterprise software vendors largely ignore.  The social media-related integrations of such vendors are usually focused on Twitter and Facebook.  Twitter integrations in enterprise software are a dime a dozen but I have yet to see a SaaS CRM system integrating Weibo.  

In my opinion, the attitude is very short-sighted. A recent deal between Atos and Ufida has sensitized me to the critical importance of the Asian software market. SAP also sees the importance of this market as revealed by the recent announcement at the Sapphire in Beijing that they are planning to spend 2 billion dollars in China until 2015.

The fact that a Weibo API exists and is similar to that of Twitter would suggest that existing Twitter integrations could probably be easily ported to Weibo. Switching to the new API, however, probably won’t be enough.  Can the current Twitter sentiment analysis tools handle Chinese or Chinese slang?  Do existing assumptions regarding how Twitter users interact with businesses and other consumers apply to the Chinese market?  Are Klout’s assumptions regarding social media influence applicable to China?

China represents an unbelievable opportunity for non-Chinese enterprise software vendors.  The challenge for such vendors won’t be one of technology but rather one of culture.  

You must be Logged on to comment or reply to a post.
  • Hi Richard,
    Great blog!
    By chance I also signed up for Weibo just today and it was really easy! I just used the Google translation feature in a Chromium browser.

    Regarding retweets and connections to Twitter:
    Now that you know their API, couldn't you build an add-in for Seesmic to connect it to Weibo? That way you would be able to send tweets from Twitter to Weibo and vice versa.

    Cheers, Christian

    • Actually, the Weibo API is pretty straight-forward. A Seesmic add-in or even a ByDesign add-in shouldn't be difficult. The question is why hasn't it been done yet.  I assume that the main reason is that non-Chinese vendors (in the consumer and in the enterprise space) haven't really looked at the Chinese market yet. Or maybe such vendors that have focused on Twitter see Weibo as a threat / a competing social network?


  • Trust you to take Chip's tweet and turn it into an operative enterprise idea.  ESME 2.0 maybe?  Really enjoyed reading this and admire how quickly you act (not only think)
    • Thanks.

      For me, it was another example of where I was easily distracted by something that interested me and I didn't finish another blog that I'm still working on. But you've got to follow the rabbit hole - who knows what wonders you will find.