PI Web Services 2012 Release Notes

Transcription

2

3 Table of Contents Overview... 1 Fixes and Enhancements... 1 Fixes... 1 Enhancements... 1 Known Issues... 2 Setup... 3 Operating Systems... 3 System Prerequisites... 3 Server Platforms... 3 Distribution Kit Files... 4 Installation and Upgrade... 5 Upgrading PI Web Services... 6 PI Web Services IIS Edition configuration and installation... 6 Verify PI Web Services IIS Edition Installation Hosting PI Web Services as a Windows service Uninstalling PI Web Services List of Files Installed During Setup Documentation Overview Technical Support and Resources... 18

4

5 Overview PI Web Services 2012 is an incremental release of PI Web Services, a product designed to provide web service access to PI System data. PI Web Services 2012 has added the capabilities to search for PI Asset Framework (PI AF) element templates, PI AF elements and attributes, and PI event frames. The web service is a Windows Communication Foundation (WCF) service that allows web service clients to access PI System data through Simple Object Access Protocol (SOAP). PI Web Services supports writing of data to the PI System as well as retrieval of standard PI summary calculations. PI Web Services is designed for lightweight, firewall-friendly data access over LAN or WAN and facilitates two main scenarios: Development of thick or thin/web applications, in various programming languages and on various operating systems Integration of PI System data within other Line-of-Business Systems, such as ERPs and data orchestration engines PI Web Services belongs to the OSIsoft PI Data Access family of products, which is designed to support implementation of custom applications on top of the PI System, as well as integration of PI System data with other applications and business systems. For more information on other PI Data Access products and details on the licensing specific to these products (e.g. development vs. runtime), please contact your account manager. Fixes and Enhancements Fixes Fix for an issue where the IIS Application Pool hosting PI Web Services could become disabled due to unhandled failures Fix for an issue where aggressive caching caused unintended memory usage spikes Enhancements Incremental performance improvements Search for PI AF elements, element templates, and element attributes, improving access to time-series data in an asset-centric way Search for PI event frames, including the ability to navigate to referenced elements and their attributes in order to obtain time-series data Support for writing to AF and event frame attribute paths Support for reading data from event frame attribute paths Support for requesting interpolated time-series data by time interval (StartTime, EndTime, TimeStep), in addition to requesting it by number of interpolations (StartTime, EndTime, NumInterval) PI Web Services 2012 Release Notes Template Version 2.1 Page 1

6 An improved installation experience in both IIS and Standalone editions PI Web Services IIS edition now automatically registers the.net Framework v4.0 with IIS during setup, eliminating the need to do this manually after installation PI Web Services IIS edition now automatically creates a dedicated IIS Application Pool with identity of Network Service, eliminating the need to do this manually after installation PI Web Services Standalone edition now automatically creates a port reservation during setup, eliminating the need to this manually after installation A change to the default value for the configuration option that controls the display precision of floating point values Known Issues When using integrated Windows authentication (Kerberos), the process account for PI Web Services must be trusted for delegation when performing PI AF element, element template, or element attribute search or retrieval. See the topic Configure Kerberos authentication in the PI Web Services user guide for configuration instructions. Filter expressions are not supported when calling GetPIArchiveData with the RetrievalType property of PIArchiveManner set to PlotValues, or for any call to GetPISummaryData. Filters are also not supported for AF paths. PI Filters in PI Web Services use a filter type of RemoveFiltered, which means that no information related to filtered values is returned in the results. This deviates from the default behavior of PI SDK, which adds events with a value of Filtered at filter boundaries to aid in the detection and presentation of filtered data that has been omitted from the results. Summary and interpolated retrievals incorrectly calculate the duration when the time range spans a Daylight Saving Time (DST) transition and local, i.e., not UTC, times are used. Calls to GetPIArchiveData (interpolated) and GetPISummaryData will be off by the amount of the DST transition. When the time range is shorter than the transition offset (typically one hour), the call will fail with the error "The time string contains extra unexpected characters." and a time duration beginning with "+-". If such retrievals are desired, OSIsoft recommends the use of UTC (time ending with Z ) time specification. When calling SignUpForPIUpdates with an unresolvable AF or EF attribute path, no error code is returned. Subsequent calls to GetPIUpdates using the generated update ticket will contain an update with value No Data from that particular path. In addition, since No Data is returned instantaneously, the effect of the maxwaitforupdates parameter will be subverted. PI Web Services may be installed on a server which also hosts Microsoft SharePoint (and possibly PI WebParts). However, OSIsoft recommends that a web site and application pool that are not under the control of Microsoft SharePoint, be created prior to installation. The web site should execute under the new application pool, and the web site should be selected as the host for PI Web Services during installation. PI Web Services 2012 Release Notes Page 2

