Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This document is intended mainly for system administrators and secondarily for Insight administrators to provide context and information on how to Install & Configure Insight and LUNA. Readers are expected to have a basic knowledge of the UNIX / Windows Operating Systems, Microsoft SQL Server / Oracle Databases / MySQL, and Apache Tomcat and Jboss JSP Server.
Please note that while references to Deploy Director and Browser Insight remain in this document, Deploy Director is no longer supported beyond 5.6 and Browser Insight is no longer supported beyond 6.2.



Figure 1: Insight and LUNA Component Diagram

LUNA Components are as follow:


LUNA Publisher: Schedules and is used to pull data out of the Insight Collection Manager, storing it in an XML format. The LUNA Publisher then converts the archive data into a Lucene index for each collection and merges all Collection indexes into one single search index. Once merged, the LUNA Server is placed into a maintenance mode and the newly merged index replaces the existing one.
LUNA: LUNA is the dynamic web based front end to Insight collections. With LUNA, users can perform simple keyword searches as well as more complex structured queries, and control how they view, browse, and organize their results to create groups and presentations. LUNA includes the Web 2.0 tools your users are demanding which enable them to save and share their work by linking and embedding any view, image, group, or presentation.
LUNA Server: The LUNA Server is the server side component behind the LUNA client. Collections published to LUNA are indexed on the LUNA Server. The LUNA Publisher will automatically update the indexes based upon a schedule that you define.

Insight's Components are as follows:


