General Guidelines for Selecting Your Development Tools

Upgrading Your Java EE Applications 4-3

4.4.2 Guidelines and Resources for Upgrading Deployment Descriptors for Oracle WebLogic Server

To prepare your applications for WebLogic Server deployment, you must remove OC4J-specific deployment descriptors and replace them with their equivalent WebLogic Server specific settings. For a successful deployment, examine each of the deployment descriptors and perform one the following actions for each deployment descriptor feature used by the application: ■ If the OC4J deployment descriptor feature has a direct mapping within the equivalent WebLogic Server specific deployment descriptor, then use the equivalent WebLogic Server descriptor with the appropriate elements and values. ■ If the OC4J deployment descriptor feature does not have a direct mapping, then review the appropriate Oracle WebLogic Server documentation. Features that are not directly mapped to Oracle WebLogic Server deployment descriptors can often be achieved by configuring the WebLogic domain accordingly. Table 4–2 provides a list of documentation resources that will help you upgrade your deployment descriptors to Oracle WebLogic Server. Table 4–1 J2EE, OC4J, and WebLogic Server Deployment Descriptors J2EE Standard Descriptor OC4J Proprietary Descriptor WebLogic Proprietary Descriptor application.xml orion-application.xml weblogic-application.xml web.xml orion-web.xml weblogic.xml ejb-jar.xml orion-ejb-jar.xml weblogic-ejb-jar.xml application-client.xml orion-application-client.xml weblogic-appclient.xml ra.xml oc4j-ra.xml weblogic-ra.xml webservices.xml oracle-webservices.xml weblogic-webservices.xml Table 4–2 Documentation Resources for Upgrading Deployment Descriptors to Oracle WebLogic Server When upgrading to this WebLogic-Specific Deployment Descriptor... Refer to these documentation resources... weblogic-application.xml Enterprise Application Deployment Descriptor Elements in Oracle Fusion Middleware Developing Applications for Oracle WebLogic Server weblogic.xml Appendix A, orion-web.xml and orion-ejb-jar.xml Upgrade Reference provides upgrade advice for each of the deployment descriptor elements in the orion-web.xml and orion-ejb.jar.xml files. weblogic-ejb-jar.xml Appendix A, orion-web.xml and orion-ejb-jar.xml Upgrade Reference provides upgrade advice for each of the deployment descriptor elements in the orion-web.xml and orion-ejb.jar.xml files. weblogic-appclient.xml Client Application Deployment Descriptor Elements in Oracle Fusion Middleware Programming Stand-alone Clients for Oracle WebLogic Server weblogic-ra.xml Configuring the weblogic-ra.xml File in Oracle Fusion Middleware Programming Resource Adapters for Oracle WebLogic Server 4-4 Oracle Fusion Middleware Upgrade Guide for Java EE

4.4.3 About Security Elements in Deployment Descriptor Files

If you use the suggested procedures in Section 5.3.6, Configuring Security on Oracle WebLogic Server , then the security configurations, including authentication methods, security constraints, and EJB method permissions, that are contained in standard Java EE application deployment descriptors, such as web.xml and ejb-jar.xml, can remain untouched for upgrade and will continue to function when the application is deployed to Oracle WebLogic Server. For security configurations specified in OC4J specific descriptors for example, security role mappings, see the WebLogic Server Security documentation to map each configuration to an element within the equivalent Oracle WebLogic Server deployment descriptor described in Section 4.4.1, Comparison of OC4J and Oracle WebLogic Server Deployment Descriptors .

4.4.4 Upgrading Deployment Plans

Deployment plans are a standard Java EE server capability supported by both Oracle WebLogic Server and OC4J. However, deployment plans are not portable between application servers. When you upgrade from OC4J to Oracle WebLogic Server, you must regenerate and save your application deployment plans saved as part of the deployment process on Oracle WebLogic Server. Alternatively, you can construct new deployment plans using the weblogic.PlanGenerator command line tool. For more information, see Overview of weblogic.PlanGenerator in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.

4.5 Task 5: Review Oracle WebLogic Server API Support

Before you can redeploy your Oracle Application Server 10g application on Oracle WebLogic Server, you must review your applications to identify the application programming interfaces referenced by the source code. For more information, refer to the following sections: ■ APIs Available With the Java Required Files JRF Domain Template ■ Other Oracle WebLogic Server API Requirements

4.5.1 APIs Available With the Java Required Files JRF Domain Template

Oracle Fusion Middleware11g provides an Oracle WebLogic Server domain template, referred to as the Oracle Java Required Files JRF template. You can use this template to create or extend an Oracle WebLogic Server domain. The resulting domain contains an updated version of some of the key capabilities and features of Oracle Application Server 10g. For more information, see Section 5.1.4, Using the Java Required Files JRF Domain Template . weblogic-webservices.xml WebLogic Web Service Deployment Descriptor Element Reference in Oracle Fusion Middleware WebLogic Web Services Reference for Oracle WebLogic Server Table 4–2 Cont. Documentation Resources for Upgrading Deployment Descriptors to Oracle WebLogic When upgrading to this WebLogic-Specific Deployment Descriptor... Refer to these documentation resources...