|Publication number||US7089317 B2|
|Application number||US 10/106,680|
|Publication date||Aug 8, 2006|
|Filing date||Mar 25, 2002|
|Priority date||Mar 21, 2002|
|Also published as||EP1347381A2, EP1347381A3, US20030236923|
|Publication number||10106680, 106680, US 7089317 B2, US 7089317B2, US-B2-7089317, US7089317 B2, US7089317B2|
|Inventors||Thulasiraman Jeyaraman, Mark William Hapner, William A. Shannon, Kenneth David Saks, Kathleen A. Stout, Rahul Sharma, Qingqing Ouyang|
|Original Assignee||Sun Microsystems, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (17), Referenced by (56), Classifications (15), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application takes priority under 35 U.S.C. §119(e) of U.S. Provisional Patent Application No. 60/367,138 filed Mar. 21, 2002, entitled “J2EE CONNECTOR ARCHITECTURE” naming Thulasiraman Jeyaraman as inventor, which is also incorporated herein by reference for all purposes. This application is also related to the following co-pending U.S. patent applications, which are filed concurrently with this application and each of which are herein incorporated by reference, (i) U.S. patent application Ser. No. 10/106,293, entitled “CALLBACK EVENT LISTENER MECHANISM FOR RESOURCE ADAPTER WORK EXECUTIONS PERFORMED BY AN APPLICATION SERVER THREAD” naming Jeyaraman as inventor, (ii) U.S. patent application Ser. No. 10/106,671, entitled “MECHANISM TO MANAGE THE LIFECYCLE OF A RESOURCE ADAPTER” naming Jeyaraman as inventor, each of which are incorporated by reference in their entirety.
1. Field of Invention
The invention relates generally to computer systems. More particularly, methods and apparatus for providing a generic contract between an application server and a message provider which allows the message provider to deliver messages to message endpoints (MDBs) residing in the application server independent of the specific messaging style, messaging semantics and messaging infrastructure used to deliver messages. Such a contract also serves as the standard message provider pluggability contract that allows any message provider to be plugged into any application server via a resource adapter.
2. Description of Relevant Art
In modern Enterprise Information Systems (EIS) is formed to include a number of EIS resources. An EIS resource provides EIS-specific functionality to its clients examples of which include a record or set of records in a database system, a business object in an ERP system, and a transaction program in a transaction processing system. Generally, an EIS is formed of a number of interconnected personal computers, workstations, mainframes, and the like along with other devices such as large mass storage subsystems, network interfaces, as well as interfaces to the public telephony systems are interconnected providing an integrated environment in which information may be shared among the various users. Typically, users may be performing a variety of operations, including order receipt, manufacturing, shipping, billing, inventory control, and other operations in which sharing of data on a real time basis provides a significant advantage over, for example, maintaining separate records and attempting to reconcile them later.
The Java 2 Platform, Enterprise Edition (J2EE) provides containers for client applications, web components (based on servlets, Java Server Pages) and Enterprise JavaBeans components. These containers provide deployment and runtime support for application components as well as an integrated view of the services provided by underlying application server for the associated application components. Containers can run on existing systems such as, for example, web servers (for the web containers) application servers, TP monitors, and database systems for EJB containers enabling EISs to leverage both the advantages of their existing systems and those of J2EE. For example, EISs can write (or rewrite) new applications using J2EE capabilities and can also encapsulate parts of existing applications in Enterprise Java Beans (EJB), Message Driven Beans (MDB), Java Server Pages (JSP) or Servlets. IN addition, EIS applications access functions and data associated with applications running on Enterprise Information Systems (EIS).
The J2EE Connector architecture defines standard contracts which allows bi-directional connectivity between enterprise applications and EISs. An architecture for integration of J2EE servers with EISs is referred to as a connector architecture. There are two parts to the connector architecture: an EIS vendor-provided resource adapter and an application server that allows this resource adapter to plug in. The contracts support bi-directional communication between the application server and the resource adapter. (It is well to note that a resource adapter is a system-level software driver that is used by a Java application to connect to an EIS. The resource adapter plugs into an application server and provides connectivity between the EIS, the application server, and the enterprise application. The J2EE Connector architecture defines a standard architecture for connecting the Java 2 Platform, Enterprise Edition (J2EE) platform to heterogeneous EISs.)
Accordingly, the connector architecture defines a set of scalable, secure, and transactional mechanisms (i.e., a set of contracts) such as transactions, security, connection management, that a resource adapter has to support to plug in to an application server that enable the integration of EISs with application servers and enterprise applications. The connector architecture also defines a Common Client Interface (CCI) for EIS access. The CCI defines a client API for interacting with heterogeneous EISs. The connector architecture enables an EIS vendor to provide a standard resource adapter for its EIS. In this way, an application server vendor extends its system once to support the connector architecture and is then assured of a seamless connectivity to multiple EISs. Likewise, an EIS vendor provides one standard resource adapter and it has the capability to plug in to any application server that supports the connector architecture.
Asynchronous message delivery or event notification is a widely used application communication paradigm. Some of the characteristics of asynchronous message-based communication paradigm include a message producer is not directly aware of message consumers (there could be one or more consumers interested in the message). Message delivery is solicited, that is, a message consumer has to express interest in receiving messages. Message producer is not directly aware of message consumers and consequently it produces messages of a constant type Messaging infrastructure stores and routes messages reliably (depending on QoS) to interested messsage consumers. Inherently, the interaction is loosely coupled. The message producer and the consumer do not share any execution context. The message producer generally is not interested in the outcome of message processing by consumers. The message delivery always involves a message routing infrastructure, which offers varying QoS for storing (persistence) and routing messages reliably.
J2EE applications could use two different approaches to interact with a message provider. One approach relies upon the direct use specific messaging APIs to send and synchronously receive messages. Alternatively, any message provider could provide a connector resource adapter which supplies connection objects for use by applications to send and synchronously receive messages using the specific messaging API without requiring any additional contracts (it could use MDBs to asynchronously receive messages via a message provider).
While the above approaches allow a J2EE application to send and receive messages, there is no standard system-level contract to plug-in message providers to an application server, and to deliver messages to message endpoints (MDBs) residing in the application server. Without a standard pluggability contract, an application server (of which there may be m) would have to use special contracts to interact with various message providers (of which there may be n), and a message provider has to do the same to interact with different application servers representing an mxn type problem.
Therefore, there is a need for a standard, generic contract between an application server and a message provider which allows the message provider to deliver messages to message endpoints (MDBs) residing in the application server independent of the specific messaging style, messaging semantics and messaging infrastructure used to deliver messages. Such a contract also serves as the standard message provider pluggability contract which allows any message provider to be plugged into any application server via a resource adapter.
Broadly speaking, the invention relates to an improved method, apparatus and computer system for providing a generic contract between an application server and a message provider which allows the message provider to deliver messages to message endpoints (MDBs) residing in the application server independent of the specific messaging style, messaging semantics and messaging infrastructure used to deliver messages. Such a contract also serves as the standard message provider pluggability contract which allows any message provider to be plugged into any application server via a resource adapter.
In one embodiment a method for providing a generic contract between an application server and a message provider is described. An appropriate resource adapter is selected and activation configuration information from a messaging application is then obtained. Messaging application activation information is then obtained and an activation instance based, in part, upon the selected resource adapter is instantiated. The messaging application in the application server is deployed and a message endpoint factory instance is instantiated in the application server. An messaging endpoint associated with the messaging application is activated thereby allowing the message provider to deliver messages to the message endpoint residing in the application server that is independent of a specific messaging protocol.
In another embodiment of the invention, an apparatus for providing a generic contract between an application server and a message provider is described. The apparatus includes means for selecting an appropriate resource adapter means for obtaining activation configuration information from a messaging application and means for obtaining messaging application activation information, means for instantiating an activation instance based, in part, upon the selected resource adapter, means for deploying the messaging application in the application server, means for instantiating a message endpoint factory instance in the application server ,and means for activating an messaging endpoint associated with the messaging application thereby allowing the message provider to deliver messages to the message endpoint residing in the application server that is independent of a specific messaging protocol.
In yet another embodiment of the invention, a computer program product for providing a generic contract between an application server and a message provider is disclosed. The computer program product includes computer code for selecting an appropriate resource adapter, computer code for obtaining activation configuration information from a messaging application, computer code for obtaining messaging application activation information, computer code for instantiating an activation instance based, in part, upon the selected resource adapter, computer code for deploying the messaging application in the application server, computer code for instantiating a message endpoint factory instance in the application server, and computer code for activating an messaging endpoint associated with the messaging application thereby allowing the message provider to deliver messages to the message endpoint residing in the application server that is independent of a specific messaging protocol.
The invention, together with further advantages thereof, may best be understood by reference to the following description taken in conjunction with the accompanying drawings in which:
The present invention will now be described in detail with reference to a few preferred embodiments thereof as illustrated in the accompanying drawings. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art, that the present invention may be practiced without some or all of these specific details. In other instances, well known process steps and/or structures have not been described in detail in order to not unnecessarily obscure the present invention.
In accordance with one embodiment of the present invention, there is provided a method, apparatus, and system for providing a standard, generic contract between an application server and a message provider which allows the message provider to deliver messages to message endpoints (each of which is associated with a corresponding message application) residing in the application server. By generic, it is meant that the contract is independent of the specific messaging style, messaging semantics and messaging infrastructure used to deliver messages. In this way, the contract also serves as the standard message provider pluggability contract that allows any message provider to be plugged into any application server via an associated resource adapter.
Accordingly, a deployer (typically an individual desiring to set up a link between a selected message provider and a particular message application) selects a particular resource adapter from a library of resource adapters (typically provided by the message vendor) based upon particular requirements of the messaging application. Once selected, the deployer, by way of a deployment tool, requests activation information from the messaging application and message specific information (QoS, for example) from the selected resource adapter. The activation information includes a set of configurable properties (specific to the messaging style and the message provider) and is used to instantiate a configuration instance by the deployer for the activation of the messaging application and which is passed on by the resource adapter In this way, the resource adapter is expected to know the endpoint message listener type (using the information from the activation spec) and deliver messages to the endpoint. In some cases, the resource adapter might optionally pass a transactional type instance while creating a message endpoint in order to receive transactional notifications when a message delivery is transacted. The resource adapter supports methods used for application activations and deactivations. The resource adapter supplies a message endpoint factory instance and a configured activation specification instance during endpoint activations and deactivations. In some cases, the resource adapter could reject an activation by throwing an exception, for example, which may be due to any number of reasons, such as incorrect activation information or the application server has not completed endpoint activation, or the application server might decide to limit concurrent message deliveries, or the application server might have encountered an internal error condition. In some cases where the offending condition is temporary, the application server may decide to block the creation of the messaging endpoint instance instead of calling an exception.
In order to receive messages provided (or pushed) by the message provider, the resource adapter instantiates a message endpoint factory, based in part, upon the activation specification. The message endpoint factory provides the link between the message provider and the messaging application. In this way, the message provider is only required to maintain a single contract in order to communicate with any number of application servers thereby reducing the connectivity requirements for the message providers
Although, the invention will initially be described in terms of a messaging system as part of a J2EE based enterprise computer system, the present invention can be used in any networked computer system that uses JMS as its messaging infrastructure.
In the described embodiment, the messaging application deployer 102, or more simply referred to as the deployer 102 is an intelligent entity (such as, for example a human) that has the responsibility to deploy the message endpoint (application) 100 on an application server. The deployer 102 is expected to know the needs of the messaging application 100 (such as for example, message listener type, Quality of Service (QoS) etc.) and be aware of the details of the runtime environment (i.e., the application server) in which the messaging application 100 would be deployed. In some cases, the deployer 102 may also interact with a message provider to do the necessary setup for message delivery.
Accordingly, the deploy tool 104 is provided either by a message application vendor or a third party since it is the deploy tool 104 that assists the deployer 102 in deploying the messaging application 100 on the application server. In general, the deploy tool provides a list of resource adapters capable of delivering messages to the message messaging application (using, for example, the desired Message Listener type information to identify possible candidates). The deploy tool also provides the activation configuration information provided by the messaging application developer (obtained from the messaging application deployment descriptor) and also provides, in a J2EE environment, an Activation Spec Java Bean instance (obtained from the chosen resource adapter), and helps to configure the JavaBean instance using a property sheet editor, etc. The deploy tool also provides JavaBean instances (obtained from the chosen resource adapter) of administered objects (upon request from messaging application deployer) and helps in configuring them. It passes on the configured JavaBean instances to the application server (it may also serialize the JavaBean instances depending on the address space in which the deploy tool runs). When necessary, the deploy tools also assists in undeploying the message messaging application.
More specifically, referring to
Once an appropriate resource adapter 108 has been selected by the deployer 102 (by way of the deployment tool 104) the deployer 102 obtains an activation configuration information set 110 that is typically provided by a third party, such as a messaging application developer. It should be noted that the deployer 102 may be required to set up the message provider 101 with information required to receive any incoming messages provided by the messaging application 100 (which may be accomplished by specific tool, or tools, provided by the message provider). In addition to the activation configuration information set 110 from the messaging application 100, the deployer 102 (again using the deployment tool 104) creates an activation spec JavaBean 112 from the selected resource adapter 108 using information in the form of a deployment descriptor 114 based upon, for example, message provider specific details.
At this point, as shown in
Once message endpoints are activated, they are ready to receive messages from a message provider. Message delivery setup could either be durable or non-durable. In the case of non-durable message deliveries, messages are lost during application server downtime. When the application server becomes functional again, it automatically reactivates all message endpoints that were previously deployed, and messages delivery starts again. But the messages that were produced during the downtime are lost. This is because messages are not retained by the message provider and redelivered when the message endpoints are reactivated. However, in the case of durable activations, messages are not lost during application server downtime. When the application server becomes functional again, it automatically reactivates all message endpoints that were previously deployed, and messages delivery starts again. The messages that were produced during the downtime are retained by the message provider and redelivered when the message endpoints are reactivated. It is the responsibility of the message provider to persist undelivered messages and redeliver them when the endpoint is available (that is, when the endpoint is reactivated by the app server). Durability of message delivery is an attribute of the activation setup, and thus it must be captured as part of the endpoint activation information. No additional contracts are required to support durable activations. Activation durability can be specified by a endpoint deployer via the Activation Spec JavaBean.
In this way, the message provider is only required to maintain a single contract in order to communicate with any number of application servers thereby reducing the connectivity requirements for the message providers.
In the described embodiment, the message endpoint factory is used to get an endpoint instance via create endpoint call. Each such call results in a new endpoint instance which could be used to deliver messages concurrently; that is, for each active message endpoint, there could be multiple endpoint instances consuming messages concurrently. There is no limit to the number of such endpoint instances that could be created, although the application server may limit the concurrency by either throwing an unavailable exception or by blocking the create endpoint call. Thus, for each message endpoint, depending on traffic, the resource adapter may choose to deliver messages serially using a single endpoint instance or concurrently using multiple endpoint instances. The resource adapter uses the message endpoint factory to create message endpoint instances to deliver messages either serially or concurrently. There is no limit to the number of such endpoints that could be created to deliver messages. It is up to the application server to decide whether to allow message delivery before activation is completed. If the application server chooses to prevent message delivery before an endpoint is activated, it could block the creation of an endpoint until the activation is completed or throw an exception.
If desired, the resource adapter could pass a transactional instance while creating a message endpoint in order to receive transactional notifications when a message delivery is transacted. The application must notify the resource adapter via the transactional instance if a message delivery is transacted.
CPUs 402 are also coupled to one or more input/output devices 410 that may include, but are not limited to, devices such as video monitors, track balls, mice, keyboards, microphones, touch-sensitive displays, transducer card readers, magnetic or paper tape readers, tablets, styluses, voice or handwriting recognizers, or other well-known input devices such as, of course, other computers. Finally, CPUs 402 optionally may be coupled to a computer or telecommunications network, e.g., an Internet network, or an intranet network, using a network connection as shown generally at 412. With such a network connection, it is contemplated that the CPUs 402 might receive information from the network, or might output information to the network in the course of performing the above-described method steps. Such information, which is often represented as a sequence of instructions to be executed using CPUs 402, may be received from and outputted to the network, for example, in the form of a computer data signal embodied in a carrier wave. The above-described devices and materials will be familiar to those of skill in the computer hardware and software arts.
It should be noted that the present invention employs various computer-implemented operations involving data stored in computer systems. These operations include, but are not limited to, those requiring physical manipulation of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. The operations described herein that form part of the invention are useful machine operations. The manipulations performed are often referred to in terms, such as, producing, identifying, running, determining, comparing, executing, downloading, or detecting. It is sometimes convenient, principally for reasons of common usage, to refer to these electrical or magnetic signals as bits, values, elements, variables, characters, data, or the like. It should remembered however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities.
The present invention also relates to a device, system or apparatus for performing the aforementioned operations. The system may be specially constructed for the required purposes, or it may be a general-purpose computer selectively activated or configured by a computer program stored in the computer. The processes presented above are not inherently related to any particular computer or other computing apparatus. In particular, various general-purpose computers may be used with programs written in accordance with the teachings herein, or, alternatively, it may be more convenient to construct a more specialized computer system to perform the required operations.
Although only a few embodiments of the present invention have been described, it should be understood that the present invention may be embodied in many other specific forms without departing from the spirit or the scope of the present invention.
Although the methods of providing reliable B1B communications in accordance with the present invention are particularly suitable for implementation with respect to a Java™ based environment; the methods may generally be applied in any suitable object-based environment. In particular, the methods are suitable for use in platform-independent object-based environments. It should be appreciated that the methods may also be implemented in some distributed object-oriented systems.
It should also be appreciated that the present invention may generally be implemented on any suitable object-oriented computer system. Therefore, the present examples are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5787245||Nov 13, 1995||Jul 28, 1998||Object Technology Licensing Corporation||Portable debugging service utilizing a client debugger object and a server debugger object|
|US5835770 *||Feb 25, 1994||Nov 10, 1998||International Business Machines Corporation||User inquiry facility for task status in a distributed system|
|US6003050 *||Feb 10, 1998||Dec 14, 1999||Microsoft Corporation||Method for integrating a virtual machine with input method editors|
|US6038590 *||Jul 1, 1996||Mar 14, 2000||Sun Microsystems, Inc.||Object-oriented system, method and article of manufacture for a client-server state machine in an interprise computing framework system|
|US6708163 *||Nov 1, 2002||Mar 16, 2004||Hillol Kargupta||Collective data mining from distributed, vertically partitioned feature space|
|US6721777||May 24, 2000||Apr 13, 2004||Sun Microsystems, Inc.||Modular and portable deployment of a resource adapter in an application server|
|US6757899 *||Oct 11, 2001||Jun 29, 2004||Harris Corporation||Dynamic CORBA gateway for CORBA and non-CORBA clients and services|
|US6816882 *||May 31, 2000||Nov 9, 2004||International Business Machines Corporation||System and method for automatically negotiating license agreements and installing arbitrary user-specified applications on application service providers|
|US6826716 *||Sep 26, 2001||Nov 30, 2004||International Business Machines Corporation||Test programs for enterprise web applications|
|US20020147961||Feb 28, 2002||Oct 10, 2002||Charters Graham Castree||Method, apparatus and computer program product for integrating heterogeneous systems|
|US20030093402||Oct 15, 2002||May 15, 2003||Mitch Upton||System and method using a connector architecture for application integration|
|US20030093470||Oct 15, 2002||May 15, 2003||Mitch Upton||System and method for implementing a service adapter|
|US20030097574||Oct 15, 2002||May 22, 2003||Mitch Upton||Systems and methods for integration adapter security|
|US20030105884||Oct 15, 2002||Jun 5, 2003||Mitch Upton||System and method for using Web services with an enterprise system|
|US20030182452||Oct 15, 2002||Sep 25, 2003||Mitch Upton||System and method for implementing a schema object model in application integration|
|US20030182459||Mar 25, 2002||Sep 25, 2003||Sun Microsystems, Inc.||Mechanism to manage the lifecycle of a resource adapter|
|US20040015974||Mar 25, 2002||Jan 22, 2004||Sun Microsystems, Inc.||Callback event listener mechanism for resource adapter work executions performed by an application server thread|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7487513||Dec 30, 2003||Feb 3, 2009||Sap Ag||Web service archive|
|US7496891 *||Dec 22, 2004||Feb 24, 2009||International Business Machines Corporation||Real-time dynamic modification of service-oriented systems using annotations to specify real-time system constraints|
|US7509429 *||May 28, 2004||Mar 24, 2009||Sap Ag||Message endpoint activation|
|US7594237||Jun 1, 2004||Sep 22, 2009||Sap Ag||Program object to support connection generation|
|US7657658 *||Jun 7, 2004||Feb 2, 2010||Sap Ag||Resource adapter deployment|
|US7676810||Jun 3, 2004||Mar 9, 2010||Sap Ag||Identification of execution context|
|US7702791||Oct 31, 2001||Apr 20, 2010||Bea Systems, Inc.||Hardware load-balancing apparatus for session replication|
|US7703077 *||Apr 30, 2002||Apr 20, 2010||Microsoft Corporation||Programming model to detect deadlocks in concurrent programs|
|US7797669||Feb 13, 2004||Sep 14, 2010||Microsoft Corporation||Analysis of distributed software systems via specification substitution|
|US7908589 *||Aug 29, 2006||Mar 15, 2011||Sap Ag||Deployment|
|US7912800||Aug 29, 2006||Mar 22, 2011||Sap Ag||Deduction engine to determine what configuration management scoping questions to ask a user based on responses to one or more previous questions|
|US7921169||Aug 4, 2008||Apr 5, 2011||Oracle International Corporation||System and method for exactly once message store communication|
|US8065661||Aug 29, 2006||Nov 22, 2011||Sap Ag||Test engine|
|US8131644||Aug 29, 2006||Mar 6, 2012||Sap Ag||Formular update|
|US8135659||Oct 1, 2008||Mar 13, 2012||Sap Ag||System configuration comparison to identify process variation|
|US8135794 *||Mar 31, 2010||Mar 13, 2012||Microsoft Corporation||Availability and scalability in a messaging system in a manner transparent to the application|
|US8176014||Apr 6, 2007||May 8, 2012||Oracle International Corporation||System and method for providing a cache that stores entity beans and employs data invalidation|
|US8185869 *||Nov 3, 2008||May 22, 2012||International Business Machines Corporation||System and apparatus for real-time dynamic modification of service-oriented systems using annotations to specify real-time system constraints|
|US8255429||Dec 17, 2008||Aug 28, 2012||Sap Ag||Configuration change without disruption of incomplete processes|
|US8321498||Mar 1, 2005||Nov 27, 2012||Oracle International Corporation||Policy interface description framework|
|US8321594 *||Dec 6, 2007||Nov 27, 2012||Oracle International Corporation||Achieving low latencies on network events in a non-real time platform|
|US8370506||Mar 9, 2012||Feb 5, 2013||Oracle International Corporation||Session initiation protocol-based internet protocol television|
|US8396893||Dec 11, 2008||Mar 12, 2013||Sap Ag||Unified configuration of multiple applications|
|US8401022||Feb 3, 2009||Mar 19, 2013||Oracle International Corporation||Pragmatic approaches to IMS|
|US8458703||Jun 24, 2009||Jun 4, 2013||Oracle International Corporation||Application requesting management function based on metadata for managing enabler or dependency|
|US8505067||Aug 20, 2009||Aug 6, 2013||Oracle International Corporation||Service level network quality of service policy enforcement|
|US8533773||Nov 17, 2010||Sep 10, 2013||Oracle International Corporation||Methods and systems for implementing service level consolidated user information management|
|US8583830||Nov 17, 2010||Nov 12, 2013||Oracle International Corporation||Inter-working with a walled garden floor-controlled system|
|US8584087||Dec 11, 2009||Nov 12, 2013||Sap Ag||Application configuration deployment monitor|
|US8589338||Jan 24, 2008||Nov 19, 2013||Oracle International Corporation||Service-oriented architecture (SOA) management of data repository|
|US8675852||Jan 15, 2008||Mar 18, 2014||Oracle International Corporation||Using location as a presence attribute|
|US8744055||Jan 4, 2008||Jun 3, 2014||Oracle International Corporation||Abstract application dispatcher|
|US8862686 *||Aug 28, 2003||Oct 14, 2014||International Business Machines Corporation||System and method for providing shared web modules|
|US8879547||Jun 1, 2010||Nov 4, 2014||Oracle International Corporation||Telephony application services|
|US8914493||Mar 10, 2008||Dec 16, 2014||Oracle International Corporation||Presence-based event driven architecture|
|US8966498||Jan 24, 2008||Feb 24, 2015||Oracle International Corporation||Integrating operational and business support systems with a service delivery platform|
|US8990286 *||Apr 12, 2012||Mar 24, 2015||Oracle International Corporation||Integration of web services with a clustered actor based model|
|US9021456||Dec 24, 2008||Apr 28, 2015||International Business Machines Corporation||Using collaborative annotations to specify real-time process flows and system constraints|
|US9038082||Feb 17, 2011||May 19, 2015||Oracle International Corporation||Resource abstraction via enabler and metadata|
|US9170978 *||Aug 16, 2013||Oct 27, 2015||Verizon Patent And Licensing Inc.||Data center activation and configuration|
|US20030182426 *||Sep 30, 2002||Sep 25, 2003||Sun Microsystems, Inc.||Apparatus and method of lazy connection transaction enlistment|
|US20030204641 *||Apr 30, 2002||Oct 30, 2003||Microsoft Corporation||Programming model for concurrent programs|
|US20050050155 *||Aug 28, 2003||Mar 3, 2005||International Business Machines Corporation||System and method for providing shared web modules|
|US20050273783 *||Jun 3, 2004||Dec 8, 2005||Tankov Nikolai D||Identification of execution context|
|US20050278452 *||May 28, 2004||Dec 15, 2005||Tankov Nikolai D||Message endpoint activation|
|US20050289212 *||Jun 1, 2004||Dec 29, 2005||Tankov Nikolal D||Non-transactional resource reference|
|US20060031388 *||Jun 3, 2004||Feb 9, 2006||Tankov Nikolai D||Connection resource system|
|US20060080435 *||Jun 7, 2004||Apr 13, 2006||Tankov Nikolai D||Resource adapter deployment|
|US20060136896 *||Dec 22, 2004||Jun 22, 2006||International Business Machines Corporation||Real-time dynamic modification of service-oriented systems using annotations to specify real-time system constraints|
|US20080235327 *||Dec 6, 2007||Sep 25, 2008||Oracle International Corporation||Achieving low latencies on network events in a non-real time platform|
|US20090125898 *||Nov 3, 2008||May 14, 2009||International Business Machines Corporation||System and Apparatus for Real-Time Dynamic Modification of Service-Oriented Systems Using Annotations to Specify Real-Time System Constraints|
|US20090328051 *||Jun 24, 2009||Dec 31, 2009||Oracle International Corporation||Resource abstraction via enabler and metadata|
|US20100162222 *||Dec 24, 2008||Jun 24, 2010||International Business Machines Corporation||Using Collaborative Annotations to Specify Real-Time Process Flows and System Constraints|
|US20100192025 *||Mar 31, 2010||Jul 29, 2010||Microsoft Corporation||Availability and scalability in a messaging system in a manner transparent to the application|
|US20130275489 *||Apr 12, 2012||Oct 17, 2013||Oracle International Corporation||Integration of web services with a clustered actor based model|
|US20150052228 *||Aug 16, 2013||Feb 19, 2015||Verizon Patent And Licensing Inc.||Data center activation and configuration|
|U.S. Classification||709/230, 719/315, 709/203|
|International Classification||G06F9/46, G06F15/16, G06F3/00, G06F9/445|
|Cooperative Classification||H04L67/141, H04L67/34, H04L67/14, G06F9/546|
|European Classification||G06F9/54M, H04L29/08N33, H04L29/08N13, H04L29/08N13A|
|Jul 29, 2002||AS||Assignment|
Owner name: SUN MICROSYSTEMS INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JEYARMAN, THULASIRAMAN;HAPNER, MARK WILLIAM;SHANNON, WILLIAM A.;AND OTHERS;REEL/FRAME:013124/0955;SIGNING DATES FROM 20020625 TO 20020628
|Feb 20, 2007||CC||Certificate of correction|
|Jan 6, 2010||FPAY||Fee payment|
Year of fee payment: 4
|Jan 8, 2014||FPAY||Fee payment|
Year of fee payment: 8