Tip:
Highlight text to annotate it
X
First of all, let's take a look at what happens when you install
Notifications. You will notice that Notifications is not
installed on this particular machine, and you can tell that by looking at the
PI System Explorer. See, take a look down here. We
do not see in this pane down here, we do not
see Notifications listed. That indicates to me
Notifications is not installed or
associated with this AF Server. So, let me just minimize that.
I am going to go ahead and do the install for Notifications.
Now, I have got the Notifications Set-up right
here. I will just go ahead and Run this Set-up.
We are going to be prompted for several different
servers that we are going to be required to identify. For example,
the AF Server and any WebParts Server
that might be involved, an IIS Server for
the Notifications Acknowledgement, that kind
of thing. So, that's all coming up.
We will see that as we go through the Install.
Okay, that's going to be the Default Directory, I will
take that. In fact, I am going to take the Default for a lot of these things.
Now here are the different things that I can install.
As we described earlier, there's three parts to this: the Client,
the Service, and then this Acknowledgement Page. We are going to install
all of them in this case. And now,
we are being prompted here for the Name of the AF Server, and it's just
gone out and it's found the Default. Now, in this
environment right here, we have got a very simplistic install.
I have only got one AF Server in this
environment, and, and that's this one
called OSIsoft.trng. In fact, that's the name of
all the Servers. That's the same machine that we are using for
SMTP for sending e-mail. It's our Web Server
for the PI Notifications
that we are going to be using, the Notifications Acknowledgment Page.
And it's also our PI WebParts Server. So, we are
going to see that Server Name a lot during this particular
install. Everything's being self-contained on a single
machine. And, speaking of single
machine, if you are using this, you know,
this AF Server on the same machine as
Notifications, then you can get away with using local
system. If you are going across
from an AF Server on a different machine,
then, typically, what you are going to be using is their dame... is a
domain user. Now, if you are choosing
the domain user option because you are
installing this on a machine that is not the same machine as
your AF Server, then make sure that that domain user
does have Administrative Privileges to run AF.
Here's the spot where we get
a lot of different things we have to answer here. We need to
specify what is the PI Server that's going to be
carrying the historization of the Notifications. So, this
is why we are looking for the Name of the PI Server and, again,
as I said, this particular Server here, OSIsoft.trng,
it's going to be used over and over again. That is our PI
Server here. It is also our SMTP Server.
So, I am going to go ahead and make reference to that.
Now that's if you are going to be using the e-mail Notification,
or, or e-mail Delivery Channel which
it would be a real stretch to imagine you are going to go to all the trouble of installing
Notifications and you are not doing any e-mail notification.
If you are only using specific Delivery
Channels -- oh, like .xml or something that you have written yourself --
then I could see not using an SMTP Server for
e-mail. But, you know, this is overwhelmingly what the majority of
our users are going to be doing. So, that's going to be the SMTP Server.
It just needs to be a machine that you have access to
within your environment. Now, we do recommend that you
come up with some kind of an e-mail address. I am just going to go with
training@osisoft.com. Everything that we send
via Notifications is going to have that as the Sender
Name. Now, at this point, if you
have a WebParts Server -- now, this is where you can
go ahead and specify what that Server Name is. Well, we do have a Web
Sorp...WebParts Server and, hey, guess what. It's the
same server that we have used for everything else. So, this is a
real simply, or real, real simple installation
here. So, I am going to go ahead and specify that. It could
be something that's -- or, excuse me,
it could be something that's on your network.
Does not have to be the same server, obviously. Now, there's one thing about
this WebParts Server. It does have to be a fully-qualified domain
name. So, in my case, it's osisoft-
trng.osisoft.int.
Yeah, so that is a requirement that the -- you specify the fully-
qualified name. I will go ahead and
say Next. Now, I should point out, in general, if
you accept the Defaults, you should be good here, because what we are doing here
is we are specifying what Virtual Directories are going to be installed
on the IIS Machine that you are using if you are using
that Notifications Acknowledgement Page,
and you have the option to change the Defaults if you
want, but -- and, and if you are not the person who's familiar with
IIS, you know, your WebServer, you might want to get them involved at
this point. But, just choosing the Default should work.
Now, I am going to go ahead and specify we are going to change -- or choose
the Default Website. This particular
II -- a copy of IIS on this machine is running several
WebServers, and I am going to go ahead and -- or
websites, I should say -- and I am going to go ahead and specify
the Default. And, this is going to be the Name,
the Virtual Directory Name, that's going to be created.
Now, I am going to to ahead and leave the Default Virtual Directory Name
and also the Default for this Parent here. Now, right here,
this Physical Directory is telling us where we are going to be installing this
Acknowledgement Page or the --
basically, the support files for this Acknowledgement Page.
That's what we are doing in this particular screen
here. We are specifying
for IIS's purpose, for the Web Service purposes,
you know, things about that Acknowledgement Page.
I will go ahead and click on Next,
and it looks like everything's
been answered at this point. So, I will go ahead and choose Next
and wait for the installation to finish. Now, the big finish
to this, the, the grand finale, should be, when we are finished,
we should be able to launch this PI System Explorer
and see that there's been a new
option added to the pane down at the bottom.
That's going to be the Notification shows up for the first time.
Okay. It looks like the Notification was
installed properly. I will go ahead and Finish. And, as I
said, the, the grand finale to this would be to launch
the PI System Explorer.
It's under PI System, and to take a look
and see if we have added Notifications.
And there we go. Take a look down here. We can see two new
things have been added: Notifications, and then Contacts. The Contacts
are going to be part of the Notifications.