San Leandro, California This book is a work in progress. Please bear Starting with PI release (), migration tools became. San Leandro, CA USA Any trademark that appears in this book that is not owned by OSIsoft, Inc. is the property of its owner and use (use of PI ICU or PI SMT is Shutdown of PI subsystem pibufss in progress. San Leandro, CA USA. Tel: (01) BatchView, PI Vision, PI Data Services, PI Event Frames, PI Manual Logger, PI ProfileView, PI. WebParts Directory runs is called the Domain Controller. Group Questions – Identify the role of Data Archive subsystems Run piartool –al to see the progress of archive shift.
- PI Interface for Performance Monitor Version x
- SLHS Physics OSIsoft Energy Project
- System Administration Schools and Certifications
- 188.8.131.52. Insert an Excel OLE Object into ProcessBook 2.1
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, mechanical, photocopying, recording, or otherwise, without the prior written permission of OSIsoft, LLC. All other trademarks or trade names used herein are the property of their respective owners.
Supported Features Command Line Parameters Error and Informational s Performance data providers supply data from services or other applications, which can start and stop at any time.
By default, the interface connects to its providers during startup, which means it does not detect providers that become available after it starts.
To enable the interface to detect data providers that start after it has performed its initial scan, you can configure the interface to periodically unload and reload data providers at a specified frequency, which imposes some overhead but enables it to detect newly-arrived data providers.
The interface can collect performance data from the local host and from remote providers. It can run on the same computer as the PI Server to which it sends performance data, or it can run on a different computer.
The interface supports three different PI tag configurations: Data tags: Send data from a performance counter to a PI tag. Status tags: Sends the state of the performance counter to a PI tag. Examples: performance counter offline, performance counter not running Latency tags: Reports in milliseconds how much time it takes for the interface to request and receive performance data from a machine for a specified scan class.
How the PI Interface for Performance Monitor Works To monitor performance, the interface reads Microsoft Windows performance counter data from each machine being monitored at frequencies specified by the scan classes configured for the interface instance. After the performance data from a counter is received and calculated, the interface writes the data to the PI point that contains the corresponding performance counter path in its Extended Descriptor attribute.
The interface includes definitions for a set of digital states that are assigned to status tags to indicate whether the interface has encountered problems collecting performance data.
The interface also logs such errors. When the interface starts, it creates a worker thread pool that connects to local and remote machines and gathers performance data from them. The default number of threads is 10, the minimum is 1 and the maximum is This setting is critical for successful interface runtime behavior in cases when one or more remote machines goes offline.
As a general rule, if the interface is configured to monitor machines, and you anticipate that 10 of them might go offline at the same time, set the number of worker threads to 12, to allocate 10 for each offline machine plus two to dispatch the remaining 80 online devices. This setting can vary greatly, depending on the number of PI points loaded for each machine, the number of scan classes and their frequencies. After initialization, the interface connects to the target PI Server and locates the PI points that have a PointSource attribute matching the PointSource parameter configured for the interface instance.
After the interface finds all PI points with the matching PointSource, it tries to load them one by one, checking additional tag attributes as follows: Scan is enabled Location1 matches the interface instance ID Location2 is 0 for data and status tags, 1 for latency tags Location4 specifies a valid scan class Data type is digital or numeric Extended Descriptor contains a valid performance counter path for data and status tags or, for latency tags, [LATENCY:computer].
PI Interface for Performance Monitor 7. Connect to the computers being monitored, retrieve performance counters configuration data from them, and initialize the loaded PI points. Put the request for performance data for a device in a worker thread, process returned data, and make it available for writing to the PI Server.
Try to reconnect to any unreachable remote machines. Check availability of performance data for each PI point and write data to the PI point value and status. The interface writes values directly to the PI Server unless buffering is enabled for the interface, in which case data is buffered and written to the PI Server by the buffering subsystem. Check for tags that are added, edited and deleted and revise the internal tag list accordingly.
Remove any unused machines from the interface if all its points are removed or deactivated. By default, the interface establishes an initial connection to the target machines and only attempts to reconnect if a connection is lost. As a result, if other PI interfaces are started after the interface starts, the interface cannot detect and load points for the newly-started interfaces.
To enable the interface to detect interfaces that are started after normal data collection begins, you can run the interface in extended mode.
In extended mode, the interface periodically unloads and reloads data providers, enabling it to detect newly-started interfaces. To minimize overhead, you can configure how often the interface unloads and reloads data providers using PI ICU. Note the following limitations: In defining performance points, you cannot mix addressing conventions when specifying the target computer.
Use the same method either IP address or host name for all points that you configure to monitor the computer. Mixing addressing modes can cause the interface to stop collecting data. Do not run two instances of the interface in extended mode on the same computer to monitor the same remote devices.
In extended mode, the interface periodically closes and reopens connections to the remotely monitored device. If two instances are periodically reconnecting to the same computers, one instance might incorrectly report the target computers as being offline.
Configuring the PI Interface for Performance Monitor This chapter provides detailed instructions for configuring the interface. A minimum functional configuration is described, which you can adjust according to your requirements. Before installing and configuring, verify that the PI Server is up and running. If you want to install it on a computer other than the PI Server node, download the installer from the OSIsoft web site and run the installer on the desired computer.
PI Interface for Performance Monitor Version x
Ensure that the computer where you install the interface has network access to both the PI Server and the computers that you want to monitor. This guide assume you are running the interface on the PI Server node.
SLHS Physics OSIsoft Energy Project
Prior to PI Servera basic version of the interface was installed, limited to 32 ponts. As of PI Server and later, the full interface is installed, removing this limitiation. If you are running the basic version and want to upgrade to the full version, refer to the PI Server release notes for instructions. PI Interface for Performance Monitor 9. Settings are specified as command line parameters.
To create an instance of the interface, perform the following steps: 1. ICU displays the settings of the new instance of the interface. On the General tab, edit the basic settings as follows. Note that, when defining scan classes, you can spread the server workload using offsets, to ensure that all scans do not occur at the same time. To configure interface-specific settings, click PIPerfMon. On this tab you can enable debugging and override the default thread count for the interface.
After configuring the desired settings, click Apply. PI ICU displays a command window and invokes the startup batch file, and you can observe progress as the interface attempts to initialize and run. Watch log for messages indicating success or errors. To stop the interface, close the command window. The right pane lists the digital state sets defined for the PI Server. Right-click the server and choose Import from File. The Import Digital Set s dialog is displayed.
System Administration Schools and Certifications
To dismiss the dialog, click Open. Verify that the new digital state set is added to the server s list. To dismiss the dialog, click Close. To ensure that buffering is running when the interface starts, click bufsrv pre 3.
If prompted, update service dependencies. Set Startup Type to Auto. Click the Create button.
184.108.40.206. Insert an Excel OLE Object into ProcessBook 2.1
To start the service, click. To verify that the service is created and is running, launch the Windows Administrative Tools Services control panel and verify that the service is listed. To ensure that the interface restarts when its host computer, configure it as a Windows service. To configure the service, go to the PI ICU Services tab and enter the required settings, then create and start the service.
By default, the service runs using the Local System account.
To be able to collect performance data from a remote machine, the account associated with the service must have administrative privilege or be a member of the Performance Monitor Users group on the remote machine. If this account does not have privileges to obtain performance counters on a remote computer, specify an account with sufficient privileges. To configure the account for the service: 1. Launch the Windows Services control panel. Right-click the Performance Monitor interface service and choose Properties.
The Properties dialog is displayed. Display the Log On tab, enable This account and enter the user name and password for the account.
To save your changes, click OK. PI Interface for Performance Monitor Configuring PI Tags for the PI Interface for Performance Monitor A Windows performance counter provides information about the performance of the operating system, an application, a service, or a driver. A PI tag also called a PI point is a time-stamped record of a single set of measurements for example, tank temperature. If you misconfigure tags, the interface cannot correctly transmit the data to the PI Server.
A performance monitor tag is associated with data from a single performance counter. The interface supports the following point configurations: Data points Latency points Status points Note: The Performance Monitor interface includes the PIPerfCreator utility, which retrieves performance counter information from a selected computer and creates the corresponding PI data points.
In addition, PI System Management Tools includes a feature that enables you to browse performance counters and selectively create the corresponding points. For details, see Automated Tag Creation. The followings sections describes these configurations in detail. Data Points Data points contain calculated performance data.
To map a data point to a performance counter, enter the performance counter path in the PI point s Extended Descriptor attribute, using the format defined by the Microsoft Performance Counters specification.