Browse Prior Art Database

A Method/Process For Packaging and Un-packaging of Files Being Transported Between a Batch Load Client and Digital Library Servers

IP.com Disclosure Number: IPCOM000014338D
Original Publication Date: 2002-Oct-16
Included in the Prior Art Database: 2003-Jun-19
Document File: 1 page(s) / 40K

Publishing Venue

IBM

Abstract

IBM DB2 Digital Library (DL) does not provide a batch loading mechanism. Furthermore, for large amounts of data the interactive loading operation suffers from numerous performance problems. A process was devised for loading data within DL using a batch load mechanism. One of the performance problems involves moving the meta data files and BLOBS into their corresponding library server and object servers respectively. This performance problem stems from the fact the files are being moved via the DL isolator one at a time. Within the batch loading mechanism, an algorithm exists for checking the files sizes and quantities to determine the most optimum manner in which to transfer the BLOBS to the object server. In addition, the meta data is transferred to the library server and loaded. The files being moved are analyzed for size and quantity to determine the most optimum manner in which to transfer them versus always transferring them one at a time in a sequential manner. Our mechanism is faster than the existing DL isolator mechanism. At this time, no other mechanism is known. 1

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

Page 1 of 1

  A Method/Process For Packaging and Un-packaging of Files Being Transported Between a Batch Load Client and Digital Library Servers

    IBM DB2 Digital Library (DL) does not provide a batch loading mechanism. Furthermore, for large amounts of data the interactive loading operation suffers from numerous performance problems. A process was devised for loading data within DL using a batch load mechanism. One of the performance problems involves moving the meta data files and BLOBS into their corresponding library server and object servers respectively. This performance problem stems from the fact the files are being moved via the DL isolator one at a time. Within the batch loading mechanism, an algorithm exists for checking the files sizes and quantities to determine the most optimum manner in which to transfer the BLOBS to the object server. In addition, the meta data is transferred to the library server and loaded.

The files being moved are analyzed for size and quantity to determine the most optimum manner in which to transfer them versus always transferring them one at a time in a sequential manner. Our mechanism is faster than the existing DL isolator mechanism. At this time, no other mechanism is known.

1