WEB SERVICE TESTING

WEB SERVICE INTRO

WSDL

SOAP

PUTTY TERMINAL

RESTCLIENT PLUGIN

TESTING EXAMPLES

WHAT IS WEB SERVICE

bull Web means HTTP protocol and Services means request ndash response

bull Web services are web application components and it can be published found and used on the Web

bull Web services communicate using open protocols

bull Web services have no GUI

bull Web services are a simple interface using HTTP protocol

FROM WHERE ITrsquoS COME

bull Web services can be

bull 1048766developed by one company

bull 1048766used by another company and

bull 1048766hosted by a third company

bull 1048766Such involvement of several companies is a

business cases for independent testing of web

services

WHAT WE CAN DO WITH IT

bull Web services is a stateless protocol

bull 1048766we send a request

bull 1048766 we receive a response

WEB SERVICES HAVE TWO TYPES OF USES

bull Reusable application-components

bull There are things applications need very often So why make these over and over again

bull like currency conversion weather reports or even language translation as services

bull Connect existing software

bull Web services can help to solve the interoperability problem by giving different applications a way to link their data

bull With Web services you can exchange data between different applications and different platforms

WSDL (WEB SERVICES DESCRIPTION LANGUAGE)

WSDL STANDS FOR WEB SERVICES DESCRIPTION

LANGUAGE

WSDL IS A LANGUAGE FOR DESCRIBING WEB SERVICES

AND HOW TO ACCESS THEM

WSDL IS AN XML-BASED LANGUAGE FOR DESCRIBING

WEB SERVICES

WSDL IS ALSO USED TO LOCATE WEB SERVICES

THE WSDL DOCUMENT STRUCTURE

Element Description

lttypesgt A container for data type definitions used by the web service

ltmessagegt A typed definition of the data being communicated

ltportTypegt A set of operations supported by one or more endpoints

ltbindinggt A protocol and data format specification for a particular port

type

OPERATION TYPESTHE REQUEST-RESPONSE TYPE IS THE MOST COMMON OPERATION TYPE BUT WSDL DEFINES FOUR TYPES

Type Definition

One-way The operation can receive a message but will not return a

response

Request-response The operation can receive a request and will return a

response

Solicit-response The operation can send a request and will wait for a

response

Notification The operation can send a message but will not wait for a

response

A ONE-WAY OPERATION EXAMPLE

bull ltmessage name=newTermValuesgt

ltpart name=term type=xsstringgt

ltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgt

ltoperation name=setTermgt

ltinput name=newTerm message=newTermValuesgt

ltoperationgt

ltportType gt

WSDL REQUEST-RESPONSE EXAMPLE

ltmessage name=getTermRequestgtltpart name=term type=xsstringgt

ltmessagegt

ltmessage name=getTermResponsegtltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgtltoperation name=getTermgt

ltinput message=getTermRequestgtltoutput message=getTermResponsegt

ltoperationgtltportTypegt

WEB SERVICE TESTING

TO VERIFY THE WEB SERVICE EITHER USE OF BELOW

TECHNIQUE

SOAP

PUTTY TERMINAL

RESTCLIENT PLUG IN

SOAP(SIMPLE OBJECT ACCESS PROTOCOL)

bull SOAP is an XML based protocol for accessing Web

Services

bull SOAP is a communication protocol between applications

bull SOAP is a format for sending messages

bull SOAP communicates via Internet

bull SOAP is platform amp language independent

bull SOAP is simple and extensible

bull SOAP allows you to get around firewalls

SOAP BUILDING BLOCKS

bull A SOAP message is an ordinary XML document

containing the following elements

bull An Envelope element that identifies the XML document

as a SOAP message

bull A Header element that contains header information

bull A Body element that contains call and response

information

bull A Fault element containing errors and status information

SKELETON SOAP MESSAGE

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltsoapHeadergt

ltsoapBodygt

ltsoapFaultgtltsoapFaultgt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP ENVELOPE ELEMENT

bull The required SOAP Envelope element is the root element of a SOAP message This element defines the XML document as a SOAP message

bull Example

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

Message information goes here

ltsoapEnvelopegt

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

WHAT IS WEB SERVICE

bull Web means HTTP protocol and Services means request ndash response

bull Web services are web application components and it can be published found and used on the Web

bull Web services communicate using open protocols

bull Web services have no GUI

bull Web services are a simple interface using HTTP protocol

FROM WHERE ITrsquoS COME

bull Web services can be

bull 1048766developed by one company

bull 1048766used by another company and

bull 1048766hosted by a third company

bull 1048766Such involvement of several companies is a

business cases for independent testing of web

services

WHAT WE CAN DO WITH IT

bull Web services is a stateless protocol

bull 1048766we send a request

bull 1048766 we receive a response

