Inform IT. Enterprise Historian TM and Profile Historian. Release Notes. Version 3.2/1 Patch 4 for History Services

Transcription

1 Inform IT Enterprise Historian TM and Profile Historian Version 3.2/1 Patch 4 for History Services Release Notes

2 NOTICE The information in this document is subject to change without notice and should not be construed as a commitment by ABB Inc. ABB Inc. assumes no responsibility for any errors that may appear in this document. In no event shall ABB Inc. be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, nor shall ABB Inc. be liable for incidental or consequential damages arising from use of any software or hardware described in this document. This document and parts thereof must not be reproduced or copied without written permission from ABB Inc., and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose. The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license. This product meets the requirements specified in EMC Directive 89/336/EEC and in Low Voltage Directive 72/23/EEC. Copyright 2003 ABB Inc. All rights reserved. Release: June 2003 Document number: 3BUF D1 RevA TRADEMARKS Registrations and trademarks used in this document include: Windows ActiveX PostScript Registered trademark of Microsoft Corporation. Registered trademark of Microsoft Corporation. Registered trademark of Adobe Systems Inc. Acrobat Reader Registered trademark of Adobe Systems Inc.

3 TABLE OF CONTENTS Section 1 - Introduction Prerequisites and Requirements...5 Section 2 - Functionality Fixed Problems...6 Section 3 - Installation Introduction...9 Installing the Server Patch File...10 Preparing Your PC for Patch Installation...10 Stopping ABB Processes in PAS...11 Installing the Patch...13 Post Installation...13 Restoring the Configuration File...13 Restarting PAS...13 Verifying Patch Installation...14 Installing the Client Patch File...15 Getting Your PC Client Ready for Patch Installation...15 Installing the Patch...17 Post Installation...17 Restarting the PDL Data and Message Log Servers...17 Verifying Patch Installation BUF D1 RevA 3

4

5 Section 1 Introduction These release notes describe patch 4 for Inform IT Enterprise Historian version 3.2/1, and Profile Historian version 3.2/1. The problems fixed on both platforms are described in Section 2, Functionality. This patch includes two patch files - one for installation on the server platform, and another file for installation on remote PC clients. The server patch includes both server and client fixes, so you are NOT required to install the client file on the server platform. The patch is installed in the same manner whether you install it on the Enterprise Historian or Profile Historian platform. Installation instructions are provided in Section 3, Installation. Prerequisites and Requirements In order to install this patch, the Enterprise Historian or Profile Historian software must be at Version 3.2/1, and the History Services software version 2.5/1 must be installed. Instructions for installing the base platform software (including History Services version 2.5/1) are provided in: Inform IT Enterprise Historian Version 3.2/1 for Windows 2000 Administrator s Guide. Inform IT Profile Historian Version 3.2/1 Administrator s Guide. This patch cannot be installed with patch 1, patch 2, or patch 3 for Inform IT Enterprise Historian version 3.2/1, and Profile Historian version 3.2/1. If one of these patches is already installed, you must remove it BEFORE installing patch 3. Details are provided in Section 3, Installation. Patch 4 will fix the problems that were fixed by patches 1, 2 & 3. 3BUF D1 RevA 5

6 Fixed Problems Section 2 Functionality Section 2 Functionality Fixed Problems This patch fixes the problems for Enterprise Historian version 3.2/1 as described in Table 1, and Profile Historian version 3.2/1 as described in Table 2. Table 1. Fixed Problems for Enterprise Historian Version 3.2/1 PRACA In Patch No. Description ,2,3,4 Digital signals from OPC data sources are collected by History come in as VARIANTS of type VT_BOOL where VARIANT_TRUE, = -1 and VARIANT_FALSE = 0 (Microsoft standard). History stores each digital signal as a floating point number: VARIANT_FALSE = 0 and VARIANT_TRUE = 1. NOTE: While VARIANT_TRUE is passed into History as -1, it is stored as 1 because most client applications expect to see TRUE as 1 rather than -1. Prior to this patch, History checked each digital signal against the VARIANT_TRUE (-1). If the signal did not equal -1, it was considered VARIANT_FALSE and stored as value 0. This did not account for some OPC servers (for example, the Maestro OPC server and AF100 OPC server) that did not follow the Microsoft standard and passed in values other than 0 and - 1. Thus, if an OPC server passed in a value 1, it would be considered FALSE and stored as 0. This patch changes the way History checks digital signals. Now History checks each signal against both the VARIANT_TRUE and VARIANT_FALSE. Any value that is found not equal to either 0 or -1 is stored as whatever value it is. In other words, if the value is passed in as 1 it is stored as ,3,4 Prior to this patch, the Production Data Log (PDL) application had a problem communicating with Produce IT Batch. Specifically, PDL could no longer communicate with Produce IT Batch after a task limit has been reached. This patch raises the task limit to a level that will minimize the likelihood of the limit being reached. 6 3BUF D1 RevA

