|
New Page 1
|
SAP Lotus Notes
Integration - Using Domino Mail
Transfer Agent
Page 4 of 6
4.0 Technical Specification on the
Integration Process: How to integrate SAP R/3 with Lotus Notes
using the Domino Mail Transfer Agent for SAP
R/3:
The two approaches of Domino Mail Transfer Agent
for R/3 and R/3 workflow enabled mail template are the ones, which
are easiest to imply. These are installed, configured and made
available to the users in original form without using much
development. The other approaches of integration by using LEI, DECS
and LSX are used as integration tools. Even out of these approaches,
LSX requires developer programming while LEI and DECS both are based
on the administrative-level system integration. This is supported by
the fact that in both of these approaches, the users are provided
with form-based control with standard administrative user interface.
Integration of Lotus and SAP R/3 is of great
importance to the organizations to send messages from a Non-Domino
end to a Domino end. This is achieved by using the object Server
Task of a Domino Mail Transfer Agent, which is responsible for
receiving mails from SAP R/3. This is accomplished by receiving the
messages via the RFC function SX_OBJECT_RECEIVE, through a
connection with R/3 system, built in the starting stages during the
registration process.
In order to connect object server with SAP R/3,
the users are required to set an environment variable on the
platforms called as RFC_INI, which is a path to saprfc.ini. This
path is to be stored in the Domino Program Directory. The next step
is to enter the following connection details in saprfc.ini:
DEST=YOUR_MAIL_SERVER (the destination is used,
when launching the Server task)
TYPE=R
GWHOST=<ip-address>
GWSERV=<sapgw##>
PROGID=<hierachical name of Domino Server>
SYSNO=<##>
Here, DEST stands for destination specifying
connection information. GWHOST is the gateway host that is the R/3
system’s ip address with or without SAP router strings. GWSERV
stands for the user’s system address. PROGID is an arbitrary string
used to identify RFC destination from an R/3 (usually combination of
server name and task name) and SYSNO stands for the system number
that is with the SAP GUI.
Although the Object Server enables users to
receive mails from R/3, but in order to send mails to R/3, the users
are required to enable the Object Client part. In order to activate
the Object Client part, the users can follow any one of the steps
given below:
- Type "load objclnt Password [ClntNo [SapMail [SapServer]]]" on
the server console. Here, Password stands for the R/3 password for
the system, ClntNo stands for Objclient in case of multiple
instances, SapMail stands for foreign domain database and
SapServer stands for server for the SAP mail database.
- To start the Object Client automatically along with the Domain
Server users can add
"ServerTasks=Replica,Router,Update,Stats,AMgr,Adminp,Sched,CalConn,Http,
objclnt Password, ..."
To the ServerTasks line of notes.ini. Or create
a program document in the PNAB
|
Basics |
 |
Schedule |
|
|
Program name: |
nobjclnt |
Enabled/disabled: |
STARTUP ONLY |
|
Command line: |
Password |
|
|
|
Server to run on: |
mail_server/mail_org/DE |
|
|
In order to check the connectivity of the object client with
other systems, the users are required to type ‘show task ’ or ‘shta’
on the server console.
|
New Page 1
|