WEB SERVICES HAVE TWO TYPES OF USES

bull Reusable application-components

bull There are things applications need very often So why make these over and over again

bull like currency conversion weather reports or even language translation as services

bull Connect existing software

bull Web services can help to solve the interoperability problem by giving different applications a way to link their data

bull With Web services you can exchange data between different applications and different platforms

WSDL (WEB SERVICES DESCRIPTION LANGUAGE)

WSDL STANDS FOR WEB SERVICES DESCRIPTION

LANGUAGE

WSDL IS A LANGUAGE FOR DESCRIBING WEB SERVICES

AND HOW TO ACCESS THEM

WSDL IS AN XML-BASED LANGUAGE FOR DESCRIBING

WEB SERVICES

WSDL IS ALSO USED TO LOCATE WEB SERVICES

THE WSDL DOCUMENT STRUCTURE

Element Description

lttypesgt A container for data type definitions used by the web service

ltmessagegt A typed definition of the data being communicated

ltportTypegt A set of operations supported by one or more endpoints

ltbindinggt A protocol and data format specification for a particular port

type

OPERATION TYPESTHE REQUEST-RESPONSE TYPE IS THE MOST COMMON OPERATION TYPE BUT WSDL DEFINES FOUR TYPES

Type Definition

One-way The operation can receive a message but will not return a

response

Request-response The operation can receive a request and will return a

response

Solicit-response The operation can send a request and will wait for a

response

Notification The operation can send a message but will not wait for a

response

A ONE-WAY OPERATION EXAMPLE

bull ltmessage name=newTermValuesgt

ltpart name=term type=xsstringgt

ltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgt

ltoperation name=setTermgt

ltinput name=newTerm message=newTermValuesgt

ltoperationgt

ltportType gt

WSDL REQUEST-RESPONSE EXAMPLE

ltmessage name=getTermRequestgtltpart name=term type=xsstringgt

ltmessagegt

ltmessage name=getTermResponsegtltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgtltoperation name=getTermgt

ltinput message=getTermRequestgtltoutput message=getTermResponsegt

ltoperationgtltportTypegt

WEB SERVICE TESTING

TO VERIFY THE WEB SERVICE EITHER USE OF BELOW

TECHNIQUE

SOAP

PUTTY TERMINAL

RESTCLIENT PLUG IN

SOAP(SIMPLE OBJECT ACCESS PROTOCOL)

bull SOAP is an XML based protocol for accessing Web

Services

bull SOAP is a communication protocol between applications

bull SOAP is a format for sending messages

bull SOAP communicates via Internet

bull SOAP is platform amp language independent

bull SOAP is simple and extensible

bull SOAP allows you to get around firewalls

SOAP BUILDING BLOCKS

bull A SOAP message is an ordinary XML document

containing the following elements

bull An Envelope element that identifies the XML document

as a SOAP message

bull A Header element that contains header information

bull A Body element that contains call and response

information

bull A Fault element containing errors and status information

SKELETON SOAP MESSAGE

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltsoapHeadergt

ltsoapBodygt

ltsoapFaultgtltsoapFaultgt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP ENVELOPE ELEMENT

bull The required SOAP Envelope element is the root element of a SOAP message This element defines the XML document as a SOAP message

bull Example

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

Message information goes here

ltsoapEnvelopegt

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

FROM WHERE ITrsquoS COME

bull Web services can be

bull 1048766developed by one company

bull 1048766used by another company and

bull 1048766hosted by a third company

bull 1048766Such involvement of several companies is a

business cases for independent testing of web

services

WHAT WE CAN DO WITH IT

bull Web services is a stateless protocol

bull 1048766we send a request

bull 1048766 we receive a response

WEB SERVICES HAVE TWO TYPES OF USES

bull Reusable application-components

bull There are things applications need very often So why make these over and over again

bull like currency conversion weather reports or even language translation as services

bull Connect existing software

bull Web services can help to solve the interoperability problem by giving different applications a way to link their data

bull With Web services you can exchange data between different applications and different platforms

WSDL (WEB SERVICES DESCRIPTION LANGUAGE)

WSDL STANDS FOR WEB SERVICES DESCRIPTION

LANGUAGE

WSDL IS A LANGUAGE FOR DESCRIBING WEB SERVICES

AND HOW TO ACCESS THEM

WSDL IS AN XML-BASED LANGUAGE FOR DESCRIBING

WEB SERVICES

WSDL IS ALSO USED TO LOCATE WEB SERVICES

THE WSDL DOCUMENT STRUCTURE

Element Description

lttypesgt A container for data type definitions used by the web service

ltmessagegt A typed definition of the data being communicated

ltportTypegt A set of operations supported by one or more endpoints

ltbindinggt A protocol and data format specification for a particular port

type

