What Is Groupware

Solution Management SAP Solution Topic Area Solution Manager
Phase Area
What is Groupware?
Best Practice for Solution Management
Version Date: January 2007
Contents
Applicability, Goals, and Requirements................................................................................................3
Different GWI Technologies ...............................................................................................3
Best Practice Procedure and Verification.............................................................................................5
Procedure .........................................................................................................................5
GWI Scenarios............................................................................................................5
Activity Management ...................................................................................................5
Business Partner Management....................................................................................6
Public folder synchronization (GWA01)........................................................................6
Private folder synchronization (GWA02) ......................................................................6
Workforce Management (People/Resources Planning) ................................................7
Components................................................................................................................8
Groupware Adapter .....................................................................................................8
Groupware Connector .................................................................................................9
Mapbox........................................................................................................................... 11
MapBox Family of components..................................................................................12
The MapStore Schema..............................................................................................16
Data Exchange in the Groupware Integration system landscape ......................................19
Queues used for the data exchange ................................................................................21
Benchmarks for data processing .....................................................................................23
Benchmarks related to the MapBox ...........................................................................23
Limitations for the GWConnector.....................................................................................24
Excursus: Impact of the UserList ...............................................................................24
Most Common Problems.................................................................................................25
Problems related to MapBox .....................................................................................25
Problems related to GWConnector ............................................................................26
Verifying Connection to the MS Exchange Server............................................................28
Obtaining Error Details ....................................................................................................29
Using Diagnostics Tool (Exchange Connector) ................................................................30
Using Diagnostics Tool (Lotus Connector) .......................................................................30
Problems related to GWI application................................................................................31
Performance problems ..............................................................................................31
Settings Related to the MapBox ................................................................................31
Recommended memory settings for the MapBox.......................................................31
How do I set the recommended memory settings for the MapBox? ............................31
Further recommendations ...............................................................................................32
Recommendations concerning the system landscape ................................................32
Performance and Hardware Requirements ......................................................................33
Hardware Requirements of GWConnector.................................................................33
Network Bandwidth Requirements.............................................................................33
Hardware Requirements of the MapBox ..........................................................................34
Recommended support packages/ patch levels .........................................................34
GWConnector proxy recommendations ...........................................................................35
Integration Landscape ...............................................................................................35
Further Information ...........................................................................................................................36
Important Notes...............................................................................................................36
GWI Application Notes ....................................................................................................37
Knowledge Documents....................................................................................................37
Applicability, Goals, and Requirements
Different GWI Technologies

In general, Groupware Integration can be divided into; server-to-server, client-to-client and server-to-client,
based synchronization scenarios.
In a client-to-client based synchronization, an application is implemented on a Mobile Client.

For example, the field sales application which supports the business process ‘Activity
Management’. Following the example, appointments can be maintained in the field sales
application and synchronized with a CRM backend system employing the so called ‘ConnTrans’
application. Synchronization between the application on the Mobile Client, with Outlook or Lotus
Notes running on the same mobile client is supported.
In a server-to-server based synchronization business objects are synchronized between a CRM

server and Groupware (Microsoft Exchange or Lotus Domino) via the CRM Groupware Adapter,
including the MapBox and the Groupware Connector. It is not possible to use the client-to-client
based synchronization in parallel to the server-to-server based synchronization. This scenario is
supported for CRM 4.0 and 5.0.
In a third scenario (client-to-server) the CRM server communicates directly with a CRM Web
user-interface. This scenario will be supported starting from CRM Release 5.1.
In the following figure, the three groupware solutions are depicted schematically.
client-to-server
CRM
client-to-client Web-UI Groupware
CRM 5.1
Groupware
Mobile CRM
Sales Server server-to-server
CRM Exchange
MW Server
Groupware
In this document, we will focus on the server-to-server based synchronization only. The server-to-server
based groupware Integration enables the synchronization of business partners and activities
(appointments and tasks) between CRM and Microsoft Exchange or Lotus Domino. You can generally
distinguish between public folder synchronization (GWA01) and private folder synchronization (GWA02).
These different synchronization techniques will be described in the next section.
The server-to-server based groupware integration is part of the Austrian Package which is an ‘easy to
implement’ solution based on CRM 4.0. It also contains business partner management, activity
management and the CRM reporting framework. The SAP Sales Express solution (a predecessor of the
Austrian Package) is a package that contains the server-to-server based groupware integration in addition
to campaign management and integration with SAP ERP.
Best Practice Procedure and Verification
Procedure
GWI Scenarios
The Business Partner data as well as activities and tasks in SAP CRM can be integrated using server-to-
server based synchronization. This data exchange between CRM and Groupware can be implemented
bidirectional, that is, the data created or modified in the CRM system can be conveyed to Groupware and
data created or modified in Groupware can be conveyed to CRM. The synchronization between SAP CRM
and Groupware Servers takes place in real time.
The data synchronization is only supported for predefined fields, meaning that there is no guarantee that
data fields from Custom Forms being used within Microsoft Outlook or Lotus Notes will be synchronized
between SAP CRM and Groupware Servers.
The Business Scenarios ‘Business Partner Management’, ‘Activity Management’ and ‘People/Resource
planning (Workforce-Management)’ are supported and will be discussed in this section.
To enable data exchange between the CRM server and groupware systems, the CRM Middleware is
enhanced with a framework that seamlessly integrates the CRM server with the Groupware servers, for
example, Microsoft Exchange 2000/2003 or Lotus Domino 5.0.x groupware servers.
A user of groupware solutions normally performs the following tasks:
Maintains Contacts
Sends and receives e-mail messages
Creates personal tasks
Uses the calendar for managing appointments with employees and business partners
The following business scenarios can be used with Groupware Integration:
Activity Management
Allows bidirectional exchange of activities (CRM), appointments and tasks (groupware) between
the CRM server and the groupware server
Allows bidirectional exchange of attachments along with activities (CRM) and appointments and
tasks (groupware) between the CRM server and groupware server
Provides additional information, such as a link to the opportunity that triggered this particular
activity
Tasks and appointments in Microsoft Exchange (Outlook) or Lotus Domino that are flagged for replication
(via assignment of the category CRM_ACT) will be replicated to SAP CRM. Activities that are created in
SAP CRM will be sent to Microsoft Exchange (Outlook) or Lotus Domino when the ‘calendar maintenance’
flag is set.
In the customizing settings of the CRM server, you can define filter criteria for Business partner exchange
with Groupware based on the category and role for the business partners. The filter criteria can be defined
to be applicable for replication from CRM to the groupware server, which can be either inclusive or
exclusive.
For appointments and tasks which are replicated from the CRM server to groupware, it is possible to
attach a link to the activity or task accessible via the SAP portal. Alternatively, a business server page
(BSP) link is available. For details see SAP note 931165.
The replication of attachments is supported for activities from CRM to groupware and vice versa. The total
maximum size of all the attachments in a Business Activity should not exceed 1 MB.
Follow-up activities and tasks to CRM Opportunities are also replicated to the Groupware Server. In this
case the CRM Opportunity information is embedded along with the corresponding appointment or task.
Meeting Requests to distribution lists are not supported by the current version.
Private appointments are not synchronized between the Groupware server and CRM, however, private
tasks are synchronized.
Business Partner Management