7 Setup Operating Systems This release supports, in order of preference: Microsoft Windows Server 2008 R2 (Full Installation or Server Core) Microsoft Windows Server 2012 (Full Installation or Server Core) Microsoft Windows Server 2008 (Full Installation only) Microsoft Windows Server 2003 In addition, the following operating systems are supported for development and testing only: Microsoft Windows 8 Microsoft Windows 7 System Prerequisites.NET Framework 4 must be installed. You can download.net Framework 4 from PI Web Services is generally hosted in Microsoft Internet Information Services (IIS), version 6 or later. PI Web Services can also be run in a standalone manner, specifically as a Windows service outside the context of IIS. When using IIS, it must be installed with the features described in the setup instructions below. Server Platforms PI Server 3.3 or later (PI Server 2012 recommended) AF Server 2.1 or later that includes PI SQL for AF Server (AF Server 2012 is recommended). If you will use PI Web Services to access PI AF 2.1 or earlier, verify that PI SQL for AF Server is installed on the AF Server. When present, PI SQL for AF Server is listed in the Windows Add or Remove Programs list. The PI SQL for AF Server setup kit is available at the OSIsoft Technical Support Web site. PI Web Services 2012 Release Notes Page 3

8 Distribution Kit Files The PI Web Services 2012 Distribution Kit contains the following files: AFClient_x64_2012.msi AFClient_x86_2012.msi dotnet35setup.dll dotnet40setup.dll en_visual_c++_2010_sp1_redistributable_package_x64_ exe en_visual_c++_2010_sp1_redistributable_package_x86_ exe MSRuntimes.msi MSRuntimesSetupVS2010SP1_x64.dll MSRuntimesSetupVS2010SP1_x86.dll MSRuntimes_x64.msi MSVC9SP1x64Redistrib.dll MSVC9SP1x86Redistrib.dll osilogow.jpg PI Web Services 64.msi PI Web Services Standalone Edition 64.msi PI Web Services Standalone Edition.msi PI Web Services.msi pi.ico pibufss.msi PIOLEDB.msi PIOLEDB64.msi PIOLEDBEnterprise.msi PIOLEDBEnterprise64.msi pisdk.msi pisdk_x64.msi PIWebServicesIniFiles.xml Setup.exe Setup.ini SetupFileGenerator.exe SetupUtils.dll Setup_silent.ini Setup_standalone.ini Setup_standalone_silent.ini vcredist_x64.exe vcredist_x86.exe PI Web Services 2012 Release Notes Page 4

9 Installation and Upgrade Before you install PI Web Services 1. Verify the system you plan to use has the user accounts required for PI Web Services. Note: The PI Web Services setup kit checks for the minimum system requirements. If the setup kit cannot verify the requirements described here, the installation will fail. 2. Verify that the server that runs PI Web Services includes: Windows Server 2008 R2, Microsoft Windows Server 2008 with Service Pack 2, Windows Server 2003 with Service Pack 2, or Windows Server 2003 R2, Windows 7, Windows Server 2012, or Windows 8. Note: For all operating systems, you must be logged in as an administrator if you run the PI Web Services setup kit. Microsoft Internet Information Services (IIS) for Windows Server that is enabled to use the Windows features described in PI Web Services IIS Edition requirements. Note: The PI Web Services setup kit contains both the 32-bit and 64-bit version of PI Web Services. The setup kit installs the appropriate version based on the operating system that you use. 3. Verify that the server that runs PI Web Services has network access to one or more of these OSIsoft servers: PI Server 3.3 or later PI AF server 2.1 or later that includes PI SQL for PI AF server Note: To search for PI event frames, you must use PI AF server 2.4 or later. After you finish If you are upgrading PI Web Services, see Upgrading PI Web Services. For details about how to use the PI Web Services setup kit, see PI Web Services Edition configuration and installation and Host PI Web Services with a Windows Service. If the server you use also runs PI WebParts, see Host PI Web Services on a PI WebParts server in the PI Web Services User Guide. For information about how to configure security settings on PI System servers, see the sections Secure access to PI Server data and Requirements to secure access through PI Asset Framework in the PI Web Services User Guide. PI Web Services 2012 Release Notes Page 5

