Skip to main content

NightWatchman Enterprise 7.3

Installing Enterprise View

Using the wizard

To install Enterprise View using the wizard, run EnterpriseView.msi.

  1. On the Welcome screen, click Next.

  2. On the License Agreement screen, accept the terms of the agreement and click Next.

  3. On the Prerequisites Checks screen, you will not be able to install components that fail their respective prerequisite checks.

  4. In the Custom Setup screen, choose the features you want installed. You must run the installer once for each of the components you want installed separately.

    • Enterprise View Web application – installs its Web components

    • Database – installs the database for Enterprise View

    Click Change to install the components in a different location. They are installed in C:\Program Files\1E\Enterprise View\

  5. On the Website Configuration screen, set the parameters for the Enterprise View website as follows:

    • Website Port – sets the port to be used for the Enterprise View website. This defaults to the standard IIS port 80. If changed from the default, users will need to add this to the URL for the Enterprise View Website, for example http://myserver:8080/EnterpriseView

    • IP Address – sets the IP address for the Enterprise View website.

    • Host Header – sets the host header for the Enterprise View website. This is the server name used to locate the website when users enter the site URL in their browser. In order to use it when it has been set, you will need to have defined the appropriate DNS settings.

  6. In the Database Server screen, set the parameters for installing it Set the Database server that you are installing to: parameter to the server where the database resides. Click Browse... to display a list of server and instances visible from the local computer. The format of the database server identified may be one of the following:

    • (Local) – uses of the local default instance

    • ServerName – uses a remote server using the default instance

    • ServerName\Instance – uses a remote server and named instance using a dynamic port. For this option to work correctly the SQL browser service must be enabled.

    • ServerName, Port – uses of a remote server and instance defined by its fixed port

    Set the Name of an existing or new database catalog: field to an existing database on the database server or a new name. If it is on a existing database server, the Enterprise View tables are created in the existing database. If it is on a new server, a new database is created with the new name and the tables are in that database. Clicking the Browse button will display the existing database catalogs on the selected database server.

  7. On the Ready to Install screen, click Next.

  8. Click Finish.

Post-installation

If you set up an additional host header for the Enterprise View website:

  1. Configure the IIS client access policy to allow cross domain access to the Enterprise View website. This is done via the ClientAccessPolicy.xml file which resides in the IIS root folder, typically c:\inetpub\wwwroot. If this file already exists, append the contents of the ClientAccessPolicy.xml file from the Enterprise View %INSTALL_DIR%\Dashboard.web folder to it. If it does not exist, copy it from the Dashboard.web folder to the IIS root folder.

  2. Edit the web.config file the Enterprise View %INSTALL_DIR%\Dasboard.web folder and modify the service base URI used to access the Enterprise View website.

  3. Locate the line in the file:

    <!-- add key="ServiceBaseUri" value="http://<<HostFQDN>>/EnterpriseView/"/-->

  4. Remove the comments and update the <<HostFQDN>> placeholder with the base URI for your Enterprise View website. For example,

    <add key="ServiceBaseUri" value="http://machineA.acme.com/EnterpriseView/"/

  5. Save the file and test the new configuration by accessing the Enterprise View home page using the host FQDN.

Detailed requirements

A definitive checklist of prerequisites and dependencies you need to meet in order to install Enterprise View.

Component

Product

Notes

OS

  • Windows Server 2016

  • Windows Server 2012 R2

Enterprise View will install on systems running these OSes.

Database servers

  • SQL Server 2017

  • SQL Server 2016 SP1

  • SQL Server 2014 SP2

You must have one of these database servers installed. SQL server must be configured to use a case-insensitive, accent-sensitive collation as the server default (the preferred collation is SQL_Latin1_General_CP1_CI_AS).

Enterprise View will install on these database servers.

If you are using your own database as a data source for the Enterprise View Website and it is local to the Website, you must add NT AUTHORITY/NETOWRK SERICE to the database users and grant appropriate permissions to that account for any specivic tables you want to use.

If it is remote, you must add the machine account for the computer hosting the Enterprise View Website in the format: <DOMAIN><MACHINENAME>$ where the <DOMAIN> is the domain where the host computer is running and <MACHINENAME> is the name of the computer hosting the Enterprise View Website.

Runtime libraries

  • Silverlight

This runtime library is required.

Installation and service accounts

To install Enterprise View, you will need the following accounts.

Installation account

  • Must be domain user account

  • Must have local admin rights on the server where Enterprise View is being installed

  • Must have sysadmin rights on the SQL Server instance, unless the EnterpriseView database is pre-created by a DB administrator. This right can be temporary.

For a default installation, the programs and files associated with NightWatchman Management Center are created in C:\Program Files\1E\NightWatchman Management Center

In this section: