Director s Station 4.9. Release Notes. June 2010

Transcription

1 Director s Station 4.9 Release Notes June 2010

2 2010 SirsiDynix. All rights reserved. The processes and all the routines contained herein are the proprietary properties and trade secrets of SirsiDynix. Except as provided by license agreement, this manual shall not be duplicated, used or disclosed for any purpose or reason, in whole or in part, without the express written consent of SirsiDynix. The information in this document is subject to change without notice and should not be construed as a commitment by SirsiDynix. SirsiDynix grants the right of copying the enclosed material solely for the internal business use of the end user if (1) this document has been obtained by purchase or by license agreement in conjunction with SirsiDynix products, and (2) this copyright statement is included with each copy. All other copying or distribution is strictly prohibited. Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in sub-paragraph (b)(3) of the Rights in Technical Data and Computer Software clause in DFARS Rights for non-dod U.S. Government departments and Agencies are as set forth in FAR (c)(1,2). Sirsi, WebCat, Vizion, WorkFlows, Unicorn, UnicornECOLE, UnicornOASIS, UnicornSTILAS, Site Source, DRA, DRA Net, Inlex, MultiLIS, Taos, JurisLink, Corinthian, Dynix, URSA, Horizon, Remote Patron Authentication, and TeleCirc are trademarks of SirsiDynix. Other product and company names herein may be the trademarks of their respective owners. All titles, versions, trademarks, claims of compatibility, etc., of hardware and software products mentioned herein are the sole property and responsibility of the respective vendors. SirsiDynix makes no endorsement of any particular product for any purpose, nor claims responsibility for its operation and accuracy. This document is compatible with Director s Station 4.9. Information in this document may also be compatible with later versions. 06/2010

3 Contents Section 1: Overview Comments and suggestions Section 2: Enhancements Section 3: System requirements Software requirements Server requirements Supported web browsers Hardware requirements Requirements for installing and running the SirsiDynix Agent Section 4: Fixed bugs Section 5: Known issues Section 6: Installation Notes About the SirsiDynix Agent Notifications Restarting the SirsiDynix Agent after a reboot iii

4 Contents iv

5 Section 1: Overview These SirsiDynix Director s Station 4.9 Release Notes cover new features, bug fixes, and known issues since Director s Station This document contains these sections: Enhancements on page 3 System requirements on page 5 Fixed bugs on page 9 Known issues on page 11 Installation Notes on page 13 Comments and suggestions SirsiDynix welcomes and appreciates your comments on its documentation. We want to know what you think about our manuals and how we can make them better. If you have comments about this guide, please send them to docs@sirsidynix.com. Be sure to include the title and version number of the guide and tell how you used it. Then tell us your feelings about its strengths and weaknesses and any recommendations for improvements. 1

6 Section 1: Overview 2 Release Notes

7 Section 2: Enhancements This section contains information about key features and enhancements in SirsiDynix Director s Station 4.9. Enhancements are modifications to the software from the previous version. The following table includes a list of version 4.9 enhancements, with their corresponding tracking numbers, and a brief description of how each enhancement improves functionality. Tracking No. Enhancement Details BIP-805 SDA-88 Director s Station 4.9 upgrade to SwiftKnowledge Implemented data extraction and ETL process Director s Station 4.9 includes an upgrade of the SwiftKnowledge platform to SwiftKnowledge version , which contains the latest engine fixes and implementations. The upgrade to SwiftKnowledge offers administrators a more stable platform to build on, as well as enhancing browser support. The data extraction and ETL processes replace the datainterchng report in the Symphony finished reports. These new processes allow extraction processes to run in parallel by using multi-threading. 3

8 Section 2: Enhancements 4 Release Notes