OPERATION TYPESTHE REQUEST-RESPONSE TYPE IS THE MOST COMMON OPERATION TYPE BUT WSDL DEFINES FOUR TYPES

Type Definition

One-way The operation can receive a message but will not return a

response

Request-response The operation can receive a request and will return a

response

Solicit-response The operation can send a request and will wait for a

response

Notification The operation can send a message but will not wait for a

response

A ONE-WAY OPERATION EXAMPLE

bull ltmessage name=newTermValuesgt

ltpart name=term type=xsstringgt

ltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgt

ltoperation name=setTermgt

ltinput name=newTerm message=newTermValuesgt

ltoperationgt

ltportType gt

WSDL REQUEST-RESPONSE EXAMPLE

ltmessage name=getTermRequestgtltpart name=term type=xsstringgt

ltmessagegt

ltmessage name=getTermResponsegtltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgtltoperation name=getTermgt

ltinput message=getTermRequestgtltoutput message=getTermResponsegt

ltoperationgtltportTypegt

WEB SERVICE TESTING

TO VERIFY THE WEB SERVICE EITHER USE OF BELOW

TECHNIQUE

SOAP

PUTTY TERMINAL

RESTCLIENT PLUG IN

SOAP(SIMPLE OBJECT ACCESS PROTOCOL)

bull SOAP is an XML based protocol for accessing Web

Services

bull SOAP is a communication protocol between applications

bull SOAP is a format for sending messages

bull SOAP communicates via Internet

bull SOAP is platform amp language independent

bull SOAP is simple and extensible

bull SOAP allows you to get around firewalls

SOAP BUILDING BLOCKS

bull A SOAP message is an ordinary XML document

containing the following elements

bull An Envelope element that identifies the XML document

as a SOAP message

bull A Header element that contains header information

bull A Body element that contains call and response

information

bull A Fault element containing errors and status information

SKELETON SOAP MESSAGE

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltsoapHeadergt

ltsoapBodygt

ltsoapFaultgtltsoapFaultgt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP ENVELOPE ELEMENT

bull The required SOAP Envelope element is the root element of a SOAP message This element defines the XML document as a SOAP message

bull Example

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

Message information goes here

ltsoapEnvelopegt

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

WHAT WE CAN DO WITH IT

bull Web services is a stateless protocol

bull 1048766we send a request

bull 1048766 we receive a response

WEB SERVICES HAVE TWO TYPES OF USES

bull Reusable application-components

bull There are things applications need very often So why make these over and over again

bull like currency conversion weather reports or even language translation as services

bull Connect existing software

bull Web services can help to solve the interoperability problem by giving different applications a way to link their data

bull With Web services you can exchange data between different applications and different platforms

WSDL (WEB SERVICES DESCRIPTION LANGUAGE)

WSDL STANDS FOR WEB SERVICES DESCRIPTION

LANGUAGE

WSDL IS A LANGUAGE FOR DESCRIBING WEB SERVICES

AND HOW TO ACCESS THEM

WSDL IS AN XML-BASED LANGUAGE FOR DESCRIBING

WEB SERVICES

WSDL IS ALSO USED TO LOCATE WEB SERVICES

THE WSDL DOCUMENT STRUCTURE

Element Description

lttypesgt A container for data type definitions used by the web service

ltmessagegt A typed definition of the data being communicated

ltportTypegt A set of operations supported by one or more endpoints

ltbindinggt A protocol and data format specification for a particular port

type

OPERATION TYPESTHE REQUEST-RESPONSE TYPE IS THE MOST COMMON OPERATION TYPE BUT WSDL DEFINES FOUR TYPES

Type Definition

One-way The operation can receive a message but will not return a

response

Request-response The operation can receive a request and will return a

response

Solicit-response The operation can send a request and will wait for a

response

Notification The operation can send a message but will not wait for a

response

A ONE-WAY OPERATION EXAMPLE

bull ltmessage name=newTermValuesgt

ltpart name=term type=xsstringgt

ltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgt

ltoperation name=setTermgt

ltinput name=newTerm message=newTermValuesgt

ltoperationgt

ltportType gt

WSDL REQUEST-RESPONSE EXAMPLE

ltmessage name=getTermRequestgtltpart name=term type=xsstringgt

ltmessagegt

ltmessage name=getTermResponsegtltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgtltoperation name=getTermgt

ltinput message=getTermRequestgtltoutput message=getTermResponsegt

ltoperationgtltportTypegt

WEB SERVICE TESTING

TO VERIFY THE WEB SERVICE EITHER USE OF BELOW

TECHNIQUE

SOAP

PUTTY TERMINAL

RESTCLIENT PLUG IN

SOAP(SIMPLE OBJECT ACCESS PROTOCOL)

bull SOAP is an XML based protocol for accessing Web

Services

