Websphere Integration Developer 6.1 Certification

WID 6.1 Certification Test 316

2009-12-17T08:40:00.000-08:00

Test 316: IBM WebSphere Integration Developer V6.1 Application Development
Websphere Integration Developer v612
Contact us...

Section 1 - Programming Model and Design (21%)
Section 2 - Component Implementation (30%)
Section 3 - Human Tasks (11%)
Section 4 - Connectivity (12%)
Section 5 - Component Assembly and Configuration (12%)
Section 6 - Application Testing and Debugging (14%)

The test consists of six sections containing a total of approximately 57 multiple-choice questions. The percentages after each section title reflect the approximate distribution of the total question set across the sections.

Section 1 - Programming Model and Design (21%)

Section 2 - Component Implementation (30%)

Section 3 - Human Tasks (11%)

Section 4 - Connectivity (12%)

Section 5 - Component Assembly and Configuration (12%)

Section 6 - Application Testing and Debugging (14%)

WebSphere Learning Resources

2009-07-10T20:45:00.001-07:00

Websphere Learning resources

Websphere Business Modeler v6.1

Websphere Business Modeler Learning resources
Websphere Business Integration Developer Learning resources

Websphere Business Modeler Learning resources

Certification preparations

Forums

IBM DeveloperworksModel business measures

IBM Redbooks

Learning Resources

Websphere Business Integration Developer Learning resources

Adapters

Courses

IBM Infocenter

Websphere Integration Developer 6.1 (includes Business Modeler, process server, enterprise service bus, business services fabric)
Websphere Integration Developer 6.0.1/6.0.2 (includes Business Modeler, process server, enterprise service bus, business services fabric)
Websphere Integration Developer 5.0
Websphere Application Server Network Deployment 6.1

Redbooks

Related Websphere Resources

Tutorials

Configure the integrated test environment

2009-06-16T18:31:00.005-07:00

Application Testing and Debugging
Websphere Integration Developer v612
Contact us...

Configure the integrated test environment
1. Deploying modules to the test environment

Configure the integrated test environment

In WebSphere® Integration Developer, the integrated test environment features runtime support for WebSphere Process Server, or WebSphere Enterprise Service Bus, or both, depending on the test environment profiles that you chose to install when you installed WebSphere Integration Developer.

WebSphere Process Server enables you to run business integration components that cannot be run on any other type of server, such as BPEL business processes, human tasks, business state machines, business rules, and other components. You can also run mediation flows that are contained in mediation modules. By comparison, mediation flows are the only business integration component that you can run on WebSphere Enterprise Service Bus. The deployment documentation provides sufficient information about the integrated test environment to enable you to deploy your modules. However, if you want to learn more about WebSphere Process Server or WebSphere Enterprise Service Bus, see the documentation at the IBM WebSphere Business Process Management Version 6.1 information center.

WebSphere Integration Developer extends the deployment capabilities of the Rational® Application Developer base on which it is built. Similarly, the WebSphere Integration Developer deployment documentation extends and supplements the deployment documentation of Rational Application Developer.

Deploying modules to the test environment

In WebSphere® Integration Developer, you can deploy modules to the test environment and work with server tools that enable you to perform such tasks as creating test servers, editing server configurations, and starting and stopping servers.

Creating servers in the test environment
If you chose to install the WebSphere Process Server and WebSphere Enterprise Service Bus test environment profiles when you installed WebSphere Integration Developer, then you will already have default test environment servers. However, if you deleted one or both of these default servers or if you are working with a standalone installation of WebSphere Process Server or WebSphere Enterprise Service Bus, you will need to create one or more test environment servers for testing your modules.
Editing server configurations in the test environment
There may be occasions when you want to edit a server configuration. For example, you may want to open the server administrative console and then edit some properties, such as configuring the behavior of human tasks at run time. Or you may want to open the WebSphere Integration Developer server configuration editor and then edit some basic settings, such as modifying a port number.
Starting servers in the test environment
Before you can create a running instance of a component in WebSphere Integration Developer, you need to start the server.
Adding modules to test environment servers
Before you can test your modules on a test environment server, you need to add the modules to the server.
Publishing modules to test environment servers
In WebSphere Integration Developer, you will occasionally need to publish modules to a running test environment server. This effectively redeploys the modules and allows the running server to pick up changes that you have made to the components of your modules.
Publishing changed resources to a server
If new or changed resources exist in your workspace that have not yet been published to the server, the state of the server in the Servers view will be Republish. If you want to see the specific resources that are new, changed, or deleted and then decide whether to publish the updates to the server, you can open the View and Publish Changes to Server dialog box.
Removing modules from servers
From time to time, you will want to remove modules from your servers. For example, if you have modules that you no longer need to test, you should consider removing them from the server so that they do not needlessly impact the performance of the server.
Restarting servers in the test environment
In WebSphere Integration Developer, you may encounter situations where you need to restart a running test environment server. For example, you will probably need to restart a server if you make changes to the server configuration while the server is running.
Stopping servers in the test environment
Whenever you finish using a test environment server in WebSphere Integration Developer, you should stop it. This ensures that the server will not unnecessarily impact the performance of other tools in the workbench or the computer that it is running on.
Creating or resetting default server profiles
A default server profile is a test environment server profile that is created when the WebSphere test environment is installed with WebSphere Integration Developer. In the Servers view, you can choose to create or reset a default server profile for either WebSphere Process Server or WebSphere Enterprise Service Bus. For example, you may now want to create a default server profile that you earlier chose not to have created when you installed the WebSphere test environment. Or you may need to reset an existing default server profile that is no longer functioning correctly.

Use the integrated test environment to test modules, mediation mo

2009-06-16T18:31:00.003-07:00

Application Testing and Debugging
Websphere Integration Developer v612
Contact us...

Use the integrated test environment to test modules, mediation modules and components

Use the integrated debugger to troubleshoot mediation flows and c

2009-06-16T18:31:00.001-07:00

Application Testing and Debugging
Websphere Integration Developer v612
Contact us...

Use the integrated debugger to troubleshoot mediation flows and components

Identify and resolve common errors in integration applications an

2009-06-16T18:30:00.003-07:00

Application Testing and Debugging
Websphere Integration Developer v612
Contact us...

Identify and resolve common errors in integration applications and mediation flows

Use the BPC Explorer to test processes and tasks

2009-06-16T18:30:00.001-07:00

Application Testing and Debugging
Websphere Integration Developer v612
Contact us...

Use the BPC Explorer to test processes and tasks

Use the Module Dependency Editor to declare dependencies for modu

2009-06-16T18:26:00.001-07:00

Component Assembly and Configuration
Websphere Integration Developer v612
Contact us...

Use the Module Dependency Editor to declare dependencies for modules, mediation modules, and libraries

When developing and deploying integration applications, you may need to declare dependencies for your modules, mediation modules, and libraries. Use the dependency editor to manage these required resources.

When a new module or library is created, it may not have any dependencies. Using the dependency editor, you can add dependencies on libraries and Java™ projects. For modules and mediation modules, you can also add dependencies on J2EE projects.

Using the dependency editor, you can add dependencies on libraries and Java™ projects. For modules and mediation modules, you can also add dependencies on J2EE projects.

You can add dependencies when you create a new project. Follow these steps to add dependencies for a module, mediation module, or library that already exists in the workspace:

In the Business Integration view, double-click the Dependencies artifact under the module, mediation module, or library from which you want to add a dependency. The dependency editor opens.
Depending on what you need to add, expand the Library, Java, or J2EE section in the Dependency editor. You can only add J2EE projects dependencies for modules and mediation modules.
Click Add to add the library or project.
In the selection window, click the library or project and click OK to add it as a dependent. In the dependency editor, you should see the resource added to the container.
Select a newly added Java or J2EE project in the container to see the Deploy with Module setting and, for J2EE projects, the On Build Path setting. You can clear either of these check boxes to remove dependencies. Do not clear the Deploy with Module check box for libraries. See related concepts for more information on dependencies.

Show Me

Configure Quality of Service (QoS) qualifiers when wiring components

2009-06-16T18:25:00.005-07:00

Component Assembly and Configuration
Websphere Integration Developer v612
Contact us...

Configure Quality of Service (QoS) qualifiers when wiring components in the assembly editor

Create module imports, exports and standalone references

2009-06-16T18:25:00.003-07:00

Component Assembly and Configuration

Websphere Integration Developer v612

Create module imports, exports and standalone references

Create module imports, exports and standalone references

Imports

An import allows you to use functions that are not a part of the module that you are assembling.

Imports are used in an application in exactly the same way as local components. This consistency provides a uniform assembly model for all functions, regardless of their locations or implementations.

Imports have interfaces that are the same as, or a subset of, the interfaces of the remote service that they are associated with so that those remote services can be called. To share the interfaces between modules, put the interfaces into a library. Then, for both modules, add a dependency on the library to use its resources.

Imports and exports require binding information, which specifies the means of transporting the data from the modules. An import binding describes the specific way an external service is bound to an import component. For an import that is generated from an export, the binding type of the import will be specified for you. Imports can use the following bindings: SCA, Web service, HTTP, messaging (JMS, MQ JMS, generic JMS, MQ), stateless session bean, and EIS. Available function (or business logic) implemented in remote systems (such as Web services, EIS functions, EJBs, or remote SCA components) is modeled as an imported service.

Exports

An export is a published interface from a component or import that offers its service to the outside world, for example, as a Web service.

Exports have interfaces that are the same as or a subset of the interfaces of the component or import that they are associated with so that the published service can be called. An export dragged from another module into an assembly diagram will automatically create an import. Exports that are shown under the module assembly in the Business Integration view can also be used to create imports in other modules.

Each export has an address at which it will be deployed on the server. The export can be exposed at that address.

Imports and exports require binding information, which specifies the means of transporting the data from the modules. When you use the Generate Export action from the menu of a component, you need to select the binding so that the binding is generated when the export is created. An export binding describes the specific way a module's services are made available to clients. If an export in a module assembly does not have any binding, when deployed, SCA binding is assumed.

For enterprise information systems (EIS), an export allows an event in the enterprise system, such as the creation of a business object in SAP, to drive an action. Unlike other exports, you cannot drag and drop an export with an EIS binding to create an EIS import.

Stand-alone references

Stand-alone references allow a Java™ program to invoke SCA components or imports.

