D58_BB_ConfigGuide_EN_UK

SAP CRM 4.0

July 2004

English

D58 - Groupware Integration in Project Resource Planning

SAP AGNeurottstr. 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best PracticesD58 - Groupware Integration in Project Resource Planning: Configuration Guide

Copyright

© Copyright 2004 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 in the United States and/or other countries.

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, 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.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG Page 2 of 25


Icons

Icon Meaning

Caution

Example

Note or Tip

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Contents

Groupware Integration in Project Resource Planning: Configuration Guide...................................6

1 Purpose................................................................................................................................... 6

2 Preparation.............................................................................................................................. 7

2.1 Prerequisites..................................................................................................................7

2.2 Uploading the Installation Role......................................................................................8

2.3 Installing the Java Virtual Machine................................................................................8

2.4 Installing the Microsoft® SOAP ToolKit.........................................................................8

2.5 Installing the SAP J2EE Engine.....................................................................................9

2.6 Installing the Software Delivery Manager......................................................................9

2.7 Installing the SAP Java Connector *)...........................................................................10

2.8 Installing the Microsoft® Outlook 2000........................................................................10

2.9 Installing the MapBox..................................................................................................11

2.9.1 Install MapBox.........................................................................................................11

2.9.2 Create User.............................................................................................................12

2.9.3 Create RFC-Destination..........................................................................................13

2.9.4 Edit MapBox Server................................................................................................14

2.9.5 Starting and Stopping the MapBox..........................................................................14

2.10 Installing the SAP Groupware Connector....................................................................15

2.10.1 Getting the Required Parameters for the Groupware Adapter.................................15

2.10.2 Defining User in Microsoft Exchange 2000..............................................................16

2.10.3 Creating a Public Folder to Store SAP CRM Contacts............................................17

2.10.4 The 1st use of MS Outlook 2000..............................................................................17

2.10.5 Using the Contacts Folder in the MS Outlook Address Book..................................18

2.10.6 Install SAP Groupware Connector...........................................................................19

2.11 Troubleshooting...........................................................................................................19

3 Configuration......................................................................................................................... 20

3.1 Internal SyncPoint.......................................................................................................20

3.1.1 Define RFC Destination for the MapBox..................................................................20

3.1.2 Define Internal SyncPoint Settings..........................................................................20

3.1.2.1 Enter MapBox RFC Destination in Configuration Table..................................20

3.1.2.2 Limit the Number of Processing Retries..........................................................20

3.1.2.3 Define Session Timeout for Payload Interface................................................21

3.1.3 Delete Timed Out Sessions from Status Table........................................................21

3.2 Creating SAP CRM Sites and Subscriptions...............................................................22

3.2.1 Creating Site IDs for Groupware Adapter................................................................22



3.2.2 Creating Subscriptions for Groupware Adapter.......................................................23

3.2.3 Register Inbound Queues for WFM Groupware Integration....................................24

3.2.4 Specifies Number Ranges for Categories for WFM Groupware Objects.................24

3.3 Setting Configuration Parameters for the Groupware Connector................................25



Groupware Integration in Project Resource Planning: Configuration Guide

1 PurposeThis configuration guide provides the information you need to set up the configuration of this building block manually.

If you do not want to configure manually and prefer an automated installation process using BC Sets and other tools, refer to the installation guide of this building block.

This guide describes the installation of the SAP Groupware Integration on a Microsoft Windows 2000 Advanced Server. All components are installed on one machine. In this scenario are Microsoft Exchange Server and SAP CRM 4.0 used.

For other operating systems or landscape’s have a look to the SAP Marketplace http://service.sap.com (alias: PLATFORMS) or in the appropriate installation guides of the used products.

The following picture shows the system landscape of this SAP Best Practices Building Block:

*) The installation or configuration process of this product is not described in this guide!

System prerequisites for the Groupware ServerHardware Requirements:

Component Description

Processor Intel PIII 600MHz (or better)

RAM 1 GB

