CIS 764 Database Systems Engineering L 12 1

CIS 764 Database Systems Engineering L 12. 1: Deployment Deploy … to place or arrange for deliberate (intended) purpose. e. g. to install middleware to the running server. Fall 2007 http: //www. cis. ksu. edu 1

CIS 764 Database Systems Engineering Recall the homework, previously given: Oracle tutorial: “ Web Application with ADF Business Components and JSF” includes master-detail page, a search page, and edit page. Do “in essence” to show some use of ADF components. http: //www. oracle. com/technology/obe 1013 jdev/masterdetail_adf_bc/master-detail_pagewith_adf_bc. htm The middleware application was run in the “embedded” server, e. g. a test server running in the development environment (not in the intended target server). Now, the final step (the “impossible” homework): (“impossible” only in that default CIS lab permissions block deployment. ) Fall 2007 http: //www. cis. ksu. edu 2

CIS 764 Database Systems Engineering Follow the general deployment tutorial: http: //www. oracle. com/technology/obe 1013 jdev/deployment. htm but: Use your JSF-ADF homework as the sample application (connected to the course sample data base). (Do not install the sample application given in the tutorial. ) Submission: (i) As usual, post a few screen shots and words. Show your use of the Enterprise Manager with access to your application. Show running the client with connection to the remote URL (not “localhost”). (ii) Set up a static page with the URL to your actual application; email a URL link to access your static page. (and have the application running when it is checked). Likely hours for checking the application: T, Th 1: 00 -2: 00 (for CIS labs) T, W, Th evenings for non- cis. ksu. edu Fall 2007 http: //www. cis. ksu. edu 3

CIS 764 Database Systems Engineering For CIS labs … we ( Bill, Aditi) are in process of working with CIS staff to allow permissions. We may need to change port numbers. Fall 2007 http: //www. cis. ksu. edu 4

CIS 764 Database Systems Engineering From previous tour of J 2 EE architecture, deployment is based on an Enterprise Application a. Rchive. JDev (and other tools) use a deployment descriptor file which identifies the application and target. EAR file: config file WAR file: manifest web components ( html, jsp, images, servlets, tag files) Model. jar file: manifest class ( ejbs, business components, etc. ) Fall 2007 http: //www. cis. ksu. edu 5

CIS 764 Database Systems Engineering Recall, these components deploy to web container and model (EJB) container, respectively. For stand alone applications that use J 2 EE resources, the application would deploy into an application container (on the application machine). See http: //java. sun. com/j 2 ee/1. 4/docs/tutorial/doc/Overview 3. html and http: //www. theserverside. com/tt/articles/content/J 2 EE-Deployment/chapter. html and http: //publib. boulder. ibm. com/infocenter/wasinfo/v 4 r 0/index. jsp? topic=/com. ibm. websphere. v 4. doc/wass_content/06060007. html Fall 2007 http: //www. cis. ksu. edu 6

CIS 764 Database Systems Engineering end. Fall 2007 http: //www. cis. ksu. edu 7