![]() |
|||
This Sample demonstrates the use of Websphere Service Component Architecture (SCA). |
|||
|
|||
Run | TechNotes | |||
IBM Websphere Service Component Architecture (SCA) provides a consistent interface design for accessing components and services such as EIS services, Web Services, J2EE components, etc. The SCA programming model provides a significant simplification of the programming model for writing applications that run on WebSphere. The programming model is based on concepts and techniques that are relatively modest refinements of existing J2EE concepts and techniques, or which have simple mappings to existing J2EE concepts. SCA supports a strong separation of application business logic from technical infrastructure code. Separation of application business logic from technical infrastructure code allows applications to be created with far fewer IT specialists, and provides for greater code portability and isolation from IT infrastructure change. SCA exposes business-level interfaces to application business-logic code. The data structures used as arguments to these base SCA are modeled in a standardized Business Object (BO) data-structure representation that also hides the technical details of the technology of the underlying SCA implementation. IBM provides a rich set of tools for generating base SCA and BO types specific to customer data and computing infrastructure without the need for programming. IBM also provides a rich set of tools for the J2EE programming model that allows technical IT specialists to create arbitrarily complex SCA servics or applications using the J2EE APIs directly. The objective of this sample is to show how an SCA connection is defined and accessed. The service being invoked in this sample is a simple Java class. Other samples in the Samples Gallery show the use of SCA to access actual Business Integration services. In a typical application development environment, the SCA invocation and wiring code shown in this sample would be generated from the development tools. |