Chapter 4.1 : Deployment in Web

Chapter 4.1 : Deployment in Web

1. 4.1.1 Define steps to deploy a web application

   • 1. Arrange the resources (Servlet,JSPs, static files and deployment descriptors)in the prescribed directory format
     • 2. Write the Web Application deployment descriptor(web.xml).
       • 3. Create the WebLogic-Specific Deployment Descriptor (weblogic.xml)
         • 4. Archive the file in the above directory structure into a .war.file.
           • 5. Deploy the Web Application on WebLogic Server in one of two ways using the Administration Console or by copying the Web Application into the applications directory of your domain
             • 6. Assign deployment attributes for your Web Application

2. 4.1.2 Understand the directory structure

   • WebApplicationName/
     • Place your static file such as HTML files and JSP files in this directory(or a Subdirectory)
       • /WEB-INF/web.xml
         • The Web Application deployment descriptor that configures the Web Application
           • /WEB-INF/weblogic.xml
             • The WebLogic-specific deployment descriptor file that defines how named resources in the web.xml file are mapped to resources residing elsewhere in WebLogic Server
               • /WEB-INF/classes
                 • Contains server-side classes such as HTTP servlets and utility classes
                   • /WEB-INF/lib
                     • Contains .jar files used by the Web Application

3. 4.1.3 Configuring URI’s and Web Applications

   • You construct the URL used to access a Web Application from a client by using the following pattern
     • http://hoststring/ContextPath/servletPath/pathInfo
       • Where:
         • Hoststring is either a host name that is mapped to a virtual host or hostname:portNumber
           • ContextPath is the name of your Web Application
             • servletPath is a servlet that is mapped to the servletPath
               • pathInfo is the remaining portion of the URL, typically a file name

4. 4.1.4 Configuring JSP in web

   • An app can use JavaServer Pages (JSPs) to implement web pages. JSPs are servlets defined using static content (such as HTML) mixed with Java code.
     • Configuring JSP Tag Libraries
       • Weblogic Server, in accordance with the Servlet 2.2 specification provides the ability to create and use custom JSP tags.
         • Custom JSP tags are Java classes that can be called from within a JSP page
           • To create custom JSP tags, you place them in a tag library and define their behavior in a tag library descriptor (TLD) file.
             • You can install JSP tag libraries with the <taglib> element
               • A tag library has a path to the JSP Tag Library Descriptor (TLD) file (<taglib-location>) and a URI that JSPs use to select the library for loading (<taglib-uri>). This URI pattern must match the value in the taglib directive in your JSP pages.
                 • This TLD must be made available to the Web Application containing the JSP by defining it in the Web Application deployment descriptor.
                   • It is a good idea to place the TLD file in the WEB-INF directory of your Web Application, because that directory is never available publicly.
                     • For example, if the taglib directive in the JSP page is: <%@ taglib uri="myTaglib" prefix="taglib" %>
                       • and the TLD is located in the WEB-INF directory of your Web Application, you would create the following entry in the Web Application deployment descriptor: <taglib>     <taglib-uri>myTaglib</taglib-uri>    <taglib-location>WEB-INF/myTLD.tld</taglib-location> </taglib>