10 Upgrading PI Web Services PI Web Services upgrades should follow the steps as above, with the following notes: You may only upgrade to a like edition of PI Web Services. For instance, upgrading from PI Web Services 2010 R3 IIS edition to PI Web Services 2012 Standalone edition is not supported. You can only choose a new installation directory if you are installing PI Web Services for the first time. If you upgrade, the setup kit installs PI Web Services in the directory used for the earlier version. During upgrade of PI Web Services IIS edition, any customized settings applied to the IIS Virtual Directory containing PI Web Services will be erased. In upgrade scenarios where the IIS Virtual Directory has had custom settings applied, OSIsoft recommends that the user manually audit the Virtual Directory s settings prior to upgrade, and reconfigure the Virtual Directory subsequent to the upgrade s completion. Previous versions of PI Web Services IIS edition asked the user to select an IIS Application Pool to use. PI Web Services 2012 automatically creates a new IIS Application Pool named PIWSAppPool. On upgrade, the IIS Virtual Directory selected for PI Web Services installation will be reconfigured to use the PIWSAppPool Application Pool. An upgrade of 32-bit PI Web Services 2010 R3 Standalone edition due to a known issue in that prior release. OSIsoft recommends that 32-bit PI Web Services 2010 R3 Standalone edition be uninstalled before installing PI Web Services This issue does not affect 64-bit PI Web Services 2010 R3 Standalone edition, or any IIS edition of PI Web Services. The default value for the FloatPrecision configuration parameter has changed in the PI Web Services 2012 release from the previous value, DisplayDigits, which references the PI Point configuration. For backwards compatibility purposes, the previous value will be maintained on upgrade. See the topic Properties to control PI Web Services features in the PI Web Services user guide for more information. PI Web Services IIS Edition configuration and installation PI Web Services IIS Edition is hosted by Microsoft Internet Information Services (IIS) for Windows Server. The web server on which you install PI Web Services must include: A website to host PI Web Services. The PI Web Services setup kit will create a default website in IIS. If you do not want to use the default website: You must designate a website to host PI Web Services before you run the setup kit. PI Web Services 2012 Release Notes Page 6

11 You can set up this website when you install PI Web Services by selecting the location of the website root directory and naming its virtual directory, or selecting the default. To customize the root directory, use the IIS Manager Add a New Web site feature before you install PI Web Services. Verify that the web server that hosts the website has folder and registry permissions that are compatible with PI Web Services. When PI Web Services is hosted on a Microsoft Internet Information Services (IIS) for Windows Server, the web server that hosts PI Web Services must be configured to include the settings listed here. Note: If the server you use does not have these IIS features activated, the setup kit will fail. ASP.NET.NET Extensibility ISAPI Extensions ISAPI Filters for.net Framework 4 IIS 6 Management Compatibility IIS 6 WMI Compatibility IIS 6 Management Console If you are using Windows 7, you must also enable these settings: Default Document Static Content Refer to these topics for details about how to configure IIS, based on the Microsoft Windows operating system version, and then install and verify that PI Web Services is ready to use. For additional information about post-installation procedures, and security configurations, refer to the PI Web Services User Guide. Install and configure IIS on Windows Server 2003 Before you run the PI Web Services setup kit, the Microsoft Windows Server 2003 that you use to host PI Web Services must be installed and configured as described here. 1. Click Start, point to Control Panel, and then click Add or Remove Programs. 2. In Add or Remove Programs, click Add/Remove Windows Components. 3. In the Windows Components Wizard, under Components, select Application Server. 4. Click Next. 5. After the wizard completes the installation, click Finish. 6. Verify that an ISAPI extension for.net 4 is enabled. Change this setting if required. PI Web Services 2012 Release Notes Page 7