HDD min. 300 MB free disk space

Software Requirements:

Component Description

Groupware Server Microsoft Exchange 2000 (on a separate Server)

CRM System mySAP CRM 4.0 (on a separate server)


MS Exchange 2000 *) Groupware Integration SAP CRM 4.0 *)

Groupware Adapter

SAP Exchange Connector

J2EE

MS Outlook

MS SOAP

JCo JDK

http://service.sap.com/


Operating System Microsoft Windows 2000 Advanced Server

Java Virtual Machine Java(TM) 2 SDK, Standard Edition v.1.3.1_09

Collaboration Data Objects CDO 1.2.1

is available with:Microsoft Exchange 2000Microsoft Outlook 98Microsoft Outlook 2000

Using Microsoft Outlook 2000 you need to add CDO 1.2.1 as a custom installation option because it is not part of the general installation. It is mandatory to install MS Outlook as the default mail client.

Simple Objects Access Protocol Microsoft SOAP Toolkit 2.0

Internet Browser Microsoft Internet Explorer 5.5 (or higher)

Java Connector SAP JCo 2.0 (PL 10)

J2EE SAP J2EE Engine 6.20 (PL 20)

Java Software Logistic SAP SDM (PL 13)

SyncPoint MapBox 4.0

SAP Groupware Connector 4.0 (PL 1)

2 Preparation

2.1 Prerequisites

!! This Building Block is only suitable for NON-UNICODE Systems.

For actual information regarding availability of groupware integration in a

UNICODE environment check note 753645 !!

Before using this building block, you need to install the following building blocks:

Building Block Description

D62 CRM Connectivity and Replication for Prov. Services



If you want to use this building block, install the following SAP Notes in your SAP CRM System:

SAP Note Description Component

693065 Security Recommendation for MapBox Configuration file CRM-MW-MBX

2.2 Uploading the Installation Role

Use

If you reference this Guide in one of the scenarios you can ignore this step. The role is already installed.

Before you start with the installation using the automated procedures described in this installation guide, upload the installation role and assign it to your user. If you prefer to carry out some of the steps manually, refer to the configuration guide of this building block.

This building block provides one or more installation roles, which enable you to access all the transactions required for the installation from the relevant system. The following roles are available for this building block:

Technical name Description File name for upload

/SMB23/D58_01ID58: Groupware Integration in Project Resource Planning (CRM)

_SMB23_D58_01I.SAP

ProcedureFor details on how to upload the installation roles to the system and how to work with the roles, refer to the document Essential Information.

2.3 Installing the Java Virtual MachineDownload and install the Java Virtual Machine (JVM) with support for J2SE 1.3.1 and JDK 1.3.1, from http://java.sun.com/products/archive/j2se/1.3.1_09. Create an environment variable named JAVA_HOME with the value of your installation path of the JVM (e.g. <jdk-install-path>) and expand your Path variable with the value of the path to the file ‘java.exe’ (<jdk-install-path>\bin).

You must restart your computer after this installation.

2.4 Installing the Microsoft® SOAP ToolKitDownload the Microsoft® SOAP Toolkit 2.0 from the Microsoft Homepage and do a double-click on the downloaded file (SoapToolkit20.exe) follow the instructions to install this kit: http://download.microsoft.com/download/xml/soap/2.0/W98NT42KMe/EN-US/SoapToolkit20.exe


http://download.microsoft.com/download/xml/soap/2.0/W98NT42KMe/EN-US/SoapToolkit20.exe

http://onesearch.sun.com/ClickThru?qt=1.3.1_09&url=http%3A%2F%2Fjava.sun.com%2Fproducts%2Farchive%2Fj2se%2F1.3.1_09%2F&pathInfo=%2Fsearch%2Fdevelopers%2Findex.jsp&hitNum=1&col=javatecharticles&col=javasc&col=javatutorials&col=devall&col=devarch


