Picture Perfect 4.6 Release Notes

Size: px

Start display at page:

Download "Picture Perfect 4.6 Release Notes"

Emerald Little
5 years ago
Views:

1 Picture Perfect 4.6 Release Notes P/N C 06FEB12

2 Content Introduction 3 Installation 4 New features 4 Application notes 8 Known issues 10 Recommendations for controller deployment 14 Contacting technical support 15 Copyright Copyright 2011 UTC Fire & Security. All rights reserved. This document may not be copied in whole or in part or otherwise reproduced without prior written consent from UTC Fire & Security, except where specifically permitted under U.S. and international copyright law. 2 Picture Perfect 4.6 Release Notes

3 Introduction These are the release notes for Picture Perfect 4.6. For installation instructions, refer to the Picture Perfect 4.6 Installation Manual on the Documentation CD in conjunction with these release notes. Before installing Picture Perfect 4.6, please note: You must be at Picture Perfect 4.0 Service Pack (SP) 3 before upgrading to Picture Perfect 4.6. Refer to Installation on page 4. To ensure that your badge design records are properly back up and converted, please follow the instructions for Badge Designs in the Picture Perfect 4.6 upgrade preparation checklist in section 3 of the Picture Perfect 4.6 Installation Manual. Included in your shipment The following CD/DVDs are included in your Picture Perfect 4.6 media kit: Picture Perfect 4.6 Software Installation DVD: Contains Picture Perfect software for Linux and AIX versions of the application server and Informix database. Controller R120 firmware is also included on the installation DVD. Documentation CD: Contains the latest manuals for UTC Fire & Security access products. Picture Perfect 4.6 Release Notes 3

4 Installation To install Picture Perfect 4.6, refer to the Picture Perfect 4.6 Installation Manual on the Documentation CD. Upgrades To upgrade an Enterprise system from Picture Perfect version 4.0 SP 3 or from version to version 4.6, refer to the Picture Perfect 4.6 Enterprise Edition User Manual included in your media kit on the Documentation CD. To upgrade any other (non-enterprise) Picture Perfect configuration from version 4.0 SP3 or from version to version 4.6, refer to the Picture Perfect 4.6 Installation Manual included in your media kit on the Documentation CD. New features Technology refresh with latest released software for: Client operating system: - Windows 7 Ultimate (32-bit and 64-bit) - Windows XP SP3 (32-bit) (Windows Vista is no longer supported) Note: The hardware and software requirements for an Imaging workstation are the same as for a Client workstation, with the exception that Windows 7 64-bit is supported only for non-imaging workstations. Server database: Informix UC8 Server operating system: - Red Hat Linux 5.6 (32-bit) or - AIX 6.1 (64-bit) TL 6 Web browsers: - Internet Explorer 8.0 on Windows XP (32-bit) or Windows 7 (32-bit and 64-bit) - Firefox (or later) Java runtime update 26 4 Picture Perfect 4.6 Release Notes

5 Table 1: Required technology level for Picture Perfect (PP) 4.6 Component Required Version Distributed with PP AIX 6.1 TL6 no yes Linux Enterprise Informix Server Server-side Java/AIX Server-side Java/Linux RHEL 5.6 x86 no yes Customer Supplied Notes UC8 yes no PP base installation JRE bit IBM (SR5) JRE 1.6.0_26 (32-bit) no yes Required by PP Phase 2 installation yes no PP base installation Tomcat yes no PP base installation Web Server/AIX Web Server/ Linux OpenSSL/ AIX OpenSSL/ Linux Client OS IBM HTTP Server no yes Required by PP Phase 2 installation Apache 2.2. no no Supplied with RHEL no no Supplied with AIX 6.1 TL no Supplied with RHEL 6.0 Windows XP (32-bit) Windows 7 (32- bit/64-bit) no yes Picture Perfect 4.6 Release Notes 5

