1 / 19

PUG 2008

PUG 2008. Vince Messina Polaris. When, Why and How to Upgrade Polaris Servers. Every 3-5 years New software and hardware Call on us. When. Server warranties are three to five years Microsoft releases new versions of the O/S and SQL at about the same regularity

jaden
Download Presentation

PUG 2008

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PUG 2008 Vince Messina Polaris

  2. When, Why and How to Upgrade Polaris Servers • Every 3-5 years • New software and hardware • Call on us

  3. When • Server warranties are three to five years • Microsoft releases new versions of the O/S and SQL at about the same regularity • Dell processors change every few months Faster with more memory (all servers shipped over the last three years have 64-bit processor but need 64-bit O/S)

  4. Polaris 3.4 • Media Record Management System: • Polaris Fusion • Changes to PAC to support the new content delivery • Changes to Tech Client to support data management • New Label Manager • Computype Spine Label System in 3.3 • Supports virtually any format • Find Tool • New Search Access Points (30>) • New TOM (for Fusion) • Consistent capitalization • Sys. Admin. • New Parameters, Profiles & Tables

  5. Polaris 3.4 • Full Unicode support of MARC • (In 3.5 - Search can include diacritics) • PAC Applications • Saving a Title to an Existing Title List • Book Jackets in New Titles Lists • Integration of ChiliFresh Content • Patron Services/Circ • Maintaining Queue Position for Re-Activated Requests • Phone Number Added to E-Mail Notices • Credit Card Processing

  6. Polaris 3.4 • Re-architectured Licensing Model We are developing a new licensing model that will support branch level licensing and number of seats per license. (Will allow individual libraries to add what were formerly system level options e.g. Outreach, Syndetics, etc.) • Integration with 3rd party partner Talking Tech that provides inbound and outbound telephony including text messaging

  7. Polaris 3.5 (Q1 2009) • Polaris API to support external PAC development. • Multi-Lingual Notification Processing, Print and E-mail • Multi-Lingual Telephony Support, Inbound and Outbound • Floating Collections support • SQL Failover and Server Clustering • Acquisitions and Serials Workflow Enhancements • Currency Conversion • Systems Admin tuning to support 150-plus branches • Loading of Canadian Postal Codes • Course Reserves extension • Tentative: Load Balancing of Holds • Tentative: Line Item Specific Holds • Branch level Telephony • More than 2 Doz. Other features

  8. Pending Projects • PUG development commitments • Fiscal Year Rollover • ITG Self-Check Integration (RFID, EM Security, Media Locks) • International Date Support & Currency Conversion (Canada) • Patron Associations • Patron Merging • Patron Transaction Scrubbing • Rotating Collections • Remaining PUG Developments • Forum/Listserv

  9. System Requirements

  10. Polaris 3.3 • Windows Server 2003 (32 bit) • 32 bit server (or 64-bit running32-bit mode) • SQL Server 2000 or 2005 • Windows 2000, Windows XP, Windows Vista Polaris 3.4/5 • Windows Server 2003 or Server 2008 (32 or 64-bit) • 32 or 64-bit server • SQL Server 2005 or SQL 2008 – (32 or 64-bit) • Windows XP or Windows Vista • Will not support Windows Server 2000 or SQL 2000

  11. Polaris 4.0 • 64-bit Server & O/S • Windows Server 2003 or server 2008 • SQL Server 2005 or SQL 2008 • Windows XP or Windows Vista

  12. Polaris Server Configurations • Production • D/C • Training, Terminal, Reports, PAC, Telephony, Exchange, Web

  13. Getting started • Determining what you have • Which servers • Licenses • Changes • Price Quote • Purchase • Installation

  14. Remote vs. Onsite Installation • Onsite – no interruptions • Scheduled/finite time from start to finish • Other services as required by library • Add server(s) to Domain & assign I/P • Install the O/S • Move Active Directory from Server to Server

  15. Polaris Installation • Verify memory • Verify Updates and Service Packs • Install the latest Pre-requisites • Verify security settings • Backups, backups, backups! • Process all messages in Msg. Queue • Disable Site Scan & stop Polaris services • Remove SimplyReports, including Scheduling Exec. • Verify SQL Server status – upgrade if necessary

  16. Polaris Installation • Run Setup from Polaris Build Folder • Network Service full control permission from Polaris directory • Install Clients on Server • Verify Reporting Services • For separate web server, install server side • Upgrade Terminal Server client (if necessary) • Install Polaris licenses, SIP, PIM, SimplyReports... • Populate SIP Service ports where necessary • Adjust job history for SQL to 3 months

  17. The end is near • Q/A • Reconfigure and enable latest version of Site Scan • Cleanup old installation and backup files

  18. An ongoing process New Server technology New Microsoft development New Polaris features

  19. PUG ‘08 800-272-3414 vince.messina@polarislibrary.com Thank you

More Related