I2 Technologies Us, Inc.

I2 Technologies, Inc.

Other

Craig L Dunn

Erik Lee Huddleston

Howard R Courts

Bruce C Macartney-Filgate

Neil K Dholakia

Jacob P Poorte

Timothy J McHyde

Brian J Huddleston

Conor McGann

Michael R Stoffman

Kristin Campanie

An implantable device including a tapered body having a sidewall, an internal cavity, a first end, and a second end, the sidewall including a frusto-conical inner surface extending from the first end to the second end, the first end including a first end opening and the second end including a second end opening, a first side opening extending through the sidewall, a second side opening extending through the sidewall, the second side opening arranged diametrically opposite the first side opening, an external thread arranged helically about a central longitudinal axis of the tapered body, the external thread having a continuously decreasing outer diameter along the tapered body, a first ancillary member operatively arranged to be inserted through the first end opening and then the first or second side opening, and a second ancillary member operatively arranged to be inserted through the first end opening and then the first or second side opening.

Percutaneous sacroiliac joint implant and method for surgically inserting and securing the implant into the sacroiliac joint

In accordance with the present invention, a messaging system utilizes a local queue manager to receive messages intended for other processes. Messages received by the local queue manager are stored onto a local persistent storage device when a process sending the message has completed the sending action. The local queue manager then sends the message to an appropriate recipient. When the message has been received and confirmed, the recipient removes the message from the persistent storage device. If a hardware or software failure occurs, the message is stored and can be re-sent after the failure is corrected. In certain embodiments, a message writer is operable to communicate the message to the receiving process and remove the message from the queue after sending it to the receiving process. In certain embodiments, a message communicated by the sending process comprises a first format, and a message collector is operable to format the message received from the sending process into a standard format for transport to the local queue manager and storage on the persistent storage device.

Messaging system for computers

A system and method are provided for maintaining states for user sessions with a web system. Maintaining state includes receiving a request from a user that initiates a user session with the web system and processing the request to provide a web page to the user. Session data ( ) representing a state of the user session is stored in memory in a global session server ( ). Then, for each subsequent request associated with the user session, the subsequent request is received, and the session data ( ) is retrieved from the global session server ( ). The subsequent request is then processed using the session data ( ) to provide a web page to the user, and the session data ( ) is changed to reflect the processing. The session data ( ) is then updated in the global session server ( ). The global session server ( ) thereby stores session data ( ) unique to each user session accumulated over multiple web transactions. In one implementation, the session data ( ) includes name/value pairs where the values can be self describing objects such as text, numbers, arrays, and interfaces to other objects.

System and method for maintaining a state for a user session using a web system

An enterprise interaction hub ( ) is disclosed which includes a number of layers that interact to manage an enterprise web system. An interaction layer ( ) receives requests to the enterprise web system and returns responsive web pages. A presentation layer ( ) is coupled to the interaction layer ( ) and generates the responsive web pages. A business layer ( ) is coupled to the presentation layer ( ) and provides business logic for use by the presentation layer ( ) in generating the responsive web pages. An integration layer ( ) is coupled to the business layer ( ) and interfaces with existing legacy data to provide the legacy data to the business layer ( ). A trend collection layer ( ) monitors and accumulates historical information from the interaction layer ( ), the presentation layer ( ), the business layer ( ) and the integration layer ( ). The trend collection layer ( ) also stores the historical information in a trend database ( ). A profile database ( ), accessible by the presentation layer ( ) and the business layer ( ), stores profile data, including data mined from the trend database ( ), that characterizes individual user access to the enterprise web system. The profile data is used by the presentation layer ( ) and the business layer ( ) to provide customized dynamic content in the generated web pages.

Enterprise interaction hub for managing an enterprise web system

An enterprise interaction hub (10) is disclosed which includes a number of layers that interact to manage an enterprise web system. An interaction layer (12) receives requests to the enterprise web system and returns responsive web pages. A presentation layer (14) is coupled to the interaction layer (12) and generates the responsive web pages. A business layer (16) is coupled to the presentation layer (14) and provides business logic for use by the presentation layer (14) in generating the responsive web pages. An integration layer (18) is coupled to the business layer (16) and interfaces with existing legacy data to provide the legacy data to the business layer (16). A trend collection layer (32) monitors and accumulates historical information from the interaction layer (12), the presentation layer (14), the business layer (16) and the integration layer (18). The trend collection layer (32) also stores the historical information in a trend database (36). A profile database (38), accessible by the presentation layer (14) and the business layer (16), stores profile data, including data mined from the trend database (36), that characterizes individual user access to the enterprise web system. The profile data is used by the presentation layer (14) and the business layer (16) to provide customized dynamic content in the generated web pages.

A system and method are provided for maintaining states for user sessions with a web system. Maintaining state includes receiving a request from a user that initiates a user session with the web system and processing the request to provide a web page to the user. Session data (220) representing a state of the user session is stored in memory in a global session server (212). Then, for each subsequent request associated with the user session, the subsequent request is received, and the session data (220) is retrieved from the global session server (212). The subsequent request is then processed using the session data (220) to provide a web page to the user, and the session data (220) is changed to reflect the processing. The session data (220) is then updated in the global session server (212). The global session server (212) thereby stores session data (220) unique to each user session accumulated over multiple web transactions. In one implementation, the session data (220) includes name/value pairs where the values can be self describing objects such as text, numbers, arrays, and interfaces to other objects.

Growing community of inventors

Austin, TX, United States of America

Craig L Dunn