7 Section 2 Functionality Fixed Problems Table 1. Fixed Problems for Enterprise Historian Version 3.2/1 PRACA In Patch No. Description ,3,4 Prior to this patch, when using History Services in a New Zealand time zone, any attempt to open an Archive Group would cause the History Builder to crash. This problem has been fixed ,4 Prior to this patch, HsBar could not be used to perform an on-line backup. hsbar aborted the backup if History was running. This interlock was implemented to prevent inconsistencies that could occur in a backup image when the backup was done at the same time PDL data was being collected. This interlock has been removed so that on-line backups are now permitted; however, the problem with running the on-line backup while PDL data is being collected has not been fixed. If you are using PDL, do not run HsBar on-line. In this case you must stop the History process via PAS before using HsBar. If you attempted an on-line backup while collecting PDL data, and you have problems restoring the data, contact the Technical Support Group via SUPPORTLINE - U.S.: (1-800-HELP-365); International: ( ) ,4 Prior to this patch, when an OPC server passed in a vendor status for good data, the status information was misinterpreted. This information is now interpreted correctly Prior to this patch, the History Client application (sending ProduceIT/PDL messages into a History Message Log) would sometimes crash during a transition from backup to primary. This problem has been fixed Prior to this patch, you were not able to retrieve data from logs whose storage type is TYPE1, when the log was full, and the start time for the query was specified as some time later than the timestamp for the first value stored in the log. This problem has been fixed The problem where by the PDLAPISRV task leaked memory has been fixed. 3BUF D1 RevA 7

8 Fixed Problems Section 2 Functionality Table 2. Fixed Problems for Profile Historian Version 3.2/1 In Patch PRACA No. Description ,3,4 Prior to this patch, Profile clients could not retrieve data from profile logs that were configured to START_INACTIVE. This is now possible ,3,4 Prior to this patch, the Profile Server was set up to collect roll trim array numbers as integers. It now accepts real values as well ,3,4 Prior to this patch, when using the Profile Client display to look at reel turnups, the reel number (embedded in the title of the reel) was always zero. The reel number is now displayed correctly. 8 3BUF D1 RevA

9 Section 3 Installation Introduction Section 3 Installation Introduction Review all the instructions, and your ABB Support terms and conditions, for precautions, scope of license, restrictions, and limitation of liability and warranties, before installing this software. In case of difficulties, please contact the Technical Support Group via SUPPORTLINE: in the U.S. - (1-800-HELP-365); International - ( ). Install the patch server and client files on their respective nodes. Refer to the instructions in: Installing the Server Patch File on page 10. Installing the Client Patch File on page 15. The server patch includes both server and client fixes, so you are NOT required to install the client file on the server platform. 3BUF D1 RevA 9

10 Installing the Server Patch File Section 3 Installation Installing the Server Patch File Preparing Your PC for Patch Installation Read these important considerations and perform the steps described below before you begin installing the patch file on the Enterprise Historian or Profile Historian server. The Enterprise Historian or Profile Historian version 3.2/1 software, including History Services version 2.5/1 must already be installed. This patch cannot be installed without History Services. If patch 1 or patch 2 or patch 3 is already installed on your system, the patch must be removed BEFORE you install patch 4. You can check to see whether or not one of these patches is installed via the Windows Add/Remove Programs utility. History Services must be stopped BEFORE you remove the patch, so if you need to remove the patch, do so AFTER you stop PAS (step 5 below). 1. Log in as a Windows user with Administrator privileges. The username must be defined local to the PC where you install the software. Do not use a domain-defined username. 2. Make a backup of your system before installing the patch. 3. This step is only required when you are installing the patch on a Profile Historian server platform. Before you install the patch you must save the AdvHistProfCfg.txt configuration file. This file is located in the HsData\History directory on the drive where history data is stored. This file contains the IP address of the Accuray Object Server. It must be restored when you are finished installing the patch. 4. Exit all Windows applications. 5. Stop all services under PAS supervision on the server. See Stopping ABB Processes in PAS on page BUF D1 RevA

11 Section 3 Installation Installing the Server Patch File Stopping ABB Processes in PAS Open the PAS window, from the Windows task bar, choose: Start > ABB Industrial IT> System Services > Process Administration. Click Stop All in the PAS window, Figure 1. This shuts down all processes under PAS supervision, including History. Figure 1. Process Administration Service Window If patch 1 or patch 2 or patch 3 is installed on the server and needs to be removed, do so now. Use the Windows Add/Remove Programs utility in the Windows Control Panel (Start>Settings>Control Panel>Add/Remove Programs), Figure 2. 3BUF D1 RevA 11

12 Installing the Server Patch File Section 3 Installation Figure 2. Removing an Existing Patch 12 3BUF D1 RevA