12 Configure IIS Application Server settings 1. Choose Start > Control Panel > Add or Remove Programs and click Add/Remove Windows Components. 2. In the Windows Component Wizard, under Components, select Application Server and click Details. 3. In Application Server dialog, verify that Internet Information Services (IIS) is selected: 4. Select Internet Information Services in Application Server and click Details. 5. Verify that Internet Information Services Manager and World Wide Web Service are selected in Internet Information Services (IIS): 6. Select World Wide Web Service in Internet Information Services (IIS) and click Details. 7. Verify that World Wide Web Service is selected in World Wide Web Service: 8. Click OK in each of the three open windows. 9. Click Next in the Windows Component Wizard. 10. Click Finish in the Windows Component Wizard. 11. Run the PI Web Services setup kit. Install and configure IIS on Windows Server 2008 R2 Before you run the PI Web Services setup kit, the Microsoft Windows Server 2008 R2 that you use to host PI Web Services must be installed and configured as described here. 1. Choose Start > Administrative Tools > Server Manager. 2. Select the Roles home page under the server where you want to install PI Web Services. Review the list of Role Services and verify that these services are installed: Under Application Development: ASP.NET.NET Extensibility ISAPI Extensions ISAPI Filters Under Management Tools: IIS 6 Management Compatibility IIS 6 WMI Compatibility IIS 6 Management Console 3. If these role services are not installed, then add the IIS Web Server role and the required role services. 4. Add web server role and services. PI Web Services 2012 Release Notes Page 8

13 Add web server role and services 1. In Server Manager right-click Roles >Add Roles. 2. Click Next to use the Add Roles Wizard to add the web server role. 3. Click Server Roles and select Web Server (IIS) in the Roles window. 4. Click Next. 5. Review the information in the Web Server (IIS) window and click Next. Under Application Development in the Role services list: Select ASP.NET Click Add Required Role Services in the Add Roles Wizard pop-up. You can click pop-up links for further information. 6. Select IIS 6 Management Compatibility in the Role services list and then click Next. 7. Verify that these items are listed as Installed in the Roles list: Under Application Development: ASP.NET.NET Extensibility ISAPI Extensions ISAPI Filters for.net Framework 4 Under IIS 6 Management Compatibility: IIS 6 Management Compatibility IIS 6 WMI Compatibility IIS 6 Management Console 8. Review your selections in the Confirm Installation Selections window and then click Install. 9. Verify that the web server was installed and click Close. 10. Run the PI Web Services setup kit. Install and configure IIS on Windows 7 1. Choose Control Panel > Programs and click Turn Windows features on or off. 2. In Windows Features, click to expand Internet Information Services. 3. Click to expand: 4. Verify that: For Vista, Internet Information Services, and then Web Management Tools, and then IIS 6 Management Compatibility. For Windows 7, Web Management Tools, and then IIS 6 Management Compatibility. PI Web Services 2012 Release Notes Page 9

14 Under IIS 6 Management Compatibility, these components are selected: IIS 6 Management Console IIS Metabase and IIS 6 configuration compatibility IIS Management Console is selected. 5. Click to expand World Wide Web Services and then: Click to expand Application Development Features and verify that these settings are selected: ISAPI Filters.NET Extensibility ASP.NET, if it is available in the list. If not, then verify that ASP.NET is installed after you install IIS. ISAPI Extensions Click to expand Common Http Features and verify that these settings are selected: 6. Click OK. Default Document HTTP Errors Static Content 7. Run the PI Web Service setup kit. Install PI Web Services IIS Edition If you upgrade from an earlier version of PI Web Services, the PI Web Services setup kit will: Rename your existing web.config file to old_web.config Upgrade PI Web Services in the directory used for the earlier PI Web Services installation. Before you install PI Web Services on Microsoft Windows Server 2008, Windows 7, or later, verify that you are logged in as an administrator. 1. Verify that the server on which you plan to install PI Web Services includes: All system requirements Microsoft Internet Information Services (IIS) on Windows Server configured as described in PI Web Services IIS Edition requirements. 2. Run the PI Web Services setup kit: Click Start to start the PI SDK installation. During the PI Software Development Kit (PI SDK) installation, Enter the appropriate information when you are prompted for: user information PI Web Services 2012 Release Notes Page 10