Services that are not defined as SCA components (for example, JavaServer Pages) can still invoke SCA components; they do so through the use of stand-alone references. Stand-alone references contain partner references that identify the components to call. On their own, stand-alone references do not have any implementation or interface.
You can use the palette in the assembly editor to create stand-alone references in the module assembly. You can add partner references to the stand-alone references and wire them to target components or target imports.

Note: You can only use one stand-alone references node in each assembly diagram.

Configure EJB, Java, and SCA bindings

2009-06-16T18:25:00.001-07:00

Component Assembly and Configuration
Websphere Integration Developer v612
Contact us...

Configure EJB, Java, and SCA bindings
1. Related links

Configure EJB, Java, and SCA bindings

Configure bindings to support synchronous invocation patterns

2009-06-16T18:00:00.005-07:00

Connectivity
Websphere Integration Developer v612
Contact us...

Configure bindings to support synchronous invocation patterns (JMS, MQ, Web Services, HTTP)

Configure bindings to support synchronous invocation patterns (JMS, MQ, Web Services, HTTP)

Invocation Patterns

SCA provides four invocation patterns.

Synchronous
Client issues a request and waits for the response.
Asynchronous one-way
Client issues a request and a response is not expected.
Asynchronous deferred response
Client issues a request and the response will be requested by the client at a later point in time.
Asynchronous call back
Client issues a request and the target will call a service implemented by the client with the response.

JMS binding configuration

Use JMS binding when you need to access a messaging system.

The following must be configured to support synchronous invocation (Client issues a request and waits for the response)

JMS Messaging domain
Set to Point-to-Point
Managed connection factory
A factory used to create the connection to the messaging provider
Send Destination Properties
The destination where the message would be sent
Receive Destination Properties
The destination where the response message would be received. This value is specified in the JMSReplyTo field of the sent message.

MQ binding configuration

Use MQ binding when you need to access a WebSphere MQ messaging system and need to use the MQ native functions.

The following must be configured to support synchronous invocation (Client issues a request and waits for the response)

Request Queue Manager
Send Destination Queue
Receive Destination Queue

Web Service binding configuration

Use Web Service binding when you need to access an external service over the Internet or provide a service over the Internet.

The following must be configured to support synchronous invocation (Client issues a request and waits for the response)

JMS Messaging domain
Set to Point-to-Point
Managed connection factory
A factory used to create the connection to the messaging provider
Send Destination Properties
The destination where the message would be sent
Receive Destination Properties
The destination where the response message would be received. This value is specified in the JMSReplyTo field of the sent message.

HTTP configuration

Use HTTP binding when you need to access an external service over the Internet or provide a service over the Internet and you are working with other Web services based on the HTTP model; that is, using well-known HTTP interface operations like GET, PUT, DELETE, and so on.

The following must be configured to support synchronous invocation (Client issues a request and waits for the response)

JMS Messaging domain
Set to Point-to-Point
Managed connection factory
A factory used to create the connection to the messaging provider
Send Destination Properties
The destination where the message would be sent
Receive Destination Properties
The destination where the response message would be received. This value is specified in the JMSReplyTo field of the sent message.

Configure bindings to support asynchronous invocation patterns

2009-06-16T18:00:00.003-07:00

Connectivity

Websphere Integration Developer v612

Configure bindings to support asynchronous invocation patterns (JMS, MQ)

Configure bindings to support asynchronous invocation patterns (JMS, MQ)

Invocation Patterns

SCA provides four invocation patterns.

Synchronous
Client issues a request and waits for the response.
Asynchronous one-way
Client issues a request and a response is not expected.
Asynchronous deferred response
Client issues a request and the response will be requested by the client at a later point in time.
Asynchronous call back
Client issues a request and the target will call a service implemented by the client with the response.

JMS binding configuration

Consider a JMS binding when these factors are applicable:

You need to access a messaging system
The services are loosely coupled
Reliability is more important than performance; that is, asynchronous data transmission is preferred over synchronous.
Note: There are several types of JMS bindings. If you are using the Web Service binding, only the SOAP/JMS transport protocol is supported. See Service import and export binding types.

The following must be configured to support asynchronous invocation

JMS Messaging domain
Set to Point-to-Point
Managed connection factory A factory used to create the connection to the messaging provider
Send Destination Properties
The destination where the message would be sent
Receive Destination Properties
The destination where the response message would be received. This value is specified in the JMSReplyTo field of the sent message.

MQ binding configuration

Consider an MQ binding when these factors are applicable:

You need to access a WebSphere MQ messaging system and need to use the MQ native functions
The services are loosely coupled
Reliability is more important than performance; that is, asynchronous data transmission is preferred over synchronous.

The following must be configured to support asynchronous invocation.

JMS Messaging domain
Set to Point-to-Point
Managed connection factory A factory used to create the connection to the messaging provider
Send Destination Properties
The destination where the message would be sent
Receive Destination Properties
The destination where the response message would be received. This value is specified in the JMSReplyTo field of the sent message.

Create imports from external services

2009-06-16T18:00:00.001-07:00

Connectivity
Websphere Integration Developer v612
Contact us...

Create imports from external services
1. Accessing external services

Create imports from external services

Accesing external services

This scenario discusses different ways to access services that are external to the application, and provides high level tasks for accessing these external services.

Add, configure, and bind an adapter

2009-06-16T17:59:00.003-07:00

Connectivity
Websphere Integration Developer v612
Contact us...

Add, configure, and bind an adapter

Add, configure, and bind an adapter

Resource adapters

Resource adapters, usually referred to as adapters, provide a mechanism that allows for the integration of an existing EIS infrastructure with the WebSphere Process Server or WebSphere Enterprise Service Bus server. They provide a service-oriented approach to EIS integration. Adapters offer a consistent framework for access to back-end systems and their applications.

Accessing external services with adapters

Services and artifacts on external systems can be imported into WebSphere® Integration Developer. A wizard discovers applications and data on an Enterprise Information Systems (EIS) and lets you generate services from the discovered applications and data. The generated artifacts are interfaces and business objects, which can be used by components in a module.

Configuring and using adapters

The following adapters can be configured to work with WebSphere® Integration Developer. In the documentation for each adapter, you will be shown how to use the external service wizard with the adapter as well as additional information that will be helpful such as field level reference information and runtime information

Use and configure the data binding framework

2009-06-16T17:59:00.001-07:00

Connectivity
Websphere Integration Developer v612
Contact us...

Use and configure the data binding framework

Use and configure the data binding framework

A data binding takes an incoming stream of data in a native format and converts it to a business object to be used by services created with the service component architecture; for example, data from a Java™ application to a service created with the WebSphere® Integration Developer editors and wizards. A data binding can also take an outgoing stream of data in a business object and convert it to a native format.

A data binding works with a data handler. The data binding delegates the transformation logic to a data handler. The data binding works as a mediator between the transport-dependent protocol (JMS, MQ, HTTP and so on) and the transport-independent protocol of the data handler.

In this section, you are shown how to create a data binding resource configuration and given a list of the predefined data binding resource configurations.

Creating a data binding resource configuration
The steps to create a data binding resource configuration with the binding resource configuration wizard are shown.
Email, FTP and Flat Files data bindings configuration
The configuration of data bindings for the Email, FTP and Flat Files adapters is discussed.
JMS, MQ JMS and generic JMS data bindings configuration
The configuration of JMS, MQ JMS and generic JMS bindings is discussed.
MQ data binding configuration
The configuration of the MQ binding is discussed.
HTTP data binding configuration
The configuration of the HTTP binding is discussed.
Creating a data binding resource configuration for WTX
WebSphere Transformation Extender (WTX) is a universal validation and transformation engine used to exchange business documents in many data formats.

Parent topic: Working with configurations that access external services

Assign staff to a human task

2009-06-16T17:50:00.003-07:00

Human Task

Websphere Integration Developer v612

Assign staff to a human task

Assign staff to a human task

You need a way to associate a human task with a specific person or any member of a group of people who is qualified and permitted to complete the task. You can also assign roles (for example, Potential Owner, Reader) to a human task so that specific access rights can be granted.

People assignment roles and criteria

Roles and criteria interact to identify staff members according to their access rights. More specifically, authorization roles determine what their members are allowed to do in the runtime environment, and people assignment criteria define who will be member of an authorization role.

To understand how this works, you have to keep in mind that a task is assigned first and foremost to a role, not an individual. Each staff member in this role group has the permissions assigned to the role as a whole. Criteria act to further refine the list of members who can claim the work. Officially, a people assignment criteria is a database query that retrieves a list of members from the runtime engine

People assignment settings

Use the staff settings to determine which roles can interact with your human task.

There are six possible roles to choose from, and those that appear will depend on the kind of human task that you are working with.

Administrators
Administrators have the authority to perform upper level duties like suspend, terminate, restart, force-retry, and force-complete.
Potential creators
Potential creators can create an instance of the human task, but cannot start it.
Potential starters
Potential starters have the authority to initiate an existing instance. The starter role is subtly different from that of creator, and although a creator can create a new instance, only a starter can start it. In many usage scenarios, the same employee fulfils both roles.
This role is only associated with an invocation task.
Potential owners
Potential owners can claim, work on and complete tasks.
Editors
Editors can work with the content of a task, but cannot claim or complete it. For example, an editor can receive the work item to review a document and add comments, but an editor is not able to finish the task.
Readers
Readers are allowed to view tasks, but cannot work on them. This role can be used in situations where an employee wants to monitor as task without taking any action in it.

Assigning roles to your human task

A role is a set of employees who share the same level of authority. When it comes to working on tasks, the role that the person belongs to defines their authorization.

Human task editor

To create and manipulate tasks that will be assigned to human staff members in the runtime environment, use the human task editor.

The human task editor is a graphical programming environment that you use to configure the interaction between a service and its associated human participants, or between two humans.

Identify the escalation and notification mechanisms available for

2009-06-16T17:50:00.001-07:00

Human Task

Websphere Integration Developer v612

Identify the escalation and notification mechanisms available for human tasks
1. Related links

Identify the escalation and notification mechanisms available for human tasks

An escalation is a notification that is sent out when an expected result from a task has not been achieved within a set period of time. For example, an escalation could be used to alert a manager when a staff member is unable to complete a task by the deadline.

Note: The duration value for a human task is separate from the escalation function. Although the duration value will indicate when a task is due, it will NOT trigger an escalation.

