Chapter 6 – outbound adapters and one way protocols

Chapter 6 introduces outbound adapters and one way protocols for interactions from SOA Suite – both SOA composite applications and Service Bus Projects. The SOA Suite supports several outbound transports that are intrinsically one way: they hand over a message to an external resource without waiting for a response. The technology adapters for JMS, MQ, UMS (User Messaging Service) and AQ support this one-way, fire and forget message exchange pattern.

Parts in this chapter:

The adapter for JMS is introduced in this chapter, used in its outbound mode for sending messages to a JMS destination where it will be consumed by a financial application for collecting details to calculate landing fees for incoming aircrafts. To learn about the similarities between various outbound adapters, especially those for asynchronous actions, we will replace that JMS adapter with an AQ adapter as an alternative implementation.Additionally this chapter looks at various ways for interacting with EJBs.

image

The external resource targeted by the SOA Suite component can be a human. We people are extremely asynchronous in the eyes of automated systems: if we respond at all, we do so rather tardily. The SOA Suite caters for humans through the User Messaging Service (UMS) and the UMS adapter. Through UMS, we can have messages sent from composites through email, instant messaging (chat) and text message (SMS). The next figure shows what this chapter leads up in this area – outbound notifications through email and chat (IM).

Sources for this chapter can downloaded from Github: Folder Chapter 6 .

Preparation of runtime environment

Instructions for preparing the database are here.

Instructions for configuring the JMS resources are here: article on this blog

Configure UMS Email driver for outbound email using GMail – see article on this blog.

Configuring Chat in SOA Suite 12c with the XMPP driver in the UMS Adapter (as well as setting up test XMPP chat accounts and using an (XMPP) chat client – see article on this blog

Geef een reactie

Het e-mailadres wordt niet gepubliceerd. Verplichte velden zijn gemarkeerd met *

De volgende HTML tags en attributen zijn toegestaan: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>