15 a path to a folder where PI SDK will be installed names for a default user and a default PI Server Note: It is possible to buffer data sent to the PI Server to guard against loss of connection. Data is not buffered by default. To enable buffering, use the PI SDK Utility. See the PI SDK Utility Help for details. Click Finish to complete the PI SDK installation. Note: If you run the PI Web Services setup kit on a 64-bit Windows server, repeat the PI SDK installation steps to install PI SDK for 32-bit operating systems. During the PI AF client setup, enter: user information a path to a folder where PI AF client will be installed the name of the default PI AF server to which PI Web Services will connect Review the list of PI AF client features that will be installed and click Next. Click Finish to complete the PI AF client installation. During the installation of PI Web Services, use the Select Installation Address window to select: Site A website location to host the website content and web service files used by Internet Information Services (IIS) on Windows Server. By default, this file tree is stored in: [wwwroot] \PIWebServices Virtual directory A name for the IIS virtual directory. The default value is PIWebServices. Installation directory You have the option to select a path to an installation folder for PI Web Services. If you are upgrading PI Web Services, the upgrade is installed in the folder used for the previous installation. 3. Click Next to start the installation of PI Web Services. 4. Click Close to exit the setup kit. Verify PI Web Services IIS Edition Installation Use these steps to verify that you can connect to the web server if you use the PI Web Services IIS Edition. Note: To find the installation path for PI Web Services, go to the Windows Registry directory: HKLM\SOFTWARE\PISystem\PI Web Services\CurrentInstallationPath. PI Web Services 2012 Release Notes Page 11

16 Procedure 1. Open a browser such as Windows Internet Explorer to verify your installation for data retrieval from PI server and PI Asset Framework: If you used the default installation and website directories, enter: If you did not use the default installation and website directories, enter the path you used for the website relative URL: directory name]/pitimeseries.svc You should see this screen: 2. Verify that you can use the newly installed PI Web Services to search for PI Server data: If you used the default installation and website directories, enter: If you did not use the default installation and website directories, enter the path you used for the website relative URL: directory name]/pisearch.svc 3. Verify that you can use the newly installed PI Web Services to search for PI event frames: If you used the default installation and website directories, enter: PI Web Services 2012 Release Notes Page 12

17 If you did not use the default installation and website directories, enter the path you used for the website relative URL: directory name]/pisoap.svc Hosting PI Web Services as a Windows service The PI Web Services Standalone Edition provides a Windows managed service as an alternative to hosting PI Web Services with Microsoft Internet Information Services (IIS). This edition is useful for environments with security restrictions that prohibit the use of IIS. While the service edition of PI Web Services still provides services over HTTP, it uses a smaller resource footprint and has a smaller potential attack surface than that of IIS. Note: You may install just one edition of PI Web Services on a single server. To change from one edition to another, you must first uninstall the existing edition. If you have IIS installed on your server, you must uninstall it before you run the PI Web Services Standalone Edition setup kit. Verify that the server that runs PI Web Services includes: Windows Server 2008 R2, Microsoft Windows Server 2008 with Service Pack 2, Windows Server 2003 with Service Pack 2, or Windows Server 2003 R2, Windows 7, Windows 2012, or Windows 8. Note: For all operating systems, you must be logged in as an administrator if you run the PI Web Services setup kit. The PI Web Services Standalone Edition is bundled with the PI Web Services setup kit. The computer must have network access to one or more of these OSIsoft servers: PI Server 3.3 or later PI AF server 2.1 or later that includes PI SQL for PI AF server Note: To search for PI event frames, you must use PI AF server 2.4 or later. See the sections Configure Security for PI Web Services Standalone Edition and View and configure message logs in the PI Web Services User Guide for information about how to configure security settings. Install PI Web Services Standalone Edition If you upgrade from an earlier version of PI Web Services, the PI Web Services setup kit will: Rename your existing web.config file to old_web.config Upgrade PI Web Services in the directory used for the earlier PI Web Services installation 1. Double-click the PI Web Services setup kit. PI Web Services 2012 Release Notes Page 13