bull SOAP is a communication protocol between applications

bull SOAP is a format for sending messages

bull SOAP communicates via Internet

bull SOAP is platform amp language independent

bull SOAP is simple and extensible

bull SOAP allows you to get around firewalls

SOAP BUILDING BLOCKS

bull A SOAP message is an ordinary XML document

containing the following elements

bull An Envelope element that identifies the XML document

as a SOAP message

bull A Header element that contains header information

bull A Body element that contains call and response

information

bull A Fault element containing errors and status information

SKELETON SOAP MESSAGE

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltsoapHeadergt

ltsoapBodygt

ltsoapFaultgtltsoapFaultgt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP ENVELOPE ELEMENT

bull The required SOAP Envelope element is the root element of a SOAP message This element defines the XML document as a SOAP message

bull Example

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

Message information goes here

ltsoapEnvelopegt

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

WEB SERVICES HAVE TWO TYPES OF USES

bull Reusable application-components

bull There are things applications need very often So why make these over and over again

bull like currency conversion weather reports or even language translation as services

bull Connect existing software

bull Web services can help to solve the interoperability problem by giving different applications a way to link their data

bull With Web services you can exchange data between different applications and different platforms

WSDL (WEB SERVICES DESCRIPTION LANGUAGE)

WSDL STANDS FOR WEB SERVICES DESCRIPTION

LANGUAGE

WSDL IS A LANGUAGE FOR DESCRIBING WEB SERVICES

AND HOW TO ACCESS THEM

WSDL IS AN XML-BASED LANGUAGE FOR DESCRIBING

WEB SERVICES

WSDL IS ALSO USED TO LOCATE WEB SERVICES

THE WSDL DOCUMENT STRUCTURE

Element Description

lttypesgt A container for data type definitions used by the web service

ltmessagegt A typed definition of the data being communicated

ltportTypegt A set of operations supported by one or more endpoints

ltbindinggt A protocol and data format specification for a particular port

type

OPERATION TYPESTHE REQUEST-RESPONSE TYPE IS THE MOST COMMON OPERATION TYPE BUT WSDL DEFINES FOUR TYPES

Type Definition

One-way The operation can receive a message but will not return a

response

Request-response The operation can receive a request and will return a

response

Solicit-response The operation can send a request and will wait for a

response

Notification The operation can send a message but will not wait for a

response

A ONE-WAY OPERATION EXAMPLE

bull ltmessage name=newTermValuesgt

ltpart name=term type=xsstringgt

ltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgt

ltoperation name=setTermgt

ltinput name=newTerm message=newTermValuesgt

ltoperationgt

ltportType gt

WSDL REQUEST-RESPONSE EXAMPLE

ltmessage name=getTermRequestgtltpart name=term type=xsstringgt

ltmessagegt

ltmessage name=getTermResponsegtltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgtltoperation name=getTermgt

ltinput message=getTermRequestgtltoutput message=getTermResponsegt

ltoperationgtltportTypegt

WEB SERVICE TESTING

TO VERIFY THE WEB SERVICE EITHER USE OF BELOW

TECHNIQUE

SOAP

PUTTY TERMINAL

RESTCLIENT PLUG IN

SOAP(SIMPLE OBJECT ACCESS PROTOCOL)

bull SOAP is an XML based protocol for accessing Web

Services

bull SOAP is a communication protocol between applications

bull SOAP is a format for sending messages

bull SOAP communicates via Internet

bull SOAP is platform amp language independent

bull SOAP is simple and extensible

bull SOAP allows you to get around firewalls

SOAP BUILDING BLOCKS

bull A SOAP message is an ordinary XML document

containing the following elements

bull An Envelope element that identifies the XML document

as a SOAP message

bull A Header element that contains header information

bull A Body element that contains call and response

information

bull A Fault element containing errors and status information

SKELETON SOAP MESSAGE

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltsoapHeadergt

ltsoapBodygt

ltsoapFaultgtltsoapFaultgt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP ENVELOPE ELEMENT

bull The required SOAP Envelope element is the root element of a SOAP message This element defines the XML document as a SOAP message

bull Example

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

Message information goes here

ltsoapEnvelopegt

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

WSDL (WEB SERVICES DESCRIPTION LANGUAGE)

WSDL STANDS FOR WEB SERVICES DESCRIPTION

LANGUAGE

WSDL IS A LANGUAGE FOR DESCRIBING WEB SERVICES

AND HOW TO ACCESS THEM

WSDL IS AN XML-BASED LANGUAGE FOR DESCRIBING

WEB SERVICES

WSDL IS ALSO USED TO LOCATE WEB SERVICES

THE WSDL DOCUMENT STRUCTURE

Element Description

lttypesgt A container for data type definitions used by the web service

ltmessagegt A typed definition of the data being communicated