User Manager: The User Manager functions as a single point of entry for all Insight Collections and Personal Insight Managers. It consolidates the functions of authentication and authorization for all shared resources within Insight and for LUNA. The User Manager can integrate with an existing security infrastructure if an institution already has a single sign-on solution in place. The User Manager also provides access to resources such as shared folders and groups within Insight. LUNA enables end-user management of viewing preferences, and storage folders for media groups and presentations.
Collection Manager: The Insight Collection Manager provides a common interface between client requests and the underlying data repository. Each Collection Manager may contain multiple collections and Virtual Collections of consistent or heterogeneous structures. The Collection Manager also functions as a broker between the clients (the Insight Java Client, Inscribe data editor, Studio (LUNA Publisher and XML Gateway) and the underlying database, coordinating search requests, and data updates.
Personal Insight Manager: The Personal Insight Manager is a specialized version of the Collection Manager which supports the creation of Personal Collections with the Insight Java Client.
Media Manager: The Insight Media Manager is built around a servlet, and manages access to Insight's media content. The Media Manager supports direct upload of processed content and also manages access to the JPEG2000 wavelet images that power Insight's Image Workspace.
Java Client: The Insight Java Client provides an additional interface for searching, viewing, and managing images, audio, video, and other media. The Java Client also provides end-user collection building tools with Personal Insight and the ability to create Virtual Collections – a subset of content with different access levels.
Inscribe®: The optional Inscribe data editor is an end-user cataloging tool designed to support all of an institution's cataloging needs. The Inscribe data editor includes built-in support for controlled vocabularies, date and numeric validation, and complex data relationships. Inscribe also supports an institution's workflow requirements by facilitating the publishing and review processes.
Studio: Studio provides collection administrators with the tools to build and manage collections. Studio is a wizard-based tool supporting batch processing of media, batch import of metadata, user management, catalog template creation and management, and other basic functions. The LUNA Publisher is accessible from within the Studio client.
Administrator Tools: The Insight Administrator Tools allow a collection administrator to dynamically manage collections. Components of the Insight Administrator Tools include tools for batch media processing, user and resource management, data indexing, and configuring of the search and user interface.
JPEG2000 Wavelet Encoder: The Administrator Tools and Studio include a JPEG2000 Wavelet Encoder. Wavelet encoded images improve performance when accessing large images, reduce storage requirements, and optimize network usage on image delivery.
Insight XML Gateway: The XML Gateway provides a web-services based interface for searching and retrieving content stored within Insight collections. The XML Gateway is middleware which allows backend interaction between Insight and other XML aware applications.






Finding Installers and Tools on the CDs

Insight 6.3 is available for download in the Support section of the Luna Imaging website. There is one CD for the general installers, one for the clients and one if you are upgrading Insight. Below is a list of the tools / installers available on each CD:
Table 1: Distribution CD Contents

 

CD1 – Insight

CD2 – Clients

CD3 –Upgrade

Insight Suite Installer including installers for: User Manager, Collection Manager, Personal Insight Manager, BrowserInsight, XML Gateway, Media Manager, Insight Studio, Tomcat 5.0

X

 

 

Insight Upgrade Installer including upgrade installers for: User Manager, Collection Manager, BrowserInsight, XML Gateway, Media Manager, Tomcat 5.0

 

 

X

Insight 6.3

X

X

X

Inscribe 6.3

X

X

X

Insight Studio 6.3

X

X

X

Insight Administrator Tools 6.3

X

X

X

Command Line Indexer

X

 

X

Background template

X

 

X

Browser background template

X

 

X

XML Gateway test application (with source code)

X

 

X

Log Analyzer

X

 

X

Insight Launch Manager

X

 

X

Insight client bundles for Deploy Director

 

 

X

Simple Search Servlet for the Insight XML Gateway

X

 

X

Collection Reporting Tools

X

 

X

Check Hostname

X

 

X


The LUNA Suite is contained on it's own DVD and is available for download at the Luna Imaging Inc Support website.

Locations of Commonly Used Components

The Suite installer for Insight 6.3 manages where all of the components are installed.

Platform

Location

Windows

C:\program files\LunaImaging\6.x

Solaris / Linux

/home/<username> /LunaImaging/6.x


Basic structure for the Insight Server Components

This structure may be useful in understanding where to find common components.
Figure 2: Insight Installation Directory <installation directory>

----- AdminTools

 

----- user_manager

 

----- InsightUserServer.dat ? User Manager configuration file

----- collection_manager

 

----- <Collection Short Name1>

 

----- InsightServer.dat ? Collection Manager

 

----- <Collection Short Name2> configuration file

 

----- …

----- personal_insight_manager

 

----- <Collection Short Name1>

 

----- InsightServer.dat ? Personal Insight

 

----- <Collection Short Name2> configuration file

 

----- …

----- tomcat

 

----- bin

 

----- conf

 

----- server.xml where BrowserInsight,

 

----- Catalina ? XML Gateway and Media

 

----- localhost Manager contexts are stored

 

----- logs ? Tomcat Logs

 

----- …

----- License-Files ? Where the Insight 6.3

----- media_manager license key is kept

 

----- servlet

 

----- WEB-INF

 

----- themes ? where Insight saves background

 

----- support images (themes)

 

----- Tomcat_conf_additions.txt

 

----- Resin_conf_additions.txt

 

----- MediaManager.dat ? Media Manager configuration file

----- browserInsight

 

----- servlet

 

----- support

 

----- Tomcat_conf_additions.txt

 

----- Resin_conf_additions.txt

 

----- BrowserInsight.conf ? BrowserInsight configuration file

----- xmlgateway

 

----- servlet

 

----- WEB-INF

 

----- web.xml ? XML Gateway configuration file

 

----- support

 

----- Tomcat_conf_additions.txt

 

----- Resin_conf_additions.txt

----- InsightStudio

 

----- Utilities

 

------check_server_version ? a script to display the version

  1. of all server components

    Basic Structure of the Media Manager Source File Directory


    The Media Manager organizes files by size / file-type, collection, and batch. The top level directory is the size / filetype (one size for each JPEG derivative, then SID, Audio, Video, and JP2K). Content is organized in this sub-directory structure to ensure that the Media Manager can manage content from multiple collections as well as multiple Collection or Personal Insight Managers.
    Figure 3: Media Manager Directory Organization
    <media source directory>

----- Size0

 

----- Collection-Triplet

 

----- BatchID

 

----- Images

----- Size1

 

----- Collection-Triplet

 

----- BatchID

 

----- Images

----- Size2

 

----- Collection-Triplet

 

----- BatchID

 

----- Images

----- Size3

 

----- Collection-Triplet

 

----- BatchID

 

----- Images

----- Size4

 

----- Collection-Triplet

 

----- BatchID

 

----- Images

----- JP2k

 

----- Collection-Triplet

 

----- BatchID

 

----- Images

----- AUDIO

 

----- Collection-Triplet

 

----- BatchID

 

----- Audio

----- VIDEO

 

----- Collection-Triplet

 

----- BatchID

 

----- Video

----- QTVR

 

----- Collection-Triplet

 

----- BatchID

 

----- QTVR

----- MISC

 

----- Collection-Triplet

 

----- BatchID

 

----- Files

----- SOURCE

 

----- Collection-Triplet

 

----- BatchID

 

----- Images

The second piece of the directory structure is the Collection-Triplet, which is the combination of the InstitutionID, CollectionID, and Virtual CollectionID, separated by hyphens. The final directory is the Media Batch, which helps with the organization of content based on processing logic – Media Batches are created by the end-user and may separate images digitized at one time, or simply imported at one time.

  • No labels