Title of the Project: - Enterprise Service Bus

Team Members: -

No. Name Roll No.

1. Vineet Varghese 4274
2. Tushar Ralebhat 4257
3. Ankur Gautam 4204

Date of synopsis submission : -27/10/10

Project type (Area of project) : - Networking.

Sponsored : - No

Whether Company is providing you

1. Machines : Yes
2. Software : Yes
3. Guidance : Yes

Description of problem:-

a. Problem Statement: -
Enterprise Service Bus based Unified Information Management & Messaging
Service

b. Introduction: -
Information management is one of the key areas where companies are focusing
nowadays to make their enterprises more intelligent. However, the information itself
comes in various formats and sources and having a unified interface for its management
and consumption becomes very important. This project involves setup of ESB Based
infrastructure to provide information management capabilities to an enterprise.
Enterprise service bus (ESB) consists of a software architecture construct which
provides fundamental services for complex architectures via an event-driven and
standards-based messaging-engine (the bus).Developers typically implement an ESB
using technologies found in a category of middleware infrastructure products,
usually based on recognized standards.
ESB Architecture :

An ESB is expected to exhibit the following characteristics:

• General agnosticism to operating-systems and programming-languages; for example, it
should enable interoperability between Java and .NET applications
• General use of XML as the standard communication language
• Support for web-services standards
• Support for various MEPs (Message Exchange Patterns) (for example: synchronous
request/response, asynchronous request/response, send-and-forget, publish/subscribe)
• Adapters for supporting integration with legacy systems, possibly based on standards
such as JCA
• A standardized security-model to authorize, authenticate and audit use of the ESB
• Facilitation of the transformation of data formats and values, including transformation
services (often via XSLT or XQuery) between the formats of the sending application and
the receiving application
• Validation against schemas for sending and receiving messages
• The ability to apply business rules uniformly
• Enriching messages from other sources
• The splitting and combining of multiple messages and the handling of exceptions
• The provision of a unified abstraction across multiple layer
• Routing or transforming messages conditionally, based on a non-centralized policy
(without the need for a central rules-engine) queuing, holding messages if applications
temporarily become unavailable
Mule ESB is a lightweight Java-based enterprise service bus (ESB) and
integration platform that allows developers to connect applications together quickly and
easily, enabling them to exchange data. Mule ESB enables easy integration of existing
systems, regardless of the different technologies that the applications use, including
JMS, W Services, JDBC, HTTP, and more.

c. Objective: -
To enable communication between various applications via ESB so that there are no
conflicts , promote flexibility and enable loose coupling and easy connection between
services.

d. Scope: -
• Setup of ESB based Infrastructure using Mule ESB platform
• Design and Implementation of Web Services based Information access to Business
Centric
• Application providing the following
o Master Customer Information
o Employee Information from Open LDAP exposed as Web Service
o Blended, Onsite, Offshore Rate Management
 o Quotation Management End Points
o Software Documentation templates
o Technology Assessment and Case Studies
o Effort Calculation Services
o Approval Services
o Unified communication services supporting Email and SMS
• Design and development of a Front End Portal to show interaction between the Web
Tier and
• the ESB Tier using Mule ESB
• Integration of Mule ESB platform with the following Technologies
o Axis Web Services: Allows Mule managed components to be published as Axis
services
and allows components to invoke web services using Axis client calls. Includes a
WSDL
connector that invokes remote web services by obtaining the service WSDL.
o Email Transport – (SMTP/POP3/IMAP): This transport supplies various email
connectivity options.
o FTP Transport: Allows files to be read / written to a remote FTP server.
o HTTP Transport: This transport supplies HTTP transport of Mule messages
between
applications and other Mule servers.
o LDAP Transport: Allows you to send and receive Mule Messages to/from an
LDAP
directory.
o TCP Transport: Enables events to be sent and received over TCP sockets.
o UDP Transport: Enables events to be sent and received as datagram packets.
o RMI Transport: Enables events to be sent and received over RMI via JRMP.
o EJB Transport: Allows EJB invocations to be made using outbound endpoints.
o JMS Transport: A Mule transport for JMS connectivity. Mule itself is not a JMS
server
but can use the services of any JMS 1.1 or 1.02b compliant server such as ActiveMQ
and
OpenJms, and commercial vendors such as Weblogic, SonicMQ, and more.
• Integration of Rich Internet Clients with Web Services Infrastructure
• Unified access to Data, Business Logic and JSON based Presentations
• JMS Messaging and EJB Interactions
• Authentication and Authorization

e. System Requirements:-
• Mule ESB 2.2.1 Community Edition
• Java/J2EE – JSP Servlets, EJB, JMS
• JBoss Application Server
• Java Mail
• Open LDAP Server