WebSphere Integration Developer Guide Tutorial part 1th

WebSphere Integration Developer Guide Tutorial part 1th WebSphere Integration Developer Overview

Introduction

This series of articles provides a guided tour of application development through WebSphere integration Developer. This first article provides a brief overview of the WebSphere integration Developer and its main concepts.

Subsequent articles will conduct in-depth research on each concept and related construction tools. We'll look at each of the areas in the product and understand their functionality and role, and you'll have the opportunity to build the next part of the entire application yourself. Some of the topics covered in future articles include:

SOA Development

Building and assembling simple applications

Business processes, state machines, and rules

Human tasks

EIS Connection Support

Mediations and selectors

Although these articles are mutually reinforcing, when you delve into a particular part of the important, you will find that each article is self-contained.

What is WebSphere integration Developer?

You might want to know what WebSphere integration Developer is and why it's worth paying attention to. Today's companies are facing growing pressure to integrate, automate systems, and build new channels of communication with customers. Companies need flexible, standards-based products and solutions.

There are a number of issues that you typically encounter during integration activities, including:

Data synchronization between two or more heterogeneous enterprise Information Systems (EIS).

Intelligent Agent product requests from consumers to multiple producers.

Publish product data to the global repository, enabling users to access and leverage this information. The scope of publishing work can range from creating catalogs of available products to participating in the global online marketplace.

Use an arched process (overarching process) to coordinate multiple existing business processes.

Manage the order Processing process from order receipt to inventory management and supply chain management.

Develop, approve, and escalate work tasks to efficiently handle customer requests.

Dynamically respond to changes in the business environment by constantly changing the rules and decisions that govern the business.

The WebSphere integration Developer can address these types and other types of application integration issues. On its basis, WebSphere integration Developer is built on industry standards (especially WSDL, XSD, BPEL, Java™, and UML) and at the forefront of evolving standards (Tuscany Service Component architecture is a good example). To build your application on top of these standards, you can use a series of visual construction tools and a higher level of concepts that will allow you to focus on solving business problems without having to write a lot of Java EE code or be a proficient WSDL expert. It does not need to be immersed in these standards to be able to achieve them.

From the point of view of WebSphere integration Developer, service-oriented architecture refers to the key components that can focus on the system, visualize them, build them visually, and then end the work and use WebSphere Process Server to run the system. After that, you can also visualize unit tests and debug the entire application or a single part of it.

The WebSphere integration Developer supports three construction methods for Top-down, bottom-up, and intermediate encounters. You can start with the top layer, the design layer, and plan the whole idea, and then gradually deepen and implement the various parts (services). Alternatively, you can implement these services separately from a bottom-up approach, and then combine them into larger applications. More likely, it is possible to use the development approach of the middle encounter, perhaps by first laying out the initial high-level design, and then using the Enterprise Metadata Discovery tool to study the enterprise information System and define the various services associated with it. You may also want to introduce and reuse external WEB services provided by your business partners.