ltportTypegt A set of operations supported by one or more endpoints

ltbindinggt A protocol and data format specification for a particular port

type

OPERATION TYPESTHE REQUEST-RESPONSE TYPE IS THE MOST COMMON OPERATION TYPE BUT WSDL DEFINES FOUR TYPES

Type Definition

One-way The operation can receive a message but will not return a

response

Request-response The operation can receive a request and will return a

response

Solicit-response The operation can send a request and will wait for a

response

Notification The operation can send a message but will not wait for a

response

A ONE-WAY OPERATION EXAMPLE

bull ltmessage name=newTermValuesgt

ltpart name=term type=xsstringgt

ltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgt

ltoperation name=setTermgt

ltinput name=newTerm message=newTermValuesgt

ltoperationgt

ltportType gt

WSDL REQUEST-RESPONSE EXAMPLE

ltmessage name=getTermRequestgtltpart name=term type=xsstringgt

ltmessagegt

ltmessage name=getTermResponsegtltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgtltoperation name=getTermgt

ltinput message=getTermRequestgtltoutput message=getTermResponsegt

ltoperationgtltportTypegt

WEB SERVICE TESTING

TO VERIFY THE WEB SERVICE EITHER USE OF BELOW

TECHNIQUE

SOAP

PUTTY TERMINAL

RESTCLIENT PLUG IN

SOAP(SIMPLE OBJECT ACCESS PROTOCOL)

bull SOAP is an XML based protocol for accessing Web

Services

bull SOAP is a communication protocol between applications

bull SOAP is a format for sending messages

bull SOAP communicates via Internet

bull SOAP is platform amp language independent

bull SOAP is simple and extensible

bull SOAP allows you to get around firewalls

SOAP BUILDING BLOCKS

bull A SOAP message is an ordinary XML document

containing the following elements

bull An Envelope element that identifies the XML document

as a SOAP message

bull A Header element that contains header information

bull A Body element that contains call and response

information

bull A Fault element containing errors and status information

SKELETON SOAP MESSAGE

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltsoapHeadergt

ltsoapBodygt

ltsoapFaultgtltsoapFaultgt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP ENVELOPE ELEMENT

bull The required SOAP Envelope element is the root element of a SOAP message This element defines the XML document as a SOAP message

bull Example

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

Message information goes here

ltsoapEnvelopegt

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

THE WSDL DOCUMENT STRUCTURE

Element Description

lttypesgt A container for data type definitions used by the web service

ltmessagegt A typed definition of the data being communicated

ltportTypegt A set of operations supported by one or more endpoints

ltbindinggt A protocol and data format specification for a particular port

type

OPERATION TYPESTHE REQUEST-RESPONSE TYPE IS THE MOST COMMON OPERATION TYPE BUT WSDL DEFINES FOUR TYPES

Type Definition

One-way The operation can receive a message but will not return a

response

Request-response The operation can receive a request and will return a

response

Solicit-response The operation can send a request and will wait for a

response

Notification The operation can send a message but will not wait for a

response

A ONE-WAY OPERATION EXAMPLE

bull ltmessage name=newTermValuesgt

ltpart name=term type=xsstringgt

ltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgt

ltoperation name=setTermgt

ltinput name=newTerm message=newTermValuesgt

ltoperationgt

ltportType gt

WSDL REQUEST-RESPONSE EXAMPLE

ltmessage name=getTermRequestgtltpart name=term type=xsstringgt

ltmessagegt

ltmessage name=getTermResponsegtltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgtltoperation name=getTermgt

ltinput message=getTermRequestgtltoutput message=getTermResponsegt

ltoperationgtltportTypegt

WEB SERVICE TESTING

TO VERIFY THE WEB SERVICE EITHER USE OF BELOW

TECHNIQUE

SOAP

PUTTY TERMINAL

RESTCLIENT PLUG IN

SOAP(SIMPLE OBJECT ACCESS PROTOCOL)

bull SOAP is an XML based protocol for accessing Web

Services

bull SOAP is a communication protocol between applications

bull SOAP is a format for sending messages

bull SOAP communicates via Internet

bull SOAP is platform amp language independent

bull SOAP is simple and extensible

bull SOAP allows you to get around firewalls

SOAP BUILDING BLOCKS

bull A SOAP message is an ordinary XML document

containing the following elements

bull An Envelope element that identifies the XML document

as a SOAP message

bull A Header element that contains header information

bull A Body element that contains call and response

information

bull A Fault element containing errors and status information

SKELETON SOAP MESSAGE

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltsoapHeadergt

ltsoapBodygt

ltsoapFaultgtltsoapFaultgt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP ENVELOPE ELEMENT

bull The required SOAP Envelope element is the root element of a SOAP message This element defines the XML document as a SOAP message

