Several assembly tools exist that are graphical user interfaces for assembling enterprise or Java™ Platform, Enterprise Edition (Java EE) applications. You can use these tools to assemble an application and secure Enterprise JavaBeans™ (EJB) and Web modules in that application.
To secure an EJB module, a Java archive (JAR) file, a Web module, a Web archive (WAR) file, or an application enterprise archive (EAR) file, you can use an assembly tool. You can create an application, an EJB module, or a Web module and secure them using an assembly tool or development tools such as the IBM® Rational® Application Developer.
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.
However, a Java EE 5 or later module can exist within an application that includes pre-Java EE 5 files and uses the .xmi file name extension.
The ibm-webservices-ext.xmi, ibm-webservices-bnd.xmi, ibm-webservicesclient-bnd.xmi, ibm-webservicesclient-ext.xmi, and ibm-portlet-ext.xmi files continue to use the .xmi file extensions.
sptcfgIn this information ...Subtopics
Related tasks
Related reference
| IBM Redbooks, demos, education, and more(Index) |