18 2. De-select the option When done unzipping open:.\setup.exe, click Browse to locate a folder where you want to extract the installation files for PI Web Services and click Unzip. 3. Open the folder that contains the extracted files and rename the file setup.ini to another name such as setup_old.ini. 4. Rename the file setup_standalone.ini to setup.ini. 5. Run the Setup.exe contained in the folder that contains the extracted files. Note: If you run the PI Web Services setup kit on a 64-bit Windows server, it will install the PI SDK for both the 32-bit and 64-bit operating systems. 6. During the PI Software Development Kit (PI SDK) installation, enter the appropriate information when you are prompted for: user information a path to a folder where PI SDK will be installed names for a default user and a default PI Server Note: It is possible to buffer data sent to the PI Server to guard against loss of connection. Data are not buffered by default. To enable buffering, use the PI SDK Utility. See the PI SDK Utility Help for details. 7. Click Start to start the PI SDK installation. 8. Click Finish to complete the PI SDK installation. 9. During the PI AF client setup, enter the name of the AF server to which you want PI Web Services to connect. Note: You might be asked to provide the name of a PI Server for storage of Module Database configuration data. You can test this using PI SMT. 10. Click Install to start the PI AF client installation. 11. Click Finish to complete the PI AF client installation. 12. During the installation of PI Web Services, use the Select Installation Address window to select: Installation directory: Use the default installation directory: C:\Program Files\PIPC\PI Web Services\. You have the option to select a path to another installation folder for PI Web Services. Port: You have the option to select the port on which PI Web Services will listen. By default, the PI Web Services setup kit will use port 80. PI Web Services 2012 Release Notes Page 14

19 Uninstalling PI Web Services 2012 From Programs and Features, select PI Web Services 2012 and click Uninstall. The setup kit will remove the installed files and delete the Web application and virtual directory created to host the Web service. PI Web Services 2012 Release Notes Page 15

20 List of Files Installed During Setup PI Web Services 2012 includes the following OSIsoft products as dependencies, each of which have their own installation manifests: PI SDK PI AF Client 2012 SP1 PI OLEDB Enterprise 2012 Refer to the OSIsoft Technical Support and Resources Web site for complete information as to expected contents of these dependencies. PI Web Services 2012 Standalone edition All editions of PI Web Services 2012 contain the following non-versioned help and sample files. Directory File Version [PIHOME]\PI Web Services\Help [PIHOME]\PI Web Services\Help\Samples [PIHOME]\PI Web Services\Help\Samples [PIHOME]\PI Web Services\Help\Samples [PIHOME]\PI Web Services\Help\Samples [PIHOME]\PI Web Services\Help\Samples [Multiple HTML help files] web_config_basic_no_security.config web_all_bindings_basic.config web_config_netnamedpipes.config web_config_nettcp.config web_config_wshttp.config PI Web Services 2012 IIS edition PI Web Services 2012 IIS edition contains the following files: Directory File Version [PIHOME]\PI Web Services Global.asax [PIHOME]\PI Web Services PIInstrumentation.config [PIHOME]\PI Web Services PISearch.svc [PIHOME]\PI Web Services PISoap.svc [PIHOME]\PI Web Services PITimeSeries.svc [PIHOME]\PI Web Services web.config [PIHOME]\PI Web Services\Bin OSIsoft.PIDataServices.Common.dll [PIHOME]\PI Web Services\Bin OSIsoft.PIDataServices.Configuration.dll [PIHOME]\PI Web Services\Bin OSIsoft.PIDataServices.DataAccess.dll [PIHOME]\PI Web Services\Bin OSIsoft.PIDataServices.DataService.dll [PIHOME]\PI Web Services\Bin OSIsoft.PIInstrumentation.dll [PIHOME]\PI Web Services\Bin OSIsoft.PIInstrumentation.InstallState [PIHOME]\PI Web Services\Bin OSIsoft.PIInstrumentation.Listeners.dll PI Web Services 2012 Release Notes Page 16