bull Example

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

Message information goes here

ltsoapEnvelopegt

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

OPERATION TYPESTHE REQUEST-RESPONSE TYPE IS THE MOST COMMON OPERATION TYPE BUT WSDL DEFINES FOUR TYPES

Type Definition

One-way The operation can receive a message but will not return a

response

Request-response The operation can receive a request and will return a

response

Solicit-response The operation can send a request and will wait for a

response

Notification The operation can send a message but will not wait for a

response

A ONE-WAY OPERATION EXAMPLE

bull ltmessage name=newTermValuesgt

ltpart name=term type=xsstringgt

ltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgt

ltoperation name=setTermgt

ltinput name=newTerm message=newTermValuesgt

ltoperationgt

ltportType gt

WSDL REQUEST-RESPONSE EXAMPLE

ltmessage name=getTermRequestgtltpart name=term type=xsstringgt

ltmessagegt

ltmessage name=getTermResponsegtltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgtltoperation name=getTermgt

ltinput message=getTermRequestgtltoutput message=getTermResponsegt

ltoperationgtltportTypegt

WEB SERVICE TESTING

TO VERIFY THE WEB SERVICE EITHER USE OF BELOW

TECHNIQUE

SOAP

PUTTY TERMINAL

RESTCLIENT PLUG IN

SOAP(SIMPLE OBJECT ACCESS PROTOCOL)

bull SOAP is an XML based protocol for accessing Web

Services

bull SOAP is a communication protocol between applications

bull SOAP is a format for sending messages

bull SOAP communicates via Internet

bull SOAP is platform amp language independent

bull SOAP is simple and extensible

bull SOAP allows you to get around firewalls

SOAP BUILDING BLOCKS

bull A SOAP message is an ordinary XML document

containing the following elements

bull An Envelope element that identifies the XML document

as a SOAP message

bull A Header element that contains header information

bull A Body element that contains call and response

information

bull A Fault element containing errors and status information

SKELETON SOAP MESSAGE

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltsoapHeadergt

ltsoapBodygt

ltsoapFaultgtltsoapFaultgt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP ENVELOPE ELEMENT

bull The required SOAP Envelope element is the root element of a SOAP message This element defines the XML document as a SOAP message

bull Example

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

Message information goes here

ltsoapEnvelopegt

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

A ONE-WAY OPERATION EXAMPLE

bull ltmessage name=newTermValuesgt

ltpart name=term type=xsstringgt

ltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgt

ltoperation name=setTermgt

ltinput name=newTerm message=newTermValuesgt

ltoperationgt

ltportType gt

WSDL REQUEST-RESPONSE EXAMPLE

ltmessage name=getTermRequestgtltpart name=term type=xsstringgt

ltmessagegt

ltmessage name=getTermResponsegtltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgtltoperation name=getTermgt

ltinput message=getTermRequestgtltoutput message=getTermResponsegt

ltoperationgtltportTypegt

WEB SERVICE TESTING

TO VERIFY THE WEB SERVICE EITHER USE OF BELOW

TECHNIQUE

SOAP

PUTTY TERMINAL

RESTCLIENT PLUG IN

SOAP(SIMPLE OBJECT ACCESS PROTOCOL)

bull SOAP is an XML based protocol for accessing Web

Services

bull SOAP is a communication protocol between applications

bull SOAP is a format for sending messages

bull SOAP communicates via Internet

bull SOAP is platform amp language independent

bull SOAP is simple and extensible

bull SOAP allows you to get around firewalls

SOAP BUILDING BLOCKS

bull A SOAP message is an ordinary XML document

containing the following elements

bull An Envelope element that identifies the XML document

as a SOAP message

bull A Header element that contains header information

bull A Body element that contains call and response

information

bull A Fault element containing errors and status information

SKELETON SOAP MESSAGE

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltsoapHeadergt

ltsoapBodygt

ltsoapFaultgtltsoapFaultgt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP ENVELOPE ELEMENT

bull The required SOAP Envelope element is the root element of a SOAP message This element defines the XML document as a SOAP message

bull Example

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

Message information goes here

ltsoapEnvelopegt

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

WSDL REQUEST-RESPONSE EXAMPLE

ltmessage name=getTermRequestgtltpart name=term type=xsstringgt

ltmessagegt

ltmessage name=getTermResponsegtltpart name=value type=xsstringgt

ltmessagegt

ltportType name=glossaryTermsgtltoperation name=getTermgt

ltinput message=getTermRequestgtltoutput message=getTermResponsegt

ltoperationgtltportTypegt

WEB SERVICE TESTING

TO VERIFY THE WEB SERVICE EITHER USE OF BELOW

TECHNIQUE

SOAP

PUTTY TERMINAL

RESTCLIENT PLUG IN

