Abstract: A disclosed method for transforming data from client-server request/response cycle includes receiving session-level semantic events. The session-level semantic events are mapped to accumulation containers based on a policy, for instance, based on a session identifier. The session level semantic events are examined for a type. From the type, the session level semantic events are mapped to one or more rules which perform aggregations, accumulations, or other operations based on the data from the session level semantic events. The rules perform these aggregations, accumulations, or other operations over a set of session level semantic events for generating information (termed “enterprise facts”) that are independent of the client-server protocol and have an meaning in context that spans more than the request/response cycle. Enterprise facts are generated when an session level semantic event that is a triggering condition for an action is received.

Abstract: Disclosed are computer-implemented methods and systems for generating composite resources of a web site. A request including an identifier of a composite site is received and the identifier used to retrieve a characterization of the composite site. The characterization includes identifiers of component resources that make up the composite site resource as well as the layout in which the components should be assembled to form the composite site resource. Upon identifying the components, this information is passed to a client system that retrieves the component resources, e.g., from across a network. The retrieved components are assembled into the composite site resource at the server side, of a client-server interaction with the end-user. The composite site resource is provided to the end user's client system. An additionally disclosed aspect is where the composite site resources includes an HTML frameset.

Abstract: Disclosed are computer-implemented systems and methods for the management and operation of network-based partner, e.g., business, relationships. A representation of the partner relationship is established that includes rules for allocation of compensation, the subject matter to come under the partner relationship, and a resources to be presented to users/customers when they encounter an aspect of the partner relationship, for instance by browsing a web site of one of the partner entities. A system implementing the partner relationship includes a transactional engine for monitoring the browsing activity of a user while browsing partner relationship resources. A composite site manager generates the partner relationship resources based on component resources drawn from the partner entities and a presentation characterization forming part of the relationship representation. The transactional engine generates event data from the client-server request/response data flow.