会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 1. 发明授权
    • Monitoring a path of a transaction across a composite application
    • 通过复合应用程序监视事务的路径
    • US08756269B2
    • 2014-06-17
    • US13407021
    • 2012-02-28
    • Bret W. DixonScot Dixon
    • Bret W. DixonScot Dixon
    • G06F15/16
    • H04L29/08099H04L41/12H04L67/025H04L67/10
    • At each intermediate transaction hop from among multiple transaction hops in a transaction flow through a composite application, an entry with tracking data for a current transaction hop of the multiple transaction hops is inserted into a tracking envelope associated with the transaction flow and the tracking envelope is passed to a next transaction hop of the transaction hops in the transaction flow. At a final transaction hop of the multiple transaction hops, a final entry with tracking data for the final transaction hop is inserted into the tracking envelope and the multiple entries with tracking data for each of the transaction hops in the tracking envelope are exposed in a single tracking event.
    • 在通过复合应用的事务流中的多个事务跳的每个中间事务跳转中,具有多个事务跳的当前事务跳跃的跟踪数据的条目被插入到与事务流相关联的跟踪包络中,并且跟踪包络是 传递到事务流中的事务跳的下一个事务跳。 在多个事务跳跃的最后事务跳转中,将具有用于最终事务跳转的跟踪数据的最终条目插入到跟踪包络中,并且跟踪包络中的每个事务跳跃的跟踪数据的多个条目暴露在单个 跟踪事件。
    • 2. 发明授权
    • Application access to LDAP services through a generic LDAP interface integrating a message queue
    • 应用程序通过集成消息队列的通用LDAP接口访问LDAP服务
    • US08910184B2
    • 2014-12-09
    • US13283975
    • 2011-10-28
    • Bret W. DixonScot Dixon
    • Bret W. DixonScot Dixon
    • G06F3/00G06F9/44G06F9/46G06F13/00G06F9/54
    • G06F9/44G06F9/546G06F13/00G06F2209/547
    • An LDAP bridge service retrieves a generic LDAP message request, placed in a request queue by a message queuing application, from the request queue. The LDAP bridge service formats the generic LDAP request into a particular API call for at least one LDAP API. The LDAP bridge service calls at least one LDAP API with the particular API call for requesting at least one LDAP service from at least one LDAP server managing a distributed directory. Responsive to the LDAP bridge service receiving at least one LDAP specific response from at least one LDAP API, the LDAP bridge service translates the LDAP specific response into a response message comprising a generic LDAP response. The API bridge service, places the response message in a response queue of the message queuing network, wherein the message queuing application listens to the response queue for the response message.
    • LDAP桥服务从请求队列中检索由消息队列应用程序放置在请求队列中的通用LDAP消息请求。 LDAP桥服务将通用LDAP请求格式化为至少一个LDAP API的特定API调用。 LDAP桥服务至少调用一个LDAP API,并具有特定的API调用,用于从至少一个管理分布式目录的LDAP服务器请求至少一个LDAP服务。 响应于LDAP桥接服务从至少一个LDAP API接收至少一个LDAP特定响应,LDAP桥服务将LDAP特定响应转换成包括通用LDAP响应的响应消息。 API桥服务将响应消息放置在消息排队网络的响应队列中,其中消息队列应用程序监听响应消息的响应队列。
    • 3. 发明授权
    • Message queue transaction tracking using application activity trace data
    • 消息队列事务跟踪使用应用程序活动跟踪数据
    • US08549540B1
    • 2013-10-01
    • US13537043
    • 2012-06-28
    • Scot DixonSimon Teverey HubandLuke Rowan McKenna
    • Scot DixonSimon Teverey HubandLuke Rowan McKenna
    • G06F3/00
    • H04L43/14G06F9/546G06F2209/548
    • An approach is provided that detects inbound messages being put to message queues managed by a middleware message queuing platform. The approach retrieves activity trace data corresponding to each of the inbound messages, with the activity trace data maintained by the middleware message queuing platform. The approach generates inbound event records corresponding the inbound messages based on the activity trace data. The approach then detects outbound messages retrieved from the message queues. Activity trace data corresponding to the outbound messages is retrieved and the approach generates an outbound event record for each outbound message. The approach receives a transaction request from a requestor that corresponds to a message. The approach retrieves and returns the inbound event records and outbound event records that correspond to the requested message. The retrieved event records are used for transaction tracking: to build transaction flow topologies and to report transaction performance metrics.
    • 提供了一种检测入站消息被放入由中间件消息队列平台管理的消息队列的方法。 该方法检索与每个入站消息对应的活动跟踪数据,活动跟踪数据由中间件消息队列平台维护。 该方法基于活动跟踪数据生成对应入站消息的入站事件记录。 然后,该方法检测从消息队列中检索到的出站消息。 检索与出站邮件对应的活动跟踪数据,并且该方法为每个出站邮件生成出站事件记录。 该方法从与消息对应的请求者接收事务请求。 该方法检索并返回与所请求的消息相对应的入站事件记录和出站事件记录。 检索到的事件记录用于事务跟踪:构建事务流拓扑并报告事务性能指标。
    • 4. 发明申请
    • APPLICATION ACCESS TO LDAP SERVICES THROUGH A GENERIC LDAP INTERFACE INTEGRATING A MESSAGE QUEUE
    • 通过一般的LDAP接口集成消息队列来应用LDAP服务
    • US20130111499A1
    • 2013-05-02
    • US13283975
    • 2011-10-28
    • Bret W. DixonScot Dixon
    • Bret W. DixonScot Dixon
    • G06F13/00G06F9/46G06F9/44
    • G06F9/44G06F9/546G06F13/00G06F2209/547
    • An LDAP bridge service retrieves a generic LDAP message request, placed in a request queue by a message queuing application, from the request queue. The LDAP bridge service formats the generic LDAP request into a particular API call for at least one LDAP API. The LDAP bridge service calls at least one LDAP API with the particular API call for requesting at least one LDAP service from at least one LDAP server managing a distributed directory. Responsive to the LDAP bridge service receiving at least one LDAP specific response from at least one LDAP API, the LDAP bridge service translates the LDAP specific response into a response message comprising a generic LDAP response. The API bridge service, places the response message in a response queue of the message queuing network, wherein the message queuing application listens to the response queue for the response message.
    • LDAP桥服务从请求队列中检索由消息队列应用程序放置在请求队列中的通用LDAP消息请求。 LDAP桥服务将通用LDAP请求格式化为至少一个LDAP API的特定API调用。 LDAP桥服务至少调用一个LDAP API,并具有特定的API调用,用于从至少一个管理分布式目录的LDAP服务器请求至少一个LDAP服务。 响应于LDAP桥接服务从至少一个LDAP API接收至少一个LDAP特定响应,LDAP桥服务将LDAP特定响应转换成包括通用LDAP响应的响应消息。 API桥服务将响应消息放置在消息排队网络的响应队列中,其中消息队列应用程序监听响应消息的响应队列。
    • 5. 发明授权
    • Message queuing application access to specific API services through a generic API interface integrating a message queue
    • 消息通过集成消息队列的通用API接口排队应用程序访问特定的API服务
    • US08910185B2
    • 2014-12-09
    • US13284067
    • 2011-10-28
    • Bret W. DixonScot Dixon
    • Bret W. DixonScot Dixon
    • G06F3/00G06F9/44G06F9/46G06F13/00
    • G06F9/44G06F9/546G06F2209/548
    • An API bridge service retrieves a generic API message request, placed in a request queue of a message queuing network by a message queuing application, from the request queue. The API bridge service formats the generic API request into a particular API call for at least one specific API. The API bridge service calls at least one specific API with the particular API call. Responsive to the API bridge service receiving at least one API specific response from at least one specific API, the API bridge service translates at least one API specific response into a response message comprising a generic API response. The API bridge service, places the response message in a response queue of the message queuing network, wherein the message queuing application listens to the response queue for the response message.
    • API桥服务从请求队列中检索通过消息队列应用程序放置在消息排队网络的请求队列中的通用API消息请求。 API桥接服务将通用API请求格式化为至少一个特定API的特定API调用。 API桥接服务通过特定的API调用调用至少一个特定的API。 响应于API桥接服务从至少一个特定API接收至少一个API特定响应,API桥服务将至少一个API特定响应转换成包括通用API响应的响应消息。 API桥服务将响应消息放置在消息排队网络的响应队列中,其中消息队列应用程序监听响应消息的响应队列。
    • 6. 发明申请
    • MESSAGE QUEUING APPLICATION ACCESS TO SPECIFIC API SERVICES THROUGH A GENERIC API INTERFACE INTERGRATING A MESSAGE QUEUE
    • 消息队列应用程序访问特定的API服务通过一般的API接口交织消息队列
    • US20130111500A1
    • 2013-05-02
    • US13284067
    • 2011-10-28
    • Bret W. DixonScot Dixon
    • Bret W. DixonScot Dixon
    • G06F3/00G06F9/44
    • G06F9/44G06F9/546G06F2209/548
    • An API bridge service retrieves a generic API message request, placed in a request queue of a message queuing network by a message queuing application, from the request queue. The API bridge service formats the generic API request into a particular API call for at least one specific API. The API bridge service calls at least one specific API with the particular API call. Responsive to the API bridge service receiving at least one API specific response from at least one specific API, the API bridge service translates at least one API specific response into a response message comprising a generic API response. The API bridge service, places the response message in a response queue of the message queuing network, wherein the message queuing application listens to the response queue for the response message.
    • API桥服务从请求队列中检索通过消息队列应用程序放置在消息排队网络的请求队列中的通用API消息请求。 API桥接服务将通用API请求格式化为至少一个特定API的特定API调用。 API桥接服务通过特定的API调用调用至少一个特定的API。 响应于API桥接服务从至少一个特定API接收至少一个API特定响应,API桥服务将至少一个API特定响应转换成包括通用API响应的响应消息。 API桥服务将响应消息放置在消息排队网络的响应队列中,其中消息队列应用程序监听响应消息的响应队列。
    • 7. 发明申请
    • MONITORING A PATH OF A TRANSACTION ACROSS A COMPOSITE APPLICATION
    • 监测复合材料应用中的交易路径
    • US20130226985A1
    • 2013-08-29
    • US13407021
    • 2012-02-28
    • Bret W. DixonScot Dixon
    • Bret W. DixonScot Dixon
    • G06F15/16
    • H04L29/08099H04L41/12H04L67/025H04L67/10
    • At each intermediate transaction hop from among multiple transaction hops in a transaction flow through a composite application, an entry with tracking data for a current transaction hop of the multiple transaction hops is inserted into a tracking envelope associated with the transaction flow and the tracking envelope is passed to a next transaction hop of the transaction hops in the transaction flow. At a final transaction hop of the multiple transaction hops, a final entry with tracking data for the final transaction hop is inserted into the tracking envelope and the multiple entries with tracking data for each of the transaction hops in the tracking envelope are exposed in a single tracking event.
    • 在通过复合应用的事务流中的多个事务跳的每个中间事务跳转中,具有多个事务跳的当前事务跳跃的跟踪数据的条目被插入到与事务流相关联的跟踪包络中,并且跟踪包络是 传递到事务流中的事务跳的下一个事务跳。 在多个事务跳跃的最后事务跳转中,将具有用于最终事务跳转的跟踪数据的最终条目插入到跟踪包络中,并且跟踪包络中的每个事务跳跃的跟踪数据的多个条目暴露在单个 跟踪事件。
    • 8. 发明申请
    • Linking Single System Synchronous Inter-Domain Transaction Activity
    • 链接单系统同步域间事务活动
    • US20130179448A1
    • 2013-07-11
    • US13344385
    • 2012-01-05
    • Bret William DixonScot DixonSimon Teverey Huband
    • Bret William DixonScot DixonSimon Teverey Huband
    • G06F17/30
    • G06F16/284G06F11/302G06F11/3065
    • An approach is provided to correlate transaction data occurring at two different domains running on a common operating system image without using static, or common, correlators. Request-type event records are collected at a first domain within the operating system image, with each of the request-type event records including execution identifiers and a unique token that indicates the order in which the corresponding request-type event occurred on the first domain. Similarly, response-type event records are collected at a second domain within the operating system image. The request-type event records are matched with the response-type event records based on the execution identifiers and an overall order that is indicated by unique tokens included in the records. The matching of request-type event records with response-type event records indicate a number of inter-domain transactions which are recorded in a correlation data store.
    • 提供了一种方法来将在两个不同的域上发生的交易数据相关联,而不使用静态或常见的相关器,在公共操作系统映像上运行。 请求类型事件记录在操作系统映像中的第一域收集,其中每个请求类型事件记录包括执行标识符和唯一标记,其指示相应的请求类型事件在第一域上发生的顺序 。 类似地,在操作系统映像中的第二域收集响应类型事件记录。 请求类型事件记录与基于执行标识符的响应类型事件记录和由记录中包含的唯一令牌指示的整体顺序相匹配。 请求类型事件记录与响应类型事件记录的匹配指示记录在相关数据存储中的多个域间事务。