The Administrator Tools allow administrative (backend) management of the Insight database. Unlike Insight Studio, which communicates with the User Manager, Collection Manager and Personal Insight Manager, the Administrator Tools interacts with the database directly. Administrator Tools predate Insight Studio and currently contain features and functions not yet available in Insight Studio.

Common Tasks you May Need to Perform Using the Administrator Tools:

• • Adding an administrative user
  • Adding a new reference to a collection
  • Creating a multi-page document
  • Configuring the measurement tool
  • Managing Personal Collection User Groups
  • Batch media processing using MrSID encoding

Installing the Administrator Tools

The Insight Studio installers can be found in the admin_tools directory of CD2 - Clients. The installers are platform-specific and are separated into directories specific to each platform.

Running the Installer

Double-click the installer appropriate to your platform:

It may take a few minutes for the installer to load.
The nstaller runs in a series of panels, the first of which is an introduction. A panel index runs down the left edge of the display to let you know where you are in the process. You can always go back to previous panels and page back forward through panels you have already completed (the installer will retain your selections). The installer will not let you step past a panel when it needs information from you. Default values are provided on most screens. Documentation later in the manual will often assume that default settings have been used.

Selecting an Installation Type

The difference between a Typical and Advanced install set is subtle. Though both sets in fact install the debug console, the difference is in how debug console is invoked when running the Administrator Tools:
Typical
Administrator Tools will run without displaying the debug console unless the CTRL key is held down during startup. For the Mac you will need to launch the console window located in Applications/Utilities.
Advanced
Administrator Tools will always display the debug console on startup.

Choosing an Installation Location

Installation of the Administrator Tools can take up to 50MB, please plan accordingly when installing the server components. A default installation location will be offered on the Choose Install Folder panel, change as needed.

Creating a Shortcut Folder

The installer can create links to Administrator Tools and documentation. Choose the location for the links. On Windows, the default is to place a Shortcut to the Administrator Tools into the Luna Imaging program group, if present.

Configuring the Administrator Tools

A full installation or upgrade of 6.3 Server Components should automatically configure the Administrator Tools on the server with access to your collection, Personal Insight, and User Managers. As you install new collections, the installer will add entries for each collection you install or upgrade on this version of the Administrator Tools.

Copying the insightadminstore.dat Configuration File

The quickest method to configure a new version of the Administrator Tools is to copy insightadminstore.dat file from an existing version of the Administrator Tools.
To copy insightadminstore.dat:

1. Locate the existing installation of the Administrator Tools.

1. Find insightadminstore.dat in the installation directory.
2. Copy it to your network or to disk so you can transfer it to the other machine.
3. Copy insightadminstore.dat from your network or disk to the installation directory for your new machine.
4. Start the Administrator Tools.

To Add a New Collection, User, or Personal Insight Manager Manually

If you need to add a collection, User, or Personal Insight Manager manually:

1. Right-click on the Collection or User Manager node and select Register new from the pop-up menu.

