There are many prompts that are going to appear
as you do the installation.
You can just see them listed here. This is all of the information
that you are going to be asked for. And we will cover those as we actually
see the installation. So let's go ahead and
do a sample installation. Let me go ahead
and switch over to Windows Explorer.
And what I have done is created myself a directory
called PISource and that's where I put the things
that I downloaded off of the website in order to
do the installation. The majority of customers these days
are downloading all this off the web. But of course you
may have removable media like a CD
So I am going to go ahead and run this installation.
And as that unzips,
I should point out that
PI is going to be put, by default, into the root
directory. It will be c:PI
And there we go. And I will
go ahead and I am ready to run the installation.
And as most installation program do,
this is going to tell you what's already been installed
and what has not yet been installed. You can see a list of those things
that will be installed--
Sample interfaces and just a variety of services etc.
So I will go ahead and acknowledge.
And when you go to the install program, it recommends that we close all
Window applications and it's a good idea.
Now this is going to be put... We are being
prompted at this point for the location of the license file.
And I had located
on my particular license file
in this directory right here, the PISource directory.
So I will just go out and specify that is where the
license will be found during this particular installation
in the PISource directory.
And when you click on Next, you are going to be
prompted for registration information. And
normally people do not put personal information,
just information for your company. And the serial
number... If you have gotten this shipped
via the mail, you should have this as part
of your packing list. If you do not know what your serial number
is, then just put in a zero. This is also sometimes called the Server Number.
If you do not know that, you can also contact your
sales person or technical support
and they will get that for you.
I click next and this is the default directory
as I mentioned. This is going to
go into the... This is looking at the D: drive so I
think I am going to go ahead and put this on my C: drive.
And some people choose to put
PI on a different drive than their
Operating System. Sometimes that can help performance.
Let's go ahead and put it on which ever drive, though it has to be a local drive.
At this point you get to choose
whether you are going to install the
default points or not. The default points are great for
testing. These are points such as... Well you
might have seen these before. You may have seen
these when we are running testing
or webinars or training.
Sinusoid, CDT158, CDM158. These
are just kind of standard tags that would ship
in each system. I just typed them here-- maybe
you can recognize those from my demos.
They are great little points to have just for
troubleshooting purposes. So for example,
we'd like to leave them on there
because if you have got a problem looking at archive
data and you recognize that these
tags are viewable but the other tags,
the realtime data, are not viewable. That's a pretty
good indication you probably have a problem with your interface
and not a problem with your archives. So we suggest
that you keep that check. And we also
do suggest that you startup PI
when the Operating System starts.
By checking that, this will make these
autostart services that will startup when the Operating System boots.
And let me go back just for a
second and remind you that
you may find that there are extra screens that show up on your
screen that you do not see right here. For example during my server setup, it did not
ask me where to install the PI SDK.
That's because I already had PI SDK based
applications installed on this computer. If you do not,
you are going to be prompted to do
so. And normally what we suggest people do is they put
the PI SDK into Program
FilesPIPC. That's normally where
the PI SDK is going to be installed.
So if you get that prompt, that's the proper way to
answer that. We have just answered this prompt and we move onto
the next one which is where we specify the path
of the archives, the PI Archives. And for that we suggest you just
default to PIDAT
Now if you do have a very large
hard drive,
drive E: just for the sake of putting archives on it.
You can go ahead and switch it over to that
and put this into a different directory called
PIArch or something like that. That's fine too. It just
defaults here and that's a fine place to put. But if you have
other places to put it, that's not a problem. Just
make sure you do not go off to a
network drive somewhere. That's certainly not recommended.
Now as to the default archive size,
you will notice that it defaults to 128MB.
We do not really suggest anything
hard and fast. In fact if you look at our
notes in the Powerpoint slides, what you will see
is that we suggest you go off to our website
and on our tech support website, there is a
section in the knowledge center called System Manager
Resources, Archive Sizing. And it is there
that you will read that we suggest
that you do between
10KB to 100KB per PI Tag.
That's a huge range. So really your
mileage will vary tremendously
or your performance will vary tremendously
depending on the type of data compression
you are doing. So we do not think it's a good
idea to come up with hard and fast rules of thumb for archive
sizing. Suffice to say, the system is flexible
enough that if you do have unusual
needs, we can accommodate that with sizing.
The one rule is do not make these too big
as that will slow them down slightly.
The rule is 10-100KB per 1 PI Tag.
The advanced button takes you
to another screen where you can
specify the location of the event queue.
Now we have not discussed that yet, the event queue comes later
in the class. But this snap shot event queue
is a temporary holding place
for data that for whatever reason is not
making it into the archive. And technically
if you were put this on a different
disk drive for example. If you have got a drive F:
and I locate it there. Technically
we could actually if the archive process for some
reason fails, we could continue to put
data into that event queue
file while the archive process has failed.
So for example, if your archives are on drive E:
and this is on a different drive, and if drive E:
failed, as long as PI itself is not located on drive
E:, that actually could work.
Typically people put this all on the same
drive but you do have a flexibility. Just to put this in
perspective, we did not have this choice in previous versions of
PI. And it did not affect people a great deal but it is an extra
flexibility that we wanted to build into the system in case you
did have the flexibility to put
this event queue on a different drive.
Now the event queue sizing, there is a rule of thumb for that.
We simply suggest you make this half the
size of your archives. So again, this is the size
of the file that we flow to
if for whatever reason we cannot write to the archives.
As far as the event queue page size goes,
we do not have any hard and fast rules as to the
size. Defaulting to 1024KB
is fine.
It basically has to do with the size of
the annotations that can be written to the PI archive.
But unless you are doing something very
unusual for annotations, the defaults should just be fine.
And the last thing of course
is to click next and then start the installation.
So what you are going to notice here during
the installation is, there is actually several installations that
go on that we are going to install a variety of interfaces. We
are also going to install that SDK that I mentioned-- PI SDK.
So they will show up as we do the
install, you will notice a couple of different installs kick off.
Now while we are watching this,
let me point out that the system is being installed
in the C:PI directory.
And I should see that that's already been created.
I refresh this screen and there you can see the PI
directory. And within the PI directory, you will find the DAT
directory. That's where we are going to be putting the archives.
We are going to initially create three archives, and they are not there yet.
And in addition, if you recall,
the PI
client applications are going to go under
Program Files and into the sub-directory called PI PC.
So Program FilesPI PC
is where the client and also the
SDK... We were not prompted this time to choose a location
for the SDK because it was already
selected, or it was already installed on this machine.
But if it had not been installed on this machine,
then the default is to prompt you for
a location. And the default location for that
location is Program FilesPI PC.
And if I go back to the
install, you will notice that we are now in the middle of the
SDK. You can see there is a separate install, the SDK install.
You do not have to acknowledge any of the prompts here.
It is simply going to run through these different installs.
Now a random interface,
that's a random simulator that is going to be installed.
And the other interfaces are being installed as well.
Now this install normally takes quite a bit longer than this.
Here is another type of interface, the
PI Ping interface. You will notice that we install five interfaces
in total. We will talk more about them later. But the PI Ping
interface, along with SNMP and PI Performance Monitor,
these are interfaces to help you monitor the health of your system.
And as soon as we are done this, you will get the
acknowledgement that the install has completed successfully.
And as you can see, if we
go back into the PIDAT directory,
you can see that the archives
have been installed correctly.
And now we are ready to do our post installation configuration.