The SAP CRM Business Partner data can be integrated with either a global address book on the
Groupware Server or with the private address book of individual groupware users.
Public folder synchronization (GWA01)

Allows bi-directional exchange of business partners (CRM) and contacts (groupware) between the
CRM server and groupware public contact folder
The synchronization with the global address book is called ‘public folder synchronization’ (GWA01). In this
case all SAP CRM Business Partners that are meant for replication to Groupware are replicated to the
global address book from where all groupware users can access the CRM Contacts. This integration is
“bidirectional”, i.e. the contacts that are added to the global address book or the modifications that are
made to the existing contacts in the global address book in Groupware is conveyed to SAP CRM Server.
No relationship data to an account, organization or Group is mapped.
Private folder synchronization (GWA02)

Allows the transfer of Contact Person and Business Partner information from CRM to the Private
Contact Folder of individual users in Groupware. The business partner data sent to the individual
groupware users is distributed based on the subscriptions defined in the Administration Console.
The private folder integration is “uni-directional”, that is, the new contacts that are added to the private
address book or the modifications that are made to the existing contacts in the private address book are
not replicated back to the SAP CRM Server. The synchronization with the address book of individual
groupware user is called ‘private folder synchronization’ (GWA02). In this case, replication rules are to be
set in the CRM Server (Admin Console) for the CRM Business Partner data. The individual groupware
users receive the respective CRM Business Partner data in their private address book on the Groupware
Server, based on these rules.
The global address book synchronization and the private address book synchronization can be set up in
parallel.
Workforce Management (People/Resources Planning)

Workforce Management (WFM) allows the replication of appointments and tasks from CRM project
resource planning to the groupware system.
Recurring appointments are synchronized between Resource Planning Application and Groupware
Server within the ‘Workforce Management Groupware Integration’ scenario. Daily, weekly and monthly
recurring appointments with an appointment start and end time on the same day can be replicated
between the RPA and groupware via CRM Middleware. The replication of yearly recurring appointments
is not supported.
Example
A user in Project Resource Planning uses the resource search to find appropriate and available
resources for a requirement. WFM Core sends the results of the search to the application. The
resource manager then creates an assignment by staffing a project role (to which the requirement
is attached) with a resource. This assignment can be transferred to groupware as a task to the
resource’s mailbox.
The activities created in the RPA are provided to groupware users. Activities are represented as an
appointment or a task (on the groupware server). The groupware adapter transforms both objects to the
Internet standards for groupware objects, that is, iCalendar for tasks and appointments.
Components
In this section we will provide an overview of the technical components relevant for groupware integration,
namely the Groupware Adapter, the MapBox, the Groupware Connector and the Groupware Connector
Proxy. A detailed description of these components will be given in the next section.
The following figure illustrates the general architecture and main components of groupware integration.
On the CRM server, the Groupware Adapter manages incoming and outgoing messages. The MapBox
framework (SAP SyncPoint) performs the required transformations of the data which is exchanged with
groupware. The format of the messages exchanged between the CRM server and groupware is based on
the vCard and iCalendar standards. A server-specific SAP Groupware Connector acts as a bridge
between the Groupware Adapter and the Groupware Server. It provides the mapping of the standard
exchange formats to the proprietary Groupware Server formats and vice versa.
Groupware Adapter
The SAP Groupware Adapter on the CRM server is based on the SyncPoint technology and supports the
transformation of BDoc messages to standard groupware formats (iCalendar and vCard) by using a
sophisticated XSLT mapping framework called MapBox and the Payload Interface (SOAP based
messaging interface for exchanging data between the CRM server and groupware connector). iCalendar
and vCard are the Internet standards to represent groupware calendar objects and contacts. Predefined
mappings of a BDoc message to iCalendar and vCard, created using the MapBox, are delivered for
groupware integration.
The Groupware Adapter is a CRM-Middleware enhancement of the Inbound / Outbound Adapter used for
the Mobile Sales solution (Sync-Adapter). The Sync-Adapter provides the overall controlling framework
and the technical I/O-paths for the data transferred between the external site and the CRM-middleware.
The Internal SyncPoint (ISP) consists of the Sync-Adapter, a Payload Interface (PLIF) and the MapBox.
The PLIF is a general Messaging Interface which the CRM Middleware uses to communicate with the
outside world. This Interface does not manipulate data, but is responsible for the technical aspects of the
message exchange.
Groupware Adapter
Transforms BDOC => BDOC-XML
Queue handling
Calls the MapBox
Groupware Connector
The SAP Groupware Connector is an external application to the CRM server and performs the message
synchronization between the CRM server and the groupware server. Message transfer is performed using
a reliable and open messaging interface based on XML-SOAP.
Technically, the Groupware Connector is an application written in C++ which scans the CRM outbound
queue for messages which are relevant for Groupware Integration at regular intervals (usually every 5
seconds). In addition, the Groupware Connector receives XML documents from the Microsoft Exchange
Server or Lotus Domino Server and transfers them to the CRM Groupware Adapter.
SAP provides two Groupware Connectors, one for the Microsoft Exchange Server and another for the
Lotus Domino Server. Both connectors perform server-based data synchronization between the CRM
server and a Groupware Server. They are linked to the CRM server through the Groupware Adapter that
is part of the SyncPoint technology. The connection between the connectors and the groupware adapter
is established through the SOAP protocol over HTTP.
The Microsoft Exchange Connector uses Microsoft Collaboration Data Objects (CDO) to connect to the
Microsoft Exchange Server. The Lotus Domino Connector uses the Lotus Domino toolkit for Java/CORBA
to connect to the Lotus Domino Server. The SAP CRM Groupware Connector is created as a Windows
NT service and runs under a NT user account.
The Groupware Connector can be set up to serve one or many Exchange Servers. In case only one
Exchange Server is connected, the default proxy will be used. In a scenario where multiple Exchange
Servers will be connected, a proxy must be implemented for every exchange server. Furthermore, one
proxy per domain is required.
The configuration of the Groupware Connector (here the MS Exchange Connector) can be analyzed and
changed in the Groupware Connector Administration Tool.
The configuration of the Groupware Connector Proxy can be seen in the Admin Tool, Proxies => General.
Mark the corresponding proxy, double-click on the proxy name or use button “Edit Proxy Configuration”.
Mapbox
The MapBox stores:
customizing data
iCal/vCard
mapping between BDOCID and GWI-related UID. This BDoc ID -> GW ID is needed to map a
groupware object to a BDoc in the reverse direction. When, for example, an activity/bp is
created/changed in Groupware, the GWConnector checks if a BDOCID already exists for an
incoming UID. If no BDOCID exists, the creation of a new activity/bp in CRM is triggered. If a
BDOCID related to the UID is found, a change/update of the activity/bp is performed.
userlist: mapping between BP-GUID and email-address. The userlist is stored as an xml-file
(Userlist.xml). The xml-file contains partner functions, roles and rules that define for which roles
which partner functions are activated.
The MapBox is an XML-based document transformation framework, performing document
mapping along with flow-control capabilities. Technically, the MapBox is a Java-based Mapping
component which is called from SAP CRM via a Java Connector (JCO). The MapBox uses a set
of instructions to transform a source document into a destination document. This mapping-
scenario is called the MapScenario. The MapBox is also employed for the multiple backend
solution (MBS).
In general, mapping scenarios are employed when two systems need to interact with each other, but the
document format is not identical for both systems. From this point of view, the MapBox has a similar
function as an XI (exchange interface) system as the MapBox connects two different systems which
understand different formats of an XML based document.
Input
Output
XML
MAPBOX XML
Docu
Docum
ment
ent
As shown in the figure above, the MapBox receives XML documents in a given format and delivers XML
documents in a different format. As an example, consider an SAP CRM system exchanging contact-
details with a Groupware solution such as Microsoft® Outlook. While the SAP CRM system and
Microsoft® Outlook both model and interact with respect to the same real world entities, namely business
contacts (that have real-world attributes such as Name, Communication details, etc.), they do not use the
same internal representation nor the same modeling schema to depict these real world entities. In this
example the SAP CRM system provides XML BDocs, whereas the Groupware solution expects business
objects in the format vCard.
MapBox Family of components
To achieve the task of the transformation, the MapBox is assisted by a number of components which are
described below.
a) The MapBoxLauncher
The MapBox is an application framework. To use the MapBox in various usage scenarios,
applications need to set up the MapBox according to their requirements. The MapBox family of
components provides an application for use in the Groupware Integration application and the Multiple
Exchange Platforms projects, called the MapBoxLauncher. As the name may suggest, the
MapBoxLauncher ‘launches’ the MapBox for use by other applications.
Programmatically, the MapBoxLauncher provides a way for an SAP CRM system to send messages
for execution of the MapBox and, once the processing is performed by the MapBox, to receive the
processed message. Using the interface that the MapBoxLauncher provides, applications can invoke
the MapBox as a function call in ABAP® programs.
For the users, the MapBoxLauncher is the sole access-point for the MapBox. Thus, using the
MapBoxLauncher’s web-based user interface, users can perform operations such as:
(i) Configuring the MapBox to process messages from a SAP CRM system
(ii) Starting the MapBox
(iii) Monitoring the MapBox processing status
(iv) Re-starting/Stopping the MapBox
Starting and Stopping MapBox in the MapBoxLauncher
Log Settings in the MapBox Launcher
b) The MapBox Repository (also known as the MapStore)