1. Provide a name for your collection or User Manager.
2. Provide connection information. This can be found in the configuration file for the server component (in the insightServer.dat file in the server component's installation directory). Once you have the database connection information, enter the connection string, database username & password, query mode, driver name, and driver URL prefix.

1. Press Save.
2. The Administrator Tools should have added a new entry in the list with the Collection, User, or Personal Insight Manager you just added.

To connect to a User, Collection, or Personal Insight Manager

1. Right click on the desired node (User, Collection, or Personal Insight Manager).
2. Choose Connect from the pop-up menu.
3. Enter the administrative username and password.

Managing Administrative Users

The Administrator Tools manage all points of access for administrators and grants access to read or modify collection and User Manager configurations. The Admin Accounts section of the Administrator Tools is also where you control access to Insight Studio.

Adding Users and Managing Access to Insight Studio and the Administrator Tools

The Administrator Tools are quite powerful. They enable users to manage Insight's environment and to add, remove, and modify content in Insight collections. Be careful who you grant access to.
As different users may not need access to all Insight components, access is granted component by component. Access rights vary slightly between User Managers and Collection/Personal Insight Managers, but the process is essentially the same.
NOTE: Insight Studio not only requires an entry in the Admin Accounts, but a matching entry in your User Manager's "User List".
To add a user:

1. Start the Administrator Tools.
2. Connect to the User, Collection, or Personal Insight Manager.
3. Select the Admin Accounts node. User Manager: Admin Accounts is the first node under the expanded User Manager node.Collection/Personal Insight Manager: Admin Accounts is under Server Settings for your Collection/Personal Insight Manager. You will need to expand Server Settings to see Admin Accounts.
4. Right-click on the Admin Accounts node to add a new Admin Account. If you want to delete or modify an existing Admin Account, right-click on the entry in the list on the right and choose edit or delete.
5. Enter the username & password for the Admin Account you wish to add. Then grant the Admin Account the specific permissions you want.

Figure 9: Admin Account Settings for User Manager

Figure 10: Admin Account Settings for Collection Manager

1. 1. Server Admin Privileges: These are the access rights to User, Collection, and Personal Insight Managers. Rights can be separately assigned for viewing, editing, and deleting entries in the Managers, Collection Editor (running the indexer and MrSID or JPEG2000 Media Processing), access to Insight Studio, and Collection Delete Permissions.
   2. Account Admin Permissions: These are the permissions to add, modify, or delete administrative users.
2. Add the same user to the "user list" in your User Manager if you have not already. (for instructions on adding a user to the user list, please see Adding/Editing a User and Assigning Access to Collections Using User Groups in the Administrator Tools on page ).

Administrator Tools by Section

The Administrator Tools break up Insight backend management into small tasks, and allow administrators to adjust all aspects of Insight. Below is a list of each of the sections and an explanation of what can be accomplished in each.
User Manager
User List: The list of users for Insight.
User Groups: User Groups provide a backend handshake between a User Manager and a Collection Manager. You can associate User Groups with a set of users to grant access to Collections.
User Shares: Allows you to create and manage the shared directories in Insight.
Collections: Allows you to add/remove Collection references from the User Manager.
Image Groups: If you run the Administrator Tools from the same machine as the User Manager, you can manage the User Manager's image groups.
Collection Manager
Catalog Templates: Catalog Templates are separate from collections to enable you to reuse metadata schema across collections:
Field Groups: Field Groups are used to define related fields that should always be displayed together. Field Groups may be different from record types, which allow data to be displayed differently than how it is stored.
Record Types: Record Types are associations of fields grouped for data organization. Record Types represent the logical underlying structure of the metadata schema.
Fields: Fields are the lowest level representation of data. The Fields section (as opposed to Record Fields and Standard Fields) represents the basic information about a field. Fields contains low-level information as well as browser attributes.
Record Fields: Record Fields define data validation rules for a field.
Record Relationships: Record Relationships define connections between different record types.
Collection Settings: Collection settings are collection specific:
Collection Configuration: Here are the basic attributes of a collection, including display information, background image, Remote Launch Information, and other basic collection information.
User Groups: User Groups provide a backend handshake between a User Manager and a Collection Manager. On the Collection Manager, User Groups are associated with Profiles which allows assignment of rights and privileges to a logical group of Users (or to an individual User).
Media Groups: There are three types of media groups: temporary groups (created and deleted during user sessions), groups (which are the same as groups created in the Insight Java Client), and collections (which are just a special type of group).
Tables: Tables represent physical tables in the database, and are used to map fields and record types from Insight to the database.
Edit Joins: Joins map fields in Insight to tables (which ultimately connect them to the database). There are two types of joins:
Read-only joins allow Insight to act as a read-only "published" view of an existing database (non-Insight tables).
Read-Write joins allow Insight to both read and write to an existing database (non-Insight tables).
Multi-Page Documents: The Multi-Page Document Tool enables administrators to create multi-page documents or document templates. Once the structure of each multi-page document has been specified, administrators will need to run the indexer in order to make them visible within Insight.
Approval Levels: Approval levels allow you to control data and media publishing privileges for users.
Measurement Tool: The measurement tool enables you to auto-populate the Measurement Tool in the Image Workspace with values in your data.
Collection Editor:
Indexer:

1. 1. 1. 1. Creates multi-page documents based on the structures identified in the Multi-Page Document Tool.
         2. Manually parses fields marked as containing "Fuzzy Dates" and enables them to be searched using natural language date values.
         3. Updates thumbnail caches (performs a soft-restart of the Collection Manager).
         4. Imports data from a set of existing external data tables

Media Batches: All media processed using Insight Studio and the Administrator Tools are processed in Batches. The Media Batches tool enables users to publish, review, and link these batches.
Media Processing: Media processing enables you to import batches of media and create the set of Insight derivatives including either a MrSID file or JPEG2000 file.
Server Settings: these settings are collection independent:
Personal Collection User Groups: This option is only available on a Personal Collection Manager. Personal Collection User Groups provide a backend handshake between a User Manager and a Collection Manager.
Admin Accounts: Admin Accounts allow you to grant or restrict access to the Collection Manager via the Administrator Tools and Insight Studio.
Profiles: Profiles enable you to create a basic set of privileges for a set of users. Profiles control access to features within Insight and map to SPS's which associate with a Media Manager. Profiles also have a 1:1 association with Inscribe profile privileges, controlling access to Inscribe.
Inscribe Profile Privileges: Inscribe Profile Privileges enable you to control access to Inscribe, including who has the rights to view, add, modify or delete records, or to process media.
Connection Pools: Connection Pools place a limit on the number of connections a Collection Manager can support simultaneously.
Field Standards: Field Standards provide access to two areas:

1. field properties in the Insight Java client
2. mappings for Cross-Collection searching

Stop List: the Stop List contains a list of words that should not be indexed in the search tool. Stop lists often contain commonly used words like "and", "or", or "the".
LPS Data: LPS data is one component of a Media File's URL. Commonly, the LPS Data for an image matches the Media Processing Batch and Collection Identifier.
SPS Data: SPS Data allows you to map the base set of URL's for an image. There is at least one SPS entry for each media file size and type. SPS's ultimately allow you to distribute media across multiple machines.
Maximum ID's: Maximum ID's represent internal keys for Insight.