- Import the SCA asset.
- Go to the business-level application settings page.
Click .
- On the business-level application settings page, specify
the type of composition unit to add.
Although you can
add an asset, shared library, or business-level application to your
business-level application, the logic is in your SCA asset. Add the
SCA asset as a composition unit.
Under Deployed assets,
click .
- On the Add page, select one unit from the list of available
units, and then click Continue.
On
the Add page, you might be able to select multiple deployable SCA
composites. However, the Feature Pack for SCA supports deploying only
one deployable composite at a time. Select only one unit and click Continue.
If you select multiple units, the product deploys only one of those
units.
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.
- On the Set options page, change the composition unit
settings as needed, and then click Next.
This page is not shown if you have multiple deployable unit
assets.
- On the Map composition unit to a target page, specify
one target server that is enabled for the Feature Pack for SCA, and
then click Next.
The target server
can be an existing cluster. To map the composition unit to a cluster,
select the existing cluster from the Available list,
click Add, and then click Next.
The cluster name is shown in the Current targets list
as WebSphere:cluster=cluster_name.
You
must specify only a single server or cluster as the target, and not
map an SCA composition unit to multiple servers or clusters.
If
you are adding an SCA asset that uses security, specify a target server
that is 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.
This page is not shown
when you add a business-level application.
- On the Relationship options page, click Next to
accept the default values.
The relationships in SCA
applications are set at the asset level. Either the asset must be
defined as an SCA contribution or, in the asset view, a relationship
must be set to another asset. When a relationship is set to another
asset manually at the asset level, the relationship only exposes all
the packages within the asset to the other depended asset. The namespaces
are not exposed.
This page is shown only for SCA assets that
have multiple deployable or composition units.
On the Set Java EE composition
unit relationship page, associate SCA components with Java EE applications
and then click Next. Java EE
applications are also known as enterprise applications or enterprise
archive (EAR) files. An SCA composite definition can specify an EAR
file to use on the archive attribute of an implementation.jee tag.
Use this page to associate SCA components in this business-level application
to the EAR files named in the composite definition. If your SCA application
does not use EAR files, take the default values and click Next.
- On the Map security roles to users or groups page, specify
security roles for users or groups as needed, and then click Next.
This page is only shown for SCA assets that use security.
- On the Map RunAs roles to users page, map a user identity
and password to RunAs roles as needed, and then click Next.
This page is only shown for SCA assets that use security.
- On the Map virtual host page, specify a virtual host
that hosts Web services for each SCA composite, and then click Next.
By default, composites map to default_host.
This page is only shown for SCA assets that contain a Web
service binding.
- On the Attach policy set page, attach a policy set and
assign policy set bindings as needed, and then click Next.
This page is only shown for SCA assets that use Web services.
- On the Summary page, click Finish.
Several messages are displayed, indicating whether the
product adds the unit to the business-level application successfully.
A message having the format Completed res=[WebSphere:cuname=unit_name] indicates
that the addition is successful. Click Manage application.
If
the product adds the unit successfully, the name of the unit is shown
in a list of deployed assets on the business-level application settings
page.
If the unit addition is not successful, read the messages
and add the unit again. Correct the problems noted in the messages.
- On the Adding composition unit to the business-level
application page, click Save.