9 Section 3: System requirements There are specific hardware and software requirements for your Director s Station server, which are explained in this section. Also, because the Director s Station administration and user interfaces are both web-based, you must use supported web browsers for your workstations. This section explains these topics: Software requirements Software requirements on page 5 Hardware requirements on page 6 Requirements for installing and running the SirsiDynix Agent on page 6 Director s Station 4.9 is compatible with Symphony version and above. There are specific software requirements for both the Director s Station server and the admin or user workstations where you access Director s Station. Server requirements In order to use Director s Station 4.9, you must have this software installed on your Director s Station server: Windows Server 2003 Enterprise Edition with IIS 6.0.NET 3.5 with SP1 framework Microsoft SQL Server 2005 Enterprise Edition, SP1 or later, with Analysis Services 2005 Perl Supported web browsers The Director s Station Admin console and user interfaces require a compatible web browser to display Director s Station 4.9 functionality. You must have one of these browsers installed on any workstation where you want to access Director s Station functionality. Director s Station 4.9 supports these web browsers: Browser Supported Versions Platforms Internet Explorer 7.x, 8.x Windows, Macintosh Mozilla Firefox or earlier Windows 5

10 Section 3: System requirements Hardware requirements In order to successfully use Director s Station 4.9, the Director s Station server must meet certain hardware requirements. These requirements are specified by the number of seats that you need (or the number of users accessing the server simultaneously) and your total library circulation (or your annual circulation multiplied by the number of years of Director s Station data that you want to retain). There are no specific workstation hardware requirements. If you need Number of seats Use this hardware Total circulation Processors Memory Disk 1 to 3 Less than 1 million 1 CPU, quad core 4 GB 200 GB 1 million to 25 million 1 CPU, quad core 8 GB 500 GB 25 million to 50 million 1 CPU, quad core 16 GB 1 TB 5 to 15 1 million to 25 million 2 CPUs, quad core 16 GB 500 GB 25 million to 50 million 2 CPUs, quad core 32 GB 1 TB 15 to million to 50 million 4 CPUs, quad core 32 GB 1 TB Requirements for installing and running the SirsiDynix Agent The ILS server and any OPAC server on which you install the SirsiDynix Agent must meet the following requirements. For more information, see About the SirsiDynix Agent on page 13. The server must be a supported Symphony platform (any supported Windows, Solaris, Linux, AIX, or HP-UX server). The Java Platform, Standard Edition 6 release, 32-bit or 64-bit installation must be installed. SirsiDynix staff will install Java 6 on the server if it is not currently installed. Important: Not all server platforms support the installation of Java 6. For example, AIX must be at 5.3 to install Java 6. The JRE_HOME or JAVA_HOME environment variables must be set on the server. If the server is a Windows server, you must be logged in as the Admin user to install the SirsiDynix Agent and the SirsiDynix Agent service. If the server is a Windows server, you must configure the SirsiDynix Agent to run as the same user that runs Symphony (usually the sirsi user). This user must have the Log On as a Service privilege enabled. On Solaris, Linux, AIX, or HP-UX, the SirsiDynix Agent must be owned by and run by the sirsi user. 6 Release Notes

11 Section 3: System requirements The SirsiDynix Agent requires HTTP access to the Director s Station server. Depending on your network configuration, this may require changes in firewall settings. Requirements for installing and running the SirsiDynix Agent 7

12 Section 3: System requirements 8 Release Notes

