Deployment

Publish in

Documents

12 views

Please download to get full document.

View again

of 16
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Share
Description
Downloads | Product Documentation | Support secure search Documentation OTN Home Oracle Forums C ommunity eDocs Home BEA WebLogic Server 8.1 Documentation Deploying WebLogic Server Applications Overview of WebLogic Server Deployment Deploying WebLogic Server Applications Overview of WebLogic Server Deployment The following sections provide a basic overview of key BEA WebLogic ServerTM deployment topics: Deployment Units Deployment Files Deployment Targets Staging Modes Deployment Nam
Tags
Transcript
  pdfcrowd.comopen in browserPRO version Are you a developer? Try out the HTML to PDF API eDocs Home > BEA WebLogic Server 8.1 Documentation > Deploying WebLogic Server Applications > Overview of WebLogic Server Deployment Deploying WebLogic Server Applications   Overview of WebLogic Server Deployment The following sections provide a basic overview of key BEA WebLogic Server TM  deployment topics:Deployment Units Deployment FilesDeployment TargetsStaging ModesDeployment NamesDeployment ToolsSecurity Roles Required for Deployment  secure search   Documentation   Downloads | Product Documentation | SupportOTN Home Oracle Forums Community   pdfcrowd.comopen in browserPRO version Are you a developer? Try out the HTML to PDF API Document Scope and Audience This document is written mainly for Administrators who want to deploy Java 2 Platform, Enterprise Edition (J2EE)applications or application modules to WebLogic Server. This document assumes that you are working in aproduction environment, which is generally characterized by multiple WebLogic Server instances or clusters runningon multiple machines. It also assumes that you have one or more application module archive files that have beentested and are ready to deploy on a production server.If you are an engineer and need to deploy or package applications in a development environment, see DevelopingWebLogic Server Applications. Also see Deployment Topics for Developers on page 4-13 for information about deployment features that apply to development environments.  Deployment Units A deployment unit   refers to a J2EE application (an Enterprise Application or Web Application) or a standalone J2EEmodule (an EJB or Resource Adapter) that has been organized according to the J2EE specification and can bedeployed to WebLogic Server.For each type of deployment unit, the J2EE specification defines both the required files and their location in thedirectory structure of the application or module. Deployment units may include Java classes for EJBs and servlets,resource adapters, Web pages and supporting files, XML-formatted deployment descriptors, and even othermodules.J2EE does not specify how   a deployment unit is deployed on the target server—only how standard applications andmodules are organized. WebLogic Server supports deployments that are packaged either as archive files using the jar  utility, or as exploded archive directories. Standalone Modules J2EE provides specifications for creating standalone modules, which include Enterprise JavaBeans and resource  pdfcrowd.comopen in browserPRO version Are you a developer? Try out the HTML to PDF API adapter modules. WebLogic Server also supports deploying Web Services modules, which are not part of the J2EEspecification.Standalone modules generally provide parts of a larger, distributed application, but do not necessarily provide adirect user interface. For more information on a particular module type, refer to the J2EE 1.3 specification at:http://java.sun.com/j2ee/download.html#platformspec. Enterprise JavaBean Enterprise JavaBeans (EJBs) are reusable Java components that implement business logic and enable you to developcomponent-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 directoryfor an EJB contains the compiled EJB classes, optional generated classes, and XML deployment descriptors for theEJB. See Programming WebLogic Server Enterprise JavaBeans  for more information on the different types of EJBs. Resource Adapter  A Resource Adapter (also referred to as a connector) adds Enterprise Information System (EIS) integration to theJ2EE platform. Connectors provide a system-level software driver that WebLogic Server can use to connect to anEIS. Connectors contain both the Java classes, and if necessary, the native components required to interact withthe EIS. See Programming WebLogic Server J2EE Connectors  for   more information. Note: Resource Adapters cannot be deployed as exploded archive directories. Web Services Web Services are a type of service that can be shared by and used as components of distributed Web-basedapplications. They commonly interface with existing back-end applications, such as customer relationshipmanagement systems, order-processing systems, and so on.A Web Service module is a virtual module that includes both a Web Application and a Web Service deploymentdescriptor at minimum. A Web Service module may also include EJBs that implement the Web Service. SeeProgramming WebLogic Web Services for more information.  pdfcrowd.comopen in browserPRO version Are you a developer? Try out the HTML to PDF API Deployable Applications J2EE also defines several different types of deployable applications: Web Applications, Enterprise Applications, andclient applications. Applications generally include one or more standalone J2EE modules to provide a logical service,and may also provide a direct user interface to the applications' contents. 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 WARfile.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 WebApplications. See Developing Web Applications for WebLogic Server for more information. Enterprise Application An Enterprise Application consists of one or more of the following J2EE applications or modules:Web ApplicationsEnterprise Java Beans (EJB) modulesResource Adapter modulesAn Enterprise Application is packaged as a JAR file with an .ear  extension, but is generally deployed as an explodedEAR 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 andmodules. See Developing WebLogic Server Applications for more information.

Previous Document

MODUL 06

We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks