The component's implementation executes the logic.

Service components are the main building blocks of a module. You can implement your services using a variety of programming paradigms, from process-flow style BPEL processes, to state machine-style event management, to declarative business rules style. The style of implementation you select will be determined both by your comfort level with a given paradigm and the nature of the problem.

WebSphere Business Integration tools generate many types of service implementations for components:

• Business processes
• State machines
• Human tasks
• Java
• Rule groups
• Selectors
• Interface maps
• Mediation flows

You can create implementations using a variety of visual construction tools. You can find detailed information about working with each of the implementations in other sections of the documentation.

In the assembly editor, the component's implementation type is represented by an icon in the component. The following image shows the CustomerQuery component. The symbol beside the component's name shows that it has a business process implementation type:

All the implementations are listed with their symbols on the assembly editor palette.

If the component's implementation does not exist, the component will have an exclamation mark in the lower left corner, as shown in the above CustomerQuery component. If the implementation already exists, then there is no exclamation mark, as shown in the following image of the CustomerQuery component:

Components that do not have an implementation type specified have the untyped icon, , as shown in the following image of the CustomerQuery component:

In bottom-up development, you can drag one of the implementations (for example, a human task) from the same module onto the canvas of the assembly editor and the component will be created for you. The component will show its implementation type with no exclamation mark to indicate that the implementation exists.

Also, you can set qualifiers on the component's implementation. The qualifiers provide “quality of service” support (such as transaction support, event sequencing, or security) required from the hosting container.



For training on IBM Lombardi mail us at [email protected]

IBM Business Process Manager incorporates key functionality from WebSphere Process Server, WebSphere Lombardi Edition, and IBM Integration Designer (formerly WebSphere Integration Developer) into a unified user environment. It integrates the most current functionality from those three products and enhances the features from the previous product versions.

IBM Business Process Manager is a comprehensive and consumable business process management platform that provides visibility and management of your business processes. It includes tooling and run time for process design, execution, monitoring, and optimization. It is also designed to help process owners and business users to engage directly in the improvement of their business processes.

Some of the new and enhanced features in the following list existed in previous versions of one of the products (WebSphere Process Server, WebSphere Lombardi Edition, or WebSphere Integration Developer). However, the features are new to users who previously had only one or two of the products but did not have all three.

Some features that previously existed in earlier versions of the integrated products have been replaced by new features in IBM Business Process Manager. For a list of deprecated features, see Deprecated features:   .

New and enhanced features in IBM Business Process Manager V7.5IBM Business Process Manager V7.5 provides the following new or enhanced features:

• A unified authoring environment for creating human-centric, standards-based Business Process Modeling Notation (BPMN) processes (using Process Designer) and integrating them with system-centric Business Process Execution Language (BPEL) processes (using Integration Designer).
• A shared repository and a common execution environment for both BPMN processes and BPEL processes. Together, the unified authoring environment, the shared repository, and the common execution environment provide these enhancements:
  • Graphical implementation and testing of process applications, services, user interfaces, and rules.
  • Standards-based process design, using BPMN.
  • IBM Integration Designer tooling for constructing services, data transformations, BPEL orchestrations, and integration to applications and back-end systems.
  • Business rule authoring that expresses business logic in an accessible manner, providing the same rule-authoring experience as WebSphere ILOG JRules. Rules content can be easily exported to WebSphere ILOG JRules, providing a starting point for business decisions.
  • The IBM ILOG JViews Chart charting engine, which has been added to IBM Business Process Manager V7.5. For existing customized charts, tooling is provided for converting from CDL format to Cascading Style Sheet (CSS) format.
  • Property sheets that make it possible to configure implementation details rather than code them, so that less technical users can participate in design.
  • Complete life-cycle integration, keeping the solution synchronized from model design through deployment.
  • Interactive playback that makes it possible to validate process requirements at any time.
  • Shared library of all process assets, for drag-and-drop reuse and collaborative implementation.
• Real-time control for inflight processes with these features:
  • The inbox in IBM Process Portal provides a consolidated view of all outstanding tasks.
  • A graphical view of process status helps process participants understand the remaining steps in the process.
  • Explicit event modeling defines workflow and exception handling.
  • Exposed process parameters and thresholds provide real-time control during inflight processing.
  • Ad hoc actions are supported; designated users can perform spontaneous tasks and alter workflow.
  • Users can communicate and collaborate on specific tasks during process execution.
  • Real-time scoreboards provide visibility into work in progress, along with the ability to take corrective action if necessary.
  • The framework for the Business Space user interface is included within Business Process Manager.
  • A federated task view makes it possible to perform tasks, manage work items, track performance, and respond to events, all in real time.
  • Optionally, users can perform process tasks directly from Microsoft Office and Microsoft SharePoint. The Microsoft integrations are offered as optional add-on components.
• Enhanced monitoring capabilities, with process visibility into both human and system interactions. IBM Business Process Manager supports insightful dynamic process visibility with these features:
  • Performance measurements are expressed in terms of key performance indicators (KPIs) and service level agreements (SLAs).
  • Business Performance Data Warehouse automatically gathers and correlates performance events and business data to modeled process metrics, for process visibility that is always up to date.
  • The process Optimizer allows visualization of performance bottlenecks and other problems directly on the process model diagram.
