HTTP

293 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
293
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

HTTP

  1. 1. Configure and run the SimpleOpenAccount application A mediation module is configured to select between multiple service endpoints in the WebSphere Service Registry and Repository (hereafter referred to as Service Registry). The selection is based on the Status attribute (set to available or unavailable) in the service metadata. IBM Tivoli Composite Application Monitor for SOA (Monitoring Agent) monitors the service traffic and updates the Status attribute to unavailable in Service Registry if a performance threshold is exceeded. Subsequent requests coming through the mediation module go through the endpoint query, which only returns endpoints with Status=available. The dynamic feedback mechanism ensures that only service endpoints that meet the recommended performance threshold are used to service requests. Configure and deploy the business process, mediation module and service endpoints The module is pre-configured so you will need to note some values that will be used to configure other components. The web service endpoints are configured to run on a WebSphere Application Server using port 9080. If you use a different port, update all the ports in the WSDL files for all the service endpoints. These can be found in the project for each of the service endpoints: EquinoxVerifyCreditServiceProject, ExterianVerifyCreditServiceProject and JKInternalVerifyCreditServiceProject. Import and configure the WebSphere Integration Developer artifacts 1. Start WebSphere Integration Developer and open the Business Integration perspective. 2. Import the SimpleOpenAccount.zip file into the workspace. 3. Select all the files in the zip file to be imported. 4. Change ports to reflect your server configuration. Refer to screenshot below.
  2. 2. 5. Expand the DynamicServiceSelection module and drill down to the DynamicServiceRouter. 6. Double click DynamicServiceRouter to open the mediation module. 7. Right-click the ServiceEndpointLookup primitive and click on Show in properties.
  3. 3. 8. Click on the Properties tab and click on Details. 9. Click on the Advanced tab. 10. Note the Version and Registry Name. 11. Note the Status property and Value under User Properties. Deploy and start components 1. Click on the Servers tab.
  4. 4. 2. Right-click WebSphere Process Server v6.1 and click Start. Wait until the server is started. 3. Right-click on the server and click Add and Remove Projects. 4. Click Add All. 5. Click Finish. Wait while the applications are deployed and started.
  5. 5. Configure Service Registry In this section you register your services in Service Registry. Make sure you edit the port value in all three service endpoint WSDL files to reflect your application serving port, before uploading to Service Registry Upload service documents to Service Registry 1. Make sure the Service Registry is started. 2. Open an Internet Explorer window and navigate to http://localhost:<service_registry_port>/ServiceRegistry 3. Expand Service Documents and click Load Documents. 4. Click Browse and select WSDLEquinoxVerifyCredit.wsdl. 5. Enter 1.0 for document version and click OK. 6. Follow the prompts and upload the missing documents VerifyCredit.wsdl, AccountBusinessObjects.xsd and AccountServiceObjects.xsd. 7. Click Add another document and repeat the upload for ExterianVerifyCredit.wsdl and JKInternalVerifyCredit.wsdl. 8. Click Finish to complete the document upload. Configure metadata with custom property 1. Expand Service metadata  WSDL. 2. Click on Ports.
  6. 6. 3. Select all three service endpoints as shown above. 4. Click Add Property. 5. Enter Status and available for the Name and Value pair. These entries are case- sensitive; make sure to use the same case in the mediation module. 6. Click OK to save this information. ITCAM for SOA configuration To configure ITCAM for SOA, review the Event Handler User’s guide. Event handler configuration The event handler is explained in detail in the WSRR Support Pac: (ftp://ftp.software.ibm.com/software/integration/support/supportpacs/individual/sa04. pdf) Here is a snapshot of our Event Handler configuration.
  7. 7. Test the application The OpenAccount business process is configured and ready for testing. The business process calls the Verify Credit mediation module to check the client’s credit worthiness. The module looks up the available service endpoints in the Service Registry and selects one to service the request. The response is sent back to the business process which completes the account open request. 1. Open a browser to http://localhost:<server_port>/TestClient/faces/Setting.jsp 2. Click New. 3. Click OpenAccount. 4. You can fill out the form with random information. If you choose not to, all the fields have default values so you shouldn’t have problems. 5. Scroll to the bottom of the Input Data form and click Create. 6. This action triggers the OpenAccount business process. 7. Use the Tivoli Enterprise Portal to observe the service traffic generated by this action. 8. Observe the console in WebSphere Integration Developer to determine which service endpoint is selected for each execution of the business process.
  8. 8. 9. The application is configured to exceed the response-time threshold with the first execution of the process. This should trickle through the monitoring tool in about 5 minutes. Keep an eye on the Status property of the selected endpoint Service Registry. It should change to unavailable when the Monitoring agent forwards the data to the Event Handler. 10. Execute the test again and observe that a different endpoint is chosen the second time. 11. The status of the first endpoint should be restored automatically to available after the Monitoring agent observes no more traffic on the endpoint in its next data collection interval.

×