Distributed Objects   «Prev  Next»

Lesson 9J2EE roles for development and deployment.
Objective What are the J2EE Roles defined for development and deployment?

J2EE Development and Deployment Roles

We explored earlier the way EJBs separate the business logic from the "plumbing".
This means that different people, within the development team for an application, can play different roles.

Bean Provider A "Bean Provider" is an expert in the business rules and logic of the service the bean provides.
He or she writes the bean so that it conforms to the contract with the container.
The bean provider will also package the bean in an EJB jar file together with a deployment descriptor that contains the structural information and any supporting classes.
They may also include application assembly information.
Application Assembler Assembles multiple beans into a single deployment unit. They may be the same person as the Bean Provider. They can also modify the following information:
  1. EJB's service name (not the bean's class name)
  2. Values of environment variables
They must not change the structural information, but can add security information and change method permissions.
Container Provider Provides deployment tools for the deployment of the bean into the server/container. They must fulfill the container side of the contract with the bean.
Deployer Deploys the bean using the tools provided by the Container Provider.
System Administrator Configures the container and server; sets up security management; and monitors run time of the deployed EJB application
Client Programmer Writes applications that access the enterprise beans via their home and remote interfaces.