HTTP bindings for imports and exports

© Copyright IBM Corporation 2008 All rights reserved 

IBM WebSphere Integration Developer and WebSphere Process Server V6.1 

Lab exercise 

SCA HTTP binding lab 

Overview of HTTP Binding – high level concept................................................................................................... 2 

Lab requirements .................................................................................................................................................. 2 

What you should be able to do ............................................................................................................................. 3 

Introduction to the lab example............................................................................................................................. 3 

Exercise instructions ............................................................................................................................................. 4 

Part 1: Set up the environment for Stock Quote (HTTP Binding) project ............................................................. 6 

Part 2: Create HTTP export bindings for the service provider ............................................................................ 10 

Part 3: Create HTTP import bindings for the client module ................................................................................ 18 

Part 4: Deploy the application ............................................................................................................................. 26 

Part 5: Test the application from the Web interface............................................................................................ 28 

Part 6: View HTTP traffic through TCP/IP monitor ............................................................................................. 29 

Part 7: Try out different data bindings................................................................................................................. 33 

Part 8: Try out different function selectors .......................................................................................................... 37 

Part 9: Explore HTTP binding configurations at runtime..................................................................................... 40 

What you did in this exercise .............................................................................................................................. 46 

Solution instructions ............................................................................................................................................ 47 

Task: Adding remote server to the WebSphere Integration Developer test environment .................................. 50 

2008 August, 19 IBM WebSphere V6.1 – Lab exercise Page 1 of 52 

SCA HTTP binding

© Copyright IBM Corporation 2008. All rights reserved 

Overview of HTTP Binding – high level concept 

The objective of this lab is to provide you with an understanding of how the new HTTP Binding works in 

WebSphere Integration Developer V6.1 and WebSphere Process Server V6.1. The support for HTTP Binding 

is same in WebSphere Enterprise Service Bus V6.1 as in WebSphere Process Server V6.1. 

HTTP binding allows existing, or newly-developed, HTTP applications to participate in a Service Oriented 

Architecture (SOA) managed through WebSphere Process Server or WebSphere Enterprise Service Bus, and 

allows a network of SCA runtimes to communicate across an existing HTTP infrastructure. 

The picture below shows the HTTP export used by invoking applications to send requests into a SCA module 

using HTTP(or HTTPS) protocols. The HTTP import allows the SCA module to invoke external applications 

using HTTP (HTTPS) protocol 

This allows clients to allow their existing HTTP application to invoke a SOA application, or allow SOA 

application to invoke HTTP applications. Many new Web 2.0 applications use HTTP as the underlying protocol. 

This facilitates tying the Web 2.0 applications in the SOA world. 

Lab requirements 

List of system and software required for the student to complete the lab. 

• WebSphere Integration Developer V6.1 with the integrated WebSphere Process Server V6.1 as the 

unit test server. 

• Lab Files – extract the Labfiles61SCA.zip to your C:\ (or any other directory). This archive file 

contains the following files: 

o 

o 

LabFiles61\HTTPBinding\HTTPBinding_SQuote_start_PI.zip - starting Project Interchange 

file 

LabFiles61\HTTPBinding\Solution\HTTPBinding_SQuote_Solution_PI.zip - complete lab 

solution Project Interchange file – refer to the Solution section at the end of this lab 

• Optional: Even though the lab instructions use the integrated unit test server within WebSphere 

Integration Developer, you can optionally, chose to use an externally installed WebSphere Process 

Server V6.1. You will need to configure for a new server in the servers view pointing to the external 

WebSphere Process Server V6.1 installation 




What you should be able to do 

At the end of this lab you should be able to: 

• Create and configure HTTP import and export bindings in the WebSphere Integration Developer V6.1. 

Understand how to set use the different data binding and the function selector options 

• Run the application and navigate through the Administration console to see the HTTP binding 

configurations. Use TCP/IP monitor view in WebSphere Integration Developer to view the HTTP traffic 

between the client and the provider. 

Introduction to the lab example 

In this lab, you will import a skeleton of a service provider Stock Quote application and a Stock Quote 

service client application, into the WebSphere Integration Developer workspace. You will then add HTTP 

bindings so that the client can send request and receive response from the service provider using HTTP 

application. The complete application looks like the one shown below abstractly. 

You will then work through the different configuration options of the HTTP bindings. 

The picture below depicts the structure of the application you work with in this lab: 

The Stock quote client module, called SQuoteClient shown on the left side of the picture above, is a simple 

SCA module that has a SCA POJO component being called from a JSP page through the stand-alone 

reference. The SCA POJO is wired to a HTTP import, called SQuoteHTTP. 

The HTTP request from the client contains the customer ID and the stock symbol. 

The Stock Quote service provider module, called SQuote, shown on the right side of the picture above is a 

simple SCA module receiving HTTP request through the HTTP export, called SQuoteHTTP. The service is 

provided by a SCA POJO component, called SQuote. The SCA POJO implementation contains some hard 

coded values to return as a response. It has been intentionally kept simple to keep the focus on the HTTP 

bindings. 

2008 August, 19 IBM WebSphere V 6.1 – Lab exercise Page 3 of 52 



The bottom half of the picture shows the actual components in WebSphere Integration Developer. The data 