6 Client Web Browser Client-side Java.Net Framework EPI Builder Runtime Internet Explorer 8.0 on Windows XP (32-bit) or Windows 7 (32- bit/64-bit) Firefox (32-bit) JRE 1.6.0_26 (32-bit/64-bit) no yes If not shipped with the OS, the customer needs to download and install a browser. yes no The customer needs to download and install clientside Java from the PP Webtop..NET 3.5 yes no Suggested yes no Jloox 3.4 yes no Database replication in an Enterprise system: Picture Perfect Enterprise Edition 4.6 uses the IBM Informix Enterprise Replication (ER) tool to replicate database table information between geographically distributed servers. This tool is an enhancement/ replacement for the Personnel/Badge and Categories "refreshers" technique used in previous Picture Perfect versions. Informix ER provides high availability and improved performance for high volume data transfers at network latency limited to 300 ms. The benefits of Enterprise Replication include: Updates from any host are now supported (as opposed to allowing changes only on the nethost) Latency on one subhost no longer affects the refresh time on other subhosts. Significantly improved performance. 6 Picture Perfect 4.6 Release Notes

7 New Alarms: Enterprise Replication introduces four new pre-defined logical alarms and associated input groups: Sequence Object 90% full Aborted Transaction (conflicts) reported ER Server stopped or suspended Server clock out of sync. National Language Support (NLS): All languages previously supported continue to be supported. Micro controller firmware versions: Support for mixed versions of R118, R117, and R120 or currently shipping version in a single system for PXNPlus and DirecDoor. Support for legacy firmware on PX micros. Flashing of micros is not required before upgrading the host software. Support for the DirecDoor I/O expansion board, which provides five additional 4-state inputs and five additional relay outputs. Support for FQDN usage for browser/client connections to the Picture Perfect host. Note: Picture Perfect 4.6 does not support co-residency with Facility Commander. Picture Perfect 4.6 Release Notes 7

8 Application notes The Picture Perfect 4.6 base package installs Apache Tomcat If Tomcat is already installed in the expected location, the Picture Perfect 4.6 base installation program skips it without checking the version. To ensure that the correct Tomcat version is used with Picture Perfect 4.6, we recommend removing any existing Tomcat version other than The expected Tomcat installation directory is as follows: On Linux: /var/www/apache-tomcat On AIX: /usr/httpserver/apache-tomcat Use the command rm -rf <Tomcat directory> to remove the Tomcat directory. You must be at Picture Perfect 4.0 Service Pack 3 or Picture Perfect before upgrading to Picture Perfect 4.6. If the upgrade is from 4.0, the 4.6 media kit must be used to convert the database. If upgrading from no database migration is needed. The technology must be refreshed for all the hosts as defined in Table 1 on page 5. In general, the Picture Perfect 4.6 Enterprise solution needs 1.8 times the space of the base database space. For example, if the base database space is 25 GB in a previous Picture Perfect version, 44 GB is needed in Picture Perfect 4.6. The Picture Perfect 4.6 Enterprise solution upgrades take a much longer time, since the hostconfig tool now synchronizes all hosts. For more details, please refer to the FAQ section in the Enterprise Edition User Manual. The command to unmount the Picture Perfect 4.6 Installation DVD is: umount /media/pp46 8 Picture Perfect 4.6 Release Notes

9 After an upgrade, badge records that have been modified may be marked red in the grid. If this occurs, review the Host Bid Format and change the formats (%10s, %12s, %13s, %16s), according to the number of digits used in the badge and the format referenced. Check the number of digits in the badge record, and be sure the BID format used in the record matches, otherwise use the Badge Formats to make necessary changes. Existing licenses for Picture Perfect are compatible with Picture Perfect 4.6. Picture Perfect 4.0 customers need to get new licenses. DO NOT press Ctrl+C during the installation or removal of any Picture Perfect package because this will interrupt the installation and you will need to remove the package, and then reinstall it. Picture Perfect operators must have read/write permissions to their home directory on the client workstation local hard drive. As your system grows, it is possible to outgrow the 2 MB or 4 MB memory limit on your controllers. Please contact Sales Engineering for guidance. The M/2, M/4, and M/5P controllers are not supported in Picture Perfect 4.6. The Restore option in the GUI is no longer supported because Restore now requires Picture Perfect to be stopped. Open access (public) to the database is no longer supported. A new user ppuser with read-only permissions is now available, and should be the preferred user. Existing users like ppapp and ppadmin continue to work as before. Picture Perfect 4.6 for Linux supports 800 controllers per host/subhost. Picture Perfect 4.6 for AIX supports 1000 controllers per host/subhost. Picture Perfect 4.6 Release Notes 9