During the course of it’s processing, it is sometimes necessary in a MapScenario, to store some data
for a later use in some Mapping tasks. For a MapScenario, the only way to be able to refer to some
data is to import & store this data itself. For the purpose of both storing intermediate data during the
processing of a MapScenario as well as for data that the MapBox would require later, a repository
known as the MapStore is provided for the MapBox.
c) The CoordServer
The Coordination Server for the MapBox ensures that the access to the MapStore is thread-safe, that
is, problems arising from accessing the same records from the MapStore by two different instances of
the MapBox are prevented.
d) The CoordLauncher
The CoordLauncher is a J2EE-based component that “launches” the CoordServer for use by the
MapBox. Using the CoordLauncher’s web-based User Interface, users can monitor the execution
status of the CoordServer. (No start-stop functionality is provided, because once configured, the
CoordServer starts automatically once the SAP J2EE Engine 6.20 starts its execution).
e) The Internal SyncPoint

The Internal SyncPoint (ISP) is a component that resides on the SAP CRM server and is responsible
for communicating with the MapBox from the CRM server. Thus, the ISP forwards processing
requests to the MapBoxLauncher, from where they get passed to the MapBox for processing. The ISP
is also responsible for reporting of exceptions during the execution of the MapBox.
The relationship of the MapBox to the components mentioned above is schematically depicted in the
diagram below. The ISP sends a request for processing a message (for example, to transform a SAP
CRM Appointment to a Microsoft® Outlook Appointment) to the MapBox, via the MapBoxLauncher (MBL).
The processing request consists of the message to be processed, the name of the MapScenario to be
executed, and other parameters needed for the execution. The MapBoxLauncher forwards this request to
the MapBox. During it’s processing, the MapBox may need to write some records to the MapStore. The
CoordServer is consulted before the MapStore access.
Once the MapScenario is executed, the MapBoxLauncher packages the return values of the MapBox call
(which include the processed message in case the execution was successful, or an error message in case
the MapScenario encountered any exceptions/errors during its execution), returns the processing control
back to the ISP, and awaits for further processing requests.
Operations such as start-stop-restart and execution monitoring for the MapBox are performed by the UI-
component of the MapBoxLauncher. The CoordLauncher provides a means for monitoring the operational
status of the CoordServer.
The MapStore Schema
The MapStore on the CRM Server consists of five MapBox tables with the following content:
1. MBGLOBSTORE
Table MBGLOBSTORE contains the mapping data. The data is client-independent and is transported to
all other clients. Data of type c (MapCode).
DATASET: scenario, such as MBDGWA_01, MBDGWA_02 (any name can be given here)
MBGUID: GUID (key field)
MBDATA : XML-Data
2. MBMANDTSTORE
MBMANDTSTORE contains data of type d (MapData). If customizing is downloaded, it is stored in this

table. The data consists of client-specific runtime data which is not transported.
Customizing data is used in the following way: The BDOC only stores abbreviations, for example, for
country (e.g. DE). The MapBox retrieves the long name for the country from table MBMANDTSTORE (e.g.
DE => Deutschland). The key for finding the correct data is given by a path such as
“MBDGWA_01.d.BUPA. GW_BUPA_COMPLETION”, which corresponds to the hierarchical folder
structure that the MapBox is organized in and to the columns contained in the table.
Furthermore, MBMANDTSTORE stores the relationship between a BPGUID and an email-address. If an

