“10 DBMS WITH THEIR CORRESPONDING DDEVELOPER”
1. File.Transfer JAVA File Upload\Download Client - AhsiaSoft LLC File.Transfer JAVA™ is the answer. With advanced features, such as Drag-n-Drop file Upload, file management of client files, file compression, file limits such as size, type, location, restart of interrupted downloads, multiple file downloads, directory uploads, download failure detection, and industry standard data compression, it's no wonder that companies like Associated Press , Xerox, Disney, and Pepsi chose Ahsiasoft tools to aid their development efforts.
Publisher's Website:
http://www.ahsiasoft.com/ 2. Java Performance Validator - Software Verification Ltd Java Performance Validator allows you to identify code hotspots and bottlenecks in your application. There are six instrumentation methods and a sampling profiler for high speed, low overhead sampling. Displays include a realtime callstack, call graph, call tree, statistics, relations, integrated source code display and line timing statistics. Java Performance Validator also provides data HTML and XML export..
Publisher's Website:
www.softwareverify.com 3. NetAdvantage for JSF - Infragistics NetAdvantage for JSF is a set of rich, easily-styled AJAX Web UI components. The components include tree, grid, menu, tab, and numerous input controls. The core of our framework is AJAX-enabled and UI element-based for styling simplicity. We provide you with the ability to quickly and easily deliver that polished, professional look and feel your users expect from a world-class application.
Publisher's Website:
www.infragistics.com 4. Document Converter Suite - Amyuni Technologies Inc Amyuni’s new Document Converter gives you more document conversion power in a more streamlined product. Our flagship PDF Converter technology has been applied to RTF, HTML, Excel and JPEG formats and integrated them in one global Amyuni printer driver. The Suite is completely customizable. PDF, RTF, HTML, Excel and JPEG formats are modules contained in one global printer driver. You can buy only the modules you need.
Publisher's Website:
www.amyuni.com 5. Visual Java/SWING Components Library - Eltima Software GmbH Eltima Java Components will greatly extend the set of components available in standard visual library, bringing a whole lot of new ways to present your creativity to your customers and clients. Make your software look different! No routine coding – utilize your resources wisely! Based on standard components, this collection supports all Java Look and Feel such as Windows, Motif, Macintosh, etc, and adds new styles to your software, buttons, color dialogs, search fields, and more.
Publisher's Website:
www.eltima.com 6. Java Memory Validator - Software Verification Ltd Java Memory Validator is a memory analysis and heap inspection tool for detecting memory leaks in Java applications. Java Memory Validator allows you to analyse the allocations by allocation location, object type, object generation, allocation hotspot view, heap dump, leaked memory and virtual memory view. The heap dump also allows you to query the path to root and paths from root for any object in the heap dump. Poweful HTML/XML export and watermarking functions are also provided.
Publisher's Website:
www.softwareverify.com 7. 2D / 3D Line Graph - Sirius Computer Consultants Limited The 2D / 3D Line Graph provides both a client and server side solution for the incorporation of line graphs and charts into web pages. It provides versatile components so that web authors and Java developers can easily build and publish dynamic and interactive line charts.
Publisher's Website:
www.jpowered.com 8. edtFTPj - Enterprise Distributed Technologies edtFTPj is the first choice of Java developers worldwide for incorporating FTP functionality into their applications. edtFTPj is Open Source, licensed under the LGPL, the GNU Lesser General Public License. This means you can freely embed edtFTPj into your commercial Java applications, subject to the normal LGPL restrictions. Unrestricted (non-GPL) source licenses can be also be purchased.
Publisher's Website:
www.enterprisedt.com/index.html 9. JGraph - JGraph Ltd JGraph is the most powerful, lightweight, feature-rich, and thoroughly documented open-source graph component available for Java. It is accompanied by JGraphpad, the first free diagram editor for Java that offers XML, Drag and Drop and much more!
Publisher's Website:
http://www.jgraph.com 10. Database Workbench Pro - Upscene Productions Database Workbench Pro is a multi-DBMS developer tool that includes many feature like Diagramming Tools, Test Data Generator, Two-Way Visual Query Builder, Stored Code Debugger, SQL Insight, Parameter Insight, Cross DBMS Migration Tool, Cross DBMS Compare Tool, Visual Object Editors, Metadata Printing and much more.
Publisher's Website:
www.upscene.com “HOW DBMS HANDLE OR ACCOMMODATE DATA INPUT”
ABSTRACT
The recent advances in database technology have enabled the development of a new
generation of spatial databases, where the DBMS is able to manage spatial and non-spatial
data types together. Most spatial databases can deal with vector geometries (e.g., polygons,
lines and points), but have limited facilities for handling image data. However, the widespread
availability of high-resolution remote sensing images has improved considerably the
application of images to environmental monitoring and urban management. Therefore, it is
increasingly important to build databases capable of dealing with images together with other
spatial and non-spatial data types. With this motivation, this paper describes a solution for
efficient handling of large image data sets in a standard object-relational database management
system. By means of adequate indexing, compression and retrieval techniques, satisfactory
performances can be achieved using a standard DBMS, even for very large satellite images.
This work is part of the development of the TerraLib library, which aims to provide a
comprehensive environment for the development of GIS applications.
1 Introduction
The recent technological advances in database
technology are providing the support for major
advances in non-conventional database
applications. In the area of geographical
information systems (GIS), database technology
has enabled the complete integration of spatial
data types in object-relational data base
management systems, creating a new generation
of spatial databases (Shekhar, Chawla et al.
1999). This integration is bound to change
completely the development of GIS technology,
enabling a transition from the monolithic
systems of today (that contain hundreds of
functions) to a generation of spatial information
appliances, small systems tailored to specific
user needs (Egenhofer 1999). Three major
challenges in spatial database construction are:
(a) the efficient handling of spatial data types,
which include both vector (i.e., polygons, lines
and points) and raster data structures; (b) the
availability of tools for query and manipulation
of spatial data; (c) the support for advanced
applications, such as mobile GIS, spatiotemporal
data models(Hornsby and Egenhofer
2000), geographical ontologies, (Fonseca,
Egenhofer et al. 2002)and dynamic modelling
and cellular automata (Couclelis 1997).
One area of special interest is the efficient
handling of raster data, especially satellite images.
Remotely sensed imagery is one of the most
pervasive sources of spatial data currently
available to researchers who are interested in
large-scale geographic phenomena. The variety of
spatial and spectral resolutions for remote sensing
images is large, ranging from IKONOS 1-meter
panchromatic images to the polarimetric radar
images soon to be part of the next generation of
RADARSAT and JERS satellites. Recent
advances in remote sensing technology, with the
deployment of a new generation of sensors, have
improved considerably such application areas as
environmental monitoring and urban
management.
The construction of spatial databases that
handle raster data types has been studied in the
database literature and the main approach taken
has been to develop specialized data servers, as in
the case of PARADISE (Patel, Yu et al. 1997)and
RASDAMAN. (Reiner, Hahn et al. 2002)The
chief advantage of this approach is the capacity of
performance improvements, especially in the case
of large image databases. The main drawback of
this approach is the need for a specialized, nonstandard
server, which would greatly increase the
management needs for most GIS applications.
Therefore, the approach taken by the authors was
to include raster data management into objectrelational
database management systems. We
consider that, by means of adequate indexing,
compression and retrieval techniques,
satisfactory performances can be achieved using
a standard DBMS, even for very large satellite
images. This work is part of the development of
the TerraLib library, which aims to provide a
comprehensive environment for the
development of GIS applications(Câmara,
Souza et al. 2000).
With this motivation, this work describes
the conception and implementation of the image
data handling facilities in TerraLib. These
facilities include: (a) efficient storage and
indexing; (b) decoders for the different image
data formats; (c) basic data manipulation
functions; (d) iterators to provide a convenient
way of accessing the image data and developing
image processing algorithms. These facilities
are supported in different DBMS, including
ORACLE, PostgreSQL, mySQL and Access,
therefore allowing easy interface with existing
user environments.
2 The Raster Data Type in TerraLib
Images in TerraLib are handled by a generic
raster data type and are usually associated to a
cartographical projection and may be multidimensional,
e.g., the different spectral bands of
a remote sensing image. Images are usually
associated to different file formats, such as TIFF
and JPEG, and may refer to different
representations: (a) a synthetic image that has
an associated look-up table, where the pixel
value is associated to an RGB triple; (b) a multiband
image; (c) an image which is associated to
a categorical coverage; (d) an image where each
pixel has an ID of a unique spatial object. We
have defined three basic classes in TerraLib:
· A generic raster data structure
(TeRaster).
· A class that stores the metadata about a
raster data set (TeRasterParams),
including: image type, number of lines,
columns, and dimensions, resolution,
bounding box, cartographical
projection, rotation and skew
parameters, and compression technique
used.
· A class that handles different data
formats, including storage in a DBMS
(TeDecoder).
The two basic functions available to the
TeRaster class
“THE OTHER THING CAN A DBMS SOFTWARE DO WITH DATA”
This book teaches you how to use Structured Query Language, or SQL, which is a computer language used to define and manipulate databases. A database is a set of computer files for storing information that's used by a business or other organization. A typical business might keep information about customers and their orders, suppliers of materials, and employees who work for the company. Storing this type of information in computer files enables easy retrieval and updating as well as flexible analysis of the raw data to produce management reports, such as sales trends or average employee-benefit costs.
Of course, how "easy" and "flexible" it is to work with the data is determined largely by how well the database has been set up and by the capabilities of the database management system (DBMS), which provides the software to store and update database contents. In this chapter, we look at the building blocks of DB2 Universal Database for AS/400, or UDB/400, the DBMS that runs on IBM AS/400 computer systems. In subsequent chapters, we'll explore how to use SQL to create and manipulate a UDB/400 database.
UDB/400 is an integrated part of OS/400, the AS/400's operating system
1, which means that you don't have to buy UDB/400 as a separate software product and that any AS/400 application you write can take advantage of UDB/400 features. UDB/400 is also the only relational DBMS that runs on the AS/400.
2Figure 1.1 shows a simplified view of how UDB/400 fits into the AS/400 architecture.
As you can see, UDB/400 provides a DBMS layer that all high-level language (HLL) programs (i.e., RPG IV, Cobol, C/C++, and Java) use to access application data stored in UDB/400 files. You can also see that all utilities and remote applications — for example, a Java applet running in a Web browser and using Java Database Connectivity (JDBC) or a Windows application running on a PC and using Open Database Connectivity (ODBC) — must go through UDB/400 to access the AS/400 database. This integrated, uniform interface provides a high degree of consistency and control for AS/400 application developers.
If you're familiar with other operating systems and DBMS products, you'll find that UDB/400 has features of both conventional operating systems' file-management facilities and relational DBMS products. For example, like a conventional file-management facility, UDB/400 lets you use built-in HLL input/output (I/O) operations, such as Cobol's Read and Write verbs, to access data. Like other relational DBMS products, UDB/400 lets you access the same data using SQL. This "dual" nature of UDB/400 is even expressed in the nomenclature: UDB/400 documentation for conventional file access uses the terms "file," "record," and "field," while documentation for SQL access uses the comparable terms "table," "record," and "column," respectively.
In this chapter, we look briefly at both sides of UDB/400, considering it as a conventional file system and as an SQL-based relational DBMS. The remainder of the book concentrates on just the SQL perspective. At the end of this chapter, you'll find a list of
additional resources you can use to learn more about other aspects of UDB/400.
The AS/400 Integrated File System (IFS)
The UDB/400 database is arguably the most important and widely used way to store data on an AS/400, but it's not the only way. Everything stored on an AS/400 is stored in the AS/400's integrated file system (IFS). The IFS is organized as a hierarchical directory structure that includes 11 distinct file systems, as depicted in
Figure 1.2.
One of these file systems, QSYS.LIB, contains record-structured files managed by UDB/400, as well as other types of OS/400 objects. These record-structured files can contain text, numeric, and other forms of data and can be read and updated by HLL programs and SQL. As a shorthand, we use the term "QSys files" to mean those database files in file system QSYS.LIB. Creating and manipulating QSys files with SQL is the main focus of this book.
The "root" file system in the IFS provides a Windows-like directory structure for stream files — that is, files that contain a sequence (or stream) of bytes that aren't organized by the operating system into separate records, as the bytes in QSys files are. Like QSys files, stream files can contain text or numeric data, but stream files are not the main database files used by UDB/400.
Files in the root file system and some of the other non-QSYS.LIB file systems can be accessed by PCs and other computers connected to the AS/400; for the most part, these files have specialized purposes not directly related to UDB/400. As you'll see in
Chapter 3, however, UDB/400 files can reference the contents of files in the non-QSYS.LIB file systems
3, typically for image files and other types of data managed by non-AS/400 applications. You can learn more about the IFS and its file systems by consulting the resources listed at the end of this chapter.
OS/400 Objects, Libraries, and User Profiles
Because UDB/400 is an integral part of OS/400, it helps to have a general understanding of how OS/400 is organized and where UDB/400 fits in. Everything in the OS/400 operating system, including the database, is organized as objects. OS/400 identifies more than 80 types of objects that can be stored in the QSYS.LIB file system, including libraries, programs, database files, display and printer files, user profiles, message queues, SQL packages, and so forth.
4 OS/400 also has a few object types for files outside the QSYS.LIB file system, but these object types aren't of central importance in developing typical AS/400 business applications. In the following discussion, we concentrate just on QSYS.LIB objects and, most important, on database files, which are what most AS/400 applications use.
Like other operating systems (e.g., Unix), OS/400 stores program instructions, application data, and other system components on disk, loading them into main memory as needed. But, unlike most other operating systems, OS/400 doesn't let you get at the bytes on disk or in memory directly. Instead, you must always use specific commands or other system interfaces that are valid for each type of object. For example, you can't execute a database file or perform a file-update operation on a program object.
5 The system prevents any attempt to use an invalid operation on an object altogether rather than let it proceed and possibly cause damage or produce undesirable results. This protection is uniform across all AS/400 operations, including user commands, application code, and operating-system operations. Object encapsulation is so integral to the AS/400 that there are no "back doors" that a system programmer can use to subvert the integrity of an OS/400 object.
6 As we progress through UDB/400's capabilities, you'll learn about various types of OS/400 objects and the way to use them.