within the module is represented as a Business object. The HTTP bindings perform the data transformation 

need to convert the BO to and from the HTTP payload. The diagram shows the BO and the HTTP payload at 

different points within the data flow. 

The HTTP import binding on the client side requires the URL of the service end point being invoked. In 

addition, it requires the data binding to perform the data translation. 

The HTTP export binding on the service provider side needs to expose the URL. In addition it needs the data 

binding for data transformation, and the function selector to determine the operation to invoke on the Interface 

of the service provider. 

Exercise instructions 

Some instructions in this lab are Windows ® operating-system specific. If you plan on running the lab on an 

operating-system other than Windows, you will need to run the appropriate commands, and use appropriate 

files (.sh or .bat) for your operating system. The directory locations are specified in the lab instructions using 

symbolic references, as follows: 

Reference variable Windows location AIX ® /UNIX ® location 

 

 

 

 

C:\IBM\WID61\runtimes\bi_v61 

C:\IBM\WID61 

C:\Labfiles61 

HTTPBinding 

Note for Windows users: When directory locations are passed as parameters to a Java program such as 

EJBdeploy or wsadmin, it is necessary to replace the backslashes with forward slashes to follow the Java 

convention. For example, replace C:\LabFiles61\ with C:/LabFiles61/ 




Instructions if using a remote server for testing 

Note that the previous table is relative to where you are running WebSphere Integration Developer. The 

following table is related to where you are running the remote test environment: 

Reference variable 

Example: Remote 

Windows test server 

location 

Example: Remote 

z/OS ® test server 

location 

Input your values for the 

remote location of the test 

server 

server1 sssr011 

 

C:\Program 

Files\IBM\WebSphere\AppServer 

/etc/sscell/AppServer 

localhost mvsxxx.rtp.raleigh.ibm.com 

8880 8880 

N/A 1023 

AppSrv01 default 

N/A ssadmin 

N/A fr1day 

Instructions for using a remote testing environment, such as z/OS, AIX ® or Solaris, can be found at the end of 

this document, in the section “Task: Adding remote server to the WebSphere Integration Developer test 

environment”. 




Part 1: Set up the environment for Stock Quote (HTTP Binding) project 

In this part of the lab, you will create a new WebSphere Integration Developer V6.1 workspace and import the 

HTTP Bindings project interchange into the workspace. 

____ 1. Start WebSphere Integration Developer V6.1 with a new workspace 

__ a. Select Start Programs IBM Software Development Platform IBM WebSphere 

Integration Developer IBM WebSphere Integration Developer from the start menu 

__ b. Enter or click the Browse button to set the new ‘Workspace’ location: 

\HTTPBinding\workspace (Ex: C:\Labfiles61\HTTPBinging\workspace) 

__ c. Click OK. The WebSphere Integration developer is launched 

__ d. Click the curved arrow at the top right to ‘Go to Business Integration perspective’ 

____ 2. Import the Project Interchange file, HTTPBinding_SQuote_start_PI.zip, into the workspace from 

directory \HTTPBinding. 

__ a. Right-click inside Business Integration View (top left view in the Business Integration 

Perspective) and select Import from the pop-up menu 




__ b. From the ‘Import’ panel, expand ‘Other’ and select ‘Project Interchange’ 

__ c. Click Next 

__ d. In the following ‘Import Project Interchange Contents’ panel, click the Browse button for 

“From zip file” and navigate to 

\HTTPBinding\HTTPBinding_SQuote_start_PI.zip and hit Open 




__ e. Click the Select All button to select all the check boxes for the projects listed 

__ f. Click Finish button (projects are imported and the auto-build will run) 

__ g. Verify you have Resources, SQuote, SQuoteClient and SQuoteWebClinet modules listed in 

the ‘Business Integration’ view 

__ h. Expand SQuoteClient module from the Business Integration view, and double click on 

“Dependencies” to open the Dependency editor. You should see the Resources project as the 

dependent library. Later before publishing the application to the server, you will add the 

SQuoteWebClient as the dependent J2EE dependency. The SQuoteWebClient contains 

index.jsp file that drives the input parameters to the application. 

____ 3. Verify you have WebSphere Process Server V6.1 listed in your ‘Servers’ view. You may or may not 

have the WebSphere ESB Server in the view, depending on whether you had selected to create a 

WebSphere ESB server profile during the install 




____ 4. Ensure the ‘Automatic Publishing’ is in the ‘Never publish automatically’ mode. By default the 

option select is ‘Never publish automatically’ 

__ a. In the ‘Servers’ view, right click on ‘WebSphere Process Server V6.1’ and select ‘Open’ from the 

pop-up menu. This opens the ‘Server Overview’ panel for WebSphere Process Server V6.1 

__ b. In the ‘Server Overview’ panel, expand ‘Automatic Publishing’ by clicking on the pull-down 

button ( ) and ensure the radio button for ‘Never publish automatically’ is selected 

__ c. Save the server configuration. File Save or Ctrl + S 

____ 5. Close the ‘Server Overview’ tab. 




Part 2: Create HTTP export bindings for the service provider 

In this part of the lab, you will generate HTTP export binding for the service provider, which is SQuote module; 

eventually you will configure and export bindings. 

____ 1. Generate HTTP export binding 

