Polaris - Management

July 24th, 2008 by Chandell Asuncion

Management 1, 2, and 3

  1. Management 1 - WORKSTATIONS: the Polaris Client (SEE: Polaris - Training, Cataloging, and System Administration)
  2. Management 2 - SERVER: SQL Client / Database (SEE: Below)
  3. Management 3 - SERVER: WINDOWS: HOST Services (accessible by right-clicking on “my computer” > manage > Services and Applications > Services) - (SEE: Below)

Microsoft SQL Server.2005 - Management Studio

  • SQL Server 9.0.3054
  • User ID and Password is needed

Databases (10 databases)

  • Not only are you working with multiple tables, and fields, but you also have multiple databases. This is important to understand for building queries
  • Database - expand to see a list of the tables. You won’t need a list of 1000+ tables, you need a list of the most common tables. A list (60+) has been forwarded to Clair, Grace and Maile.
  • Each table contains various columns and keys - expand table to see values.
  • Polaris, Demo Polaris, and Polaris Transactions
  • Polaris assigns different field names than you may be use to. i.e. Title, is listed in many forms, you will want to use BrowseTitle for your queries instead of Title, or SortTitle.
  • New Query: Assumes that you know SQL
  • Select GETDATE () - will retrieve the date and time.
  • QUESTION: Since this is an ORGANIZATION database, queries will return values for all branches?
  • Polaris Users Group: PUG: http://www.polarisusersgroup.org/ - request or share SQL queries
  • CUSTOM QUERIES, such as one to create reports on overdue fines by Homeroom, can be created on the system level and then accessed by all.

Management 3

  • Right Click > Manage > Services and Applications > Services - THESE MUST BE MANAGED REGULARLY
  • DNS Client - that no longer recognized a patron who is trying to login it is possible that the DNS services client has stopped running. (rare)
  • HTTP SSL: Not needed
  • Message Queuing - allows simultaneously communications for transactions with a number, such as checks outs.
  • Remote Procedure Call Error - (RPC) - something got in the way - and save again or repeat the procedure.
  • Electronic Resources Management System (3.3) Daemon - z39.50 uses this to communicate with other databases, and with the client. - When it fails it says “I don’t know what you are talking about” - it is possible that the z39.50 service has stopped. THIS IS ONE PLACE TO CHECK WHEN RECEIVING ERRORS - to see if the service has stopped.

http://www.polarislibrary.com/

  • Help Desk (Web userid and password - not tied to your AD login)
  • Customer Tools > Customer Extranet (Web userid and password - not tied to your AD login)

Posted in Polaris |

One Response

  1. Dan Waldron Says:

    Where did you get your blog layout from? I’d like to get one like it for my blog.

Leave a Comment

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.

Locations of visitors to this page