Creating SCA business-level applications (deprecated)

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.

Deprecated feature: 8.5.5.19 or later

The Service Component Architecture (SCA) programming model and samples are deprecated, and will be removed in a future release. You cannot deploy new SCA business-level applications.

Update your applications to use different programming models. The programming models that you use vary depending on how you previously incorporated SCA in your application.

If you used SCA for binding, consolidate the ways in which your application is exposed to a few standards, such as Java API for RESTful Web Services (JAX-RS) or Java Message Service (JMS). For example, use JAX-RS for application bindings. To minimize the duplication of binding level implementation, structure your application to use shared code.

If you want to continue to use SCA as part of your long-term strategy, consider hosting your applications on IBM Business Process Manager.

Before you begin

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.

If your SCA composite or application uses Feature Pack for SCA Version 1.0.1 functionality, you must deploy the SCA asset or application to a Version 8.x target or to a feature pack Version 1.0.1.0 target. Version 1.0.1 functionality includes:

Java™ Message Service (JMS) bindings
Atom bindings
HTTP bindings with a wire format of JSON-RPC
Java Platform, Enterprise Edition (Java EE) integration modules (implementation.jee, implementation.web, or implementation.ejb components)
SCA Spring component implementations
OSGi applications as SCA component implementations
Service Data Objects (SDO) composites

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.

About this task

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.

Procedure

Select a way to create your business-level application.

Table 1. Ways to create SCA business-level applications . You can create a business-level application using the administrative console, wsadmin scripts, or programming.
Option	Method
Administrative console business-level application creation wizard	Click Applications > New Application > New Business Level Application and follow instructions in the wizard. See an example use of the console to create a business-level application that has an SCA asset.
wsadmin scripts	Use the wsadmin scripting tool to create an empty business-level application. See an example use of scripting to create a business-level application that has an SCA asset.
Java application programming interfaces	Use programming to create an empty business-level application.

Create your business-level application using the administrative console, wsadmin, or programming.
Save the changes to your administrative configuration.
When saving the configuration, synchronize the configuration with the nodes where the application is expected to run.

Results

The name of the application is shown in the list on the Business-level applications page.

What to do next

After you create a business-level application, you can do the following to add composition units to it:

Import any SCA or other assets needed by your business-level application.
Add assets, shared libraries, or other business-level applications as composition units.
When you add an asset, you must specify a target that supports SCA composites. Specify only a single server or cluster as the target. Do not map an SCA composition unit to multiple servers or clusters. Components and service names within SCA composites must be modified so that they are different from each other.

If the asset or application uses OASIS support, specify a Version 8.5 target.

If the asset or application uses Feature Pack for SCA Version 1.0.1 functionality, specify a Version 8.x target or a feature pack Version 1.0.1.0 target.

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.
Save the changes to your administrative configuration.
Start the business-level application.

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.