__ a. In Business Integration view, expand SQuote module and double click on Assembly Diagram 

( ) to open it in an Assembly Diagram editor 

____ 2. Right click on SQuote, that is SCA Java component and select Generate Export HTTP Binding 

from the pop-up menu. This opens the ‘Configure HTTP Export Service’ panel 

____ 3. To configure the ‘HTTP Export Binding’ follow the instructions below: 

__ a. Accept the default value /SQuoteExport as the ‘Context Path:’ for ‘End-point configuration’. 

This is used in building the URL for this endpoint and later used by the service client 

__ b. Click the Browse button for ‘Data binding cconfiguration:’ to set the ‘Data format’. This opens 

the ‘Data Binding Selection’ panel. The data binding class selected here will apply to all the 




Interface operations. If needed, you can override the data binding for each operation. Later, you 

will see where the data binding for each operation can be overridden 

1) In the ‘Data Binding Selection’ panel, select the radio button for ‘Show Data Binding 

classes’ and then select the HTTPStreamDataBindingXML class when listed. This will 

convert the internal Business object into XML data within HTTP payload. Later, you will see 

other options and view the outputs 

2) Click OK 

__ c. Now, click the Browse button for the ‘Function selector class:’ to set the ‘Function Selector’. 

This opens the ‘Function Selector Selection’ panel 

1) In the ‘Function Selector Selection’ panel, select the radio button for ‘Show Function 

Selector classes’ and then select the UrlMethodFunctionSelector class when listed. 

This will use the URL and HTTP method to build the function selector string. Later, you will 

see other options 




2) Click OK 

__ d. The final ‘Configure HTTP Export Service’ panel must look like the picture shown below: 

__ e. Click OK on the ‘Configure HTTP Export Service’ panel. You will see the SQuoteExport binding 

added to the module and wired to the SQuote SCA component as shown below: 

__ f. Save the Assembly Diagram. File Save or Ctrl + S 

____ 4. Configure and explore the HTTP Export Binding configuration properties 

__ a. Select the new SQuoteExport binding in the SQuote ‘Assembly Diagram’ editor, and then select 

the Properties tab at the bottom of the tool. You can expand the window to full screen of the tool 

to see all the options 

__ b. Select the Properties Description panel. Here you can see the general attributes of the binding 




__ c. Now, select the Properties Details panel. Here, you can view the export binding interface and its 

operations. For export, there are no quality of service qualifiers needed 

Stop and Think: Why can not you specify any quality of service qualifiers on export bindings? The qualifiers 

are specified on the Interface of the wired SCA component. 

__ d. Now, select the Properties Binding panel. Here you will see the values entered when creating 

the HTTP export binding, namely the context path, Data Binding class and the Function selector 

class. If needed, you can replace the values here. Later in the lab, you will change some of these 

options 




__ e. Select the Properties Advanced configuration panel 

1) In the HTTP Headers tab of the panel, you can modify or add Transfer encoding, Content 

encoding, Media type, character set and HTTP headers used by the HTTP response 

generated by the service provider HTTP Export. 

2) In the HTTP Method Settings tab, you can specify Pingable option on any HTTP method 

along with the status code returned by the ping. Any values specified in the Advanced 

configuration applies to all the Interface methods 

____ 5. The global values specified in the Bindings panel and ‘Advanced configuration’ panel can be 

overridden at the Interface operation level. The instructions below will show how to add, modify the 

values for each operation 

__ a. Select the Property ‘Method bindings’ panel and then select the ‘Generic’ tab for the 

‘getQuote’ method. Here, you can specify the native method names (used to compare with the 




function name returned by function selector class). The default native method name for operation 

"getQuote" is /SQuoteExport/getQuote@GET. This is returned by URL method function selector 

if the input request from /SQuoteExport/getQuote HTTP method is GET. However, the client is 

using HTTP POST method (since the payload as coming as a POST and not GET) and hence 

there will be a mismatch. You need to add the new native method that matches the HTTP POST 

method 

1) Click the ‘Add’ button for the ‘Native Method:’ and enter 

/SQuoteExport/getQuote@POST as a value in the ‘Add’ dialog 

2) Click OK. You should see "/SQuoteExport/getQuote@POST" added to the native method 

list 

3) Now, select /SQuoteExport/getQuote@GET from the native method list and then click the 

‘Remove’ button as you do not need it 

4) Save the Assembly Diagram. File Save or Ctrl + S 

__ b. Now, select the Property ‘Method bindings’ tab and then select the ‘Data Serialization’ tab for 

the ‘getQuote’ method. Here you can override the data binding class, specified during the initial 

configuration and seen in the Property Binding panel. You can specify separate data binding 

classes for input and output 




__ c. Now, select the ‘HTTP Headers’ tab on the Property Method bindings panel for the ‘getQuote’ 

method. Here, you can override or add Transfer Encoding, Content Encoding, Media type, 

Character set and HTTP headers value that have been specified for all the methods in the 

‘Advanced configuration’ panel 

__ d. Now, select the "HTTP Method Settings" tab on the Property ‘Method bindings’ panel for the 

‘getQuote’ method. Only HTTP methods present in this panel are accepted by the service 

provider. By default, only “GET” is allowed. If you need to accept other HTTP methods, or make 

