Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop SCA composites
Develop Service Component Architecture (SCA) services
To develop SCA service implementations, you can use either a top-down development approach starting with an existing WSDL file or you can use a bottom-up development approach starting from an existing Java interface or implementation. When using either the top-down or bottom-up development methodologies, you can develop service clients or use tools to map business exceptions on remotable interfaces.
- Develop SCA services from existing WSDL files
We can develop a Service Component Architecture (SCA) service implementation when starting with an existing WSDL file.
- Develop SCA services with existing Java code
We can develop an Service Component Architecture (SCA) service implementation when starting with an existing Java application.
- Develop SCA service clients
We can develop a Service Component Architecture (SCA) service client starting with either a Java interface or a WSDL file for the SCA service to invoke.
- Use business exceptions with SCA interfaces
We can implement exceptions for remotable interfaces in the Service Component Architecture (SCA) environment to provide additional flow of control for error conditions to meet the needs of your business application.
- Considerations for developing SCA applications using EJB bindings
When developing Service Component Architecture (SCA) applications that you intend to use with EJB bindings, keep in mind that the SCA EJB binding is architected in a Java-centric manner, in contrast to the XML-centric implementations of the SCA default binding and the SCA web services binding.
Assembly tools
Rational Application Developer documentation