When you create an escalation for your human task, you will need to know the following ahead of time:

The state that the task is in when the escalation period begins (this is also known as the activation state).
The state that you want the task to be in when the escalation period ends (it is when the task is NOT in this expected state at the end of the period that the actual escalation is thrown).
The escalation period, or how long you want the system to wait for the expected state to be reached before notification occurs.
The manner in which the notification takes place.

If you are creating more than one escalation for an activation state, you have two options:

Chained escalation In a chained escalation, the escalations are executed sequentially, or one after the other. In such a case, the first escalation must fully complete before the next one is initiated.
Parallel escalation With a parallel escalation, the escalations are in two separate paths, and are executed at the same time (or in accordance with the escalate after setting as described below).

Implement client interactions for human tasks

2009-06-16T17:49:00.003-07:00

Human Task

Websphere Integration Developer v612

Implement client interactions for human tasks (including API, human task manager, business flow manager)

Implement client interactions for human tasks (including API, human task manager, business flow manager)

Setting up a user interface for your human task

The human task editor provides various client types that you can use to customize a user interface through which users can interact with the tasks in the runtime environment.

A client delivers task-related information to a staff member in the form of an interactive application. You can generate various types of clients for your human tasks, and use the generated clients to customize a user interface through which users can interact with the tasks in the runtime environment. Or, you can use generated clients to quickly demonstrate a human workflow, for example as a proof of concept or prototype.

Using the client generator, you can generate clients for both stand-alone human tasks that exist independently of a business process, and inline human tasks that exist within a business process. You can create one client for all the human tasks in a module, or generate one client per task. You can also generate one client for all human tasks in multiple processes or modules.

You can generate and use multiple web-clients for each human task. You may wish to provide a choice of user interfaces or to provide clients with different functionality for different roles or simply to provide basic clients that can be re-used with a different look and feel. You can also use generated clients at the same time as the Business Process Choreographer explorer; the effect on the human task instance is the same even though the user interface is different.

Before you begin: Client types and prerequisites

These are the types of clients that you can configure or generate for your human tasks. This topic contains useful information that you may need before you proceed to generate your client.

Human Task Manager

A human task manager provides services to run human tasks within an application server.

Business Flow Manager settings

A Business Flow Manager provides services to run business processes within an application server.

Design human tasks

2009-06-16T17:49:00.001-07:00

Human Task
Websphere Integration Developer v612
Contact us...

Design human tasks

Design human tasks

A human task is, quite simply, a unit of work that involves a human. Quite often, this task requires that the human interact with other services, and thus becomes a task within a larger business goal.

Scenario: Human workflow management

Most business processes involve people in some way. This scenario provides a very high-level view of the concepts and steps for a process in which people play a significant or dominant role. See the documentation under Developing integration applications > Using people interactionsfor detailed information about the topics introduced here.

A process is composed of tasks. A human task is, quite simply, a unit of work that involves human intervention.

Human workflow management considerations

When you are planning a project that includes people in the process, there are some concepts that you need to understand in order to make sensible decisions.

Inline and stand-alone human tasks

There are two ways to implement a human task. Here is a discussion on when each type should be used.

Life cycle of a human task

A human task goes through a number of stages from its start to its finish.

Configure components to emit CEI events

2009-06-16T17:42:00.005-07:00

Component Implementation

Websphere Integration Developer v612

Configure components to emit CEI events

Configure components to emit CEI events

You monitor events in WebSphere® Process Server to assess problem determination, to tune performance, and to measure the effectiveness of your business processes.

WebSphere Process Server event monitoring capabilities include performance monitoring and service component monitoring.

The Common Event Infrastructure (CEI) is used to provide basic management services for events. The format of those events is defined by the Common Base Event specification.

Event generation and monitoring

In WebSphere® Integration Developer, you can enable 6.0.2 event generation or 6.1 monitor model generation for many of the business integration components produced by the editing tools, such as business processes and business rules. The primary tool for enabling event generation and monitoring in WebSphere Integration Developer is the event monitor.

In any editor where the event monitor resides, you can select one or more monitorable component elements and then use the event monitor to choose the events that you want to generate and monitor for the selected elements. For example, in the business process editor, you could select a Receive activity in a business process and then use the event monitor to choose the Activity Started and Activity Stopped events for generation and monitoring. A complete list of monitorable components and elements is found in the topic "Monitorable components and elements in WebSphere Integration Developer."

Before you work with the event monitor, you should have a basic understanding of the following event-related concepts:

Common Event Infrastructure
Common Base Event
Business events

Monitorable components and elements in WebSphere Integration Developer

In WebSphere® Integration Developer, you can use the event monitor to enable event generation and monitoring for a wide variety of business integration components and their elements.

The event monitor can be invoked from the Properties view of the assembly editor or from the Properties view of any of the following component editors:

Business process editor
Business state machine editor
Business object mapping editor
Business rule group editor
Interface mapping editor
Human task editor
Selector editor

If you want to enable event monitoring at the SCA level, then you must open the event monitor in the assembly editor and select one or more component or import interface operations to monitor.

If you want to enable event monitoring at the component level, then you can open the event monitor in one of the component editors (such as the business process editor) and select one or more component elements to monitor.

You can configure one or more components to emit CEI events at different levels:

Assembly diagram level
Component level
Component element level

Opening the event monitor

In WebSphere® Integration Developer, you can use the event monitor to enable (or disable) event and monitor model generation and monitoring. The event monitor is accessible as a properties page in many of the WebSphere Integration Developer editors.

The method you use to open the event monitor differs depending on whether you want to enable event monitoring at the SCA level in the assembly editor or at the component level in one of the component editors.

Specifying event properties for component elements

In the event monitor, you can specify event properties for individual component elements that you have selected in a component editor. For example, you can choose whether to generate all events, or selected events, or no events for a component element. You can also specify other event properties for a selected component element, such as the content level and transaction behavior.

Specifying event properties for components

In the event monitor, you can globally specify event properties for all monitorable elements in a component. For example, you can specify 6.1, 6.0.2, or hexBinary format for the generated events associated with all of your component elements. And if you are specifying event properties for a business process, you can enable or disable the default events for all of your business process activities.

Configure a selector to dynamically invoke SCA components

2009-06-16T17:42:00.003-07:00

Component Implementation
Websphere Integration Developer v612
Contact us...

Configure a selector to dynamically invoke SCA components

Configure a selector to dynamically invoke SCA components

A selector is a dispatch pattern you use to dynamically determine which implementation of a component to invoke at runtime. Like a rule group, a selector has date range entries, selection criteria, and a default destination. You select a destination in a selector the same as your would for a rule group. That is, when a selector is invoked, it selects a destination using the selection criteria and date range entries. A destination could be any service-oriented component.

One major difference between a selector and a rule group is that the destination of a selector can be any service component, while a destination in a rule group can be only a rule set or decision table. In other words, a selector can dynamically re-route a service call to any other component at runtime.

You can call a selector from any of your service-oriented components. The selector’s job is to use dynamic information to determine which component should be called to do the work. The set of destination components is also configurable, allowing you to provide additional destinations at runtime.

Creating a selector

To create and configure a selector to dynamically invoke SCA components, follow the instructions below:

In the workbench, switch to the business integration perspective.
If you have already created a module, select it in the business integration view.
From the main menu, click File > New > Selector.
In the New Selector window, specify a module, a folder and a name for the new selector, and click Next.
In the select an interface window, browse to an existing interface or click New to create one. If you create a new interface here, you will have to create an operation for it before you can use it in the rule group. Create this operation using the interface editor.

This creates a selector, and launches it in a new editor.

Selector editor
The selector editor is a graphical editor that you use to visually choose and schedule the processing of components within WebSphere Integration Developer.
Specifying a target component for your selector
The target component is the destination where the selector will direct the implementation.
Choosing dates and times
The selector can be used to schedule the routing of an operation to a specific component for a specific date and time.
Customizing algorithms for date and time selection
When you want to specialize the date and time selection criteria, you can create your own custom algorithm.
Standards for date and time selection in a selector
There are a number of ways you can configure your selector. Here are some suggestions that are based on the number and nature of the available destinations.

Parent topic: Choosing components with the selector editor

Related concepts

Component selection

Choosing components with the selector editor

To visually determine where to route operations within the WebSphere® Integration Developer family of tools, use the selector editor.

The selector editor presents a tabular display of potential destinations. Use this tool to graphically select them, and specify which ones to use and when.
Note: Selectors can only be deployed to the WebSphere Process Server.

Click on any of the links shown below to learn more about that topic.

Component selection
The selector editor is used to route an operation from a client component to one of several possible target components.
Planning for the future with the selector editor
When you are designing your business solution, it is sometimes a good idea to include a selector even though it is not immediately going to be used.
Choosing components without using a selector
When used with time-based routing, the selector is, in essence, a scheduling tool. You use it to route an operation to a component for a specific period of time. To achieve the same results on a daily, or a periodic basis, you can use a combination of a business process and a rule set as described here.
Creating a selector
This topic provides instructions on how to create a selector.
Refactoring a selector
When you refactor parts of your selector, dependencies on those parts are automatically and universally updated throughout the product as a whole.
Generating documentation for your selector
If you need a high level synopsis of your selector, including how it interacts with other resources within the same project, you can create a customized report using the documentation generator.
Using a selector to delegate
The selector can also be used as a tool for general delegation as described in this topic.
Replacing an existing component with a selector
If you are making changes to an existing business integration solution, you may find it useful to replace an existing component with a selector.
Managing multi-operational interfaces
Sometimes a selector's component destination may not need to implement all of the operations in an interface, so here is a possible solution.

Use interface maps to facilitate the wiring between two SCA compo

2009-06-16T17:42:00.001-07:00

Component Implementation

Websphere Integration Developer v612

Use Interface maps to facilitate the wiring between two SCA components

Use Interface maps to facilitate the wiring between two SCA components

SCA components can only communicate with one another if they have matching interfaces. If they don't, then they cannot communicate.

An interface map resolves differences between the interfaces of interacting components to enable them to communicate with one another.

Differences between interfaces in components that need to interact with one another are common. These differences arise because in WebSphere® Integration Developer you are often assembling components that were created for different applications. Reusing them to create a new application is one of WebSphere Integration Developer's strengths, since otherwise you would be recoding similar components. But you typically must make some adjustments.

Creating interfaces

