1 / 12

Handle System Usage at Content Directions

Handle System Usage at Content Directions. Andy Stevens Content Directions, Inc., Brooklyn, NY Handle Workshop CNRI, Reston, VA September 20, 2002. Server Environment. Red Hat Linux 7.0, 2.2.16 kernel JDK 1.3.1 (Blackdown distribution) Handle Server hsj-5.2.0

shiro
Download Presentation

Handle System Usage at Content Directions

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. Handle System Usage atContent Directions Andy StevensContent Directions, Inc., Brooklyn, NY Handle Workshop CNRI, Reston, VASeptember 20, 2002

  2. Server Environment • Red Hat Linux 7.0, 2.2.16 kernel • JDK 1.3.1 (Blackdown distribution) • Handle Server hsj-5.2.0 • One of many server programs running on a dual-processor 800MHz Compaq Proliant Environment Issues • Poor Linux threading: Must run Handle Server in green thread mode to avoid running out of Unix processes • Linux/JDK1.3 stacksize bug

  3. Installation Issues • Easy to install — if you know Java. YMMV. • Wrote our own start/stop shell script (would be useful to include in distribution for Linux & Solaris users) • Our server configuration: standalone (no mirroring)

  4. Software Development w/ Handle Client • We use our locally installed Handle Server for software development and testing only. All “production” Handles are currently loaded into the CNRI-administered global server (DOI server) • Occasionally have a software bug due to increased network latency and replication latency on remote production server. • Development server usage: currently loaded with ~20,000 Handles (wish there was an easy way to figure out this number!)

  5. Bugs discovered in Handle Server • Corruption of large Handles (fixed) • Cannot force-delete handles remotely • Cache TTL is ignored (defaults to 24 hours) • “List Handles” doesn’t always work Bugs discovered in Handle Client • No way to turn off stderr in C client?

  6. Handle Server Wish List • Include Javadoc with server distribution • Would like method to automatically checkpoint server (would like ability to execute most administrative functions from a command line instead of GUI tool) • Better reporting: ability to list homed prefixes, list handles, etc.

  7. How We’re Using Handles • Ordinary URL redirects (“unilinks”) • Multiple Resolution (“MultiLinks”) • Store label/URL pairs as Handle values of type “MULTIRES” • MultiLink choices are displayable by any knowledgeable client (CDI has written one) • Use URL value as default for non-MultiLink clients.

  8. Example MultiLink Handle

  9. Example Implementation

  10. Example of embedded MultiLink using CDI software library

  11. Hierarchical MultiLink

  12. Other R&D • Metadata Database: Oracle database to hold metadata for each Handle. • “Pinger”: ping all URLs for a given Handle to check for bad links, etc. • “Autolinker”: Automatically generate MultiLinks based on metadata.

More Related