activity is created in CRM, it only contains the BP GUID. In table MBMANDTSTORE, it finds the
corresponding email address.
3. MBMANTTSTORE
This table contains client-independent customizing data of type m (Mandant Data).
4. MBVALUESTORE
Acts as a Key-Value table to store runtime data.
5. MBPAIRSTORE
Acts as a Key-Key table to store runtime data.
Pair values UID and BDOC ID are stored in this table. If, for a certain UID a corresponding BDOC ID is
found, the Groupware Connector will interpret the new data as an insert and update the existing data.
Otherwise, a new activity/business partner will be created.
The tables of most interest for the analysis are the tables MBMANDTSTORE and MBGLOBSTORE. All
MapBox, tables will be analyzed in case of intermediate state I.
The figure above illustrates the internal data model of the MapBox. Each MapStore table corresponds to a
certain logical part of the dataset.
The names are made up of several parts. The same structure can be found in the MapStore tables, as you
can see in the example of MBGLOBSTORE below:
The XML document contained in field MBDATA can be read with report GWA_VIEW_MBSTORE, which
will be available in future CRM releases.1
1
The report is currently only available in the SAP-own Test System Q4C.
In order to execute the report, proceed as follows:
Select the table
P_GLOBST => MBGLOBSTORE
P_MANDT => MBMANDTSTORE
P_MANTT => MBMANTTSTORE
Copy GUID into field S_MBKEY, double-click

=> you will receive an XML file
Data Exchange in the Groupware Integration system

landscape
In the following paragraph, we will illustrate the data flow within a GWI system landscape.
BDOC
Mapbox iCal / vCard

(XML format)
(XML format)
Proxy
(XML format)
Groupware
Clients
On the CRM server, the Groupware Adapter manages incoming and outgoing messages. As the
MapBox is a Java-based application, whereas the CRM application is programmed in ABAP, the BDOCs
in CRM have to be transformed in a way that they can be read by the Mapbox. Therefore, the Groupware
Adapter transforms the BDOC messages to BDOC-XML.
Groupware Adapter is not a part of CRM Middleware. CRM Middleware calls the Groupware Adapter.
Groupware Adapter calls MapBox, which transforms the message and gives it back to the Adapter.
The MapBox represents the Groupware Adapter framework and runs on J2EE. It performs the required
transformations and enrichments or reductions of data. The incoming BDOC-XML messages are either
transformed to vCard-Format (for business partners) or to iCalendar (for activities). The messages are
pushed towards the MapBox.
After the transformation into vCard and iCalendar standards, the messages are put into the outbound
queue of the CRM-Server. They remain there with status “NOSEND”.
A server-specific SAP Groupware Connector acts as a bridge between the Groupware Adapter and the
Groupware Server. The Groupware Connector regularly checks if there are entries in the outbound
queues of the CRM Server. It retrieves the data from the CRM outbound queues (Pull-mechanism).
Furthermore, the Groupware Connector provides the mapping of the standard exchange formats to the
proprietary Groupware Server formats and vice versa.
During the replication of appointments, tasks and business partners from Groupware to CRM, the
Groupware Connector Proxies (written in C++) scan all user’s mailboxes, calendars and tasks for new
entries. This is done for all employees who are maintained in the userlist.xml file (can be displayed in
Groupware Connector). Microsoft’s ICS (Incremental Change Synchronization)2 is used for monitoring and
synchronizing changes if Outlook is used.
The following figure shows the protocols used for communication between the different GWI components:
2ICS: Incremental change synchronization (ICS) provides a mechanism to monitor and synchronize
changes to an information store hierarchy or content. The changes include creating, modifying and
deleting folders and messages.
ISP_D* BDOC-XML => iCal /vCard
CRM- GWAdapter I BDOC-XML MapBox
BDOCID=>
Applicat BDOC =>BDOC- UID
iCal /vCard
ion XML
O iCal
ISP_O*
MW vCard
GW connector pulls the

message
GW
In case UID=>BDOCID
Connector UID =>
GW connector BDOCID
creates an
object
iCal/vCard/ MAP BOX
MSX
ok
UID=>BDOCID²
GW
ISP_I* Inbound Queue
Connector
²bp-number, MW
activity-number
task-number
The figure above illustrates the data flow in a GWI environment from a more technical point of view.
Queues used for the data exchange

The following section takes a closer look at the queues used for exchanging data in a GWI landscape.
According to a naming convention, many queues used for the exchange of GWI data start with ISP*
(whereas ISP stands for Internal Sync Point).
Data flow direction CRM => Groupware

On the creation of a business partner or activity in CRM, a BDOC in XML-format is formed and processed
by the ISP_D* queue. After the transformation into iCal/vCard format, the data is put into the ISP_O*
queue where it is fetched by the GWConnector.
Data flow direction Groupware => CRM
Newly created iCal/vCard objects are sent via the ISP_I* queues to the MapBox. Having transformed the
objects into BDOCs, they are processed by the ISP_S* queues. If there is an error, messages are sent
back to the GWConnector in the ISP_D* queue.
There are two kinds of ISP_D* queues:

One is reserved for GWA01-Scenario (public folder synchronisation)
the other for scenario GWA02 (private folder synchronization).
ISP_O* (outbound) queues, flowing from the MapBox to the Groupware Connector, contain:
the userlist (say ISP_O*17)
the catlist (say ISP_O*18)
the Public Folders (say ISP_O*19)
and every Private Folder (say Employee 1 in ISP_O*20 , Employee 2 in ISP_O*21 ).
ISP_I* (inbound) queues are created for every user. When a new user is created, a unique queue name is
dynamically created and linked to the user’s email-address. The mapping between email-address and
queue-name is stored in table ISPQTAB and is fixed from thereon. Furthermore, public folder queues and
system queues (see below) will be processed in ISP_I* queues.
Example:
Employee 1 ISP_I*10.
Public Folder ISP_I*11
CMW_PIF_ID_QUEUE ISP_I*12
CMW_PIF_PROTOCOL ISP_I*13 etc
The ISP_S* (secondary) queue is formed after mapping. For every BDOC type, a different ISP_S* queue
is created.
Example:
BUPA_MAIN (Public folder) ISP_S*5
BUS_TRANS_MSG (Activities) ISP_S*6.
Furthermore, the Groupware Adapter provides a predefined set of system queues. There are the
following system queues:
_ISP_QFILLED (ReadOnly) GWA provides a list of currently filled queues from CRM
side.
CMW_PIF_ID_QUEUE (WriteOnly) GWC posts IDs of the newly created messages in
Groupware server storage. This will update the mapping between CRM and Groupware items on
GWA side.
CMW_PIF_PROTOCOL (WriteOnly) GWC posts error notifications into this queue.
USER_LIST (ReadOnly) GWA provides a list of users whose data is intended for
replication Groupware to CRM.
CATS_LIST (ReadOnly) GWA provides list categories used to mark messages in
Groupware server storage intended for reapplication.
Whenever an update or deletion related to a user arrives, it is processed by the queue belonging to that
user.
Benchmarks for data processing

