You can create an empty business-level application and then add Service Component Architecture (SCA) assets, shared libraries, business-level applications, and other artifacts as composition units to the empty business-level application.
Configure the target application server. You must deploy SCA composite assets of a business-level application to a Version 8.x server or cluster (target) or to a Version 7.0 target that is enabled for the Feature Pack for SCA.
If your SCA composite or application uses OASIS support, you must deploy the SCA asset or application to a Version 8.5 target.
Optionally, determine what assets or other files that you want to add to your business-level application and whether your application files can run on your deployment targets.
You can create business-level applications using the administrative console, the wsadmin tool, or programming.
You create SCA business-level applications the same way as for non-SCA business-level applications. However, when you use an SCA asset in a business-level application, function that applies only to applications that use SCA composites becomes available. For example, you can access administrative console pages that apply only to applications that use SCA composites.
The name of the application is shown in the list on the Business-level applications page.
After you create a business-level application, you can do the following to add composition units to it:
If the application does not run as desired, edit the application configuration, then save and run it again.
If the business-level application does not start, ensure that the deployment target to which the application maps is running and try starting the application again. If SCA composite assets do not start, ensure that each asset is mapped to a deployment target that supports SCA composites.
When an SCA application fails to start, multiple first failure data capture (FFDC) entries are logged for a single error. The FFDC log entries pertain to the same problem and are not different issues related to the failure. Use the information provided in the FFDC log entries to fix the problem and try starting the SCA application again.
If an asset composition unit uses an Enterprise JavaBeans (EJB) binding and does not start because it has a non-WebSphere target of "null", delete the asset composition unit and add it again to the business-level application. Specify a target that supports SCA composites when you add the asset to the business-level application. You cannot change the target after deployment.
If the META-INF/sca-deployables directory has multiple SCA composite files and the application does not start because the product cannot obtain the CompUnitInfoLoader value, place only the file that contains the composite in the META-INF/sca-deployables directory. You can place the other composite files anywhere else within the archive.
If the SCA application uses security, the target must be in the global security domain.
In multiple-node environments, synchronize the nodes after you save changes to the target before starting the business-level application.
For applications that use implementation.osgiapp in multiple-node environments, target the EBA composition unit to the same server or cluster as the SCA composition unit.