Search results

Service Oriented Architecture (SOA) promises a great leap forward in the re-use of applications by simplifying application composition. The technology that simplifies application composition is Service Component Architecture (SCA). SCA is an open component architecture for wiring services together to build composite applications. WebSphere Enterprise Service Bus provides the on-ramp and off-ramp to incorporate many different applications and services into an SOA solution. In this IBM Redbooks publication we introduce SCA and how it has evolved from earlier application integration architectures. We explain how WebSphere ESB connects applications and components to the service bus by using adapters and other types of SCA imports and exports. Our main focus is helping you sort through the many choices that need to be made when deciding how to connect applications together to meet the requirements of a business scenario. We propose six different solution patterns, each with alternative implementations to choose from, to take on most integration scenarios. We also provide seven worked examples of some of the alternatives, which are fully described in the text, and are also available as working samples from the ITSO Redbooks Web site.

IBM® WebSphere® Process Server is a business integration server that was built to support solutions that are based on the service-oriented architecture (SOA). It plays a key role in the architecture of the IBM SOA Foundation by providing functionality for process services. Another key component of the architecture is the enterprise service bus (ESB). IBM provides three key ESB products: IBM WebSphere Enterprise Service Bus, WebSphere Message Broker, and the WebSphere DataPower Integration Appliance XI50. This IBM Redbooks® publication has been written for architects who are planning an SOA solution and application designers who are implementing an SOA solution with WebSphere Process Server and WebSphere Message Broker. In this book, we highlight the ESB capabilities of WebSphere Message Broker and explain how you can leverage them with WebSphere Process Server. In addition, we discuss interoperability and provide examples to illustrate the integration of the two products.

This IBM Redbooks publication provides a practical demonstration of how to develop applications that take advantage of CICS Web services facilities. This book can be viewed as a follow-on from the IBM Redbooks publication Application Development for CICS Web Services, SG24-7126-00, with the addition of using modern tooling techniques. Because we are creating a new application, we follow the bottom-up approach described in Application Development for CICS Web Services, SG24-7126-00. Although not a requirement, we highly recommend that you review that publication for a much deeper discussion of CICS Web services development topics and alternative approaches. The primary purpose of this book is to demonstrate that well structured CICS Web services are easy to develop using the CICS Web Services Assistant. We also look at modern tooling, such as WebSphere Developer for zSeries (WD/z).

Service-oriented architecture (SOA) is one of the most important topics on the agenda of any IT person. SOA involves a new vision of how to design, develop, and manage applications. It also has new requirements when building an architecture for the underlying infrastructure. This IBM Redbooks publication is the result of a project managed in the IBM European Design Center, based in Montpellier, France. The scope of the project involved helping a major worldwide customer in the automotive industry to validate and justify an SOA implementation. In particular, the customer wanted to add new business values to work with its partners, by adding new data models. It also wanted to modernize an infrastructure, by adding new Internet interfaces. The customer faced the need to eradicate an obsolete programming language. Furthermore, it wanted to build a smooth migration path, with as few risks and costs as possible. The thought, planning, and architecture of the new system, which included integration of the SOA concepts, was built by the customer with the participation of Atos Origin, a leading international IT services provider. The existing customer IT infrastructure was already built around UNIX systems, IBM System z, non-IBM clusters, SAP solutions, 3270 screens, IMS-DL/I databases, and specific code. SOA was the right solution to connect this existing environment to new components using Java, Web services, and DB2 in particular. This book explores the business needs and the architectural choices that were faced by t

The Patterns for e-business are a group of proven, reusable assets that can be used to increase the speed of developing and deploying e-business applications. This IBM Redbooks publication focuses on the use of the WebSphere Enterprise Service Bus and WebSphere Message Broker together to form an enterprise service bus (ESB) implemented in a service-oriented architecture (SOA). This book discusses patterns for integrating WebSphere Enterprise Service Bus and WebSphere Message Broker and includes a scenario to help you design, develop, and deploy these products. This book is designed to assist customers that are approaching the use of both advanced and basic ESB products from typically messaging and J2EE worlds, but are not quite sure when each is appropriate.

