Introducing NightWatchman Enterprise 7.3
How it works
Quick starts, evaluations and pilots
Working with NightWatchman Enterprise
Specifying a data source
The tiles require data sources to display anything useful. The data sources must be added to the
DataSources.xml file in the Enterprise View\Dashboard.Web\Source directory. By default the
DataSources.xml file contains four data sources: Dashboard, NightWatchman, NightWatchmanServer and LOCAL.
The Dashboard data source relates to the Enterprise View settings, the NightWatchman and NightWatchmanServer relate to the data held by NightWatchman Management Center and NightWatchman Server Edition products. The fourth default data source called LOCAL refers to a local directory where you can store and retrieve XML data.
Data source types
There are two data source types, SQL and XML. XML data sources refer to XML format files held locally in the Enterprise View\Dashboard.Web\Source\LocalData directory. SQL data sources must have their SQL connection information defined.
Using your own database
If the database you are using as a data source is local to the Enterprise View website you need to add NT AUTHORITY/NETWORK SERVICE to the database users and grant that account the appropriate permissions for any specific tables you want to use in the database.
If the data source database is remote you need to add the machine account for the computer hosting the Enterprise View website. This will be 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.
For example, given a server called ACMESVR030 running on the domain ACME, you need to add the following machine account as a user on the database:
Creating an SQL data source
When creating an SQL data source, you need to specify the connection string to the database. This includes the server name, the database and configuration settings for the connection.
For example to create a data source for an ACME database residing locally to the Enterprise View website you would add the following to the
DataSources.xml file as a new element of the
The XML LOCAL data source
If you want to use an XML file as the input data source for a tile, use the LOCAL data source already defined. All data files should reside in the folder, relative to the Enterprise View installation directory:
When specifying the command in the tile using the LOCAL data source, give the name of the file (see above) containing the data.
Defining an XML data file
The XML data file needs to obey the following format. The file must start with the
xml version and encoding tag:
There must be a single
<Result></Result> tag which contains all the rows of data. Each row of data must appear in a
<Row> tag. Each column in the row must be defined as a number of
column/value pairs separated by spaces in the following format:
For example, the following shows an XML data file representing a four column data table where the columns are named Id, Month, PCSaving and ServerSaving.
XML format tile definition file
The contents of the tile definition file must start with the
xml version and encoding tag:
The tile definition must be placed in the
<DashboardTile></DashboardTile> tag. The attributes for this tag lets you define general attributes for the tile, including the schemas for any presentation elements the tile definition uses and the tile's title, description and type. The following parameters can be set in the
|Activator||The activator specifies how data is actively retrieved for the tile. Each activator corresponds to the tile presentation elements that will be used in the tile. There are four supported activators to choose from but only one can be set per tile. The activators and corresponding presentation elements are:|
|Description||Description for the tile as it appears in the configuration page of the Enterprise View website.|
|RefreshFrequencyMins||Duration (in minutes) between refreshing the data in the tile.|
|ThumbnailSource||Icon for the tile as it appears in the configuration page of the Enterprise View website.|
|Title||Title for the tile as it appears at the top of the tile and on the configuration page of the Enterprise View website.|
|Type||Must be Standard to enable the supported presentation elements described below.|
The schema definitions that are required to allow particular components to be used in a tile definition. Each
Each tile command is used to gather information from a particular data source. You can have a number of commands defined in a single command collection each referring to the same or a different data source. All the commands must be placed in a single
<CommandCollection></CommandCollection> tag, usually as the first element inside the
The command definition must provide the name for a data source defined in the
DataSources.xml file and an identifier that will be used to run the command in a presentation element. The command identifier must be unique within the tile definition but this is not checked by Enterprise View – you will need to ensure this is the case.
Each command must be defined using the
<Command></Command> tag using the following format:
CommandID is the data source and command identifier respectively and
Command... is the command to run.
It is usual, though not required, to put the command definition in a
CDATA statement. This allows XML reserved characters to be used in the command without the need for escape characters.
For example, the following command uses the ACME data source and selects the Rating and Number columns from the
dbo.UserSatisfaction table in the database the ACME data source references. The command would then be used in a presentation element by referring to the ACMECMD identifier.
These commands always use the LOCAL XML data source and the command definition always consists of the name of the file containing the required data.
For example, the following command references the
DepartmentCost.xml file which must be located in the LocalData directory. The command is then used in a presentation element by referring to the DEPTCOST identifier.