Getting Started with WebSphere Application Server

More documents

Recommendations

Info

128 Getting Started with WebSphere Application Server Community Edition - A Web client, as shown in (4), that consumes Web Services in a Web application deployed in Community Edition As a part of the Java EE specification, users can also use the service reference tag to import a Web service to the Web client. This is shown in (5). Figure 7.1 - Community Edition Web services: The big picture Not shown in the figure is how to work with IBM Data Studio and DB2 to create Data Web services in minutes. This is discussed in section 7.4. 7.2 Developing Web Services in Community Edition Follow these steps to develop Web Services in Community Edition: 1. Create a Dynamic Web project to host the Web Services classes in Eclipse. 2. Create a Service Endpoint Interface (SEI) 3. Provide the SEI service implementation class 4. Declare the SEI implementation class in the web.xml file and deploy the Web project into Community Edition. Each of these steps will be discussed in more detail in the following sections.
Chapter 7 – Web services 129 7.2.1 Creating a Web Service project in Eclipse As discussed in earlier sections, you can create a Dynamic Web Project to host Web Services classes as follows: Note: 1. From Eclipse main menu, select File -> New -> Dynamic Web Project 2. In the New Dynamic Web Project dialog, input the Project Name, such as HelloServiceProject, and click Next 3. Keep the default values on the following pages and click Finish. We do not recommend you to use the Axis2’s Web Services wizard provided by the Eclipse Web Tools Platform (WTP) to create a Web Services project. 7.2.2 Creating a service endpoint interface Service endpoint interface (SEI) is a normal Java interface, which is used to describe what a Web service can do. To develop a SEI, you need to define an interface and annotate it with the @WebService annotation. In this section, you will use the Java First Development; this means that the WSDL document is not available and therefore you should not provide the wsdlLocation property; otherwise you will receive a WSDL file not found exception. This is illustrated in Listing 7.1 below. package com.ibm.wasce.samples; import javax.jws.WebService; @WebService (name="HelloPeople", targetNamespace="http://samples.wasce.ibm.com") public interface HelloPeople { public String sayHello(String targetName); } Listing 7.1 – SEI: HelloPeople.java Though in the above listing the @WebService annotation properties name and targetNamespace have some values, it is fine to provide the @WebService annotation without any properties to use defaults. 7.2.3 Providing the service implementation class After creating a SEI, you need to provide a Java bean to implement it. You have to designate the endpointInterface property when the service class is implementing a SEI as shown in Listing 7.2. package com.ibm.wasce.samples; import javax.jws.WebService; @WebService(serviceName = "HelloBillService",
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: Chapter 4 - Working with databases
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 97 and 98: Note: Chapter 5 - Enterprise Java B
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 130 and 131: 130 Getting Started with WebSphere
Page 161: PART III - ADMINISTERING COMMUNITY
Page 178 and 179:
178 Getting Started with WebSphere
Page 181 and 182:
10 Chapter 10 - Tuning a Community
Page 183 and 184:
Chapter 10 - Tuning a Community Edi
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
10.4.2 Operating system tuning Chap
Page 193:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 211 and 212:
A Appendix A - Solutions to review
Page 213 and 214:
Appendix A - Solutions to review qu
Page 215 and 216:
Page 217 and 218:
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:
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:
Page 240:
show all

Getting Started with WebSphere Application Server

Create successful ePaper yourself

Delete template?

Save as template?