13 Section 4: Fixed bugs This section contains a list of all resolved issues, or fixed bugs, for Director s Station 4.9. Resolved issues are problems that SirsiDynix has identified through the testing process and fixed for this version. The following table includes a list of fixed bugs for version 4.9, with their corresponding tracking numbers, and a brief description of each issue and how it has been fixed. Tracking No. Summary Description BIP-666 BIP-667 BIP-682 BIP-733 BIP-746 BIP-878 Measures reports show large negative numbers SQL Server Analysis Service stops and does not restart SQL Server stops data load when errors occur All Activity Measures report not complete SQL Server Service Pack 3 (and later) causes ETL to fail Vendor Cycles need larger column sizes Previously, the measures in the All OPAC Measures Report would show very large negative numbers when the calculation exceeded the boundary of the integer datatype. This has been fixed so that the Number of Searches, Number of Hits, and Number of Sessions measures are now updated from Integer size to BigInt. When the Microsoft SQL Server Analysis Service would stop, it would not restart on its own. This has been fixed so that Director s Station now automatically restarts the Microsoft SQL Server Analysis Service. Previously, the Microsoft SQL Server would stop loading data when certain errors occurred. This has been fixed so that when these errors are encountered, they are handled by the server and captured in a log file, and the Microsoft SQL Server continues to load data. After upgrading from Director s Station to 4.8.1, the All Activity Measures report did not include a complete set of command codes. This has been fixed so that the All Activity Measures report now contains all merged command codes. Previously, if you installed Microsoft SQL Server Service Pack 3 on the Director s Station server, the ETL would fail. This has been fixed so that Director s Station will now support Microsoft SQL Server Service Pack 3, as well as any future service packs. Large vendor records were not showing up in vendor stats in the All Acquisition Measure report. This has been fixed so that the numeric columns for the Vendor Cycle and Fund Cycle were modified to accept larger values in the All Acquisition Measure report. 9

14 Section 4: Fixed bugs 10 Release Notes

15 Section 5: Known issues This section contains information about known issues and possible work arounds in version 4.9. Known issues are reported issues that either do not affect the software or have not been fixed in this version. The following are known issues with version 4.9. Tracking No. Known Issue Details / Work Around BIP-953 UNI Error after ing any drill down report when using Firefox and up Bills do not display in Director s Station reports This issue only occurs when using Firefox or later. In any drill down report, if you reload the report after you it, an error displays and the report closes. To work around this issue, use an earlier version of Firefox or Internet Explorer 7.x or 8.x as your web browser. A change to billing payment data extracted from Symphony causes the ETL process to break, preventing billing data from displaying in All Bill Measures. If you are running Symphony or Symphony Patch Cluster 1, you must install Symphony patch S3.3.1.UNI *.tgz (where * is the Symphony platform_database). 11

16 Section 5: Known issues 12 Release Notes

17 Section 6: Installation Notes When you install or upgrade to Director s Station 4.9, you must install several components. You must install the Director s Station and SirsiDynix Host software on the Director s Station server. You must also install the SirsiDynix Agent software on the Symphony ILS server and any remote OPAC servers from which you want to import data to use within Director s Station. SirsiDynix will install or upgrade these Director s Station components for you, but there are some important notes that you should be aware of when working with these components. This section provides information about the SirsiDynix Agent which is installed on your ILS server and any remote OPAC servers as part of Director s Station 4.9. About the SirsiDynix Agent The SirsiDynix Agent is a background process that periodically extracts complete or updated data from your library s ILS and forwards it to the Director s Station server for reporting. The SirsiDynix Agent requires HTTP access to the Director s Station server. It periodically polls the Director s Station server to learn if there are scheduled tasks to do and sends the results of completed tasks using HTTP. Notifications If a SirsiDynix Agent is unable to communicate with the Director s Station Host, the Agent can send you an notification to alert you. This optional feature is enabled at the time the Agent is installed. If you want to receive these notifications, you will need to provide SirsiDynix with an address that the notifications can be sent to and information about your mail server. Contact SirsiDynix for details. Restarting the SirsiDynix Agent after a reboot If your ILS or OPAC is running on a Solaris, Linux, AIX, or HP-UX server, when you reboot your system, you must manually restart your SirsiDynix Agents. On Windows systems, the Agent is configured to run as a service that starts automatically. To manually restart your SirsiDynix Agent 1 Log in as the sirsi user. 13

18 Section 6: Installation Notes 2 Navigate to the directory where the Agent is installed (typically Unicorn/ Sdagent) and enter this command to start the Agent: bin/agent.sh start Starting the agent from the Sdagent directory instead of bin ensures that the logs are directed to Sdagent/logs. If you start the agent from the bin directory, the logs are directed to bin/logs instead. 14 Release Notes