Now the second of the two default delivery
channels that ship with Notifications is this thing called a WebService.
So, if I create a new Delivery Endpoint, that
WebService can be the type of endpoint I am
configuring here. Now, the WebService
Delivery Channel does not have anything
that you could call standard in the way of parameters.
That's because what you are doing here is you are essentially telling it
what website to go to to then
find a WebService, and once you have found that
WebService and specify which method within the
WebService to use, and then, of course, since there are so many different,
you know, there's different WebServices, different methods they employ,
this parameter here is going to be completely dependent
on what you are connecting to as a WebService. Now here's an example
that you will see right here of a Notification
in which -- well, the, the WebService
Delivery Channel's being used here. Here's the
website name that contains that
WebService. Now what the user ended up doing -- he clicked on this
and then, after clicking on that,
that generated a list of WebServices that he could choose
from. He specified his WebService. Each
WebService contained more than one Method,
so he chose the Method he's interested in and then, depending
on that Method -- in this case, it's something that generates a --
or triggers a new work order -- we are going to pass the Equipment Name,
Failure Type, and the Action to Take. These are the parameters
that we are going to be, you know, passing on through
Notifications. So, as you can see, there's no real
generic settings that you are going to find here,
other than the fact that you do have to identify, you know, where
are on the web you are getting that information,
you know, what the name of the service is, and then which Method
within that you are going to be using. Okay, so what kind of things
could you do with a WebService? Well, one of the examples we have on our
vCampus Site is this example of
using a Skype WebService to make a phone call.
Actually, you know, have it dial the phone number for you, and of course,
you can develop your own WebService if you are a developer
and invoke that from within Notifications.
I would like to demonstrate how you could create a delivery
endpoint that makes use of that. I will go ahead and -- from,
from this Contacts Section
here in our Navigator -- I am going to go ahead
and choose a New Delivery Endpoint. Now, this is
an example of an endpoint that
really is not associated with a Contact. If you remember, when
we did this earlier with e-mail, we associated
that with a specific user. But, in
this case, there is going to be no user involved. There's not going to
be no contact involved because we are simply sending this to a WebService.
So, for example, for the name,
I will just call this -- oh, I can call it something like the Maintenance
System if this is something that's going to send
information to a Relational Database, or, you know, just
to make the demonstration here, we will just call it WebService
#1.
And no description in this case. But, the Delivery Channel --
as you can see, we are choosing WebService. That's one of the two that's shipped with
the system. The third is the Office Communication Server which we will
discuss in the next video. And, the, the,
the way you make of this is you specify the WebService
Address. Now, you know, if you are not familiar with WebServices,
you can read an awful lot about it. Just do a Google Search for
WebService. It's basically a mechanism that allows,
you know, operability over the web. So,
for example, these folks, whoever created
that -- actually, this is something
one of the gentlemen out of our Montreal Office in the Training Department
created for us. It's a little WebService that we have
installed on this server, and what it does is it
allows us to write to a Relational Database, to a Microsoft
Access File, and it's generating work orders for us.
So, if I know that that's
the address and, of course, you know, you have to get in, get somebody
involved who's familiar with the WebService at this point
if you are not that person. Once you know that address, you
should be able to interrogate that Server as I just did,
and it, it publishes -- this is part of the WebService
Standard -- it publishes its WebServices
that are available at that URL.
Now, the WebService we want is this Work Order
Generator, and it has two Methods. The Method we
want is a New Work Order. Now, as you can see,
that New Work Order is going to bring up its own set of parameters.
If I had chose ed... -- chosen to Edit a Work Order,
then that would have had different parameters. Now, when I
choose this, I get to specify some defaults, so
I think, for example, let's say that we only have
one that we are making use of right now. This is in our
Lot 3. There's a Heat Exchanger.
We will call this HeatExchanger. That's the
Equipment Name that this work order goes with.
Failure Type -- we will just say By Default. We will just
make that NA. And the Action to Take --
typically when these things fail we have
a variety of different
mechanisms to clear them. So, I will just
say this is Foul_Clear3, And, and that
becomes the defaults for this particular,
this particular WebService.
Right now if I test this, it's going to throw an Exception Error.
But I would like to show you the rest of the configuration
because, to be honest, the only thing we are going to miss by not seeing this
work completely today is, is the
End Result. Every single other thing, the configuration which, of course,
is what we are trying to teach today -- that we will be able to do.
So, anyway, having said that, let me go ahead and check all this in.
And now I can make
use of this New Delivery Endpoint.
I want that delivery endpoint to have a Subscription
to this Notification. Right now, if you look at
Subscriptions for this Notification, there's only
one Subscriber -- well, it's an Escalation Team --
so, I am going to add a second Subscriber. That's
going to be this delivery endpoint.
Yeah, see, as we mentioned, Escalation Teams, Groups,
and individual Delivery Endpoints that are not
associated with a Contact, those can be your Subscribers.
So, I am going to simply subscribe him to that.
And, as you can see, we have picked up what the defaults are.
Now, if you are going to make use of this for
a variety of pieces of equipment -- you know, this particular Notification
goes with this Heat Exchanger in the West Lot
3, then that's fine. But, what, and
you can keep the defaults. But, as you can see, you
go in here and change this. If this is going to a different location,
you can specify that. For example, in here,
I think I will change this -- we will say we are going to do a different procedure.
There we go. And, and, those are the
arguments. That's how I, I can pass those arguments so I
can go back to the defaults. So that's
how we would configure this. So we will go ahead and check all this in.
Now, the Grand Finale to this
would be -- let's go ahead and actually see this
execute this WebService.
Well, we whi.. will not quite see that.
What we will see today -- 'cause it's going to fail -- is we will
see it attempt to execute it. So,
I have, I have checked everything in. My Notification's
running. What I need to do is just
fire something off, or trigger this. And, if you
recall, I was triggering this using the Archive Editor.
This is something we have done a lot in this class
just for demonstration purposes. So that's my
Trigger Tag, the tag that's associated with the
Element Attribute that's in the Target.
So, I am going to push this -- I think the Alarm Limit was
250. I am going to push this to 275.
I will go ahead and save it.
Let's go back, see if we can grab it before it activates.
Yeah, so now what we should see is this
Notification. There we go. We see
the Notification. It went ahead and it successfully sent the
e-mail. Now, here is that error that
I was saying we were going to see in the case of this WebService. But as you
can see, it did execute. It, it's a Subscriber now.
If this had worked properly, if it had worked
properly, the big finish would have been, you'd
see this in your Relational Database. This is a copy of that
Access Relational Database. And, what we would have done is
just sim... simply written those values into that database.
Now, one last thing I want to
say about this is that these delivery endpoints that are
WebServices, there are no Global Configuration Options for that.
This is something that for each and everyone of these
WebServices Delivery Endpoints,
those settings are going to be unique.