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 7.0 server or cluster that is enabled for the Feature Pack for SCA.
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.
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:
When you add an asset, you must specify a target server or cluster that is enabled with the Feature Pack for SCA. Specify only a single server or cluster as the target. Do not map an SCA composition unit to multiple servers or clusters.
If the asset or application uses Feature Pack for SCA Version 1.0.1 functionality, specify a server or cluster that is enabled for feature pack Version 1.0.1.0 or later.
For applications that use implementation.osgiapp, add the enterprise bundle archive (EBA) asset as a composition unit to the business-level application before adding the SCA asset as a composition unit.
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 is enabled for the Feature Pack for SCA.
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 enabled for the Feature Pack for SCA 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 server or cluster 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.
In this information ...Subtopics
Related tasks
| IBM Redbooks, demos, education, and more(Index) |