IP Library Granted Patent US 7,275,104
Granted Patent B1
US 7,275,104 · App. 10/425,802 · Granted Sep 25, 2007

Web-services-based data logging system including multiple data logging service types

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,275,104
App. No.
10/425,802
Granted
Sep 25, 2007
Kind
B1
Abstract

Methods, apparatuses, and systems allowing for configuration of message logging policy on a granular basis for web services networks. In certain embodiments, the present invention allows for an efficient data logging scheme where only messages, or message elements, of interest are stored. According to one embodiment of the present invention, the fabric services associated with the web services network architecture supports different instances of a logging service to which message data are logged. For example, the logging service instances can be configured to log only header information (header logging instance), only payload information (payload logging instance), or entire messages (message logging instance). The web services network control points can be configured to flag messages transmitted to a logging node with a logging service type, which determines which logging service instance operates on the message.

Claims (36)

1. A control point enabling policy-based data logging, comprising:

a control point module operative to mediate transport of messages between providing nodes and consuming nodes, said control point module, as part of said transport mediation, being operative to:

identify message types corresponding to the messages transmitted between the providing nodes and the consuming nodes;

associate logging service types to the messages based on the corresponding messages types; and

transmit the messages to a data logging node with indications of the logging service types;

a network directory comprising at least one service operation identifier, at least one message type identifier associated with the at least one service operation identifier, and at least one logging service type identifier associated with the at least one message type identifier, and wherein said control point module is operative to access the network directory to associate logging service type identifiers with the messages, and wherein the at least one logging service type identifier is a header-only logging service identifier.

2. A control point enabling policy-based data logging, comprising:

a control point module operative to mediate transport of messages between providing nodes and consuming nodes, said control point module, as part of said transport mediation, being operative to:

identify message types corresponding to the messages transmitted between the providing nodes and the consuming nodes;

associate logging service types to the messages based on the corresponding messages types; and

transmit the messages to a data logging node with indications of the logging service types;

a network directory comprising at least one service operation identifier, at least one message type identifier associated with the at least one service operation identifier, and at least one logging service type identifier associated with the at least one message type identifier, and wherein said control point module is operative to access the network directory to associate logging service type identifiers with the messages, and wherein the at least one logging service type identifier is a payload-only logging service identifier.

3. A data logging node supporting a plurality of data logging service types, comprising:

a data logging interface operative to support the plurality of data logging service types;

a data logging module operative to:

receive a log message and a data logging service type identifier; and

store at least one element of the log message, wherein the at least one stored element is based on the data logging service type identifier associated with the log message; and

wherein the log message comprises a header and a payload, and wherein the payload comprises a message associated with a web services invocation between a consuming node and a providing node, and wherein the header includes the data logging service type identifier associated with the log message;

wherein the at least one stored element of the log message is one from the group comprising the message header and the message payload; and

wherein one of the plurality of data logging service types is a header-only message logging type.

4. A data logging node supporting a plurality of data logging service types, comprising:

a data logging interface operative to support the plurality of data logging service types;

a data logging module operative to:

receive a log message and a data logging service type identifier; and

store at least one element of the log message, wherein the at least one stored element is based on the data logging service type identifier associated with the log message; and

wherein the log message comprises a header and a payload, and wherein the payload comprises a message associated with a web services invocation between a consuming node and a providing node, and wherein the header includes the data logging service type identifier associated with the log message;

wherein the at least one stored element of the log message is one from the group comprising the message header and the message payload; and

wherein one of the plurality of data logging service types is a payload-only message logging type.

5. A data logging node supporting a plurality of data logging service types, comprising:

a data logging interface operative to support the plurality of data logging service types;

a data logging module operative to:

receive a log message and a data logging service type identifier; and

store at least one element of the log message, wherein the at least one stored element is based on the data logging service type identifier associated with the log message; and

wherein the log message comprises a header and a payload, and wherein the payload comprises a message associated with a web services invocation between a consuming node and a providing node, and wherein the header includes the data logging service type identifier associated with the log message;

wherein the at least one stored element of the log message is one from the group comprising the message header and the message payload; and

wherein one of the plurality of data logging service types is an entire-message logging type.