2.5 Installing the SAP J2EE EngineDownload the SAP J2EE Engine 6.20 from SAP Service Marketplace http://service.sap.com (alias: PATCHES). Navigate to SAP WEB AS SAP WEB AS 6.20 Binary Patches SAP J2EE Engine 6.20 OS independent SAPJ2EE620C_20-10001433.SAR.

Procedure1. Unzip the downloaded file with the SAP tool sapcar.exe.

2. Start the install process by executes <unzip-path>\visual.bat.

On the Welcome screen click on Next.

Enter your name and company and then click Next.

Insert the Destination directory <j2ee-install-path> and click on Next.

Enter a Program Folder and click Next.

Leave the Select components to install unchanged and click on button Next.

If necessary, increase the Maximum JAVA heap size, verify that the displayed JavaVM (JDK) Path is correct and then click on Next.

On the screen Total Info click on Start to begin the installation.

Mark Run Config Tool and to finish the installation click on Exit

The SAP J2EE Engine Config Tool window appears.

3. Highlight in the left frame cluster\dispatcher and mark in the right frame checkbox Enabled, do the same for entry cluster\server.

4. Save your entries with button (Apply changes).

5. Close the SAP J2EE Config tool with File Exit.

6. Open a Command Prompt and change to <j2ee-install-path>\configtool.

7. Execute service.exe –install.

2.6 Installing the Software Delivery ManagerDownload the Software Delivery Manager (SDM) from SAP Service Marketplace http://service.sap.com (alias: PATCHES). Navigate to SAP WEB AS -> SAP WEB AS 6.20 Binary Patches SAP Java SL 6.20 OS independent SDMKIT_13-10001735.JAR.

Procedure1. Open a Command Prompt and change into a valid directory, in that the downloaded file will

be extracted.

2. Unpack the file with the command ‘jar xvf <download directory>\<file>’.

3. Execute the file <sdm-unzip-path>\install.bat and do the required entries:

SDM installation directory <sdm-install-path>

SDM component directory <sdm-install-path>\comp_root

Port for GUI-Communication 50017





Port for Admin-Communication 50018

Port for HTTP-Communication 50019

Inst-Dir von Java Virtual Machine <jdk-install-path>

Point of Presence of SDM-files <sdm-unzip-path>

4. Start the SDM, therefore execute startSDM.bat in the <sdm-install-path>.

5. Mark in the left frame the entry Server and complete the required entries in the Configuration tab.

7. Save your entries by clicking on button (Save Repository).

8. Close the SDM.

2.7 Installing the SAP Java ConnectorDownload and install the SAP Java Connector (JCo) from SAP Service Marketplace http://service.sap.com (alias: PATCHES). Navigate to SAP WEB AS SAP WEB AS 6.20 Binary Patches SAP JCO 2.0 <your OS> JCO20_10-10001362.ZIP.

Procedure1. Unzip the file JCO20_10-10001362.ZIP into an arbitrary directory <sapjco-install-

path>.

2. If you already have an older librfc32.dll in the C:\WINNT\system32 directory, replace it with the one that comes with JCo.

3. Add <sapjco-install-path> to the PATH environment variable.

4. Finally, add <sapjco-install-path>\sapjco.jar to your CLASSPATH environment variable

5. For further information about the installation process or SAP JCo refer to the file <sapjco-install-path>\docs\jco\intro.html.

6. Copy the files sapjcorfc.dll and sapjco.jar from the <sapjco-install-path> to <j2ee-install-path>\cluster\server\additional-lib.

7. Register the librfc32.dll with command regsvr32“C:\WINNT\system32\librfc32.dll”.

To apply these changes reboot your server!

2.8 Installing the Microsoft® Outlook 2000

ProcedureInsert your Microsoft Office CD and follow the instructions to install Microsoft Outlook 2000.

Enter your customer information’s and then click Next.




In the following window click on Customize....

Enter a installation directory and click on Next.

in the window Microsoft Office 2000: Selecting Features select your choice and additionally expand the entry Microsoft Outlook for Windows and mark the entry Collaboration Data Objects with the option Run from My Computer