any of them pingable, you will need to add the method here and override the Pingable option on 

any HTTP method along with the status code returned by the ping. 

__ e. Click on Add next to the table 

__ f. From the Add Pingable HTTP Method window, ensure that you have the following options: 

1) Method: POST 

2) Status Code: 200 




3) Click OK from Add Pingable HTTP Method window 

__ g. Now you should see one more Method Type, POST, added to the table 

__ h. Save the Assembly Diagram. File Save or Ctrl + S 

____ 6. To review the ‘Binding’ summary, select the Properties Summary panel. You can see the endpoint 

URL of the method getQuote as /SQuoteWeb/SQuoteExport/getQuote. The /SQuoteWeb is the 

Web context root of the module. The /SQuoteExport is the context root of the HTTP export binding, 

specified in the initial configuration panel. The /getQuote is the context root of the Interface method 

getQuote. You can now see how the entire end point URL is built. You will need this when configuring 

the HTTP Import binding on the client side 

____ 7. You have now completed creating and configuring the HTTP export bindings; explored the different 

configurations as well. You will come back later to explore other data binding and function selector 

options 




Part 3: Create HTTP import bindings for the client module 

In this part of the lab, you will generate HTTP import binding for the client module, which is SQuoteClient; 

eventually you will configure and import bindings. 

____ 1. Create HTTP import binding 

__ a. In Business Integration view, expand SQuoteClient module and double click on Assembly 

Diagram ( 

) to open it in an Assembly Diagram editor 

__ b. Select an Import from the ‘Palette’ (left side of the Assembly Diagram) and click to place it on to 

the canvas as shown below: 

__ c. Rename the name of the import to SQuoteHTTP in the properties panel. You will see the display 

name of the import change 

__ d. Hover over SQuoteHTTP and click the ‘Add Interface’ icon ( 

interface. The ‘Add Interface’ dialog opens. 

) that appears to add an 

1) Ensure the radio button next to ‘Show WSDL’ is selected 

2) Now, select ‘StockQuoteService’ listed form the matching interfaces 




3) Click OK 

__ e. From the SQuoteClient; the SCA component output reference, drag a wire and connect to the 

SQuoteHTTP import. This will add the wire 

__ f. Right click the SQuoteHTTP import and select Generate Binding HTTP Binding from the 

pop-up menu. This opens the ‘Configure HTTP Import Service’ panel 

____ 2. To Configure the ‘HTTP Import Binding’ follow the instructions below: 

__ a. For the ‘End-point configuration’ enter the ‘End-point URL’ as 

http://localhost:9080/SQuoteWeb/SQuoteExport/getQuote. This is the endpoint of the keep 




the default value for the context path of /SQuoteExport. This is used in building the URL for this 

endpoint and later used by the service client 

Note: The default HTTP port number might be different from 9080 depending on your environment. You might 

want to use the correct port number. 

__ b. Click the Browse button for ‘Data binding configuration:’ to set the ‘Data format’. This opens 

the ‘Data Binding Selection’ panel. The data binding class selected here will apply to all the 

Interface operations. If needed, you can override the data binding for each operation. Later, you 

will see where the data binding for each operation can be overridden 

1) In the ‘Data Binding Selection’ panel, select the radio button for ‘Show Data Binding 

classes’ and then select the HTTPStreamDataBindingXML class when listed. This will 

convert the internal Business object into XML data within HTTP payload. Later, you will see 

other options and view the outputs 

2) Click OK 

__ c. Ensure the check box for the ‘Generate TargetFunctionName message header property’ is 

selected. This is not currently used, but will be used later when using with 

HeaderHTTPFunctionSelector function selector class 

__ d. The final ‘Configure HTTP Import Service’ panel must look like the picture shown below: 




__ e. Click OK on the ‘Configure HTTP Import Service’ panel 

__ f. Save the Assembly Diagram. File Save or Ctrl + S. The Assembly diagram must looks like 

the picture shown below: 

____ 3. Configure and explore the HTTP Import Binding configuration properties 

__ a. Select the new SQouteHTTP import binding, and then select the Properties tab at the bottom of 

the tool. You can expand the window to full screen of the tool to see all the options 

__ b. Select the Properties Description panel. Here you can see the general attributes of the binding 

__ c. Now, select the Properties Details panel. Here, you can view the import binding Interface and its 

operations. For the operation getQuote, you can add Quality of service (QOS) qualifiers and 

event monitors. In this lab, you do not add any QOS or events 




__ d. Now, select the Properties Binding panel. Here you will see the values entered when creating 

the HTTP import binding, namely the endpoint URL of the service provider and the data binding 

class. In addition, you can specify the HTTP version and method. You will keep the HTTP 

version of 1.1. For the HTTP method, change it to POST (select from the drop down list) 

__ e. Save the configuration. File Save or Ctrl + S 

__ f. Now, select the Properties Advanced configuration panel. Any values specified in the 

Advanced configuration applies to all the Interface methods 

1) In the HTTP Headers tab of the panel, you can you can modify or add Transfer encoding, 

Content encoding, Media type, character set and HTTP headers used by the HTTP 

response generated by the service provider HTTP Export 




2) In the HTTP Proxy tab, you can specify any Proxy server or SSL proxy server that needs to 

