- Standalone Enterprise Applications
- Application Server-Based Enterprise Applications
- Application Server Architecture Provider Roles
- Application Server Components
- Application Server Client Interfaces
- Application Server Client Implementations
- Enterprise Application Configuration and Deployment
- Application Service Management
- Conclusions
Conclusions
In this article, you got a glimpse of how application-server architectures handle the problem of building enterprise applications by partitioning an enterprise architecture into elements whose providers can encapsulate the proper level of knowledge to create those elements. The enterprise application container and server providers can thus focus on what they know best, which is to provide infrastructure and domain-independent services; likewise, enterprise application component developers can focus on what they know best, which is the business logic and data specific to a particular domain.
I also discussed how EJB makes implementing such enterprise application server components a simple task. EJB clients talk to EJBs using standard interface patterns and can also operate inside their own J2EE application client container environment. Finally, application servers and EJB can make configuring and deploying components and providing management services for components a simple matter of declaring properties in an XML file. Although standalone enterprise applications will still be key components of an enterprise-system solution, enterprise application servers and EJB can provide your enterprise with a central hub to rapidly deploy the lion's share of your enterprise system's business logic and data handling.