Web Components 

Compatible WAR Files

The application’s Web components are packed in a WAR file, which is packed in the EAR file. This EAR file is deployed on the J2EE Engine 7.0. The WAR file must consist of:

●      The Web components

●      web.xml, which must be J2EE 1.2 or 1.3 compliant

●      web-j2ee-engine.xml – a J2EE Engine-specific deployment descriptor that contains specific deployment settings

The deployment descriptors are located in a WEB-INF directory in the WAR file.

The Web Container in J2EE Engine 6.20 is compatible with the J2EE 1.2 standards (the JavaServer Pages Specification 1.1 and the Java Servlet Specification 2.2). That is, the Web applications running on J2EE Engine 6.20 can be developed according to the J2EE 1.2. However, if they have additional deployment properties, these properties are specified in the standard web.xml. These applications do not have web-j2ee-engine.xml.

Use the SAP NetWeaver Developer Studio or the Deploy Tool to redeploy your Web application on the J2EE Engine 7.0.

You do not have to redeploy each component of your application. When you convert or redeploy the application’s EAR file, the converter will automatically convert the deployment descriptors in the application’s WAR files as described below.

Using the SAP NetWeaver Developer Studio

If you use the SAP NetWeaver Developer Studio to assemble your Web application and to deploy it on J2EE Engine 7.0, the SAP NetWeaver Developer Studio will create the necessary J2EE compliant deployment descriptors, compose an SDA file, and it will also deploy the application through the SDM.

Using the Deploy Tool

If your Web application contains specific settings in web.xml, then the background converter will replace the existing web.xml with a J2EE compatible web.xml, and will create the web-j2ee-engine.xml in which it will store the additional deployment properties. If the Web application does not contain specific deployment properties, the Web application will be deployed as is, that is, the converter will not modify the existing web.xml.

Required Changes

In J2EE Engine 6.20, the thread in which JavaServer Pages and Servlets are executed was granted administrative rights by default. In J2EE Engine 7.0, it is granted guest rights. Therefore, if your Web application requires administrative rights, you must set a run-as identity to a security role, which is granted administrative rights. The run-as identity is specified in the <run-as>element in web.xml.

<run-as>      <role-name>Administrator</role-name> </run-as>

 

For information about the main incompatible changes in the Web Container between J2EE Engine 6.20 and 7.0, and how to solve any possible problems arising from these changes, see Web Container.

 

See also:

Developing Web Applications in the Development Manual