Exchange Integration with MSX-A on a Windows 2003 Server

Question

Hi
We try to integrate Microsoft Exchange (Version 2003 SP1) into SAP Enterprise Portal 6.0 SR1. The MSX-A components are installed on the OWA System, a different Windows 2003 System with Outlook XP (SP3) on it.
The error displayed in the Calendar iView on the Portal:
"An internal error occurred while generating the XML from the MSX-A component"
From the "SAP EP Test Exchange Transport Setup" Tool an error occures on the "Data Retrieval" Test:
"An error occurred retrieving the data."
and in detail:
MAPI_E_LOGON_FAILED(80040111)
MS KBase http://support.microsoft.com/kb/181739/en-us didn't help. To resolution 3: Policy "Log on Locally" on a Windows 2003 doesn't exist anymore (?). "Deny Log on Locally" isn't given to relevant groups.
Thanks and best regards
Nicolaj

Answer 1

hi All
i am illustrating the process of integration the central notes to be referred and constraints .hope this definitely helps you please do not forget to give full points for this effort
with regards
subrato kundu
<b>Process</b>
Microsoft outlook  Integration With SAP Enterprise Portal 6.0
(Process description)
These documents describe the entire process of integrating Exchange server with enterprise portal server to leverage the usage of lotus notes within the portal framework.
Step1: Create a System
o     Choose System Administration&#61664;System configuration&#61664;System Landscape&#61664;Portal Content&#61664;Content Provided by SAP. Right click on collaboration and then choose New From Par&#61664;System.
o     Select com.sap.netweaver.col.app.gw and choose next.
o     Select a server (Microsoft Exchange server) and then choose next.
o     Enter the System Name and ID (for ex Exchange) and choose next and then finish.
o     Enter System Aliases by choosing system Alias from the display drown list.
o     Enter the system Alias in the alias field and choose add and then save.
Step II: Create E-Mail Transport
&#61607;     The email transport defines the SMTP server and other configuration required for sending e-mails. To configure an e-mail transport choose
&#61607;     System Administration&#61664;System Configuration&#61664;Knowledge Management&#61664;Collaboration&#61664;GroupWare Transports&#61664;Mail Transport
&#61607;     SMTP Sever: The address of the SMTPServer for sending e-mails
&#61607;     Sent Messages: You specify the folder on the server where the sent e-mail is to be   store: -Sent Items on Microsoft Exchange Server.
&#61607;     System Alias name: Alias that was defined for the groupware server in system configuration.
Step III: Check E-Mailing Service
This is a global service that is required for sending e-mails and which can be   located by choosing System Administration&#61664;System configuration&#61664;Knowledge Management&#61664;Content Management&#61664;Global services&#61664;Mailing Service. This service needs to be active and an email transport must already have been created.
Microsoft Exchange Transports
The overall transport consists of two parts: MSX-J on the portal server and the MSX-A on the Exchange Server or a machine near to the Exchange Server.
MSX-J is the java part that runs on the portal server is deployed automatically on the portal server during installation, and implements the groupware API.It uses the Groupware APIs and repository development kit.
MSX-A is the active server page and sap exchange connector.dll running on a n iis server with Microsoft Collaboration data objects (CDO) and in the same domain as the exchange server or in a trusting domain .The ASP and DLL are Collectively CALLED MSX-A and is installed as part of the Outlook Installation. This needs to be installed on every IIS SERVER dedicated to the MS Exchange Server
    The Process flow is
1.TheMSX_J transport makes an HTTP(s) call to the MSX_A running on the IIS.
2.Microsoft Internet Information Server (IIS) uses Basic Authentication to authenticate user based on NT user/password against the Microsoft Exchange Server.
3.CDO uses the authentication token and fetches the data.
4.MSX-A converts the data into XMl and returns it to MSX-J
Installation of MSXA Components
You have to carry out these steps for every IIS that accesses the exchange server or the Outlook WEB Access 5.5 SP Server in the system landescape:
1.Locate the MSX-A component shipped with Exchange transport.
The components can be found in<irj>\root\WEB-INF\PORTAL\PORTALAPPS\com.sap.netweaver.coll.appgw\WEB –INF\external\Exchange.
2 Locate an IIS that is in the same domain as the Exchange Server or in a trusted domain.
3.Create a folder on the IIS for example,c:\SAPExchangeTransport.
4.Copy the MSX-A Components to the folder you just created.
5.Register the DLL by using command regsrvr32 in the command prompt for example c:\winnt\sysytem32\regsvr32.exe c:\SAPExchangeTransport\SapExchangeConnector.dll
6.Create a new Iis Website or if using Outlook Web Access 5.5 sp4 create a virtual directory
Since most of configuration errors arise in the setup and configuration of the MSX-A components a separate test application is shipped with the connectivity, which allows you to check that the setup is correct.
1.locate SAPPXchTest.exe which is shipped with the exchange transports.The components can be found at <irj>\root\portalapps\com.sap.netweaver.coll.appl.gw\external\exchange.
2 copy the executable file to the machine on which the MSX-A component has been deployed.
3.Test the CDO version by launching the executable file on the machine on which msx-a was deployed.Choose Test CDO-Version .You should receive a success message .if you recive an error message follow the instructions given
4Test data retrieval by launching the executable file on the machine on which MSX-A was deployed choose Test&#61664;Data Retrieval Fill in necessary fields you should receive a success message but if you receive an error message follow the instructions given
5.Choose Save Results
6.open the log file indicted by the message
<b>Notes</b>
0000801234     Additional attachment in room created appointments
0000788151     Post Installation Steps for Groupware after an upgrade
0000763062     Problem creating an appointment with attachment
0000738965     E-mail address is mandatory for Groupware Integration
0000736644     Mandatory Steps for MS Exchange Integration
0000736541     Support information for MS Exchange Integration
0000732911     Integrating Outlook Web Access in Enterprise Portal 6.0
0000712902     SSO to Outlook web access using user/password does not work
<b>Constraints</b>
Constraints of Microsoft Exchange Connectivity
&#61607;     The Microsoft Exchange transport currently only support items with types appointment and meeting request .Other types such as discussion and not currently not supported.
&#61607;     Deleting an instance of a recurring appointment affects only that particular instance
&#61607;     Calendar items in personal folder are not supported. Users can only view and modify items located on the exchange server from the iviews
&#61607;     Public folders on the exchange server are not supported
&#61607;     Calendar items are delivered as such  if sent to recipients within the intranet .If the recipients is in different domain than the sender ,the format in which the items are delivered depends on the server responsible for sending the item in question