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
Community Edition.
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
characteristics:
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
applications).
BLA1
EJB
module
Web
module
BLA3 BLA2
Java EE
Enterprise
application
Business
Logic
Configuration
Composition
JAX-WS
Web
service
module
Portlet
module
Java
library
DB2
database
CICS
transaction
Java
library
WARJAR Axis2 PAR JAR EAR