In your Class Workbook, you will find some information
about what's going to be required during the install. You will also
find a bunch of screen prints. But, let's just go ahead and I will
demonstrate what a Server Install looks like.
So, here I am back on my Server Machine. I have got that
License.dat file. I just put it somewhere locally,
somewhere arbitrary. It does not matter where. And then I have also got
the Setup Kit. Now, my Setup Kit consists of
this big huge amount of files here along with
a Setup that runs it all. You may have just a single executable.
It really depends on when you download it, where you
downloaded it from, whether you got it on media that we shipped
to you, etc. So, one way or another, just go ahead and
run that Setup. During the PI
Server 2010 Install, we do required AF, so we
warn you about that. Now, PI AF is a, an important
and integral component of the PI Server now.
So, we warn you abut that. It has to be up and running
during the install. We will connect to it during the install.
It does not have to be on the same machine. It
can be, just be anywhere on the network, and typically --
well, typically, it can be on a different machine, so
for performance issues that's, of course, a decision up to you --
where you install PI AF. But it has to be there
and it has to be running. So I will go ahead and acknowledge this.
You are going to take most of the defaults here. Now, the first thing
here we have to do is install the SDK, this Software Development
Kit. And you may or may not be prompted
for things like where do you want to put this?
And what's the name of the Default Server? Yeah, I am going to, I am going to
take the Default here, Program Files PIPC. The only
restriction about where you put the SDK
is do not put it in the same Directory as the PI Server. That's not
supported. I will go ahead and just assume the default.
As you can see, it already picked up my Default Server Name.
That's the name of my PI Server. It is the same
name as my AF Server, you will notice later on. I am
putting the PI Server on the same machine that's running the
AF Server, just for simplicity. But, it does not have to be like
that. Now, if there's anything running
right now that needs to be shut down, we are going to go ahead and warn
you about that at this point.
I will just go ahead and acknowledge to continue with the Server Install.
Yeah, this is where we
have the option of where we are going to be
finding that License File. So,
I get to specify where it is. In my case, I
had put it in a different Directory.
Yeah, there
it is. So, I will go ahead and just identify the
Directory. We cannot proceed with the Install if that License
File is not there. As I mentioned earlier,
the AF Server does have to be available to you on
the network. The AF Server is, in fact,
on the same, the same computer that I am installing it on.
So, I will go ahead and initiate a connection just
to verify that it's there and it's running.
And,
once we get that Success Message, I will go ahead and click on Next.
Now,
this is an issue for -- may be an issue for those
of you who have, or been -- are upgrading from previous versions
of PI. The -- what, what to do with the Module
Database. AF is our Asset Framework.
It's our Asset Database. But, it's not our first. We had one called
The PI Module Database that's been used for
years by customers to get, you know, huge
value of doing Asset Relative Displays
Calculations, that type of thing.
We do support the older
Asset Database, Module Database, in
AF. In fact, what you can do is just move everything into
AF and then, basically, AF becomes your new Module Database.
And even, you know, it's synchronized in, in such
a way that anything you do to AF or
anything you do from that point forward, is going to go ahead
be propagated so that all the Clients that
require Module Database are going to be aware of the changes you have
made. Now, that's described in, in a lot
better detail than what we are going to do in this
particular video in a webinar
that I would like to point you to. If you go out
to our website
and look under Webinars, that's going to be under Resources
and then Webinars. There's a
series called the "Show Me How" Webinar Series
in which we have presented just a variety of important topics
for customers. Now, these Webinars are
only available to those of you who are on our SRP,
our Technical Support Agreement, and this
particular Webinar is all about the move from
Module Database to AF. So it's a nice
hour-long description of exactly
what your options are with regard to moving to the new
structure, to the new AF structure from the Module
Database. Now, for those of you are doing brand new
installations, like I am here, there is nothing to
really recover, so we are just going to choose No. But,
if you do have something to recover, we do run an automatic
it's kind of a wizard that's going to step you through
some of the choices you have and how,
you know, how you are going to move that Asset Database from the old structure
to this new AF Structure. I will go ahead and say No, and
acknowledge that.
Now, this is just my use...user information.
I will just choose the defaults on that. And now, this is where
we are going to be putting PI. Typically, the Pi Server's going to be
in a PI Directory. We have,
traditionally, over the years, have organized it underneath
Root. But, as you can see, nowadays in this
installation, it's going under Program Files, so just go
and accept the default. Now, one suggestion I would
have for the PI Server is you try to keep it off of any
drive that's actively doing, you know, the
kind -- has, has the swap disc that you
might use for your Operating System's Memory Management, so
you know, typically C: is going to be the same drive that's got
your swap files on it, you know, your Memory Management
for the Windows Operating System. And,
so, if you had a Drive D then it would be a good idea to put
that, put PI on that Drive D.
So it's not competing for resources with your Memory Management.
Now, there's this new option
in PI Server 2010 to disable the traditional
PI Server Passwords. PI Server Passwords --
we, you know, we have determined over the years
there are some vulnerabilities to making use
of the PI Server Passwords. When we
originally came up with our PI Server Security,
you know, we basically -- I think we did this about nine years ago --
it was a, a proprietary algorithm
for implementing security. And, of course, it has not
benefited from all the advances we have seen in security
that, that Microsoft and others have brought to the table.
So, one of the things
we do suggest -- we do have full support for Windows Integrated
Security or we, we can do
security basically using the concept of PI Trusts,
which we will discuss later in the class. But,
one thing we give you the option to do is just disable
these passwords, these, you know, these imperfect
passwords built on a technology that really is not
state-of-the-art when it comes to
security. And, so,
in this case, I would suggest -- we do encourage you, yes, go ahead and
disable Passwords.
Unless you have got a, a huge install
base and you are doing an upgrade and, and you are afraid that you do not have the
time or the energy to do a
proper transition from Passwords to Trusts
or from Passwords to Windows Integrated Security,
then we suggest, you know, unless there's a --
that's the situation, we suggest you do disable these, these
passwords.