Interfaces are the means of exchanging data between components. In this section, you will learn about the relationship between interfaces and implementations, the parts of an interface, different ways of starting the interface editor and developing an interface, and see some tutorials and samples about interfaces.

Interfaces
An interface provides the input and output of a component. It is created independent of the internal implementation of the component.
Interface editor
You create interfaces with the interface editor. How you use the interface editor to create interfaces and work with interfaces is discussed in this section.
Developing interfaces: top-down
Top-down development means building the entire interface yourself, meaning you have no initial interface.
Developing interfaces: bottom-up
Bottom-up development means starting with an interface that was created outside of WebSphere® Integration Developer, importing it into a module and then, if necessary, modifying it in the interface editor.
Developing interfaces: meet-in-the-middle
Meet-in-the-middle development means taking an already created interface and adding it to a component that has been implemented but has no interface.
Inline schemas
Inline schemas are a way of including the schema within a WSDL file rather than specifying that it be imported.

Mapping interfaces

An interface provides the means to interact with a component. It is independent of the internal implementation of the component. In WebSphere Integration Developer, you can use the interface mapping editor to resolve and reconcile the differences between the interfaces of interacting components.

Note:

Interface maps can be used only in modules for business services, not for mediation services.

The following topics provide the conceptual information about and step-by-step instructions for mapping interfaces:

Interface maps
Interface maps are created in the interface mapping editor to resolve and reconcile differences between the interfaces of interacting components.
Interface mapping editor
With the interface mapping editor, you can build and edit interface maps in a graphical mode.
Operation mappings
Each operation mapping maps one operation in the source interface to one operation in the target interface.
Parameter mappings
Parameter mappings map parameters in the source operation to parameters in the target operation.
Creating interface maps
Using the interface mapping editor, you can establish correspondence between the operations and parameters of interfaces, thereby permitting the exchange of data between them, by creating interface maps.
Adding event monitoring to interface maps
The event monitor generates and monitors events. Event monitoring can be set for operation mappings and parameter mappings in interface maps.
Hints and tips for the interface mapping editor
This topic provides troubleshooting tips and other helpful information to consider when using the interface mapping editor.

Create business rule groups

2009-06-16T17:41:00.007-07:00

Component Implementation

Websphere Integration Developer v612

Create business rule groups

Create business rule groups

Business rules complement business processes and state machines. If there is condition with a variable, for example, a business rule can change the value in that variable at run time. Created by a visual programming language, a business rule makes a decision based on context. The decision can be simple or complex. Business rules are nonprocedural and the rules can be changed independently of an application.

Creating a rule group

A rule group is a container for business rules (ruleset or decision table business rules). It also controls the timing and implementation of these business rules.

In the workbench, switch to the business integration perspective.
From the main menu, click File > New > Rule Group.
In the New Rule Group window, specify a module (or create one if necessary by clicking New), a folder and a name for the new rule group, and click Next.
In the select an interface window, browse to an existing interface or click New to create one. If you create a new interface here, you will have to create an operation using the interface editor before you can use it in the rule group.

This creates a rule group, and launches it in a new editor. Click any of the topics listed below to configure your new rule group.

Rule group editor
A rule group controls the timing and implementation of business rules.
Specifying the rule logic for a rule group
The rule logic is either a rule set or a decision table that is implemented at the appropriate time by the rule group. The rule logic is the destination of the rule group.
Scheduling rules using the rule group editor
The rule group editor can be used to schedule the running of a specific rule for a specific date and time.
Customizing algorithms for date and time selection
When you want to specialize the date and time selection criteria, you can create your own custom algorithm.
Using rule set names in a rule group
Each operation in a rule group contains a rule logic table, which maps a set of date ranges to a destination rule set or decision table. To avoid confusion, it is always a good practice to use rule set and decision table names which are unique within the operation. If the same name is used twice, it is more difficult to see that there are actually two different destinations.

Creating a rule set

A rule set captures decision-making business logic in the form of a series of if-then statements.

In the workbench, switch to the business integration perspective.
From the main menu, click File > New > Rule Set.
In the New Rule Set window, specify a module (or create one if necessary by clicking New), a folder and a name for the new rule set, and click Next.
In the select an interface and operation window, browse to an existing rule group, or click New to create one. If necessary, use the drop down lists to select a different interface and operation.
Click Finish.

This creates a rule set, and launches it in a new editor. Click any of the topics listed below to configure your new rule set.

Rule set editor
A rule set captures decision-making business logic in the form of a series of if-then statements.
Adding a variable to a rule set
Variables store the data that are used by a rule set.
Creating an if-then rule in the rule set editor
An if-then rule determines what action to run according to the condition of the incoming message.
Creating an action rule in the rule set editor
An action rule determines what action to run no matter what the incoming message is.
Creating rule set templates
Use a rule set template to define the implementation and parameters for an if-then or action rule. This template can then be used to create new instances of the same rule using different parameters.
Creating a new rule from a template in the rule set editor
Rules can be created from existing templates. In this way, you can create a similar rule without having to redefine the implementation, and by making changes to the parameters within the constraints specified.
Letting a Web user override the default values in a rule set
In a rule set, there are often situations where you want to allow a Web user to override the default output value as programmed. To capture this in a rule set, use the following approach.
Structuring an ordered rule set for modification
In some rule sets, there may be a tight dependency between the rules and their order of processing. This is the nature of sequential execution. Here are some suggestions on how to plan for possible changes to an ordered rule set.
Calling one rule set from another one
Currently, you cannot call one rule set from another directly, you can only call out to operations which exist in another component. To work around this, separate the rule sets into two distinct rule groups, and then invoke one from the other.

Creating a decision table

A decision table captures multi-conditional decision-making business logic in tabular format.

In the workbench, switch to the business integration perspective.
From the main menu, click File > New > Decision Table.
In the New Decision Table window, specify a module (or create one if necessary by clicking New), a folder and a name for the new decision table, and click Next.
In the select an interface and operation window, browse to an existing rule group, or click New to create one. If necessary, use the drop down lists to select a different interface and operation.
If you want to configure the layout of the decision table, click Next.
In the Decision Table layout window, use the settings to determine how the decision table will appear in the editor. The preview shows what the table will look like.
Click Finish.

This creates a decision table, and launches it in a new editor. Click any of the topics listed below to configure your new decision table.

Decision table editor
A decision table captures multi-conditional decision-making business logic in tabular format.
Working with conditions in a decision table
A condition is an evaluation of the incoming message that looks for a specific value.
Configuring actions in a decision table
An action is an operation that is executed when the appropriate conditions are met.
Working with initialization action rules
An initialization action rule automatically performs an operation of some kind when data is first being passed to a decision table.
Using an otherwise condition
An otherwise condition is used in a decision table for situations when the specified conditions will not be met. The otherwise condition cause a rule to fire when no other evaluation can be resolved.
Changing the layout of your decision table
Some decision tables are easier to understand if you change their orientation.
Creating decision table templates
Use a template to define the implementation and parameters for either a condition or an action value in a decision table. This template can then be used to create new cells with the same format, but with different parameter values.
Using templates in your decision table
The individual cells of your decision table can be populated with an existing template for the value. In this way, you can create a similar expression without having to redefine the implementation, and by making changes to the parameters within the constraints specified.
Editing a decision table template
This topic provides instructions on how to make changes to an existing templates.

Suggest transaction boundaries within a business process

2009-06-16T17:41:00.005-07:00

Component Implementation

Websphere Integration Developer v612

Suggest transaction boundaries within a business process

Suggest transaction boundaries within a business process

Transactional behavior of business processes

Business processes are executed as part of transactions. The navigation of a business process can span multiple transactions in the case of long-running processes, or happen as part of one transaction in the case of microflows. Such navigation transactions can be triggered by external requests, internal messages, or responses from asynchronous services. When a transaction starts, the required activities are performed according to the process definitions. Invoked services can participate in the transaction.

A business process runs under one of two execution modes:

Microflows
run under a single transaction in a short period of time.
Long-running business processes
run in a series of chained transactions over days, months, or even years. Long-running processes can be optimized with respect to transaction boundaries.

Business process developers can declare transaction behavior for invoke, human task, and snippet activities:

Commit before
guarantees that the activity runs in a new transaction.
Commit after
guarantees that the current transaction is committed after executing the activity.
Requires own
guarantees that the activity runs in a new transaction and the current transaction is committed after executing the activity.
Participates
behavior states that the activity runs within an existing transaction, if one is available.

Setting up a process as long-running

Transaction boundaries are only applicable to long-running processes containing more than one transaction.

To setup a process as long-running, just check the Process is long-running checkbox.

Setting up Human Task transaction behaviour

Set the transaction behaviour choices on the Properties/Server page.

Setting up Invoke transaction behaviour

Set the transaction behaviour choices on the Properties/Server page.

Setting up Snippet transaction behaviour

Set the transaction behaviour choices on the Properties/Server page.

Create custom Java logic using the visual snippet editor

2009-06-16T17:41:00.003-07:00

Component Implementation

Websphere Integration Developer v612

Create custom Java logic using the Visual snippet editor
1. Customizing behavior with visual snippets
2. Related links

Create custom Java logic using the Visual snippet editor

Customizing behavior with visual snippets

To visually define custom behavior, use the visual snippet editor.

The visual snippet editor displays a diagrammatic representation of the Java™ programming language. Use this tool to graphically create and manipulate snippets of Java code.

Click on any of the links shown below to learn more about that topic.

Custom behavior
There are situations when a user has the opportunity to specify custom behavior within the context of one of the WebSphere® Integration Developer family of tools.
Visual snippet editor
The visual snippet editor is a diagrammatic programming environment that you use to graphically create and manipulate Java code.
Using the visual snippet editor to write Java code
When should you use the visual snippet editor to compose Java code instead of writing it yourself?
The building blocks of the visual snippet editor
Compose your own visual snippet using a combination of the following building blocks.
Creating a custom visual snippet
To create a new custom visual snippet, follows these instructions.
Using inline expressions for simple equations
When you are coding an expression in the visual snippet editor, there are a couple different ways that you can compose the expression.
Using mapping service snippets
When you want to transform data in a business object from one format to another using the visual snippet editor, you can use one of the three mapping service snippets provided.
Refactoring a visual snippet
When you refactor parts of your visual snippet, dependencies on those parts are automatically and universally updated throughout the product as a whole.
Configuring a custom event in a visual snippet
A custom event is a specific business-related message that can be declared in the visual snippet editor to be emitted in the runtime environment.

