[AIX HP-UX Linux Solaris Windows]This topic applies only on the z/OS operating system.

Multiple SCA implementation packaging considerations

The Feature Pack for Service Component Architecture (SCA) supports several implementation technologies that can provide the business logic for SCA service components. Because a primary architectural objective of SCA is to enable you to combine existing services together, it is easy to assume that a single composite with multiple components might have different implementation technologies. However, there are restrictions that limit packaging of multiple SCA implementations.

Business-level application deployment constraints

Before deploying an SCA application, particularly one that uses an OSGi application, consider the following constraints:

Class loading

A purpose of the OSGi application framework is to build a class loader structure that is wholly defined by the OSGi service registry and OSGi application design, and avoid class loader problems that affect Java EE servers.

If your applications use different implementation technologies, differences in class loader structures might cause the SCA run time to copy objects from one environment to another. OSGi applications are remote-only interfaces that do not permit pass-by-reference behavior.

Your SCA application must use correct semantics for local and remote interfaces.




Related concepts
SCA application package deployment
Related tasks
Using OSGi applications as SCA component implementations
Concept topic    

Terms of Use | Feedback

Last updated: Oct 22, 2010 3:02:28 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v700osgijpa&product=was-nd-mp&topic=csca_osgi_deploypkg
File name: csca_osgi_deploypkg.html