Benchmarks related to the MapBox
MapBox processing underlies the following technical limitations
The total size of the documents attached to an activity may not exceed 1 MB. Attachments bigger
than 1 MB cannot be processed.
The blocksize for adapter objects BUPA_MAIN and GWA_COUNTRY should be set to 10
(transactions R3AC1, R3AC5 ‘Adapter Object Overview’).
3
A high number of users in table MBMANDTSTORE can lead to performance problems during the
processing of ISP_D* queues. In order to quicken the processing in ISP_D* queues, please refer
3
Performance issues have been detected in systems with more than 100 000 users in table
MBMANDTSTORE. Entries in MBMANDTSTORE will be deleted if they have been correspondingly
removed from the CRM server.
to note 920953 ‘Slow performance by MapBox when processing ISP_D queues’. Please take as
well into account the prerequisites of this Note before applying the same.
Limitations for the GWConnector

According to customer experience, a number of 5000 users in userlist.xml will cause problems for the
GWConnector in question of performance. For further details please refer to SAP note 983436.
Excursus: Impact of the UserList
Functionality:
The UserList.xml file contains a list with all Business Partners with role Employee in CRM. There is no
mechanism involved to allow only a few employees (who are using Groupware) to be downloaded to
UserList.xml file. If certain Employees should not be included in the UserList.xml file, there are several
ways to do so:
They can be manually removed by editing the UserList.xml file.
Alternatively, the employees email address (who will not be part of Groupware) has to be deleted
in CRM transaction “bp”.
You can also move the email address of the business partner maintained in the Standard Address
Dependent Communication Section to the Address Independent Communication Section in CRM
transaction “bp”.
If the employees relevant for GWI are changed frequently, filtering on the userlist.xml file can be
done by implementing the following SAP note:
983436 Groupware Integration: Filtering on UserList.xml file
For further information, also refer to SAP note 935129.
For the replication of activities from Groupware to CRM, the user ID (SMTP address) of the organizer who
triggers the appointment change has to be available in the UserList.xml. The userlist has no relevance for
the synchronization of activities from CRM to Groupware.
The Groupware Connector Proxy will sequentially go through the storages of all users provided in the list
and replicate changes to CRM one by one, by posting the messages into user’s data queue in Groupware
Adapter.
A user will be deleted from the UserList.xml provided it is not part of the configured exchange servers.
- Presumed bh1 and bh2 are known exchange servers, users of type abc@bh3.com will be automatically
deleted from the userlist file.
- users of type xyz@bh1.com won't be removed from the UserList.xml even though the corresponding
mailbox is not existing in either bh1 or bh2 exchange servers.
In the xyz@bh1.com example, the Groupware Connector throws an error message and locks the
corresponding activity in Admintool -> Current Locks. Therefore, it is important to maintain a valid SMTP
address during the creation of business partners.
Performance:
In order to estimate the performance of a certain GWI system landscape, please refer to the Groupware
Connector Administration Guide p.11f.
Most Common Problems

Problems related to MapBox
This section contains a description of the most common errors relating to the MapBox.
In CRM transaction smq1, you detect that the ISP_D_* or ISP_I_* queue has failed. The error
messages indicated are one of the following:
1. An MAPCASEEXCEPTION has occurred (RC 94)
2. MapBox Commit - Fatal Error (RC 115)
The possible causes of the errors mentioned above are:

a) Insufficient memory for execution. There are several possible reasons for this error:
- Insufficient heap memory provided for the SAP J2EE Engine 6.20.
- Incorrect block size set during customizing download.
- Older version of SAP J2EE Engine 6.20.
b) Insufficient MapBox instances for processing: there are more requests for processing than
MapBox can handle. Set the parameter Number of Instances to an optimal value of 10. This
can be increased based on the number of queues coming in from SMQ2.
c) Corrupt MapStore: this indicates a presence of intermediate state entries in the MapStore.
d) Connection loss: the MapBox may have lost its connection with the CRM server during
processing.
The different reasons for connection loss are:
a) CRM server is restarted without restarting SAP J2EE.
b) Network issues.
c) Incorrect settings of the Connection details
d) Incorrect configuration of the RFC destination on SM59.
e) Invalid MapScenario: the MapScenario that the MapBox used for execution is in error.
f) Invalid Input Message: the input message for the MapBox is in error.
g) Incorrect JCO version. This however happens only on a 6.20 version of J2EE Engine.
h) The most common problem for MAPCASEEXCEPTION is however a corrupt XSL file on the
MapStore. Use SAP Note 710346 to upload the correct XSL available via the related SAP
Note. Consult SAP Support for the relevant XSL/Note.
i) Incorrect Log Settings: If the log levels of MapBox are set to a very high value, this can cause
a File System overload, resulting in an unexpected behavior of MapBox. Refer to MapBox
installation guide for the optimal settings of all MapBox log parameters.
Also refer to the MapBox Troubleshooting Guide which is available as an attachment to SAP note
817787. Further common errors and methods for solutions are indicated there.
If this does not solve the problem, open a customer message under component CRM-MW-MBX.
Problems related to GWConnector
Verifying Connection to the Payload Interface

Review this section if the following error occurs: “[ERR:3001] SOAP Transport error“
Use MS Internet Explorer or Netscape Navigator to connect to the CRM Adapter. In order to find the CRM
Adapter URL, choose Administrative Tool CRM Adapter Connection General.
Your browser may return a response like “Unable to locate server XXX” or “Page cannot be displayed”.
The two possible reasons for the responses are:
• The payload interface server is down.
Make sure the payload interface server is running on the specified server and is configured according
to the port provided in the URL (The standard HTTP port 80 is used by default).
• The specified URL is invalid.
If a different URL is configured for the Payload interface on the server, you will get the error message
“HTTP Error 404 - Not Found“. Check the configuration of the payload server.
Resolving Payload Interface errors

Review this section if you are getting errors concerning the Payload Interface (error codes 3001 through
3009). These errors can be raised while processing different operations and their resolution depends on
their error code returned by the Payload Interface. You can find the corresponding error code in the text of
error messages.
Code Short Description

0 Success
1 Success - queue created on the fly
2 Error – access denied.
Most probable reasons:
• Wrong parameters are specified for CRM Adapter connection in Admin Tool.
3 Queue does not exist