SOAP(SIMPLE OBJECT ACCESS PROTOCOL)

bull SOAP is an XML based protocol for accessing Web

Services

bull SOAP is a communication protocol between applications

bull SOAP is a format for sending messages

bull SOAP communicates via Internet

bull SOAP is platform amp language independent

bull SOAP is simple and extensible

bull SOAP allows you to get around firewalls

SOAP BUILDING BLOCKS

bull A SOAP message is an ordinary XML document

containing the following elements

bull An Envelope element that identifies the XML document

as a SOAP message

bull A Header element that contains header information

bull A Body element that contains call and response

information

bull A Fault element containing errors and status information

SKELETON SOAP MESSAGE

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltsoapHeadergt

ltsoapBodygt

ltsoapFaultgtltsoapFaultgt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP ENVELOPE ELEMENT

bull The required SOAP Envelope element is the root element of a SOAP message This element defines the XML document as a SOAP message

bull Example

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

Message information goes here

ltsoapEnvelopegt

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

WEB SERVICE TESTING

TO VERIFY THE WEB SERVICE EITHER USE OF BELOW

TECHNIQUE

SOAP

PUTTY TERMINAL

RESTCLIENT PLUG IN

SOAP(SIMPLE OBJECT ACCESS PROTOCOL)

bull SOAP is an XML based protocol for accessing Web

Services

bull SOAP is a communication protocol between applications

bull SOAP is a format for sending messages

bull SOAP communicates via Internet

bull SOAP is platform amp language independent

bull SOAP is simple and extensible

bull SOAP allows you to get around firewalls

SOAP BUILDING BLOCKS

bull A SOAP message is an ordinary XML document

containing the following elements

bull An Envelope element that identifies the XML document

as a SOAP message

bull A Header element that contains header information

bull A Body element that contains call and response

information

bull A Fault element containing errors and status information

SKELETON SOAP MESSAGE

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltsoapHeadergt

ltsoapBodygt

ltsoapFaultgtltsoapFaultgt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP ENVELOPE ELEMENT

bull The required SOAP Envelope element is the root element of a SOAP message This element defines the XML document as a SOAP message

bull Example

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

Message information goes here

ltsoapEnvelopegt

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

SOAP(SIMPLE OBJECT ACCESS PROTOCOL)

bull SOAP is an XML based protocol for accessing Web

Services

bull SOAP is a communication protocol between applications

bull SOAP is a format for sending messages

bull SOAP communicates via Internet

bull SOAP is platform amp language independent

bull SOAP is simple and extensible

bull SOAP allows you to get around firewalls

SOAP BUILDING BLOCKS

bull A SOAP message is an ordinary XML document

containing the following elements

bull An Envelope element that identifies the XML document

as a SOAP message

bull A Header element that contains header information

bull A Body element that contains call and response

information

bull A Fault element containing errors and status information

SKELETON SOAP MESSAGE

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltsoapHeadergt

ltsoapBodygt

ltsoapFaultgtltsoapFaultgt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP ENVELOPE ELEMENT

bull The required SOAP Envelope element is the root element of a SOAP message This element defines the XML document as a SOAP message

bull Example

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

Message information goes here

ltsoapEnvelopegt

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

SOAP BUILDING BLOCKS

bull A SOAP message is an ordinary XML document

containing the following elements

bull An Envelope element that identifies the XML document

as a SOAP message

bull A Header element that contains header information

bull A Body element that contains call and response

information

bull A Fault element containing errors and status information

SKELETON SOAP MESSAGE

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltsoapHeadergt

ltsoapBodygt

ltsoapFaultgtltsoapFaultgt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP ENVELOPE ELEMENT

bull The required SOAP Envelope element is the root element of a SOAP message This element defines the XML document as a SOAP message

bull Example

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

Message information goes here

ltsoapEnvelopegt

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

SKELETON SOAP MESSAGE

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltsoapHeadergt

ltsoapBodygt

ltsoapFaultgtltsoapFaultgt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP ENVELOPE ELEMENT

bull The required SOAP Envelope element is the root element of a SOAP message This element defines the XML document as a SOAP message

bull Example

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

Message information goes here

ltsoapEnvelopegt

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

THE SOAP ENVELOPE ELEMENT

bull The required SOAP Envelope element is the root element of a SOAP message This element defines the XML document as a SOAP message

bull Example

ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

Message information goes here

ltsoapEnvelopegt

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

THE SOAP HEADER ELEMENT

bull The optional SOAP Header element contains application-specific information (like authentication payment etc) about the SOAP message

bull If the Header element is present it must be the first child element of the Envelope element

bull Note All immediate child elements of the Header element must be namespace-qualified

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapHeadergtltmTrans xmlnsm=httpwwwXYZcomtransactionsoapmustUnderstand=1gt234ltmTransgt

