Browse Prior Art Database

Technique to continuously improve configuration parameters of a software component connected to an endpoint Disclosure Number: IPCOM000235827D
Publication Date: 2014-Mar-26
Document File: 6 page(s) / 45K

Publishing Venue

The Prior Art Database


Technique to continuously improve configuration parameters of a software component connected to an endpoint. The proposed technique also paves way for auto configuration of parameters whenever there is a change in the available resources.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 36% of the total text.

Page 01 of 6

Technique to continuously improve configuration parameters of a software component connected to an endpoint

A software component which is interested in receiving events from the endpoint like Enterprise Information Systems or an application usually adopts two strategies.

PULL Model: The software component makes regular calls/connections to the EIS and pulls the events or records from the target system. During this process it is essential that the software component makes optimum number of trips and pulls the optimum number of events per each trip from the endpoint for better performance and throughput of the entire system.

PUSH Model: The software component registers itself as the consumer for the events and the endpoint pushes the events as and when the events get generated at the endpoint. This works very much similar to any of PUB-SUB model.

Though the technique is generic enough to be applied to any software

component which connects to an endpoint and receive events at regular intervals

, the system describes the usage scenarios and implementation specifics using Adapter/Connector for better illustrative purpose.

Adapters/Connectors are the prime components in the Middleware Integration domain to help applications connect to various Information Stores or EIS.

Adapter allows business events to flow from/to an Enterprise Information System (EIS) to a listening client such as a business process or other application. The event flow is bidirectional and referred as INBOUND and OUTBOUND.

Inbound allows adapter to poll the target EIS on predefined interval; whereas in Outbound flow client external to adapter will send the event to adapter and will be delivered to EIS.

Figure 1.


Page 02 of 6

Adapter enables managed, bidirectional connectivity between enterprise information systems (EIS) and J2EE components. Adapters are also used for business data monitoring in enterprise application and service integration scenarios.

Adapter is configured to poll for a determined number of events at determined intervals. Some EISs limit the number of events for which a adapter may poll during one poll cycle. Consequently, to insure efficient utilization of the resources (network, bandwidth) between the adapter and the EIS and to limit the latency of business objects ready for transmission, the selection and determination of polling quantities and polling intervals can greatly affect the efficiency of business object transmission from an EIS across a adapter .

Currently users set the poll quantity and poll frequency based on trial and error method as there is no system/method available which considers the consumption of the available resources (memory and processor) and the success and failures of the events processed in a given cycle. Thus the optimum poll quantity and poll frequency parameters are essential to get the best through-put from the software component for the given and available system resources.

The article discloses an approach to im...