This version of SAP Exchange Connector 2.0 should only be used with Microsoft Exchange 2000 Server Service Pack 2 upwards for production operation. It must not be used with Microsoft Exchange 2000 Server (with or without Service Pack 1) for production operation, because these versions do not contain the hot fix for the message ID problem (SRZ010716000612). You may use SAP Exchange Connector 2.0 with Microsoft Exchange 2000 Server (with or without Service Pack 1) for test purposes, but pay attention to the restrictions regardingstatus notification assignment.
The new version of the SAP Exchange Connector (version 2.0) connects the Microsoft Exchange 2000 Server (hereinafter generally known as Exchange) to the SAP system. This enables SAP applications and SAP users to send and receive documents to and from an Exchange mailbox. Documents can also be sent and received in the SAP system using other connectors that are connected to the Exchange server, for example, over the Internet or as a fax. Attachment files (for example, SAP documents, Microsoft Office documents, fax bitmaps) can be transmitted in both directions.
Note that SAP Exchange Connector 2.0 is compatible only with Microsoft Exchange 2000 Server, and not with any earlier versions. (Both native mode and mixed mode are possible for the interaction between Windows and Exchange.)
The SAP Exchange Connector controls message receipt, message conversion and message transport between Exchange andSAPconnect, the SAP systemís communications interface. This mean that connectors installed on the Exchange server (gateways) can also be used from the SAP system. Examples include:
The SAP Exchange Connector exchanges messages with the SAP communications component SAPconnect by SAP Remote Function Call (RFC). The RFC used here is based on the transport protocol TCP/IP.
The communication between the SAP Exchange Connector and Exchange takes place using RPC mechanisms. The RPCs can be transported locally or using the LAN protocols TCP/IP, NetBEUI, IPX/SPX, or Banyan Vines.
The SAP Exchange Connector is made up of three Microsoft Windows 2000 system services. These services can be installed either on an Exchange server or, to distribute the load, on a separate Microsoft Windows 2000 computer. The diagram below illustrates the interaction between the three services:
The RFC Out service takes messages from the SAP system and transfers them via a queue to the Gateway service, which then forwards them to the Exchange MTA. Incoming messages flow via the Gateway service and the RFC In service, which then forwards messages to the SAP system.
The diagram below shows the flow of internal and external messages in more detail:
Messages can be sent via the server coupling between the SAP system and Exchange. External messages can be sent from and received in the SAP system using the fax, Internet, and X.400 connectors connected to the Exchange server.
SAP users receive status messages, such as read or send confirmations for messages sent using the SAP Exchange Connector. This applies both to messages sent to Exchange mailboxes, and to messages sent using Exchange connectors to Internet, fax, or X.400 addresses.
The SAP Exchange Connector was designed according to the store-and-forward concept. If the connection to the SAP system or Exchange is interrupted, the transfer of messages is triggered repeatedly for a specified time period.
The diagram below shows an example scenario for implementing the SAP Exchange Connector:
You can also set up a mail system group between Exchange and SAP systems using the SAP Exchange Connector. Exchange is the central mail system in this mail system group. All messages sent internally in the SAP system are then transferred to Exchange. For more information, seeA Mail System Group Between an SAP System and an External Mail System.