MIPL Databases

MIPS maintains databases for each project during active flight operations and works with the Planetary Data System (PDS) Imaging Node to transfer databases for post mission archive.

The content and design of the databases are determined by each project's data processing, distribution, and decision support requirements. Some projects (i.e. DS1) store a very limited amount of processing information and use the database primarily to support automated data distribution via FEI while others have extensive information stored in the database which is used to trigger/automate data processing and support near-realtime decision support applications such as the Planetary Image Atlas.

A database schema describes the database tables and fields. Case is significant when interacting with the database. If mixed case names are specified in your access parameters (username, password, database or server name) or the Database SIS (mars98, gll) it must be entered as shown.

Users are not required to be proficient in Structured Query Language (SQL) a language for communicating with relational database systems. But the more SQL you know, the easier it will be. Any adhoc access to MIPL databases (i.e. using dbq, dbView or dbWindows) will require knowledge of at least the SQL select command.

SQL References:

1)  Sybase Adaptive Server Enterprise Transact-SQL User's Guide,
    32300-01-1150, Sybase Inc.

2)  Sybase Adaptive Server Enterprise Reference Manual,
    Volume 1: Commands, Functions and Topics,
    32401-01-1150, Sybase Inc.

The Sybase Relational Database Management System (RDBMS) has been selected and implemented to support Real Time processing, science analysis and data distribution within MIPL and MIPL User Community.

The Sybase client/server architecture allows us to split database applications between a client application running on one machine and a server application on another machine; both within the same organization or between different parts of the world.

A single Sybase Server can manage many different databases, and MIPL maintains multiple Sybase Servers, for example separate test and operations servers. When using MIPL applications that interface with a database you will indicate which Sybase Server you wish to use. Most users have Sybase accounts on the MIPL Operational Server - MIPS1.

In addition to providing a Sybase Server when running database applications, the user must provide a Sybase username, password and database name. This information is provided by the MIPS Sybase System Administrator (Jan.Yoshimizu@jpl.nasa.gov).

The MIPL Database Password Server provides a user's Sybase password to kerberized MIPL applications automatically, without prompting the user for it.

The Database Password Server frees users from the need to remember their Sybase password and provides another layer of security as the user no longer must pass the password (exposed for anyone to view) to MIPL applications. It also allows applications to run in batch.

To use the Database Password Server with MIPL applications the user is required to:

• Install Kerberos client version 4
• Obtain a Kerberos Principle account and get registered in the MIPL Database Password Server contact the Password Server Administrator (Jan Yoshimizu) or the MIPL Project CogE for your project.