WebSphere Process Integration architecture

WebSphere Process Integration architecture
Business processes:
  • The business process component in WebSphere Process Server implements a WS-BPEL obedient process engine. Users can develop and deploy business processes with carry for long and short running business processes and a robust compensation model in a highly scalable infrastructure. WS-BPEL models can be formed in WebSphere Integration Developer or imported from a business model that has been created in WebSphere Business Modeler.
Human tasks:
  • Human tasks in WebSphere Process Server are stand-alone components that can be used to assign work to employees or to invoke any other service. Additionally, the Human Task Manager ropes the ad-hoc creation and tracking of tasks. Existing Lightweight Directory Access Protocol (LDAP) directories (and operating system repositories and the WebSphere user registry) can be used to access staff information. Of course, WebSphere Process Server supports multi-level escalation for human tasks, including e-mail notification.
  • WebSphere Process Server also includes an extensible Web client that can be used to work with tasks or processes. This Web client is built based on a set of reusable Java Server Faces (JSF) components that can also be used to create custom clients or embed human task functionality into other Web applications.
Business state machines:
  • A business state machine provides another way of modeling a business process. Businesses can represent their business processes based on states and events that from time to time are easier to model than a graph-oriented business process model. One illustration is an ordering process where the order can be cancelled or modified at any time during the order process.
Business rules:
  • Business rules are a means of implementing and enforcing business policy through the externalization of business. This allows dynamic changes of a business process for a more receptive business environment. Business rule authoring is supported by an Eclipse-based desktop tool. WebSphere Process Server also includes a Web-based runtime tool for business analysts so that business rules can be modernized as business needs dictate without affecting other SCA services.
Interface maps: 
  • Very often interfaces of existing components match semantically but not syntactically (for example, updateCustomer versus. updateCustomerInDB2). This is especially true for already existing components and services. Interface maps transform these calls so that these components can be invoked. Moreover, business object maps can be used to translate the actual business object parameters of a service invocation.
Business object maps:
  • Used to translate one type of business object into another type, these maps can be used in a range of ways (for example, as an interface map to convert one type of parameter data into another).
  • In business integration scenarios, it is often necessary to access the same data, such as customer records, in various back-end systems (for example, Enterprise Resource Planning and Customer Relationship Management). A common trouble with keeping business objects in sync is that different back-end systems use diverse keys to represent the same objects. The WebSphere Process Server relationship service establishes relationship instance between objects in these different systems. These relationships are typically accessed from a business object map while one business object format is being transformed into another.
  • Different services that all contribute to the same interface can be selected and invoked dynamically by a selector. For example, a customer support process might use different human job implementations during different times of the day. Work is routed to different support centres (Americas, Europe, and Asia-Pacific) based on the time of day. WebSphere Process.
Technical Overview of WebSphere Process Server and WebSphere Integration   Developer

These components can use the features of a number of supporting services in WebSphere Process Server. Most of these can be classified as some form of transformation, which is not unexpected. A number of the transformation challenges in the process of connecting components and external services are addressed by a component of WebSphere Process Server:

WebSphere Process Server is build on a robust J2EE runtime provided by WebSphere Application Server. The architectural model is shown in Figure
ibm websphere application server
The J2EE runtime offers Qualities of Service that WebSphere Process Server exploits, such as clustering, failover, scalability, and security. The J2EE server also includes a built-in messaging provider that can be configured to connect to an obtainable WebSphere MQ network.

Also in the infrastructure layer is the Common Event Infrastructure, which is the foundation for monitoring applications. IBM uses this infrastructure throughout the IBM product portfolio; monitoring products from Tivoli and WebSphere (WebSphere Business Monitor) exploit it. The event definition (Common Business Event, or CBE) is being homogeneous by the OASIS standards remains so that other companies and clients can use the same infrastructure to monitor their environments.

On top of this infrastructure, WebSphere Process Server implements a layer called the SOA core. To do assimilation in an SOA properly, you must have a single invocation model and a single data model. SOA is this invocation model: every integration component is described using an interface. These services can then be assembled in a component assembly editor; the effect is a very flexible, encapsulated solution. Business objects are the universal data description. They are being used as data going in and out of services and are based on the SDO standard.

SCA Bindings describe the physical description of components. Services that can be accessed include Plain Old Java Objects (POJOs), EJBs, Web services, JMS messages, and adapters.
WPS 3801795427342251007

Post a Comment Default Comments


Home item

Blog Archive

Popular Posts

Random Posts

Flickr Photo