Location
  • 03 Oct 2023
  • PDF

Location

  • PDF

Article summary

This information is specific to the latest release of PARCview:

7.2.x


A PARCview location in most cases corresponds to a site. More specifically, it is a list of data sources within a dataPARC configuration database. For customers with multiple sites (i.e. facilities at different physical locations), each with their own configuration database, the location tab can be used to define database connections to multiple locations so that a PARCview client can connect to them. These are called “remote locations”.

Locations can also be used to divide the source list within a single site, though this is mostly organizational. These are non-remote locations.

The Location name is the only configuration required for non-remote locations. The rest of the fields may be required for remote locations.


PARCSecurity Permissions

PARCsecurity Console should be configured for the following permissions for rights to System Configuration elements.

  • DataPARC Admin: Grants administrative access to PARCview.
  • System Config Process Area: Grants access to the Process Area tab in System Configuration.
  • System Config Process Tags: Grants access to the Process Tags tab in System Configuration.
  • System Config Reason/Evidence/Category: Grants access to the Reason, Evidence and Category tabs in System Configuration.


Configuration

Name: Name of the plant. This is used in the TagName to define the location. It is best to keep this name short but uniquely descriptive. No spaces allowed.

Active: Allows the Location to be used in PARCview.

UA Server URI: Address of remote UA Server. Ignored for non-remote locations.

GDS Server: Address of remote GDS Server. Ignored for non-remote locations.

DSN: Although most client connections to SQL are handled by the UA Server, SQL Templates that are configured to “Use PARCview DSN” and PARCserver applications still require a direct database connection as of version 7.0.0.0. PARCcalcConfig and any Excel reports or other applications that make direct SQL calls for the connection string will also need this field. Enter “File Name=” followed by a file path to a .UDL file. The file can be local to the client and the file path can be unique on each client. This setting can be overriden in Site Connection Configuration.

Timezone: The default time zone to use when dealing with source-specific data, and the time zone to use for data that cannot be mapped to a specific source’s time zone, such as time periods.

Remote Location: If checked, this is a remote location, meaning it defines a connection to a dataPARC SQL database other than the one currently being used. The name must match the name of the location as defined in its own database.

Default: Default location selected in PARCview.


Log Files

PARCMessage is a built-in error monitoring software. It creates an ongoing log of errors generated from PARCview on the specific computer where PARCMessage is running in the system tray. The Icon in the tray is a triangle, red if errors are present, and green if there are no errors.

Errors can also be stored in the PARCview install directory both on the server and clients ...\Capstone\PARCView\LogFiles.


Required Server Applications

No server applications are required to use System Configuration.

UA Server: All PARCview vr 7 functionality requires a Universal Access (UA) server.

GDS: All PARCview vr 7 functionality requires a Global Discovery Server (GDS).


Was this article helpful?

What's Next