Skip to content
Stephen Brady edited this page Apr 21, 2014 · 22 revisions

The WSDL

Over the following link you can access the wsdl https://<host>/ews/Services.wsdl The WSDL references 3 schemas: messages.xsd, types.xsd, xml.xsd

The original WSDL lacks the service definition, this was added manually and is used to generate the binding classes.
This is the added section:
<wsdl:service name="ExchangeService">
<wsdl:port name="ExchangeServicePort" binding="tns:ExchangeServiceBinding">
<soap:address location="https://host/ews/exchange.asmx"/>
</wsdl:port>
</wsdl:service>

You can find the WSDL in the project ews-api

##Strategies to connect over webservice to microsoft exchange server

  1. You can use the official ms api: http://archive.msdn.microsoft.com/ewsjavaapi
    This is implemented in the project ews-ms-api and described here ews-ms-api
  2. You can generate your own classes
    This is implemented in the project ews-api and described here ews-api

Security

Here you find two Authentication Scenarios Authentication

  1. Negotiated
  2. Basic

Monitoring

Cause the webservice is encrypted over ssl you need 2 tools to monitor the traffic:

  1. stunnel http://mirror.bit.nl/stunnel/
  2. tcpmon http://ws.apache.org/commons/tcpmon/download.cgi

You will connect over http to the tcpmon. The tcpmon forwards the traffic to the stunnel. The stunnel makes the https connection to the exchange server. Like this you can monitor the soap messages on the tcpmon.

stunnel

The config you use in the config file:
[https]
client = yes
accept = 127.0.0.1:8443
connect = <host>:443
TIMEOUTclose = 0

tcpmon

Listen on :8080 and forward to port 8443.

Examples

You can find examples under the soap-examples

Resources

Clone this wiki locally