Click on Install Now

After the installation, finish the Microsoft Office Installer.

2.9 Installing the MapBox

2.9.1 Install MapBoxDeploy the following files with the SDM kit (in the order of mentioned below):

You can find these files on the CD CRM 4.0 Component CD 2, or in the SAP Service Marketplace http://service.sap.com, alias: PATCHES. Navigate to SAP CRM -> SAP CRM 4.0 Binary Patches MAPBOX 4.0 Win32 MAPBOX04_0-10002068.SCA

SAPXMLToolkit.sda

For this SDA you have to configure 2 additional parameters “Default-Directory for the Deployment” and “Directory for Deployment” before you can deploy it.

CoordServer.sda




MapBox.sda

You have to copy the file <deploy directory>\smoketest\coordserver.cfg to <j2ee-install-path>\cluster\server.

CoordLauncher.sda

After deploying CoordLauncher.sda you have to copy the file connection.xml (this file is located in the directory <installation path of smoketest>) to path C:\mw\j2ee_mapboxlauncher\connection.xml (you have to create these directories manually).

MapBoxLauncher.sda

Procedure1. Make sure that your J2EE-Engine is started, the services “SAP J2EE Engine Dispatcher” and

“SAP J2EE Engine Server” have to be started.

2. Run startSDM.bat from the <sdm-install-path> directory.

3. Mark the entry Server in the left frame.

4. In the SAP Software Delivery Manager click on tab Deployment.

5. Click on button (Add SCA/SWC/SDA to Deployment List) and switch to the directory where the SDA are located, add an archive by marking it and clicking on Choose and then Next.

6. In the left frame mark the SDA click on Next.

7. Click Next.

8. Click Start.

9. After successfully deploying click on button Confirm.

10. Do steps 3 to 9 for all SDA's in the order mentioned above.

2.9.2 Create User

UseFor the connection to the MapBox create a user in the CRM system in the corresponding client.

Procedure1. Access the activity using one of the following navigation options:

SAP CRM User Maintenance

Transaction Code SU01

SAP Menu Architecture and Technology System Administration User Maintenance User



2. In the User field enter MAPBOX and choose Create.

3. On tab Address fill in the following fields:

Title: Mr.

Last Name: MapBox

Function: RFC-User for MapBox

On tab Logon data fill in the following fields:

Initial password: login

Repeat password: login

User Type: Service (check radio button)

On tab Defaults fill in the following field:

Logon Language: EN

On tab Profiles add the following profiles:

SAP_ALL

SAP_NEW

4. Save your entries.

2.9.3 Create RFC-Destination

UseFor the connection to/from the MapBox you will need a RFC destination.


SAP CRM Display and maintain RFC destinations

Transaction Code SM59

SAP Menu Architecture and Technology System Administration Network RFC Destinations

2. Click on button Create.

3. In the following screen fill in the fields:

RFC Destination: MAPBOXSMB23

Connection Type: T

Description: Connection to the MapBox

4. Press Enter

5. On tab Technical settings activate Registered Server Program and in the field Program ID enter the value MAPBOXSMB23.



6. Enter the details of the Gateway Host (your SAP CRM server) and Gateway Service (Gateway port number of the CRM, e.g. sapgw00).


2.9.4 Edit MapBox Server1. Connect and Logon to your MapBox Server (e.g. VNC, Terminal Service or pcAnywhere).

2. Edit the files connection.xml on your MapBox server with the data you have inserted/created below. The sections are:

<JCO msg_sys=”<message server CRM>” sap_system=”<SID>” sap_gateway=”<SAP Gateway Port>” sap_grpname=”<Logon Group>” TraceLevel=”2”/>

and<connection_parameters>

<connection_def><!—logon-settings, like number of instances, the client <logon client=”<CLIENT>” user=”MAPBOX” password=”login”

language=”EN” destination=”MAPBOXSMB23”/>


2.9.5 Starting and Stopping the MapBox

