Abstract: A method, system and computer program for addressing a web service defined by a service definition document, such as a Web Services Definition Language (WSDL) document. The method includes, for example, generating a messaging destination for a service element, and each associated port element, of the WSDL document, and providing an invocation mechanism associated with each port destination for invoking the web service. A destination is an addressable location in the messaging configuration, such as a message queue.

Abstract: The present invention provides a web service gateway which enables a web client to access a target service which does not provide a transport mechanism with which the client can communicate. The gateway imports a target service document describing the target service interface, end point addresses and supported transport mechanisms, and then modifies it by adding end point addresses and transport mechanisms supported by the gateway. A client may then access the target service by obtaining the modified document and sending a request to a gateway provided end point address using the associated transport mechanism. The gateway then forwards the request to the target service by converting the request and forwarding it to an end point address and transport mechanism specified in the target service document.

Abstract: Methods, systems, and products are disclosed in which port type agnostic proxy support for web services intermediaries is typically provided by receiving in a web services intermediary a request for execution of a web services operation, wherein the request includes parametric information from which an endpoint for a target service that supports the operation can be identified; identifying, in dependence upon the parametric data, the endpoint for a target service that supports the operation; creating a target service request for execution of the operation on the target service; and issuing the target service request to the target service. Exemplary embodiments typically also include the return path of request-response processing: receiving in the intermediary a response from the target service; creating in the intermediary, in dependence upon the response from the target service, a response from the intermediary; and returning the response from the intermediary to the requesting client.

Abstract: Methods, systems, and products are disclosed in which port type agnostic proxy support for web services intermediaries is typically provided by receiving in a web services intermediary a request for execution of a web services operation, wherein the request includes parametric information from which an endpoint for a target service that supports the operation can be identified; identifying, in dependence upon the parametric data, the endpoint for a target service that supports the operation; creating a target service request for execution of the operation on the target service; and issuing the target service request to the target service. Exemplary embodiments typically also include the return path of request-response processing; receiving in the intermediary a response from the target service; creating in the intermediary, in dependence upon the response from the target service, a response from the intermediary; and returning the response from the intermediary to the requesting client.

Abstract: Methods, systems, and products are disclosed in which port type agnostic proxy support for web services intermediaries is provided generally by receiving in a web services intermediary a request for execution of a web services operation, wherein the request includes parametric information from which an endpoint for a target service that supports the operation can be identified; identifying, in dependence upon the parametric data, the endpoint for a target service that supports the operation; determining whether the request requires a synchronous response; creating a target service request for execution of the operation on the target service; issuing the target service request to the target service; and waiting for a response from the target service if the request requires a synchronous response.

Abstract: When a request is received from a client device for the invocation of a web services operation, an off-ramp device coupled to an on-ramp device that provides an interface to web services verifies that the requested service is in a configuration file and then determines the selection scope of a desired service. Based on the selection scope of the desired service, the off-ramp device can determine whether to perform discovery and selection of a service implementation (“request” selection scope), retrieve a service implementation from a session level cache (“session” selection scope), or retrieve a service implementation from an application level cache (“application” selection scope). If a service implementation corresponding to the requested service does not exist in the session or application level cache, the discovery and selection operations may be performed to identify a service implementation to handle the request and the service implementation may be stored in an appropriate cache.

Abstract: A message broker data processing apparatus comprising: a unit for receiving published messages on a topic from a plurality of publisher applications; a unit for processing the received messages; and a unit for distributing the processed messages to a subscriber application; wherein the unit for receiving includes a plurality of publication point data processing nodes, each of which receives published messages on the topic from a publisher application.

Abstract: A foldable container is formed from a single blank of sheet material which has stacking shoulders, reinforced corners side panels and display panels. The container includes a bottom section delimited by pairs of upright end panels and side panels. The bottom section is slightly wider adjacent its center than adjacent the front and back. Two of the side panels are foldably connected to peripheral segments of the bottom section, pre-glued and cooperate with the latter to form an open top product-accommodating compartment. The top edges of each of the side panels include shoulders for supporting a container stacked thereon and positioning tabs that extend upwardly and fit into corresponding openings in the bottom of the upper container. The lateral edge of each end panel and adjacent side panel has foldably connected thereto a corner-reinforcing member and create shopping accessibility from the front of the container.

Abstract: An apparatus and method for selecting a web service in response to a request from a client device are provided. With the apparatus and method of the present invention, when an a request is received from a client device for the invocation of a web services operation, the request is received in an off-ramp device coupled to an on-ramp device that provides an interface to web services. The off-ramp device verifies that the requested service is in a configuration file and then determines the selection scope of the desired service, as defined in the configuration file. Based on the selection scope of the desired service, the off-ramp can determine whether to perform discovery and selection of a service implementation (“request” seleciton scope), retrieve a service implementation from a session level cache (“session” selection scope), or retrieve a service implementation from an application level cache (“application” selection scope).

Abstract: The present invention provides a web service gateway which enables a web client to access a target service which does not provide a transport mechanism with which the client can communicate. The gateway imports a target service document describing the target service interface, end point addresses and supported transport mechanisms, and then modifies it by adding end point addresses and transport mechanisms supported by the gateway. A client may then access the target service by obtaining the modified document and sending a request to a gateway provided end point address using the associated transport mechanism. The gateway then forwards the request to the target service by converting the request and forwarding it to an end point address and transport mechanism specified in the target service document.

