Home | About Infosytech | Infosytech News | Innovation | Clients | Careers
Facebook Twitter Google+ Linkedin Skype Youtube
Banner
Home » Products

TIBCO Common Services Framework

ESB Common Services is a collection of services that would provide integration application related cross-cutting functionalities to promote reusability and standardization.

Currently, ESB Common Services provide logging, auditing and exception management services for Integration Applications as illustrated in the figure below.

ESB

Various direct as well as indirect benefits of using ESB Common Services and Components:

  • Standardized reusable common functionality
  • End-to-end integration transaction visibility
  • Platform decoupling through standardized exceptions
  • Production support scalability
  • Quality and service level agreement monitoring through business intelligence

ESB Common Services are runtime services that can be used by any consumer. In order to simplify the usage from an integration application development perspective, ESB Common Component provides an abstraction of these services to simplify and standardize the implementation of integration applications. In addition, ESB Common Component provide common functions such as UUID generation, exception categorization mappings caching, job level shared variable such as transaction id etc. to simplify and standardize the implementation of integration applications.

ESB Common Services provides logging, auditing, managing exceptions and reporting services for integration applications.

Logging and Auditing Service

The Logging and Auditing Service provides operations for application endpoints to log and audit their runtime contextual information (i.e. the application runtime state) specific to an integration transaction and its activities such as create customer transaction or update account transaction.

Logging operation supports four levels: Trace, Debug, Warning and Error. For tracing purposes, the application endpoints are required to log the execution context and a log message describing the context. The execution context is formally defined and described in the messaging specification and suffice it to say that it is a set of values that uniquely identify the running transaction and the application within which it is running.

For debugging purposes, application endpoints are required to log the execution context, along with message payload, transport headers and the log message.

For warning and error levels, application endpoints are required to log the execution context, along with exception context, message payload, transport headers and the log message.

Auditing operation provides the capability to audit the message that has initiated the integration transaction, the details of the interacting parties and the transaction outcome along with its contextual information. The purpose of a specific audit can be described using the ‘Audit Code’ and ‘Audit Message’.

Both log and audit interface operations are defined using one-way interaction pattern and hence can be invoked using asynchronous messaging transports such as JMS. The messaging structure of log and audit interfaces is defined using XSD.

Exception Management Service

The exception management service translates infrastructure and application specific exception messages into a well-defined, user-friendly, canonicalized exception messages based on the pre-defined maps. Specifically, the exception management service provides the following features:

  • The capability to translate an exception into a canonical form based on the exception classification and categorization mappings during runtime
  • The capability to load the exception categorization mappings to support unidentified exceptions at runtime
  • The capability to log and audit the exceptions based on the integration application specific exception management policy data
  • The capability to send meaningful alerts to/through HP OpenView for manual handling and visibility purposes based on the integration application specific exception management policy data
  • The capability to provide the categorization mappings for client caching purposes.

Once the execution context along with the exception context is provided, the exception management service will lookup and respond with the exception details based on the integration application specific data and the categorized exception mappings.

The lookup interface operation is a request-response interaction pattern and the interface includes the request and response messaging structures defined using XSD. The manage exception operation is provided by the exception management service as a one-way interaction pattern for logging, auditing and alerting exceptions.

Clients