WAS v8.5 > Deploy applications > Deploy SCA composites

Deploy SCA business-level applications

Deploying an SCA business-level application consists of creating an empty business-level application and then adding SCA assets, shared libraries, business-level applications, and other artifacts as composition units to the empty business-level application.

Develop the artifacts to go in the application and configure the target server. You must deploy SCA composite assets of a business-level application to a v8.x target or to a v7.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 v8.5 target.

If your SCA composite or application uses Feature Pack for SCA v1.0.1 functionality, you must deploy the SCA asset or application to a v8.x target or to a feature pack v1.0.1.0 target. v1.0.1 functionality includes:

• JMS bindings
• Atom bindings
• HTTP bindings with a wire format of JSON-RPC
• 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

When creating a business-level application, we can configure the application enough to enable it to run on the server. Later, we can configure the application and its contents further, start or stop the application, and otherwise manage its activity.

The topics in this section describe how to deploy and administer a business-level application or its contents using the dmgr console. We can also use programming or wsadmin scripting.

• Import assets to a repository.
• Create an SCA business-level application that has SCA assets, shared libraries, or business-level applications.
• Start the application.
• Stop the application.
• Update SCA composite artifacts.
• Update the application and its configuration units.
• View the composite definition of an SCA asset composition unit.
• View SCA domain information.
• View or edit JMS bindings on references and services of SCA composites.
• Delete the application.

After making changes to administrative configurations of the applications in the dmgr console, ensure that you save the changes.

Subtopics

• SCA composites
  A SCA composite is a composition unit within an SCA domain. An SCA composite can consist of components, services, references, and wires that connect them. A composite is the unit of deployment for SCA.
• SCA contributions
  A SCA contribution contains artifacts that are needed for an SCA domain. Contributions are sometimes self-contained, in that all of the artifacts necessary to run the contents of the contribution are found within the contribution itself. However, the contents of the contribution can make one or many references to artifacts that are not contained within the contribution. These references might be to SCA artifacts, or to other artifacts, such as Web Services Description Language (WSDL) files, XSD files, or to code artifacts such as Java class files.
• SCA application package deployment
  WAS v8.5 supports deployment of many types of SCA artifacts as composition units of business-level applications. Typical artifacts include JAR files, compressed .zip files, and web application archive (WAR) files.
• Create SCA business-level applications
  We can create an empty business-level application and then add SCA assets, shared libraries, business-level applications, and other artifacts as composition units to the empty business-level application.
• Update SCA composite artifacts
  We can view and update SCA composite artifacts in business-level applications.
• View SCA composite definitions
  We can view information on the definition of a SCA composite in the dmgr console.
• View SCA domain information
  We can view information on SCA composites in an SCA domain in the dmgr console.
• View and editing JMS bindings on references and services of SCA composites
  We can view information on a JMS binding for a SCA composite in the dmgr console. The JMS bindings page of the console displays the settings of a binding.jms element. We can use the console page to edit resource and response resource settings.
• Importing assets
  You must register application business logic such as Java EE archives, libraries, and other resource files with the product configuration as assets before we can add the assets to one or more business-level applications. Importing an asset registers it with the product configuration.
• SCA application package deployment
  WAS v8.5 supports deployment of many types of Service Component Architecture (SCA) artifacts as composition units of business-level applications. Typical artifacts include JAR files, compressed .zip files, and web application archive (WAR) files.
• Create SCA business-level applications
  We can create an empty business-level application and then add SCA assets, shared libraries, business-level applications, and other artifacts as composition units to the empty business-level application.
• Update SCA composite artifacts
  We can view and update Service Component Architecture (SCA) composite artifacts in business-level applications.
• View SCA composite definitions
  We can view information on the definition of a Service Component Architecture (SCA) composite in the dmgr console.
• View SCA domain information
  We can view information on Service Component Architecture (SCA) composites in an SCA domain in the dmgr console.
• View and editing JMS bindings on references and services of SCA composites
  We can view information on a JMS binding for a SCA composite in the dmgr console. The JMS bindings page of the console displays the settings of a binding.jms element. We can use the console page to edit resource and response resource settings.
• Export WSDL and XSD documents
  We can export Web Services Description Language (WSDL) and XML schema definition (XSD) documents used by a Service Component Architecture (SCA) composition unit to a location of your choice.

Related concepts:

Business-level applications
Assets
Composition units

Related

Administer business-level applications using programming
Administer applications using wsadmin.sh
Administer application servers
Importing assets
Manage assets
Start business-level applications
Stopping business-level applications
Update business-level applications
Delete business-level applications

Reference:

Business-level application page

+

Search Tips   |   Advanced Search