Assignments (16)
RELEASE OF SECURITY INTEREST IN PATENTS Recorded Aug 7, 2019
From: BRIGHTWOOD LOAN SERVICES LLC, AS ADMINISTRATIVE AGENT AND COLLATERAL AGENT
To: AKANA, INC.; ROGUE WAVE SOFTWARE, INC.; PERFORCE SOFTWARE, INC.
Reel/Frame 049996/0115 →
RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL Recorded Jul 22, 2019
From: ANTARES CAPITAL LP, AS COLLATERAL AGENT
To: AKANA, INC.
Reel/Frame 049823/0685 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Jul 22, 2019
From: PERFORCE SOFTWARE, INC.; PERFORCE INTERMEDIATE HOLDINGS, LLC; AKANA, INC.; GLIFFY, INC.; KLOCWORK INC.; OPENLOGIC, INC.; ROGUE WAVE HOLDING CORP.; ROGUE WAVE HOLDINGS, INC.; ROGUE WAVE SOFTWARE, INC.; RWS, INC.; TOTALVIEW TECHNOLOGIES, INC.; TOTALVIEW TECHNOLOGIES LLC; VISUAL NUMERICS, INC.; ZEROTURNAROUND USA, INC.; ZEROTURNAROUND, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 049823/0752 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Jul 8, 2019
From: AKANA, INC.
To: CORTLAND CAPITAL MARKET SERVICES LLC, AS COLLATERAL AGENT
Reel/Frame 049688/0800 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Feb 8, 2019
From: AKANA, INC.
To: ANTARES CAPITAL LP, AS COLLATERAL AGENT
Reel/Frame 049859/0124 →
RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL Recorded Feb 8, 2019
From: FIRST EAGLE PRIVATE CREDIT, LLC (F/K/A/ NEWSTAR FINANCIAL, LLC (NEWSTAR FINANCIAL, LLC F/K/A NEWSTAR FINANCIAL, INC.))
To: ROGUE WAVE SOFTWARE, INC.; ROGUE WAVE HOLDINGS, INC.; KLOCWORK INC.; TOTALVIEW TECHNOLOGIES, INC.; TOTALVIEW TECHNOLOGIES LLC; RWS, INC.; OPENLOGIC, INC.; VISUAL NUMERICS, INC.; AKANA, INC.
Reel/Frame 048289/0928 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Feb 8, 2019
From: AKANA, INC.; ROGUE WAVE SOFTWARE, INC.; PERFORCE SOFTWARE, INC.
To: BRIGHTWOOD LOAN SERVICES LLC, AS COLLATERAL AGENT
Reel/Frame 048290/0223 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Feb 8, 2019
From: AKANA, INC.; ROGUE WAVE SOFTWARE, INC.; PERFORCE SOFTWARE, INC.
To: BRIGHTWOOD LOAN SERVICES LLC, AS COLLATERAL AGENT
Reel/Frame 048290/0241 →
RELEASE OF SECURITY INTEREST Recorded Dec 6, 2016
From: MULTIPLIER CAPITAL, LP
To: AKANA, INC.
Reel/Frame 040842/0358 →
SECURITY INTEREST Recorded Nov 29, 2016
From: AKANA, INC.
To: NEWSTAR FINANCIAL, INC.
Reel/Frame 040456/0699 →
SECURITY AGREEMENT Recorded Apr 7, 2016
From: AKANA, INC.
To: MULTIPLIER CAPITAL, LP
Reel/Frame 038381/0780 →
CHANGE OF NAME Recorded May 1, 2015
From: SOA SOFTWARE, INC.
To: AKANA, INC.
Reel/Frame 035566/0196 →
RELEASE OF SECURITY INTEREST Recorded Jun 23, 2014
From: VENTURE LENDING & LEASING V, INC.
To: SOA SOFTWARE, INC.
Reel/Frame 033217/0035 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 10, 2014
From: BLUE TITAN SOFTWARE, INC.
To: SOA SOFTWARE INC.
Reel/Frame 033070/0604 →
SECURITY INTEREST Recorded Aug 18, 2008
From: SOA SOFTWARE, INC.
To: VENTURE LENDING & LEASING V, INC.
Reel/Frame 021411/0393 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 29, 2003
From: MARTINEZ, FRANK; TOTH, PAUL KEVIN
To: BLUE TITAN SOFTWARE, INC.
Reel/Frame 014024/0847 →