Method and apparatus for validating and configuring database transaction requests from multiple clients

• US 7,299,234 B2
• Filed: 01/14/2004
• Issued: 11/20/2007
• Est. Priority Date: 01/14/2004
• Status: Expired due to Fees

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Morgan, Fabian F., Phillips, Brent Russel, Marappan, Kumar, Focazio, Robyn Lee
• Primary Examiner(s): Alam; Hosain
• Assistant Examiner(s): LIN, SHEW FEN
• Application Number:
  US10/756,932
• Publication Number:
  US 20050165776A1
• Time in Patent Office: 1,406 Days
• Field of Search: 707100-104, 709/229, 709/223
• US Class Current: 707/703
• CPC Class Codes: G06F 16/95 Retrieval from the web
• CPC Class Codes: Y10S 707/959 Network
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

The present invention provides a method, computer program product, and a data processing system for validating and configuring a database transaction request. A first transaction criteria of a plurality of transaction criteria is identified in a singleton in-memory object by reading a client identifier element value specified in a database transaction request. Each of the plurality of transaction criteria is associated with a respective client. Default data for a database path is determined based on the client identifier element value. A database command is generated that includes the default data.

Claims

1. A method for validating transaction requests from a plurality of clients to access a database, the method comprising the computer implemented steps of:

providing an interface to validate transaction requests to access a database, using a plurality of validation criteria, from said plurality of clients having different requirements for said validation criteria, said interface in a singleton in-memory object;

using said different requirements to validate said transaction requests from said plurality of clients;

said interface including;

said database command including a plurality of mandatory fields;

associating a first one of said plurality of validation criteria with one of said plurality of mandatory fields, wherein data that is received for said first one of said plurality of validation criteria is included in said one of a plurality of mandatory fields;

defining a first requirement for validating transaction requests from first ones of said plurality of clients using said first one of said plurality of validation criteria, said first requirement requiring data to be included in said transaction requests from said first ones of said plurality of clients for said first one of said plurality of validation criteria;

defining a second requirement for validating transaction requests from second ones of said plurality of clients using said first one of said plurality of validation criteria, said second requirement not requiring data to be included in said transaction requests from said second ones of said plurality of clients for said first one of said plurality of validation criteria;

in response to receiving a first transaction request from one of said first ones of said plurality of clients;

validating said first transaction request responsive to said first transaction request including first data for said first one of said plurality of validation criteria; and

generating a database command that includes said first data in said one of said plurality of mandatory fields after said first transaction request has been validated;

in response to receiving a second transaction request from one of said second ones of said plurality of clients;

validating said second transaction request determining default data that has been specified for said second ones of said plurality of clients to use for said first one of said plurality of validation criteria response to said second transaction request not including said second data, and generating a database command that includes said default data in said one of said plurality of mandatory fields after said second transaction request has been validated; and

transforming, by a data processing system, said transaction requests into a database command by generating said database command in response to validated transaction requests, wherein said database command is generated in response to a validated transaction request regardless of which one of said plurality of clients sent said validated transaction request.

2. The method of claim 1, further comprising:

associating a second one of said plurality of validation criteria with a second one of said plurality of mandatory fields;

defining a third requirement for validating transaction requests from said first ones of said plurality of clients using said second one of said plurality of validation criteria, said third requirement not requiring data in said transaction requests from said first ones of said plurality of clients for said second one of said plurality of validation criteria; and

in response to receiving said first transaction request;

validating said first transaction request if said first transaction request includes said first data and regardless of whether said first transaction request includes second data for said second one of said plurality of validation criteria;

if said first transaction request does not include data for said second one of said plurality of validation criteria, determining second default data that has been specified for said first ones of said plurality of clients to use for said second one of said plurality of validation criteria; and

if said first transaction request has been validated, generating a database command that includes said first data in said one of said plurality of mandatory fields and said second default data in said second one of said plurality of mandatory fields.

3. The method of claim 1, further including:

in response to receiving said first transaction request;

generating an exception if said first transaction request does not include said first data, wherein said first transaction request is not validated.

4. The method of claim 1, wherein the database command is a structured query language command, and wherein each one of said transaction requests is included in an extensible markup language document.

5. A computer program product in a data processing system comprising:

a computer readable medium including instructions for validating transaction requests from a plurality of clients, said computer program product including;

instructions for providing an interface to validate said transaction requests to access a database, using a plurality of validation criteria, from said plurality of clients having different requirements for said plurality of validation criteria, said interface in a singleton in-memory object; and

instructions for using said different requirements to validate said transaction requests from said plurality of clients; and

said interface including;

said database command including a plurality of mandatory fields;

instructions for associating a first one of said plurality of validation criteria with one of a plurality of mandatory fields of said database command, wherein data that is received for said first one of said plurality of validation criteria is included in said one of said plurality of mandatory fields;

instructions for defining a first requirement for validating transaction requests from first ones of said plurality of clients using said first one of said plurality of validation criteria, said first requirement requiring data to be included in said transaction requests from said first ones of said plurality of clients for said first one of said plurality of validation criteria;