10 Known issues Facility records: On Picture Perfect 4.6 Enterprise systems, facility records (Facilities) must be created or deleted on the nethost ONLY and not on the subhost(s). The root cause for this issue is that facilities created on a subhost are assigned very large ids which can lead to buffer overruns of shared memory and result in unexpected process behavior at the client. Archiving History Tables and Import of Archive Data: When archiving history data with force rollover, select only one history table at a time, e.g., choose either Badge, Alarm, Operator, Tour, or Event table. If multiple tables are selected, only the last table is imported during an import of archive data. Badge Design Screen: On the badge design screen, the arrow keys on the keyboard are not operational. Use the mouse to position the image instead of the arrow keys. A hot fix for this issue is available through Technical Support. Other shortcuts for moving objects on the badge design screen, such as Ctrl+Numpad Plus, Ctrl+Numpad Minus, Ctrl+Page Up, Ctrl+Page Down, are not operational in Windows XP Pro SP3. Batch Badge Printing: The preview option for the batch badge printing does not display all badges selected for printing. You can still preview the badges individually. Batch printing is not affected by this issue. A hot fix is available through Technical Support. Mifare Encoding Keys: For all operators to be able to create Mifare encoding keys, you must change the permission of the ImageWare key registry to allow all user to have full control. To change the ImageWare key registry permissions: 1. Click Start > Run, and type Regedit in command line. Click OK. 2. Go to HKEY_LOCAL_MACHINE/SOFTWARE/ImageWare Systems. 3. Right-click on the entry, and then select Permissions. 4. Click Users Group, and then check the Allow Full Control check box to allow all users to have full control. 5. Click OK to exit. External Encoder Setup: In the External Encoder Setup, the application window paints when moved across the screen. 10 Picture Perfect 4.6 Release Notes

