Avaya TV

Advanced Breeze Techniques Video-Part 2

This video explores Breeze Connectors and demonstrates how they fit into System Manager and the Breeze APIs.


[00:00:01]
>> Hi, and welcome to part two of Advanced Avaya Breeze Techniques. My name is Andrew Prokop and I work at Arrow Systems Integration as a communications consultant and techno geek. Today, I want to talk about Breeze connectors and how they are used to augment the built-in functionality of the Breeze platform.

[00:00:17]
I will then show you a concrete example using the SMS text connector from WEBTEXT. I will begin by showing you the Breeze API definition. Since my previous videos have dealt exclusively with Engagement Designer, you've been shielded from the low level Java aspects of Breeze. However, in order to understand connectors, you need to at least be aware of this underlying set of APIs.

[00:00:40]
These APIs are what Engagement Designer drag and drop tasks are built on. As an ED developer, you fill in parameters and input values, but in order for those tasks to actually do anything, they must use these APIs. For instance, if I open up the call object, you will see the functionality encapsulated in ED tasks such as drop and allow call.

[00:01:03]
So here we see drop and here we see allow call. I can do the same for media. Let's open up MediaService. And we see things like play, prompt and collect, send digits, the functions that we've used in our tasks, such as play and collect, and play announcement. Call and media processing are both performed by Avaya Components.

[00:01:28]
Call processing is provided by Communication Manager, and media processing is the job of the Avaya Media Server. However, there is functionality that Avaya has essentially off-shored to third parties. For instance, the ability to send SMS text messages is exposed by both the Java API and Engagement Designer. But the work required to do the actual sending is handed off to a third party.

[00:01:53]
To fit themselves into Breeze, third parties write a special kind of snap-in called a connector. A connector is invoked by the appropriate APIs to do the actual work defined by those function calls. For SMS, there are two third party providers, Clickatell and WEBTEXT. Both are cloud services that are invoked when a Breeze snap-in attempts to send an SMS text.

[00:02:16]
As a Breeze developer, you don't need to know that. Java programmers code to the API, and Engagement Designer developers use the Send SMS task. However, Breeze administrators need to be aware of the connector, and it's not a bad idea for everyone else to know of them too. Connectors are found where you find every other Breeze snap-in, under the Breeze Service Management section in System Manager.

[00:02:40]
I mentioned before that Breeze supports two connectors for SMS text. In my lab, I have chosen to use the one by WEBTEXT, which happens to be called WebtextConnector. So let's find that. So I'm under Service Management. These are all the loaded snap-ins. They're alphabetically ordered, so if I go towards the end, then I can find WebtextConnector.

[00:03:05]
To see the configuration values for WebtextConnector, you go to Configuration > Attributes. Under Service Globals, I will find WebtextConnector. These are the values that the connector uses when it communicates with the WEBTEXT cloud service. So API id and API password. This is my account with WEBTEXT. And then the WEBTEXT service URL, this is where the connector will send any of the commands that it needs to perform its function, such as to send a text message, it will send it to this service URL.

[00:03:54]
In future videos, I plan on addressing the debug tools that you can use on your snap-ins. And I will re-address connectors and more specifically the Breeze connector bus. Until then, this should be enough to supply you with the most important information about connectors. With that, I will put an end to this video.

[00:04:10]
For more fun and games, be sure to subscribe to the Aero Systems Integration YouTube Channel. Bye for now.
Error: There was a problem processing your request.