be configured to call the service provider 

3) In the Security tab, you can specify the SSL or Basic Authentication Alias. These aliases 

are configured in the runtime where this application is deployed. Here, you just need to 

specify the name of the aliases. The Basic authentication uses username/password to 

authenticate the client whereas the SSL authentication uses SSL certificates and settings 

between the client server and the service provider. Setting the security settings is done by 

the server administrator; all you need to know is the authentication aliases. In addition, the 

administrator can also specify ad override many of the HTTP binding attributes in the 

runtime 

4) In the Performance tab, you can specify the read timeout for the response and the number 

of retries. Read timeout of 0 indicates that there is no timeout 




____ 4. The global values specified in the ‘Bindings’ panel and ‘Advanced configuration’ panel can be 

overridden at the Interface operation level. The instructions below will show how to add, modify the 

values for each operation 

__ a. Select the Property ‘Method bindings’ panel and then select the ‘Generic’ tab for the 

‘getQuote’ method. For the HTTP method, select POST and accept defaults for the other values 

__ b. Now, select the Property ‘Method bindings’ tab and then select the ‘Data Serialization’ tab for 

the ‘getQuote’ method. Here you can override the data binding class, specified during the initial 

configuration and seen in the Property Binding panel. You can specify separate data binding 

classes for input and output 

__ c. Now, select the ‘HTTP Headers’ tab on the Property Method bindings panel for the ‘getQuote’ 

method. Here, you can override or add Transfer encoding, Content encoding, Media type, 

character set and HTTP headers value that have been specified for all the methods in the 

"Advanced configuration" panel 




__ d. Select the "HTTP Proxy" tab on the Property ‘Method bindings’ panel of method "getQuote". 

Here, you can override the proxy settings 

__ e. Select the "Security" tab on the Property ‘Method bindings’ panel of method "getQuote". 

Here, you can override the SSL and Basic authentication aliases 

__ f. Select the "Performance" tab on the Property ‘Method bindings’ panel of method "getQuote". 

Here, you can override the performance attributes 

____ 5. To review the ‘Binding’ summary, select the Properties Summary panel. You can see the endpoint 

URL of the service provider that is invoked. This is the one you had used during the initial configuration 

of the HTTP import binding 

____ 6. Save the configuration. File Save or Ctrl + S 

. 

. 




Part 4: Deploy the application 

In this part of the lab, you will add the SQuoteWebClient module as a J2EE dependency to SQuoteClient 

module and deploy the J2EE project to the WebSphere Process Server test environment. 

____ 1. In Business Integration view, expand on SQuoteClient module and double click on ‘Dependencies’ 

( ) to open the Dependency Editor 

__ a. In the Dependency Editor, expand J2EE and click the Add button to add SQuoteWebClient as 

J2EE dependent project 

__ b. From the J2EE Project Selection panel, select SQuoteWebClient listed and click OK 

__ c. Ensure that the check box next to Deploy with Module is selected by selecting the 

SQuoteWebClient module. This module contains the index.jsp page that is used to drive the 

input to the application. 

__ d. Save the dependency editor. File Save or Ctrl + S 

____ 2. Start the WebSphere Process Server 

__ a. If using a remote testing environment, follow the directions provided in Task: Adding Remote 

Server to WebSphere Integration Developer Test Environment at the end of this document 

to add a server to the WebSphere Integration Developer test environment and start it. This is 

especially true for z/OS, AIX, Solaris remote test environment, where the WebSphere Integration 

Developer is remote to the test environment 

__ b. If using a local test environment ,right click on WebSphere Process Server V6.1 and select 

‘Start’ ( )from the pop-up menu 

__ c. Wait until the sever status is indicated as Started 

____ 3. Add the J2EE project to the configured projects on the server 




__ a. From the ‘Servers’ view, right click on WebSphere Process Server V6.1 and select Add and 

Remove projects… from the pop-up menu. The ‘Add and Remove Projects’ panel opens 

__ b. From the ‘Add and Remove Projects’ panel, click the ‘Add All’ button to add the available 

projects to the configured projects 

__ c. Click Finish 




Part 5: Test the application from the Web interface 

In this part of the lab, you will test the SQuote application by accessing the SQuoteClient module though the 

Web interface. 

____ 1. In the Business Integration view, expand ‘SQuoteClientWeb Web Content’, right click the 

‘index.jsp’ file and select ‘Run as Run on Server’ from the pop-up menu. Select ‘WebSphere 

Process Server V6.1’ listed from the ’New Server’ panel. This opens an embedded browser as shown 

below: 

Note: Alternatively, you can open the embedded browser within WebSphere Integration Developer V6.1. Click 

the Web browser icon ( ) located on the toolbar to open the embedded Web browser and enter the URL: 

http://localhost:9080/SQuoteWebClient/index.jsp where as 9080 is the default HTTP port bound to the 

application. 

To find the default HTTP port, right click on the ‘WebSphere Process Server V6.1’ in the ‘Servers’ view and 

select the ‘Run administrative console’ from the pop-up menu. In the administrative console, expand ‘Servers’ 

in the left navigation pane and click on the ‘Application servers’ link. In the right pane, click the ‘server1’ link. In 

