Getting Started with WebSphere Application Server

More documents

Recommendations

Info

206 Getting Started with WebSphere Application Server Community Edition http://www.ibm.com/software/webservers/appserv/community/ Available commands: ? Alias to: help exit Exit the shell clear Clear the terminal screen echo Echo or print arguments to STDOUT unset Unset a variable set Set a variable source Load a file/url into the current shell print Alias to: echo . Alias to: source help Show command help quit Alias to: exit Listing 12.1 – Starting the GShell Visit the following URL for more details about GShell commands: http://publib.boulder.ibm.com/wasce/V2.1.1/en/gshell.html 12.2 Customizing a new server assembly Community Edition is a flexible, component-based Java EE server. Most of the time, in our application or production environment, you will not need all the components of a Java EE application server. Users will only require some components critical to their applications available in the server. Community Edition provides two options for users to assemble a new server and customize which components to include: • Function-centric: you can choose the desired set of server plug-ins, such as Web Container, JMS and Java EE application deployment capabilities; • Application-centric: you can choose one or more application plug-ins, and Community Edition server will automatically encapsulate all other necessary plugins into the new server assembly. You can use the administrative console or GShell command deploy/assemble to assemble a customized server as needed. Visit the following URL for more details about customizable server assemblies: http://publib.boulder.ibm.com/wasce/V2.1.1/en/creating-custom-server-assemblies.html 12.3 Plug-in management The Community Edition server is assembled entirely out of plug-ins. A Community Edition plug-in is usually referred to as a Configuration archive (.car) file. You may download a plug-in from a remote running server or a plug-in repository, simply by specifying the
Chapter 12 – Advanced features 207 location or URL of the remote repository from the administrative console. In Community Edition, you can also export your applications or existing modules as plug-ins. A Community Edition plug-in is a jar-structured file that contains a META-INF/geronimoplugin.xml descriptor. A plug-in repository is basically a plug-in catalog together with a maven-structured repository containing plug-ins, which contains a geronimoplugins.xml file to list all available plug-ins in the repository. Visit the following URL for more details about plug-ins in Community Edition: http://publib.boulder.ibm.com/wasce/V2.1.1/en/managing-server-plugins.html 12.4 WADI Clustering Web application Distribution Infrastructure (WADI) is a project hosted on codehaus at http://wadi.codehaus.org/. WADI solution deals with session state in a cluster with a persistence mechanism in a distributed environment. WADI is integrated in Community Edition to provide an alternative clustering solution. In a traditional Tomcat clustering environment, the state of each session is replicated among nodes and maintained in memory, which impacts the performance significantly with more nodes added into the cluster. WADI can be used to solve this problem. To enable WADI clustering in Community Edition, follow the steps below: 1. Stop the server if it is running; 2. Enable relevant WADI modules by editing /var/config/config.xml with keywords load=”true”; 3. Update the deployment descriptor file, web.xml, of the application with keyword ; 4. Update embedded deployment plan geroimo-web.xml file of the application with keyword . Visit the following URL for more details about WADI clustering in Community Edition: http://publib.boulder.ibm.com/wasce/V2.1.1/en/configuring-wadi-clusters.html 12.5 Farming deployment Administering an application in a clustering environment is always painful. To make sure the status of a clustered application is well-maintained, each node in the cluster should be identical, which means users need to deploy the application to be clustered on each node. In a Community Edition server farm, you can reduce the workload greatly by leveraging Farming plug-ins. With this feature, once you deployed an application on one node, the application can be deployed on any other nodes in this cluster. To enable farming in Community Edition, follow the steps below:
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 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157: 156 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 235: C Appendix C - Using the sample cod
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?