Abstract: The present invention provides a mechanism for the dynamic discovery and selection of web service implementations at runtime without explicit client control. With the mechanism of the present invention, service requests are received from clients and a portType or other type identifier of operations that need to be supported by a service implementation is identified. A discovery mechanism is invoked for querying service information sources to identify candidates from these sources that support the portType or operations identified. A list of these candidates is compiled and a selection mechanism is used to select a candidate from the compiled list. The selected candidate is then used to generate a service object used by a client for accessing the actual service implementation.

Abstract: A message broker data processing apparatus has a unit for receiving published messages on a topic from a publisher application; a unit for processing the received messages; and a unit for distributing the processed messages to subscriber applications; wherein the unit for distributing includes a plurality of subscription point data processing nodes, a first subscription point data processing node distributes messages to a subscriber application which has previously registered a subscription request identifying the first subscription point data processing node with the broker apparatus.

Abstract: A system and method for effectively synchronizing data in an object oriented distributed transaction processing system employing a multilevel data store. Each object that maintains first-level volatile data registers as a synchronization object if unsynchronized changes to that data exist. A register object at each node tracks synchronized objects registered for that node. Each registered synchronization object, in turn, registers with its superior node when registered synchronization objects are present. A hierarchy of registered synchronization objects and synchronization objects is thereby created. The transaction termination process transmits a pre-prepare message to the registered synchronization hierarchy providing each synchronization object an opportunity to flush its data to the second-level persistent data store. The hierarchical structure of registered objects ensures that the minimum number of messages are transmitted over the network.

Abstract: A system and method for efficiently employing procedural transaction managers from an object oriented transaction processing system. Implementation classes are introduced to bridge selected functions from an object oriented transaction processing system into a procedural system. Bridging allows both the reuse of existing procedural transaction managers and interoperation between procedural and object transactions systems which eases migration to new object oriented systems. Implementation classes include methods necessary to manage information necessary to use a procedural transaction API and to manage information returned by the procedural API.

Abstract: A system and method for reducing message traffic during two phase commitment in a distributed transaction processing system. Transactional objects manage transactions in a distributed system. A coordinator object is responsible for ensuring data consistency by enforcing atomic transaction changes. Any change to one or more resources by a transaction is either made at all or none of the resources. Distributed transactions use interposition to create subordinate coordinator for domains other than the primary domain. Each subordinate coordinator controls transaction commitment of all resources within that domain via a single message sequence per coordinator. Dynamic registration of subordinate coordinator resources ensures that the subordinate coordinator is not added to the commit tree of the root coordinator unless it has recoverable resources. Dynamic registration minimizes the size of the commit tree thereby minimizing the number of messages transmitted during commitment processing.

Abstract: A system and method for using the TRAN procedural transaction coordinator, from the Encina product produced by Transarc Corporation, as the core of an OMG-compliant Object Transaction Service. The method allows the object-oriented Object Transaction Service to interoperate with Encina procedural applications. The interoperation involves coordinated processing of both object oriented transactional requests and Encina procedural transactional requests. Both object oriented and procedural requests can be part of a single atomic transaction without requiring gateways between the products. A system of implementation classes are used to transform object-oriented method invocations into the necessary procedural calls. The implementation classes also accept upcalls from the procedural TRAN and transform them into the necessary Object Transaction Service method invocations.

Abstract: An object oriented transaction processing system based on the Object Management Group Object Management Architecture provides effective transaction scheduling and servicing through a combination of Object Transaction Services and a Transactional Object Request Broker. The Object Transactional Services manage the information needed to provide reliability in transactions, including a two phase commit process to implement transaction atomicity. The transactional Object Request Broker includes a transaction monitor facility to schedule objects to respond to object transaction requests. The tunable transaction monitor increases the efficiency of transaction processing by optimizing use of computer system resources allocated to servicing transactions. The transaction monitor activates the objects necessary to satisfy a transaction request. Activation includes an ability to start new processes or threads of execution or to reuse existing processes or threads.

Abstract: A server concurrency control technique for use in a client/server computing system where a client sends a request to a server for access to a server resource involves receiving client requests of a plurality of lock requester types at a lock requester interface; comparing each of said requests against a lock requester set which has a lock requester type representation corresponding to a lock requester type of previously received client requests which are presently holding locks to server resources; and as a result of the comparing step, determining whether a newly received client request conflicts with previously received client requests which are currently holding locks to server resources.

Abstract: A concurrency control mechanism for a client/server computing system analyzes each client request to determine whether it can be given concurrent access to a server's resources, along with other client requests which are presently accessing the server's resources. Each client request triggers the setting up of a lock request mode which contains conflict resolution logic based on the particulars of the corresponding request. When a new request comes in, the new request's newly created lock request mode is compared to the lock request modes of the previous requests which are currently accessing the server's resources and the conflict resolution logic is carried out to determine whether the new request should be also allowed access.

Abstract: A server in a client/server computing system where a distributed transaction is being carried out, has: a server resource having local data associated therewith; a software element for receiving a registration request from the server resource requesting that the server resource be registered in a transaction, after the server resource has received the transaction context in the explicit transaction propagation mode; and a software element for creating a distributed transaction object representing the transaction in response to receipt of the registration request, the distributed transaction object persisting until the transaction is completed.