blob: c1c3a7d556023dceab8ee3c792f3eae701ddef1a [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2005" />
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="task" />
<meta name="DC.Title" content="Validating WS-I Web service traffic compliance" />
<meta name="abstract" content="As well as setting the level of WS-I compliance during Web services creation, you can validate WS-I compliance of the SOAP traffic a Web service produces through the TCP/IP Monitor." />
<meta name="description" content="As well as setting the level of WS-I compliance during Web services creation, you can validate WS-I compliance of the SOAP traffic a Web service produces through the TCP/IP Monitor." />
<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.html" />
<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="twsival" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="../ibmdita.css" />
<title>Validating WS-I Web service traffic compliance</title>
</head>
<body id="twsival"><a name="twsival"><!-- --></a>
<h1 class="topictitle1">Validating WS-I Web service traffic compliance</h1>
<div><p>As well as setting the level of WS-I compliance during Web services
creation, you can validate WS-I compliance of the SOAP traffic a Web service
produces through the TCP/IP Monitor.</p>
<div class="p"> Prerequisites:  Before you can use the validation tool to ensure
that your Web service SOAP traffic is WS-I compliant, you must have completed
the following steps:<ul><li>Generate a Web service.</li>
<li> <a href="twsdlval.html">Validate the WSDL that is produced.</a> </li>
<li>Generate a Proxy and a sample application. </li>
<li> <a href="tmonitor.html">Set up the TCP/IP Monitor.</a> Ensure that
your Web service sample application traffic is directed through the TCP/IP
Monitor.</li>
</ul>
</div>
<div class="section"><p>To validate your Web service, complete the following steps:</p>
</div>
<ol><li><span>Invoke a method in your Web service sample application to generate
traffic through the TCP/IP Monitor.</span></li>
<li><span>To ensure that your Web service SOAP traffic is WS-I compliant,
you can generate a log file by clicking the <img src="../images/wsivalico.gif" alt="Validate icon" /> icon.</span></li>
<li><span>In the dialog box that opens, select a name for the log file and
specify where you want it to be stored.</span></li>
</ol>
<div class="section"> This log file will show whether or not messages sent to and from
your Web service are WS-I compliant, and list any non-compliant elements.
You can open the log file in an XML editor to examine its contents.</div>
</div>
<div>
<div class="linklist"><strong>Related Concepts</strong><br />
<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsiover.html">WS-I</a></div></div>
<div class="linklist"><strong>Related Tasks</strong><br />
<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/twsicomply.html">Setting the level of WS-I compliance</a></div></div>
</div>
</body>
</html>