Implement an event handler in a business process

2009-06-16T17:41:00.001-07:00

Component Implementation

Websphere Integration Developer v612

Implement an event handler in a business process
1. Using event handlers
2. Related links

Implement an event handler in a business process

Using event handlers

Event handlers are constructs that respond to external stimuli with an appropriate defined action.

In the Graphical User Interface environment, events usually signify that the user has made a demand on the system, and the application must respond to it appropriately. In such cases, a receive or pick activity can usually be used, but they have limitations. For example, they can only be used during normal execution of a process, and they can only be implemented once. This effectively means that you have to know ahead of time how many events to expect, and when to expect them.

Event handlers make a business process more dynamic by dealing with events that happen independently of, or asynchronously to the processing of the application. They can respond to events that happen at any time during an application's lifetime, or as many times as those events repeat.

Implement error handling within a business process

2009-06-16T17:40:00.005-07:00

Component Implementation

Websphere Integration Developer v612

Implement error handling within a business process
1. Dealing with faults in your business process
2. Related links

Implement error handling within a business process

Dealing with faults in your business process

There are a number of ways of dealing with potential faults in your business process.

A fault is any exceptional condition that can change the normal processing of a business process and, if not handled, can lead to unexpected conditions or results. A well designed process is one that anticipates possible faults with fault handlers that are designed to lead to predictable outcomes. To this end, when you are planning your process, you will need to be able to anticipate as many potential control issues as possible, predict what the result of the exception will be, and what action must take place.

Implement error handling within a mediation

2009-06-16T17:40:00.003-07:00

Component Implementation

Websphere Integration Developer v612

Implement error handling within a mediation
1. Error handling in the mediation flow
2. Related links

Implement error handling within a mediation

Error handling in the mediation flow

The following are the various ways to deal with errors in the mediation flow, including ways to use the Stop and Fail mediation primitives, where to look for fail information in the message, and how to handle WSDL faults.

Configure BPEL activities using the properties view

2009-06-16T17:40:00.001-07:00

Component Implementation

Websphere Integration Developer v612

Configure BPEL activities using the properties view

Configure BPEL activities using the properties view

Building business processes

To create and manipulate business processes, use the business process editor.

The BPEL-based business process editor displays a visual representation of a business process written in the Business Process Execution Language. It builds upon the existing functionality of the language, and adds a number of useful extensions. You use this tool to visually create and manipulate business processes.

Business process editor

The business process editor is a graphical programming environment that you use to visually create and manipulate business processes.

To configure BPEL activities, use the properties view.

The properties view displays properties that are relevant to the object that is currently selected on the canvas or the tray. You can click on the tabs to the left of this view to toggle through the pages. Some pages display properties in tabular format, and you can add or modify these properties by clicking the appropriate cell and then interacting with the graphical interface that appears. Properties marked with an * are mandatory.

The contents of the page will differ on the activity or object chosen.

Administration tab: business process editor
This topic includes a description of each of the fields on the Administration tab of the Properties view.
Authorization tab: business process editor
This topic includes a description of each of the fields on the Authorization tab of the Properties view.
Compensation tab: business process editor
This topic includes a description of each of the fields on the Compensation tab of the Properties view.
Correlation tab: business process editor
This topic includes a description of each of the fields on the Correlation tab of the Properties view.
Description tab: business process editor
This topic includes a description of each of the fields on the Description tab of the Properties view.
Details tab: business process editor
This topic includes a description of each of the fields on the Details tab of the Properties view.
Environment tab: business process editor
This topic includes a description of the Environment tab of the Properties view.
Expiration tab: business process editor
This topic includes a description of each of the fields on the Expiration tab of the Properties view.
Import tab: business process editor
This topic includes a description of each of the fields on the Import tab of the Properties view.
Java Imports tab: business process editor
This topic includes a description of each of the fields on the Java Imports tab of the Properties view.
Join Behavior tab: business process editor
This topic includes a description of each of the fields on the Join Behavior tab of the Properties view.
Link Evaluation Order tab: business process editor
This topic includes a description of each of the fields on the Link Evaluation Order tab of the Properties view.
Query properties tab: business process editor
This topic includes a description of each of the fields on the Query properties tab of the Properties view.
Repeat tab: business process editor
This topic includes a description of each of the fields on the Repeat tab of the Properties view.
Server tab: business process editor
This topic includes a description of each of the fields on the Server tab of the Properties view.

Develop mediation flows using mediation primitives and Service Me

2009-06-16T17:39:00.001-07:00

Component Implementation

Websphere Integration Developer v612

Develop mediation flows using mediation primitives and Service Message Objects

Develop mediation flows using mediation primitives and Service Message Objects

Mediation flows overview

Mediation service applications intercept and modify messages that are passed between existing services (providers) and clients (requesters) that want to use those services. Mediation services are implemented using mediation modules that contain mediation flows.

Mediation modules can be deployed on the WebSphere® Enterprise Service Bus or the WebSphere Process Server.

Mediation flow: Hello world

Get started with mediation flows. Create and test a basic mediation flow.

Mediation Flow editor

The Mediation Flow editor is a graphical programming environment that you use to visually create and manipulate mediation flows.

You can visually compose a mediation flow by defining the source and target operations in the Operation connections section, and then visually adding and wiring mediation primitives in the flow section. You then add properties for the primitives in the properties view.

Creating a mediation flow

A mediation flow consists of a sequence of processing steps that are run by mediation primitives when an input message is received. Mediation flows can only be contained in mediation modules.

Use the business process editor to create a business process component

2009-06-16T17:38:00.003-07:00

Component Implementation

Websphere Integration Developer v612

Use the business process editor to create a business process component (including path conditions, activities, snippets, etc.)

Use the business process editor to create a business process component (including path conditions, activities, snippets, etc.)

Overview

The business process editor is a graphical programming environment that you use to visually create and manipulate business processes.To illustrate how to use the business process editor, we will complete the base business process generated by the tooling:

Before ()
This is a generated business process. We will complete this to look line the one below (after).
After ()
This is the completed business process.

The building blocks of the business process editor

Compose your own business process using a combination of the building blocks listed below:

Partners

Partners are the external users or services that interact with the process.

You can create interface and reference partners. Add an interface Partner when you want to receive something in your process, and add a reference Partner when you want to send something to a Partner.

Variables

Variables store the messages that are exchanged between the partners in a process and the data that is used in its business logic.

A variable belongs to the scope in which it is declared. If it is created in the global process scope then it is a global variable, and thus visible to the process as a whole. Those that are created within nested scopes are called scoped or local variables, and can only be seen by objects within the scope in which it was created.

Correlation artifacts

Correlation sets are used in runtime environments where there are multiple instances of the same process running. The sets allow two partners to initialize a business process transaction, temporarily suspend activity, and then recognize each other again when that transaction resumes.

Activities

A business process is any course of action or procedure that an organization follows to achieve a larger business goal. When you break it down, a business process is actually a series of individual tasks that are executed in a specific order. You build a business process by adding and manipulating these activities in the business process editor.

Activities are the individual business tasks within the process that compose the larger business goal.

Once you've created a new process, you are ready to create the activities that will run the task to be performed by that process.

These tasks or activities are grouped as follows: ()

Build the Business Process

Follow these steps to build the completed business process as shown above.

Use the Business State Machine editor to create a business proces

2009-06-16T17:38:00.001-07:00

Component Implementation
Websphere Integration Developer v612
Contact us...

Use the business state machine editor to create a business process component (including events, guards, actions and correlation sets)

Use the business state machine editor to create a business process component (including events, guards, actions and correlation sets)

Overview

The business state machine editor is a graphical programming environment that you use to visually create and manipulate business state machine .To illustrate how to use the business state machine editor, we will complete the base business state machine generated by the tooling:

Before ()
This is a generated business process. We will complete this to look line the one below (after).
After ()
This is the completed business state machine.

Building state machines

To create and work with business state machines, use the state machine editor.

The business state machine editor displays a visual representation of a state-based, event driven, business application. You use this tool to visually create and manipulate business state machines.

Note: Business state machines can only be deployed to the WebSphere® Process Server.

The building blocks of the business state machine

Compose your own business state machine using a combination of the following building blocks.

Using the Business State Machine Editor

Here are some of the functions you can do with the business state machine editor.

How to generate a State Machine implementation
How to add a state
How to transition from one state to another state

How to add a variable-State Machine

How to setup the initial state

How to add an operation to a transition

How to add an action to a transition

How to add an Entry element to a State

How to add a condition to a transition

How to add a Visual Snippet - State Machine

How to add a correlation set - State Machine

Work with and understand generated artifacts

2009-06-16T17:26:00.003-07:00

Programming Model and Design

Websphere Integration Developer v612

Work with and understand generated artifacts

Work with and understand generated artifacts

Module

When you create a module, WID automatically generates J2EE artifacts.

Business Integration View	J2EE View

J2EE View details

NewModule	NewModuleApp

NewModuleEJB

Support iterative development and synchronization of applications

2009-06-16T17:26:00.001-07:00

Programming Model and Design

Websphere Integration Developer v612

Support iterative development and synchronization of applications and business models with Business Process Management (BPM) tools
1. Phases of modeling for iterative development
2. Related links

Support iterative development and synchronization of applications and business models with Business Process Management (BPM) tools

You can use the following tools to support iterative development and synchronization of applications and business models.

With these tools, you can model a business solution, compose and assemble the solution, implement it, deploy it to a runtime server, and monitor business metrics of the solution on the server. You can continue to refine the model and the implementation iteratively.

The WebSphere® family of products allows you to develop a model of the application that you want to implement and then import that model into WebSphere Integration Developer where you can refine it into a sophisticated application. You can continue to develop both the model and the application and keep them synchronized.

Phases of modeling for iterative development

You can model a process and develop and test its implementation in parallel, using synchronization tools to keep the model and the application synchronized. Some of the work requires a good understanding of the artifacts that are used in the integration environment.

Package assets within modules, mediation modules and libraries

2009-06-16T17:25:00.003-07:00

Programming Model and Design

Websphere Integration Developer v612

Package assets within modules, mediation modules and libraries to support effective component reuse and application maintainability

Package assets within modules, mediation modules and libraries to support effective component reuse and application maintainability

Modules

