This third party connector has two version of connector JEC and
EWSJ connector former is used to connected to Microsoft Exchage server 2003
(which is not suppport exchange web service) connection happen through WebDev ,
EWSJ uses EWS provided by the exchange.
We will explore more on EWSJ connector
1) To integrate with Java applcation with
Microsoft Exchange server 2007 SP3
2) Using EWS(Exchange web services)
provided by Microsoft
3) SSL enabled
4) Standard certificates (generated using a CA)
are not self-sighed, and will always work.
5) In some rare cases, self-signed (test)
certificates will not work.
This happens because there is a special mechanism that is part of JEC/EWSJ that kicks-in to enable SSL communication with test certificates, and it does not cover all possible cases
This happens because there is a special mechanism that is part of JEC/EWSJ that kicks-in to enable SSL communication with test certificates, and it does not cover all possible cases
6) EWSJ connector deployed as part of Application
Server.
7) EWSJ Connector will access the Microsoft
provided web service. (https://<exchagehost>/EWS/Exchange.asmx)
9) EWSJ is support the most secured
ways of communication with Exchange, NTLMv2, NTLM and Digest authentication
methods are supported, SSL is used by default.
Seperatly, all security patches need to be applied to Exchange.
10) EWSJ
Connector provides the API for the Exchange Web Services , So that we call the
API from the java applcation without knowledge of the web service.
11) it not open source
, JEC / EWSJ Enterprise
License - $999 USD
12 ) It has interface
for PowerShell also.
The alternative
solution would be using JavaAPI for EWS provided by Microsoft itself .
this can be
download http://archive.msdn.microsoft.com/ewsjavaapi/Release/ProjectReleases.aspx?ReleaseId=5754
Comments
Post a Comment