WAS v8.5 > Deploy applications > Deploy SCA composites > Deploy SCA business-level applications

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.

Configure the target application server. You must deploy SCA composite assets of a business-level application to a v8.x server (target) or to a v7.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 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

Optionally, determine what assets or other files to add to your business-level application and whether the application files can run on your deployment targets. We can create business-level applications using the dmgr console, wsadmin, or programming.

We create SCA business-level applications the same way as for non-SCA business-level applications. However, when we 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 dmgr console pages that apply only to applications that use SCA composites.

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

   Ways to create SCA business-level applications. We can create a business-level application using the dmgr console, wsadmin scripts, or programming.

   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: Creating an SCA business-level application with the console.
   wsadmin scripts See Set up business-level applications using wsadmin.sh.	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 Create an empty business-level application using programming.	Use programming to create an empty business-level application.

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

3. Save the changes to your administrative configuration.

Results

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

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 your business-level application.
2. Add assets, shared libraries, or other business-level applications as composition units.

   If the asset or application uses OASIS support, specify a v8.5 target.

   If the asset or application uses Feature Pack for SCA v1.0.1 functionality, specify a v8.x target or a feature pack v1.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 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 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.

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

• Create SCA business-level applications with the console
  We can create an empty business-level application and then add SCA assets, shared libraries, or business-level applications as composition units to the empty business-level application.
• Example: Creating an SCA business-level application with the console
  We can add many different types of artifacts to business-level applications. For example, we can add applications or modules, Java archives (JAR files), data in compressed files, and other business-level applications. This example describes how to create an empty business-level application and then add a SCA JAR file to the application using the dmgr console.
• Provide HTTP endpoint URL information settings for SCA composites
  Use this page to specify endpoint Universal Resource Locator (URL) prefix information for SCA composites accessed by web service bindings. The information is used to form complete endpoint addresses.
• SCA composite component settings
  Use this page to view and edit the attributes associated with a SCA component.
• SCA component reference settings
  Use this page to view and edit the attributes associated with a SCA component reference.
• SCA component service settings
  Use this page to view and edit the attributes associated with a component service.
• JMS binding settings for SCA composites
  Use this page to view property settings for a JMS binding that connects SCA composite references or services. Also use this page to edit resources of the JMS binding. The settings shown on this page define a binding.jms element.
• Service provider policy sets and bindings collection for SCA composites
  Use this page to attach and detach policy sets to a composition unit, a service provider, its endpoints, or operations of a SCA composite. We can select the default bindings, create new application-specific bindings, or use bindings created for an attached policy set. We can view or change whether the service provider can share its current policy configuration.
• SCA service provider settings
  Use this page to manage policy sets for a SCA web service provider. We can attach and detach policy sets to a service provider, its endpoints, or operations. We can select the default bindings, create new application-specific bindings, or use bindings created for an attached policy set. We can view or change whether the service provider can share its current policy configuration.
• References policy sets and bindings collection for SCA composites
  Use this page to attach and detach policy sets to a composition unit, a service reference, its endpoints, or operations of a SCA composite. We can select the default bindings, create new application-specific bindings, or use bindings created for an attached policy set. We can view or change whether the service reference can share its current policy configuration.
• SCA service client settings
  Use this page to manage policy sets for a SCA web service client. We can attach and detach policy sets to a service reference, its endpoints, or operations. We can select the default bindings, create new application-specific bindings, or use bindings created for an attached policy set. We can view or change whether the service reference can share its current policy configuration.
• Create SCA business-level applications with the console
  We can create an empty business-level application and then add SCA assets, shared libraries, or business-level applications as composition units to the empty business-level application.
• Composition unit settings
  Use this page to view composition unit settings and to change the configuration properties of a composition unit. The specific settings available for configuration can vary, depending upon the contents of the composition unit. For example, there are additional configuration settings if the asset contained in the composition unit is an SCA composite, or an OSGi application.
• JMS binding settings for SCA composites
  Use this page to view property settings for a JMS binding that connects SCA composite references or services. Also use this page to edit resources of the JMS binding. The settings shown on this page define a binding.jms element.
• Provide HTTP endpoint URL information settings for SCA composites
  Use this page to specify endpoint Universal Resource Locator (URL) prefix information for SCA composites accessed by web service bindings. The information is used to form complete endpoint addresses.
• SCA composite component settings
  Use this page to view and edit the attributes associated with a SCA component.
• SCA component reference settings
  Use this page to view and edit the attributes associated with a SCA component reference.
• SCA component service settings
  Use this page to view and edit the attributes associated with a component service.
• Service provider policy sets and bindings collection for SCA composites
  Use this page to attach and detach policy sets to a composition unit, a service provider, its endpoints, or operations of a Service Component Architecture (SCA) composite. We can select the default bindings, create new application-specific bindings, or use bindings created for an attached policy set. We can view or change whether the service provider can share its current policy configuration.
• References policy sets and bindings collection for SCA composites
  Use this page to attach and detach policy sets to a composition unit, a service reference, its endpoints, or operations of a Service Component Architecture (SCA) composite. We can select the default bindings, create new application-specific bindings, or use bindings created for an attached policy set. We can view or change whether the service reference can share its current policy configuration.
• SCA service provider settings
  Use this page to manage policy sets for a Service Component Architecture (SCA) web service provider. We can attach and detach policy sets to a service provider, its endpoints, or operations. We can select the default bindings, create new application-specific bindings, or use bindings created for an attached policy set. We can view or change whether the service provider can share its current policy configuration.
• SCA service client settings
  Use this page to manage policy sets for a Service Component Architecture (SCA) web service client. We can attach and detach policy sets to a service reference, its endpoints, or operations. We can select the default bindings, create new application-specific bindings, or use bindings created for an attached policy set. We can view or change whether the service reference can share its current policy configuration.
• Example: Creating an SCA business-level application with the console
  We can add many different types of artifacts to business-level applications. For example, we can add applications or modules, Java archives (JAR files), data in compressed files, and other business-level applications. This example describes how to create an empty business-level application and then add a Service Component Architecture (SCA) JAR file to the application using the dmgr console.

Related

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 using wsadmin.sh
Start business-level applications using scripting
Deploy business-level applications

Reference:

Business-level application settings
Composition unit settings

+

Search Tips   |   Advanced Search