Create a J2C application for an Information Management System (IMS) phonebook transaction using IMS TM Resource Adapter

Page 5 of 8  Document options PDF - Fits A4 and Letter 2957 KB (46 pages) Get Adobe® Reader® My developerWorks needs you! Connect to your technical community Rate this tutorial Help us improve this content

Task 4 (Optional): Create a Web service to invoke the J2C bean

In the previous sections, you installed a J2C Resource Adapter, created a J2C bean that executed against the IMS sample transaction: IVTNO. You also created a simple JSP TestClient that tested your J2C bean. In this optional section, you will wrap the J2C bean as a Web service, and then test it by using the generated WSDL file. You will then generate a Web service client and test it as well.

What is a Web service? Web services are self-contained, self-describing modular applications that can be published, located, and invoked across the Web. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction. The following standards play key roles in Web services: Web Services Description Language (WSDL) and Simple Object Access protocol (SOAP).

Creating a Web service

1. In the Project Explorer view, navigate to the J2C bean implementation class that was created previously.
   
   
2. Expand J2CPhoneBook > Java Resources: src > sample.ims, as shown in Figure 51.

3. Right-click the PhoneBookImpl.java and select New > Other from the context menu, as shown in Figure 52:

4. In the New wizard screen, select Web Page, Web Service, or EJB from J2C Java Bean and click Next, as shown in Figure 53:

5. Press Browse to look up the J2C bean Implementation class, as shown in Figure 54:

6. Type P, select the PhoneBookImpl class in package sample.ims and click OK, as shown in Figure 55:

7. This returns the fully-qualified implementation class in the dialog, as shown in Figure 56.
   
   
8. Press Next to continue.

9. Select Web Service as the J2EE Resource Type, as shown in Figure 57.
   
   
10. Click Next, and then Finish. The J2EE Resource from a J2C Java Bean wizard will now create the necessary J2EE resources for the Web service implementation. This might take a few moments.

11. Examine the generated J2EE resources for Web services.
    
    
12. Expand J2CPhoneBook > WebContent > WEB-INF > wsdl. Note the generated PhoneBookImpl.wsdl file and associated xml mapping files, as shown in Figure 58:
    
    

13. Double-click the PhoneBookImpl.wsdl file to open up the WSDL editor. Observe the visual representation of the wsdl file in the Design view, as shown in Figure 59. There is also a source view, if you prefer.
    
    

Note that the Web service operation is runPhoneBook and that the operation has one input and one output, and that these map to the INPUTMSG and OUTPUTMSG defined previously.

What is WSDL? Web Services Description Language (WSDL) is an XML-based open specification that describes the interfaces to and instances of Web services on the network. Businesses can make the WSDL documents for their Web services available though UDDI, WSIL, or by broadcasting the URLs to their WSDL via email or Web sites.

14. Note that the http://localhost:portnumber/... is generated. This tutorial uses port 9082.
    1. If the port number is not 9082, in the Design view, click the http that is displayed in http://localhost:portnumber/J2C....
    2. Click the Properties tab and change the port number to 9082, as shown in Figure 60.
    3. Save the changes (Ctrl+S).
       
       

15. Close the PhoneBookImpl.wsdl editor by pressing Ctrl+Shift+F4.
    
    

Back to top

Testing the Web service using Web Service Explorer

In this part of the tutorial, you will use the Web Services Explorer to test your Web service.

1. Make sure that WebSphere Application Server is running. You will test your Web service using the WebSphere Application Server test environment. Using the Servers view, note the Status. If the WebSphere Application Server is not running, press the green arrow on the Servers tab to start it, as shown in Figure 61. This will take a few moments.

2. From the Project Explorer view, right-click the PhoneBookImpl.wsdl file and select Web Services > Test with Web Services Explorer, as shown in Figure 62.

3. The Web Services Explorer window will launch. It contains two views: a Navigator view and an Actions view. To make more space, maximize the window by double-clicking the title, as shown in Figure 63:

4. The Actions view specifies both the operations and endpoints for the Web service. The Endpoint is defined as http://localhost:9082/J2CPhoneBook/services/PhoneBookImpl. Note that this is the location of the Web service and that it points to the WebSphere Application Server running on your local workstation and listening on port 9082, as shown in Figure 64:

5. Click the runPhoneBook operation, as shown in Figure 65:

6. This will invoke the WSDL operation, as shown in Figure 66:

7. Enter the necessary information to run the IVTNO transaction, as shown in Figure 67. These will be the same parameters used for TestClient.jsp:
   1. in__ll: 59
   2. in__zz: 0
   3. in__trcd: IVTNO
   4. in__cmd: DISPLAY
   5. in__name1: LAST1
   
   
   
8. Click Go to run the Web service:

9. The Web service executes, and the results are displayed in the runPhoneBookResponse object, as shown in Figure 68. Scroll through the Status window or resize the window, as necessary, to see the results:

10. Click the Source link to display the Web service results in the Form view, as shown in Figure 69:

11. This will display the actual SOAP response and SOAP request envelope. Scroll down to see the data being transmitted to and from IMS, as shown in Figure 70:

What is SOAP? Simple Object Access Protocol (SOAP) is an XML-based standard for messaging over HTTP and other Internet protocols. It is a lightweight protocol for the exchange of information in a decentralized, distributed environment. It is based on XML, and consists of three parts: An envelope that defines a framework for describing what is in a message and how to process it. A set of encoding rules for expressing instances of application-defined data types. A convention for representing remote procedure calls and responses.

12. Close all open editor windows (pressing Ctrl+Shift+F4 will accomplish this).

Back to top

Generating a Web service client and using it to test the Web service

In this part of the lab exercise, we will generate Web service client and test it with your Web service.

1. Make sure that WebSphere Application Server is running. Using the Servers view, note the Status. If the WebSphere Application Server is not running, press the green arrow on the Servers tab to start it, as shown in Figure 71. This will take a few moments.

2. From the Project Explorer view, right click the PhoneBookImpl.wsdl file and select Web Services > Generate Client, as shown in Figure 72.

3. The Web Service Client dialog opens. Move the slider all the way up to the Test client position so that the tool not only generates the client, but also deploys and tests it.
   
   
4. Click the Client project: J2CPhoneBook link, as shown in Figure 73:

5. In the following dialog, change the client project name from J2CPhoneBook to J2CPhoneBookWeb and click OK, as shown in Figure 74:

6. You will return to the Web Service Client form. Click Next. The dialog shown in Figure 75 displays:

7. Accept the defaults and click Next. If you see the warning shown in Figure 76, click Yes All:

8. On the dialog shown in Figure 77, clear all of the methods by clicking Deselect All, and then select only the runPhoneBook(sample.ims.data.INPUTMSG) method. That is the only method that you want to expose to your Client:

9. Click Finish. The warning shown in Figure 78 is normal. Click OK if it displays:

10. If you moved the slider to the Test Client position in Step 3, the client tool will generate the Web service client, deploy it into WebSphere Application Server and run it from the built-in Web browser, as shown in Figure 79:

The resulting JSP component looks exactly like the one in Step 4 in Task 3: Deploy and test your application > Testing your application.. The difference is in the way the JSP component calls the Java bean’s runPhoneBook() method, invoking it through a Web service instead of calling it directly.

11. Follow steps 6-9 in Task 3: Deploy and test your application > Testing your application again to test the Web service client.
    
    
12. When you are done testing, in the Server view, click the red square icon to stop the WebSphere Application Server, as shown in Figure 80:

13. Close all open editor windows (pressing Ctrl+Shift+F4 to accomplish this).

You have completed the optional Web service generation part of the J2C bean tutorial.

Back to top

	Page 5 of 8