This video demonstrates the steps to configure PI Vision 2020 after installation.
It is divided into the following sections.
First, we want to make sure that the PI data archives and AF servers that
we want to connect to in Vision are listed in our known servers table.
On the PI Vision web server open PI system explorer and click file then click connections.
I’m going to confirm that I can connect to my data archive
by selecting the server and clicking connect. To add additional AF servers click add asset server,
enter the name of the AF server in the host field, click connect
and ok. Similarly, to add PI data archives click add data server,
enter the name of the PI data archive in the host field, click connect and okay.
Next, there are three local user groups that were created when PI Vision was installed.
These groups control who has access to different PI Vision components. Open computer management,
expand local users and groups under system tools and select groups. The PI Vision admins,
PI Vision users and PI Vision utility users groups were all created when PI Vision was installed.
The PI Vision admins group controls access to the PI Vision admin site
and by default contains the user who installed PI Vision. The PI Vision users group controls
access to the PI Vision site and by default contains authenticated users.
The PI Vision utility users group controls access to use the PI Vision display utility,
which is installed with PI Vision or the PI ProcessBook to PI Vision migration utility which
is a separate installation. By default, this group also contains the user who installed PI Vision.
To add domain users or groups to a PI Vision local group double-click the group, click add, enter the
name of the domain user or group account, click check names then click ok and apply.
To remove existing users or groups from a PI Vision local group,
double-click the group, select an existing member, click remove and apply. Be sure to
update all of these PI Vision local groups with your necessary domain users and groups.
Next, we will check the SQL permissions before attempting to create the PI Vision SQL database
automatically. On the SQL server, open SQL server management studio and connect to the SQL server
instance. Note the SQL server instance name, which will be needed for the PI Vision admin site. The
full name will be located at the top of the object explorer pane, and it might end with SQL express.
Next verify that this SQL server has allow triggers to fire others
set to true. To check this right click the SQL instance and go to properties.
Under advanced confirm that allow triggers to fire others is set to true.
Additionally, the user accessing the PI Vision admin site must have
specific permissions on the SQL server to be able to create the PI Vision SQL database.
Expand security, logins, right-click the user account and select properties.
Click server roles and confirm that the db creator server role is selected. Alter any
login permission is also required which is given to users who have the security admin server role.
After verifying that my user account is in the PI Vision admins group
and has the appropriate permissions on the SQL server, we will navigate to the PI Vision admin
site on the PI Vision web server. Right click the web browser and select run as administrator.
Then enter the PI Vision admin site url.
By default, the PI Vision admin site will be located at https colon slash web server slash
PI Vision slash admin where web server is the name of the PI Vision web server. Alternatively
open IIS manager, expand sites, the site where PI Vision is installed, in my case default website
PI Vision and select admin. In the actions pane click browse https.
Note that navigating to the PI Vision admin site via IIS manager will use localhost in the url,
which might not be included in the certificate subject alternative name. In the overview page
of the PI Vision admin site click manage configuration next to PI Vision database.
In the SQL server field use the drop-down or manually enter the name of the SQL server instance
to host the PI Vision SQL database which was found in SQL server management studio. In the database
field enter the name of the PI Vision SQL database to be created on the SQL server. Click save to
create the PI Vision SQL database and verify green check marks appear next to the fields.
If you are not able to create the PI Vision SQL database using the PI Vision admin site, you
may create the PI Vision SQL database manually. Please see the run the go.bat script to configure
the PI Vision database section of the PI Vision installation and administration guide for details.
The next step in the PI Vision admin site is to add the data archives and AF servers that we want
to be exposed in PI Vision. In the PI Vision admin configuration page, click the data servers tab.
Here the data archives from the known servers table on the PI Vision web server are shown.
To verify connectivity to a data archive,
click test connection and make sure a green check appears in the status. Select
the allow checkbox next to each data archive to be used in PI Vision and click save.
Next, click the asset servers tab in the PI Vision admin configuration page. To verify connectivity
to an AF server click test connection and verify a green check appears in the connection status.
Select the check box next to each AF database to be used in PI Vision or select the all check box
to allow access to all databases for each AF server. Click save when finished.
Finally click overview to go back to the PI Vision admin overview page and verify green checks appear
next to the PI Vision SQL database, each data archive server, and each AF server.
The last configuration item to set up in the PI Vision admin site
is PI ProcessBook import folders. Click import folder management.
Here we can set up specific folders and the PI ProcessBook displays that are added to that folder
will get picked up and be available to view in PI Vision. Make sure the PI Vision application
pool account has read access to any folder and its subfolders to be added in this page.
To add a PI ProcessBook, import folder enter the folder path in the folder field
and optionally an alias in the friendly name field.
Click add, refresh the page, and verify a green check appears in the folder accessible column.
We have now created the PI Vision SQL database and managed the PI Vision local groups
in addition to configuring data archive, AF server and PI ProcessBook import folder access using the
PI Vision admin site. In the next video we will configure Kerberos delegation to allow users
to access data archives and AF servers using windows integrated security.