New book project

18 Sunday Jun 2017

Posted by mp3monster in Books, General, Packt

Tags

API, book, Cloud Service, OMESA, Oracle, Packt

Now the big news, we have just agreed with Packt Publishing to write a book around Oracle’s new API Platform Cloud Service (APIP CS). This is going to be more of a team effort with 4 of us working on the book. With all the authors working for Capgemini as well it should be a lot easier in terms of effort The book is being targeted for late this year to be published so that we can cover the major features being released this summer which will make the product a lot more rounded and complete.
The book will also bring in another initiative that has been running in a fairly low profile manner, but starting to shape up in the form of something called OMESA (OMESA.io). This initiative is a cross party approach to define a reusable reference architecture that engages both the legacy landscape along with API driven / microservices based contemporary solution delivery.

We will of course continue to blog about ICS at https://oracle-integration.cloud

OTN Appreciation Day : OMCS Push Listeners

11 Tuesday Oct 2016

Posted by mp3monster in General, Oracle, Technology

≈ Leave a comment

Tags

#ThanksOTN, Appreciation Day, Cloud, Cloud Service, integration, JMS, messaging, Messaging CS, OMCS, Oracle, oracle-base, OTN, Push Listener, Technology Network

The background to this post, and the OTN Appreciation Day can be seen at Oracle-Base.

Oracle Messaging Cloud Service (OMCS) is I think an overlooked gem of Oracle iPaaS portfolio. I say this as it offers a JMS 1.1 compliant Java library but at the same time provides a means through which integration through REST APIs can be performed. This means it is possible to pretty transparently connect legacy JMS based integrations with new REST based products. The magic sauce (and therefore my favourite feature) is the concept of the Push Listener. Through the REST API it is possible to register a REST URL as a target for queues and topics to have messages sent to. Once registered when a message appears on the queue or topic it will get passed on as a REST call. Whilst is is possible to do with with a little bit of Java code. the Push Listener simplifies the job to a REST call with a bit of XML configuration.

There is one small challenge that makes the integration completely transparent to the recipient of the PushListener today, and that is it currently demands that authentication process take place on initial contact. This is not a complicated or challenging thing to address, but does require a tiny bit of code to address.