![1
Integration of Legacy Application with Modern J2EE Application using
Service oriented architecture (SOA)
By
Shuaibullah abbasi
Courtesy by IBM [1]](https://image.slidesharecdn.com/cecc9263-a774-4755-b7fe-e9a674bc3883-160426072625/85/integeration-1-320.jpg)
![3
1. Introduction
1.1 Service-oriented architecture (SOA) definition
A service-oriented architecture is essentially a collection of services. These services
communicate with each other. The communication can involve either simple data passing or
it could involve two or more services coordinating some activity. Some means of connecting
services to each other is needed.
1.2 WebSphere Message Broker
WebSphere Message Broker is a powerful information broker that allows both business data
and information, in the form of messages, to flow between disparate applications and across
multiple hardware and software platforms. Business rules can be applied to the data that is
flowing through the message broker in order to route, store, retrieve, and transform the
information [2].
1.3 Application integration and WebSphere Message Broker
Application integration, at a high level, refers to solutions that are implemented to integrate
software applications within and between organizations. Historically, application integration
has been concerned with the integration of legacy software applications, such as between
different departments and divisions within companies, or new acquisitions. Within an
organization, these applications often vary considerably across departments, exist on
different platforms, are written in different programming languages, and use different data
formats. Integrating the applications is a more practical and cost effective solution than the
alternative of re-writing the existing applications. WebSphere Message Broker is used in the
implementation of application integration architecture because it provides a mechanism for
connecting, routing, and transforming business data from a variety of transports without any
need to change the underlying applications generating the data. Websphere Message Broker
enhances the flow and distribution of information by enabling the transformation and
intelligent routing of messages without the need to change either the applications that are
generating the messages or the applications that are consuming them. In WebSphere
Message Broker, connectivity is provided by applications that communicate by sending and
receiving messages. WebSphere Message Broker also has the following key capabilities that
make it a valuable solution for business integration:
• Distributes any type of information across and between multiple diverse systems and
applications, providing delivery of the correct information in the correct format and
at the correct time.
• Reduces the number of point-to-point interconnections and simplifies application
programming by removing integration logic from the applications Routes
information in real time based on topic and content to any endpoint using a powerful
publish/subscribe messaging engine
• Validates and transforms messages in-flight between any combination of different
message formats, including Web Services, and other XML and non-XML formats
• Routes messages based on (evaluated) business rules to match information content
and business processes](https://image.slidesharecdn.com/cecc9263-a774-4755-b7fe-e9a674bc3883-160426072625/85/integeration-3-320.jpg)
![4
• Improves business agility by dynamically reconfiguring information distribution
patterns without reprogramming end-point applications
• Access control to securely deliver personalized information to the right place at the
right time[2]
1.4 Introduction to Message Queuing
Message queuing allows distributed applications to communicate asynchronously by
sending messages between the applications. The messages from the sending application are
stored in a queue and are retrieved by the receiving application. The applications send or
receive messages through a queue by sending a request to the message queuing system.
Sending and receiving applications can use the same message queuing system or different
ones, allowing the message queuing system to handle the forwarding of the messages from
the sender queue to the recipient queue.
Queued messages can be stored at intermediate nodes until the system is ready to forward
them to the next node. At the destination node, the messages are stored in a queue until the
receiving application retrieves them from the queue. Message delivery is guaranteed even if
the network or application fails. This provides for a reliable communication channel
between the applications.
The complexity and details of the underlying model (to store and forward messages between
different environments) are handled by the message queuing system. By maintaining this
level of abstraction, distributed applications can be developed without the need to worry
about the details of how the information is transported.
Because the sending and receiving applications operate independently of one another, the
ending application is less dependent on the availability of the remote application, less
dependent on the network between them, and less dependent on the computer system on
which the receiving application runs. This leads to a higher level of availability for the
participating applications.
Messages and message queue operations can be configured by the applications to operate in
specific modes. For example, a sending application can specify that queued messages should
survive system crashes.w As another example, the receiving application can specify a
maximum waiting period for a receiving operation from a queue (in case no messages are
available yet on the receiving queue). [3]
1.5 IBM Websphere Portal Server](https://image.slidesharecdn.com/cecc9263-a774-4755-b7fe-e9a674bc3883-160426072625/85/integeration-4-320.jpg)
![6
• Enhance B to B or partner and supplier communication
• Streamline Business Control or Business Management processes
WebSphere Portal (Portal for short) supports multiple industry portals and various
communities within a company. Portal consists of four basic services: Framework,
Integration, Content, and Collaboration Figure 1-2 illustrate the IBM WebSphere Portal
framework [4].
Figure 1.2 IBM WebSphere Portal framework courtesy by Bernhard Stimpfle, Jeanette Coury, and Rufus Credle](https://image.slidesharecdn.com/cecc9263-a774-4755-b7fe-e9a674bc3883-160426072625/85/integeration-6-320.jpg)
Ad
More Related Content
What's hot (19)
Viewers also liked (9)
Ad
Similar to integeration (20)
Ad
integeration
- 1. 1 Integration of Legacy Application with Modern J2EE Application using Service oriented architecture (SOA) By Shuaibullah abbasi Courtesy by IBM [1]
- 2. 2 Abstract Service oriented architecture (SOA) is an approach for building distributed systems that deliver application functionality as a set of self-contained business-aligned services. It promises lower integration costs, increased reusability and improved enterprise agility and adaptability. One of the key obstacles for SOA is the presence of existing legacy applications that support critical business processes but are inflexible and hard to adapt for integration with modern business applications. This research presents a survey of key approaches to integrate/transform legacy applications into modern enterprise applications. It also presents a decision framework to guide architects in selecting the optimal combination of legacy modernization options. Application: E-banking solutions. Tools: IBM Websphere Application server, IBM Websphere Message Queue, IBM Websphere Message Broker and IBM Websphere Portal Server.
- 3. 3 1. Introduction 1.1 Service-oriented architecture (SOA) definition A service-oriented architecture is essentially a collection of services. These services communicate with each other. The communication can involve either simple data passing or it could involve two or more services coordinating some activity. Some means of connecting services to each other is needed. 1.2 WebSphere Message Broker WebSphere Message Broker is a powerful information broker that allows both business data and information, in the form of messages, to flow between disparate applications and across multiple hardware and software platforms. Business rules can be applied to the data that is flowing through the message broker in order to route, store, retrieve, and transform the information [2]. 1.3 Application integration and WebSphere Message Broker Application integration, at a high level, refers to solutions that are implemented to integrate software applications within and between organizations. Historically, application integration has been concerned with the integration of legacy software applications, such as between different departments and divisions within companies, or new acquisitions. Within an organization, these applications often vary considerably across departments, exist on different platforms, are written in different programming languages, and use different data formats. Integrating the applications is a more practical and cost effective solution than the alternative of re-writing the existing applications. WebSphere Message Broker is used in the implementation of application integration architecture because it provides a mechanism for connecting, routing, and transforming business data from a variety of transports without any need to change the underlying applications generating the data. Websphere Message Broker enhances the flow and distribution of information by enabling the transformation and intelligent routing of messages without the need to change either the applications that are generating the messages or the applications that are consuming them. In WebSphere Message Broker, connectivity is provided by applications that communicate by sending and receiving messages. WebSphere Message Broker also has the following key capabilities that make it a valuable solution for business integration: • Distributes any type of information across and between multiple diverse systems and applications, providing delivery of the correct information in the correct format and at the correct time. • Reduces the number of point-to-point interconnections and simplifies application programming by removing integration logic from the applications Routes information in real time based on topic and content to any endpoint using a powerful publish/subscribe messaging engine • Validates and transforms messages in-flight between any combination of different message formats, including Web Services, and other XML and non-XML formats • Routes messages based on (evaluated) business rules to match information content and business processes
- 4. 4 • Improves business agility by dynamically reconfiguring information distribution patterns without reprogramming end-point applications • Access control to securely deliver personalized information to the right place at the right time[2] 1.4 Introduction to Message Queuing Message queuing allows distributed applications to communicate asynchronously by sending messages between the applications. The messages from the sending application are stored in a queue and are retrieved by the receiving application. The applications send or receive messages through a queue by sending a request to the message queuing system. Sending and receiving applications can use the same message queuing system or different ones, allowing the message queuing system to handle the forwarding of the messages from the sender queue to the recipient queue. Queued messages can be stored at intermediate nodes until the system is ready to forward them to the next node. At the destination node, the messages are stored in a queue until the receiving application retrieves them from the queue. Message delivery is guaranteed even if the network or application fails. This provides for a reliable communication channel between the applications. The complexity and details of the underlying model (to store and forward messages between different environments) are handled by the message queuing system. By maintaining this level of abstraction, distributed applications can be developed without the need to worry about the details of how the information is transported. Because the sending and receiving applications operate independently of one another, the ending application is less dependent on the availability of the remote application, less dependent on the network between them, and less dependent on the computer system on which the receiving application runs. This leads to a higher level of availability for the participating applications. Messages and message queue operations can be configured by the applications to operate in specific modes. For example, a sending application can specify that queued messages should survive system crashes.w As another example, the receiving application can specify a maximum waiting period for a receiving operation from a queue (in case no messages are available yet on the receiving queue). [3] 1.5 IBM Websphere Portal Server
- 5. 5 A portal offers a single point of personalized, unified access to applications, content, processes, and people. A portal delivers integrated content and applications, plus offers a unified, collaborative workplace. A portal also provides other valuable functions such as security, search, and workflow. A portal is an open, standards-based framework supporting a wide array of options across databases, directories, platforms, and security. Portals are the next-generation desktop, delivering e-business applications over the Web to many different client devices. Portals are designed to meet the needs of all enterprises, from small and medium businesses to the largest enterprises that demand the most scalable, secure, and robust infrastructure. A consistent, integrated user experience is achieved by portals that do not only aggregate components into a single view, but in addition allow integration of these components within the context. This is often called integration on the glass, because all the applications are integrated in context by the portal into one single window on the monitor of the portal end user. This is a very powerful concept that in today’s world of widely fractured IT infrastructures enables the delivery of consistent and integrated views on multiple IT services. Integration on the glass improves the user experience and productivity of the IT user; instead of dealing with different IT systems with potential different user interfaces, integration on the glass provides a single, consistent view. In addition to contextual integration capabilities, portals can provide rich programming frameworks for building user interfaces for component-oriented applications in service- oriented architectures. Service-oriented architecture (SOA) is an approach for building distributed systems that deliver application functionality as services to either end-user applications or other services. SOA provides means to integrate and manage these different services. For more information, refer to the following Web page: http://www.ibm.com/SOA Portals provide first-class user interface (UI) support in service-oriented architectures. Portlets, their basic building block, let developers focus on unique aspects of their application, while the middleware handles common functions for life cycle, per-user customization, aggregation, and integration with other components. In addition, portals might provide valuable service functions such as security, search, collaboration, and workflow. Portals provide the ability to aggregate and integrate the UI in a similar way SOA run times can combine and integrate services. Component UIs are aggregated into larger, higher value UIs, giving users a single view of IT services with a single UI to master. Applications originally designed separately can be integrated (aggregation and context) together to enable new function. The portal model allows for improved agility for on- demand businesses. Portal administrators become application integrators who create new applications for their users without programming: by defining new pages, adding portlets to them, connecting the portlets together in context, and setting entitlements. With portal technologies, end users can become their own application assemblers by customizing their portal-based workspaces. There are many reasons why a portal would benefit your organization, for example: • Control information glut • Improve cycle times • Empower knowledge workers “A complete portal solution should provide users with convenient access to everything they need to get their tasks done anytime, anywhere, in a secured manner.” • Reduce IT Department Tasks complexity
- 6. 6 • Enhance B to B or partner and supplier communication • Streamline Business Control or Business Management processes WebSphere Portal (Portal for short) supports multiple industry portals and various communities within a company. Portal consists of four basic services: Framework, Integration, Content, and Collaboration Figure 1-2 illustrate the IBM WebSphere Portal framework [4]. Figure 1.2 IBM WebSphere Portal framework courtesy by Bernhard Stimpfle, Jeanette Coury, and Rufus Credle
- 7. 7 (1) (4) (2) Websphere MQ (3) Figure 1.1: Integration of Legacy Application with Modern J2EE Application J2EE Application Websphere Message Broker R E Q 2 R E Q 2 R E S 3 R E S 3 C Application R E Q 1 R E Q 1 R E S 4 R E S 4 Request Response Request Queue Response Queue
- 8. 8 2. Reference: 1. http://www.ibm.com/us/en/. 2. Saida Davies, Laura Cowen, Cerys Giddings, Hannah Parker. 3. Oracle® Procedural Gateway and Tools for IBM MQSeries Installation and User's Guide Release 9.2.0.1.0 for UNIX Part No. A96196-01. 4. Bernhard Stimpfle, Jeanette Coury, and Rufus Credle.