A module is a container for your services and is both a project in the WebSphere Integration Developer workbench, and the unit of deployment to the WebSphere Process Server. That means that any solution that you build will be deployed to the server as one or more modules. For those who are familiar with J2EE, a module is packaged and deployed as an enterprise archive (EAR) file. One of the advantages of the Service Component Architecture is that you don't have to be concerned with the underlying packaging. A module provides services that can be used by other modules and that can be accessed by external clients used by your partners or customers. A module is a collection of components, imports and exports.

Mediation modules

Mediation modules contain mediation flow components. A single mediation module can contain only one mediation flow component.

Libraries

Often, interfaces, business objects, business object maps, events, relationships, roles, and Web service ports need to be shared so that resources in several modules can use them. The library is a project that is used to store these resources.

Unlike modules or mediation modules, library projects can share resources. In order for a module or mediation module to use the resources from a library, the library has to be added as a dependent to the module. A library cannot be deployed by itself. However, you can add a library to the module and select to deploy it with the module. Also, you can add library dependencies to a library; for example, if one library uses resources in another library, then you would need to add the library dependency.

Effective component reuse and application maintainability

Artifacts in a library are public. Artifacts in a module are private. Designers of WebSphere® Integration Developer applications should organize artifacts by taking into consideration logical function and visibility. For example, related data types that are used by various pieces of a system should be placed into a library. Other modules can then easily reuse this library. Only one copy of each artifact needs to be created and maintained using this method. Likewise, related business logic features of the application should be grouped into modules. Componentizing an application in this way will yield a more flexible, easily maintained application. Adding new features to the application will also be easier.

Determine the implications of process or component design decisions

2009-06-16T17:25:00.001-07:00

Programming Model and Design

Websphere Integration Developer v612

Determine the implications of process or component design decisions (performance, component versioning, adaptability, complexity)

Determine the implications of process or component design decisions (performance, component versioning, adaptability, complexity)

The building blocks of a business solution are Service Components Architecture (SCA) components wired together to form modules that can be deployed to the WebSphere® Process Server. The WebSphere Integration Developer's assembly editor lets you build applications by assembling the SCA components.

Components are the parts of the module that are the actual services. On the inside, they are implemented using implementation types, which include business processes, state machines, human tasks, and others. The WebSphere Integration Developer tools generate implementations that the assembly editor can use for components. The structure of the component is simple; it has the following parts:

An implementation
Optionally, one or more interfaces
Optionally, one or more partner references

Performance

If you require high performance, put components in the same module.

Components within a module are collocated for performance, and can pass their data by reference. Components in the same module can talk to one another directly while components in different modules can only talk to one another indirectly via export/imports. Direct calls are faster than indirect calls. In addition, passing data by reference is significantly faster than passing data by value.

Component Versioning

When you need to run different versions of the same component at the same time, use component versioning.

Component versioning is available only for the following components:

Business process components
You can create new versions of your business process, so that multiple versions of those same processes can co-exist in a runtime environment.
State machine components
You can create new versions of your business state machine, so that multiple versions of those same state machines can co-exist in a runtime environment.
Human task components
You can create new versions of your human task, so that multiple versions of those same tasks can co-exist in a runtime environment.

Adaptability

If you want your process/component to be readily adaptable to changing business conditions, implement them as business rules and/or selectors.

Business rules
Business rules within a business process allow applications to respond quickly to changing business conditions.

Business rules greatly improves application flexibility. They externalize and manage business logic separately from the main business process. They allow you to make changes at runtime to keep up with the evolving on-demand business environment.
Selectors
You can dynamically invoke a component using selectors.

You can call a selector from any of your service-oriented components. The selector’s job is to use dynamic information to determine which component should be called to do the work. The set of destination components is also configurable, allowing you to provide additional destinations at runtime.

Complexity

A component's complexity depends on which implementation type you select to implement it.

You can implement a component using any of the following implementation types.

Java objects
An implementation of a component in Java™ is referred to as a Java object.
BPEL process
A BPEL process component implements a business process.
State machines
A state machine is an alternative way of creating a business process. A state machine is suited for processes related to changing states rather than a flow of control. A state defines what an artifact can do at a point in time. A state machine is an implementation of this set of states.
Business rules
Business rules complement business processes and state machines. If there is condition with a variable, for example, a business rule can change the value in that variable at run time. Created by a visual programming language, a business rule makes a decision based on context. The decision can be simple or complex. Business rules are nonprocedural and the rules can be changed independently of an application.
Selectors
Integrated applications contain many ways to interact. A selector is used to route an operation from a client application to one of several possible components for implementation.
Human task
A human task component implements a task done by a person. It represents the involvement of a person in a business process.
Interface map
An interface map resolves differences between the interfaces of interacting components.
Mediation flow
Mediation is a way of mediating or intervening dynamically between services. A mediation flow implements a mediation.
Stand-alone references
Stand-alone references are references to applications that are not defined as Service Component Architecture components (for example, JavaServer Pages or servlets). Stand-alone references permit these applications to interact with Service Component Architecture components.

Design effective mediation flows

2009-06-16T17:15:00.001-07:00

Programming Model and Design

Websphere Integration Developer v612

How to Design effective mediation flows
1. Mediation flows overview
2. Related links

How to Design effective mediation flows

Mediation is a way of mediating or intervening dynamically between services. A mediation flow implements a mediation.

Mediation has several useful functions. For example, you can use mediation when you need to transform data from one service into an acceptable format for a subsequent service. Logging lets you log messages from a service before they are sent to the next service. Routing lets you route data from one service into an appropriate service determined by the mediation flow. A mediation operates independently of the services it connects to. A mediation in the assembly editor appears as a mediation flow component between exports and imports.

Mediation flows overview

Determine the best component implementation type and characteristics

2009-06-16T17:14:00.001-07:00

Programming Model and Design

Websphere Integration Developer v612

Determine the best component implementation type and characteristics when building a business process

Determine the best component implementation type and characteristics when building a business process

Service implementation types are the implementations of the service components. A BPEL process component implements a business process. A State machine is an alternative way of creating a business process. A state machine is suited for processes related to changing states rather than a flow of control. A state defines what an artifact can do at a point in time. A state machine is an implementation of this set of states.

Process types

You can use the business process editor to build either microflows or long-running processes.

Choosing between a business process and a state machine

You can model service-oriented applications using either the process editor or the state machine editor

Design and use interfaces

2009-06-16T17:04:00.001-07:00

Programming Model and Design
Websphere Integration Developer v612
Contact us...

Design and use interfaces

Design and use interfaces

Interfaces

Interfaces are the means of exchanging data between components. An interface provides the input and output of a component.

The inputs and outputs of each component, specified by the interface, determine which data can be passed from one component to another. An interface is created independent of the implementation of the component. An interface may also be created for a component that has no implementation; that is, the implementation will be done later.

Creating interfaces

Interface maps

Interface maps are created in the interface mapping editor to resolve and reconcile differences between the interfaces of interacting components.

Design and use business objects and the business object framework

2009-06-16T17:03:00.003-07:00

Programming Model and Design

Websphere Integration Developer v612

Design and use business objects and the business object framework API when developing a solution

Design and use business objects and the business object framework API when developing a solution

Business objects

Business objects define the data flowing between components.

They are containers for application data, such as a customer or an invoice. Data is exchanged between components by business objects. The underlying structure of a business object is an XML schema definition (XSD).

A business object contains fields which have a name, a type (scalar type or another business object), a default value (for scalar types) and cardinality. Business objects can extend (define a superset of fields) other business objects through parent/child relationships, however, a business object can only inherit from a single parent. These objects can also be used in conjunction with each other to perform a task.

Business object framework API

In WebSphere Process Server, the business object framework is made up of the following elements:

Business object definition
Business graph definition
Business object metadata definition
Business object services (service APIs)

Service Data Objects (SDO)

Service data objects complement Service Component Architecture. Service Component Architecture defines the services as components and the connectivity between them. Service data objects define the data flowing between components.

Each component passes information as input and output. When a service is invoked, data objects are passed as an XML document with document literal encoding when using a WSDL port type or as a Java™ object when using a Java interface. Data objects are the preferred form for data and metadata in Service Component Architecture services. Similar to components, service data objects separate the data object from its implementation. For example, a component interacts with purchase orders while the purchase order itself might use JDBC, EJB, and so on, to perform the updates to the data. Service data objects let the integration developer focus on working with business artifacts. In fact, service data objects are transparent to the integration developer. They are defined by a service data objects Java Specification Request (JSR).

Service Message Objects (SMO)

Service message objects are enhanced business objects that include the application data and header information related to the transport protocol used to invoke a service such as SOAP or JMS. A service message object is composed of a body that contains the application data (also known as the payload or operation message) in a business object, and headers containing additional context information.

Service message objects are used inside mediation flow components. When a mediation flow component is invoked, the business object that is input to the mediation flow is wrapped with additional context and header information and becomes a service message object. This contextual information, such as SOAP header information can be accessed from within the mediation flow component.

Service Data Objects and business objects

Service Data Objects and business objects define the data flowing between components that are defined in Service Component Architecture.

The Service Data Object (SDO) technology is an open standard for enabling applications to handle data from heterogeneous data sources in a uniform way. SDO incorporates J2EE patterns but simplifies the J2EE data programming model.

Part of the IBM® WebSphere® Application Server capabilities that are built into WebSphere Process Server, SDOs provide a framework for data application development that simplifies the J2EE data programming model.

WebSphere Process Server includes business objects, which are enhanced SDOs, based on the data-access technology. SDOs provide a universal means of describing disparate data (for example, JDBC ResultSet and XML Schema described data). Business objects include some extensions that are important for integration solutions and are used to further describe the data that is being exchanged between Service Component Architecture services. Business objects are part of the Service-oriented architecture (SOA) core of WebSphere Process Server.

A business object is a set of attributes that represent a business entity (such as Employee), an action on the data (such as a create or update operation), and instructions for processing the data. Components of the integration application use business objects to exchange information and trigger actions. Business objects are flexible because they can represent many kinds of data. For example, in addition to supporting the data canonicalization model of traditional integration servers, they also can represent data returned from a synchronous EJB Session Bean facade or a synchronous business process, and then they can be bound to IBM WebSphere Portal portlets and JSF components.

Business objects are the primary mechanism for representing business entities, or documenting literal message definitions, enabling everything from a simple basic object with scalar properties to a large, complex hierarchy or graph of objects.

