WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Assembling secured applications

Why and when to perform this task

There are several assembly tools that are graphical user interfaces for assembling enterprise (J2EE) applications. You can use these tools to assemble an application and secure EJB and Web modules in that application. An EJB module consists of one or more beans. You can enforce security at the EJB method level. A Web module consists of one or more Web resources (an HTML page, a JavaServer Pages (JSP) file or a servlet). You can also enforce security for each Web resource. You can use an assembly tool to secure an EJB module (Java archive (JAR) file) or a Web module (Web archive (WAR) file) or an application (enterprise archive (EAR) file). You can create an application, an EJB module, or a Web Module and secure them using an assembly tool or development tools like the IBM Rational Application Developer.

Steps for this task

  1. Secure EJB applications using an assembly tool. For more information, see Securing enterprise bean applications.
  2. Secure Web applications using an assembly tool. For more information, see Securing Web applications using an assembly tool.
  3. Add users and groups to roles while assembling secured application using an assembly tool. For more information, see Adding users and groups to roles using an assembly tool.
  4. Map users to RunAs roles using an assembly tool. For more information, see Mapping users to RunAs roles using an assembly tool.
  5. Adding the was.policy file to applications.
  6. Assemble the application components that you just secured using an assembly tool. For more information, see Assembling applications.

Result

After securing an application, the resulting .ear file contains security information in its deployment descriptor. The EJB module security information is stored in the ejb-jar.xml file and the Web module security information is stored in the web.xml file. The application.xml file of the application EAR file contains all the roles used in the application. The user and group to roles mapping is stored in the ibm-application-bnd.xmi file of the application EAR file.

The was.policy file of the application EAR contains the permissions granted for the application to access system resources.

The was.policy file of the application EAR contains the permissions granted for the application to access system resources protected by Java 2 security.

This task is required to secure EJB modules and Web modules in an application. This task is also required for applications to run properly when Java 2 security is enabled. If the was.policy file is not created and it does not contain required permissions, the application might not be able to access system resources.

What to do next

After securing an application, you can install an application using the administrative console. When you install a secured application, refer to the Deploying secured applications article to complete this task.



Sub-topics
Enterprise bean component security
Securing enterprise bean applications
Web component security
Securing Web applications using an assembly tool
Role-based authorization
Adding users and groups to roles using an assembly tool
Mapping users to RunAs roles using an assembly tool

Related concepts
Java 2 security policy files

Related tasks
Assembling applications
Adding the was.policy file to applications

Task topic    

Terms of Use | Feedback

Last updated: Mar 17, 2005 4:28:29 AM CST
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tsec_assemble.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)