• There is a problem on groupware connector or groupware adapter side. Contact support team for
details. This error should not happen normally.
4 Another session already established
• Two or more groupware connectors are connected to the same groupware adapter. Verify the
CRM Adapter Connection setting for all running instances of groupware connectors.
5 Session ID not known

• Connection session with groupware adapter has expired due to timeout. Connector will automatically
restore connection as needed. This error can normally be ignored.
6 Wrong parameter
7 Property not known

8 Feature not implemented

9 Unspecific error
details.
10 No more messages available

• All messages are already retrieved from groupware adapter’s data queue. This error can be
ignored typically.
11 Operation not allowed

details.
101 SOAP transport error
• The Groupware adapter is experiencing problems with the network connection. See the chapter
"Verifying Connection to the Payload Interface" for details.
Verifying Connection to the MS Exchange Server

Read this section if one of the following errors occur:
[ERR:1001] Administrative logon failed“
[ERR:2002] Logon failed for:<mailid>“
You will require MS Outlook to be installed.

Proceed as follows:
Log off from MS Outlook (if started).
Choose Start Settings Control Panel Mail applet and configure the Administrative Log-on profile
as follows:
1. Display profiles.
2. Add a new “Microsoft Exchange Server” profile.
3. Type in the name of your account.
4. Specify the Exchange server and Account provided in config.xml (gw.server and gw.admin.account
properties).
5. Select the newly created account in “When starting MS Outlook, use this profile” combo-box.
Launch MS Outlook. If MS Outlook is unable to log on either the Exchange Server name or the
Account provided is invalid.
If MS Outlook is able to login successfully, then probably you may need to follow one of two
procedures to fix the error message:
[ERR: 1001] Invalid Administrative Account. Server =???, Account =???.
[0x8004011d] E_FAILONEPROVIDER.
Add msx_gwconnect to the list of local users using Start -> Control Panel -> User Accounts as
local administrator.
Delete as many temporarily created profiles as possible, which often fixes the error. ( Start ->
Control Panel -> Mail -> Show Profiles )
If you receive the message ERR:#2002, the provided administrative account may have no permissions to
log on to the mailbox corresponding to the provided mail ID.
The Connector (as well as MS Outlook) uses Windows NT authentication for providing authorization in the
Exchange Server. That means, you have to log on locally to the computer running MS Outlook, using the
administrative account, when connecting to the MS Exchange Server. When running the Connector as a
service, authentication information provided on the Logon tab of the service properties is used.
Obtaining Error Details
In case of a connector failure, detailed error information is available in the following places:
1. Error log file provides one line per error with short info.
2. Trace log file provides detailed error information if available. You may use the contents from the
error log to search in the trace file for details.
3. ErrDumps subfolder contains detailed information about errors sent to CRM. A copy of the sent
messages is stored on the local drive.
4. queue-locks.xml use Current Locks page in the Admin Tool to view contents of this file
Each of the mentioned items is available by default. However each of them can be disabled from the
Admin Tool.
Detailed system information may be required to provide support for the solution. The information can be
partially obtained using the diagnostics tool. Refer to the section Using Diagnostics Tool for more detail.
Using Diagnostics Tool (Exchange Connector)
Exchange connector includes GwcDiag.exe diagnostics tool. It will gather system diagnostics using
Groupware Connector configuration and generate reports into SysInfo subfolder.
You need to logon locally using Groupware Connector administrative account to start the tool. The tool
does not require additional parameters to start.
Generated files are:
AddrBook.txt - contains complete dump of the Global Address book with names of the Exchange
Servers holding user’s mailboxes.
Summary.txt - contains short summary of solution: administrative account, size of UserList.xml, size of
Exchange Global Address Book and list of known Exchange servers (identified by references from
Global Address Book).
SysInfo.txt - contains the computer configuration with list of used DLLs.
UserList.txt - contains details of mailbox access verification for each user listed in UserList.xml
UserList Access.txt - contains list of mailboxes and folders the connector is not able to get access to.
UserList External.txt - contains list of external users listed in UserList.xml
UserList Invalid.txt - contains list of users who do not have a mailbox in the organization
Using Diagnostics Tool (Lotus Connector)

Lotus connector includes GwcDiag.bat diagnostics tool. It will gather system diagnostics using Groupware
Connector configuration and generate reports into SysInfo subfolder.
One must logon locally using Groupware Connector administrative account to start the tool. The tool does
not require additional parameters in order to start.
Generated files are:
AddrBook.txt - contains complete dump of the Public Address Book.
Summary.txt - contains short summary of solution: size of UserList.xml, size of Public Address Book
and list of known Domino servers (identified by references from Public Address Book).
SysInfo.txt - contains complete dump of java environment.
UserList.txt - contains details of mail databases access verification for each user listed in UserList.xml
UserList Access.txt - contains list of users from UserList.xml whose permissions prevent them
accessing required databases.
UserList External.txt - contains list of external users from UserList.xml
UserList Invalid.txt - contains list of users from UserList.xml that are not available in the Public
Address Book.
If further help for the solution of the problem is required, open a customer message under component
CRM-MW-GWI-GWE (MS Exchange Connector) or CRM-MW-GWI-GWD (Lotus Domino Connector).
Further typical problems related to the GWConnector and ways of solving them are described in the
GW Exchange Connector Troubleshooting Guide which is attached to note 957409.
Problems related to GWI application

Please investigate the problem following the instructions in the Groupware Troubleshooting Guide.
This Guide is attached to the following note:
908577 Groupware Integration TroubleShooting Guide.
Furthermore, the GWI customizing settings might not be maintained correctly. Please check the
customizing settings referring to the following Guide:
959294 Groupware Adapter Customizing and User Guide
If this should not solve the problem, please open a customer message under component CRM-MW-
GWI.
Performance problems
If performance problems in GWI system landscape are experienced, please assure that the following
performance related GWI settings are maintained:
Settings Related to the MapBox

The MapBox Log Level must be set to 4D in the production environment.
MapBox Message Dumps must be disabled.
Input Payload Dumps must be set to no.
The Stats File must be switched off.
Schedule an automatic batch job to delete the MapBox Logs every day.
When you perform initial downloads, ensure that the log level is set to 4D and no dumps are
enabled.
=> You need to set a higher log level and enable the dumps only for testing purposes.
Recommended memory settings for the MapBox

The MapBox-processing involves extensive XML-processing (schema-validation, parsing,
transformation, etc.) and as such, is a memory-intensive computation. Considering this; the following
recommendations are made pertaining to Memory management:
- Heap size memory bounds of the JVM:
Allocate 1024MB as the maximum heap size (-Xmx) to the JVM that hosts the MapBox.
Allocate 1024MB as the minimum heap size (-Xms) to the JVM that hosts the MapBox.
How do I set the recommended memory settings for the MapBox?