13 Section 3 Installation Post Installation Installing the Patch Post Installation In SolutionsBank, click the file named EH3.2.1P4.exe. This launches a file download dialog. Save the file to an appropriate location on your computer, and then transfer the file to the target computer where the patch is to be installed. Run EH3.2.1P4.exe on the target computer. When you are prompted to choose a custom or complete installation, choose Complete. Restoring the Configuration File This step is only required when you are installing the patch on a Profile Historian platform. This must be done BEFORE you restart PAS. After you install the patch you must restore the AdvHistProfCfg.txt configuration file that was saved prior to installing the patch. This file contains the IP address of the Accuray Object Server. Restore the file to the HsData\History directory on the drive where history data is stored. If you forgot to save the original, you can simply edit the default installed file and enter the correct IP address. Restarting PAS When you are finished installing this patch you must restart all processes under PAS supervision. This procedure is basically the same as Stopping ABB Processes in PAS on page 11. Click Start All in the PAS window. 3BUF D1 RevA 13

14 Post Installation Section 3 Installation Verifying Patch Installation To verify that the patch has been installed, use the Windows Add/Remove Programs utility. Launch this utility from the Windows Control Panel (Start>Settings>Control Panel>Add/Remove Programs), then look for the patch in the list of currently installed programs, Figure 3. Figure 3. Verifying Server Patch Installation The installed size may vary slightly, depending on whether or not a readme text file is installed. Whether or not this file is installed does not affect the operation of the patch. This patch cannot be removed without first removing the History Services software. If you need to remove this patch, first remove History Services (retain the current database), reboot, remove this patch, then reinstall History and reboot. 14 3BUF D1 RevA

15 Section 3 Installation Installing the Client Patch File Installing the Client Patch File Getting Your PC Client Ready for Patch Installation Read these important considerations and perform the steps described below before you begin installing the client patch file on the Enterprise Historian or Profile Historian remote PC clients. If patch 1 or patch 2 or patch 3 is already installed on your system, the patch must be removed BEFORE you install patch 4. You can check to see whether or not one of these patches is installed via the Windows Add/Remove Programs utility. The PDLDataServer and MessageLogServer services must be stopped BEFORE you remove the patch, so if you need to remove the patch, do so AFTER step 3). 1. Log in as a Windows user with Administrator privileges. The username must be defined local to the PC where you install the software. Do not use a domain-defined username. 2. Make a backup of your system before installing the patch. 3. Use the EH Connection Configuration tool to stop the PDLDataServer and MessageLogServer services. To do this: a. Launch this utility from the Windows task bar by choosing Start>ABB Industrial IT>Inform IT>History>EH Connection Configuration, Figure 4. Figure 4. Launching the EH Connection Configuration Tool 3BUF D1 RevA 15

16 Installing the Client Patch File Section 3 Installation This displays the Connection Configuration main window Figure 5. Figure 5. EH Connection Configuration Dialog b. Click the Advanced button to the expand the dialog, then use the corresponding Change Mode and Change Status buttons in the lower section of the dialog, Figure 6. The Change Status buttons are labeled Stop when the corresponding services are running. Clicking a button changes the status to Stopped, and the label will change to Start. Services Stopped Figure 6. Expanded View with Advanced Functions c. Click Exit when you are finished with this dialog. If patch 1, 2 or 3 is installed on the client, remove it now. Use the Windows Add/Remove Programs utility in the Windows Control Panel (Start>Settings>Control Panel>Add/Remove Programs). 16 3BUF D1 RevA

17 Section 3 Installation Installing the Client Patch File Installing the Patch 4. Exit all Windows applications. In SolutionsBank, click the file named EH3.2.1P4CLIENT.exe. This launches a file download dialog. Save the file to an appropriate location on your computer, and then transfer the file to the target computer where the patch is to be installed. Run EH3.2.1P4CLIENT.exe on the target computer. Post Installation When the License Agreement dialog is displayed, ignore the instructions provided in the dialog. Click the I Accept check box and then click Next to continue the installation. When you are prompted to choose a custom or complete installation, choose Complete. Restarting the PDL Data and Message Log Servers Use the EH Connection Configuration tool to restart the PDLDataServer and MessageLogServer services. The procedure is basically the same as the procedure for stopping these services as described in Getting Your PC Client Ready for Patch Installation on page 15. The Change Status buttons are labeled Start when the corresponding services are stopped. Clicking a button changes the status to Running, and the label will change to Stop, Figure 7. Figure 7. Services Status 3BUF D1 RevA 17

18 Installing the Client Patch File Section 3 Installation Verifying Patch Installation To verify that the patch has been installed, use the Windows Add/Remove Programs utility. Launch this utility from the Windows Control Panel (Start>Settings>Control Panel>Add/Remove Programs), then look for the patch in the list of currently installed programs, Figure 3. Figure 8. Verifying Client Patch Installation The installed size may vary slightly, depending on whether or not a readme text file is installed. Whether or not this file is installed does not affect the operation of the patch. 18 3BUF D1 RevA