A feature missing from oBIX is the ability to query an oBIX Server. After all, this is typically one of the first items on an oBIX developer's agenda.

Firstly, I'd like to say how great it was to see everyone at the Niagara Summit. One piece of feedback I got loud and clear is that we should try blogging more often. Therefore, I'm following up my Session with a series of blog articles relating to creating Appliances.

Interested in using oBIX to create some whiz bang view? Wondering how oBIX works? Or perhaps you just want to soak up some Niagara histories into an Energy App?

Niagara 3.5 is jam packed full of new exciting features. One of these is the ability for a Web Supervisor to automatically configure itself. If you're doing mass M2M, this will transform the way you engineer Niagara and save you a ton of engineering time.

Well I've got a bumper edition of a blog article for everyone today! I would first like to say a big thank you to all who attended and helped with the European Niagara Forum 2009. It was great to see everyone.

The other day, I was asked what gargantuan sized PC would be needed for 55 thousand Niagara Points. Mmmm, well by using Niagara Virtual Components, there would be 0 Niagara Points because everything would be created 'on demand'. Hence the whole solution becomes far more scalable. How's does this work then? Well read on trusty Niagara user...

One of the new features in Niagara AX 3.4 are Niagara Virtual Components. So what is a Niagara Virtual Component and what precisely are they used for?

It was great to see so many people at this year's Summit!

So far we've learnt a majority of the skills and techniques that will enable us to create a fully featured oBIX client. However, there is one important technique that provides an efficiency boost to your client applications called the 'Batch' Operation.

This week I'm going to talk about accessing histories using oBIX. Accessing histories is quite a straight forward process in oBIX as I'm sure you'll see.