instructions for defining a second requirement for validating transaction requests from second ones of said plurality of clients using said first one of said plurality of validation criteria, said second requirement not requiring data to be included in said transaction requests from said second ones of said plurality of clients for said first one of said plurality of validation criteria;

in response to receiving a first transaction request from one of said first ones of said plurality of clients;

instructions for validating said first transaction request responsive to said first transaction request including first data for said first one of said plurality of validation criteria; and

generating a database command that includes said first data in said one of said plurality of mandatory fields after said first transaction request has been validated;

in response to receiving a second transaction request from one of said second ones of said plurality of clients;

instructions for validating said second transaction request, determining default data that has been specified for said second ones of said plurality of clients to use for said first one of said plurality of validation criteria responsive to said second transaction request does not include said second data, and generating a database command that includes said default data in said one of said plurality of mandatory fields after said second transaction request has been validated; and

instructions for transforming, by the data processing system, said transaction requests into a database command by generating said database command in response to validated transaction requests, wherein said database command is generated in response to a validated transaction request regardless of which one of said plurality of clients sent said validated transaction request.

6. The computer program product of claim 5, further comprising:

instructions for associating a second one of said plurality of validation criteria with a second one of said plurality of mandatory fields;

instructions for defining a third requirement for validating transaction requests from said first ones of said plurality of clients using said second one of said plurality of validation criteria, said third requirement not requiring data in said transaction requests from said first ones of said plurality of clients for said second one of said plurality of validation criteria; and

in response to receiving said first transaction request;

instructions for validating said first transaction request if said first transaction request includes said first data and regardless of whether said first transaction request includes second data for said second one of said plurality of validation criteria;

if said first transaction request does not include data for said second one of said plurality of validation criteria, determining second default data that has been specified for said first ones of said plurality of clients to use for said second one of said plurality of validation criteria; and

if said first transaction request has been validated, generating a database command that includes said first data in said one of said plurality of mandatory fields and said second default data in said second one of said plurality of mandatory fields.

7. The computer program product of claim 5, wherein the database command is a structured query language command, and wherein each one of the transaction requests is an extensible markup language document.

8. A data processing system for validating transaction requests from a plurality of clients, comprising:

a memory that contains a set of instructions and a singleton in-memory object; and

a processing unit, responsive to execution of the set of instructions, for;

providing an interface to validate transaction requests to access a database, using a plurality of validation criteria, from said plurality of clients having different requirements for said plurality of validation criteria, said interface in a singleton in-memory object;

using said different requirements to validate said transaction requests from said plurality of clients;

said interface including;

said database command including a plurality of mandatory fields;

associating a first one of said plurality of validation criteria with one of said plurality of mandatory fields, wherein data that is received for said first one of said plurality of validation criteria is included in said one of said plurality of mandatory fields;

defining a first requirement for validating transaction requests from first ones of said plurality of clients using said first one of said plurality of validation criteria, said first requirement requiring data to be included in said transaction requests from said first ones of said plurality of clients for said first one of said plurality of validation criteria;

defining a second requirement for validating transaction requests from second ones of said plurality of clients using said first one of said plurality of validation criteria, said second requirement not requiring data to be included in said transaction requests from said second ones of said plurality of clients for said first one of said plurality of validation criteria;

in response to receiving a first transaction request from one of said first ones of said plurality of clients;

validating said first transaction request responsive to said first transaction request including first data for said first one of said plurality of validation criteria; and

generating a database command that includes said first data in said one of said plurality of mandatory fields after said first transaction request has been validated;

in response to receiving a second transaction request from one of said second ones of said plurality of clients;

validating said second transaction request, determining default data that has been specified for said second ones of said plurality of clients to use for said first one of said plurality of validation criteria responsive to said second transaction request not including said second data, and generating a database command that includes said default data in said one of said plurality of mandatory fields after said second transaction request has been validated; and

said data processing system transforming said transaction requests into a database command by generating said database command in response to validated transaction requests, wherein said database command is generated in response to a validated transaction request regardless of which one of said plurality of clients sent said validated transaction request.

9. The data processing system according to claim 8, further comprising said processing unit, responsive to execution of the set of instructions, for:

associating a second one of said plurality of validation criteria with a second one of said plurality of mandatory fields;

defining a third requirement for validating transaction requests from said first ones of said plurality of clients using said second one of said plurality of validation criteria, said third requirement not requiring data in said transaction requests from said first ones of said plurality of clients for said second one of said plurality of validation criteria; and

in response to receiving said first transaction request;

validating said first transaction request if said first transaction request includes said first data and regardless of whether said first transaction request includes second data for said second one of said plurality of validation criteria;

if said first transaction request does not include data for said second one of said plurality of validation criteria, determining second default data that has been specified for said first ones of said plurality of clients to use for said second one of said plurality of validation criteria; and

if said first transaction request has been validated, generating a database command that includes said first data in said one of said plurality of mandatory fields and said second default data in said second one of said plurality of mandatory fields.

10. The data processing system according to claim 8, further comprising said processing unit, responsive to execution of the set of instructions, for:

in response to receiving said first transaction request from said one of said first ones of said plurality of clients;

generating an exception if said first transaction request does not include said first data, wherein said first transaction request is not validated.