the following page, expand ‘Ports’ under the ‘Communications’ category and locate the entry corresponding to 

‘WC_defaulthost’. 

____ 2. Enter the following values an click the ‘Submit’ button 

• Enter Stock Symbol : ibm 

• Enter Customer ID : 123 

____ 3. You must expect the following result: 

• Stock value is : 20.0 

• Customer’s service level is : Silver 

____ 4. Continue playing with a different customer ID. The symbol does not play any role, except it cannot be 

null 




Part 6: View HTTP traffic through TCP/IP monitor 

In this part of the lab, you will see the HTTP payload between the service client and provider, using the 

built-in TCPIP monitor. This is useful to see how the data bindings convert the internal representation of data 

as Business objects to the actual HTTP payload as XML or SOAP or any custom bindings. For the TCPIP 

monitor to view the traffic, the service clients will need to send the data to a port that TCP/IP monitor is 

listening, which will then forward the request to the service provider. 

____ 1. Open the TCP/IP monitor view 

__ a. From the main menu, select ‘Window Show View Other’. This opens the ‘Show View ’ 

panel 

__ b. In the ‘Show View’ panel, expand ‘Debug’ and then select ‘TCP/IP Monitor’ 

__ c. Click OK. The TCP/IP Monitor view is opens and is shown at the bottom frame of the 

workbench 

__ d. You can change the position of the TCP/IP monitor or maximize it if you find you need more 

space to work within the monitor view 




____ 2. Configure TCP/IP monitor to listen on port 9079 (you can use any unused port besides 9079) 

__ a. In the TCP/IP monitor view, click on the pull-down button ( ), located on the top right corner of 

the monitor view panel and select ‘Properties’. The ‘Preferences’ panel for the TCP/IP Monitor 

opens 

__ b. Remove or stop any existing defined monitors by selecting them and then clicking the ‘Remove’ 

button 

__ c. On the TCP/IP Monitor preferences panel, click the Click Add button to enter a new monitor. The 

‘New Monitor’ panel opens. Enter the following entries, keeping the rest of the defaults: 

• Local monitoring port: 9079 

• Host name : localhost 

• Port : 9080 

• Click OK 

__ d. Select the newly added monitor and click the Start button to the start monitoring port 9079 

__ e. Click OK over the ‘TCP/IP Monitor’ preferences panel 




____ 3. On the TCP/IP monitor view, click on the pull-down button ( ) located on the top right corner of the 

panel and enable ‘Show Header’ option. This will show the HTTP headers within the traffic 

____ 4. 

On the request side and response side of the monitor view, change the data to be shown from Byte 

to XML. This can be done by the selecting drop down list on both the request and response side 

____ 5. You are now ready to view the HTTP traffic. However, the service client is sending the request on 

port 9080. It needs to be modified to use port 9079 on which the monitor is listening. Modify the ports 

for the service client, SQuoteClient 


