e-commerce-middleware

1. Presented by
Mr. Manish Tripathi ( I – 15-18-19)
Thakur Institute of Management Studies
&
Research
(Sunday 19 March, 2017)
1

2. WHAT IS MIDDLEWARE?
• Software that facilitates exchange of data between
two application programs within the same
environment, or across different hardware and
network environments
• The term is most commonly used for software that
enables communication and management of data
in distributed applications
• Those services found above the transport layer set
of services but below the application environment
• In this more specific sense middleware can be
described as the dash (“-”) in client-server, or the -
to- in peer-to-peer
2

3. Message-Oriented Middleware
3

4. Three Categories of Basic Middleware 4

5. KEY FEATURES OF MIDDLEWARE
• It provides services beyond those provided by the
operating system
• Middleware often enables interoperability between
applications that run on different operating systems,
by supplying services so the application can exchange
data in a standards-based way
• It is a layer between two systems that makes it easy for
the two to communicate and is considered the glue
that holds together applications, making seamless
connectivity possible without requiring the two
applications to communicate directly
5

6. TYPES OF MIDDLEWARE
6

7. RPCS (REMOTE PROCEDURE CALL) MIDDLEWARE
• The oldest type of middleware and it is
client/server based
• One client can request a service from a program
located in another computer in a network without
having to understand network details
• RPCs are synchronous; they are labelled as
“blocking middleware” because the requesting
program is suspended until the results of the
remote procedure are returned
• As the RPC’s use a point-to-point communication,
they are not scalable and consume a vast amount
of resources during they processing
• Not a viable solution in scenarios where there are
many applications requiring integration. 7

8. RPCS (REMOTE PROCEDURE CALL) MIDDLEWARE
8

9. MOM (MESSAGE ORIENTED MIDDLEWARE)
• MOM is a type of middleware that uses
messages as the method of integration
• In MOM the applications are decoupled. Sender and
receivers are never aware of each other; instead they
send and receive the messages from the messaging
system. It is the responsibility of the MOM to get the
messages to their destinations
• The messaging system uses channels that the
applications can recognize and the messages can be
sent and received asynchronously
• The asynchronous paradigm allows the application to
continue functioning after sending a request, so if the
message is taking too much time it is possible to
process other messages while is waiting, they can deal
with down connections and queue messages until it’s
viable to deliver them
9

10. MOM (MESSAGE ORIENTED MIDDLEWARE)
10

11. DISTRIBUTED OBJECTS
• Distributed objects are small applications that use
standard interfaces and protocols to communicate
with one another
• Because they are built over standards, two
compliant objects should be able to exchange
information and carry out application functions by
invoking each other methods
• Two important distributed objects specifications
exist:
1. CORBA (Common Object Request Broker
Architecture) Sun / Java
2. DCOM (Distributed Component Object Model)
Microsoft
11

12. CORBA
12

13. DCOM
13

14. DATABASE MIDDLEWARE
• Database middleware allows communications with a
database from an application or between databases
• It is used to extract information from either local or
remote databases
• It works with two database types
1. CLIs (Call level interfaces)
CLIs provide access to any number of relational databases
through a common interface
2. At-native database middleware
Native database middleware uses the features and
functions of a particular data base, using only native
mechanisms. Although only communicate with one
database, it has as advantages, improved performance
and access to all low features of a particular type of
database
14

15. Database Middleware
15

16. TRANSACTION PROCESSING MONITORS
• They are a type of middleware that preserves the
integrity of a transaction.
• TP Monitors support features such rollback,
failover, auto restart, error logging and replication
to eliminate single points of failure
• They provide a location for application logic in
addition to communication between two or more
applications
16

17. Transaction Processing Monitors
Middleware 17

18. MIDDLEWARE PRODUCTS
• BizTalk Server : Microsoft
• Informatica Power Center : Informatica
• IBM Integration Bus (formerly WebSphere
Message Broker ) : IBM
• JBoss Enterprise Service Bus (ESB) : Red Hat
• Oracle Enterprise Service Bus: Oracle
• SAP NetWeaver Process Integration : SAP
• Sun Java Composite Application Platform Suite :
Sun Microsystem
• Apache Camel : Apache Software Foundation
18

19. 19

20. 20