Why and when to perform this task
WebSphere Application Server supports the J2EE model for creating, assembling, securing, and deploying applications. This article provides a high-level description of what is involved in securing resources in a J2EE environment. Applications are often created, assembled and deployed in different phases and by different teams.
Consult the J2EE specifications for complete details.
Steps for this task
Development tools, such as the Assembling applications with the AAT and the Deployment Tool for Enterprise
JavaBeans (EJBDeploy) are used to assemble J2EE modules and to set the attributes
in the deployment descriptors.
Development tools,
such as the Deployment Tool for Enterprise JavaBeans (EJBDeploy) and the Assembling applications with the Assembly Toolkit are
used to assemble J2EE modules and to set the attributes in the deployment
descriptors.
Most of the steps in assembling J2EE applications involve deployment descriptors; deployment descriptors play a central role in application security in a J2EE environment.
Application assemblers combine J2EE modules, resolve references between them, and create from them a single deployment unit, typically an Enterprise Archive (EAR) file. Component providers and application assemblers can be represented by the same person but do not have to be.
One of the important tasks the deployer performs is mapping actual users and groups to application roles. For z/SAS authorization, user or group to role mapping is done by the security administrator (through permission to a SAF EJBROLE representing the application role).
Results
Your applications and production environment are secured.