Make sure, that the service sapms<CRM-SID> is known in the file C:\WINNT\system32\drivers\etc\services!

Shutting down the SAP J2EE EngineTo shutdown the J2EE 620 at any point of time after the deployment process, follow the steps given below:

1. Go to <j2ee-install-path>\admin\go.bat. The SAP J2EE 620 Administrator is invoked.

2. From the menu choose Connect Login

3. Choose Connect to continue.

4. Go to Server One Services and then choose deploy.

5. Select the Application radio button. The list of deployed components appears.

6. Select MapBoxLauncher and then choose Stop Application.

7. Select CoordLauncher and then choose Stop Application. Both services are now stopped.

8. Close the SAP J2EE 620 Administrator.

9. Run <j2ee-install-path>\tools\shutdown.bat.

10. Stop the services SAP J2EE Engine Server and SAP J2EE Engine Dispatcher in the Service Manager of Windows.

Starting the SAP J2EE Engine



1. Call the Service Manager and start the services SAP J2EE Engine Dispatcher and SAP J2EE Engine Server

2. Go to <j2ee-install-path>\admin\go.bat. The SAP J2EE 620 Administrator is invoked.

3. From the menu choose Connect Login

4. Choose Connect to continue.

5. Go to Server One Services and then choose deploy.

6. Select the Application radio button. The list of deployed components appears.

7. Select CoordLauncher and then choose Start Application.

8. Select MapBoxLauncher and then choose Start Application. Both services are now started.

9. Close the SAP J2EE 620 Administrator.

You must restart the applications using the SAP J2EE 620 Administrator!

You can have a look to the currently used parameters when you start the MS Internet Explorer and call URL http://localhost/MapBoxLauncher/MBLaunchPad

2.10 Installing the SAP Groupware ConnectorDownload and install the SAP Groupware Connector from SAP Service Marketplace http://service.sap.com (alias: PATCHES). Navigate to SAP CRM SAP CRM 4.0 Binary Patches SAP Groupware Connector 4.0 Win32 SAPGRPWCN04P_1-10002067.ZIP.

2.10.1 Getting the Required Parameters for the Groupware Adapter

Procedure1. Determine the URL for the SOAP request.

a. Access the activity using one of the following navigation options:

SAP CRM ICM Monitor

Transaction Code SMICM

SAP Menu Architecture and Technology System Administration Monitor System Monitoring Internet Communication Manager

b. Choose Goto Services

c. Note the entries for Host Name and Service name/Port from the line beginning with protocol HTTP (e.g. my_sap_1:50000).

2. Determine the Relative Path of the SOAP Listener.


https://websmp105.sap-ag.de:/~SAPDOWNLOAD/011000358700000570202004D/SAPGRPWCN04P_1-10002067.ZIP

http://localhost/MapBoxLauncher/MBLaunchPad


a. Access the activity using one of the following navigation options:

SAP CRM HTTP Service Hierarchy Maintenance

Transaction Code SICF

SAP Menu Architecture and Technology System Administration Administration Network HTTP Service Hierarchy Maintenance

b. Expand the tree to locate the soap node (usually found under default_host sap bc soap rfc).

ResultYou will get the complete URL HTTP://<Host Name>:<Service Name/Port>/<SICF-Tree> (e.g. http://my_sap_1:50000/sap/bc/soap/rfc).

2.10.2 Defining User in Microsoft Exchange 2000

UseThe SAP CRM Groupware Connector is created as a Windows service and runs under some Windows user account specified for this service. The Exchange mailbox alias for the user can differ from the Windows user name.

PrerequisitesThe installation must be performed under the user account that is used for running the SAP CRM Exchange Connector Service.

If you use an existing NT user account for the installation, the appropriate administrative rights must be applied. Refer to the steps 2 to 4 below.

The user must not belong to NT Domain administrators.

The mailbox alias used in the installation settings is recommended to correspond to the same user.

Procedure…

