Develop Service Component Architecture (SCA) services

To develop SCA service implementations, we can use either a top-down development approach starting with an existing WSDL file or we 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, we can develop service clients or use tools to map business exceptions on remotable interfaces.

Subtopics

• (dist)(zos) Develop SCA services from existing WSDL files
  We can develop a Service Component Architecture (SCA) service implementation when starting with an existing WSDL file.

• (dist)(zos) Develop SCA services with existing Java code
  We can develop an Service Component Architecture (SCA) service implementation when starting with an existing Java application.

• (dist)(zos) 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.

• (dist)(zos) Develop asynchronous SCA services and clients
  We can create applications that use Service Component Architecture (SCA) OASIS specifications to asynchronously run request-response services.

• (dist)(zos) 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 the business application.

• (dist)(zos) 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.

Related concepts

Development and assembly tools

Related information: