Patent application number | Description | Published |
20090217294 | SINGLE PROGRAM CALL MESSAGE RETRIEVAL - Embodiments of the present invention provide a method, system and computer program product for single program code message retrieval for message queues. In an embodiment of the invention, a message queue data processing system can be configured for single program code message retrieval for message queues. The system can include a message queue executing in a host server and providing an API to applications communicatively coupled to the message queue over a computer communications network. The API exposed by the message queue can include a single program call including program code enabled to open a queuing resource in the message queue, to retrieve all messages in a message buffer from the queuing resource and to close the queuing resource. | 08-27-2009 |
20100174696 | AGNOSTIC PROCESSING OF RESOURCE REQUESTS TO MESSAGE QUEUES AND SEQUENTIAL FILES - Embodiments of the present invention provide a method, system and computer program product for agnostic processing of message queues and sequential files. In an embodiment of the invention, a method for agnostic processing of message queues and sequential files can be provided. The method can include receiving an access request for a resource that is uniform for both a message queue and a sequential file and identifying a resource type of the resource. In response to identifying the resource type as a message queue, a corresponding access request specific to a message queue can be invoked in the message queue. Otherwise a corresponding access request specific to a sequential file can be invoked responsive to identifying the resource type as a sequential file. | 07-08-2010 |
20100228766 | QUEUE MESSAGE RETRIEVAL BY SELECTION CRITERIA - Embodiments of the present invention address deficiencies of the art in respect to message queuing and provide a method, system and computer program product for message queue retrieval by selection criteria. In an embodiment of the invention, a method for message queue retrieval by selection criteria can include receiving from a requesting application a message retrieval request for a message in a message queue storing different messages and determining from the message retrieval request both a template defining fields in the messages, and also selection criteria operable upon content stored in at least one of the fields in the messages. The method also can include applying the selection criteria to the messages in the message queue to select a message or subset of the messages in the message queue, and transmitting the message or subset to the requesting application. | 09-09-2010 |
20130013920 | DYNAMIC DATA-PROTECTION POLICIES WITHIN A REQUEST-REPLY MESSAGE QUEUING ENVIRONMENT - A request to process a request message using a request queue within a request-reply messaging environment is detected at a dynamic data protection module. At least one authorized sender module and a sole authorized recipient module of a response message to the request message is identified using a request queue policy of the request queue. A reply queue policy is dynamically created to process the response message using the identified at least one authorized sender module and the sole authorized recipient module of the response message. The dynamically-created reply queue policy is associated with a reply queue. The response message is processed responsive to a request to process the response message using the dynamically-created reply queue policy and the associated reply queue. | 01-10-2013 |
20130013924 | DYNAMIC DATA-PROTECTION POLICIES WITHIN A REQUEST-REPLY MESSAGE QUEUING ENVIRONMENT - A request to process a request message using a request queue within a request-reply messaging environment is detected at a dynamic data protection module. At least one authorized sender module and a sole authorized recipient module of a response message to the request message is identified using a request queue policy of the request queue. A reply queue policy is dynamically created to process the response message using the identified at least one authorized sender module and the sole authorized recipient module of the response message. The dynamically-created reply queue policy is associated with a reply queue. The response message is processed responsive to a request to process the response message using the dynamically-created reply queue policy and the associated reply queue. | 01-10-2013 |
20130111499 | APPLICATION ACCESS TO LDAP SERVICES THROUGH A GENERIC LDAP INTERFACE INTEGRATING A MESSAGE QUEUE | 05-02-2013 |
20130111500 | MESSAGE QUEUING APPLICATION ACCESS TO SPECIFIC API SERVICES THROUGH A GENERIC API INTERFACE INTERGRATING A MESSAGE QUEUE | 05-02-2013 |
20130212379 | DYNAMIC GENERATION AND PROCESSING OF CERTIFICATE PUBLIC INFORMATION DIRECTORIES - Digital certificate public information is extracted using a processor from at least one digital certificate stored within at least one digital certificate storage repository. The extracted digital certificate public information is stored to at least one dynamically-created certificate public information directory. At least a portion of the digital certificate public information stored within the at least one dynamically-created certificate public information directory is provided in response to a digital certificate public information request. | 08-15-2013 |
20130226985 | MONITORING A PATH OF A TRANSACTION ACROSS A COMPOSITE APPLICATION - 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. | 08-29-2013 |
20130227121 | MONITORING A PATH OF A TRANSACTION ACROSS A COMPOSITE APPLICATION - 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. | 08-29-2013 |
20130238895 | RENEWAL PROCESSING OF DIGITAL CERTIFICATES IN AN ASYNCHRONOUS MESSAGING ENVIRONMENT - A renewed digital certificate is obtained within an asynchronous messaging environment from a certificate server of an issuer of an existing digital certificate to replace the existing digital certificate. The renewed digital certificate includes an extended attribute that stores a serial number value of the existing digital certificate. A message is received with a symmetric key that is encrypted using the existing digital certificate. The symmetric key is identified within the message by the serial number value of the existing digital certificate. The message is processed using the renewed digital certificate. | 09-12-2013 |
20130346743 | DIGITAL CERTIFICATE ISSUER-CORRELATED DIGITAL SIGNATURE VERIFICATION - A message including a digital signature is received at a processor. It is determined whether a specific authorized certificate issuer is configured for a message originator within a data protection policy. In response to determining that the specific authorized certificate issuer is configured for the message originator within the data protection policy, it is determined whether a message originator certificate used to generate the digital signature is issued by the configured specific authorized certificate issuer. | 12-26-2013 |
20130346744 | DIGITAL CERTIFICATE ISSUER-CORRELATED DIGITAL SIGNATURE VERIFICATION - A message including a digital signature is received at a processor. It is determined whether a specific authorized certificate issuer is configured for a message originator within a data protection policy. In response to determining that the specific authorized certificate issuer is configured for the message originator within the data protection policy, it is determined whether a message originator certificate used to generate the digital signature is issued by the configured specific authorized certificate issuer. | 12-26-2013 |
20140006775 | MESSAGE ORIGINATOR TOKEN VERIFICATION | 01-02-2014 |
20140006778 | MESSAGE ORIGINATOR TOKEN VERIFICATION | 01-02-2014 |
20140237484 | GENERALIZED APPLICATION MESSAGE GENERATION SERVICE - A message generation request is received from an application using a message generation application programming interface (MG API) at a message generation service (MGS) device. The message generation request includes a request for the MGS to generate a message on behalf of the application and includes message generation parameters passed by the application using the MG API. A distributable message is generated on behalf of the application according to the message generation parameters passed by the application using the MG API and a message file. The message file includes at least one template message construct usable to generate the distributable message. The distributable message is distributed, on behalf of the application, to a resource as requested. | 08-21-2014 |
20140281555 | GENERALIZED CERTIFICATE USE IN POLICY-BASED SECURE MESSAGING ENVIRONMENTS - Within a secure messaging environment, a determination is made that a request to send a message has been generated by a user. A message protection policy configured to process the message within the secure messaging environment is identified. The message protection policy specifies that, within the secure messaging environment, a secured digital certificate, other than a user-assigned digital certificate of the user, is configured with an associated private key to digitally sign the message on behalf of the user. Based upon the message protection policy, a determination is made to digitally sign the message using the private key of the secured digital certificate. The message is signed on behalf of the user using the private key of the secured digital certificate. | 09-18-2014 |
20140281558 | GENERALIZED CERTIFICATE USE IN POLICY-BASED SECURE MESSAGING ENVIRONMENTS - Within a secure messaging environment, a determination is made that a request to send a message has been generated by a user. A message protection policy configured to process the message within the secure messaging environment is identified. The message protection policy specifies that, within the secure messaging environment, a secured digital certificate, other than a user-assigned digital certificate of the user, is configured with an associated private key to digitally sign the message on behalf of the user. Based upon the message protection policy, a determination is made to digitally sign the message using the private key of the secured digital certificate. The message is signed on behalf of the user using the private key of the secured digital certificate. | 09-18-2014 |
20150121067 | DIGITAL CERTIFICATE ISSUER-CORRELATED DIGITAL SIGNATURE VERIFICATION - A message including a digital signature of a message originator is received at a processor. In response to determining that the message originator is authorized by a data protection policy to originate the message, a determination is made as to whether a specific authorized certificate issuer is configured for the message originator within a data protection policy. In response to determining that the specific authorized certificate issuer is configured for the message originator within the data protection policy, a determination is made as to whether a message originator certificate used to generate the digital signature of the message originator is issued by the specific authorized certificate issuer configured for the message originator within the data protection policy. | 04-30-2015 |
20150134747 | MANAGING A MESSAGING QUEUE IN AN ASYNCHRONOUS MESSAGING SYSTEM - A computer implemented method, system and/or computer program product is provided for managing a messaging queue in an asynchronous messaging system. A duration for which a message can remain on the messaging queue is determined. An age of the message on the messaging queue is monitored. The age of the message on the messaging queue and the determined duration is compared and a notification is generated based on the comparison. | 05-14-2015 |
20150254085 | AUTORUN ON EJECT - A method for automatic execution of at least one program associated with a mounted medium, wherein the mounted medium is ejected from a device is provided. The method may include determining if an automatic program initiation on eject is required, wherein the determining is based on a detection of the mounted medium being mounted in the device. The method may also include registering the required automatic program initiation on eject, wherein the registering is based on the determination of the automatic program initiation on eject being required. The method may include storing an executable program content associated with the registered automatic program initiation on eject. Additionally, the method may include executing the stored executable program content, wherein the execution is based on a detection of the mounted medium being ejected from the device. The method may include deregistering the required automatic program initiation on eject. | 09-10-2015 |
20150261591 | FILTERED BRANCH ANALYSIS - In a method for providing information to resolve an abnormal termination of software, a processor receives a notification of an abnormal termination of software at a source line within a source code. A processor determines at least one variable from the source line. A processor causes information about the at least one variable to be displayed, wherein information about a variable comprises a variable declaration source line and a value of the variable. A processor receives a first selection of at least one variable from the source line. A processor causes a first branch analysis to be displayed, wherein the first branch analysis comprises a truncated version of the source code based on the received first selection. | 09-17-2015 |
20150261652 | FILTERED BRANCH ANALYSIS - In a method for providing information to resolve an abnormal termination of software, a processor receives a notification of an abnormal termination of software at a source line within a source code. A processor determines at least one variable from the source line. A processor causes information about the at least one variable to be displayed, wherein information about a variable comprises a variable declaration source line and a value of the variable. A processor receives a first selection of at least one variable from the source line. A processor causes a first branch analysis to be displayed, wherein the first branch analysis comprises a truncated version of the source code based on the received first selection. | 09-17-2015 |
20150278073 | LOGGING CODE GENERATION AND DISTRIBUTION - A method for diagnosing an error associated with a software is provided. The method may include receiving a stack trace associated with the error. The method may also include fetching a source code associated with the received stack trace. The method may further include parsing the fetched source code associated with the received stack trace. The method may also include generating an abstract syntax tree (AST) based on the parsed fetched source code. Additionally, the method may include inserting at least one logging call into the generated abstract tree. The method may include recompiling the captured code based on the generated abstract tree with the at least one inserted logging call. The method may also include uploading the recompiled code onto at least one deployment server. | 10-01-2015 |
20150278074 | LOGGING CODE GENERATION AND DISTRIBUTION - A method for diagnosing an error associated with a software is provided. The method may include receiving a stack trace associated with the error. The method may also include fetching a source code associated with the received stack trace. The method may further include parsing the fetched source code associated with the received stack trace. The method may also include generating an abstract syntax tree (AST) based on the parsed fetched source code. Additionally, the method may include inserting at least one logging call into the generated abstract tree. The method may include recompiling the captured code based on the generated abstract tree with the at least one inserted logging call. The method may also include uploading the recompiled code onto at least one deployment server. | 10-01-2015 |
20150331781 | DEBUGGING DATA FORMAT CONVERSION - In an approach for generating a compiler listing using Debugging With Attributed Record Format (DWARF) debugging data, a processor receives DWARF debugging data associated with source code of a programming language. A processor extracts information from the DWARF debugging data, wherein the information comprises at least source code lines, variable declaration lines, and variable reference lines. A processor generates a compiler listing based on the information extracted from the DWARF debugging data, wherein the compiler listing includes at least a symbol table, and cross-reference information. | 11-19-2015 |
20150331783 | DEBUGGING DATA FORMAT CONVERSION - In an approach for generating a compiler listing using Debugging With Attributed Record Format (DWARF) debugging data, a processor receives DWARF debugging data associated with source code of a programming language. A processor extracts information from the DWARF debugging data, wherein the information comprises at least source code lines, variable declaration lines, and variable reference lines. A processor generates a compiler listing based on the information extracted from the DWARF debugging data, wherein the compiler listing includes at least a symbol table, and cross-reference information. | 11-19-2015 |
Patent application number | Description | Published |
20130111499 | APPLICATION ACCESS TO LDAP SERVICES THROUGH A GENERIC LDAP INTERFACE INTEGRATING A MESSAGE QUEUE | 05-02-2013 |
20130111500 | MESSAGE QUEUING APPLICATION ACCESS TO SPECIFIC API SERVICES THROUGH A GENERIC API INTERFACE INTERGRATING A MESSAGE QUEUE | 05-02-2013 |
20130179446 | Linking Single System Synchronous Inter-Domain Transaction Activity - 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. | 07-11-2013 |
20130179448 | Linking Single System Synchronous Inter-Domain Transaction Activity - 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. | 07-11-2013 |
20130226985 | MONITORING A PATH OF A TRANSACTION ACROSS A COMPOSITE APPLICATION - 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. | 08-29-2013 |
20130227121 | MONITORING A PATH OF A TRANSACTION ACROSS A COMPOSITE APPLICATION - 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. | 08-29-2013 |
20140006606 | Message Queue Transaction Tracking Using Application Activity Trace Data | 01-02-2014 |
20140108641 | TRANSACTION MIDDLEWARE BASED APPLICATION LEVEL TRANSACTION INSTANCE TRACKING ACROSS A COMPOSITE APPLICATION - Responsive to transactional middleware for a particular domain processing a particular transaction instance at a processing point specified in transaction telemetry standards as a tracking point along a flow of the particular transaction, a facility of the middleware accesses correlation data for the particular transaction instance in the particular domain and extracts application level context information about the particular transaction instance from the particular domain, wherein the transaction telemetry standards specify a same set of standards for application by each separate transactional middleware instance of a composite application. At least one facility of the transactional middleware creates a tracking event comprising the correlation data and the application level context information formatted into an event structure defined by the transaction tracking standards. At least one facility of the transactional middleware surfaces the tracking event in compliance with the transaction telemetry standards. | 04-17-2014 |
20140108646 | TRANSACTION MIDDLEWARE BASED APPLICATION LEVEL TRANSACTION INSTANCE TRACKING ACROSS A COMPOSITE APPLICATION - Responsive to transactional middleware for a particular domain processing a particular transaction instance at a processing point specified in transaction telemetry standards as a tracking point along a flow of the particular transaction, a facility of the middleware accesses correlation data for the particular transaction instance in the particular domain and extracts application level context information about the particular transaction instance from the particular domain, wherein the transaction telemetry standards specify a same set of standards for application by each separate transactional middleware instance of a composite application. At least one facility of the transactional middleware creates a tracking event comprising the correlation data and the application level context information formatted into an event structure defined by the transaction tracking standards. At least one facility of the transactional middleware surfaces the tracking event in compliance with the transaction telemetry standards. | 04-17-2014 |
20150134747 | MANAGING A MESSAGING QUEUE IN AN ASYNCHRONOUS MESSAGING SYSTEM - A computer implemented method, system and/or computer program product is provided for managing a messaging queue in an asynchronous messaging system. A duration for which a message can remain on the messaging queue is determined. An age of the message on the messaging queue is monitored. The age of the message on the messaging queue and the determined duration is compared and a notification is generated based on the comparison. | 05-14-2015 |
20150186252 | TESTING OF TRANSACTION TRACKING SOFTWARE - In a method for generating test transactions across computing systems, a first test function of a first program on a first computing system of a plurality of computing systems receives a plurality of instructions, wherein a first instruction of the plurality of instructions is to invoke a first transaction between a second function of the first program and a second program on a second computing system of the plurality of computing systems. The first test function of the first program causes the transaction between the second function of the first program on the first computing system and the second program on the second computing system. The first test function of the first program sends the plurality of instructions to a second test function on a third computing system of the plurality of computing systems, based on a second instruction of the plurality of instructions. | 07-02-2015 |
20150186254 | TESTING OF TRANSACTION TRACKING SOFTWARE - In a method for generating test transactions across computing systems, a first test function of a first program on a first computing system of a plurality of computing systems receives a plurality of instructions, wherein a first instruction of the plurality of instructions is to invoke a first transaction between a second function of the first program and a second program on a second computing system of the plurality of computing systems. The first test function of the first program causes the transaction between the second function of the first program on the first computing system and the second program on the second computing system. The first test function of the first program sends the plurality of instructions to a second test function on a third computing system of the plurality of computing systems, based on a second instruction of the plurality of instructions. | 07-02-2015 |
20150229545 | TRANSACTION MIDDLEWARE BASED APPLICATION LEVEL TRANSACTION INSTANCE TRACKING ACROSS A COMPOSITE APPLICATION - Responsive to middleware for a domain processing a transaction instance at a processing point specified in transaction telemetry standards as a tracking point along a flow of the transaction instance from a requesting domain to a requestee domain, a facility of the middleware determines whether a token with correlation data comprising a unique identifier for the transaction instance available to both the requesting domain and the requestee domain is passed to the domain in compliance with transaction telemetry standards. Responsive to the facility of the middleware not detecting the token with correlation data, the token with generated correlation data accessible to the domain is generated. The facility of the middleware passes the token to at least one subsequent middleware instance of the plurality of middleware instances of the composite application along the flow of the transaction instance to uniquely identify the transaction instance. | 08-13-2015 |