| Patent application number | Description | Published |
|---|
| 20100153454 | AGGREGATING PERSISTED OPERATIONAL DATA IN A DISTRIBUTED ENVIRONMENT - Coordinating persisted data in a distributed system, in which persisted data is stored with identifiers that indicate a hierarchical relationship of the persisted data with a business scenario. When operation data is stored as a record of a transaction within the distributed system, a root identifier (ID) and a connection ID can be added to the operational data record. The root ID indicates a source endpoint of the transaction, and the connection ID indicates a communication message from the source endpoint to the destination endpoint related to the transaction. A persisted data coordination engine can access persisted data in the distributed system and generate a business scenario transaction tree based on the root ID and the connection ID. A map of the business scenario transaction tree can then be created and reported. | 06-17-2010 |
| 20100153524 | ISOLATED APPLICATION SERVER - Dynamically isolating application servers, wherein only active application servers are indicated to client applications to prevent access to inactive application servers by the client applications. A central server of a distributed system determines a state of application servers in a system, and generates a list of application servers that includes all application servers of the system including an indication of the state of the application servers. The central server also generates a filtered list of application servers that excludes inactive application servers or application servers in an inactive mode. The filtered list is passed to client applications, which enables the client applications to only access the active application servers, but not access the inactive application servers. | 06-17-2010 |
| 20100332665 | Multi-Channel Sessions - Implementations of the present disclosure provide multiple communication channels between a client and a session and include establishing a first communication channel between the session and a first application program executed on the client, the session being active on an application server, the first application program using a first communication protocol, and instantiating a second application program on the client. A second communication channel is established between the second application program and the session, the second application program using a second communication protocol different from the first. | 12-30-2010 |
| 20110119326 | EXCHANGE OF CALLBACK INFORMATION - In one embodiment, a method is provided for exchanging callback information. In this method, a first request-response based protocol request is transmitted to a computing device, and a first request-response based protocol response is received from the computing device. Here, the first request-response based protocol response is identified to encapsulate a callback request and this callback request is extracted from the first request-response based protocol response. The callback request is then processed to generate a callback response, and the callback response is encapsulated in a second request-response based protocol request. The second request-response based protocol request is transmitted to the computing device, and a second request-response based protocol response is received after the transmission of the second request-response based protocol request from the computing device. Here, the second request-response based protocol response is a response to the first request-response based protocol request. | 05-19-2011 |
| 20110131295 | Provision of Troubleshooting Tools in a Network System - In an embodiment, a method is provided for providing a tool used for troubleshooting a component. This tool is included in an application server that is in communication with multiple client computing devices. Here, a request to activate the tool is received from one or more client computing devices. This request includes a diagnostic identifier that uniquely identifies the client computing device that transmitted the request. Upon receipt of the request, the tool is activated at the application server with the diagnostic identifier used as an input parameter. When activated, the tool can identify the client computing device based on the diagnostic identifier and can provide a functionality associated with the troubleshooting to the client computing device. | 06-02-2011 |
| 20110138457 | Securing Communications Between Different Network Zones - In an embodiment, a method is provided for communicating a protocol request at a network zone. In this method, the protocol request is received from a computing device and this protocol request is encapsulated in a different protocol. The protocol request is then transmitted to a different network zone by way of the different protocol. A message is then accessed from the different network zone by way of the different protocol, and this message includes a protocol response to the protocol request. The protocol response is extracted from the message and transmitted to the computing device. | 06-09-2011 |
| 20110153538 | Rule-based Processing in Different Layers - In an embodiment, a method is provided for processing rules within a layer of an application. In this method, a rule defining a condition and a functionality associated with the condition is received at runtime of the layer. This functionality is provided by the layer. Using a microprocessor, a fulfillment of the condition is identified and the functionality is executed based on this identification. | 06-23-2011 |