1. To define the target MS Exchange administrative account, choose Start Programs Administration Tools Active Directory Users and Computers.

2. Check whether the Groupware administrative account exists.

3. If not, create an account by using create a new user in the current container button.

4. In the left window of the Exchange System Manager locate the node that represents your Exchange server. Open the nodes following the path: First Organization Name Servers.

5. Select the target server and right-click on it.

6. From the context menu, choose Properties and then choose the Security tab.

7. Add the NT user account that was used as the Exchange Connector administrative account (See Step 3).

8. Provide all possible permissions by selecting Allow and choose OK.


http://my_sap_1:50000/sap/bc/soap/rfc


2.10.3 Creating a Public Folder to Store SAP CRM Contacts

UseYou must create a public folder to store contacts (business partners) and assign the same to a valid Email address.

Procedure1. Logon to your MS Outlook with the User you have created for the connection to the Exchange

server.

2. Choose File New Folder…

3. In the following window enter in field Name: your description for this new folder.

4. Choose from the Folder contains:-dropdown list Contact Items.

5. In the box Select where to place the folder: select Public Folders All Public Folders, then click OK.

6. Do a right click on the newly created folder and select Properties.

7. In the tab Permissions select your user and under Roles select Editor, then click OK.

8. Start the MS Exchange Administrator.

9. Select the folder you created.

10. In the action menu, select Properties.

Make a note of the SMTP address of the public folder. You will be required to enter it during the installation process.

11. Close the Exchange Administrator.

2.10.4 The 1st use of MS Outlook 2000

Procedure1. Logon to the SAP Groupware server with the created user.

This user must have administrator rights on this machine.

2. Double click on the icon on your desktop

3. In the window Outlook 2000Startup click on Next.

4. In the next window check radio button Corporate or Workgroup and click Next.

5. In the following screen mark Microsoft Exchange Server under the section Use the following information services and click Next.



6. Enter the name of your Microsoft Exchange server and the Mailbox of the user which was created earlier.

7. Click on Finish.

Register Outlook as your default mail client!

2.10.5 Using the Contacts Folder in the MS Outlook Address Book

UseIt is possible to use the Exchange Contacts folder as a part of the Address Book in Microsoft Outlook. For more information, see Microsoft Outlook Help

Procedure…

1. To enable the Service, add an Outlook Address Book to a user profile.

a. On the Tools menu, select Services.

b. On the Services tab, choose Add.

c. In the Available information services list, select Outlook Address Book.

d. Choose OK twice.

Quit and restart Outlook.

Only entries in the Contacts folder that are setup to appear in the Outlook Address Book are displayed in the Address Book dialog box.

2. Set up the Contacts folder to be displayed in the Address Book dialog box.

a. If the Folder List is not visible, from the View menu, select Folder List.

b. Select the Contacts folder you want to display in the Address Book dialog box.

c. In the File menu, select Folder, then Properties for <folder name>, and then select the Outlook Address Book tab.

d. Select the Show this folder as an e-mail Address Book check box.

In the Name of the address book box, enter the name for the Contacts folder you want to display in the Show names from the box in the Address Book dialog box.

A contact must have an entry in the Email or fax phone number field to appear in the Outlook Address Book.

2.10.6 Install SAP Groupware Connector

Procedure



1. Unzip the downloaded file SAPGRPWCN04P_1-10002067.ZIP to <gw-download-path> (as described in chapter 2.10)

2. Run program <gw-download-path>\Setup.exe.

3. On the Welcome screen click Next.

4. After you have read the installation prerequisites click on Next.

5. Select MS Exchange Groupware Connector and click Next.

6. Choose a destination folder and click Next.

7. Insert the required logon information’s and click Next. The Language must be EN!

8. Fill in the parameters for the connection to the Exchange server and click Next.

9. Enter an e-mail address of your Public Folder for SAP CRM Contacts and click Next.

10. Click Next.

11. Click Finish.

2.11 TroubleshootingSAP OSS Notes Description Component

