Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop Data access resources > Develop data access applications > Develop data access applications > Service Data Objects version 2.1.1
Use SDO 2.1.1 in SCA applications
The Service Component Architecture (SCA) implementation complies with Service Data Objects (SDO) 2.1.1 (JSR 235). We can use SDO 2.1.1 in your SCA applications.
Install the product and enable SDO. Instructions on enabling the SDO feature are in the installation topics for your operating system.
Read SDO data binding for SCA applications to better understand how to work with SDO in SCA Java clients and implementations. For more information, read about using business exceptions with SCA interfaces.
Consider installing a Rational Application Developer product with SCA Development Tools that you can use to assemble service-oriented application components based on open SCA specifications. See the Rational Application Developer documentation.
To use SDO 2.1.1 in an SCA application, access the default HelperContext programmatically in a Java or Java EE component implementation type and then develop one or more SCA composites that use SDO following a bottom-up or top-down approach.
Procedure
- Develop one or more SCA components that use SDO.
- Decide whether you are going to use a top-down or bottom-up approach to developing your SCA component implementations.
The section on top-down and bottom-up development in SDO data binding for SCA applications describes the approaches. The top-down approach is typically preferred in SCA service architecture and development. When you start with a composite definition file that uses <interface.wsdl>:
- The top-down approach is strongly typed.
- The top-down approach has an implied schema, anyType, that does not need to be generated.
- The bottom-up approach has more flexibility than the top-down approach.
Java.lang.object is a restriction.
- Use a top-down approach (starting from WSDL and XSD files) or a bottom-up approach (starting from Java files) to develop SCA composites that use SDO.
- Use a top-down approach to develop SCA composites.
- Use a bottom-up approach to develop SCA composites.
- Access the default HelperContext programmatically.
We can access the default HelperContext programmatically in a Java or Java EE component implementation type. We cannot access the default HelperContext programmatically in a Spring component implementation type.
Restriction: We cannot use array types for Java parameters. We cannot map from schema elements declared with the attribute, maxOccurs="unbounded" to array types. Instead, map the element to a List, such as a List <DataObject> or List <String>.
- If you are using a top-down development approach, package your WSDL and XSD files in an SCA contribution.
Package WSDL and XSD files in an appropriate contribution enables your component to access the schema definitions. The section on schema registration in SDO data binding for SCA applications describes the registration.
Consider packaging your WSDL and XSD files so that they can be accessed across various parts of the application from a shared in-memory instance. For details, see Implement shared scopes in SCA applications that use SDO.
- Deploy your SCA composites that use SDO in an SCA business-level application.
See topics on SCA contributions and shared scopes for information on how to establish a shared SDO scope. Otherwise, there are no special deployment considerations for applications using the SDO data binding.
Results
You have developed and deployed an SCA composite that uses SDO in a business-level application.
What to do next
Test the deployed SCA composites.
Related
SDO data binding for SCA applications
Use a top-down approach to develop SCA components that use SDO
Use a bottom-up approach to develop SCA components that use SDO
Access default HelperContext objects in SCA applications
Implement shared scopes in SCA applications that use SDO
SCA contributions
Service Data Objects version 2.1.1
Data access with Service DataObjects, API versions 1.0 and 2.01
Create and accessing SDO HelperContext objects
Use business exceptions with SCA interfaces
Rational Application Developer documentation
JSR 235: Service Data Objects
OASIS Service Data Objects (SDO) TC