Orchestration generally refers to a sequence of steps that live within a single contained process, where one orchestrator can see and control the entire process. Typically, an individual BPEL process fits into this category.

Choreography is a broader process where pieces of the process are part of a choreography chain of events, but none of the individual pieces understand about each other. They know what triggers them, and what they trigger to happen, but nothing sits at a higher level co-coordinating them. They just know the part they have to play. This is more typical of how a number of different long running processes interact with one another, and especially if a broader process is broken down into a chain of smaller processes where they cross departmental, or even enterprise boundaries.

The engineer is responsible for the design of an entity, typically to the exclusion of the environment in which the entity will exist.

The architect is responsible for ensuring that the entity also serves and does not negatively impact the environment in which the entity will exist.

SOA Centre of Excellence (CoE) has been created at work as an initiative from the Enterprise Architect.

CoE has core members to be the binding link to all other teams, including IT Head, Enterprise Architect, and the Technical Team Lead).

CoE holds communication and provides advice to other team members and acts as a common destination to provide solutions, set strategies and orchestrate work among teams and projects so as to maintain a clear understanding to all memebers and turn the isolated islands into a single mainland, hence make sure that work is synchronized among teams and is not redundant.

CoE holds meetings with different team members in their respective streams covering Data, Portal, and Process streams to name a few.

You may have notice that as you were building the state machine that there was one error all along: Correlation set must have at least one property. When deployed to a server, your state machine could have several instances, each in a different state.

When an operation is called on the state machine component, you need a way to make the call on the correct instance. This is accomplished using correlation sets.

A correlation set tells the state machine which running instance to use for the given input data. It does this by examining the contents of the input data, using a specified field as a kind of key that uniquely identifies the corresponding process instance.

In WebSphere Integration Developer V6.0.2.2, these are the four steps:

1. Right-click Correlation Properties on the top-right corner of the editor and select Add Correlation Property.
2. Enter OrderNumber for the name, select int for the type, and then click OK.
3. In the OrderNumber correlation properties that opens, each operation of the business state machine displays. Click the cell next to placeOrder and then drill down to Order - orderNumber.
4. Click the cell next to orderShipped and drill down to Order - orderNumber.