21 Directory File Version [PIHOME]\PI Web Services\Bin PIWebServices.dll [PIHOME]\PI Web Services\Bin PIWebServicesInstrumentation.dll [PIHOME]\PI Web Services\Bin PIWebServicesInstrumentation.InstallState PI Web Services 2012 Standalone edition PI Web Services 2012 Standalone edition contains the following files: Directory File Version [PIHOME]\PI Web Services\SvcHost OSIsoft.PIDataServices.Common.dll [PIHOME]\PI Web Services\SvcHost OSIsoft.PIDataServices.Configuration.dll [PIHOME]\PI Web Services\SvcHost OSIsoft.PIDataServices.DataAccess.dll [PIHOME]\PI Web Services\SvcHost OSIsoft.PIDataServices.DataService.dll [PIHOME]\PI Web Services\SvcHost OSIsoft.PIInstrumentation.dll [PIHOME]\PI Web Services\SvcHost OSIsoft.PIInstrumentation.InstallState [PIHOME]\PI Web Services\SvcHost OSIsoft.PIInstrumentation.Listeners.dll [PIHOME]\PI Web Services\SvcHost PIInstrumentation.config [PIHOME]\PI Web Services\SvcHost PIWebServices.dll [PIHOME]\PI Web Services\SvcHost PIWebServicesInstrumentation.dll [PIHOME]\PI Web Services\SvcHost PIWebServicesInstrumentation.InstallState [PIHOME]\PI Web Services\SvcHost PIWebSvcHost.exe [PIHOME]\PI Web Services\SvcHost PIWebSvcHost.exe.config [PIHOME]\PI Web Services\SvcHost PIWebSvcHost.InstallState Documentation Overview PI Web Services User Guide: An introduction to PI Web Services for the end user. This user guide provides a product overview, installation procedures, security configuration, programming reference, and other topics to allow you to work with and troubleshoot PI Web Services. Additional information about PI SDK, PI AF, PI OLEDB and OLEDB Enterprise, and other topics of interest can be found in respective books available on the OSIsoft Technical Support and Resources Web site. PI Web Services 2012 Release Notes Page 17

22 Technical Support and Resources For technical assistance, contact OSIsoft Technical Support at or The OSIsoft Technical Support website offers additional contact options for customers outside of the United States. When you contact OSIsoft Technical Support, be prepared to provide this information: Product name, version, and build numbers Computer platform (CPU type, operating system, and version number) Time that the difficulty started Log files at that time Details of any environment changes prior to the start of the issue Summary of the issue, including any relevant log files during the time the issue occurred The OSIsoft Virtual Campus (vcampus) website has subscription-based resources to help you with the programming and integration of OSIsoft products. PI Web Services 2012 Release Notes Page 18

23 OSIsoft, LLC 777 Davis St., Suite 250 San Leandro, CA USA Tel: (01) Fax: (01) Web: OSIsoft Australia Perth, Australia OSIsoft Europe GmbH Frankfurt, Germany OSIsoft Asia Pte Ltd. Singapore OSIsoft Canada ULC Montreal & Calgary, Canada OSIsoft, LLC Representative Office Shanghai, People s Republic of China OSIsoft Japan KK Tokyo, Japan OSIsoft Mexico S. De R.L. De C.V. Mexico City, Mexico OSIsoft do Brasil Sistemas Ltda. Sao Paulo, Brazil Copyright: OSIsoft, LLC. 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. OSIsoft, the OSIsoft logo and logotype, PI Analytics, PI ProcessBook, PI DataLink, ProcessPoint, Analysis Framework, IT Monitor, MCN Health Monitor, PI System, PI ActiveView, PI ACE, PI AlarmView, PI BatchView, PI Data Services, PI Manual Logger, PI ProfileView, PI WebParts, ProTRAQ, RLINK, RtAnalytics, RtBaseline, RtPortal, RtPM, RtReports PI Event Frames, PI Coresight and RtWebParts are all trademarks of OSIsoft, LLC. All other trademarks or trade names used herein are the property of their respective owners. U.S. GOVERNMENT RIGHTS Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the OSIsoft, LLC license agreement and as provided in DFARS , DFARS , FAR , FAR , as applicable. OSIsoft, LLC. Published: 13-Feb-2013 PI Web Services 2012 Release Notes Page 19