International Business Machines Corporation

David B Colasurdo

Srinivas Hasti

Paul Franklin McMahan

John Patrick Whitfield

Gabriel Garcia Montero

Sachin P Patel

Michael L Fraenkel

Gabe G Montero

Described are an apparatus and method for managing test artifacts. A test plan is selected for a product having a plurality of test artifacts comprising one selected from a group consisting of an execution record and a product requirement. One of the test artifacts is selected for a snapshot at a current time. The snapshot includes a storage record that includes information associated with the selected test artifact and its relationship with other test artifacts at the current time. The snapshot of the selected test artifact is acquired. A current state of the selected test artifact is stored as an element of the snapshot. A current state of relationships of the selected test artifact to the other test artifacts is stored. A current state of the other test artifacts having a relationship with the selected test artifact is stored. A type of snapshot is determined, comprising cascading through artifacts of the test plan to capture all information and relationships associated with the test artifact, its child artifacts, and the group consisting of the execution record and the product requirement.

Management of test artifacts using cascading snapshot mechanism

Described is a method for managing test artifacts. According to an embodiment of the method, a test plan for a product is selected by a user. The test plan has multiple test artifacts that include the test plan and at least one of a test case, an execution record defining a configuration of the product, and a product requirement. One of the test artifacts is selected for a snapshot and the snapshot is acquired. The snapshot acquisition includes storing a current state of the selected test artifact, storing a current state of relationships of the selected test artifact to the other test artifacts, and storing a current state of the other test artifacts that have a relationship with the selected test artifact.

A clone managed session affinity system, method and apparatus. A clone-managed session affinity method includes receiving a request from a client. The request includes a reference to a selected clone with which the client has a session affinity relationship. The clone determines whether a session affinity cancellation condition has arisen. If the clone determines that a session affinity termination condition has arisen, the session affinity relationship is cancelled.

Clone-managed session affinity

The invention is a method and apparatus for maintaining session affinity within a server farm when requests sharing a session ID switch between server groups or between server clones in a single server group. In accordance with the invention, client requests include a list of clone identification codes, each code uniquely identifying a clone within a server group for handling the request. The clone identification code may be appended to a session identification code. For each different server that handles a request in a session, a new clone identification code is appended without deleting or overwriting any previously appended clone identification codes. When a request is received, the list of clone identification codes associated with the request is parsed in a predetermined order to search for the first clone identification code that matches one of the clone identification codes of a server in the appropriate server group. If a match is detected, the request is dispatched to that clone. If no match is found, the request is dispatched to a server clone in the server group using any reasonable Work Load Management (WLM) mechanism and then the clone identification code of the selected clone is added to the list.

Method and apparatus for maintaining session affinity across multiple server groups

The invention is a method and apparatus for invalidating session data stored in a database. In accordance with the invention, http sessions stored in the database are allowed to remain in the database without real time testing for session time out. Instead, invalid (or timed out) sessions remain in the database until a specified time. At that specified time, all http sessions are invalidated without actually testing them for time out. Alternately, each session can be individually tested for time out and only those sessions which have actually timed out are removed from the database or otherwise invalidated.

Growing community of inventors

Raleigh, NC, United States of America

David B Colasurdo