ltsoapHeadergtltsoapEnvelopegt

bull The example above contains a header with a Trans element a mustUnderstand attribute with a value of 1 and a value of 234

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

THE SOAP BODY ELEMENT I

bull The required SOAP Body element contains the actual SOAP message intended for the ultimate endpoint of the message Immediate child elements of the SOAP Body element may be namespace-qualified

bull Example

bull ltxml version=10gtltsoapEnvelopexmlnssoap=httpwwwXYZcom200112soap-envelopesoapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygtltmGetPrice xmlnsm=httpwwwxyzcompricesgtltmItemgtApplesltmItemgt

ltmGetPricegtltsoapBodygt

ltsoapEnvelopegt

bull The example above requests the price of apples Note that the mGetPrice and the Item elements above are application-specific elements They are not a part of the SOAP namespace

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

THE SOAP BODY ELEMENT II

bull A SOAP response could look something like this

bull ltxml version=10gt

ltsoapEnvelope

xmlnssoap=httpwwwXYZcom200112soap-envelope

soapencodingStyle=httpwwwXYZcom200112soap-encodinggt

ltsoapBodygt

ltmGetPriceResponse xmlnsm=httpwwww3schoolscompricesgt

ltmPricegt190ltmPricegt

ltmGetPriceResponsegt

ltsoapBodygt

ltsoapEnvelopegt

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

THE SOAP FAULT ELEMENT

bull The optional SOAP Fault element is used to indicate error messages If a Fault

element is present it must appear as a child element of the Body element A

Fault element can only appear once in a SOAP message

bull The SOAP Fault element has the following sub elements

Sub Element Description

ltfaultcodegt A code for identifying the fault

ltfaultstringgt A human readable explanation of the fault

ltfaultactorgt Information about who caused the fault to happen

ltdetailgt Holds application specific error information related to the Body

element

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

THE HTTP PROTOCOL

bull HTTP communicates over TCPIP An HTTP client connects to an HTTP

server using TCP After establishing a connection the client can send

an HTTP request message to the server

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

THE HTTP PROTOCOL

bull The server then processes the request and sends an HTTP

response back to the client The response contains a status

code that indicates the status of the request

bull In the example below the server returned a status code of

200 This is the standard success code for HTTP

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

THE HTTP PROTOCOL

bull If the server could not decode the request it could have

returned something like this

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

A SOAP REQUEST EXAMPLE

bull In the example below a GetStockPrice request is sent to a server The request has

a StockName parameter and a Price parameter that will be returned in the

response The namespace for the function is defined in

httpwwwexampleorgstock

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

A SOAP RESPONSE EXAMPLE

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

PUTTY TERMINAL

OPEN APPLICATION

ADD HOST ENTRY

LOGIN SERVER

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

EXECUTE THE LINUXUNIXCOMMAND

Ex to access a error log file

tail ndashf errorlog

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

RESTCLIENT PLUG-IN

INSTALL PLUG-IN

OPEN RESTCLIENT

IMPORT WEBSERVICE FILE

SELECT METHOD PUT URL AND CLICK ON

SEND BUTTON

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

TESTING EXAMPLES

WEB SERVICE CONTENT TESTING

WEB SERVICE ERROR LOG TESTING

INTERACTING WEB SERVICE FUNCTIONAL TESTING

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

WEBSERVICE CONTENT TESTING EX

bull Scenarios Wrong Tracking code is being added to new site

bookings when billing country Sweden

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

WEBSERVICE ERROR LOG TESTING EXI

bull Scenarios Verify invalid url is redirect to 404 page and CQ log does not throw

any error or exception

bull Actual result 20082013 175944441 ERROR [10199571 [1377017984435] GET error500html HTTP11] orgapacheslingservletsresolverinternalSlingServletResolver Original error null

bullExpected result in CQ log after hit on invalid URL 10102013 151027301 INFO [1722312881 [1381414227295] GET abchtml HTTP11] orgapacheslingengineimplSlingRequestProcessorImplservice Resource contentvaaabchtml not found

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

WEBSERVICE ERROR LOG TESTING EXII

bull Scenarios In Find address functionality Web service thrown error

when the response contains symbol as ldquoamprdquo (ampersand)

Verify Find address functionality working fine for specific country

Verify in Putty terminal Error does not occurring while performing search on find address

bull Before fixed the issue result is20082013 175049450 ERROR [10201571 [1377017449220] GET etcdesignsvaajsonlookupaddressjson HTTP11] comlbivaalookupaddressWesalAddressService Error calling address lookup javalangIllegalArgumentException could not unmarshall XML ltAddressLookup_RS xmlns=httpschemasvirgin-atlanticcomCustomerServiceAddressLookupServicesAddressLookUp2010gt

THANKS

THANKS