8/10/2019 REST Uses the HTTP Protocol to Identify

1/2

REST uses the HTTP protocol to identify, query and manipulate resources in a computer network. To fulfill its task, RESTuses the information provided by the HTTP protocol. Namely these are:

the HTTP request method (e.g. GET)

the request URL (e.g. http://essential.craftforge.net/example/wine)

the request headers (e.g. the accepted media type(s))

the request body (e.g. some XML)

An URL is responsible for allocating a resource and can contain parameters in its query part. The HTTP method is used forchoosing the right action to be performed on the resource. Request headers provide meta data for accessing a resource. Therequest body provides the resource input in case of POST and PUT requests.

10. Data Management

LISA: Virtual TDM _ Automated capture and management of complex data models

HP: Simple request/response pair data only

11. Data Decentralization

LISA: Automated protection of private data while still retaining valid data formatHP: Not Available

12. Statefull/Stateless Transactions

LISA: Statefull and Stateless transactions that maintain context in non-sequential scenarios, including

external system jumps, human input, and wait-for-transactions.

HP: Statefull, sequential test supported only. Loses context in complex scenarios.

1. Common Error Handling framework

2. Common Delivery framework

3. Common Notification framework

4. Common Logging framework

Objective: To test framework which can be used to generate errors for failures, trigger notification

and deliver the notification via Email, Fax, SMS and can generate ticket for failure in internal system

for services which can be business or technical error,

Challenges:

1. No services exposed as web service

2. No commercial tool for testing

3. All configuration in database. To configure codes in more than 25 tables

4. Continuous database inserts and later validation

5. Validation of logs in wM server logs

Solution:

1. Understand the functionality, flow of the frameworks and Identified suitable approach,

2. Requested for wM packages to be exposed as web services

3. To use soapUI for web service validation

4. Manual database configuration

Flow of services:

1. Configure codes for Error Handling, Notification - which was for Email, FAX, SMS and ticket logging

and configure delivery channels like JMS & MQ2. Trigger error with error handling framework and confirm the error custom text in the response

8/10/2019 REST Uses the HTTP Protocol to Identify

2/2

which was configured earlier,

3. Go to the database and verify audit tables

4. Verify details is notification audit tables, whether the notification is triggered for the configured

types which were pre-defined and client defined.

5. For client defined codes another service was triggered which used to get the details from other

online banking system which use to maintain the detail of client preferred notification types.

6. Verify the delivery audit tables whether the message is available with pre-defined or client-

defined details.

7. Verify the details for client defined whether the correct email id, cell number as available which

are added from online banking system

8. Verify the message is posted in correct queue JMS/MQ

9. Verify in the logs the messages are successfully consumed by third parties who used to delivery

the notification to the end users or to internal first line support people/engineers

10. Verify in the internal ticketing system the ticket is generated for configured error code.

Result: The framework was successfully implemented in production on 13 - April -2013 and is beencurrently monitored. Till now no production issues and all the notification are generated successfully

for different error codes defined for different services,