Design principles of ABCS

The following points will be helpful to make appropriate design decisions while designing different types of ABCS:

• ABCS implementation should be based on ABCS WSDL contract (top-down approach). Therefore, before creating the ABCS WSDL, identify the role of ABCS in the AIA integration.

• If it is a provider ABCS, then identify the EBM schema to be used to transform between ABM and EBM. If the AIA out-of-the-box EBM does not match provider service, then customize or go with non-canonical pattern.

• If it is a requester ABCS, then identify the appropriate EBS and its EBM, and design the transformation mechanism to transform the requester application ABM to EBS input EBM. It is also necessary to identify the EBS Message Execution Pattern (MEP) to handle the coordination.

• Identify and design the message transportation protocol such as SOAP, JMS, and JCA, but before that we must analyze the capability of requester and provider applications.

• A single ABCS should be able to handle multiple instances or versions of a provider application. At the same time, co-occurrence of multiple versions of the same ABCS should be avoided.

• ABCS should not make any assumptions regarding the target system or to the transport mechanism (SOAP, JMS, native or otherwise).