Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

A Fast, Secure Way of Transmitting Data Between Java and DB/2

IP.com Disclosure Number: IPCOM000013588D
Original Publication Date: 2000-Feb-01
Included in the Prior Art Database: 2003-Jun-18
Document File: 1 page(s) / 47K

Publishing Venue

IBM

Abstract

Disclosed is the concept of a fast, secure way of transmitting data between Java* and DB/2. This is very important to Java Applets and Applications since most problems with Java based business applications are performance and backend stability. Simply put, this concept will decrease the amount of time a user has to wait for an update or query to be made. The concept is as follows. A brief description of each step will be directly below the concept: Java Application or Applet issues a call to a Java stored procedure requesting the retrieval or update of data. The Java Stored Procedure executes whatever operations the client has asked for.

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

Page 1 of 1

A Fast, Secure Way of Transmitting Data Between Java and DB/2

    Disclosed is the concept of a fast, secure way of transmitting data between Java* and DB/2. This is very important to Java Applets and Applications since most problems with Java based business applications are performance and backend stability. Simply put, this concept will decrease the amount of time a user has to wait for an update or query to be made.

The concept is as follows. A brief description of each step will be directly below the concept:

Java Application or Applet issues a call to a Java stored procedure requesting the retrieval or update of

data. The Java Stored Procedure executes whatever operations the client has asked for.

Before the Stored Procedure terminates, a Serialized Java Object is passed back through a BLOB(Binary

Large Object) stored procedure parameter. The client receives this Serialized object and Deserializes it.


1.


2.


3.


4.

This is a brief description of each step in the concept:

Step 1

Normally the typical business application will allow users to manipulate data in a timely and intuitive way. Java has allowed developers the freedom to not only do this, but to provide an intuitive GUI (Graphical User Interface) on whatever computer platform the user runs on. This sounds great and the Java Applet or Application might look great, but performance is a problem that has plagued Java since day 1. This theory takes 2 great technologies (DB/2 and Java) and mixes them to the point of clear transition of data from DB/2 to Java. This step is essential since this step initiates the conversation between the client and server. The client should send a serialized object to the server which in turn tells the Stored Procedure exactly what data to query or update.

Step 2

The Java Stored Procedure should take the se...