Import an OSGi application as an enterprise bundle archive
(EBA) asset, then add the asset to a business-level application by
creating an EBA composition unit.
About this task
To deploy an OSGi application in
WebSphere® Application Server, you import your
OSGi application (EBA file) as an asset and create an empty business-level
application. You then add a composition unit to the business-level
application. This composition unit consists of the new EBA asset plus
configuration information for the context roots, virtual hosts, security
role mappings, and web module or Blueprint resource bindings for your
OSGi application.
Note: - An EBA file can be imported into only one asset.
- An EBA asset can be added to only one business-level application.
A business-level application is scoped to cell scope, so this means that only one instance of a given OSGi application can be deployed in a cell.
This
topic describes the specific task of deploying an OSGi application
as a business-level application. The more generalized task of creating
a business-level application, and adding assets and other artifacts
to the business-level application in the form of a composition unit,
is described in Creating business-level applications.
Each
step can be performed using either the administrative console or wsadmin
commands. You can also create an empty business-level application
or add a composition unit using programming.