Browse Prior Art Database

Built-in routines to manage JAR files execute external to the database Disclosure Number: IPCOM000022150D
Original Publication Date: 2004-Feb-27
Included in the Prior Art Database: 2004-Feb-27
Document File: 1 page(s) / 26K

Publishing Venue


This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 1

Built-in routines to manage JAR files execute external to the database

In the e-business access to database industry, there is a need for server-based workloads, as the SQL to be performed against the database server must be done with a minimum of network transmission overhead time. These server-based workloads consist primarily of invocations of stored procedures and user-defined functions, written either entirely in SQL or in a fully-capable programming language such as C, COBOL, or Java.

The ANSI specification for stored Java routines specifies that built-in routines SQLJ.INSTALL_JAR, SQLJ.REMOVE_JAR, and SQLJ.REPLACE_JAR be provided. One problem with this is that JAR objects can be large, and processing them can interfere with database engine storage requirements. In addition, any file system failures that occur can interfere with database engine processing, and even potentially cause an outage of the database management system. Our implementation moves the routines into a process external to the database engine, providing a more robust solution in that failures or overlays associated with processing these JAR objects are fenced away from the database engine and storage. In addition, as external routines they offer more flexibility for security, as either the system or the end user's identity can be assumed for security checks when executing the built-in routines.