Enterprise Service Bus Based Application



Increasing organizational agility by reducing time to market for new initiatives is one of the most common reasons that companies implement an ESB as the backbone of their IT infrastructure. An ESB architecture facilitates this by providing a simple, well defined, "pluggable" system that scales really well. Additionally, an ESB provides a way to leverage your existing systems and expose them to new applications using its communication and transformation capabilities. Nucsoft has a rich experience in doing ESB based implementations for its Clients using Open Source platforms like Mule ESB and WSO2 ESB.


Mule ESB:
Mule is a lightweight enterprise service bus (ESB) and integration framework provided by MuleSoft. The platform is Java-based, but can broker interactions between other platforms such as .NET using web services or sockets. The architecture is a scalable, distributable object broker that can handle interactions across legacy systems, in-house applications, and almost all modern transports and protocols.

WSO2 ESB:
WSO2 is an Open-Source technology platform for integrating application programming interfaces (APIs), applications, and web services locally and across the Internet.


Key Features of ESB:

  • Transformation:The ability of the ESB to convert messages into a format that is usable by the consumer application.
  • Protocol Conversion:Similar to the transformation requirement, the ESB must be able to accept messages sent in all major protocols, and convert them to the format required by the end consumer. 
  • Routing: The ability to determine the appropriate end consumer or consumers based on both pre-configured rules and dynamically created requests.
  • Enhancement: The ability to retrieve missing data in incoming messages, based on the existing message data, and append it to the message before delivery to its final destination.
  • Monitoring / Administration: The goal of ESB is to make integration a simple task.  As such, an ESB must provide an easy method of monitoring the performance of the system, the flow of messages through the ESB architecture, and a simple means of managing the system in order to deliver its proposed value to an infrastructure.
  • Security: ESB security involves two main components - making sure the ESB itself handles messages in a fully secure manner, and negotiating between the security assurance systems used by each of the systems that will be integrated.

Benefits of ESB :

  • Helps in Lightweight:Because an ESB is made up of many interoperating services, rather than a single hub that contains every possible service, ESBs can be as heavy or light as an organization needs them to be, making them the most efficient integration solution available.
  • Easy to expand:If an organization knows that they will need to connect additional applications or systems to their architecture in the future, an ESB allows them to integrate their systems right away, instead of worrying about whether or not a new system will not work with their existing infrastructure.  When the new application is ready, all they need to do to get it working with the rest of their infrastructure is hook it up to the bus.
  • Scalable and Distributable: Unlike broker architectures, ESB functionality can easily be dispersed across a geographically distributed network as needed.  Additionally, because individual components are used to offer each feature, it is much simpler and cost-effective to ensure high availability and scalability for critical parts of the architecture when using an ESB solution.
  • SOA-Friendly: ESBs are built with Service Oriented Architecture in mind.  This means that an organization seeking to migrate towards an SOA can do so incrementally, continuing to use their existing systems while plugging in re-usable services as they implement them.
  • Incremental Adoption: At first glance, the number of features offered by the best ESBs can seem intimidating.  However, it's best to think of the ESB as an integration "platform", of which you only need to use the components that meet your current integration needs.  The large number of modular components offers unrivalled flexibility that allows incremental adoption of an integration architecture as the resources become available, while guaranteeing that unexpected needs in the future will not prevent ROI.

  • For YES Bank:
  • 1.International E-Remittance (Mule ESB):
    End to end System Integration between Exchange House and Beneficiary Bank for remittance processing.

    2.E-collect -Utility Payments (Java - Mule ESB) / E-collect Dealer Payments (Java -Mule ESB):
    Solution provided to corporate customers who have a business model to collect funds through electronics channels namely NEFT / RTGS. Corporate can use the electronic collection modes along with proper MIS and validation.

    3.E-Payments Payroll Payments (Java - Mule ESB) / E-Payments Vendor Payments (Java - Mule ESB):
    Solution provided to corporate customer which processes Vendor/Employee payment postings done in their core system and to be sent to Bank’s CBS for payment processing. The financial Documents posted are specific to E- Payments (RTGS / NEFT / A2A) only.

  • For SBI DFHI Limited:
  • Systems Integration Project (WSO2 ESB):
    Nucsoft has done Systems integration of their various systems like ERP, CRM, Deal Terminals and Digital Signature.

  • For L&T Finance
  • Intranet Portal for Employees