![]() When you deploy an independent WAR file, OC4J automatically creates a J2EE application and an EAR file to wrap it. You do not have to create an EAR file for simple Web applications. The OC4J default J2EE application is available to contain independent WAR files. Use an EAR file, a WAR file, loose files in a J2EE application directory structure, or loose files in a Web application directory structure.ĭefault J2EE application or J2EE application wrapper Table 5-1 OC4J in Sta ndalone Versus Oracle Application Server: Deployment Feature Table 5-1 summarizes OC4J deployment and configuration features, comparing OC4J standalone to OC4J in Oracle Application Server. Thus, you cannot locally manage your OC4J process by using the admin.jar tool or by manually updating configuration files, because this will conflict with the management provided by Enterprise Manager. Through Enterprise Manager, you can manage and configure your OC4J processes across multiple application server instances and hosts. Oracle Application Server can oversee multiple clustered OC4J processes and is managed through the Oracle Enterprise Manager 10 g. In an enterprise production environment, OC4J is contained within Oracle Application Server, which takes over management of the J2EE enterprise systems. Note:Key admin.jar commands are discussed under "Deployment Scenarios to OC4J Standalone".įor initial considerations when using OC4J standalone for development, including use of the OC4J development flag to trigger automatic recompilation and reloading of modified servlets, see "OC4J Standalone for Development". Using Oracle Deployment Tools Versus Expert Modes Overview: OC4J Standalone Versus the Oracle Application Server Environment The following sections provide some overview: ![]() Your primary information source for using OC4J in an Oracle Application Server environment, however, should be the Oracle Application Server Containers for J2EE User's Guide. ![]() ![]() This chapter gives an overview of deployment and configuration in Oracle Application Server, and Chapter 7, "Configuration with Enterprise Manager", offers additional information. When your application is ready for enterprise use, you can deploy it to the Oracle Application Server environment. Most of this chapter is specific to configuration and deployment in a standalone environment, where you are developing on the same system you are deploying to. OC4J standalone comprises a single OC4J instance outside the Oracle Application Server environment. General Overview of OC4J Deployment and Configurationīecause this is a developer's guide, much of it is intended for use in an OC4J standalone environment, which is convenient for application development stages. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |