Nothing Special   »   [go: up one dir, main page]

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 2

webMethods

webMethods is a company that specializes in business process integration software for the enterprise.
The company's flagship product suite, provides an integrated platform that includes both service-
oriented architecture (SOA) and business process management (BPM). The webMethods Fabric suite is
used by 1,500 customers around the globe.

Overview of EAI
---------------------
Enterprise application integration is an integration framework composed of a collection of technologies
and services which form a middleware or "middleware framework" to enable integration of systems and
applications across an enterprise.
Many types of business software such as supply chain
management applications, ERP systems, CRM applications for managing customers, business
intelligence applications, payroll and human resources systems typically cannot communicate with one
another in order to share data or business rules. For this reason, such applications are sometimes
referred to as islands of automation or information silos. This lack of communication leads to
inefficiencies, wherein identical data are stored in multiple locations, or straightforward processes are
unable to be automated.
Enterprise application integration is the process of linking such applications within a single organization
together in order to simplify and automate business processes to the greatest extent possible, while at the
same time avoiding having to make sweeping changes to the existing applications or data structures.
Applications can be linked either at the back-end via APIs or (seldomly) the front-end (GUI).

Topologies
----------------------
There are two major topologies:-- hub-and-spoke, and bus.
In the hub-and-spoke model, the EAI system is at the center (the hub), and interacts with the
applications via the spokes.
In the bus model, the EAI system is the bus (or is implemented as a resident module in an already
existing message bus or message-oriented middleware).

Application connectivity
The bus/hub connects to applications through a set of adapters (also referred to as connectors). These
are programs that know how to interact with an underlying business application. The adapter performs
two-way communication, performing requests from the hub against the application, and notifying the hub
when an event of interest occurs in the application (a new record inserted, a transaction completed, etc.).
Adapters can be specific to an application (e. g., built against the application vendor's client libraries) or
specific to a class of applications (e. g., can interact with any application through a standard
communication protocol, such as SOAP, SMTP or Action Message Format (AMF)). The adapter could
reside in the same process space as the bus/hub or execute in a remote location and interact with the
hub/bus through industry standard protocols such as message queues, web services, or even use a
proprietary protocol. In the Java world, standards such as JCA allow adapters to be created in a vendor-
neutral manner.

Integration modules
An EAI system could be participating in multiple concurrent integration operations at any given time,
each type of integration being processed by a different integration module. Integration modules
subscribe to events of specific types and process notifications that they receive when these events
occur. These modules could be implemented in different ways: on Java-based EAI systems, these
could be web applications or EJBs or even POJOs that conform to the EAI system's specifications.

You might also like