Getting Started with WebSphere Application Server

More documents

Recommendations

Info

172 Getting Started with WebSphere Application Server Community Edition prefix (for example org/apache/geronimo) of the organization that supplies the library. - Artifact is the file name prefix of the library. - Version is the version identifier of the library. - Type is the type of file, typically jar. When you package your application, you have to prepare a deployment plan (for example, for a Web application, a geronimo-web.xml under WEB-INF directory). The Community Edition server can look into the plan and the deployment descriptor (for example, for a Web application, a web.xml under WEB-INF directory) to find information about the application. If your application uses the library that you have just installed, you have to add a element under in the element in the application's deployment plan. Listing 9.4 provides an example of an application deployment plan showing dependencies. … Group Artifact Version Type … Listing 9.4 - Dependency snippet 9.6 Administering applications This section describes how to administer applications, such as managing their deployment, and stopping and starting them. 9.6.1 Deploying and undeploying applications When you finish packaging an application, you can deploy the application to the Community Edition server using the administrative console. For example, if you have a Web application cviewer-2.1.1.2.war under the directory usr/local/wasce_samples/cviewer/target, and the deployment plan under the
Chapter 9 – Administering Community Edition 173 directory usr/local/wasce_samples/cviewer/src/main/webapp/WEB-INF. Follow these steps to deploy your WAR: 1. Click Deploy New under applications. The resulting Install New Applications page is illustrated in Figure 9.5: Figure 9.5 - Installing new applications into Community Edition 2. In the Archive field, browse into the directory that includes the Web application, and select the WAR file. In this example we use usr/local/wasce_samples/cviewer/target/cviewer-2.1.1.2.war. 3. In the Plan field, browse into the directory that includes a deployment plan. For this example, use usr/local/wasce_samples/cviewer/src/main/webapp/WEB- INF/geronimo-web.xml. 4. Click Install. Figure 9.6 displays the resulting page of a successful installation. Figure 9.6 - Messages after a successful new application install into Community Edition 5. You can also verify the installation in the Installed Web Applications panel. Click Web App WARs under Applications. You can see the application cviewer in the running state as illustrated in Figure 9.7.
Page 3 and 4:
G E T T I N G S T A R T E D W I T H
Page 5 and 6:
Notices This information was develo
Page 7 and 8:
Trademarks IBM, the IBM logo, and i
Page 9 and 10:
3.8 Exercises .....................
Page 11 and 12:
9.3.2 Changing port numbers .......
Page 13 and 14:
13 Preface Keeping your skills curr
Page 15:
The DB2 on Campus book series 15
Page 18 and 19:
18 Getting Started with WebSphere A
Page 21 and 22:
1 Chapter 1 - Introduction to WebSp
Page 23 and 24:
Introduction to WebSphere Applicati
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 47 and 48:
3 Chapter 3 - Development with Comm
Page 49 and 50:
Chapter 3 - Development with Commun
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
4 Chapter 4 - Working with database
Page 67 and 68:
Chapter 4 - Working with databases
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
5 Chapter 5 - Enterprise Java Beans
Page 91 and 92:
1. Define local and remote interfac
Page 93 and 94:
Chapter 5 - Enterprise Java Beans 9
Page 95 and 96:
Page 97 and 98:
Note: Chapter 5 - Enterprise Java B
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
6 Chapter 6 - Messaging Messaging i
Page 111 and 112:
Chapter 6 - Messaging 111 3. Messag
Page 113 and 114:
Chapter 6 - Messaging 113 2. Get JM
Page 115 and 116:
Chapter 6 - Messaging 115 Figure 6.
Page 117 and 118:
Chapter 6 - Messaging 117 Figure 6.
Page 119 and 120:
Chapter 6 - Messaging 119 For examp
Page 121 and 122: textMessage.getText()); } catch (JM
Page 123 and 124: Chapter 6 - Messaging 123 3. Copy t
Page 125: Chapter 6 - Messaging 125 D. Messag
Page 128 and 129: 128 Getting Started with WebSphere
Page 161: PART III - ADMINISTERING COMMUNITY
Page 181 and 182: 10 Chapter 10 - Tuning a Community
Page 183 and 184: Chapter 10 - Tuning a Community Edi
Page 191 and 192: 10.4.2 Operating system tuning Chap
Page 193: Chapter 10 - Tuning a Community Edi
Page 211 and 212: A Appendix A - Solutions to review
Page 213 and 214: Appendix A - Solutions to review qu
Page 219 and 220: B Appendix B - Up and running with
Page 221 and 222: Appendix B - Up and running with DB
Page 223 and 224:
4. The following is performed by de
Page 225 and 226:
Appendix B - Up and running with DB
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235:
C Appendix C - Using the sample cod
Page 238 and 239:
238 Getting Started with WebSphere
Page 240:
240 Getting Started with WebSphere
show all

Getting Started with WebSphere Application Server

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?