350 WebSphere Application Server V8.5 Concepts, Planning, and Design Guide
Figure 11-2 depicts an EJB OSGi bundle. An EJB bundle includes the EJB module along with
its OSGi metadata. It is then deployed as an OSGi bundle in an OSGi application.
Figure 11-2 EJB OSGi bundle
Application development and deployment support
OSGi bundles are packaged as JAR files. A single OSGi application is packaged in an
enterprise bundle archive (EBA) file, just as an enterprise application is packaged in an
enterprise archive file. WebSphere Application Server also supports deploying existing WAR
files as web application bundles to facilitate the use of an OSGi module system.
OSGi application development support is provided in IBM Rational Application Developer
V8.5 and WebSphere Developer Tools. OSGi application can be deployed to WebSphere
Application Server by using either the administrative console or wsadmin commands.
For more information about developing OSGi applications in WebSphere Application Server
11.2.3 Business-level applications
A business-level application is an application beyond the Java EE definition. A business-level
application is an administration model that provides the entire definition of an application as it
makes sense to the business. A business-level application is a WebSphere configuration
artifact, similar to a server or cluster, that is stored in the product configuration repository.
This grouping notion for enterprise level applications includes WebSphere and
Bundle-Name: Blog Biz
Chapter 11. Application development and deployment 351
non-WebSphere artifacts, such as SCA packages, libraries, and proxy filters, under a single
application definition. Business-level applications do not introduce new programming,
runtime, or packaging models. You do not need to change application business logic or
runtime settings. Figure 11-3 shows business-level applications.
Figure 11-3 Business-level applications
A business-level application has the following characteristics:
Lists one or more composition units that represent the application binary files.
Might not explicitly manage the lifecycle of every artifact.
Is a model that defines an application.
Does not represent or contain application binary files.
Can span more than WebSphere Application Server deployment target run times.
Examples include a proxy server, a web server, and WebSphere Application Server
Provides installation, distribution, activation, monitor, update, and removal management
features for applications.
Supports application service provider (ASP) scenarios by allowing single application
binary files to be shared between multiple deployments.
Aligns WebSphere applications closer with business as opposed to IT configuration.
In summary, a business-level application can be useful when an application has the following
Is composed of multiple packages.
Applies to the post-deployment side of the application lifecycle.
Contains additional libraries or non-Java EE artifacts.
Includes artifacts that run on heterogeneous environments that include WebSphere and
non-WebSphere run times.
Is defined in a recursive manner (for example, if an application includes other
WARJAR Axis2 PAR JAR EAR