Creating SCA business-level applications

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.

Before you begin

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.

New or updated for this feature pack 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 server or cluster that is enabled for feature pack Version 1.0.1.0 or later. 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)
  • [Feature Pack for SCA Fix Pack 5 or later] OSGi applications as SCA component implementations
  • SCA Spring 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.

New feature New or updated for this feature pack New feature: 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 Feature Pack for SCA extends the business-level application functionality.newfeat

Procedure

  1. 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

    See Creating 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: Creating an SCA business-level application with the console.

    wsadmin scripts

    See Setting up business-level applications using wsadmin scripting.

    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: Creating an SCA business-level application with scripting.

    Java application programming interfaces

    See Creating an empty business-level application using programming.

    Use programming to create an empty business-level application.
  2. Create your business-level application using the administrative console, wsadmin, or programming.
  3. 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:

  1. Import any SCA or other assets needed by your business-level application.
  2. Add assets, shared libraries, or other business-level applications as composition units.

    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.

    New or updated for this feature pack 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.

    [Feature Pack for SCA Fix Pack 5 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.

  3. Save the changes to your 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 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.

[Feature Pack for SCA Fix Pack 5 or later] 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 ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jun 11, 2013 8:40:09 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=tsca_bla_create
File name: tsca_bla_create.html