In WebSphere Process Server, the business object framework is made up of the following elements:

Business object definition
Business graph definition
Business object metadata definition
Business object services (service APIs)

A business object definition is the name, set of ordered attributes, properties, version number, and application-specific text that specify a type of business object. A business graph definition is the wrapper added around a simple business object or a hierarchy of business objects to provide additional capabilities, such as carrying change summary and event summary information related to the business objects in the business graph. A business object metadata definition is the metadata that can be added to business object definitions to enhance their value when running on WebSphere Process Server. This metadata is added to the business object’s XML schema definition as well known xs:annotation and xs:appinfo elements. Business object services are a set of capabilities provided on top of the basic capabilities provided by Service Data Objects. Examples are services such as create, copy, equality, and serialization.

Apply the SCA programming model

2009-06-16T17:03:00.001-07:00

Programming Model and Design
Websphere Integration Developer v612
Contact us...

Apply the SCA programming model

Apply the SCA programming model

Service Component Architecture (SCA) is a set of specifications which describe a model for building applications and systems using a Service-Oriented Architecture. SCA extends and complements prior approaches to implementing services, and SCA builds on open standards such as Web services.

SCA encourages an SOA organization of business application code based on components that implement business logic, which offer their capabilities through service-oriented interfaces and which consume functions offered by other components through service-oriented interfaces, called service references. SCA divides up the steps in building a service-oriented application into two major parts:

The implementation of service components which provide services and consume other services.
The assembly of sets of components to build business applications, through the wiring of service references to services.

SCA emphasizes the decoupling of service implementation and of service assembly from the details of infrastructure capabilities and from the details of the access methods used to invoke services. SCA components operate at a business level and use a minimum of middleware APIs.

Service-Oriented Architecture (SOA)

Service Oriented Architecture (SOA) is a business-centric IT architectural approach that supports integrating your business as linked, repeatable business tasks, or services. With the Smart SOA approach, you can find value at every stage of the SOA continuum, from departmental projects to enterprise-wide initiatives.

Components

In an SCA, a component is the actual service. Components are the building blocks of a business solution that are wired together.

Interfaces

An interface provides the input and output of a component. It is created independent of the internal implementation of the component.

Use the business process editor to create a business process component

2009-06-09T21:41:00.001-07:00

Component Implementation

Websphere Integration Developer v612

Use the business process editor to create a business process component (including path conditions, activities, snippets, etc.)

Use the business process editor to create a business process component (including path conditions, activities, snippets, etc.)

Overview

Before ()
This is a generated business process. We will complete this to look line the one below (after).
After ()
This is the completed business process.

These tasks or activities are grouped as follows: ()

Build the Business Process

Follow these steps to build the completed business process as shown above.

IBM DeveloperWorks Tutorials

2008-08-05T07:12:00.000-07:00

IBM DeveloperWorks Tutorials

IBM DeveloperWorks Tutorials

A guided tour of WebSphere Integration Developer

Part 1- Get a driver's view of the WebSphere Integration Developer landscape
This article is the first in a series exploring a service-oriented approach to application integration using IBM WebSphere Integration Developer. This first article provides an overview of WebSphere Integration Developer and its key components and concepts.
Part 2 - SOA development with WebSphere Integration Developer
This second article in a series teaches the service oriented architecture (SOA) programming model and describes how to create a simple SOA application in WebSphere Integration Developer.
Part 3 - Building a simple service-oriented application
This is the third in a series of articles exploring a service-oriented approach to application integration using IBM WebSphere Integration Developer. This third article guides you through the implementation of those services. At the end of the article, you will have completed an order processing application.
Part 4- Unleashing visual snippets and business state machines in your service-oriented application
This is the fourth in a series of articles exploring a service-oriented approach to application integration using IBM WebSphere Integration Developer. In this article, you will learn more about business state machines and the visual snippet editor.
Part 5 - Business processes in a service-oriented world
This series explores a service-oriented approach to application integration using IBM WebSphere Integration Developer. This article dives into how to build a business process, including when to use a business process versus a state machine.
Part 6 - Becoming more on-demand using dynamic business rules
This is the sixth article in a series exploring a service-oriented approach to application integration using IBM WebSphere Integration Developer. This article examines how you can make your running application dynamic and flexible so it can handle changing business conditions without requiring you to redeploy the application, using dynamic business rules.
Part 7 - Interface and Business Object Mapping and Human Tasks
This is the seventh article in a series that explores a service-oriented approach to application integration using IBM WebSphere Integration Developer. This article takes you deeper into more tools in the suite: interface and business object mapping, and human tasks.
Part 8 - Dynamically invoking a component using selectors
This is the eighth article in a series describing how to build applications based on a service-oriented architecture (SOA). This article examines selectors, another on-demand capability provided by WebSphere Integration Developer and WebSphere Process Server.

Building SOA solutions with the Service Component Architecture

Part 1 - Oh great, another programming model
With the release of IBM WebSphere Integration Developer and WebSphere Process Server, comes a new programming paradigm for building service-oriented architectures (SOA) called the Service Component Architecture, a new programming model designed specifically for building and assembling business solutions in an SOA, and targeted for integrating and composing services.
Part 2 - Assembling SCA components
Examine references and wires in the context of assembling Service Component Architecture components with IBM WebSphere Integration Developer.
Part 3 - Integrating SCA modules with imports and exports
Build vertical integration solutions from a variety of components with the Service Component Architecture (SCA) and IBM WebSphere Integration Developer.
Part 4 - Integrating with JMS and Web services
Integrate Service Component Architecture (SCA) solutions with other systems using Java™ Message Service (JMS) and Web services, two common ways of integrating heterogenous systems -- that also enable you to solve many of the complex challenges inherent in integration.

Building SOA composite business services

Part 1: Develop SOA composite applications to enable business services
Integrate existing SOA services by composing them in different ways. Part of our focus will be on how this is done within the framework of a Service Component Architecture.
Part 2: Migrate business integration projects from WebSphere Application Developer-IE v5.1 to WebSphere Integration Developer v6.0.1
This article describes some of the issues and the solutions for migrating a prototype composite application from WebSphere Application Developer-IE v5.1 to WebSphere Integration Developer v6. We'll explore WSDL bindings, WSDL interfaces, XSD definition, and Business Process Execution Language (BPEL) coding.
Part 3: Build consumable Web Services using the REST architectural style in WebSphere
This article is the third in a series about developing composite applications to enable business services. The article focuses on the Representational State Transfer (REST) architectural style. By using a facade component as a REST-style interface, existing SOAP-style Web services can support customizable URLs, multiple resource format representations, browser response caching, streaming of large attachments, and use of HTTP methods to manipulate the resource.
Part 4: Develop measurable composite applications with the Common Event Infrastructure
This article is the fourth in a series that considers the development of composite applications to enable business services. In order to determine if a composite application is meeting the stated business goals, the application needs to be measurable. This article examines how to develop measurable composite applications with the help of three reusable artifacts that are based on the Common Event Infrastructure. You can learn why the artifacts are needed and how to use them to measure a composite application.
Part 5: Using IBM WebSphere Business Modeler
This article is the fifth in a series about developing composite applications to enable business services. Composite Business Services components are compliant with the Service Component Architecture and are developed using an integrated tool suite, which includes IBM WebSphere Business Modeler (WBM) and IBM WebSphere Integration Developer (WID). The runtime for the artifacts these tools generate is the IBM WebSphere Process Server. This article describes best practices for modeling, assembling, and deploying business processes using WBM V6. It also identifies some gaps in the integration of WBM and WID, and it describes some lessons learned during the example process modeling work, which is based on a real use case described in the article.
Part 6: Automate build and deployment steps
Building and deploying composite applications with many Service Component Architecture (SCA) modules, Java 2 Platform, Enterprise Edition (J2EE) packages, and database layer components often involves many manual steps. Automating these build and deployment steps makes your applications less prone to error, and hence, more suitable for the development-to-production transition. The authors here present an automated code-building solution using Apache Ant tasks provided by IBM Rational Application Developer and an automated deployment solution using IBM WebSphere Application Server Ant deployment tasks.
Part 7: Supporting multi-tenancy for composite business services
Previous articles in this series introduced the notion of composite business services (CBS) and outlined some of the core elements of the deployment environment they required. Multi-tenancy is the capability to service multiple organizations (clients) from a shared, common hosting environment. This article describes the concept of multi-tenancy, and it describes the network-delivered approach to software-as-a-service.
Part 8: Building multi-tenant portlets using WebSphere Portlet Factory dynamic profiles
This article is the eighth in a series that addresses the development of Composite Business Services (CBSs). CBSs provide the capability to integrate existing technologies and products to reflect desirable business intentions, such as configurability. IBM WebSphere(R) Portlet Factory is a portlet creation environment that simplifies and accelerates the development, deployment, maintenance, and re-use of portlets. This article introduces how to use WebSphere Portlet Factory to achieve configurability within the presentation layer by using dynamic profiles.
Part 9: Business process parallel activities pattern for flexibility and configurability
This is the ninth installment of the series that addresses development of composite business services (CBS). A CBS can be composed from existing SOA services or created as a new service, designed for composability, or both. This article introduces a parallel activities pattern that is used to design Business Process Execution Language (BPEL) processes for CBS. The article provides a banking use case example of realizing the pattern to create a flexible and configurable business process in a simple application built from CBS. The article describes a solution to a realistic use case implemented by leveraging BPEL parallel activities. Multiple concurrent processes are instantiated such that the number of concurrent processes can be based on a variable, runtime-specified number of business objects. The article begins with a brief introduction of the parallel activities pattern, followed by a use case for a loan request in which you will learn how to use the parallel activities pattern to realize flexibility and configurability.
Part 10: Providing governance over service consumption using WebSphere Process Server and WebSphere Service Registry and Repository
Generally the focus of SOA governance has been on the service provider side, especially in terms of the service lifecycle. Very little attention has been given to the consumer or subscriber side. Who should be able to see or discover the relevant service endpoints? Or how can someone who has discovered a service send a request to consume the service? Or what is the process associated with authorizing access to the service? Answers to these questions vary from customer to customer. This article answers these questions in the context of a fictitious prototype composite application called Jivaro Bank, and it shows how WebSphere(R) Service Registry and Repository and WebSphere Process Server can be used to implement governance over service consumption and subscription.
Part 11: Implement the subscriber entitlement process
The previous article in this series described, at a somewhat high level, how IBM WebSphere Service Registry and Repository and IBM WebSphere Process Server can be used for service consumption governance. This article describes the implementation details, showing how you can customize WebSphere Service Registry and Repository to support service consumption governance, implement the subscriber entitlement process using WebSphere Process Server, and integrate it with WebSphere Service Registry and Repository using its SOAP interface.
Part 12: Combine document-centric workflows in IBM FileNet with business state machines in IBM WebSphere Process Server
Integrate event-driven Business Process Execution Language (BPEL) business processes modeled in IBM WebSphere Process Server with document-centric business processes in IBM FileNet P8. This article takes you through the process using a simple loan application scenario in a fictitious banking application.