Over years, the typical IT infrastructure grows and is very likely a collection of separated, heterogeneous environments that can collide with today's requirement for companies to react quickly to changing business needs. This changing environment demands a middleware that is both robust and extensible as well as flexible when reacting to change. With WebSphere Middleware products from IBM you can operate flexible service-oriented architectures that overcome these integration challenges. The IBM WebSphere Service-Oriented Middleware product suite includes different integration brokers and a multitude of application and technology adapters. In addition to the adapter-based integration approach, this product suite supports a wide range of open standards to connect any back-end component in a service-like manner to the middleware infrastructure. This book highlights broker-to-broker connectivity to the SAP Exchange Infrastructure as well as direct communication patterns to the SAP WebApplication Server. This book also illustrates how to integrate data and processes that are located in SAP back-end systems that use IBM Service-Oriented Middleware technology. The adapter-based scenarios use the WebSphere adapters for SAP, and the standards-based integration scenarios use the Web Services and Java Message Service capabilities that are built in to the products of both IBM and SAP.

This IBM Redbooks publication is designed for IT architects and IT specialists that are dealing with IBM WebSphere Message Broker and IBM WebSphere Enterprise Service Bus (ESB) solutions. This book illustrates how to configure an ESB using either IBM WebSphere Message Broker V6 for IBM z/OS or IBM WebSphere Enterprise Service Bus V6. It makes various traditional z/OS transactions and data available as a Web service through the broker, including IBM DB2 data, batch programs, and IBM CICS/IMS transactions. In this book, there is more focus on WebSphere Enterprise Service Bus installation and customization than on WebSphere Message Broker because the latter has already been documented in other places. This book describes multiple scenarios that show how to integrate applications using a mix of MQ and SOAP protocols using both Advanced ESB, also known as WebSphere Message Broker, and WebSphere Enterprise Service Bus. High availability using clustering of brokers in multiple logical partitions (LPARs) on z/OS is also addressed in this book, with details on which feature you can use and configure to improve continuous operation, such as shared queues, shared ports, and Sysplex Distributor.

This IBM Redbook provides guidance on how to manage WebSphere Message Broker V6.0 and its resources in a production environment. It begins with an overview of the WebSphere Message Broker V6.0 architecture, components, and features. These components play a key role in the integration of disparate applications and platforms by providing functional and transport capabilities that support and facilitate enterprise-level business integration. The book describes how to manage and to administer WebSphere Message Broker V6.0 appropriately to achieve maximum stability, availability, and performance in a production environment. This book provides extensive guidance and instructions for various administration tasks for the message broker domain, such as, resource management, security, backup and recover, monitor and health check, maintenance strategy, and problem determination. It covers all the main message broker domain components, such as the Configuration Manager, the broker, the User Name Server, and the Message Brokers Toolkit. It also discusses underlying components such as WebSphere MQ queue manager and the database that is required to run the message broker and notes all generic- and platform-specific considerations. Finally, this book includes sample scenarios that demonstrate important tasks that complement the discussions included in this book.

This IBM Redbook describes three major phases in a WebSphere Business Integration (BI) project. We discuss the planning and system design for a WebSphere BI infrastructure designed to support several business integration projects. - We extend the real-life scenario written for another IBM Redbook. Following planning and design, we discuss the implementation of the run-time engines available in IBM WebSphere Business Integration Server V4.3. - The next phase is developing and testing a business integration solution within our infrastructure. The integration solution combines three run-time engines of WebSphere Business Integration Server V4.3. These engines provide for human interaction, straight-through processing, and message brokering and aggregation. - The final phase of our WebSphere BI project involves deploying the solution into the production environment, and how to manage this solution. We address issues such as how to coordinate stopping and starting components, and troubleshooting run-time problems. We end by discussing performance tuning in WebSphere Business Integration Server V4.3.

Successfully implementing a service-oriented architecture (SOA) requires applications and infrastructure that can support the SOA principles. Applications can be enabled by creating service interfaces to existing or new functions hosted by the applications. The service interfaces should be accessed using an infrastructure that can route and transport service requests to the correct service provider. As organizations expose more and more functions as services, it is vitally important that this infrastructure supports the management of SOA on an enterprise scale. This IBM Redbook looks at how IBM messaging products support an SOA environment. In particular, it looks at WebSphere Application Server, WebSphere Enterprise Service Bus, WebSphere MQ, and WebSphere Message Broker in an SOA environment. We discuss how they support SOA, compare the potential ESB product implementations, and show examples of building the infrastructure and creating mediations.