Websphere Business Integration Created by – Schubert [email_address] … an introduction
Agenda <ul><li>Business Integration </li></ul><ul><ul><li>Introduction </li></ul></ul><ul><ul><li>Challenges </li></ul></ul><ul><ul><li>Capabilities </li></ul></ul><ul><li>Websphere Business Integration – Concepts </li></ul><ul><ul><li>Introduction </li></ul></ul><ul><ul><li>Separation of concerns </li></ul></ul><ul><ul><li>Websphere Integration – Reference Architecture </li></ul></ul><ul><ul><li>WBI – architectural pattern </li></ul></ul><ul><ul><li>WBI – run time logical view </li></ul></ul><ul><ul><li>WBI – models (business / IT / deployment) </li></ul></ul><ul><li>WBI parts </li></ul><ul><li>WBI reference architecture standards and technologies </li></ul><ul><li>Wrap up </li></ul><ul><ul><li>What can be done using WBI ? </li></ul></ul><ul><ul><li>How can it be done ? </li></ul></ul><ul><li>Bibliography </li></ul>
Introduction - i What exactly is BI (Business Integration) ? The processes of combining different business and management systems so that they may interact with one another and thus be used to enhance the overall business strategy and realize the goals of the business. Put technically in simple words, BI covers a broad range of technology, from very simple to fairly complex software systems. It also includes and covers EAI ( Enterprise Application Integration ) as well as B2B ( Business-2-Business ) integration concerns. Technical View Business View
Introduction - ii <ul><li>Why the fuss over Business Integration ? </li></ul><ul><li>All businesses have groups of interrelated activities, which work together to achieve a specific business goal. Such interrelated activities are called business processes. Business processes often change as the business models change. The challenge facing today's businesses is to be able to change business models quickly to capitalize on market opportunities or to fend off competition. This calls for rapid change in complex infrastructures as the pace of the business models changes. </li></ul><ul><li>Business integration is about modeling, creating, testing, monitoring, and managing end-to-end business processes. It involves integrating infrastructures and their applications to form a seamless flow of information to efficiently implement business models. </li></ul><ul><li>A typical Business integration initiative would entail the following steps, viz. </li></ul><ul><li> 1.] Model business process changes and simulate them before deployment </li></ul><ul><ul><li>2.] Integrate and Connect internal as well as external business processes </li></ul></ul><ul><ul><li>3.] Monitor and manage the impact that these processes have on achieving the desired business results. </li></ul></ul>
Challenges - i <ul><li>Today every organization is faced with the need to predict the changes in the global business environment, to rapidly respond to competitors, and the best exploit organizational assets to prepare for growth. An ideal business integration initiative can either help you meet such objectives or it can impede one’s ability to change. </li></ul><ul><li>The main challenges faced in a ‘successful’ Business Integration can be listed as … </li></ul><ul><li>Ability to predict and respond to change By improving the org’s visibility to business events, by enabling one to develop and roll out new business services quickly, modernizing legacy systems and helping to optimize business processes in response to market dynamics. </li></ul><ul><li>Improve organizational productivity By facilitating better decisions with accurate business intelligence, by helping employees finding meaningful information and sharing it collaboratively with others. </li></ul><ul><li>Simplify the Information Technology environment By being provisioned, deployed, monitored, and managed as a single cohesive infrastructure. </li></ul><ul><li>Leverage existing investments By being modular, open & extensible to allow one to adopt in a heterogeneous environment without needing to remove or replace one’s existing systems. </li></ul>
Challenges - ii <ul><li>In addition to the above mentioned challenges, there are a few micro challenges, which can be listed as follows, viz. </li></ul><ul><li>User experience integration By improving the org’s visibility to business events, by enabling one to develop and roll out new business services quickly, modernizing legacy systems and helping to optimize business processes in response to market dynamics. </li></ul><ul><li>Information integration Assemble operational and analytical data to provide an integrated view of business operations and to enable decision making. </li></ul><ul><li>Application integration Provide a mediated environment through integration of best-of-breed application packages offered by software vendors and customer assets. </li></ul><ul><li>Business to business partner integration Enable business partners to collaborate and execute a business process. </li></ul><ul><li>Process integration Choreograph the interaction between users, applications, data sources, and business partners using integrated business processes. </li></ul>
Capabilities - i Business integration capabilities for e-business solutions include the ability to integrate and manage business operation systems, enterprise information assets, business partners, and a collaborative network of decision makers to address specific business problems. On a broad level from a software perspective we can visualize the following structure when we talk about Business Integration capabilities, viz. Business Modeling Tools Direct to middleware tools Business Model Business / Application Services Business Integration components Software artifacts The business value from ‘things’ What ‘things’ do What ‘things’ are How ‘things’ are constructed
Capabilities - ii Business Model Get system demand forecast Create components forecast Identify critical supplies Seek supply commitments Business / Application Services Demand forecast Bill of Materials Supplier information Supplier commitments Business Integration components Adapters Mediation Staff activity Processes Business Integration components SAP/ etc. Adapters Maps Portlets BPEL flows
Introduction Websphere Business Integration ( WBI ) now called Websphere Application Connectivity is a family of products that enables companies to define, create, merge, consolidate, and streamline business processes using applications that run on a service-oriented architected IT infrastructure. These products include design and development tools, runtime servers, monitoring tools, toolkits, and process templates. Like all Websphere products, they are built on the J2EE standard-based Websphere Application Server foundation. The ability to coordinate the challenges of enterprise-level integration necessitates an architecture to facilitate the modeling and managing of services spanning information, applications, and people. Through a component-based approach, organizations can build more flexible integration solutions that leverage a common set of core infrastructure services. The WBI solution framework enables increased agility and adaptability of IT solutions through a more simplified loosely-coupled approach. An SOA-based integration foundation provides support for technology co-existence through support for a standards-based design, development, and implementation. This approach provides a scalable infrastructure across existing and future technology assets to provide a solid foundation for the enterprise integration architecture.
Separation of Concerns When defining an business’s integration architecture, it is critical to consider the breadth of integration requirements. These integration requirements may include traditional workflow processing based on human task interaction, choreography of activities between different systems, distributed data management involving structured and non-structured information, and user interaction capabilities. An enterprise requires the ability to differentiate and design service artifacts appropriate for specific styles of integration required to solve a particular integration problem. As a result, the concept of separation of concerns is the foundation to the definition of the integration services. The separation of concerns approach to defining services results in a design that isolates and characterizes functions and services that are implementation independent. With this approach, building integration solutions becomes an iterative process and components are refined over successive integration projects. Enterprises provide design governance and integration mentorship to development teams to promote best practices and the reuse of services and components.
WBI – Reference architecture The Websphere Integration Reference Architecture provides a comprehensive set of services to enable business integration. The services provide the breadth of functionality needed to solve integration requirements. More importantly, the component services can be implemented in stages to enable incremental evolution on a project-by-project basis while working towards an enterprise integration solution architecture. Although specific projects may not require all of these services, enterprise-level integration will require the ability to add these functional capabilities to the integration architecture. The resultant architecture provides for separation of concerns by enabling business logic, control logic, routing and transformation logic to be loosely-coupled and, as a result, more flexible to change. At the organizational level, this approach facilitates simpler integration solution development and enhances maintainability and operation of the solution. This high-level architecture depicts the integration functions/services required to enable a comprehensive approach to integration. Since these services are described by their interfaces and not by their implementation, a given solution may be made up of mainframe applications, local, or remote services, choreographed processes described by BPEL (the standard for business process description) or components built with J2EE. The implementations of these integration components provide support for non-functional requirements including reliability, security, availability, and management at both the operating environment level, and the component/service level as well.
WBI – Architectural pattern The Websphere Business Integration architectural pattern brings together the principal architectural elements of the platform in realizing business integration solutions. The Web-Sphere business Integration architecture and platform look anew at building business integration solutions to address the key value drivers of return on-investment, time-to-market, and flexibility.
WBI – Architectural pattern - i The Solutions concept Websphere Business Integration addresses the return on- investment value proposition by offering solution templates that prepackage domain-specific content (e.g., e-procurement solution templates). Solution templates reduce the time-to-market by enabling the quick construction and customization of solution instances using the solution studio, an integrated suite of tools. Furthermore, these business integration solution instances execute on a consistent open-standards- based solution infrastructure that provides the necessary flexibility to adapt to change without extensive software programming. The Programming Model The Websphere Business Integration programming model supports assembling business integration solutions from a set of integration components. The concept of an integration component provides a common abstraction over a variety of business function implementations. An application adapter or a Business Process Execution Language (BPEL) process choreography script, for example, can realize a component. Business-integration solution developers assemble a new solution from a palette of components rather than by writing any code. The programming model identifies a set of component kinds that handle specific aspects of a typical business integration solution (e.g., mediation, adapter) and provide the building blocks for pattern-based construction of those solutions. These component kinds in turn implement one or more business or application services.
WBI – Runtime view The Websphere Business Integration runtime consists of software infrastructure elements that host the programming model software artifacts in a business integration solution. The user experience integration and the information integration aspects of the runtime shown in the figure below are capabilities provided by the portal and the data management portfolio of products respectively, which can be used in conjunction with Websphere Business Integration. The runtime elements include the user experience integration for rendering role-based executable content, the partner integration for business-to-business interactions with the business partners of a firm such as customers and suppliers, and process choreography for the choreography of applications in the context of the business process. They also include application integration for connectivity and mediation of application data, information integration for integrating operational and analytical data sources, and business performance management for monitoring the business operations, detecting solution exceptions, and launching appropriate recovery. The run-time also features a number of common integration services, such as the directory and security services, relevant to all the runtime elements.
WBI – Runtime view - i User experience integration The user experience integration runtime element enables users with specific roles to view monitoring dashboards, review work lists, and interact with processes to execute specific work items, to analyze and view business information, and to access one or more applications. Essentially this component renders the content based on who is accessing the content (role) and where they are in the business operations (context sensitive). The Websphere Portal family of products provides this element. Partner integration The partner integration runtime element facilitates interaction between businesses across enterprise boundaries. This runtime element supports a variety of transports (e.g., Hypertext Transfer Protocol [HTTP], MQSeries*), delivery interchange protocols (e.g., Simple Object Access Protocol [SOAP], EDI), and business protocols (e.g., SWIFT, RosettaNet). Partner integration serves as a business gateway in a business integration solution and uses the trading partner profile to determine the most appropriate business channel (i.e., business protocol and quality of service and protection) to use. The Websphere Business Integration Connect product provides this runtime element process. The Websphere Business Integration Foundation provides the process-choreography element.
WBI – Runtime view - ii Application integration The application integration runtime element executes the message flows that are required for brokering between applications and providing a mediated environment for business process integration. There are many different message models (publish-subscribe, request- reply, and so forth) and topologies (point-to- point, hub-and-spoke) that apply to the implementation of this runtime element. The Websphere Business Integration Foundation, the Message Broker, and the adapters collectively realize application integration. Information integration The information integration runtime element provides the persistence for business artifacts. It also provides the federation and replication of data and optimizes the placement of data (caching). Additionally, the information integration element provides access to structured and unstructured content (e.g., data in different media forms such as faxed documents). IBM data management technology realizes the information integration runtime. Business Performance Management The information integration runtime element provides the persistence for business artifacts. It also provides the federation and replication of data and optimizes the placement of data (caching). Additionally, the information integration element provides access to structured and unstructured content (e.g., data in different media forms such as faxed documents). IBM data management technology realizes the information integration runtime.
WBI –M odels - i The above mentioned 3 levels (or echelons as termed in WBI literature) exist as the core WBI models Business Model Information technology Model Deployment Model The business echelon models take a line-of-business perspective that is of interest to business analysts and architects. A typical use of such models is in the business transformation stage where one develops an understanding of the business operations in terms of their to-be state. The business transformation analysis includes the simulation of the business operations models and iterative refinement of the models through interactions with subject matter experts in the business operations. The IT echelon model is where the solution begins to take shape in terms of software components and services. This echelon is of interest to solution and IT architects who analyze the business echelon models to arrive at the manifest of software components for solution assembly. The deployment echelon model factors the environment in which the business integration solution has to execute and is of interest to systems architects and integrators.
WBI –M odels - ii Business Model Business operation and observation models. The business operation and observation models are platform-independent characterizations of how a business operates and how to monitor and manage business performance. The process model provides a functional description of the business activities that constitute a business operation (e.g., e-procurement business operation includes processing of a request-for quote (RFQ) as a business activity). The information model captures the business artifacts (e.g., RFQ business document) and the business events (e.g., acknowledgment of the receipt of a quote) in a business operation. The resource model characterizes the resource requirements as well as the specific resources. Resource requirements are expressed in terms of the role that the resource will play in the business operation (e.g., buyer), quantity of the resource that is required (e.g., one), and the relevant resource constraints (e.g., buyer specialized in purchasing computer supplies). The organization model captures the structure of the organization involved in the business operation. The model represents organizational units, such as an enterprise (e.g., IBM Corporation), the divisions in an enterprise (e.g., Research Division), the departments within a division (e.g., Procurement), and the resources owned by the department (e.g., John Doe). The service model represents the business services that are consumed (e.g., Digital Subscriber Line [DSL] provisioning service offered by a service provider that is used by a telephone-company-fulfillment business operation) as well as those that are exposed by a business operation (e.g., order placement self-service). Workplace refers to the role and context-specific display that a human user employs to participate in a business operation. The observation model is concerned with the monitoring and management of business operations. A policy is an element of guidance for a business operation.5 It is a four - tuple: when is a policy applicable (precondition), where is it applicable (scope), what is the desired outcome (measurable intent), and what is the implication of meeting or violating the policy (business value)
WBI –M odels - iii IT Model The IT echelon represents the business integration solution as an assembly of components and services. Essentially, the business echelon models map to the component kinds and integration patterns described earlier. The BPEL and J2EE/Web services artifacts implement these component kinds. <ul><li>Solution and IT architects derive the IT echelon models from the business echelon models using architectural analysis and specific architectural styles. </li></ul><ul><li>The transformation of business echelon models to IT echelon models is aided by e-business patterns, best practices, and the practical experience of solution and IT architects. </li></ul>
WBI –M odels - iv Deployment Model The software artifacts from the IT echelon models are packaged, installed, and distributed in the deploy echelon. The software artifacts are packaged into installable units. An installable unit is a unit of deployment and consists of a descriptor and the packaged artifacts. For example, an RFQ process component in the e-procurement solution can be an installable unit. The installable unit is installed onto a logical target, which is typically one of the runtime elements described earlier (e.g., process choreography). The set of logical targets in a solution defines the logical topology for a solution. Solution modules group installable units (e.g., RFQ process component and the associated adapters and mediations that make up a solution module); a solution module is also an installable unit. The deployment template refers to a predefined set of solution modules, installable units, and logical topology with customizable points of variability. A solution template, which is a composition of components and services in the IT echelon, can be associated with one or more deployment templates. The deployment model, the instantiation of the deployment template, consisting of specific installable units and their association with logical targets, is registered in a solution registry. This facilitates the management of the solution over its life cycle (e.g., changes and fixes applied to a solution over its life cycle). A logical target in the deployment template can map to one or more physical targets in the infrastructure
WBI – Parts Websphere Interchange Server Websphere MQ workflow <ul><li>Coordinate business process activities that span multiple applications, which may be local or remote, internal or external . </li></ul><ul><li>Enables one to synchronize business events in multiple systems </li></ul><ul><li>Lets one integrate applications on diverse platforms </li></ul><ul><li>Helps one transform information formats en route between applications </li></ul><ul><li>Enables one to deliver integrated solutions as business services </li></ul><ul><li>Operating systems supported: AIX, HP Unix, Linux, Sun Solaris, Windows </li></ul><ul><li>Automates and tracks business processes in accordance with business design and provides integration processes with rich support for human interactions. </li></ul><ul><li>Allows one to bring systems and people into a managed process integration environment for EAI, B2Bi, BAM and BPM solutions, supporting service-oriented architectures based on open standards </li></ul><ul><li>Fits natively with MQ-based infrastructures for SOA's (service-oriented architectures) </li></ul><ul><li>Offers compatibility with open standards including J2EE™, XML, Web services and WS-BPEL </li></ul><ul><li>Enables use with WebSphere Business Integration Modeler and Monitor for design, analysis, simulation and monitoring of process improvements </li></ul><ul><li>Integrates and expands functionality when used with WebSphere Business Integration Server </li></ul><ul><li>Operating systems: WebSphere MQ Workflow servers run on Microsoft® Windows® XP, Windows 2000, and Windows 2003; AIX®, HP-UX, Solaris®, and z/OS® </li></ul>
WBI – Parts - i Websphere Message Broker Websphere Adapters <ul><li>It distributes information and data generated by business events in real time to people, applications, and devices throughout your extended enterprise and beyond. </li></ul><ul><li>Provides a smart approach to SOA, extending the reach of your business beyond your firewall by supporting a broad range of multiple transport protocols and data formats </li></ul><ul><li>Integrates multiple applications, networks, and device types using a platform-independent based enterprise service bus that lets you conduct business reliably and securely </li></ul><ul><li>Increases business agility and flexibility, extending easily to a Federated ESB model, while reducing development costs by separating integration logic from applications </li></ul><ul><li>Improves the flow of information around the business, moving away from hard-coded point-to-point links to more flexible distribution mechanisms such as publish/subscribe and multi-cast </li></ul><ul><li>Uses a simple programming model for connectivity and mediation, including a robust set of pre-built mediation function and ways to customize mediations </li></ul><ul><li>Exploits the industry-leading WebSphere MQ messaging infrastructure, and supports transformation options with graphical mapping, Java, ESQL, XSL, and WebSphere Transformation Extender </li></ul><ul><li>Delivers extensive administration and systems management facilities for developed solutions </li></ul>WebSphere® Business Integration (WBI) Adapters use an asynchronous standalone runtime architecture (the WBI Framework) with WebSphere MQ or JMS as the underlying transport protocol. Originally designed for WebSphere InterChange Server (WICS), they remain available for WebSphere Message Broker, WebSphere ESB, and WebSphere Process Server users transitioning from WICS or WebSphere Business Integration Server.
WBI – Parts - ii Websphere Process Server <ul><li>Built on open standards, it deploys and executes processes that orchestrate services (people, information, systems, and trading partners) within your service-oriented architecture (SOA) or non-SOA infrastructure. </li></ul><ul><li>Extends the value of core applications and databases by centralizing business processes and sharing them across the enterprise, enabling businesses to maximize resources and increase ROI </li></ul><ul><li>Helps cut costs by enabling flexible business processes with reusable assets, reducing the need to hard-code changes across multiple applications when making changes to existing processes or creating new ones. </li></ul><ul><li>Ensures compliance with regulations and internal requirements by that business operations run precisely as documented </li></ul><ul><li>Ensures process integrity to accommodate transaction intensive processes, while providing the scalability, reliability and flexibility needed for future business needs </li></ul><ul><li>Strong support for human workflow and enables rapid process changes, providing business agility and enabling you to leverage resources efficiently. </li></ul><ul><li>Operating systems supported: AIX, HP Unix, i family, Linux, Sun Solaris, Windows, z/OS </li></ul>
WBI – Reference architecture standards and Technologies J2C, JMS, IIOP, JDBC, CICS, IMS, 3270/5250 Application and information assets J2EE (JNDI, EJB, JSP, JTA, JAAS, JAXP, JAXR, JMX and others) Business application services FTP, sFTP, HTTP, HTTP/S, RosettaNet, SMTP, JMS, SOAP/HTTP, WMQ, cXML, EDI (X12, EDIFACT and others) Partner services XQuery, SQL, JDBC/ODBC Information services J2EE, BPEL4WS, WSDL, UDDI Process services WSRP, JSR 168, Java Server Faces, VoiceXML, J2EE Interaction services W3 Common Log Format, WS DM initiatives, CEI/CBE Business performance management tools Eclipse, J2EE, J2SE, J2ME, XML, UML, Java Server Faces, SWT, XMI, WS BPEL, SQLJ, JDBC, XSLT, WSDL, UDDI Development tools JMS, J2EE, SOAP, XSLT, WSDL, UDDI Enterprise service bus Relevant standards Service function
Wrap up… <ul><li>What Can be done ? </li></ul><ul><ul><li>First, you model your business process using WebSphere Business Modeler. </li></ul></ul><ul><ul><li>Next, you develop the application components using Rational Application Developer for WebSphere Software. </li></ul></ul><ul><ul><li>Then, you configure the application components within the system using WebSphere Integration Developer. </li></ul></ul><ul><ul><li>The application runs on WebSphere Process Server, which choreographs the various components. </li></ul></ul><ul><ul><li>The various components might exchange messages using WebSphere MQ. </li></ul></ul><ul><ul><li>You might expand the process to incorporate interaction with your business partners using WebSphere Partner Gateway. </li></ul></ul><ul><ul><li>If your application needs to connect to Web services, you could use WebSphere Enterprise Service Bus, which provides basic connectivity services. If your application needs more advanced services or the ability to connect to non-standard interfaces, then you could use WebSphere Message Broker instead. </li></ul></ul><ul><ul><li>Your application might access back-end applications or technologies such as DB2® PeopleSoft, SAP or Siebel, using WebSphere Adapters. </li></ul></ul><ul><ul><li>Finally, you monitor the business application using WebSphere Business Monitor. </li></ul></ul>
Wrap up… <ul><li>How can it be done ? </li></ul><ul><ul><li>A business analyst or process designer uses WebSphere Business Modeler to chart and simulate the existing and to-be business process definitions. He or she can export the process definition to a Web Services Business Process Execution Language (WS-BPEL) file, and then specify key performance indicators (KPI's) that should be used to monitor the process once it is in production. </li></ul></ul><ul><ul><li>The Software architect can import the WS-BPEL file into Rational Software Architect, where he or she creates an implementation model using UML. </li></ul></ul><ul><ul><li>J2EE or Java™ application programmers implement the business process application components in the architect's model using Rational Application Developer for WebSphere Software. </li></ul></ul><ul><ul><li>Integration developers configure the process with new and existing applications and enable it for human interaction using WebSphere Integration Developer. This role is filled by someone who is somewhat technically oriented and thoroughly understands the process flow, but does not require Java skill. </li></ul></ul><ul><ul><li>Managers and business analysts use WebSphere Business Monitor to track and analyze your company's business processes. It includes a customizable dashboard, implemented as WebSphere Portal pages with scorecards, key performance indicators, and gauges. </li></ul></ul><ul><ul><li>System administrators use WebSphere MQ, WebSphere Application Server, and Tivoli Access Manager, (and possibly other tools) to manage the infrastructure, provide security, and optimize performance. </li></ul></ul>