Building a powerful, reliable SOA with JMS and WebSphere ESB

Part 1- Combining WebSphere ESB V6.0.1 and JMS

Part 2- Creating a sample application for a common scenario

Part 3- The WebSphere ESB mediation

Make composite business services adaptable with points of variability

Part 1- Choosing the right implementation

Part 2- Using dynamic service mediation in WebSphere Business Services Fabric

Part 3- Using selectors and business rules for dynamicity

Part 4- Using WebSphere Enterprise Service Bus mediation modules

Part 5- Using WebSphere Service Registry and Repository

Migrating WebSphere Commerce to the SOA foundation tooling

Part 1- Introduction to series

Part 2- Getting WebSphere Commerce and WebSphere Process Server talking

Part 3- Migrating a business process to WebSphere Process Server

Part 5- Tying it all together with the Esperanto methodology

On demand business process life cycle

Part 1: Create the foundation for your on demand business processes

Part 2: Patterns for e-business recipe

Part 3: Business process modeling using WebSphere Business Integration Modeler

Part 4: Integrate artifacts from Rational XDE and WebSphere Business Integration Modeler

Part 5: Workflow development, deployment, and testing

Part 6: Apply customization policies and rules

Part 7: Monitor business processes and emit events using CEI

Part 8: Business process monitoring -- Create key performance indicators

Part 9: Involve people

Part 10: Develop message adapters for CICS transaction servers

Part 11: Integrate business processes with CICS transaction servers

Part 12: Implement a compensation service

Part 13: Deployment in a clustered environment

Part 14: Use a clustered WebSphere MQ deployment to balance messaging workload

Reliable and repeatable unit testing for Service Component Architecture modules

Part 1- Create automated unit tests for SCA modules

Part 2- Create repeatable tests for SCA modules that implement business processes

Part 3- Testing business processes that use human tasks

SCA application development

Part 1: An overview of Service Component Architecture

Part 2: SCA client and implementation model for Java

Part 3: Develop a sample SCA application

SOA programming model for implementing Web services

Part 1: Introduction to the IBM SOA programming model

Part 2: Simplified data access using Service Data Objects

Part 3: Process choreography and business state machines

Part 4: An introduction to the IBM Enterprise Service Bus

Part 5: Service-oriented user interfaces

Part 6: The evolving component model

Part 7: Securing service-oriented applications

Part 8: Human-based Web services

Part 9: Integrating rules with SOA

Part 10: SOA user roles

Part 11: SOA and the mainframe software environment

SCA Invocation Patterns

Use ARM to monitor SCA invocations in IBM WebSphere Process Server V6.1

Part 1: Debug SCA invocations using IBM Tivoli Composite Application Manager for Response Time Tracking

Part 2: Understand SCA invocation patterns and debug asynchronous scenarios

SCA asynchronous invocation patterns in depth

Using SOA with WebSphere process integration products

Part 1: Business modeling

Part 2: Integration development

Part 3: Business-driven development

Part 4: Enabling the CBE and CEI Infrastructure

Part 5: Sequential versus concurrent processes

Part 6: Business measures and monitoring

Part 7: Configure WebSphere security using a file-based custom user registry

WebSphere Integration Developer and WebSphere ESB advanced topics

Part 1- Content-based service invocation and routing

Part 2- Data enrichment, transformation, and validation

WebSphere Process Server relationship service

Part 1- Static relationships

Part 2- Dynamic relationships

Creating flexible service-oriented business solutions with WebSphere Business Services Fabric

Part 1: Overview
WebSphere Business Services Fabric provides an SOA platform to enable a new class of service-oriented business solutions. Business Services Fabric provides an integrated environment to model, assemble, deploy, manage and govern composite business services. This series of articles introduces you to WebSphere Business Services Fabric and shows you how to use it to build composite business services.
Part 2: Extending the ontology models
Learn how you can leverage the features of WebSphere Business Services Fabric to build composite business applications that support dynamic binding and orchestration. In Part 2, you'll learn how to model the variability points in the business process as ontology extensions using the Fabric Modeling Tool.
Part 3: Designing and implementing the business service
Learn how you can leverage the features of WebSphere Business Services Fabric to build composite business applications that support dynamic binding and orchestration. In Part 3, you'll implement a composite business process and enable it with dynamic binding and orchestration capabilities.
Part 4: Creating metadata for the business process
Learn how you can leverage the features of WebSphere Business Services Fabric to build composite business applications that support dynamic binding and orchestration. Part 4 of this series describes how to create metadata for a business process based on the Fabric Business Service Model. This metadata enables users to reuse and extend existing components, and enables dynamic endpoint selection at run-time.
Part 5: Testing the application
Learn how you can leverage the features of WebSphere Business Services Fabric to build composite business applications that support dynamic binding and orchestration. In the final article in this 5-part series you'll learn how to deploy and test the application that you've built in the previous parts of the series.

Business event processing with WebSphere Business Events

Part 1: An introduction
WebSphere Business Events is a new IBM product that enables you to detect, understand, and act on patterns in business events. Part 1 of this series introduces you to key WebSphere Business Events concepts and tools.
Part 2: Building a business events application
Part 1 of this series introduced you to key WebSphere Business Events concepts and tools. In Part 2, you'll learn how to build and test a simple Business Events application, which you'll use to integrate with other IBM products in future articles in the series.
Part 3: Using WebSphere Business Events with WebSphere Message Broker
Part 3 of this series shows you how to build WebSphere Message Broker message flows to interact with WebSphere Business Events, enabling you to use the business event processing power of Business Events in your WebSphere Message Broker application integration and message transformation environment.
Part 4: Integrating Business Events with WebSphere Enterprise Service Bus and WebSphere Process Server
Part 4 of this series shows you how to build an IBM WebSphere ESB mediation module to interact with WebSphere Business Events, IBM's premier product for business event processing.
Part 5: Integrating Business Events with WebSphere Business Monitor
In Part 5 of this series, you'll learn about the support provided in WebSphere Business Events V6.1 for integration with WebSphere Business Monitor. You'll learn how to configure WebSphere Business Events so that it can forward business events in a format that WebSphere Business Monitor can process, and how the Monitor dashboards can help you monitor and react to these events.
Part 6: Integrating Business Events with Common Business Events
Learn how you can configure WebSphere Business Events V6.1 to accept and generate WebSphere Application Server Common Base Events, which are transported via the WebSphere Common Event Infrastructure.

IBM DeveloperWorks Resources

Websphere Integration Developer IBM Redbooks

2008-08-05T06:51:00.000-07:00

IBM Redbooks/Infocenters

IBM Redbooks/Infocenters

Adapters

Courses

IBM Infocenter

Websphere Integration Developer 6.1 (includes Business Modeler, process server, enterprise service bus, business services fabric)
Websphere Integration Developer 6.0.1/6.0.2 (includes Business Modeler, process server, enterprise service bus, business services fabric)
Websphere Integration Developer 5.0
Websphere Application Server Network Deployment 6.1

Websphere Integration Developer 6.1 Certification

WID 6.1 Certification Test 316

Section 1 - Programming Model and Design (21%)

Section 2 - Component Implementation (30%)

Section 3 - Human Tasks (11%)

Section 4 - Connectivity (12%)

Section 5 - Component Assembly and Configuration (12%)

Section 6 - Application Testing and Debugging (14%)

WebSphere Learning Resources

Websphere Business Modeler Learning resources

Certification preparations

Forums

IBM DeveloperworksModel business measures

IBM Redbooks

Learning Resources

Sample Projects

Tutorials

Wikipedia

Websphere Business Integration Developer Learning resources

Adapters

Courses

IBM Infocenter

Redbooks

Related Websphere Resources

Tutorials

Configure the integrated test environment

Configure the integrated test environment

Deploying modules to the test environment

Use the integrated test environment to test modules, mediation mo

Use the integrated test environment to test modules, mediation modules and components

Use the integrated debugger to troubleshoot mediation flows and c

Use the integrated debugger to troubleshoot mediation flows and components

Identify and resolve common errors in integration applications an

Identify and resolve common errors in integration applications and mediation flows

Use the BPC Explorer to test processes and tasks

Use the BPC Explorer to test processes and tasks

Use the Module Dependency Editor to declare dependencies for modu

Use the Module Dependency Editor to declare dependencies for modules, mediation modules, and libraries

Related links

Configure Quality of Service (QoS) qualifiers when wiring components

Configure Quality of Service (QoS) qualifiers when wiring components in the assembly editor

Create module imports, exports and standalone references

Create module imports, exports and standalone references

Imports

Exports

Stand-alone references

Related links

Configure EJB, Java, and SCA bindings

Configure EJB, Java, and SCA bindings

Related links

Configure bindings to support synchronous invocation patterns

Configure bindings to support synchronous invocation patterns (JMS, MQ, Web Services, HTTP)

Invocation Patterns

Related links

Configure bindings to support asynchronous invocation patterns

Configure bindings to support asynchronous invocation patterns (JMS, MQ)

Invocation Patterns

Related links

Create imports from external services

Create imports from external services

Add, configure, and bind an adapter

Add, configure, and bind an adapter

Use and configure the data binding framework

Use and configure the data binding framework

Assign staff to a human task

Assign staff to a human task

Related links

Identify the escalation and notification mechanisms available for

Identify the escalation and notification mechanisms available for human tasks

Related links

Implement client interactions for human tasks

Implement client interactions for human tasks (including API, human task manager, business flow manager)

Related links

Design human tasks

Design human tasks

Related links

Configure components to emit CEI events

Configure components to emit CEI events

Related links

Configure a selector to dynamically invoke SCA components