[ Team LiB ] |
Deploying Applications and ModulesThe purpose of WebLogic Server is to host Java 2 Enterprise applications and modules. A J2EE application is deployed in an Enterprise Archive File (EAR). An EJB module is deployed in a Java Archive File (JAR), and a Web application module is deployed in a Web Archive File (WAR). The WebLogic Administration Console provides an easy-to-use interface for the deployment of
The first step in deploying either an application or module is to select the archive or exploded archive directory that contains the components and valid descriptors being deployed. Figure 35.27 shows the console page for deploying an application. The page enables you to navigate through the file system to select the archive that is being deployed. Figure 35.27. The Servers Configuration page enables you to select which WebLogic Server instances run on this machine.After selecting the archive, click the Target Application button to select the servers and/or clusters on which you would like to deploy the application or module. Figure 35.28 shows the console path for selecting targets for an application that is being deployed. Figure 35.28. The second step of deployment is to select the servers and/or clusters on which you would like to deploy.After checking the servers and/or clusters targeted for deployment, click the Continue button. The final step of deployment enables you to review your choices and deploy the application or module. Figure 35.29 shows the console page to deploy an application. Figure 35.29. The final step of deployment is to review your choices and deploy the application or module.When you click the Deploy button, you'll receive status information indicating the progress of the deployment. You might receive an error if the deployment is unsuccessful. NOTE For further information on deploying Web applications, see Chapter 7, "Deploying Web Applications." |
[ Team LiB ] |