615146 MapBox – installed base- no data exchange possible CRM-MW-SYP

701875Mapbox raises Mapcase Exception with NoClassDefFoundError

CRM-MW-GWI-GWA

702989 Failure of replication of BUPA into Public Folder CRM-MW-GWI-GWE

660377 ‘CALL_METHOD’ error in IC WebClient CRM-IC-FRW

634689 Central Note for Memory Issues, SAP J2EE Engine 6.20 BC-JAS-COR

558250 Memory problems with J2EE and the SAP Java Connector BC-MID-CON-JCO

Notes especially for UNICODE!

718545 Groupware Integration - Unicode CRM system handling CRM-MW-SYP

636912 Frequent installation problems with SAP Java Connector BC-MID-CON-JCO

723562 SAP Java Connector: Configuration and Requirements BC-MID-CON-JCO

753645 SAP Best Practices for Professional Services V2.470 SV-SMB-AIO-BP-ASP



3 Configuration

3.1 Internal SyncPoint

3.1.1 Define RFC Destination for the MapBox

UseYou must create an RFC destination for the MapBox that is a mapping engine and a component of SyncPoint. MapBox reduces the amount of data transferred from the CRM Server and enriches incoming data for processing in the back-end systems. In addition, it supports devices with their individual data representations.

Mostly done with point 2.9.3

3.1.2 Define Internal SyncPoint Settings

Use

You must define parameter values for RFC communication for the MapBox, the maximum number of message processing attempts (in case of an error), and a timeout value for the Payload Interface session.

Access the activity using one of the following navigation options:

Transaction Code SPRO

IMG Menu SAP Implementation Guide Customer Relationship Management CRM Middleware and Related Components Internal SyncPoint Define Internal SyncPoint Settings

3.1.2.1 Enter MapBox RFC Destination in Configuration TableTo call the MapBox you must enter the name of the RFC destination you created.

On the screen Change View ISP Configuration: Mapbox RFC Destination make the following entries:

Parameter Name Description Value Note

MAPBOX_RFC_DESTINATION MAPBOXSMB23

3.1.2.2 Limit the Number of Processing RetriesYou may enter a limit for the number of retries that are performed when the processing of any message results in a temporary error. The time interval between two attempts is determined by



the qRFC Inbound Queue scheduler. If the error condition persists even after the maximum number of retries, a fatal error will be raised. A temporary error may occur if, for example, the data that the MapBox needs to complete the mapping is not available.

On the screen Change View ISP Configuration: Max. Retries of temporary Errors make the following entries:

Parameter Name Description Values Note

MAX_RETRIES 5

3.1.2.3 Define Session Timeout for Payload InterfaceYou may enter a default value (specified in seconds) for the inactivity timeout for any session of the Payload Interface. After the session is established, the client application may override this value. If a session is inactive (no methods of the Payload interface are invoked) for a longer time than specified, the session handle is timed out and therefore invalid.

On the screen Change View ISP Configuration: Payload IF – Session timeout make the following entries:

Parameter Name Description Values Note

PIF_TIMEOUT 300

3.1.3 Delete Timed Out Sessions from Status Table

Use The session details of the Payload Interface are recorded in a status table. To prevent this table from increasing in size, timed out sessions must be deleted at regular intervals.

Procedure 1. Access the activity using one of the following navigation options:

Transaction Code SPRO SM36

IMG Menu SAP Implementation Guide Customer Relationship Management CRM Middleware and Related Components Internal SyncPoint Delete Timed Out Sessions from Status Table

2. Create a background job and schedule it periodically.

3. On the screen Define Background Job make the following sets of entries:

Field name Value Note

Job name SMB23_CMW_PIF_SESSIONMANAGER

Job class C

Exec. Target <empty>

4. Click on button Step (Define Steps (F6)).



5. On the screen Define Background Job make the following sets of entries:


User SAP* make sure that user exists

ABAP Program Choose Button ABAP Program

Name CMW_PIF_SESSIONMANAGER

