Tuesday, June 9, 2009

Generate a business process implementation

Business Process
Websphere Integration Developer v612
Contact us...
 

 

Generate a business process Implementation

Assembly Diagram

After laying out your components using the assembly editor, you can then generate an implementation for the components.

Interface

This is the interface that the ShippingProcess component uses.

Implementation types

To generate a business process implementation, right-click on a component (i.e ShippingProcess) and select Generate Implementation... > Process from the context menu.

You have 5 implementation types to choose from. 

 

 

 
After you select the implementation type, you have to select the folder where the process implementation will be generated.  Accept the default folder and click OK.

Generated Business Process implemention

The tooling generated a basic business process component, as shown below.  Notice that the properties are derived from the relationship of this component to the other components as shown in the assembly diagram (see above).
 
 
  • Receive
    A receive activity is an entry point to a process; it is the point where the process starts or continues. You need one receive activity per operation you define in the process's interface. In the process editor, you can specify which operation corresponds to which receive activity. That means that when a call is made to one of the process's operations, the corresponding receive activity accepts the call, and the process continues running from there. A process requires at least one receive activity to start. A receive activity can also occur in the middle of a business process. In this case, if the process encounters a receive activity while it is running, the process stops and waits for the corresponding operation to be called.

    Note:
    There is only a Receive activity because the Shipping interface is a one-way operation only.  If it were a two-way operation (request/response), the tooling would have also generated a Reply activity in addition to the Receive activity.
 
  • Interface Partners
    The term Interface Partner in this context is a little bit confusing.  Within a process, we use the term partner to describe the other services that may be calling your interfaces, in this case, Shipping.  Thus, any service that calls the Shipping interface is considered an Interface Partner.  Put very simply, when a client calls your process, you can think of it as an interface partner that  called you. 
 
 
  • Reference Partners
    In the assembly diagram above, you can see that ShippingProcess invokes ProcessOrder and ShippingTask.

    Each reference of the component that the process implements corresponds to one reference partner within the process. When you call another service, you will do so using a reference partner.  

Related links

 

Posted by at No comments:
Subscribe to: Posts (Atom)