Diagram ( 


__ b. Select SQuoteHTTP import component and select the Properties view 

__ c. In the Properties view, select ‘Method Binding’, expand "Bound Methods" in the Import section 

of the view, and then select getQuote operation 

__ d. Click on the Generic tab and change the endpoint URL port from 9080 to 9079. The final 

endpoint URL should look like ‘http://localhost:9079/SQuoteWeb/SQuoteExport/getQuote’ 

__ e. Save the configuration. File Save or Ctrl + S 

____ 6. You are now ready to republish, run the application and view the HTTP traffic. Republish the 

application on the server 




__ a. In the ‘Servers’ view, right click on the WebSphere Process Server V6.1 and then select 

‘Publish’ from the pop-up menu. This should update the SQuoteClient application on the server 

__ b. In the Business Integration view, expand ‘SQuoteClientWeb Web Content’, right click the 


Process Server V6.1’ listed from the ’New Server’ panel. This opens the embedded browser. 

__ c. Enter the values and click the ‘Submit’ button. (Refer Part 5 of this lab) 

__ d. View the HTTP payload in the ‘TCP/IP Monitor’ view. You can see the headers and the XML 

payload (since the data binding used is HTTPStreamDataBindingXML) 

: 

. 




Part 7: Try out different data bindings 

So far, you have used HTTPStreamDataBindingXML for the input and the output. Hence the HTTP 

request and response contain the data payload as XML. Here, you will use XML payload on the HTTP request 

but receive the HTTP response as SOAP payload. 

____ 1. 

Modify the data bindings for the HTTP Import on the client side: 


Diagram ( 


__ b. Select the SQouteHTTP import binding, and then select the Properties tab at the bottom of the 

tool 

__ c. In the Properties view, select Method bindings and then select the ‘Data Serialization’ for the 

getQuote method 

__ d. Click the Browse button for the Input data binding. On the ‘Data Binding Selection’ panel, select 

the radio button next to ‘Show Data binding class’ and then select 

‘HTTPStreamDataBindingXML’ 

__ e. Click OK 

__ f. Click the Browse button for the ‘Output data binding’. On the ‘Data Binding Selection’ panel, 

select the radio button for ‘Show Data binding class’ and then select 

‘HTTPStreamDataBindingSOAP’ 




__ g. Click OK 

__ h. Save the configuration. File Save or Ctrl + S 

____ 2. Modify the data bindings for the HTTP Export on the service provider side 



__ b. Select the SQouteExport export binding, and then select the Properties tab at the bottom of the 

tool 

__ c. In the Properties view, select Method bindings and then select the ‘Data Serialization’ for the 


__ d. Click the Browse button for the ‘Input data binding’. On the ‘Data Binding Selection’ panel, select 

the radio button next to ‘Show Data binding class’ and then select 

‘HTTPStreamDataBindingXML’ 





__ f. Click the Browse button for the ‘Output data binding’. On the ‘Data Binding Selection’ panel, 

select the radio button for ‘Show Data binding class’ and then select 

‘HTTPStreamDataBindingSOAP’ 

__ g. Click OK 




____ 3. Save the configuration. File Save or Ctrl + S 

____ 4. You are now ready to republish, run the application and test the new function selector. Republish the 



‘Publish’ from the pop-up menu 





____ 5. View the HTTP payload in the ‘TCP/IP Monitor’ view. The HTTP request has a payload of XML data 

where as the HTTP response sends back payload as SOAP data 




Part 8: Try out different function selectors 

Function selector determines the method to invoke on the HTTP export of the service provider. In this part, 

you will explore the use of HeaderHTTPFunctionSelector as the Function selector for the service provider. 

This Function selector uses the value of the HTTP header property "TargetFunctionName" as the returned 

function name. The input HTTP request must contain the "TargetFunctionName" header property. 

If you recall during the creation of the HTTP import binding on the SQuoteClient module, you had selected 

the option to generate "TargetFunctionName" message header property. This adds the 

TargetFunctionName with a value of getQuote (uses method name as the value) 

____ 1. 

In Business Integration view, expand SQuoteClient module and double click on Assembly Diagram 


__ a. Select the SQouteHTTP import binding, and then select the Properties tab at the bottom of the 

tool 

__ b. In the Properties view, select Method bindings tab and then select the ‘HTTP Headers’ tab for 

the getQuote method. You should see the property TargetFunctionName with value getQuote. 

If you had created the import without generating the TargetFunctionName property, you can 

add the property in this panel 

____ 2. Set up the function selector on the HTTP export on the service provider 



__ b. Select the SQouteExport export binding, and select the Properties view at the bottom of the 

tool 

__ c. In the Properties view, select Binding tab 

__ d. Click Browse for the Function Selector. On the Function Selector Selection panel, select the 

radio button for ‘Show Function Selector class’ and then select 

‘HeaderHTTPFunctionSelector’ listed, 





__ f. In the Properties view, select Method bindings and then select the ‘Generic’ tab for the 


__ g. For the Native method, click Add. Enter getQuote in the text entry panel 

__ h. Click OK. The client adds TargetFunctionName property with the value of getQuote 




__ i. Save the Assembly Diagram. File Save or Ctrl + S 

____ 3. You are now ready to republish, run the application and test the new function selector. Republish the 



‘Publish’ from the pop-up menu 





____ 4. View the HTTP payload in the TCP/IP Monitor view. Notice that the HTTP request contains 

TargetFunctionName header property with the value of getQuote, This is used by 

HeaderHTTPFunctionSelector to return the native method on the service provider 




Part 9: Explore HTTP binding configurations at runtime 

In this part of the lab, you will explore the HTTP binding configurations in the WebSphere Process Server 

runtime environment. You will navigate the administrative console and see what HTTP binding attributes can 

be modified and where within the console you can work with the attributes. 

____ 1. 

Open administrative console and explore the SCA modules 

__ a. In the ‘Servers’ view, right click the ‘WebSphere Process Server V6.1’ and select ‘Run 

administrative console’ from the pop-up menu. This opens the WebSphere Process Server’s 

administrative console 

__ b. Log in by providing the username and password values ( default username: admin, default 

password: admin) 

__ c. In the left navigation pane of the administrative console, expand ‘Applications’ and click on 

‘SCA modules’. You should see your SCA modules, SQuote and SQuoteClient. You may see 

other SCA modules that come with the Process Server. In this SCA modules panel, you can see 

the containing application and its status (running, stopped, and so on.). You can also start or 

stop the application running those SCA modules from this panel 

____ 2. Explore HTTP import binding 

__ a. Click on SQuoteClient SCA module. In the following panel, expand the Module components; 

Imports and Exports. There are no exports in this module. Expand on the SQuoteHTTP import 

and then expand on the Interface and Bindings 




__ b. Click on HTTP binding. In the following binding panel, you can modify the binding attributes. The 

panel has two tabs, "Binding Scope" and "Method Scope". The Binding scope applies to all the 

methods of the Interface, whereas the Method Scope applies to a selected method on the 

Interface 




__ c. In the binding panel’s Binding scope tab, you can modify the target service endpoint URL, the 

HTTP method, version, authentication, encodings, proxy settings and response timeout 

__ d. Now, click on the ‘Method Scope’ tab. Here you can select the method and then enable the 

method scope to modify the attributes at the method level. Once the method scope is enabled, 

you can change the attributes of the target service endpoint URL, the HTTP method, version, 

authentication, encodings, proxy settings and response timeout. 

__ e. Return back to SCA module panel by click on the SCA modules on the top of the panel 

____ 3. Explore HTTP export binding 

__ a. Click on SQuote SCA module. In the following panel, expand the Module components Imports 

and Exports. There are no imports in this module. Expand on the SQuoteExport export and then 

expand on the Interface and Bindings 




__ b. Click on HTTP binding. In the following binding panel, you can modify the binding attributes. The 

panel has two tabs, "Binding Scope" and "Method Scope". The Binding scope applies to all the 

methods of the Interface, whereas the Method Scope applies to a selected method on the 

Interface 




__ c. In the binding panel Binding scope tab, you can view the context path and modify ‘Pingable 

HTTP’ methods and encodings 

__ d. Click on the ‘Method Scope’ tab. Here you can select the method and then enable the method 

scope to modify the attributes at the method level. Once the method scope is enabled, you can 

view the context path and modify ‘Pingable HTTP’ methods and encodings. 

____ 4. Close the administrative console 







What you did in this exercise 

You have imported the ‘HTTPBinding_SQuote_start_PI.zip’ project interchange file to a new workspace. 

Created and configured HTTP import and export bindings in the WebSphere Integration Developer V6.1. 

Explored how to set use the different data binding and the function selector options 

Deployed the application and navigated through the administrative console to see the HTTP binding 

configurations. 




Solution instructions 

If you want to directly see the solution, there is a complete solution Project Interchange file available for 

you. 

____ 1. 

Start WebSphere Integration Developer V6.1 with a new workspace 

__ a. Select Start Programs IBM Software Development Platform IBM WebSphere 

Integration Developer IBM WebSphere Integration Developer from the start menu 

__ b. Enter or click the Browse button to set the new ‘Workspace’ location: 

\\solution_workspace (Ex: 

C:\Labfiles61\HTTPBinding\solution_workspace) 

____ 2. Import the Project Interchange file, HTTPBinding_SQuote_Solution_PI.zip, into the workspace from 

directory \HTTPBinding\Solution 

__ a. Right-click inside Business Integration View (top left view in the Business Integration 

Perspective) and select Import from the pop-up menu 

__ b. From the ‘Import’ panel, expand ‘Other’ and select ‘Project Interchange’ 




__ c. Click Next 

__ d. In the following ‘Import Project Interchange Contents’ panel, click the Browse button for 

“From zip file” and navigate to 

\HTTPBinding\Solution\HTTPBinding_SQuote_Solution_PI.zip and hit Open 




__ e. Click the Select All button to select all the check boxes for the projects listed 

__ f. Click Finish button (projects are imported and the auto-build will run) 

__ g. Verify you have Resources, SQuote, SQuoteClient and SQuoteWebClinet modules listed in 

the ‘Business Integration’ view 

____ 3. Verify you have WebSphere Process Server V6.1 listed in your ‘Servers’ view 

____ 4. Ensure the ‘Automatic Publishing’ is in the ‘Never publish automatically’ mode. By default the 

option select is ‘Never publish automatically’ 

__ a. In the ‘Servers’ view, right click on ‘WebSphere Process Server V6.1’ and select ‘Open’ from the 

pop-up menu. This opens the ‘Server Overview’ panel for WebSphere Process Server V6.1 

__ b. In the ‘Server Overview’ panel, expand ‘Automatic Publishing’ by clicking on the pull-down 

button ( ) and ensure the radio button for ‘Never publish automatically’ is selected 

__ c. Save the server configuration. File Save or Ctrl + S 

____ 5. Close the ‘Server Overview’ tab 

____ 6. 

Repeat all the steps of Part 4 (Deploying application) and Part 5 (Testing application). You can 

optionally, also perform Part 6 (View HTTP traffic through TCP/IP monitor) 




Task: Adding remote server to the WebSphere Integration Developer test 

environment 

This task describes how to add a remote server to the WebSphere Integration Developer test environment. 

This example uses a z/OS machine. 

____ 1. 

Define a new remote server to WebSphere Integration Developer. 

__ a. Right click on the background of the Servers view to access the pop-up menu. 

__ b. Select New Server. 

__ c. In the New Server dialog, specify the remote server’s host name, . 

__ d. Ensure that the appropriate server type, ‘WebSphere Process V6.1 Server’ or ‘WebSphere 

ESB v6.1 Server’, is highlighted in the server type list 

__ e. Click Next. 




__ f. On the WebSphere Server Settings page, leave the radio button for SOAP selected, changing the 

SOAP connector port to the correct setting (). If security is on in your server, 

check the box for ‘Security is enabled on this server’ and input for the user ID and 

for the password. 

__ g. Click Finish. 

__ h. The new server should be seen in the Server view. 

____ 2. 

Start the remote server if it is not already started. WebSphere Integration Developer does not 

support starting remote servers from the Server View. 

__ a. From a command prompt, telnet to the remote system if needed: 




‘telnet ’ 

User ID : 

Password : 

__ b. Navigate to the bin directory for the profile being used: 

cd /profiles//bin 

__ c. Run the command file to start the server: ./startServer.sh 

__ d. Wait for status message indicating server has started: 

ADMU3200I: Server launched. Waiting for initialization status 

ADMU3000I: Server sssr01 open for e-business; process id is 0000012000000002

HTTP bindings for imports and exports

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

Delete template?

Save as template?