In the previous video,
we showed you how to install all of the virtual machines and by now you
should have three VMs setup on your host machine. To continue
with our PI system installation, we want to
start with the PI Server. So first we are going to
head to our PI server virtual machine.
All of the installation files that we want should be in the folder that
is shared from our host machine that we setup in the previous
video. The first install kit that we want to run
is the OSISoft pre-requisites kit. But this
will require that .NET framework being installed first.
To install .NET framework on
Windows Server 2008, we want to use the server
manager which is located right next to the start button.
If we go to add features, .NET framework is the
one right at the top. So we check
that box and during the installation we'll keep everything as
the default. Once the .NET framework installation has been
completed, we can proceed with the pre-requisities
kit and the patch. For these installations we will just be using the
default settings. Once we've finished installing the
pre-requisities, the next step in our installation is to
install the SQL database. We will do this by running the
install kit for SQL Express. During the
installation, we will keep most headings as the
default. The important thing to
note is when we get to this page when it shows the named
instance of our SQL database. We want to make sure we remember
this as we will be needing it during the install of our AF server.
When the installation
for SQL Express finishes, we can
go back to our folder and install the AF Server.
During this install it will upgrade
.NET to version 4.0 which will require a
reboot of the system. When the computer
has finished rebooting, we can proceed with the installation
of the AF Server. Once we get to this
screen, we can input the name of our
SQL database that we saw earlier during the SQL Express
install.
After AF has finished
installing, we'll also run the AF
patch which may also prompt you for the SQL
database name. Next in our installation is
our installation of the PI Server.
The installation
will prompt us to find the license file for our
PI Server. Once we browse to the correct
folder where the license is located,
the message at the bottom will display that it has
found the license.
Next is to connect to our
AF Server. So in this field we want to enter the name
of our AF Server and test the connection. Once we
test the connect button, it will show that we successfully
connected to our server.
Here we want
to make sure that we choose to enable
MDB or the module database as it will be
impossible to re-enable it after the installation.
The next step in our installation is to go to the MDB to AF wizard
where we can create a mapping to our Windows
domain account. You'll notice that it says that we have
one missing mapping and that one is
required. So we'll go ahead and add this new
mapping.
Here we will enter the domain account that we'd like to
be mapped.
Once the mapping has been
created, we'll notice that it is
linked to the PI identity, PIAdmins,
so that any time you log into this domain
account, whichever machine you are on will have this
access to the PI Server.
The next step in the wizard is to
choose the database under which the MDB will be synchronized.
Currently we do not have any AF databases, so
we will need to create a new one.
We'll call this database
MDB2AFSync.
Once this database has been created, we can
complete the installation.
Once we finished installing the PI
Server, a quick way we can check the connection is by
using System Management Tools.
Our PI Server is listed on the left hand side
under the servers. Another way to check the
connection is to go to File, and then Connections.
And then checking the box next to the name of our PI Server.
Once we've checked this box,
You can see that we are connected as PIAdmin.
Now that we've finished setting up the PI
virtual server machine, Camille will walk you through the installation of the
interface VM.