Building ProcessServices-CustomerInterfaceManagement

As explained in the previous chapter, the purpose of this component is to handle the customer profile. It should check for the existence of a customer, and if not present, create the customer profile. This is a classic example of a composite service, and you may wonder why this is implemented as a business process. In the future, if we have to handle the creation of a billing account as part of a customer profile data, then it essentially leads to a cross-domain service invocation, which rightfully should be choreographed using a business process. When there is a need for invoking business services from more than one component and that belong to different application domains, a business process layer (using a BPEL) will be used to choreograph the interactions. They will not be contained within the business service component itself.

The pseudo logic for this business process component is depicted as an activity diagram, as shown next:

:

...