Variant <empty>

Language EN

6. Choose Save.

7. Click on Start Condition (Specify start condition (F5)).

8. On the screen Start Time choose Button Immediate.

9. Activate checkbox Periodic Job.

10. Choose Button Periodic values.

11. On the screen Periodic Values, choose Daily and press Save.

12. On screen Start Time choose Save.

13. Save the created job on screen Define Background Job with button Save (Ctrl+S).

Verification1. Access the activity using one of the following navigation options:

Transaction Code SM37

2. On the screen Simple Job Selection make the following sets of entries:


Job Name SMB23_CMW_PIF_SESSIONMANAGER

User Name *

From … To enter a valid period

3. Click on Execute (Execute (F8)).

4. In the Job Overview of all users the created job is displayed with status “Released”.

3.2 Creating SAP CRM Sites and Subscriptions

3.2.1 Creating Site IDs for Groupware Adapter

Procedure 1. Access the activity using one of the following navigation options:

SAP CRM Creating Site for the Groupware Adapter



Transaction Code SMOEAC

SAP Menu Architecture and Technology Middleware Administration Administration Console

2. In the Object Type field in the left screen area, choose Site.

3. Choose Create Object.

4. In the Object information: Site screen area, enter the name GWA_01 and the description Groupware_01 and choose the site type Groupware Adapter 01 (mBDoc).

You have to create a second site with name GWA_02 and description Groupware_02.

5. For this special Site Type you do not have to maintain Site Attributes.

6. Choose Save.

3.2.2 Creating Subscriptions for Groupware Adapter

UseAfter the definition of the GWA site you create subscriptions using the subscription wizard.


SAP CRM Creating Subscriptions for Groupware Adapter

Transaction Code SMOEAC

SAP Menu Middleware Administration Administration Console

2. In the Object type field enter Subscriptions.

3. Choose the Create icon.

4. Follow the subscription wizard instructions.

5. Using the subscription wizard, create two subscriptions:

Subscription WFM Groupware Integration Customizing (MESG)

Publication WFM Groupware Integration Customizing (MESG)

Subscription WFM Groupware Integration WFM->GW

Publication WFM Groupware Integration (MESG)

Criteria values

Value Low WFM

6. Assign these subscriptions to your newly created /SMB23/GWA_01 and /SMB23/GWA_02 sites.



Refer to the Administration Console documentation for further information on how to create subscriptions.

3.2.3 Register Inbound Queues for WFM Groupware Integration



SAP Menu Customer Relationship Management Workforce Management Core WFM Groupware Integration Register Inbound Queues for WFM Groupware Integration

2. Mark Register

3. Click on button Execute (F8).

3.2.4 Specifies Number Ranges for Categories for WFM Groupware Objects



IMG Menu Customer Relationship Management Workforce Management Core WFM Groupware Integration Specifies Number Ranges for Categories for WFM Groupware Objects

2. To create a new interval, choose Change Intervals.The Maintain Number Range Intervals screen appears.

3. Choose the Insert Interval icon.

4. Enter the required values:

No.: Enter a sequential number, 01.From Number Enter the first number of the number range interval, such as

0000000001.To Number Enter the last number of the number range interval, such as

9999999999.Current Number Displays the last number assigned to an internal number range

interval, for example, 1000002809.Ext Do not set this indicator (= "internal").

5. Choose Insert.




3.3 Setting Configuration Parameters for the Groupware Connector

PrerequisitesYou must have installed the Groupware Connector successfully.

Procedure 1. Choose Start Programs SAP Groupware Connector AdminTool MS Exchange

Groupware Connector <name of the instance>.The SAP Groupware Connector Administrative Tool screen appears displaying the configuration parameters on the left.

2. Select the required configuration parameter and specify the required details, e.g.Groupware Configuration General (Password)CRM Adapter Connection General (Site Type & Site Type 2).

3. Choose Apply.


Documents

D58_BB_ConfigGuide_EN_UK