CA2262322C - System and method for executing a request from a client application - Google Patents
System and method for executing a request from a client application Download PDFInfo
- Publication number
- CA2262322C CA2262322C CA002262322A CA2262322A CA2262322C CA 2262322 C CA2262322 C CA 2262322C CA 002262322 A CA002262322 A CA 002262322A CA 2262322 A CA2262322 A CA 2262322A CA 2262322 C CA2262322 C CA 2262322C
- Authority
- CA
- Canada
- Prior art keywords
- request
- client application
- data access
- server applications
- respective server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0281—Proxies
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/41—User authentication where a single sign-on provides access to a plurality of computers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q99/00—Subject matter not provided for in other groups of this subclass
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/306—User profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/563—Data redirection of data network streams
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2149—Restricted operating environment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/102—Entity profiles
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99933—Query processing, i.e. searching
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99939—Privileged access
Abstract
A system and method are provided for executing a request from a client application. Unlike conventional networks in which a client application transmits several data access transactions to several server applications, the client application of these preferred embodiments merely sends a single request to a gateway application, which converts the request into appropriate data access transactions. The preferred embodiments provide the advantage of allowing a client application to communicate with a plurality of server applications without knowing the server application's format or syntax requirements. Further, unlike environments in which a client application compiles data received from each contacted server application, in the environment of the preferred embodiments, the client application is presented with a single integrated response.
Description
System and Method for Executing a Request from a Client Application Technical Field The present invention relates generally to telecommunication services and more specifically to a new system and method for executing a request from a client application.
Background Client applications often are used to satisfy an information request requiring responses from a plurality of server applications. For example, a business frequently needs to know its daily sales from each of its divisions. To satisfy this information request, a client application contacts the server applications associated with each division to request sales activity. For each contacted server application, the client application negotiates access and executes a request for data (a "data access transaction"). Thus, to satisfy a single request, the client application transmits several data access transactions to several server applications.
To expedite the process of gathering information from several server applications, Electronic Data Interchange (EDI) standards were developed to provide standard message formats for common information or service requests between trading partners. To implement EDI standards in mature data processing environments, software components have been created to map an EDI message received from a client application to a format expected by an existing server application. Where additional data items used by an existing server application are not defined as standard fields in the EDI structure, the standard allows a "user data construct" to be populated with the non-standard data. Over time, the user data construct has become an increasingly important section of the EDI message. When a client application must communicate with many server applications, a data mapping process is usually required to format these non-standard items within the user data constructs used by each server application. One of the primary disadvantages associated with EDI standards is that once a server application changes the format of its user data construct in the EDI
message, the client application may be unable to communicate with the server application,until the data mapping process is updated. That is, networks using the EDI
Background Client applications often are used to satisfy an information request requiring responses from a plurality of server applications. For example, a business frequently needs to know its daily sales from each of its divisions. To satisfy this information request, a client application contacts the server applications associated with each division to request sales activity. For each contacted server application, the client application negotiates access and executes a request for data (a "data access transaction"). Thus, to satisfy a single request, the client application transmits several data access transactions to several server applications.
To expedite the process of gathering information from several server applications, Electronic Data Interchange (EDI) standards were developed to provide standard message formats for common information or service requests between trading partners. To implement EDI standards in mature data processing environments, software components have been created to map an EDI message received from a client application to a format expected by an existing server application. Where additional data items used by an existing server application are not defined as standard fields in the EDI structure, the standard allows a "user data construct" to be populated with the non-standard data. Over time, the user data construct has become an increasingly important section of the EDI message. When a client application must communicate with many server applications, a data mapping process is usually required to format these non-standard items within the user data constructs used by each server application. One of the primary disadvantages associated with EDI standards is that once a server application changes the format of its user data construct in the EDI
message, the client application may be unable to communicate with the server application,until the data mapping process is updated. That is, networks using the EDI
2 standard are release dependent. Because of the large and costly effort involved, changing the standard message format to incorporate the data items contained in the user data constructs or coordinating release dependent data processing changes between enterprises is not practical. There is, therefore, a need for an improved system and method for executing a request from a client application.
Brief Description of the Drawings Figure 1 is an illustration of a computer of a preferred embodiment.
Figure 2 is a block diagram of network of a preferred embodiment.
Figure 3 is a flow chart of a method of a preferred embodiment for executing a request from a client application.
Figure 4 is a block diagram of a network of another preferred embodiment.
Detailed Description of the Presently Preferred Embodiments In the embodiments described below, a system and method are presented for executing a request from a client application. Unlike conventional networks in which a client application transmits several data access transactions to several server applications, the client application of these preferred embodiments merely sends a single request to a gateway application (a "gateway"). The gateway, which can run on a computer 100 such as that shown in Figure 1, accepts a single request from a client application and converts the request into the appropriate data access transactions, which are transmitted to targeted server applications. These embodiments provide the advantage of allowing a client application to communicate with a plurality of server applications without knowing their format or syntax requirements. That is, unlike environments that use fixed-format EDI standards, the environments described below are release independent. Further, unlike conventional environments in which a client application compiles data received from each contacted server application, these preferred embodiments provide the additional advantage of presenting a client application with a single integrated response to a single information request.
Turning again to the drawings, Figure 2 is a block diagram of a network environment 200 of a preferred embodiment. As shown in Figure 2, a client application 210 is coupled with a gateway 220, which is coupled with a user profile database 270 and first, second, and third server applications 230, 240, 250 in a host environment 260. As used herein, the term "coupled with" means directly coupled with or indirectly coupled with through one or more components. The gateway comprises process control tables 223, a data access transaction identification routine 224, a data access transaction transmission routine 225, a response integration routine 226, and an integrated response presentation routine 227. While it is preferred that these routines be implemented with software and that the gateway 220 comprise the necessary hardware components (such as a CPU) to run the software, it is important to note that any appropriate hardware, analog or digital, and any appropriate software language can be used. Further, although these routines are shown as distinct elements in Figure 2, the routines can be combined. It also is important to note that the components shown in Figure 2 are presented merely for illustration and that more or fewer client and server applications than are shown can be used. Additionally, any of these routines can be located anywhere in the network 200.
With these components, the network 200 of Figure 2 can be used in a method for executing a request from a client application. As shown in the flow chart of Figure
Brief Description of the Drawings Figure 1 is an illustration of a computer of a preferred embodiment.
Figure 2 is a block diagram of network of a preferred embodiment.
Figure 3 is a flow chart of a method of a preferred embodiment for executing a request from a client application.
Figure 4 is a block diagram of a network of another preferred embodiment.
Detailed Description of the Presently Preferred Embodiments In the embodiments described below, a system and method are presented for executing a request from a client application. Unlike conventional networks in which a client application transmits several data access transactions to several server applications, the client application of these preferred embodiments merely sends a single request to a gateway application (a "gateway"). The gateway, which can run on a computer 100 such as that shown in Figure 1, accepts a single request from a client application and converts the request into the appropriate data access transactions, which are transmitted to targeted server applications. These embodiments provide the advantage of allowing a client application to communicate with a plurality of server applications without knowing their format or syntax requirements. That is, unlike environments that use fixed-format EDI standards, the environments described below are release independent. Further, unlike conventional environments in which a client application compiles data received from each contacted server application, these preferred embodiments provide the additional advantage of presenting a client application with a single integrated response to a single information request.
Turning again to the drawings, Figure 2 is a block diagram of a network environment 200 of a preferred embodiment. As shown in Figure 2, a client application 210 is coupled with a gateway 220, which is coupled with a user profile database 270 and first, second, and third server applications 230, 240, 250 in a host environment 260. As used herein, the term "coupled with" means directly coupled with or indirectly coupled with through one or more components. The gateway comprises process control tables 223, a data access transaction identification routine 224, a data access transaction transmission routine 225, a response integration routine 226, and an integrated response presentation routine 227. While it is preferred that these routines be implemented with software and that the gateway 220 comprise the necessary hardware components (such as a CPU) to run the software, it is important to note that any appropriate hardware, analog or digital, and any appropriate software language can be used. Further, although these routines are shown as distinct elements in Figure 2, the routines can be combined. It also is important to note that the components shown in Figure 2 are presented merely for illustration and that more or fewer client and server applications than are shown can be used. Additionally, any of these routines can be located anywhere in the network 200.
With these components, the network 200 of Figure 2 can be used in a method for executing a request from a client application. As shown in the flow chart of Figure
3, this method comprises the steps of receiving a request from a client application (step 310), automatically identifying a set of data access transactions corresponding to the request, each data access transaction being associated with a respective server application (step 320), transmitting the set of data access transactions to the respective server applications (step 330), receiving a set of responses from the respective server applications, at least some of the set of responses comprising a respective first optional attribute (step 340), and integrating the set of responses for presentation to the client application even when the first optional attribute is not recognized (step 350). The operation of this method will be illustrated below.
The first step in the method of Figure 3 is receiving a request from a client application (step 310). Instead of transmitting several data access transactions, the client application 210 merely transmits a single request. Unlike typical network environments, in this network 200; the transmission from the client application 210 is a request for information, not a technical implementation of the request (i.e., a data access transaction). It is preferred that a web browser be used to enable the client
The first step in the method of Figure 3 is receiving a request from a client application (step 310). Instead of transmitting several data access transactions, the client application 210 merely transmits a single request. Unlike typical network environments, in this network 200; the transmission from the client application 210 is a request for information, not a technical implementation of the request (i.e., a data access transaction). It is preferred that a web browser be used to enable the client
4 application 210 to transmit input parameters to the gateway 220 in the form of an HTTP request. After the request is received, a set of data access transactions, each associated with a respective server application, is automatically identified (step 320).
When a request from a client application 210 is received by the gateway 220, the data access transaction identification routine 224 identifies the technical implementation of the request by leveraging the process control tables 223. The tables 223 define the processing requirements of the client application's request and identify the data access transactions that must be executed to satisfy the request. Each data access transaction comprises two sections. The first section describes the message type, content, and format to define the data items present. The first section includes any navigation constraints, authority levels required for access, maximum size of input or output messages, presentation languages supported, and other general processing rules needed to communicate with a server application. The second section is the data itself (e.g., the input parameters). Any information items not specified as a required attribute of the request are optional items that may or may not be supported by a particular server application.
Next, the set of data access transactions are transmitted to the respective server applications (step 330). In contrast to networks using EDI interfaces which prevent client-server communication if a server application does not receive the exact data items it is expecting, the server applications of these preferred embodiments will process the set of data access transactions even in the presence of an additional optional attribute. That is, the interface syntax of these preferred embodiments dynamically defines the content of request-reply messages to allow processing of data access transactions even when a server application does not recognize an optional attribute. With this feature, new server applications can be added to the host environment 260 without coordinating their syntax and formatting requirements with the client application 210. In other words, the network 200 has release independence.
After the targeted server application processes the received data access transaction, the gateway 220 receives a set of responses from the respective server applications (step 340). The results returned from the server applications are parsed and placed in a common message structure. As with the data access transactions, at least some of the set of responses comprises an optional attribute. The response integration routine 226 integrates the set of responses for presentation to the client application 210 even when an optional attribute is not recognized (step 3 50).
The response integration routine 226 sorts and merges the received information using the rules defined for processing the request. Output can be conditionally modified or reformatted using a set of string manipulation and conditional fixnctions that are customizable and defined by the developer of the gateway 220. With the integrated responses, the integrated response presentation routine 227 accesses application presentation objects, which preferably dynamically builds an HTML, page for return to the client application 210.
The example described below will illustrate the principles developed above.
Figure 4 is a block diagram of a network 400 of a preferred embodiment that can be used to access government records for the State of Illinois. In this network 400, a client application 410 is coupled with a gateway 420, which is coupled with a server application for Cook County 430 and a server application for Du Page County 440. In 1 S this-example, the request is "Felony Criminal Record Search by Name." The required input data item is last name, and the optional input data items are first name, middle name, middle initial, social security number ("SSN"), date of birth ("DoB"), and sex.
The required output data items include last name, arrest date, and case number, and the optional output data items include first name, middle name, middle initial, SSN, DoB, and sex. Suppose that Cook County keeps a record of a person's SSN and Du Page County does not. When a data access transaction is sent to the Cook County and Du Page County server applications 430, 440, the Cook County server application will use all of the data supplied to qualify its search for arrest records while the Du Page County server application 440 ignores the S SN data item but still processes the data access transaction. When the response integration routine receives responses from the servers, it merges the results and indicates to the client application 410 that the SSN data item is not applicable for Du Page County's arrest records.
Now suppose that Kane County, another county in Illinois, is added to the network 400 and that the Kane County server application 460 records and stores eye color as an attribute of the arrested party. Kane County writes its transaction to include eye color as an optional search criteria and returns this attribute in its reply to a "Felony Record Search by Name" request. If the client application 410 is modified to allow input of eye color before the Kane County server application 460 is made available on the network 400, the results from Cook County and Du Page County will indicate that eye color is a "not applicable" data attribute. If the process control tables have not been updated to include eye color, when eye color data is received from the client application 410, the eye color data item and value will be ignored. If Cook County or Du Page County decides to modify its processing to allow the search to include eye color, it can do so at a later date without notification to either the gateway 420 or the client application 410. A similar procedure occurs when the gateway receives responses from the server applications. That is, the gateway 420 integrates the responses received from the server applications even when the responses contain unrecognizable data items (i.e., optional attributes).
In addition to the fiznctions described above, the gateway 220 can incorporate security fiznctionality. End users of the gateway 220 can be authorized to access one or more services through the use of user security profiles maintained in the user profile database 270. The database 270, which is preferably an Oracle 7 database, can be a part of or separate from the gateway 220. The method used to gain access to the gateway 220 depends on the client platform. For a dial-up gui application, Kerberos authentication services can be used. For a web-based client, SSL can be used to encrypt input user-id and password. It is important to note that any suitable authentication procedure can be used. Once authentication is complete, the user profile is used to create a menu of the services accessible by the client for that session.
Because the gateway 220 prevents direct connection between the client application 210 and the server applications 260, the gateway 220 acts as a firewall, adding an additional layer of security to the network 200. This firewall feature also simplifies the authentication and authorization process since security needs only be managed once (upon logging into the gateway 220), unlike conventional networks that require the client application to execute security procedures for each contacted server application.
In addition to containing authentication and authorization information, a user profile can contain information used in computing fees for the use of server applications. Fee schedules by user type or a subscription plan can be specified by each participating information provider. Because there are multiple information providers, the fees charged and revenue apportionment applicable to a server application may vary from one host to another. The gateway 220 maintains these relationships and tracks the hosts that are accessed for each request so that the appropriate fee can be charged and the correct distribution of revenue occurs.
A
complete record of the user's session can be maintained for auditing billing details.
The charges applied to a customer account can be based on the value of a transaction, subscription, or usage. Transaction- or usage-based charges can be dynamically computed and applied to accounts real-time, inputted on-line by authorized customer service representatives or agents, or batched and submitted via an import process using a standard external billings request file. Subscription charges are computed in a scheduled batch process based on the defined charge rules for the service and package configuration.
Charges are computed, and charged fees can be remitted to the appropriate information providers, distributors, and service providers using a flexible-service- or 1 S transaction- specific set of rules that provide, for example, fee schedules based on client type, charges based on subscription package, temporary sign-up promotions, association discounts, user discounts, and transaction charge schedules based on subscription package, minimum charge policy, and volume discounts.
Fees charged to end-users are apportioned to the entities involved in the , provision or sale of the service. Flexible fee apportionment schedules are defined for each transaction, allowing information providers to participate in discount programs that ensure that statutory fees are remitted in full to government institutions.
Electronic Funds Transfer can be used to transfer funds to recipients. Billing accounts can include pre-paid accounts, receivable accounts for which a bill is issued, or credit line accounts.
In the above-described embodiments, an end user initiated a request from the client application. In an alternative embodiment, the request is initiated by intelligent agent software, allowing peer-to-peer applications to use the gateway for inter-enterprise service requests. An intelligent agent is a set of objects that enable pre-defined standing requests or process initiated requests to be submitted to the gateway.
Agent objects provide standard services that enable an application to pose a request, interpret the results, and either initiate another request or create a report or document using the results. That is, the business fianctions defined for use by the intelligent agent can be designed to interpret the results to format a second request to the gateway.
When the response is posted to the results queue of the application, the content of the message will cause the application's results handler to transfer the message to the S request queue for continued processing.
To create the software that will enable a network to perform as described above, a development tool can be used that, unlike conventional development tools that use physical mapping of a legacy system data model to a virtual data model, is based on the concept of separation of function. Application components can be viewed as belonging to one of three layers - presentation, processing, or data management. This view enables development staff to define, design, and construct application components independently, leveraging existing expertise and simplifying the process of heterogeneous system integration. Graphical tools can be provided to document the results of each development phase and generate design specifications, source code, and configuration specifications for use by the development staff.
First, the "service" is defined to the gateway. A "service" is a set of applications provided by a service provider. For each service, a description that will serve as the textual display on the provider's menu and a set of rules are defined to the system. Service level rules determine the languages the presentation developers will need to support (e.g., whether fees will be charged for the service). For each service, one or more business applications will be defined. An "application" contains a set of business tasks (the result of a business task is a returned HTML page) and the sequence in which the business tasks may be executed. This sequence is important for most applications since the result of one request will generally provide the input parameters for the next. Once the high level definition is complete, data analysts in the participating organizations define the logical data management fiznctions required to support the business task. The definition includes a description of all input and output data items. Each input or output item is specified identifying, for example, whether the item is required for processing or optional, the maximum size of the item, the format of the item (e.g., date format = yyyymmdd), and the tag name by which this item will be identified. Processing constraints (i.e., sort requirements for output) and reportable error conditions and codes are also defined.
The definition of each data management fiznction is stored in the process control tables and is used as input to the specification generation fianction that creates a specification report that, at this point in the design, can be handed off to the data management development teams who will design the procedures that will execute in the host environments. Business tasks can then be defined by selecting the appropriate logical data management functions required to satisfy the request, mapping the business fiznction input items and output items to the corresponding item in the data management function definitions. As page design proceeds, data manipulation functions may be added to the task definition to aggregate data items for compression.
The number of rows of detail data to be returned with each request and other processing details can also be added. After design approval, the gateway construction tools can be used to generate the standard application interface objects that may be included in the application programs being developed for data management and presentation. The target host environments and remote transaction identifiers are specified for each data management function. The format name for the HTML
pages that will present the results of the business tasks are also specified. Once all of the required inputs have been provided, the development objects (e.g., source code for data management application interface, URLs for presentation links, configuration details for system administrators) can be generated. At this time, the system can also generate the updates to the processing control and application integration tables used by the gateway components.
It is preferred that the gateway be built upon an on-line transaction processing ("OLTP") foundation, which, in contrast to the store-and-forward mechanism used with EDI standards, provides real time interaction, guaranteed transaction delivery, and practically unlimited scalability. Differences in location and technology are configurable within the gateway platform so that the same logical request can be directed to one enterprise over an SNA network as a CICS transaction and to another as a remote procedure call to an Oracle database by routing the request through the appropriate data manager. Gateway services can be accessed by popular web browsers via standard HTTP requests using a CORBA compliant framework provided by, for example, Oracle's Web Server 3Ø Data access transactions can be executed using standard protocols or can use the protocols native to a server application.
Application interfaces are provided to access CICS regions using LU6 2 over SNA networks.
The appropriate published remote access API is used to access Oracle, Sybase, SQLServer or Informix stored procedures. Each routine preferably runs as a distinct UNIX
process enabling the use of popular monitoring tools to alert operations personnel if a routine unexpectedly becomes inoperative.
It is intended that the foregoing detailed description be understood as an illustration of selected forms that the invention can take and not as a definition of the invention. For example, the methods described above can be implemented in a computer usable medium having computer readable program code means embodied therein. It is only the following claims, including all equivalents, that are intended to define the scope of this invention.
When a request from a client application 210 is received by the gateway 220, the data access transaction identification routine 224 identifies the technical implementation of the request by leveraging the process control tables 223. The tables 223 define the processing requirements of the client application's request and identify the data access transactions that must be executed to satisfy the request. Each data access transaction comprises two sections. The first section describes the message type, content, and format to define the data items present. The first section includes any navigation constraints, authority levels required for access, maximum size of input or output messages, presentation languages supported, and other general processing rules needed to communicate with a server application. The second section is the data itself (e.g., the input parameters). Any information items not specified as a required attribute of the request are optional items that may or may not be supported by a particular server application.
Next, the set of data access transactions are transmitted to the respective server applications (step 330). In contrast to networks using EDI interfaces which prevent client-server communication if a server application does not receive the exact data items it is expecting, the server applications of these preferred embodiments will process the set of data access transactions even in the presence of an additional optional attribute. That is, the interface syntax of these preferred embodiments dynamically defines the content of request-reply messages to allow processing of data access transactions even when a server application does not recognize an optional attribute. With this feature, new server applications can be added to the host environment 260 without coordinating their syntax and formatting requirements with the client application 210. In other words, the network 200 has release independence.
After the targeted server application processes the received data access transaction, the gateway 220 receives a set of responses from the respective server applications (step 340). The results returned from the server applications are parsed and placed in a common message structure. As with the data access transactions, at least some of the set of responses comprises an optional attribute. The response integration routine 226 integrates the set of responses for presentation to the client application 210 even when an optional attribute is not recognized (step 3 50).
The response integration routine 226 sorts and merges the received information using the rules defined for processing the request. Output can be conditionally modified or reformatted using a set of string manipulation and conditional fixnctions that are customizable and defined by the developer of the gateway 220. With the integrated responses, the integrated response presentation routine 227 accesses application presentation objects, which preferably dynamically builds an HTML, page for return to the client application 210.
The example described below will illustrate the principles developed above.
Figure 4 is a block diagram of a network 400 of a preferred embodiment that can be used to access government records for the State of Illinois. In this network 400, a client application 410 is coupled with a gateway 420, which is coupled with a server application for Cook County 430 and a server application for Du Page County 440. In 1 S this-example, the request is "Felony Criminal Record Search by Name." The required input data item is last name, and the optional input data items are first name, middle name, middle initial, social security number ("SSN"), date of birth ("DoB"), and sex.
The required output data items include last name, arrest date, and case number, and the optional output data items include first name, middle name, middle initial, SSN, DoB, and sex. Suppose that Cook County keeps a record of a person's SSN and Du Page County does not. When a data access transaction is sent to the Cook County and Du Page County server applications 430, 440, the Cook County server application will use all of the data supplied to qualify its search for arrest records while the Du Page County server application 440 ignores the S SN data item but still processes the data access transaction. When the response integration routine receives responses from the servers, it merges the results and indicates to the client application 410 that the SSN data item is not applicable for Du Page County's arrest records.
Now suppose that Kane County, another county in Illinois, is added to the network 400 and that the Kane County server application 460 records and stores eye color as an attribute of the arrested party. Kane County writes its transaction to include eye color as an optional search criteria and returns this attribute in its reply to a "Felony Record Search by Name" request. If the client application 410 is modified to allow input of eye color before the Kane County server application 460 is made available on the network 400, the results from Cook County and Du Page County will indicate that eye color is a "not applicable" data attribute. If the process control tables have not been updated to include eye color, when eye color data is received from the client application 410, the eye color data item and value will be ignored. If Cook County or Du Page County decides to modify its processing to allow the search to include eye color, it can do so at a later date without notification to either the gateway 420 or the client application 410. A similar procedure occurs when the gateway receives responses from the server applications. That is, the gateway 420 integrates the responses received from the server applications even when the responses contain unrecognizable data items (i.e., optional attributes).
In addition to the fiznctions described above, the gateway 220 can incorporate security fiznctionality. End users of the gateway 220 can be authorized to access one or more services through the use of user security profiles maintained in the user profile database 270. The database 270, which is preferably an Oracle 7 database, can be a part of or separate from the gateway 220. The method used to gain access to the gateway 220 depends on the client platform. For a dial-up gui application, Kerberos authentication services can be used. For a web-based client, SSL can be used to encrypt input user-id and password. It is important to note that any suitable authentication procedure can be used. Once authentication is complete, the user profile is used to create a menu of the services accessible by the client for that session.
Because the gateway 220 prevents direct connection between the client application 210 and the server applications 260, the gateway 220 acts as a firewall, adding an additional layer of security to the network 200. This firewall feature also simplifies the authentication and authorization process since security needs only be managed once (upon logging into the gateway 220), unlike conventional networks that require the client application to execute security procedures for each contacted server application.
In addition to containing authentication and authorization information, a user profile can contain information used in computing fees for the use of server applications. Fee schedules by user type or a subscription plan can be specified by each participating information provider. Because there are multiple information providers, the fees charged and revenue apportionment applicable to a server application may vary from one host to another. The gateway 220 maintains these relationships and tracks the hosts that are accessed for each request so that the appropriate fee can be charged and the correct distribution of revenue occurs.
A
complete record of the user's session can be maintained for auditing billing details.
The charges applied to a customer account can be based on the value of a transaction, subscription, or usage. Transaction- or usage-based charges can be dynamically computed and applied to accounts real-time, inputted on-line by authorized customer service representatives or agents, or batched and submitted via an import process using a standard external billings request file. Subscription charges are computed in a scheduled batch process based on the defined charge rules for the service and package configuration.
Charges are computed, and charged fees can be remitted to the appropriate information providers, distributors, and service providers using a flexible-service- or 1 S transaction- specific set of rules that provide, for example, fee schedules based on client type, charges based on subscription package, temporary sign-up promotions, association discounts, user discounts, and transaction charge schedules based on subscription package, minimum charge policy, and volume discounts.
Fees charged to end-users are apportioned to the entities involved in the , provision or sale of the service. Flexible fee apportionment schedules are defined for each transaction, allowing information providers to participate in discount programs that ensure that statutory fees are remitted in full to government institutions.
Electronic Funds Transfer can be used to transfer funds to recipients. Billing accounts can include pre-paid accounts, receivable accounts for which a bill is issued, or credit line accounts.
In the above-described embodiments, an end user initiated a request from the client application. In an alternative embodiment, the request is initiated by intelligent agent software, allowing peer-to-peer applications to use the gateway for inter-enterprise service requests. An intelligent agent is a set of objects that enable pre-defined standing requests or process initiated requests to be submitted to the gateway.
Agent objects provide standard services that enable an application to pose a request, interpret the results, and either initiate another request or create a report or document using the results. That is, the business fianctions defined for use by the intelligent agent can be designed to interpret the results to format a second request to the gateway.
When the response is posted to the results queue of the application, the content of the message will cause the application's results handler to transfer the message to the S request queue for continued processing.
To create the software that will enable a network to perform as described above, a development tool can be used that, unlike conventional development tools that use physical mapping of a legacy system data model to a virtual data model, is based on the concept of separation of function. Application components can be viewed as belonging to one of three layers - presentation, processing, or data management. This view enables development staff to define, design, and construct application components independently, leveraging existing expertise and simplifying the process of heterogeneous system integration. Graphical tools can be provided to document the results of each development phase and generate design specifications, source code, and configuration specifications for use by the development staff.
First, the "service" is defined to the gateway. A "service" is a set of applications provided by a service provider. For each service, a description that will serve as the textual display on the provider's menu and a set of rules are defined to the system. Service level rules determine the languages the presentation developers will need to support (e.g., whether fees will be charged for the service). For each service, one or more business applications will be defined. An "application" contains a set of business tasks (the result of a business task is a returned HTML page) and the sequence in which the business tasks may be executed. This sequence is important for most applications since the result of one request will generally provide the input parameters for the next. Once the high level definition is complete, data analysts in the participating organizations define the logical data management fiznctions required to support the business task. The definition includes a description of all input and output data items. Each input or output item is specified identifying, for example, whether the item is required for processing or optional, the maximum size of the item, the format of the item (e.g., date format = yyyymmdd), and the tag name by which this item will be identified. Processing constraints (i.e., sort requirements for output) and reportable error conditions and codes are also defined.
The definition of each data management fiznction is stored in the process control tables and is used as input to the specification generation fianction that creates a specification report that, at this point in the design, can be handed off to the data management development teams who will design the procedures that will execute in the host environments. Business tasks can then be defined by selecting the appropriate logical data management functions required to satisfy the request, mapping the business fiznction input items and output items to the corresponding item in the data management function definitions. As page design proceeds, data manipulation functions may be added to the task definition to aggregate data items for compression.
The number of rows of detail data to be returned with each request and other processing details can also be added. After design approval, the gateway construction tools can be used to generate the standard application interface objects that may be included in the application programs being developed for data management and presentation. The target host environments and remote transaction identifiers are specified for each data management function. The format name for the HTML
pages that will present the results of the business tasks are also specified. Once all of the required inputs have been provided, the development objects (e.g., source code for data management application interface, URLs for presentation links, configuration details for system administrators) can be generated. At this time, the system can also generate the updates to the processing control and application integration tables used by the gateway components.
It is preferred that the gateway be built upon an on-line transaction processing ("OLTP") foundation, which, in contrast to the store-and-forward mechanism used with EDI standards, provides real time interaction, guaranteed transaction delivery, and practically unlimited scalability. Differences in location and technology are configurable within the gateway platform so that the same logical request can be directed to one enterprise over an SNA network as a CICS transaction and to another as a remote procedure call to an Oracle database by routing the request through the appropriate data manager. Gateway services can be accessed by popular web browsers via standard HTTP requests using a CORBA compliant framework provided by, for example, Oracle's Web Server 3Ø Data access transactions can be executed using standard protocols or can use the protocols native to a server application.
Application interfaces are provided to access CICS regions using LU6 2 over SNA networks.
The appropriate published remote access API is used to access Oracle, Sybase, SQLServer or Informix stored procedures. Each routine preferably runs as a distinct UNIX
process enabling the use of popular monitoring tools to alert operations personnel if a routine unexpectedly becomes inoperative.
It is intended that the foregoing detailed description be understood as an illustration of selected forms that the invention can take and not as a definition of the invention. For example, the methods described above can be implemented in a computer usable medium having computer readable program code means embodied therein. It is only the following claims, including all equivalents, that are intended to define the scope of this invention.
Claims (12)
PRIVILEGE IS CLAIMED ARE DEFINED AS FOLLOWS:
1. A method for executing a request from a client application, said method comprising the steps of:
(a) receiving a request from a client application;
(b) automatically identifying a set of data access transactions corresponding to said request, each data access transaction being associated with a respective server application;
(c) transmitting said set of data access transactions to said respective server applications;
(d) receiving a set of responses from said respective server applications, at least some of said set of responses comprising a respective first optional data item; and (e) integrating said set of responses for presentation to said client application, said step of integrating being performed even when said first optional data item is not recognized;
wherein at least some of the set of data access transactions in step (b) comprise a second optional data item, and wherein the method further comprises the step of using said respective server applications to process said set of data access transactions even when said second optional data item is not recognized by said respective server applications.
(a) receiving a request from a client application;
(b) automatically identifying a set of data access transactions corresponding to said request, each data access transaction being associated with a respective server application;
(c) transmitting said set of data access transactions to said respective server applications;
(d) receiving a set of responses from said respective server applications, at least some of said set of responses comprising a respective first optional data item; and (e) integrating said set of responses for presentation to said client application, said step of integrating being performed even when said first optional data item is not recognized;
wherein at least some of the set of data access transactions in step (b) comprise a second optional data item, and wherein the method further comprises the step of using said respective server applications to process said set of data access transactions even when said second optional data item is not recognized by said respective server applications.
2. The method of claim 1, further comprising the step of using a client application to transmit said request in response to user initiation.
3. The method of claim 1, further comprising the step of using a client application to transmit said request in response to intelligent agent software initiation.
4. The method of claim 1, wherein step (a) is performed by a web browser.
5. The method of claim 1, further comprising the steps of:
(f) receiving user identification information from said client application;
and (g) accessing a user profile database to verify said received user identification information.
(f) receiving user identification information from said client application;
and (g) accessing a user profile database to verify said received user identification information.
6. The method of claim 1, further comprising the steps of:
(f) accessing a user profile database to compute a fee for using said respective server applications.
(f) accessing a user profile database to compute a fee for using said respective server applications.
7. A computer usable medium having computer readable program code means embodied therein for executing a request from a client; application, the computer readable program code means comprising:
first computer readable program code means for receiving a request from a client application;
second computer readable program code means for automatically identifying a set of data access transactions corresponding to said request, each data access transaction being associated with a respective server application;
third computer readable program code means for' transmitting said set of data access transactions to said respective server applications;
fourth computer readable program code means for receiving a set of responses from said respective server applications, at least some of said set of responses comprising a respective first optional data item; and fifth computer readable program code means for iintegrating said set of responses for presentation to said client application, said step of integrating being performed even when said first optional data item is not recognized;
wherein said set of data access transactions comprises a second optional data item, and wherein the medium further comprises sixth computer readable program code means for processing said set of data access transactions even when said second optional data item is not recognized by said respective server applications.
first computer readable program code means for receiving a request from a client application;
second computer readable program code means for automatically identifying a set of data access transactions corresponding to said request, each data access transaction being associated with a respective server application;
third computer readable program code means for' transmitting said set of data access transactions to said respective server applications;
fourth computer readable program code means for receiving a set of responses from said respective server applications, at least some of said set of responses comprising a respective first optional data item; and fifth computer readable program code means for iintegrating said set of responses for presentation to said client application, said step of integrating being performed even when said first optional data item is not recognized;
wherein said set of data access transactions comprises a second optional data item, and wherein the medium further comprises sixth computer readable program code means for processing said set of data access transactions even when said second optional data item is not recognized by said respective server applications.
8. A system for facilitating communication between a client application and a plurality of server applications, said system comprising:
first means for receiving a request from a client application;
second means for automatically identifying a set of data access transactions corresponding to said request, each data access transaction being associated with a respective server application;
third means for transmitting said set of data access transactions to said respective server applications;
fourth means for receiving a set of responses from said respective server applications, at least some of said set of responses comprising a respective first optional data item; and fifth means for integrating said set of responses for presentation to said client application, said step of integrating being performed even when said first optional data item is not recognized;
wherein said set of data access transactions comprises a second optional data item, and wherein the system further comprises sixth imeans, located in said respective server applications, for processing said set of data access transactions even when said second optional data item is not recognized by said respective server applications.
first means for receiving a request from a client application;
second means for automatically identifying a set of data access transactions corresponding to said request, each data access transaction being associated with a respective server application;
third means for transmitting said set of data access transactions to said respective server applications;
fourth means for receiving a set of responses from said respective server applications, at least some of said set of responses comprising a respective first optional data item; and fifth means for integrating said set of responses for presentation to said client application, said step of integrating being performed even when said first optional data item is not recognized;
wherein said set of data access transactions comprises a second optional data item, and wherein the system further comprises sixth imeans, located in said respective server applications, for processing said set of data access transactions even when said second optional data item is not recognized by said respective server applications.
9. The system of claim 8, wherein said request transaction is initiated by a user.
10. The system of claim 8, wherein said request transaction is initiated by intelligent agent software.
11. The system of claim 8, further comprising:
a user profile database coupled with said client application and comprising user identification information; and sixth means for accessing said user profile database to verify received user identification information.
a user profile database coupled with said client application and comprising user identification information; and sixth means for accessing said user profile database to verify received user identification information.
12. The system of claim 8, further comprising:
a user profile database coupled with said client application and comprising fee information; and sixth means for accessing said user profile database to compute a fee for using said respective server applications.
a user profile database coupled with said client application and comprising fee information; and sixth means for accessing said user profile database to compute a fee for using said respective server applications.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/026,201 US6205482B1 (en) | 1998-02-19 | 1998-02-19 | System and method for executing a request from a client application |
US09/026,201 | 1998-02-19 |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2262322A1 CA2262322A1 (en) | 1999-08-19 |
CA2262322C true CA2262322C (en) | 2003-10-14 |
Family
ID=21830443
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002262322A Expired - Lifetime CA2262322C (en) | 1998-02-19 | 1999-02-18 | System and method for executing a request from a client application |
Country Status (4)
Country | Link |
---|---|
US (4) | US6205482B1 (en) |
AU (1) | AU3299299A (en) |
CA (1) | CA2262322C (en) |
WO (1) | WO1999042926A1 (en) |
Families Citing this family (98)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6560634B1 (en) * | 1997-08-15 | 2003-05-06 | Verisign, Inc. | Method of determining unavailability of an internet domain name |
US6205482B1 (en) * | 1998-02-19 | 2001-03-20 | Ameritech Corporation | System and method for executing a request from a client application |
BRPI9910049B1 (en) * | 1998-04-28 | 2016-11-16 | Nokia Corp | method and network for controlling wireless session protocol (wsp) sessions |
GB9815364D0 (en) * | 1998-07-16 | 1998-09-16 | Koninkl Philips Electronics Nv | Data network interfacing |
US7127493B1 (en) * | 1998-08-20 | 2006-10-24 | Gautier Taylor S | Optimizing server delivery of content by selective inclusion of optional data based on optimization criteria |
US6314468B1 (en) * | 1998-09-03 | 2001-11-06 | Mci Worldcom, Inc. | System and method for managing transmission of electronic data between trading partners |
US6715080B1 (en) * | 1998-10-01 | 2004-03-30 | Unisys Corporation | Making CGI variables and cookie information available to an OLTP system |
US6473807B1 (en) * | 1998-12-03 | 2002-10-29 | Merrill Lynch & Co., Inc. | System for invocation of CICS programs as database stored procedures |
CA2363796A1 (en) * | 1999-02-26 | 2000-08-31 | Richard T. Box | A system, method and article of manufacture for an electronic commerce interface to the government |
US6408303B1 (en) * | 1999-07-06 | 2002-06-18 | Healthcare Transaction Processors, Inc. | System and method for automated building of a trading partner profile |
US6760844B1 (en) * | 1999-07-30 | 2004-07-06 | Unisys Corporation | Secure transactions sessions |
GB2354913B (en) * | 1999-09-28 | 2003-10-08 | Ibm | Publish/subscribe data processing with publication points for customised message processing |
US6609148B1 (en) * | 1999-11-10 | 2003-08-19 | Randy Salo | Clients remote access to enterprise networks employing enterprise gateway servers in a centralized data center converting plurality of data requests for messaging and collaboration into a single request |
US6782425B1 (en) * | 1999-11-24 | 2004-08-24 | Unisys Corporation | Session based security profile for internet access of an enterprise server |
AU2001249833A1 (en) * | 2000-04-03 | 2001-10-15 | Wireless Knowledge | Application gateway system |
US6859910B2 (en) * | 2000-04-10 | 2005-02-22 | Bluestreak.Com | Methods and systems for transactional tunneling |
US7206843B1 (en) | 2000-04-21 | 2007-04-17 | Sun Microsystems, Inc. | Thread-safe portable management interface |
US7478403B1 (en) | 2000-04-21 | 2009-01-13 | Sun Microsystems, Inc. | Secure access to managed network objects using a configurable platform-independent gateway providing individual object-level access control |
US7010586B1 (en) | 2000-04-21 | 2006-03-07 | Sun Microsystems, Inc. | System and method for event subscriptions for CORBA gateway |
US6839748B1 (en) | 2000-04-21 | 2005-01-04 | Sun Microsystems, Inc. | Synchronous task scheduler for corba gateway |
US6915324B1 (en) | 2000-04-21 | 2005-07-05 | Sun Microsystems, Inc. | Generic and dynamic mapping of abstract syntax notation (ASN1) to and from interface definition language for network management |
US6813770B1 (en) | 2000-04-21 | 2004-11-02 | Sun Microsystems, Inc. | Abstract syntax notation to interface definition language converter framework for network management |
US7228346B1 (en) * | 2000-04-21 | 2007-06-05 | Sun Microsystems, Inc. | IDL event and request formatting for corba gateway |
US7783720B1 (en) | 2000-04-21 | 2010-08-24 | Oracle America, Inc. | CORBA metadata gateway to telecommunications management network |
US6950935B1 (en) | 2000-04-21 | 2005-09-27 | Sun Microsystems, Inc. | Pluggable authentication modules for telecommunications management network |
US20060036756A1 (en) * | 2000-04-28 | 2006-02-16 | Thomas Driemeyer | Scalable, multi-user server and method for rendering images from interactively customizable scene information |
US7000028B1 (en) * | 2000-06-02 | 2006-02-14 | Verisign, Inc. | Automated domain name registration |
JP2002032216A (en) * | 2000-07-19 | 2002-01-31 | Fujitsu Ltd | Hosting device for application |
US20030125992A1 (en) * | 2001-12-26 | 2003-07-03 | The Crawford Group, Inc. | Web browser based computer network for processing vehicle rental transactions on a large scale |
US7899690B1 (en) | 2000-08-18 | 2011-03-01 | The Crawford Group, Inc. | Extended web enabled business to business computer system for rental vehicle services |
US8600783B2 (en) * | 2000-08-18 | 2013-12-03 | The Crawford Group, Inc. | Business to business computer system for communicating and processing rental car reservations using web services |
US7275038B1 (en) * | 2000-08-18 | 2007-09-25 | The Crawford Group, Inc. | Web enabled business to business operating system for rental car services |
AU2001286786A1 (en) * | 2000-08-25 | 2002-03-13 | Stuart E. Massey | Transaction-based enterprise application integration (eai) and development system |
US6775671B1 (en) * | 2000-12-13 | 2004-08-10 | William Marsh Rice University | Component-based adaptation system and method |
US6826591B2 (en) * | 2000-12-15 | 2004-11-30 | International Business Machines Corporation | Flexible result data structure and multi-node logging for a multi-node application system |
US7111077B1 (en) * | 2000-12-22 | 2006-09-19 | Unisys Corporation | Method and apparatus for passing service requests and data from web based workstations directly to online transaction processing (OLTP) server systems |
EP1348169A1 (en) * | 2001-01-02 | 2003-10-01 | Delta Air Lines Inc. | Exchanging electronic messages between a host computer system and a distributed computer system |
US7216180B1 (en) * | 2001-01-16 | 2007-05-08 | Microsoft Corporation | System and method for modifying an information transfer request |
US7142690B2 (en) * | 2001-02-20 | 2006-11-28 | Ricoh Company, Ltd. | System, computer program product and method for managing documents |
US7246158B2 (en) * | 2001-04-23 | 2007-07-17 | Ricoh Company, Ltd. | System, computer program product and method for selecting an application service provider |
US20030036917A1 (en) * | 2001-04-25 | 2003-02-20 | Metallect Corporation | Service provision system and method |
US8019807B2 (en) * | 2001-05-23 | 2011-09-13 | Wireless Enterprise Solutions Technology Limited | Method and system for communication between computer systems |
US20030061062A1 (en) * | 2001-09-26 | 2003-03-27 | Tucker Timothy J. | XML data switch |
US7203948B2 (en) * | 2001-09-29 | 2007-04-10 | Siebel Systems, Inc. | Method, apparatus, and system for implementing caching of view custom options in a framework to support web-based applications |
US7461119B2 (en) * | 2001-09-29 | 2008-12-02 | Siebel Systems, Inc. | Method, apparatus, and system for managing status of requests in a client server environment |
US6907451B1 (en) | 2001-09-29 | 2005-06-14 | Siebel Systems, Inc. | Method, apparatus, and system for immediate posting of changes in a client server environment |
US7885996B2 (en) * | 2001-09-29 | 2011-02-08 | Siebel Systems, Inc. | Method, apparatus, and system for implementing notifications in a framework to support web-based applications |
US8359335B2 (en) * | 2001-09-29 | 2013-01-22 | Siebel Systems, Inc. | Computing system and method to implicitly commit unsaved data for a world wide web application |
US7146617B2 (en) | 2001-09-29 | 2006-12-05 | Siebel Systems, Inc. | Method, apparatus, and system for implementing view caching in a framework to support web-based applications |
US7870492B2 (en) * | 2001-10-02 | 2011-01-11 | Siebel Systems, Inc. | Method, apparatus, and system for managing commands in a client server environment |
US7418484B2 (en) * | 2001-11-30 | 2008-08-26 | Oracle International Corporation | System and method for actively managing an enterprise of configurable components |
US20030126109A1 (en) * | 2002-01-02 | 2003-07-03 | Tanya Couch | Method and system for converting message data into relational table format |
US7526519B2 (en) | 2002-05-01 | 2009-04-28 | Bea Systems, Inc. | High availability application view deployment |
US7222148B2 (en) | 2002-05-02 | 2007-05-22 | Bea Systems, Inc. | System and method for providing highly available processing of asynchronous service requests |
US7228175B2 (en) | 2002-05-15 | 2007-06-05 | Cardiac Pacemakers, Inc. | Cardiac rhythm management systems and methods using acoustic contractility indicator |
US8108231B2 (en) | 2002-06-14 | 2012-01-31 | The Crawford Group, Inc. | Method and apparatus for improved customer direct on-line reservation of rental vehicles |
JP2004021562A (en) * | 2002-06-14 | 2004-01-22 | Fujitsu Ltd | Client character code conversion program and server character code conversion program |
US20040039612A1 (en) | 2002-06-14 | 2004-02-26 | Neil Fitzgerald | Method and apparatus for customer direct on-line reservation of rental vehicles |
US20040003287A1 (en) * | 2002-06-28 | 2004-01-01 | Zissimopoulos Vasileios Bill | Method for authenticating kerberos users from common web browsers |
JP4598354B2 (en) * | 2002-09-30 | 2010-12-15 | 株式会社エヌ・ティ・ティ・ドコモ | COMMUNICATION SYSTEM, RELAY DEVICE, AND COMMUNICATION CONTROL METHOD |
US8832178B2 (en) | 2002-11-06 | 2014-09-09 | Noel William Lovisa | Service implementation |
US7440940B2 (en) * | 2002-12-02 | 2008-10-21 | Sap Ag | Web service agent |
US7769881B2 (en) * | 2003-01-24 | 2010-08-03 | Hitachi, Ltd. | Method and apparatus for peer-to peer access |
US8700413B2 (en) * | 2003-03-03 | 2014-04-15 | International Business Machines Corporation | Web services registration for dynamic composition of web services |
US7644275B2 (en) | 2003-04-15 | 2010-01-05 | Microsoft Corporation | Pass-thru for client authentication |
US20040215790A1 (en) * | 2003-04-24 | 2004-10-28 | Miller Robert A. | Information network access |
US7523200B2 (en) * | 2003-07-02 | 2009-04-21 | International Business Machines Corporation | Dynamic access decision information module |
EP1649352A4 (en) * | 2003-07-11 | 2008-05-14 | Computer Ass Think Inc | Trigger support for a bi-directional broker |
EP1665711B8 (en) * | 2003-09-17 | 2016-12-14 | Google Technology Holdings LLC | System and method for asynchronous wireless services using reverse service schema generation |
US20050080759A1 (en) * | 2003-10-08 | 2005-04-14 | International Business Machines Corporation | Transparent interface to a messaging system from a database engine |
US7958496B2 (en) * | 2003-12-22 | 2011-06-07 | Telefonaktiebolaget L M Ericsson (Publ) | Method of and system for application service exchange across different execution environments |
ES2409160T3 (en) | 2004-03-23 | 2013-06-25 | Boston Scientific Limited | Live View System |
US7922654B2 (en) | 2004-08-09 | 2011-04-12 | Boston Scientific Scimed, Inc. | Fiber optic imaging catheter |
US11832793B2 (en) | 2004-03-23 | 2023-12-05 | Boston Scientific Scimed, Inc. | Vivo visualization system |
US8813216B2 (en) * | 2004-12-16 | 2014-08-19 | International Business Machines Corporation | Network security protection |
WO2006081232A2 (en) * | 2005-01-25 | 2006-08-03 | The Glidden Company | Methods for a coating composition considering environmental conditions |
US20060212422A1 (en) * | 2005-03-21 | 2006-09-21 | Anil Khilani | Efficiently executing commands against a large set of servers with near real time feedback of execution and presentation of the output of the commands |
EP1872510A4 (en) * | 2005-04-18 | 2008-06-18 | Research In Motion Ltd | System topology for secure end-to-end communications between wireless device and application data source |
US8272058B2 (en) | 2005-07-29 | 2012-09-18 | Bit 9, Inc. | Centralized timed analysis in a network security system |
US7895651B2 (en) | 2005-07-29 | 2011-02-22 | Bit 9, Inc. | Content tracking in a network security system |
US8984636B2 (en) | 2005-07-29 | 2015-03-17 | Bit9, Inc. | Content extractor and analysis system |
US7434041B2 (en) * | 2005-08-22 | 2008-10-07 | Oracle International Corporation | Infrastructure for verifying configuration and health of a multi-node computer system |
US8032657B2 (en) * | 2005-09-12 | 2011-10-04 | Microsoft Corporation | Preservation of type information between a client and a server |
US8615578B2 (en) * | 2005-10-07 | 2013-12-24 | Oracle International Corporation | Using a standby data storage system to detect the health of a cluster of data storage servers |
US20070100794A1 (en) * | 2005-10-27 | 2007-05-03 | Aaron Joseph D | Method and apparatus for providing extensible document access to assistive technology providers |
US8271309B2 (en) | 2006-03-16 | 2012-09-18 | The Crawford Group, Inc. | Method and system for providing and administering online rental vehicle reservation booking services |
US8443424B2 (en) * | 2007-02-08 | 2013-05-14 | Scipioo Holding B.V. | Method and system for reducing the proliferation of electronic messages |
US9558097B2 (en) | 2007-11-13 | 2017-01-31 | Red Hat, Inc. | Automated recording and playback of application interactions |
US8849944B2 (en) * | 2007-11-27 | 2014-09-30 | Red Hat, Inc. | Multi-use application proxy |
US20090158403A1 (en) * | 2007-12-14 | 2009-06-18 | Dirk Leonard Benschop | Method and system for permitting or denying service |
US8239921B2 (en) | 2008-01-03 | 2012-08-07 | Dlb Finance & Consultancy B.V. | System and method of retrieving a service contact identifier |
US8463921B2 (en) * | 2008-01-17 | 2013-06-11 | Scipioo Holding B.V. | Method and system for controlling a computer application program |
US9195525B2 (en) * | 2008-10-21 | 2015-11-24 | Synactive, Inc. | Method and apparatus for generating a web-based user interface |
US8682998B2 (en) * | 2008-10-31 | 2014-03-25 | Software Ag | Method and server cluster for map reducing flow services and large documents |
US8620627B2 (en) * | 2009-10-13 | 2013-12-31 | The Boeing Company | Composite information display for a part |
US8993084B2 (en) | 2010-08-17 | 2015-03-31 | The Boeing Company | Multi-layer metallic structure and composite-to-metal joint methods |
US9338248B2 (en) * | 2011-12-15 | 2016-05-10 | Sap Se | Parameter driven value conversion framework in client/server architectures |
US20190102543A1 (en) * | 2017-09-29 | 2019-04-04 | AVAST Software s.r.o. | Observation and classification of device events |
Family Cites Families (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5051947A (en) * | 1985-12-10 | 1991-09-24 | Trw Inc. | High-speed single-pass textual search processor for locating exact and inexact matches of a search pattern in a textual stream |
US5187787B1 (en) | 1989-07-27 | 1996-05-07 | Teknekron Software Systems Inc | Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes |
CA2039365C (en) * | 1991-03-28 | 2000-01-18 | T. Dora Velissaropoulos | Method and means for encoding storing and retrieving hierarchical data processing information for a computer system |
US5329619A (en) | 1992-10-30 | 1994-07-12 | Software Ag | Cooperative processing interface and communication broker for heterogeneous computing environments |
GB9224224D0 (en) | 1992-11-19 | 1993-01-06 | Int Computers Ltd | Data processing system |
US5596744A (en) | 1993-05-20 | 1997-01-21 | Hughes Aircraft Company | Apparatus and method for providing users with transparent integrated access to heterogeneous database management systems |
JP3365576B2 (en) | 1993-06-14 | 2003-01-14 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Object execution method and apparatus |
GB9314460D0 (en) | 1993-07-13 | 1993-08-25 | Int Computers Ltd | Computer systems integration |
JPH0771455A (en) | 1993-08-31 | 1995-03-17 | Nippon Thompson Co Ltd | Direct-acting rolling guide unit |
WO1995027248A1 (en) | 1994-03-30 | 1995-10-12 | Apple Computer, Inc. | Object oriented message passing system and method |
US5586312A (en) | 1994-10-11 | 1996-12-17 | Unisys Corporation | Method and apparatus for using an independent transaction processing application as a service routine |
CA2204736A1 (en) * | 1994-11-08 | 1996-05-23 | Charles H. Ferguson | An online service development tool with fee setting capabilities |
US5634127A (en) * | 1994-11-30 | 1997-05-27 | International Business Machines Corporation | Methods and apparatus for implementing a message driven processor in a client-server environment |
US5513148A (en) | 1994-12-01 | 1996-04-30 | Micron Technology Inc. | Synchronous NAND DRAM architecture |
US6078925A (en) * | 1995-05-01 | 2000-06-20 | International Business Machines Corporation | Computer program product for database relational extenders |
US5710918A (en) * | 1995-06-07 | 1998-01-20 | International Business Machines Corporation | Method for distributed task fulfillment of web browser requests |
US5686312A (en) | 1996-01-29 | 1997-11-11 | Ferro Corporation | Method of determining emissions from powder coatings |
US5727159A (en) | 1996-04-10 | 1998-03-10 | Kikinis; Dan | System in which a Proxy-Server translates information received from the Internet into a form/format readily usable by low power portable computers |
US5794232A (en) * | 1996-03-15 | 1998-08-11 | Novell, Inc. | Catalog services for distributed directories |
US5802518A (en) * | 1996-06-04 | 1998-09-01 | Multex Systems, Inc. | Information delivery system and method |
US5878143A (en) | 1996-08-16 | 1999-03-02 | Net 1, Inc. | Secure transmission of sensitive information over a public/insecure communications medium |
US5873080A (en) * | 1996-09-20 | 1999-02-16 | International Business Machines Corporation | Using multiple search engines to search multimedia data |
US5890161A (en) | 1997-10-28 | 1999-03-30 | Microsoft Corporation | Automatic transaction processing of component-based server applications |
US6205482B1 (en) | 1998-02-19 | 2001-03-20 | Ameritech Corporation | System and method for executing a request from a client application |
US6732101B1 (en) * | 2000-06-15 | 2004-05-04 | Zix Corporation | Secure message forwarding system detecting user's preferences including security preferences |
-
1998
- 1998-02-19 US US09/026,201 patent/US6205482B1/en not_active Expired - Lifetime
-
1999
- 1999-02-17 AU AU32992/99A patent/AU3299299A/en not_active Abandoned
- 1999-02-17 WO PCT/US1999/003480 patent/WO1999042926A1/en active Application Filing
- 1999-02-18 CA CA002262322A patent/CA2262322C/en not_active Expired - Lifetime
-
2000
- 2000-11-20 US US09/717,326 patent/US6442611B1/en not_active Expired - Lifetime
-
2002
- 2002-08-07 US US10/214,418 patent/US6718389B2/en not_active Expired - Lifetime
-
2004
- 2004-01-27 US US10/767,411 patent/US20040249814A1/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
CA2262322A1 (en) | 1999-08-19 |
US6205482B1 (en) | 2001-03-20 |
US6442611B1 (en) | 2002-08-27 |
WO1999042926A1 (en) | 1999-08-26 |
AU3299299A (en) | 1999-09-06 |
US6718389B2 (en) | 2004-04-06 |
US20040249814A1 (en) | 2004-12-09 |
US20030041124A1 (en) | 2003-02-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2262322C (en) | System and method for executing a request from a client application | |
US8984535B2 (en) | System and method for facilitating the exchange of information among applications | |
US6615258B1 (en) | Integrated customer interface for web based data management | |
US7761306B2 (en) | icFoundation web site development software and icFoundation biztalk server 2000 integration | |
Harrison et al. | Mobile Agents: Are they a good idea? | |
US6604104B1 (en) | System and process for managing data within an operational data store | |
US20030208467A1 (en) | System for distributed task execution | |
US20050198111A1 (en) | Distributed transaction event matching | |
AU2002322282A1 (en) | Integrating enterprise support systems | |
Bishop et al. | A survey of middleware | |
US20040230982A1 (en) | Assembly of business process using intellectual capital processing | |
US20050010574A1 (en) | System and method for providing service level management | |
US7415438B1 (en) | System and method for obtaining feedback from delivery of informational and transactional data | |
WO2002041189A2 (en) | Database integrity in an internet e-commerce environment | |
CN116932214A (en) | Instruction sending method and device, electronic equipment and computer storage medium | |
US20040230618A1 (en) | Business intelligence using intellectual capital | |
KR100645529B1 (en) | Log management system capable of log processing and method using the same | |
US20040230588A1 (en) | Methods and systems for publishing and subscribing to intellectual capital | |
US20040230465A1 (en) | Intellectual capital sharing | |
Grotehen et al. | Implementing Business Objects: CORBA interfaces for legacy systems | |
MXPA00002979A (en) | Integrated customer interface for web-based data management | |
AKOR | MEDIATION INTERFACE REQUIREMENT SPECIFICATION ON GSM NETWORKS AND OTHER PRIVATE TELEPHONE OPERATORS (PTOs) |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
MKEX | Expiry |
Effective date: 20190218 |