Enterprise Application Web Application Enterprise JavaBean Resource Adapter
2.4.1 Enterprise Application
An Enterprise application consists of one or more of the following J2EE applications or modules: ■ Web applications ■ Enterprise Java Beans EJB modules ■ Resource adapter modules An Enterprise application is packaged as an archive file with an .ear extension, but is generally deployed as an exploded EAR directory. An exploded EAR directory contains all of the JAR, WAR, and RAR modules also in exploded format for an application as well as the XML descriptor files for the Enterprise application and its bundled applications and modules. See Developing Applications for Oracle WebLogic Server.2.4.2 Web Application
A Web application always includes the following files: ■ A servlet or JSP page, along with any helper classes. ■ A web.xml deployment descriptor, a J2EE standard XML document that configures the contents of a WAR file. Web applications may also contain JSP tag libraries, static .html and image files, supporting classes and .jar files, and a weblogic.xml deployment descriptor, which configures WebLogic Server-specific elements for Web applications. See Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server.2.4.3 Enterprise JavaBean
Enterprise JavaBeans EJBs are reusable Java components that implement business logic and enable you to develop component-based distributed business applications. EJB modules are packaged as archive files having a .jar extension, but are generally deployed as exploded archive directories. The archive file or exploded archive directory for an EJB contains the compiled EJB classes, optional generated classes, and XML deployment descriptors for the EJB. See Programming WebLogic Enterprise JavaBeans for Oracle WebLogic Server for more information on the different types of EJBs.2.4.4 Resource Adapter
A resource adapter also referred to as a connector adds Enterprise Information System EIS integration to the J2EE platform. Connectors provide a system-level software driver that WebLogic Server can use to connect to an EIS. Connectors contain both the Java classes, and if necessary, the native components required to interact with the EIS. See Programming Resource Adapters for Oracle WebLogic Server.2.4.5 Web Service
Parts
» Oracle Fusion Middleware Online Documentation Library
» Document Scope and Audience Guide to This Document
» Standards Compatibility Deployment Terminology
» Related Documentation New and Changed Features in This Release
» Overview of the Deployment Process Java EE 5 Deployment Implementation
» Enterprise Application Web Application Enterprise JavaBean Resource Adapter
» Web Service J2EE Library Optional Package
» JDBC, JMS, and WLDF Modules Client Application Archive
» weblogic.Deployer Administration Console WLST Deployment Tools for Developers
» Understanding Default Deployment Names Understanding Application Naming Requirements
» Steps for Creating an Application Installation Directory
» How FastSwap Deployment Works Supported FastSwap Application Configurations
» Enabling FastSwap In Your Application Application Types and Changes Supported with FastSwap
» Limitations When Using FastSwap
» Understanding Deployment Version Strings Best Practices for Preparing Deployment Files
» Deployment Configuration Life Cycle
» Understanding Application Deployment Descriptors Understanding WebLogic Server Deployment Plans
» Benefits of a Single Deployment Plan Workflow Single Deployment Plan Ownership and Limitations
» Benefits of a Multiple Deployment Plan Workflow Multiple Deployment Plan Ownership and Limitations
» Understanding Deployment Plan Contents
» Using an Existing Deployment Plan to Configure an Application
» How It Works Directory Structure
» Additional Configuration Tasks Best Practices for Managing Application Configuration
» Goals for Exporting a Deployment Configuration Tools for Exporting a Deployment Configuration
» Understanding Deployment Property Classifications
» Steps for Exporting an Applications Deployment Configuration Staging Application Files for Export
» Generating a Template Deployment Plan using weblogic.PlanGenerator
» Overview of Common Deployment Scenarios
» Deploying to a Single-Server Domain Deploying an Application with a Deployment Plan
» Understanding Deployment Targets Deploying to One or More Targets
» Deploying to a Cluster Target Enforcing Consistent Deployment to All Configured Cluster Members
» Module-Targeting Syntax Targeting Web Application Modules
» Staging Mode Descriptions and Best Practices
» Using Nostage Mode Deployment Syntax for Nostage Mode Using Stage Mode Deployment
» Syntax for Stage Mode Using External_stage Mode Deployment Syntax for external_stage Mode
» Understanding Deployment Behavior for Shared Libraries
» Registering Libraries with WebLogic Server Specifying Library Versions at Deployment
» Production Redeployment Overview of Redeployment Strategies
» Limitations of Auto-Deployment Understanding When to Use Different Redeployment Strategies
» How Production Redeployment Works
» Development Requirements Requirements and Restrictions for Production Redeployment
» Steps for Distributing a New Version of an Application Making an Application Available to Clients
» Redeploying Applications and Modules In-Place
» Stopping an Application to Restrict Client Access
» Undeploying an Application or Module
Show more