In 2002 Jeff Bezos issued a mandate that would change the world forever. At the very least it brought a massive change to how data is reused on the Internet. The mandate from Jeff Bezos was: All teams will henceforth expose their data and functionality through service interfaces. Teams must communicate with each other through these interfaces. There will be no other form of inter-process communication allowed: no direct linking, no direct reads of another team’s data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network. It doesn’t matter what technology they use.

You shouldn’t have to be a Swagger expert to get started with designing and building your new API. Creating an API from scratch can be a difficult task, so what if you could create API without writing a line of code?

Have you ever had that feeling you wanted to capture data and just send that data to just about anywhere? Google Forms gives you an easy way to create personalized surveys with the style that you want. So we got the first requirement down with that one, but what about sending the data elsewhere? That is where TIBCO Cloud Integration comes in.

Communication in our daily life is incredibly important, so why should that be any different when you’re building integration processes? Sending emails is still considered an important part of day to day operations. For example when errors occur in your integration flows, you might want to send an email. In this tutorial I’ll walk you through sending an email, and in my case I’ll use Gmail as provider.

You already know Mashery as a great tool for managing your APIs once they’re developed, but how do you even get that far? Join the Mashery team as we discuss the API tools available to define, design and test your APIs before laying down a single line of code, leading to improved cross-departmental communication of planned services, and better end-developer experiences.

Probably the most common version control system, used by developers today is git. Whether that is a self hosted server (like Gogs), a bare repo (git init) or with GitHub, most developers intuitively seem to choose for git as their version control system of choice. I try to store all my projects in local git repos and some of them make it to GitHub, while many of them don’t. When it comes to deployment of apps to TIBCO Cloud Integration, I do many updates per day so I wanted an easy way to not only store my latest source but deploy them right after.

As you’ve probably guessed by my previous two articles I love writing (about) Node.js. What isn’t great, however, is creating deployment artifacts every time you check something in to GitHub and want to deploy. To make that process a little easier there are many tools available, and of of those is Jenkins, the friendly butler. In this “How-to” I’ll walk you through using Jenkins with the tibcli utility to deploy Node.js apps to TIBCO Cloud Integration every time updates are pushed to GitHub.

I’ve just updated the Microsoft Visual Studio Code extension to help develop and deploy Node.js apps to TIBCO Cloud Integration. Apart from a whole bunch of restructuring, it now has the ability to create a new Node.js app (if you don’t want to start from an API spec) and it makes use of the .env files to work with process.env context.

With the introduction of Node.js in TIBCO Cloud Integration you have an amazing toolset to connect to almost anything and build APIs. In fact, there is a good chance that if you know Node.js that your first application was a simple application that said “Hello World” every time (your first API!). Let’s create a custom Express middleware that checks if the IP address of the sender matches a predefined list. In this tutorial we’ll use the list of TIBCO Mashery Traffic Managers as a ‘whitelist’ (so traffic from all other IP addresses will be blocked).

Think you know everything about TIBCO Cloud™ Integration? Think again! What if I told you that since TIBCO Cloud Integration was introduced in May of 2016 there have been TWELVE releases? What if I told you that we are releasing new functionality EACH MONTH?