• Features from WebSphere Process Server, incorporated now into IBM Process Server, provide transaction integrity and enhanced scalability from first projects to enterprise-wide solutions:
  • High scalability and availability are provided by the embedded WebSphere Application Server.
  • A single BPM runtime server (Process Server) supports the full range of business processes, service orchestration, and integration.
  • Built-in Service Oriented Architecture (SOA) components include a flexible enterprise service bus (ESB) connectivity infrastructure for integrating applications and services.
  • Supported standards include BPMN and BPEL execution and many data and service standards.
  • Integration adapters connect application and information assets to the ESB to accelerate business integration projects with rapidly deployable, enterprise-ready connections based on best practices. A comprehensive set of capabilities is included to service-enable your assets, including packaged, custom, and legacy applications, technology protocols, and databases.
  • Rich repair and recoverability capabilities are provided, including automatic retries, manual repair, compensation, and store-and-forward.
• Support for high levels of program manageability and governance with these features:
  • Process Center provides a scalable central repository and control center for organizing and managing all process artifacts, applications, and services that are created as part of a BPM program.
  • Toolkits manage process artifacts for reuse across multiple process applications.
  • Snapshots capture the state of all artifacts in a process application or toolkit (including business process diagrams, rules, data, forms, services, and simulation scenarios) at a specific point in time with just one mouse-click.
  • Versioning restores any historical snapshot of a process application or toolkit.
  • A Process Server registry provides centralized tools to install and track deployed versions of multiple processes across various runtime server environments.
  • Life-cycle governance provides centralized control for governing deployment of processes and services to production run time.
• IBM Business Process Manager offers three product configurations (Advanced, Standard, and Express) to match the entry point of a company into business process management. For details, see "IBM Business Process Manager 7.5 configurations" in this information center.
• IBM Business Process Manager provides enhanced authoring tools and optional add-ons for integration with popular end-user productivity tools:
  • IBM Process Designer Standards-based process design tool that is part of the basic authoring environment for all three configurations of IBM Business Process Manager (Advanced, Standard, and Express). The process design tool enables rapid composition and continuous process change.
  • IBM Integration Designer Advanced configuration authoring environment for visually constructing services, data transformations, BPEL processes, and integration to applications and back-end systems. The authoring environment is used in collaboration with the process design tool to create robust and scalable process solutions. It includes a comprehensive set of adapters to service-enable assets, including packaged, custom, and legacy applications, technology protocols, and databases. The authoring environment is fully compatible with the latest versions of WebSphere Integration Developer.
  • IBM Business Process Manager for Microsoft Office add-on is an optional add-on to all three configurations (Advanced, Standard, and Express). Microsoft Office users can use IBM Business Process Manager to view and run IBM BPM tasks directly from their Office desktop. The Office add-on installs an IBM plug-in onto the end-user Office desktop client.
  • IBM Business Process Manager for Microsoft SharePoint add-on is an optional add-on to all three configurations (Advanced, Standard, and Express). Microsoft SharePoint users can use IBM Business Process Manager to view and run IBM BPM tasks directly from web parts that are dropped into SharePoint portal pages. The SharePoint add-on is installed on any SharePoint server that will be used to host interactions with processes through the IBM BPM web parts.
• IBM Business Process Manager V7.5 supports the following migrations and data imports:
• Migration of process applications from WebSphere Process Server V6.1, V6.1.2, V6.2 and and V7.0, including design-time process definition assets and inflight process instances.
• Migration of process applications from Lombardi Teamworks 6.1, Teamworks 6.2, Teamworks 7.0 and WebSphere Lombardi Edition V7.1 and V7.2, including design-time process definition assets and inflight process instances.
• Import of design-time process models in BPMN 2.0 format from WebSphere Business Modeler V7.0, WebSphere Business Compass V7.0, and other popular modeling tools.
• IBM BPM Advanced widgets for Business Space can be used with IBM WebSphere Portal.

For training on IBM Lombardi mail us at [email protected]

If a module or library is in a process application or toolkit, it takes on the life cycle of the process application or toolkit (versions, snapshots, tracks, and so on). Module and library names must be unique within the scope of a process application or toolkit.

This topic describes the versioning of modules and libraries that are used with process applications. Note, however, that if you deploy modules directly from IBM® Integration Designer to Process Server, you can continue to follow the procedure of assigning version numbers to modules during deployment, as described in "Creating versioned modules and libraries".

A module or library that is associated with the IBM Process Center must have its dependent libraries in the same process application or in a dependent toolkit.

The following table lists the selections you can make in the dependency editor in IBM Integration Designer when a library is associated with a process application or toolkit:

Generating an import with an HTTP binding is shown in this section.

Before you begin
Prerequisite: You should have a module. The module should have an import with an interface.
About this task
In this set of steps, you will learn how you create an HTTP binding for an import. This popular protocol is used in many circumstances. It is often used by a Web service.If you intend to use the predefined HTTP bytes data binding then you must use the following schema and data handler. Under Predefined Resourcesin the Dependencies editor, select Native Body schema for Native Body DataHandler. Save your work and close the dependencies editor.

If you intend to use the predefined HTTP bytes data binding with a static service gateway then you must also add the service gateway interface and schema files. To add this interface and schema files to your module, open the dependencies editor. Under Predefined Resources, select Service gateway interface and schema files. Save your work and close the dependencies editor.

Procedure

1. Open the assembly editor. Under Outbound Imports, select HTTP and drag it to the assembly editor. Select an interface or create one.Alternately, from the palette under Components, select an import and drag it on to the canvas. An import with no implementation and no interface is created. Right-click the import, select Add Interface from the context menu and add an interface describing your interaction with a client. Generate the HTTP binding by selecting the import and from the context menu selecting Generate Binding > HTTP Binding.
   
2. The Configure HTTP Import Service dialog box opens.