+

Search Tips   |   Advanced Search

Create SCA business-level applications

We 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. We 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 wer SCA composite or application uses OASIS support, you must deploy the SCA asset or application to a v8.5 target.

If wer 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:

Optionally, determine what assets or other files to add to the business-level application and whether the application files can run on the deployment targets.

We can create business-level applications using the console, wsadmin.sh, or programming.

We 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, we can access console pages that apply only to applications that use SCA composites.

  1. Select a way to create the business-level application.

    applications. We can create a business-level application
    Option Method
    Administrative console business-level application creation wizard

    See Create SCA business-level applications with the console.

    		Click Applications > New Application > New Business Level Application and follow instructions in the wizard.

    For example use of the console to create a business-level application that has an SCA asset, see Example: Create an SCA business-level application with the console.

    wsadmin scripts

    See Set up business-level applications .

    		Use the wsadmin scripting tool to create an empty business-level application.

    For example use of scripting to create a business-level application that has an SCA asset, see Example: Create an SCA business-level application .

    Java APIs

    See Create an empty business-level application using programming.

    		Use programming to create an empty business-level application.

  2. Create the business-level application using the console, wsadmin, or programming.

  3. Save the changes to the 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 creating a business-level application, we can do the following to add composition units to it:

  1. Import any SCA or other assets needed by the business-level application.

  2. Add assets, shared libraries, or other business-level applications as composition units.

    When we add an asset, 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 v8.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.

  3. Save the changes to the administrative configuration.

  4. 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 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 we add the asset to the business-level application. We 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 containing the composite in the META-INF/sca-deployables directory. We 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.


Subtopics


Related tasks

  • Create business-level applications with the console
  • Administer application servers
  • Create an empty business-level application using programming
  • Start a business-level application using programming
  • Set up business-level applications
  • Start business-level applications
  • Deploy and administering business-level applications

  • Business-level application settings
  • Composition unit settings