Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method of logging data, the method comprising: receiving using an on-ramp and a message box server, a message, the message comprising a data payload, and forwarding the message to a receiving pipeline; if the message comprises an itinerary in a message header, then copying the itinerary comprised in the message header into one or more context properties associated with the message using an ESB pipeline component and the message box server, otherwise, using an ESB pipeline component and the message box server to select the itinerary from an itinerary database using data from the data payload or context data from the one or more context properties associated with the message and copying the itinerary into the one or more context properties; processing the message using the message box server for each of one or more steps in the itinerary at each of the one or more steps wherein the one or more steps of the itinerary comprises a logging step; if during processing of the message in the pipeline the one of the one or more steps is the logging step and a Business Rule Engine (BRE) resolver is selected for use in the logging step, then: sending a data type desired and at least a part of the message to the BRE using the BRE resolver and the message box server; determining the policy to be used to process the message using the BRE; processing the message with the BRE using the policy to obtain the data value corresponding with the data type desired using the message box server; forwarding the data value to a BRE resolver provider associated with the BRE using the message box server; logging the data value to a table associated with a Business Activity Monitor (BAM) monitoring activity where the table is comprised in a BAM database using the message box server; forwarding the message to a sending pipeline identified in the itinerary using the message box server; routing the message to an off-ramp identified in the itinerary using the message box server.
A method for logging data in an enterprise service bus (ESB) involves receiving a message with a data payload via an on-ramp and a message box server, then forwarding it to a receiving pipeline. If the message contains an itinerary (routing slip) in its header, the itinerary is copied into context properties associated with the message. Otherwise, the system selects an itinerary from an itinerary database based on the data payload or context data. The message is processed step-by-step according to the itinerary. When a logging step is encountered and a Business Rule Engine (BRE) resolver is selected, the system sends the desired data type and a part of the message to the BRE. The BRE determines a processing policy, extracts the data value corresponding to the desired data type, and forwards the data value to a BRE resolver provider. Finally, the data value is logged to a table in a Business Activity Monitor (BAM) database, and the message is routed to an off-ramp specified in the itinerary.
2. The method of claim 1 , wherein the logging step is a messaging itinerary step.
The method of logging data as described, which involves receiving a message, extracting or selecting an itinerary, processing the message step-by-step, and using a Business Rule Engine (BRE) to log specific data values to a Business Activity Monitor (BAM) database, has a logging step that is specifically a messaging itinerary step. This means the logging action is performed as part of the overall message routing and processing defined by the itinerary, indicating that the logging is tightly integrated with the message flow.
3. The method of claim 1 , wherein the logging step is a logging orchestration step.
The method of logging data as described, which involves receiving a message, extracting or selecting an itinerary, processing the message step-by-step, and using a Business Rule Engine (BRE) to log specific data values to a Business Activity Monitor (BAM) database, has a logging step that is specifically a logging orchestration step. This indicates that the logging is performed as a separate, managed process within the ESB, potentially allowing for more complex logging logic or centralized control over logging activities, distinct from merely integrating with the message routing.
4. The method of claim 1 , further comprising: if during processing of the message in the pipeline the one of the one or more steps is the logging step and an xpath resolver and policy is selected for use in the logging step, then processing the message using the xpath resolver and the policy to retrieve a data value from the message, where the data value is associated with a data type included in the logging step using the message box server; forwarding the data value to an xpath resolver provider using the message box server.
The method of logging data as described, which involves receiving a message, extracting or selecting an itinerary, and processing the message step-by-step, also includes an alternative logging mechanism. If a logging step is encountered and an XPath resolver and policy are selected, the system retrieves a data value directly from the message using the XPath expression, based on the data type specified in the logging step. The extracted data value is then forwarded to an XPath resolver provider, which presumably handles the actual logging operation to the Business Activity Monitor (BAM) database.
5. The method of claim 1 , further comprising: if during processing of the message in the pipeline the one of the one or more steps is the logging step and a context resolver and a policy is selected for use in the logging step, then processing the message using the context resolver and the policy to retrieve a data value from context properties included in the message, the data value associated with a data type included in the logging step using the message box server; forwarding the data value to a context resolver provider using the message box server.
The method of logging data as described, which involves receiving a message, extracting or selecting an itinerary, and processing the message step-by-step, also includes another alternative logging mechanism. If a logging step is encountered and a context resolver and policy are selected, the system retrieves a data value from the message's context properties using the context resolver, based on the data type specified in the logging step. The extracted data value is then forwarded to a context resolver provider, which presumably handles the actual logging operation to the Business Activity Monitor (BAM) database.
6. A method of logging data to a Business Activity Monitoring (BAM) monitoring activity, the method comprising: using an itinerary for a message, processing the message with a message box server using an itinerary logging step comprised in the itinerary; if during processing of the message using the logging step a Business Rule Engine (BRE) resolver is selected in the logging step, then: sending the data type desired and the message to the BRE using the BRE resolver and the message box server; dynamically determining the policy needed to process the message using the BRE; processing the message with the BRE using the policy to obtain the data value corresponding with the data type desired using the message box server; forwarding the data value to a BRE resolver provider associated with the BRE using the message box server; logging the data value to a table associated with a Business Activity Monitor (BAM) monitoring activity where the table is comprised in a BAM database using the message box server.
A method for logging data to a Business Activity Monitoring (BAM) system involves processing a message with a message box server according to an itinerary that includes a logging step. If the logging step uses a Business Rule Engine (BRE) resolver, the system sends the desired data type and the message to the BRE. The BRE dynamically determines the necessary processing policy, extracts the data value corresponding to the desired data type, and forwards it to a BRE resolver provider. Finally, the extracted data value is logged to a table associated with the BAM activity within the BAM database.
7. The method of claim 6 , wherein the logging step is a messaging itinerary step.
The method of logging data to a Business Activity Monitoring (BAM) system using an itinerary, a message box server, and a Business Rule Engine (BRE) resolver, has a logging step that is a messaging itinerary step. This specifies that the logging is performed directly as part of the message's defined path within the itinerary, making it a fundamental component of the message's routing and processing.
8. The method of claim 6 , wherein the logging step is a logging orchestration step.
The method of logging data to a Business Activity Monitoring (BAM) system using an itinerary, a message box server, and a Business Rule Engine (BRE) resolver, has a logging step that is a logging orchestration step. This indicates the logging operation is managed as a separate process within the ESB, allowing for greater control or potentially more sophisticated or centralized logging functionality beyond simply being part of the message flow.
9. The method of claim 6 , further comprising: if during processing of the message using the logging step an xpath resolver and a policy is selected for use in the logging step, then processing the message using the xpath resolver and the policy to retrieve a data value from the message, where the data value is associated with a data type included in the logging step using the message box server; forwarding the data value to an xpath resolver provider using the message box server.
The method of logging data to a Business Activity Monitoring (BAM) system using an itinerary and a message box server also includes an alternative logging method. If an XPath resolver and policy are selected for the logging step, the system extracts a data value from the message using the XPath resolver, based on the specified data type. This extracted data is then forwarded to an XPath resolver provider, which presumably handles the logging of this data to the BAM system.
10. The method of claim 6 , further comprising: if during processing of the message using the logging step a context resolver and a policy is selected in the logging step, then processing the message using the context resolver and a policy to retrieve a data value from context properties included in the message, the data value associated with a data type included in the logging step using the message box server; forwarding the data value to a context resolver provider using the message box server.
The method of logging data to a Business Activity Monitoring (BAM) system using an itinerary and a message box server also includes another alternative logging method. If a context resolver and a policy are selected for the logging step, the system retrieves a data value from the message's context properties using the context resolver, based on the specified data type. This extracted data is then forwarded to a context resolver provider, which presumably handles the logging of this data to the BAM system.
Unknown
December 12, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.