11 Status Command Issue: Running a status against a nonconnected micro results in continuous attempted transmissions of FUP messages to the disconnected micro. To stop the transmission of FUP messages to the disconnected micro, change the micro to a nonexistent state. VPN Connection: Picture Perfect does not support client workstations connecting to the server over the Internet unless connected via a VPN. Daylight Savings Time (DST) Change: Some Picture Perfect systems may experience a temporary discrepancy in transaction date and time during the Daylight Savings Time (DST) change. This only affects systems with servers or controllers that span multiple time zones. For example, if a server is located in Central DT and controllers are in Eastern DT, the servers may experience a one-hour divergence. eflash: When flashing controllers using eflash, an error may occur. Retry the eflash. pptools Files: During the installation of conversion files for Picture Perfect 4.6, the /pptools/* files are installed on the Picture Perfect 4.0 server. The files in this directory only affect SSL or database encryption. Red Hat Enterprise Linux 5.6 Installation: When selecting packages from the Package Group Selection window, be sure that only the recommended packages are selected as instructed in the Picture Perfect 4.6 Installation Manual. Uncheck all default selections that are not specified recommended packages. WinHlp32.exe File: Microsoft no longer includes WinHlp32.exe as a component of the Windows operating system. This may cause problems for customers who want to use Windows XP or Windows 7, but still rely on the 32-bit.hlp files for third party programs such as ImageWare (used in the Picture Perfect Image package). The Microsoft WinHlp32.exe for Windows XP and Windows 7 can be downloaded at the following Website: Tours Package on Enterprise systems: If the tours package is installed on a subhost before hostconfig is run on the nethost, the tourdbs chunk in the nethost is not created. Run hostconfig on the nethost before installing optional packages on the subhost. Picture Perfect 4.6 Release Notes 11

12 Make sure the database is up and running on the nethost before installing tours on the subhost. The tours installation package on a subhost does not update the 30-pp.rules file on the nethost. You must edit the /etc/udev/rules.d/30-pp.rules file using an editor tool, such as vi, to add the following new line: SYSFS{dev}=="<Number1:Number2>", NAME="/dev/rootvg/tourdbs", OWNER="informix", GROUP="informix", MODE="0660", SYMLINK="rtourdbs" Where <Number1:Number2> can be found as a result of running the following command: ls lh /dev/rootvg/tourdbs Example: brw-rw informix informix 253, 11 Mar 30 12:08 /dev/rootvg/tourdbs Where <Number1:Number2> are 253:11. Therefore, the line to be added to the /etc/udev/rules.d/30- pp.rules file appears as follows: SYSFS{dev}=="253:11", NAME="/dev/rootvg/tourdbs", OWNER="informix", GROUP="informix", MODE="0660", SYMLINK="rtourdbs" Temporary Categories: On systems with a large number of controllers with a large number of temporary categories with daily schedules which are assigned to multiple badges, a delay in temp categories taking effect may be noticed. Workaround: Limit the number of temp_category inserts/updates that are done simultaneously. Changing Category Assignments: When changing category assignments for multiple persons, the description fields in the operator activity history records are created inconsistently, which results in several issues: - It is not possible to reliably parse this field in exported data. - If two persons in database have identical names, they are indistinguishable in reports. - There is no way to define a template for this field. Workaround: Modify and save changes one at a time. 12 Picture Perfect 4.6 Release Notes

13 Searching on Personnel UI: Searching on the Personnel UI after selecting the category manager tab results in slower searches. Workaround: Search before selecting the category manager tab. If changes are made on the category tab, save and close, and then reopen the Personnel UI to continue working on the Personnel UI. Unknown or Invalid Badge Transactions: During unknown or invalid badge transactions on a reader configured as keypad only, the badge host transaction date and time may be corrupted. Workaround: None Invalid alarm descriptions: Invalid PERSON TRACE ALARM descriptions in notifications may occur while alarms have not been cleared in the alarm monitor if the transactions occur close together in time. Workaround: Respond to and Clear the Person Trace Alarms as soon as possible if you have routed these alarms to . Badging Client Interrupted Connection: When badging client connections are interrupted, memory leaks can occur. Workaround: None. Picture Perfect 4.6 Release Notes 13

14 Recommendations for controller deployment This is not a static topic. As software, firmware and hardware platforms change and evolve, so do the recommended deployment methods. The current recommendations are: For PXNplus-based Controllers We recommend these should be head of line controllers, attached via on-board Ethernet connection. The recommendation is to not have any downstream serial controllers. If this cannot be accomplished, then the number of downstream serial controllers should be minimized, not to exceed three CPUs. PXN based Controllers We recommend these should be head of line controllers. The recommendation is to not have any downstream serial controllers. If this cannot be accomplished, then the number of downstream serial controllers should be minimized, not to exceed three CPUs. Customers should also be planning the migration from these CPUs to PXNplus based CPUs. PX-based Controllers - We recommend limited deployments of these controllers. Customers should be migrating from PX controllers to PXNplus controller with a LAN connection, thus eliminating downstream serial connections. Downstream configurations of with PX based controllers should be limited to no more than three PX controllers. Hosts with serial ports are becoming difficult to find, so for new installations PXNplus based controllers attaching via Ethernet LAN is recommended. 14 Picture Perfect 4.6 Release Notes

15 Contacting technical support You can reach technical support by phone 8 a.m. to 7 p.m. EST, Monday through Friday. North America T F Asia T F Australia T F Canada T F EMEA T F Latin America T F rs-bctsupport@fs.utc.com Web site: Picture Perfect 4.6 Release Notes 15

FCWnx 7.6 Release Notes

FCWnx 7.6 Release Notes P/N 460666001E ISS 11NOV11 2011 UTC Fire & Security. All Rights Reserved. This document may not be copied in whole or in part or otherwise reproduced without prior written consent