Section: BS in Information Technology - 4A

Day: Thursday
Time: 5:00-8:00
SYSTEM INTEGRATION ARCHITECTURE:
• The Systems Integration Architecture provides a bridge between the
heterogeneous operational applications and platforms.
• This architecture ties together the mix of platforms, operating systems,
transports, and applications. Integration of business applications
between agencies and vendors or other agencies supports electronic
commerce.
• This Architecture encompasses the multiple layers of new and existing
systems and the middle ware in between.
• Systems Integration Architecture enables new applications to use
existing resources with minimal disruption
NEW APPLICATIONS TO USE EXISTING
RESOURCES WITH MINIMAL DISRUPTION :
• Application Communication Middleware
• Application Integration
• Data Access Integration
• Electronic Data Interchange (EDI)
• Electronic Payment
• Host Printing
• Terminal Access and Integration
APPLICATION COMMUNICATION MIDDLEWARE:
• Middleware speeds development of distributed applications by simplifying
connectivity between applications, application components and back-end
data sources.
• Middleware is software that enables one or more kinds of communication or
connectivity between two or more applications or application components in
a distributed network.
• By making it easier to connect applications that weren't designed to connect
with one another - and providing functionality to connect them in intelligent
ways - middleware streamlines application development and speeds time to
market.
APPLICATION COMMUNICATION MIDDLEWARE:
• There are many types of middleware. Some, such as message brokers or
transaction processing monitors, focus on one type of communication.
• Others, such as web application servers or mobile device middleware,
provide the full range of communication and connectivity capabilities
needed to build a particular type of application.
• Still others, such as a cloud-based integration platform as a service
(iPaaS) offering or an enterprise service bus (EBS), function as a centralized
integration hub for connecting all the components in an enterprise.
• (There's even middleware that lets developers build their own customized
middleware.)
APPLICATION COMMUNICATION MIDDLEWARE:
• Middleware got its name because the first middleware typically acted as a
mediator between an application front-end, or client, and a back-end
resource - e.g., a database, mainframe application or specialized hardware
device - from which the client might request data.
• But today's middleware operates well beyond this scope. Portal middleware,
for example, encompasses the application front-end as well as tools for
back-end connectivity; database middleware typically includes its own data
store. And as you'll read below, an emerging class of middleware leverages
container technology to help developers connect to resources distributed
across multiple clouds.
TYPES OF MIDDLEWARE:
• Message-oriented middleware (MOM) enables application components using
different messaging protocols to communicate to exchange messages. In
addition to translating - or transforming - messages between applications,
MOM manages routing of the messages so they always get to the proper
components in the in the proper order. Examples of MOM include message
queues and message brokers.
• Remote procedure call (RPC) middleware enables one application to trigger a
procedure in another application - running on the same computer or on a
different computer or network - as if both were part of the same application
on the same computer.
TYPES OF MIDDLEWARE:
• Data or database middleware simplifies access to, and interaction with, back-
end databases. Typically database middleware is some form of SQL database
server.
• API (application programming interface) middleware provides tools
developers can use to create, expose and manage APIs for their applications
- so that other developers can connect to them. Some
API middleware includes tools for monetizing APIs - enabling other
organizations to use them, at cost. Examples of API middleware include API
management platforms, API gateways and API developer portals.
TYPES OF MIDDLEWARE:
• Object request broker (ORB) middleware acts as broker between a request
from one application object or component, and the fulfillment of that
request by another object or component on the distributed network. ORBs
operate with the Common Object Request Broker Architecture (CORBA),
which enables one software component to make a request of another
without knowing where other is hosted, or what its UI looks like.
• Transactional middleware provides services to support the execution of data
transactions across a distributed network. The best-known transactional
middleware are transaction processing monitors (TPMs), which ensure that
transactions proceed from one step to the next - executing the data
exchange, adding/changing/deleting data where needed, etc. - through to
completion.
TYPES OF MIDDLEWARE:
• Asynchronous data streaming middleware replicates a data stream in an
intermediate store, enabling data sharing between multiple
applications. Apache Kafka is one of the best-known examples of
middleware for real-time data streaming.
• Device middleware provides a focused set of integration and
connectivity capabilities for developing apps for a specific mobile OS.
• Portal middleware provides tools and resources for integrating content and
capabilities from various related applications 'at the glass' - or on a single
screen - to create a single, composite application.
• Robotics middleware simplifies the process of integrating robotic hardware,
firmware and software from multiple manufacturers and locations.
APPLICATION INTEGRATION:
• Application integration enables applications and systems that were built separately
to work together, resulting in new capabilities and efficiencies that cut costs,
uncover insights, and much more.
• Application integration is the process of enabling individual applications—each
designed for its own specific purpose—to work with one another. By merging and
optimizing data and workflows between multiple software applications,
organizations can achieve integrations that modernize their infrastructures and
support agile business operations.
• Application integration helps bridge the gap between existing on-premises systems
and fast-evolving cloud-based enterprise applications. Through seamlessly
interconnected processes and data exchanges, application integration allows
enterprises to orchestrate a variety of functions across their entire infrastructures,
enabling businesses to operate more effectively and efficiently.
APPLICATION INTEGRATION CONCEPTS:
When an organization considers moving forward with application
integration, there are various components required to orchestrate
processes between two or more applications successfully.
APPLICATION INTEGRATION CONCEPTS:
• Application Programming Interface (API) - An API is a set of functions and
procedures that specify how software components should interact. They
allow developers to easily and quickly access the functionality of other
software through well-defined data structures and have, as a result, become
a popular way of integrating applications, data, and services, in recent years.
• Events and actions - An event is an occurrence in your connected
applications—such as a payment being received. An event then triggers
an action or series of actions, which can include standard functionality—like
creating, retrieving, or updating datasets—and be application-specific—such
as a new case being creating in Salesforce.
APPLICATION INTEGRATION CONCEPTS:
• Data mapping - Data mapping specifies the information exchange that's to
be used. For example, when you complete and submit contact forms in one
application, this event can trigger actions that map those form fields to
other corresponding datasets on other applications, categorizing the
information entered into first name, last name, status, etc. This simplifies the
process of exporting data for easier grouping and analysis
APPLICATION INTEGRATION USE CASES:
As more and more organizations concentrate on deploying agile integration
strategies, modernizing legacy systems is a primary focus. Industry-specific
examples include the following:
• Banking: By integrating customer accounts, loan applications services, and
other back-end systems with their mobile app, a bank can provide services
via a new digital channel and appeal to new customers.
• Manufacturing: Factories use hundreds or even thousands of devices to
monitor all aspects of the production line. By connecting the devices to
other systems (e.g., parts inventories, scheduling applications, systems that
control the manufacturing environment), manufacturers can uncover insights
that help them identify production problems and better balance quality,
cost, and throughput.
APPLICATION INTEGRATION USE CASES:
• Healthcare: By integrating a hospital patient’s record with an electronic
health record (EHR) system, anyone who treats the patient has access to the
patient’s history, treatments, and records from the primary care physician
and specialists, insurance providers, and more. As the patient moves through
different areas of the hospital, the relevant caregivers can easily access the
information they need to treat the patient most effectively.
DATA ACCESS INTEGRATION :
• Data integration is the practice of consolidating data from disparate sources
into a single dataset with the ultimate goal of providing users with
consistent access and delivery of data across the spectrum of subjects and
structure types, and to meet the information needs of all applications and
business processes.
• Data integration is a process in which heterogeneous data is retrieved and
combined as an incorporated form and structure. Data integration allows
different data types (such as data sets, documents and tables) to be merged
by users, organizations and applications, for use as personal or business
processes and/or functions.
DATA ACCESS INTEGRATION :
• Data integration is the process of taking data from multiple, disparate
internal and external sources and putting it in a single location (e.g., a data
warehouse) to achieve a unified view of collected data.
DATA ACCESS INTEGRATION :
So, why does anyone need to integrate data in the first place?
Today, companies want their business decisions to be driven by data. But
here’s the thing — information required for business intelligence (BI) and
analytics processes often lives in a range of databases and applications.
These systems can be hosted on-premises, in the cloud, and
on IoT devices, etc.
Logically, each system stores information differently: in structured,
unstructured, and semi-structured formats. With the right data integration
strategy, companies can consolidate the needed data into a single place
and ensure its integrity and quality for better and more reliable insights.
DATA ACCESS INTEGRATION SCENARIO :
Let’s imagine you run an eCommerce business and you want to build a
predictive propensity model to calculate customer lifetime value. For this
purpose, you will need a range of customer data.
The problem is, the information you have is scattered across different systems
isolated from one another including :
• CRM with customer and sales data,
• POS with customer purchase history, and
• Google Analytics with website traffic and user flow analytics data, to name a
few.
DATA ACCESS INTEGRATION SCENARIO :
So, each of these systems contains information related to the specific
operations of the company. You need all this data, some fragments of which
are locked in silos in separate databases only certain groups of people have
access to. This is something known as the “data silo problem,” meaning no
team or department has a unified view of data. And without it, you will not be
able to build accurate predictions.
HOW DOES DATA ACCESS INTEGRATION WORK :
The one-size-fits-all approach to data integration doesn’t exist. At the same
time, there are a few typical elements involved in an integration process. They
are a set of disconnected data sources, clients, and a master server that
provides a unified viewpoint on all data.
HOW DOES DATA ACCESS INTEGRATION WORK :
• The common case involves the client sending a data request to the master
server.
• The server then pulls out the requested data from internal and external
sources and unifies it into a cohesive view, which is eventually delivered back
to the client.
• An important part of data integration is the ETL process that consists of
the extract, transform, and load steps.
• With it, data is retrieved from its sources, migrated to a staging data
repository where it undergoes cleaning and conversion to be further loaded
into a target source (commonly data warehouses or data marts).
REFERENCES:
• SYSTEM INTEGRATION & ARCHITECTURE, Mr. Mubashir Ali
Lecturer(Dept. of Computer Science) dr.mubashirali1@gmail.com
• https://www.ibm.com/cloud/learn/middleware
• https://www.ibm.com/cloud/learn/application-integration
• https://www.coursehero.com/file/63381843/INTRODUCTION-TO-
SYSTEM-INTEGRATION-AND-ARCHITECTUREdocx/
• https://dts.utah.gov/standard/systems-integration-architecture
• https://www.altexsoft.com/blog/data-integration/