To set the recommended memory settings for the MapBox, perform the following steps:
SAP J2EE Engine 6.20
a) If you use Windows Services to start-stop the SAP J2EE Engine; then use the SAP J2EE
Engine 6.20 Configtool to set the memory values.
b) If you use SMICM transaction to start-stop the SAP J2EE Engine, then edit the file
Best Practice: <Title> 32
cmdline.properties present at the location

<SAP_J2EE_Engine_6.20_root>\cluster\server; set the value of the -Xmx parameter
to 1024M and that of the –Xms parameter to 1024M.
c) If you use the go.bat file present at the location

<SAP_J2EE_Engine_6.20_root>\cluster\server to start the SAP J2EE Engine 620
Server; set the value of the -Xmx parameter to 1024M and that of the –Xms parameter to
1024M.
[Where SAP_J2EE_Engine_6.20_root is the root installation directory of your SAP J2EE
Engine 6.20 installation]
SAP J2EE Engine 6.40 / SAP Web AS Java 7.00

a) Use the Config Tool to set the memory values.
Also, refer to note 697062 for information on Location of JVM options and JVM output in SAP
J2EE Engine 6.20.
Further recommendations
Do not send Attachments of more than 1 MB in size to or from groupware as it has a severe
impact on performance.
When you perform an initial download of business partners, ensure that the block size of the
BUPA-MAIN object is set to 10. If the block size is set to a higher value, it results in a non-
performant download. Equally, the block size of adapter object GWA_Country has to be set to
10.
If a change in customizing affects only one customizing object, you do not need to perform a
download of all the customizing objects. It is sufficient to download the affected customizing
object.
Recommendations concerning the system landscape
Installation of components
Regarding the setup of a Groupware integration system landscape, please take the following
recommendations into account:
Separate strictly between production and test landscape. Do not link production and test
landscape to the same mailbox! You have to be able to check for possible data
inconsistencies, for example, after performing a business partner download to the Outlook
public folder.
For J2EE versions below 640, we recommend installing the MapBox on a separate server.
Theoretically, all components can be installed on the same server. But this may lead to
performance problems, as the MapBox needs high amounts of memory.
© 2007 SAP AG
GWConnector and Exchange Server should not be installed on the same server for
performance reasons
Outlook 2003 contains CDO by default, you do not have to install it separately
Several clients can be added to one MapBox; but: for one GWConnector, only one CRM
System can be connected.
There cannot be 2 installations of MapBox listening to the same CRM client. Also MapBox is a
non-clustered application and hence a clustered J2EE Engine is not supported.
Performance and Hardware Requirements

Hardware Requirements of GWConnector
Hardware requirements actually depend on the number of users on the Groupware Server and the
amount of changes to be replicated.
The operational minimum requirements are:
Component Description
Processor Intel PIII 600 MHz or higher
Minimum RAM 256 MB
Minimum Disk Space 100 MB
Display Mode 640x480x16 or better
Result of performance testing shows that following hardware is required to serve 1000 to 1500 users:
Processor Intel P4 2 GHz
Minimum RAM 512 MB
Minimum Disk Space 100 MB
Performance of the connector scales linearly – one box with 4 * Intel P4 2 GHz and 2G of memory will
be able to serve about 5000 to 6000 users.
Note: all performance estimations are relevant to Groupware Connectors operating in Local
Area Network environment.
Note: Groupware Connector may share the same box with relevant Groupware Server if the
box has some performance and memory reserve. Use numbers above to check if there
is enough free resources for amount of users to be served.
Network Bandwidth Requirements

There are different options of installing Groupware Connector
Install one instance of Groupware Connector for the entire organization. This will require
high-speed low latency connectivity between Connector and all target Groupware Servers.
Minimum of 512Kbps is required.
© 2007 SAP AG
Below is the short table with the results of the performance benchmark in the real-life
environment (with only one worker running):
Avg. Avg. % Link

WAN Link
Msg/Sec KBps Bandwidth
Location1: 512.0 kbits/s - frame-relay (32) 0.43 12.32 24.05%

Location2: 512.0 kbits/s - frame-relay (32) 0.59 16.77 32.74%
Location3: LAN 2.65 75.09 0.75%
Location4: 1024 kbits/s - softwareLoopback (24) 0.19 5.31 5.18%
Location5: 1024 kbits/s - softwareLoopback (24) 0.15 4.15 4.05%
where average traffic is the traffic between Groupware Connector and Groupware
Server over WAN link.
Install one instance of the Groupware Connector per LAN where Groupware Server is
located. This solution will eliminate huge network traffic between Groupware Connector and
Groupware Server and will strongly improve the performance of the whole solution in a
distributed environment.
The result of performance measurement shows that performance of about 1 message per 2
seconds can be achieved over one 56Kbpps effective bandwidth line.
Note: this option is not available in SP03 release.
Hardware Requirements of the MapBox

Concerning the minimum hardware requirements of the Mapbox, review the following table:
Processor Intel PIII 600 MHz or higher
Minimum RAM 1024 MB
Minimum Disk Space 1 GB
For more info on performance and scalability, refer to the Release Notes document on the path
<\\inblr102\sapall\common\crm\gwi\mapbox\Release Notes>
Recommended support packages/ patch levels
See below the recommended ideal system landscape for a GWI scenario:
Regarding the MapBox, the latest support package level (currently SP12) is recommended by
development. MapBox SP 9 contains essential performance improvements; SPs 11/12
support the automatic the automatic restart of the MapBox on a J2EE restart.
Concerning the J2EE, the latest version is also recommended (currently J2EE version 700).
GWConnector SP 10 should not be used for public folder synchronization Please refer to
note 935267.
© 2007 SAP AG
If the public folder synchronization is not going to be used however, the Installation of
GWConnector SP10 has the following advantage:
In SPs smaller than SP10, a public folder name for installation is required. In SP 10, this is not
the case any more. This fastens the installation process.
MapBox, GWConnector and CRM system can have different SP-levels; they are independent
of each other.
GWConnector proxy recommendations

Integration Landscape
Overall performance of the entire solution greatly depends on the configured landscape. This is
particularly important for largely distributed organizations. The performance will be optimized if Proxy
instances never talk to remote Groupware servers, that is, the Groupware Connector Proxy should be
in a LAN with the Groupware Server.
The following diagram describes right and wrong approaches for build Groupware Connector’s
landscape.
© 2007 SAP AG
The following options can be considered to select the best solution:

Minimum required bandwidth between Groupware Connector and Remote Proxy
instance is 128kbps.
Minimum required bandwidth between Groupware Connector Proxy and remove
Groupware Server is 1Mbps. (This is the case for the simplest configuration).
When using Remote Proxy in comparison to setting up the Proxy to deal with remote
Groupware Servers …
Network utilization is about 5 times less during CRM => Groupware replication.
Performance of Groupware => CRM replication can be up to 100 times faster
(depending on WAN bandwidth) because Remote Proxy will not utilize the network
while detecting the changes..
Further Information
Important Notes
General GWI Notes
753300 Groupware integration – Creation, Deletion & Reminder fixes
834041 Groupware Integration – additional field mapping
908571 Groupware Integration Solution Notes: provides an overview over all notes related to
server based groupware integration
908572 Private Folder Synchronization CRM->Groupware
908577 Groupware Integration TroubleShooting Guide
908579 Groupware Integration FAQs
934841 CRM Groupware Integration Field Mappings.
938591 Known Limitations with Server Side CRM Groupware Integration.
Groupware Connector Notes

843407 SAP CRM GW connector ver 2.1 bug fixes and enhancements
935267 SAP CRM GW Connector ver 2.1 SP10 upgradation problem
957409 Groupware Exchange Connector TroubleShooting Guide
Components: EP-KM-GW* or EP-KM-CRM-EXC

CRM-MW-GWI-GWE and CRM-MW-GWI-GWD
MapBox Notes
693065 Security Recommendation for MapBox Configuration
690162 Change in signature of function module ISP_MAPBOX_2
710346 Upload and Download of Map Scenarios
776448 Patch Installation of CRM non-ABAP components
817787 MapBox Troubleshooting Guide
899930 Indexing MBMANDTSTORE for better performance
900431 ISP_S* queue fails with error parsing XML
© 2007 SAP AG
905063 Background Job to activate ISP* INBOUND queues for MapBox

852027 MapBox related Notes
906739 GRMG cannot be configured for MapBox
Component: CRM-MW-MBX and CRM-MW-SYP
GWI Application Notes

959294 Groupware Adapter Customizing and User Guide
983436 Groupware Integration:Filtering on UserList.xml file
870955 Groupware Integration-256 character Subject mapping.
935129 Groupware Integration: Deletion and Updation of UserList.xml.
904876 Supported Recurring Appointments from Groupware to WFM.
905363 Yearly Recurring Appointments MapCase Exception.
887203 Groupware WFM Integration. Updating Recurring All Day
Appointments.
903070 ISP_O * queue in NOSEND status for notification.
919687 Task Synchronization from CRM to Groupware.
935930 Synchronizing Activity Dates in the Past.
Component: CRM-MW-GWI*
Knowledge Documents
For GWI related documents, you can refer the following sections:
1) To configure Groupware Adapter:

In http://help.sap.com => Search Documentation. Under SAP Business Suite,
search for the “Groupware Integration Setup and Load Guide”.
Newer versions of this documentation are currently available in the SAP Service Marketplace:
CRM 4.0:
http://service.sap.com/instguides SAP Business Suite Solutions SAP CRM SAP CRM 4.0
General and Technical Installation Guides
CRM 5.0:
http://service.sap.com/instguides SAP Business Suite Solutions SAP CRM SAP CRM 2005
CRM Core and Standalone Components
2) In http://service.sap.com/instguides under the section SAP Business Suite Solutions->SAP CRM-

>SAP CRM 4.0->General and Technical Installation Guides
a) MapBox 4.0 SP09 (or higher)

b) SAP Groupware Connector 2.1 - Installation
c) SAP Groupware Connector 2.1 - Administration
© 2007 SAP AG
© 2007 SAP AG
© Copyright 2007 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,
pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or
registered trademarks of IBM Corporation.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented
by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries
all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data
contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted
in any form or for any purpose without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This
document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be
binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document
is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness
of the information, text, graphics, links, or other items contained within this material. This document is provided without a
warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness
for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential
damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that
you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web
pages nor provide any warranty whatsoever relating to third-party Web pages.
© 2007 SAP AG

What Is Groupware

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

What Is Groupware

Caricato da

Copyright:

Formati disponibili

Solution Management SAP Solution Topic Area Solution Manager

Version Date: January 2007

Different GWI Technologies

In a client-to-client based synchronization, an application is implemented on a Mobile Client.

In a server-to-server based synchronization business objects are synchronized between a CRM

A user of groupware solutions normally performs the following tasks:

The following business scenarios can be used with Groupware Integration:

Business Partner Management

Public folder synchronization (GWA01)

Private folder synchronization (GWA02)

Workforce Management (People/Resources Planning)

Log Settings in the MapBox Launcher

b) The MapBox Repository (also known as the MapStore)

e) The Internal SyncPoint

MBMANDTSTORE contains data of type d (MapData). If customizing is downloaded, it is stored in this

Furthermore, MBMANDTSTORE stores the relationship between a BPGUID and an email-address. If an

Copy GUID into field S_MBKEY, double-click

Data Exchange in the Groupware Integration system

Mapbox iCal / vCard

GW connector pulls the

Queues used for the data exchange

Data flow direction CRM => Groupware

There are two kinds of ISP_D* queues:

Benchmarks for data processing

Limitations for the GWConnector

Excursus: Impact of the UserList

For further information, also refer to SAP note 935129.

Most Common Problems

The possible causes of the errors mentioned above are:

Problems related to GWConnector

Verifying Connection to the Payload Interface

Resolving Payload Interface errors

Code Short Description

3 Queue does not exist

5 Session ID not known

7 Property not known

8 Feature not implemented

10 No more messages available

11 Operation not allowed

Verifying Connection to the MS Exchange Server

You will require MS Outlook to be installed.

Using Diagnostics Tool (Lotus Connector)

Problems related to GWI application

Settings Related to the MapBox

Recommended memory settings for the MapBox

How do I set the recommended memory settings for the MapBox?

cmdline.properties present at the location

c) If you use the go.bat file present at the location

SAP J2EE Engine 6.40 / SAP Web AS Java 7.00

Recommendations concerning the system landscape

Performance and Hardware Requirements

Network Bandwidth Requirements

Avg. Avg. % Link

Location1: 512.0 kbits/s - frame-relay (32) 0.43 12.32 24.05%

Hardware Requirements of the MapBox

Recommended support packages/ patch levels

GWConnector proxy recommendations

The following options can be considered to select the best solution:

Groupware Connector Notes

Components: EP-KM-GW* or EP-KM-CRM-EXC

905063 Background Job to activate ISP* INBOUND queues for MapBox

Component: CRM-MW-MBX and CRM-MW-SYP