The product offers sample files that support Service Component Architecture (SCA) specifications. You can use these sample SCA files in business-level applications. SCA services are packaged in Java archive (JAR) files that you import as assets to the product repository and then add as composition units to business-level applications. Each sample includes detailed deployment instructions in a readme.html file.
To use the samples, download SCA sample files from a product download site:
You must deploy SCA sample files as assets of a business-level application to a Version 8.0 server or cluster or to a Version 7.0 target that is enabled for the Feature Pack for SCA. The /installableApps directory contains prebuilt archives that you can deploy as assets. The other directories contain sample-specific source files, scripts, and instructions for building deployable archives.
You can deploy the prebuilt CandyStore.jar file in the /installableApps directory or build a deployable JAR file.
For a description of the 10 composites in CandyStore and details on deployment, refer to /CandyStore/documentation/readme.html.
You can deploy the prebuilt HelloJeeEar.ear, HelloJeeEnhancedEar.ear, and HelloJeeSca.jar files in the /installableApps directory or build deployable files.
For details on deployment, refer to /HelloJee/documentation/readme.html or to the topic about using existing Java EE modules and components as SCA implementations.
You can deploy the prebuilt helloworld-ws-asynch.jar, helloworld-ws-client-asynch.war, and helloworld-ws-asynchclient.jar files in the /installableApps directory or build deployable files.
For a description of the JAR files and details on deployment, refer to /helloworld-ws-asynch/documentation/readme.html. For detailed instructions on deploying the helloworld-ws-asynch.jar file in a business-level application, refer to "Example: Creating an SCA business-level application with the console" and "Example: Creating an SCA business-level application with scripting" in the information center.
Also provided with the JMS binding samples are a POJO component and a thin client:
You can deploy the prebuilt jms-callback-service.jar, jms-twoway-oneway-service.jar, and jms-twoway-service.jar files in the /installableApps directory or build deployable files.
For details on building JMS sample artifacts, creating JMS resources for the samples and deploying the samples, refer to /jms/documentation/readme.html.
You can deploy the prebuilt JobbankClientApp.ear, jobbankejb.jar, and JobbankTargetEJBApp.ear files in the /installableApps directory or build deployable files.
For a description of the files and details on deployment, refer to /jobbankejb/documentation/readme.html.
You can deploy the prebuilt Multiservice.jar, MultiService.war, helloworld-ws-asynch.jar, and JobbankTargetEJBApp.ear files in the /installableApps directory or build deployable files.
You can deploy the prebuilt WebServicesSamples.ear and EJB3CounterSample.ear files in the /installableApps directory.
For details on deployment, refer to /MultiService/documentation/readme.html.
You can deploy the prebuilt mybank-accountservice.jar and mybank-client.war files in the /installableApps directory or build deployable files.
For details on deployment, refer to /MyBank/documentation/readme.html.