How to configure and start
the TCP/IP monitor
Configuring and starting the TCP/IP monitor is done through the
"Preferences" page.
Click on "Window" in the main menu bar and select
"Preferences".
In the "Preferences" page, select "TCP/IP Monitor"
from the list of preferences on the left.
This should give you the following page:
Note that if the checkbox is checked, the TCP/IP Monitor view will
automatically be shown when there is activity. If this is not selected,
the user will need to explicitly show the TCP/IP Monitor view.
Click the "New..." button to configure a monitor in
the "Create Monitor" dialog.
Enter the port that the monitor will be listening on in the
"Local port" entry.
Enter the host and port that the monitor will forward the messages to.
Click "OK" button.
The monitor has now been configured, the next step is to start it.
Select the newly created monitor in the "TCP/IP Monitors"
window.
Click "Start" button on the right. Notice that the monitor
icon (in the "TCP/IP Monitors" window) is "green"
when the monitor is running, and "red" when it is not.
See How to validate SOAP messages
using the TCP/IP monitor? to learn more about observing,
capturing and validating SOAP traffic using the TCP/IP monitor.
How to validate SOAP
messages using the TCP/IP monitor
To Show the TCP/IP monitor view
If the TCP/IP monitor is not configured to automatically
show the monitor view when there is activity, then we need to explicitly
show the monitor view.
Click on "Window" in the main menu bar and select
"Show View" and "Others" in the submenu.
In the "Show View" dialog, select "TCP/IP
Monitor" under "Basic".
Click "OK" button.
To observe, capture and validate SOAP traffic
SOAP traffic is captured as request/response pairs in the
listening port tree in the monitor view.
You can view the contents of of a request and corresponding
response by expanding the listening port tree and selecting a
request/response pair. Note you can view the data as it appears on
the wire, as a formatted xml fragment or as an image if
appropriate.
To validate the traffic against the WS-I Basic Profile, click
the "validation icon" 
on the top right hand corner in the TCP/IP monitor view. In the
"Specify the WS-I Message Log File Name" page, select
the parent folder where the message log will be stored and enter
the name of the message log file. Click "Next".
In the "Include WSDL File" page, you have an option
to validate the messages with or without the corresponding WSDL
document. Select "Include WSDL document for Web
service". Enter the location of the WSDL document or select
it within the workbench or from your local file system. Note, the
"Next" button is enabled if the specified WSDL document
is valid or a WSDL document is not included. Click
"Next".
On the next page, indicate the name, type, parent and namespace
of the WSDL element to be analyzed.
The WSDL element contains both a name
and type. The name
refers the name of the WSDL element that should be analyzed, and
the type refers to the type of WSDL element that should be
analyzed. Since the
element definitions in a WSDL document are referential, the
element that is specified indicates the point at which the WSDL
related analysis will begin.
For example, if the WSDL element
references a <wsdl:port> element, then the analyzer will
process the <wsdl:port>, the <wsdl:binding> referenced
by the <wsdl:port>, the <wsdl:portType> referenced by
the <wsdl:binding>, and the <wsdl:operation> and
<wsdl:message> elements referenced by the
<wsdl:portType>. If the WSDL element references a <wsdl:portType>
element, then the only elements that will be analyzed are the
<wsdl:portType> and the <wsdl;operation> and
<wsdl:message> elements that it references.
The following table lists the WSDL elements that can be analyzed
and the other WSDL elements that will be analyzed when that type
of element is specified.
|
|
WSDL Element
|
Other WSDL Elements Analyzed
|
|
1
|
port
|
binding,
portType, operation, message
|
|
2
|
binding
|
portType,
operation, message
|
|
3
|
portType
|
operation,
message
|
|
4
|
operation
|
message
|
|
5
|
message
|
[none]
|
Note by default, the WSDL
element references a <wsdl:port> element.
A WS-I Message log will be created and validated against the
WS-I Basic Profile. Any identified WS-I noncompliance, will be
displayed as errors or warnings in the "Problems" view.
See How to configure and
start the TCP/IP Monitor? to learn more about configuring
and running the monitor using the "Preferences" page.
top