[AIX Solaris HP-UX Linux Windows]

Set Java EE composition unit relationships for SCA composites (deprecated)

Use this page to associate Service Component Architecture (SCA) components in an SCA composite with Java™ Platform, Enterprise Edition (Java EE) applications, otherwise known as enterprise applications or enterprise archive (EAR) files.

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.

An SCA composite definition can define Java EE applications as component implementations. You can define an EAR asset on an archive attribute of the implementation.jee tag for the component and use the application deployed from the asset as its implementation. On this page, associate SCA components in a business-level application with the EAR files named in the composite definition.

This administrative console page displays in the business-level application creation and update wizards. To view the Set Java EE composition unit relationship page, the asset that you add to a business-level application must contain an SCA composite. To view this page, complete the following actions:

  1. Import an asset that contains an SCA composite.
  2. Create a business-level application to which to add the asset.
  3. Click Applications > Application Types > Business-level applications > application_name > Add > Add Asset.
  4. On the Add composition unit page, select the SCA composite asset and click Continue.
  5. On the Set options page, change the settings as needed and click Next.
  6. On the Map composition unit to a target page, specify target servers as needed and click Next.
  7. On the Define relationship with existing composition units page, change the settings as needed and click Next.
  8. Continue changing settings as needed and click Next on any other pages until the Set Java EE composition unit relationship page is displayed in the wizard.

Component Name

Specifies the name of an SCA component in the SCA composite that you are deploying.

EAR Asset Name

Specifies the name of the enterprise application, or EAR file, that the SCA component uses.

An EAR asset is an EAR file that has been imported as an asset. The EAR asset name must match the archive attribute on the implementation.jee tag in the SCA composite definition.

Associated Java EE Composition Unit

Specifies the composition unit name of the EAR asset. Select the Java EE composition unit that the SCA component uses. To associate an SCA component with an EAR file, the EAR file must be a composition unit of your SCA business-level application.

If the Java EE composition unit that you want to associate with an SCA component is not in the drop-down list, import the EAR file that is named by the archive attribute on the implementation.jee tag of the SCA composite definition as an asset. Then, add the EAR asset as a composition unit of this business-level application.

You can use the Import an asset and Add an asset links on this page to add EAR files as assets and make them composition units of your SCA business-level application.