Abstract:
PROBLEM TO BE SOLVED: To simplify the job of an application writer by locally generating a transaction when a client can be restored, and remotely generating the transaction when the client can not be restored. SOLUTION: A client computer 10 is provided with an application program 40. When the client computer 10 desires a request for the service of a server computer 20, the first application program 40 communicates the request for the service to a first logical means 50. A transaction start command is written regardless of whether or not the client 10 can be restored, and when the client 10 can be restored, a transaction is locally generated on the client 10, and when the client 10 can not be restored, the transaction is remotely generated for the client 10 in response to the transaction start command.
Abstract:
WS-Addressing EndpointReferences represent Web service endpoints and are propagated in the SOAP Envelope as part of Web service interactions. There is disclosed a method, apparatus and computer program for resolving (or modifying) aspects of the EndpointReference at the time of its propagation based on the EndpointReference recipient. Different recipients will potentially receive differing EndpointReferences. Aspects of the EndpointReference are re-resolved as the SOAP XML representing the EndpointReference is generated for the EndpointReference's propagation. For example, the location of the recipient might make a difference to the address propagated - if the recipient is outside a firewall, it may be appropriate to provide the recipient with the address of the firewall itself and to allow the firewall to re-route any request from the data to the web service endpoint. Alternatively, metadata contained within the EndpointReference might vary depending on the recipient - policy metadata contained within the EndpointReference might specify more stringent security requirements depending on the recipient.
Abstract:
A client processing apparatus for use in a client/server computing system which carries out transactions, issues a begin command to signify the beginning of a transaction; sends a substantive transactional command to a remote server, said command including a transaction context having a specific value which indicates that a transaction has been started but transaction objects which represent the transaction have not yet been created; and receives a modified transaction context from said remote server once said remote server has created said transaction objects.
Abstract:
Client/server middleware processes a source code client application program so that when the application program signifies the beginning of a transaction using a transaction begin command, the transaction is automatically created locally for a recoverable client and remotely for a non-recoverable client. The source code client application program can thus be written without regard to whether the transaction will be created locally or remotely, the middleware takes care of this function.
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.
Abstract:
A client processing apparatus for use in a client/server computing system which carries out transactions, the apparatus having: a means for issuing a begin command to signify the beginning of a transaction; a means for sending a command to a an object in a remote server, the command including a transaction context having a specific value which indicates that a transaction has been started but transaction objects which represent the transaction have not yet been created; and a means for receiving a modified transaction context from the remote server once the remote server has created the transaction objects.
Abstract:
Transaction processing in a distributed object-oriented environment. Server 21 stores transaction state data including coordinator object 211, and server 22 has resource object 221 which receives a transaction context of the transaction represented by coordinator object 211, via the explicit transaction propagation mode. Server resource 221 makes a transaction registration request to customised coordinator proxy (CCP) object 222, and CCP object 222 creates a distributed transaction resource (DTR) object 223 representing the transaction. DTR object 223 registers with remote coordinator object 211, may create duplicate CCP object 222', forwards the 2-phase commit protocols to server resource 221 and then destroys duplicate CCP object 222' and itself. Since the DTR and duplicate CCP objects persist in server 22 during the lifetime of the transaction, even though original CCP object 222 is destroyed as soon as the resource object 221's direct involvement with the transaction has finished, these transaction representations can be counted to determine the total number of transactions currently pending in which the server is involved.