crm connectivity

CRM 4.0

April 2005

English

CRM Connectivity (C71)

SAP AGNeurottstr. 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices CRM Connectivity (C71): Configuration Guide

Copyright

© Copyright 2005 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 of 46


Icons

Icon Meaning

Caution

Example

Note

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.

© SAP AG of 46


ContentConfiguration Guide........................................................................................................................ 6

1 Prerequisites........................................................................................................................ 6

1.1 User Roles.....................................................................................................................6

2 Local Settings...................................................................................................................... 6

2.1 SAP R/3......................................................................................................................... 6

2.1.1 Defining Client Administration (SAP R/3)..............................................................6

2.1.2 Defining Logical System (SAP R/3).......................................................................7

2.1.3 Assigning Logical System to Client (SAP R/3)......................................................8

2.1.4 Creating an RFC User (SAP R/3)..........................................................................9

2.2 SAP CRM.................................................................................................................... 10

2.2.1 Defining Logical System (SAP CRM)..................................................................10

2.2.2 Assigning Logical System to Client (SAP CRM)..................................................10

2.2.3 Creating RFC User (SAP CRM)..........................................................................11

3 Cross-Connectivity.............................................................................................................12

3.1 SAP R/3 with SAP CRM..............................................................................................13

3.1.1 SAP R/3..............................................................................................................13

3.1.1.1 Creating a Logical System for SAP CRM (SAP R/3)..............................13

3.1.1.2 Connecting SAP CRM (SAP R/3)...........................................................14

3.1.1.3 Creating RFC User in Client 000 (SAP R/3)...........................................15

3.1.1.4 Checking Table CRMCONSUM (SAP R/3)............................................16

3.1.1.5 Maintaining Table CRMRFCPAR (SAP R/3)..........................................17

3.1.1.6 Activating Event Control.........................................................................18

3.1.2 SAP CRM............................................................................................................19

3.1.2.1 Defining Logical System for R/3 (SAP CRM).........................................19

3.1.2.2 Connecting SAP R/3 (SAP CRM)...........................................................19

3.1.2.2.1 Creating RFC Destination for the R/3 System........................................193.1.2.2.2 Creating RFC Destination for Replication & Realignment (Clt 000).......203.1.2.2.3 Creating RFC Destination for Replication & Realignment (Application

Client).....................................................................................................21

3.1.2.3 Creating RFC User in Client 000 (SAP CRM)........................................22

3.1.2.4 Site IDs and Subscriptions for OLTP......................................................23

3.1.2.4.1 Creating Site for OLTP...........................................................................233.1.2.4.2 Creating Subscriptions for OLTP............................................................24

3.2 SAP CRM Misc Connections.......................................................................................25

3.2.1 Internet Pricing and Configurator (IPC)...............................................................25

3.2.1.1 Connecting IPC......................................................................................25

3.2.1.1.1 Creating IPC User..................................................................................25

© SAP AG of 46


3.2.1.1.2 Creating RFC Destinations for IPC.........................................................263.2.1.1.2.1 Creating RFC Destination for IPC Server......................................273.2.1.1.2.2 Creating RFC Destination for IPC Dispatcher................................28

3.2.1.1.3 Activating Web UI for IPC.......................................................................29

3.2.1.2 Checking IPC Settings...........................................................................29

3.2.1.2.1 Checking IPC Configuration Files..........................................................303.2.1.2.2 Checking Database Connections...........................................................30

3.2.2 Index Management System (IMS).......................................................................34

3.2.2.1 Creating RFC Destination for IMS..........................................................34

3.2.2.2 Checking IMS Configuration Files..........................................................36

3.2.2.3 Creating the Search Server Relation (SAP CRM)..................................36

3.2.3 Web Server Environment....................................................................................38

3.2.3.1 Creating User WEBLOGIN (CRM).........................................................38

3.2.3.2 Creating User WEBLOGIN (R/3)............................................................39

3.2.3.3 Creating RFC Destination for FTP and HTTP........................................40

3.2.3.4 Settings on the Web Server...................................................................40

3.2.3.4.1 Creating the Directory for Document Publication...................................413.2.3.4.2 Maintaining Properties of the Default FTP Site......................................413.2.3.4.3 Creating a Virtual FTP Directory............................................................423.2.3.4.4 Creating a Virtual HTTP Directory..........................................................423.2.3.4.5 Setting Product Catalog Parameters in WEB.XML.................................43

3.2.3.5 Setting Target for Publishing Catalog Contents (SAP CRM)..................44

3.2.4 CAT Server.........................................................................................................45

3.2.4.1 Checking CAT Server Settings...............................................................45

3.2.4.2 Defining RFC Destination for CAT Server..............................................45

© SAP AG of 46


Configuration Guide

1 PrerequisitesBefore starting with the installation of this building block, please see the Scenario Installation Guide of the SAP Best Practices CRM scenario that you want to install.

1.1 User Roles

UseWith the building block CRM Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:

Technical name Description File name for upload

R/3 System

C71_01C CRM Connectivity Configuration Role (SAP R/3) C71_01C.SAP

CRM System

C71_04C CRM Connectivity Configuration Role (SAP CRM) C71_04C.SAP

ProcedureFor details about how to upload the configuration roles to the system and how to work with the roles please refer to the document Essential Information.

2 Local SettingsThis chapter describes all local settings that are necessary for each required component.

2.1 SAP R/3

2.1.1 Defining Client Administration (SAP R/3)

UseThis activity allows you to change Customizing settings and to start CATT procedures.

© SAP AG of 46


Prerequisites

You have logged on to the system in English in order to start with the installation of the Best Practices Scenario. The logon language of the install user must be English (EN) to ensure that the CATT procedures run correctly.

Procedure1. Run the following activity:

SAP R/3 Role Menu Defining Client Administration (SAP R/3)

Transaction Code SCC4

SAP Menu Tools Administration Administration Client Administration Client Maintenance

2. Choose Display Change.

3. Confirm the warning message Caution: The table is cross client.

4. Select your SAP R/3 client and choose Details.

5. In the Change View “Clients”: Details screen, activate the following settings:

Automatic recording of changes

Changes to Repository and cross-client Customizing allowed

eCATT and CATT Allowed.

6. Save.

7. Go back to the SAP Easy Access Menu.

2.1.2 Defining Logical System (SAP R/3)

UseThe purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must

1. Define the systems as logical systems.

2. Assign the logical system for the SAP R/3 System to a client.

This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.

Logical systems are defined cross-client

Procedure1. Access the transaction using:

SAP R/3 Role Menu Defining Logical System (SAP R/3)

© SAP AG of 46


Transaction Code SPRO

IMG Menu SAP NetWeaver SAP Web Application Server IDoc Interface/Application Link Enabling (ALE) Basic Settings Logical systems Define Logical System

2. Choose New Entries.

3. In the column Log.System, enter a name for the logical system that you want to create.

We recommend that you use the following naming convention:

<system ID>CLNT<client number> (for example: ES7CLNT020)

<system ID> is the ID number of your R/3 system

<client number> is the number of the relevant client in your R/3 system.

4. In the column Name, enter a description of the logical system.

Log. System Name

<Logical system 2>, (for example ES7CLNT020) SAP R/3 System

5. Choose Save.

A transport request for Workbench appears.

6. Select an existing request or create a new request, if necessary.

A transport request for Customizing appears.

7. Select an existing request or create a new request, if necessary.

2.1.3 Assigning Logical System to Client (SAP R/3)

UseThe purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.

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

SAP R/3 Role Menu Local Settings SAP R/3 Assigning Logical System to Client (SAP R/3)


SAP Menu Tools Administration Administration Client Administration Client Maintenance

2. Choose Display Change.

3. Confirm the warning message Caution: The table is cross client.

4. Select your R/3 client and choose Details.

© SAP AG of 46


5. In field Logical System, select the newly created logical system of your SAP R/3 client using the input help.

6. Save and confirm the warning message Be careful when changing the logical system.

7. Choose Back twice.

2.1.4 Creating an RFC User (SAP R/3)

UseTo enable communication between the SAP R/3 back-end system and other SAP systems, you have to create an RFC user in the SAP R/3 System.

The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.

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

SAP R/3 Role Menu Creating an RFC User (SAP R/3)

Transaction Code SU01

SAP Menu Tools Administration User Maintenance Users

2. In the User field, enter RFCUSER.

3. Choose Create.

4. In the Maintain User screen, enter the following data on the Tab entry screens:

Address

Last Name RFC User

Function

Logon data

User type System

Password LOGIN

Defaults

Logon Language EN

Profiles

Profile SAP_ALL and

SAP_NEW

5. Save your entries.

The user RFCUSER has the profiles SAP_ALL and SAP_NEW assigned, which gives him full authorization rights. If this authorization is not applicable to your project you can restrict the rights of this user according to SAP Note 0338537.

© SAP AG of 46


2.2 SAP CRM

2.2.1 Defining Logical System (SAP CRM)

UseThe distribution of data between systems makes it necessary to identify each system as a unique logical system.

A logical system is an application system in which the applications are coordinated to work in one common database. In SAP terms, a logical system corresponds to a client.

ProcedureTo carry out the activity, choose one of the following navigation options:

SAP CRM Role Menu Defining Logical Systems


IMG Path Customer Relationship Management CRM Middleware and Related Components Communication Setup Set Up Logical Systems Define Logical System

Then carry out the following steps:


2. Enter the following data:

A name for the logical system that you want to create (Log.System)

A clear description for the logical system (Name)

Log.System Name

<CRM system>CLNT<Client>, (for example, CS7CLNT200)

For example: “CRM Best Practices”


2.2.2 Assigning Logical System to Client (SAP CRM)

UseThe purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.

© SAP AG of 46



SAP CRM Role Menu Assigning Logical System to Client (SAP CRM)


SAP Menu Customer Relationship Management CRM Middleware and Related Components Communication Setup Set Up Logical Systems Assign client to logical system


1. Choose Display -> Change.

2. Confirm the message Caution: The table is cross-client.

3. Select your CRM client.

4. Choose Details. The Change View “Clients”: Details screen appears.


Field / Area Entry

Logical system <Logical System of CRM client> (for example, CS7CLNT200)

Client role Customizing

Changes and Transports for Client-Specific Objects

Automatic recording of changes

Cross-Client Object Changes Changes to Repository and cross-client Customizing allowed.

Protection: Client Copier and Comparison Tool

Protection level 0: no restriction

Restrictions when Starting CATT and eCATT

eCATT and CATT Allowed

6. Save and confirm the warning message Be careful when changing the logical system.

7. Choose Back twice.

These settings cannot be transported. When a new system is being set up, these settings must be made manually after the system installation has been completed.

2.2.3 Creating RFC User (SAP CRM)

Use

© SAP AG of 46


An RFC user is required for setting up the connectivity between systems.

Procedure

To carry out the activity, choose one of the following navigation options:SAP CRM Role Menu Creating RFC User


SAP Menu Architecture and Technology System Administration Administration User Maintenance Users


2. Choose Create (F8).


Address tab page

Last Name RFCUSER

Function Default-User for RFC connection

Logon data tab page

Password LOGIN

User Type System

Defaults tab page

Logon Language EN

Profiles tab page

Profile SAP_ALL and SAP_NEW


The user RFCUSER has the profiles SAP_ALL and SAP_NEW assigned, which gives full authorization rights. If this authorization is not applicable to your project you can restrict the rights of this user according to SAP Note 0338537.

3 Cross-ConnectivityThis chapter describes all settings that are necessary to connect the components of the mySAP Business Suite landscape with each other. The settings for each combination of two components to be connected are described in a separate structure node. The separate structure nodes make it possible to identify the activities required to connect certain components with each other. The structure nodes for components that are not part of the installation can be skipped.

© SAP AG of 46


3.1 SAP R/3 with SAP CRM

3.1.1 SAP R/3

3.1.1.1 Creating a Logical System for SAP CRM (SAP R/3)

UseTo enable communication between your SAP CRM and your SAP R/3 systems, you need to define logical systems for both systems in your R/3 system.

If the logical system has already been created, skip this activity. You can check if the logical system already exists by running the IMG activity Define Logical System.

Procedure1. To define the two required logical systems for your system, choose one of the following

navigation options:

SAP R/3 Role Menu Creating a Logical System for SAP CRM


IMG Menu SAP NetWeaver SAP Web Application Server IDoc Interface/Application Link Enabling (ALE) Basic Settings Logical systems Define Logical System

2. Choose New entries.

3. In the column Log.System, enter a name for the logical system that you want to create.

We recommend that you use the following naming convention:

<system ID>CLNT<client number> (for example: DS7CLNT712)

<system ID> is the ID number of your CRM system being connected to the backend R/3 system.

<client number> is the number of the relevant client in your CRM system.

4. In the column Name, enter a description of the logical system.

Log. System Name

<Logical system 1> (for example DS7CLNT712) SAP CRM System


6. A transport request for Workbench appears.Select an existing request or create new request, if necessary.

7. A transport request for Customizing appears.Select an existing request or create a new request, if necessary.

© SAP AG of 46


3.1.1.2 Connecting SAP CRM (SAP R/3)

UseCommunication between the systems is based on the RFC interface and Remote Function Calls (RFCs) manage the communication process, parameter transfer and error handling between different systems. To set up this functionality for your systems, you need to define RFC destinations in your system landscape.

Procedure3. To define an RFC destination in the SAP R/3 System, open the transaction:

SAP R/3 Role Menu Connecting SAP CRM (SAP R/3)

Transaction Code SM59

IMG Path SAP NetWeaver SAP Web Application Server IDoc Interface/Application Link Enabling (ALE) Communication Create RFC Connections

4. In the Display and maintain RFC destinations screen, choose Create.Enter the data according to the RFC destination:

Field name User action and default values

RFC destination <SAP CRM System name>CLNT<client>(for example AS7CLNT001)

Connection type 3 (Connection to R/3 System)

Description SAP CRM System

5. Choose Enter.

Technical settings

Load distrib. No

Target host <SAP CRM target host name>, for example pwdf0421

System number <SAP CRM target system number>, for example 74

Save as IP Address

Logon/Security

Security Options

Trusted system No

Logon Screen deselect

SNC Inactiv

Logon

Language EN

Client <SAP CRM target client>, for example 001

User RFCUSER

Password LOGIN (password you have chosen in user

© SAP AG of 46


maintenance)

Current User deselect

Unencrypted Password (2.0)

deselect

6. Choose Enter.

Special Options

Trace deselect

Slow RFC Connection deselect

Unicode Select, if the target system is a unicode system

7. Choose Enter.

8. Save your RFC destination.

9. You can now test your newly created RFC connection using Test connection.

3.1.1.3 Creating RFC User in Client 000 (SAP R/3)

UseThe RFC user in client 000 is required for replication and realignment queues.

ProcedureTo create the RFC user, logon to client 000 in the R/3 system and carry out the following steps:


SAP Menu Tools Administration User Maintenance Users


For R/3 Release > 3.1i


3. In the Maintain User screen, enter the following data:

Address Release 4.0 from Release 4.5 on

Last Name RFC User RFC User

Function Default user for RFC connection

Default user for RFC connection

Logon data

User type Background System

Password LOGIN LOGIN

© SAP AG of 46


Profiles

Profile SAP_ALL and SAP_NEW SAP_ALL and SAP_NEW


For R/3 Release 3.1i


3. In the Create User Master Record screen, enter the following data:

Field Entry

Initial password LOGIN

User type Background

Authorization profiles SAP_ALL and SAP_NEW


3.1.1.4 Checking Table CRMCONSUM (SAP R/3)

UseThe table CRMCONSUM contains the consumers (applications) that are to receive data from the R/3 System.

ProcedureTo check table CRMCONSUM choose:

SAP R/3 Role Menu Checking table CRMCONSUM

Transaction Code SM30 (for R/3 Release 3.1i: SE16)

SAP Menu System Services Table Maintenance Extended Table Maintenance


1. In the Table/view field, enter the table name CRMCONSUM.

2. Choose Maintain.

ResultThe table should have the following entries:

Column Entry

User CRM

Active √

Description CRM

Q-Prefix R3A

© SAP AG of 46


3.1.1.5 Maintaining Table CRMRFCPAR (SAP R/3)

UseThe parameters in this table indicate the RFC destinations which receive data. The required parameters include, for example: consumer, client, object name, and download type.

You can send data to a certain consumer only in an initial download and not in a delta download by making the appropriate specifications for the data exchange.

ProcedureTo maintain the parameter settings, choose:

SAP R/3 Role Menu Maintaining Table CRMRFCPAR



1. In the Table/view field, enter the table name CRMRFCPAR.

2. Choose Maintain.


If you choose New Entries and some of the fields are not maintainable, go back and choose the Copy As… button.

4. Create the following parameter values.

Parameter name Description Recommended Parameter value

User User that uses the OLTP plug-in functions as data receivers

CRM

Object name Object name *

Destination Specifies the destination of the CRM server <RFC destination of CRM system>(e.g. CS7CLNT200)

Caution: the RFC destination name is case sensitive

Load Type Restricts CRMRFCPAR entries to the initial (I) or delta (D) download.

All load types

Out Queue Name RFC outbound queue

In Queue Name RFC inbound queue

BAPI name

INFO Information/Comments

© SAP AG of 46


InQueue flag Controls whether qRFC inbound queues are used on the CRM server

X

Send XML XML supports (Should data be sent in XML format?)

Mixed mode

Stop data Causes the OLTP System to place data into the outbound queue. This field can be used to change the behavior of the queue. The field HOLD_DATA replaces the parameter RECORD_ASYNCHRONOUS_MESSAGE in table CRMPAROLTP.

Normally the queue is processed automatically. If an X has been entered, the data is held in an outbound queue in the OLTP system.

Ignore data

Data rcd inactivie


For some of the fields left blank here (e.g. queue names, BAPI name, description), entries will be added automatically by the system when starting the download of objects at a later stage of the installation.

Be sure that there is only one (the new) entry with Consumer CRM maintained in table CRMRFCPAR. If not, delete other existing entries with CRM as Consumer. Otherwise the download of sales documents R/3 CRM might not run through.

3.1.1.6 Activating Event Control

UseThe activation of the event control is a prerequisite for the replication of data from the R/3 system to the CRM system.

ProcedureTo check the event control activation, choose:

SAP R/3 Role Menu Activating Event Control



1. In the Table/view field, enter the table name TBE11.

2. Choose Maintain.

3. Set the applications NDI to status Active.

© SAP AG of 46


4. Choose Save.

3.1.2 SAP CRM

3.1.2.1 Defining Logical System for R/3 (SAP CRM)

UseThe distribution of data between systems makes it necessary to identify each system as a unique logical system.

A logical system is an application system in which the applications are coordinated to work in one common database. In SAP terms, a logical system corresponds to a client.


SAP CRM Role Menu Defining Logical Systems


IMG Path Customer Relationship Management CRM Middleware and Related Components Communication Setup Set Up Logical Systems Define Logical System



2. Confirm the message Caution: The table is cross-client.


A name for the logical system that you want to create (Log.System).

A clear description for the logical system (Name).

Log.System Name

<R/3 OLTP System>CLNT<Client>,(for example, BECCLNT024)

For example:“OLTP R/3 System”


3.1.2.2 Connecting SAP R/3 (SAP CRM)

3.1.2.2.1 Creating RFC Destination for the R/3 System


SAP CRM Role Menu Creating RFC Destination for the R/3 System


IMG Path Customer Relationship Management CRM Middleware and Related Components Communication Setup

© SAP AG of 46


Define RFC Destinations




Field Entry

RFC Destination <R/3 system name>CLNT<client>, e. g. CS7CLNT200

Connection Type 3 (R/3 connection)

Description OLTP R/3 System

3. Choose Enter.

Technical settings

Load distribution No

Target host <Target host R/3 system>, e. g. pwdf0421

System number <System number of R/3 system>

Logon/Security

Trusted system No

SNC Option Inactive

Language EN

Client <R/3 client>

User RFCUSER

Password LOGIN

Current user

Unencrypted password

4. Save your RFC destination.


3.1.2.2.2 Creating RFC Destination for Replication & Realignment (Clt 000)


SAP CRM Creating RFC Destination for Replication & Realignment (Client 000)


IMG Path Customer Relationship Management CRM Middleware

© SAP AG of 46


and Related Components Communication Setup Define RFC Destinations




Field Entry

RFC Destination SAPCRM_MW_RR_000

Connection Type L (Logical destination)

Description Processing R&R queues – client 000

3. Choose Enter.

Logon/Security

Authorization --

Language --

Client 000

User RFCUSER

Password LOGIN

Current user --

Unencrypted password --


3.1.2.2.3 Creating RFC Destination for Replication & Realignment (Application Client)


SAP CRM Creating RFC Destination for Replication & Realignment (Application Client)


IMG Path Customer Relationship Management CRM Middleware and Related Components Communication Setup Define RFC Destinations




Field Entry

RFC Destination SAPCRM_MW_RR_<CRM client>

© SAP AG of 46


Connection Type L (Logical destination)

Description Processing R&R queues – application client

3. Choose Enter.

Logon/Security tab page

Authorization

Language --

Client <your CRM client>

User RFCUSER

Password LOGIN

Current user

Unencrypted password

4. Choose Enter.

Special Options

Trace deselect

Slow RFC Connection deselect

Unicode Select, if the target system is a unicode system


6. Confirm the information message.


3.1.2.3 Creating RFC User in Client 000 (SAP CRM)

UseAn RFC user is required in client 000 for the replication and realignment queues.

Procedure1. Access the transaction using:

SAP CRM Role Menu Creating RFC User in Client 000


SAP Menu Architecture and Technology System Administration User Maintenance Users




Address tab page

Last Name RFCUSER

Function Default-User for RFC connection

© SAP AG of 46


Logon data tab page

Password LOGIN

User type System

Defaults tab page

Logon Language EN

Profiles tab page



The system user RFCUSER is created with the initial password LOGIN.

The user has the profiles SAP_ALL and SAP_NEW assigned, which gives full authorization rights. If this authorization is not applicable to your project you can restrict the rights of this user according to SAP Note 0338537.

3.1.2.4 Site IDs and Subscriptions for OLTP

3.1.2.4.1 Creating Site for OLTP

The OLTP R/3 system must be defined as a site, like the other systems of the distribution model. The CRM and CDB sites are already predefined so you need only to create the R/3 site and Mobile client sites.

Once you have created the sites, you must define the distribution rules (subscriptions), which determine the data each site is to receive.

All of the objects have to be loaded to the CRM system first, even though you wish to load data from the OLTP system to the CDB. There are two steps for loading the data:

1. Load objects from the OLTP to the CRM system applications component (site type CRM)

2. Load objects from the CRM system to CDB.

The second step is only required when using Field Sales.

R/3 Site Definition

The RFC Destination for connection to R/3 must be defined before performing R/3 Site Definition.


SAP CRM Role Menu Creating Site for OLTP

Transaction Code SMOEAC

© SAP AG of 46


SAP Menu Achitecture and Technology Middleware Administration Administration console


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

2. Choose Create Object.

3. In the Object information: Site screen area, enter the name OLTP and the description OLTP R/3 System and choose the site type R/3.

4. Choose Site attributes next to the Type field.

5. In the Maintenance of R/3 site attributes dialog box, enter the RFC destination for the R/3 system.

6. Choose Enter.

7. Choose Save.

3.1.2.4.2 Creating Subscriptions for OLTP

UseAfter the definition of the R/3 site you create subscriptions using the subscription wizard to enable uploading of the data from CRM to OLTP.


SAP CRM Role Menu Creating Subscriptions for OLTP

Transaction Code SMOEAC

SAP Menu Middleware Administration Administration Console


1. In the Object type field, enter Subscriptions.

2. Choose the Create icon.

3. Follow the subscription wizard instructions.

4. Using the subscription wizard, create three subscriptions:

Subscription All Business Partners (MESG) subscription

Publication All Business Partners (MESG)

Criteria values - - -

Subscription All Business Partner Relationships (MESG) subscription

© SAP AG of 46


Publication All Business Partner Relationships (MESG)


Subscription All Business Transactions (MESG) subscription

Publication All Business Transactions (MESG)


5. Assign these subscriptions to your OLTP site.

For the Best Practices scenarios only Business Partners and Transactions are replicated from the CRM system into the R/3 system. Please create further subscriptions if additional data has to replicated into the R/3 system.

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

3.2 SAP CRM Misc Connections

3.2.1 Internet Pricing and Configurator (IPC)

The installation of the IPC itself is part of the system setup and therefore not described here.

The latest version of the guides dealing with the IPC installation you find in the installation guidelines area on the SAP Service Marketplace:

http://service.sap.com/instguides

3.2.1.1 Connecting IPC

3.2.1.1.1 Creating IPC User

UseIn order to set up the connection from IPC to the CRM system you have to define a user with RFC authorization.

Procedure

© SAP AG of 46


The IPC user is usually created during the technical installation process of the IPC. Check to make sure a user has not already been created.

To carry out the activity, choose one of the following navigation options:

SAP CRM Role Menu Creating IPC User


IMG Path Architecture and Technology System Administration User Maintenance Users


1. In the User field, enter IPCUSER.



Address tab page

Last Name IPCUSER

Function Default user for connection to IPC

Logon data tab page

Password LOGIN

User Type Service

Profiles tab page



Result

The system user IPCUSER is created with the initial password LOGIN.The user has the profiles SAP_ALL and SAP_NEW assigned, which gives full authorization rights. If this authorization is not applicable to your project you can restrict the rights of this user according to SAP Note 0338537.

3.2.1.1.2 Creating RFC Destinations for IPC

The RFC destinations for the IPC are normally created during the installation of the IPC. Please skip this activity if the RFC destinations IPC_RFC_SERVER and IPC_RFC_DISPATCHER are already available.

Use

© SAP AG of 46


Before creating RFC destinations, you must decide how many IPC servers you want to use. Except for the socket-based scenario, you cannot dynamically add IPC servers to a running dispatcher. Therefore you must decide how many servers are appropriate, configure CRM and the dispatcher accordingly, then start the dispatcher.

For example, suppose you want two IPC servers. CRM needs to talk to the dispatcher to get connected to a server, and for each server you must maintain three RFC destinations. As a convention, RFC destinations and RFC program IDs are the same. In addition, all server destinations start with the same string, followed by a number. You can only choose the dispatcher's destination and the "prefix string" of the servers' destinations. You choose IPC_RFC_DISPATCHER as the RFC destination (and program ID) of the dispatcher, and IPC_RFC_SERVER_ as the prefix string for the servers. This means that you create RFC destinations/program IDs IPC_RFC_SERVER_1 and IPC_RFC_SERVER_2 for the servers.

3.2.1.1.2.1 Creating RFC Destination for IPC Server


SAP CRM Role Menu Creating RFC Destination for IPC Server






Field Entry

RFC Destination IPC_RFC_SERVER_1

Connection Type T (TCP/IP)

Description RFC destination for IPC Server

3. Choose Enter.

Technical settings

Activation Type Registered Server Program

Program ID IPC_RFC_SERVER_1

Gateway Host <Gateway host of CRM system>

Gateway service <Gateway service>, usually sapgw<system number of CRM system>

© SAP AG of 46


Logon/Security

SSL Inactive


3.2.1.1.2.2 Creating RFC Destination for IPC Dispatcher


SAP CRM Creating RFC Destination for IPC Dispatcher






Field Entry

RFC Destination IPC_RFC_DISPATCHER


Description RFC destination for IPC Dispatcher

3. Choose Enter.

Technical settings


Program ID IPC_RFC_DISPATCHER

Gateway Host <Gateway host of CRM system>

Gateway service <Gateway service>, usually sapgw<system number of CRM system>

Logon/Security

SSL Inactive

© SAP AG of 46



3.2.1.1.3 Activating Web UI for IPC

These settings are normally executed during the installation of the IPC.

UseTo be able to call the IPC web application user interfaces from the CRM system someadditional settings have to be applied in the CRM system.

Please skip this section if you don’t use the IPC in combination with Web applications, e.g. Internet Sales.

ProcedureIt is assumed that the IPC Web Applications are running on a SAP J2EE Engine installed on the following host:

<J2EEEngine_host>

It is assumed that the SAP J2EE Engine’s http port is:

<J2EEEngine_http_port>.

The complete address http://<J2EEEngine_host>:<J2EEEngine_http_port> is referred to as:

<J2EEEngineURL>.

1. To carry out the activity, choose one of the following navigation options:

SAP CRM Role Menu Activating Web UI for IPC


IMG Path CRM Basic Functions Configuration Engine Define URLs


3. Create the following destinations:

Field Entry

UI_CFG <J2EEEngineURL>/ipc/ipc/command.do

UI_CSR <J2EEEngineURL>/csr/csr/init.do

UI_ANALYSIS <J2EEEngineURL>/ipcpricing/

3.2.1.2 Checking IPC Settings

Use

© SAP AG of 46


The steps described in this section are general activities that are already part of the IPC installation. To make sure that all parameter settings are correct you can carry out steps referred to in the subordinate sections.

PrerequisitesThe IPC installation described in the IPC Installation Guide has been executed. The RFC destinations of the IPC have been created as described in the section RFC Destinations for IPC.

3.2.1.2.1 Checking IPC Configuration Files

UseTo check whether the IPC configuration settings are correct you have to control two parameter files for the IPC and the JSP server.

ProcedureGeneral Settings

Edit the file dispatcher.properties in the folder lib/properties in your IPC installation. Check whether the entries in this file match the entries in the RFC destinations IPC_RFC_DISPATCHER and IPC_RFC_SERVER_1.

Parameter Entry Comment

rfcEnabled true

rfcGateways <crm-servername>:<port>, e.g. pgwdf108:sapgw10

port = sapgw<system number of the CRM system>

rfcDispatcherProgId IPC_RFC_DISPATCHER

rfcServerCount <number of servers>, e.g. 1

rfcServerProgIdPrefix IPC_RFC_SERVER_

Correct the settings if necessary.

3.2.1.2.2 Checking Database Connections

UseTo check whether the database connections between IPC and CRM are set up correctly, run the following steps on the machine where the IPC server is installed.

ProcedureTo start the IPC Administrator locally, choose the following menu path from the IPC desktop:

IPC Checking Database Connections

© SAP AG of 46


Windows Desktop Start Programs SAP Internet Pricing and Configurator Administrator

On the screen SAP Internet Pricing and Configurator Administrator, choose Server.

The following table describes typical server settings:

Field Entry

Dispatcher selected

Dispatcher Host - localhost: server and dispatcher are running on the same server

- otherwise IP address of the server where the dispatcher is running

Dispatcher Port 4444: default port

Server Port

These settings are normally maintained during the IPC installation. Do not change these settings unless you are very familiar with their meanings.


1. Accept proposed entries for the other fields.

2. Choose Database.

© SAP AG of 46


3. Check whether an entry for your CRM server exists in the upper window. If not, run the steps 4 – 6. Otherwise continue with step 7.

4. Choose Add to define the database info.

5. On the screen Add new database info, enter the following parameters:

© SAP AG of 46


Field/Button Entry

CRM-System selected

Alias <CRM system name>, must be identical with the SID, for example CS7

Load balanced not selected

Application Server <application server of the CRM system>, for example pwdf0422

System Number <System number of the CRM system>

User <User of the CRM system>, a user IPCUSER is already created in the CRM system (see section Creating IPC User)

Password <User password for the CRM system>; the default password for the user IPCUSER is login

Client <Client of the CRM system>

6. Choose OK.Result: The active button for the system is set to active and a client entry is automatically generated.

7. Double-click on the CRM server in the upper window. Check whether your CRM client is displayed in the lower window. If not, mark the CRM system in the upper screen, then choose Add client and enter the following:

Field/Button Entry

User IPCUSER

Password LOGIN

Client <CRM client>

8. Set the client to active and choose Log In.

9. Choose Pricing engine Parameters, then Default.

10. Choose Document Parameters, and accept the default parameters.

11. Choose Document Header Attributes, and enter any default values for customer master attributes that you require. You do not need to enter a value for all attributes.

The entry of values for step 10 and 11 is only necessary if the pricing data is replicated to the IPC.

12. Choose Save and Close.

ResultThe IPC database connections are set up.

© SAP AG of 46


3.2.2 Index Management System (IMS)

In this section you can find general information about the settings for the Index Management System (IMS).

The Index Management System itself is part of the Text Retrieval & Information Extraction (TREX.)The installation is part of the system setup and therefore not described here.

For information concerning the installation of the IMS please refer to the installation guide of the TREX.You can find the latest version of this guide in the installation guidelines area on the SAP Service Marketplace:

http://service.sap.com/instguides

3.2.2.1 Creating RFC Destination for IMS

The RFC destination for the IMS is normally created during the installation of the TREX. Please skip this activity if the RFC destination is already available.

ProcedureTo create a RFC destination for TREX 6.0, choose one of the following navigation options:

SAP CRM Creating RFC Destination for IMS





Field Entry

RFC Destination TREXDEFAULT_START


Description RFC destination for TREX

3. Choose Enter.

Technical settings

Activation Type Start on Explicit Host

© SAP AG of 46


ProgramPath to the RFC server program on the TREX host:• UNIX/<TREX_Directory>/ims_server_admin.x

• Windows<TREX_Directory>\ims_server_admin.exe

Target host <Target host IMS server>

Save asEnter the following depending on your chosen option:

• The host name (with domain name if necessary) of the TREX host in the form <host_name.domain_name>• The IP address of the TREX host

Gateway Host Enter the host name (with domain name if necessary) or the IP address of the TREX host.

Gateway service Enter the name of the gateway in the form sapgw<inst_no.>

Replace <inst_no.> with the instance number that you entered during the gateway installation

usually sapgw47

Logon/Security

SSL Inactive


To create a RFC destination for TREX 6.1 and higher, choose one of the following navigation options:

SAP CRM Creating RFC Destination for IMS





Field Entry

RFC Destination TREXDEFAULT_REG or TREXDEFAULT_REG


Description RFC destination for TREX

3. Choose Enter.

© SAP AG of 46


Technical settings


Program IDName that the RFC server uses to register with the SAP Gateway: <registration_name>

Use the same lower/uppercase conventions as used in theTREX configuration file <TREX_DIR>/TREXRfcServer.ini or <TREX_DIR>/TREXDaemon.ini

If the lower/upper case is not the same, the connection test will not work.

Gateway Host Host name (with domain name if necessary) or the IP address of the host on which the gateway is installed.

Gateway service Name of the gateway in the form sapgw<instance_number>, usually sapgw47

Logon/Security

SSL Inactive


3.2.2.2 Checking IMS Configuration Files

UseThis activity is only relevant if errors occur when testing the RFC connection IMSDEFAULT.

ProcedureEdit the file imsconfig.cfg in the folder of your TREX installation (e.g. ..\Program Files\SAP\SAPTREX). Check whether at least the following entries are available.

You will find these parameters in the section Connection at the end of this file.

Parameter Entry Comment

HOST < hostname of server, where TREX is installed>

INSTANCE sapgw<XY>, e.g. sapgw47

XY = 47 if standalone gateway is used or system number of the CRM system

SERVICE sap_rfcretrieval

Correct the settings if necessary.

3.2.2.3 Creating the Search Server Relation (SAP CRM)

Use

© SAP AG of 46


Before you can publish a product catalog for CRM Internet Sales, you have to create a Search Server Relation.


SAP CRM Creating Search Server Relation

IMG Menu SAP Web Application Server Knowledge Management Settings in the Knowledge Warehouse System Text Retrieval & Information Extraction Define Search Server Relation

1. On the Search Server Relation tab check whether an entry with a Search server ID IMS_SSR exists. If not, run steps 2 – 9.

2. Choose Create SSR. A dialog box appears.

3. In the field Search server relation ID, enter IMS_SSR.

4. Choose Create SSR.

5. In the dialog box that appears, enter the following values

Field name Value

Search engine DRFUZZY

RFC destination (TCP/IP) TREXDEFAULT_START or TREXDEFAULT_REG

Description: Search Server Relation


7. Select the entry IMS_SSR.

8. Choose Set SSR DEFAULT.

9. In the security prompt, choose Yes.

10. Choose the RFC destinations tab.

11. For the Search Server Relation IMS_SSR two entries should exist. One entry is for indexing (I) and the other one for searching (S).

This search server relation establishes an RFC connection. To test the RFC destination for the search server relation, proceed as follows:

12. Select one of the Search Service Relation entries.

13. From the screen area Setting search engine, choose Connection Test.

14. Sometimes you have to restart the transaction SRMO before the connection test works.

ResultA message box appears. If the connection is successful, a green traffic light is displayed and the fields Version info for RFC server and Version info for search eng. contain entries.

© SAP AG of 46


3.2.3 Web Server Environment

3.2.3.1 Creating User WEBLOGIN (CRM)

Use In order to set up the connection from the Web server to the CRM system you have to define a user with RFC authorization.

The user WEBLOGIN is usually required during the installation process of the Web server (e.g. SAP J2EE Engine). Please check whether a user is already with a different name has been already created. In this case the user WEBLOGIN is obsolete.


SAP CRM Creating User WEBLOGIN


SAP Menu Architecture and Technology Administration System Administration User Maintenance Users

1. In the User field, enter WEBLOGIN.



Address tab page

Last Name WEBLOGIN

Internet Mail A valid e-mail address which appears as sender of order confirmations

Comm. Method INT

Function Default user for SAP J2EE Engine

Logon data tab page

Password sapphire

User Type Service

Profiles tab page



ResultThe system user WEBLOGIN is created with the password SAPPHIRE.

© SAP AG of 46


The profiles SAP_ALL and SAP_NEW are assigned to all users that were created automatically. These profiles give them full authorization rights. If this is not applicable to your project you can restrict the rights of these users according to SAP Note 0338537.

3.2.3.2 Creating User WEBLOGIN (R/3)

UseIn order to set up the connection from the Web server to the R/3 system you have to define a user with RFC authorization.

The user WEBLOGIN is usually required during the installation process of the Web server (for example, SAP J2EE Engine). Please check whether a user is already with a different name has been already created. In this case the user WEBLOGIN is obsolete.


SAP R/3 Creating User WEBLOGIN

Transaction code SU01

SAP Menu Architecture and Technology Administration System Administration User Maintenance Users

1. In the User field, enter WEBLOGIN.



Address tab page

Last Name WEBLOGIN

Internet Mail A valid e-mail address which appears as sender of order confirmations

Comm. Method INT

Function Default user for SAP J2EE Engine

Logon data tab page

Password sapphire

User Type Service

Profiles tab page

© SAP AG of 46




ResultThe system user WEBLOGIN is created with the password SAPPHIRE.

The profiles SAP_ALL and SAP_NEW are assigned to all users that were created automatically. These profiles give them full authorization rights. If this is not applicable to your project you can restrict the rights of these users according to SAP Note 0338537.

3.2.3.3 Creating RFC Destination for FTP and HTTP

UseFor replication data from the CRM system to the Web server RFC destinations for the FTP and HTTP services have to be created.


SAP CRM Creating RFC Destination for FTP and HTTP

Transaction Code SE38

SAP Menu Architecture and Technology ABAP Workbench Development ABAP Editor

1. Enter RSFTP005 in the field Program.

2. Choose Execute.The RFC destinations SAFTP and SAPFTPA will be created.

3. Choose Back.

4. Enter RSHTTP05 in the field Program.

5. Choose Execute.The RFC destinations SAHTTP and SAPHTTPA will be created.

3.2.3.4 Settings on the Web Server

UseThese settings refer to the Internet services comprised by the Microsoft Internet Information Server. The CRM system also requires HTTP and FTP services, which have to be configured with the Internet Service Manager.

Procedure

© SAP AG of 46


Start the Internet Service Manager. From the Web Server desktop, choose

Web Server Windows NT: Start Windows NT 4.0 Option Pack Microsoft Internet Information Server Internet Service Manager

Windows 2000: Start Programs Administrative Tools Internet Service Manager

In the left window of the Internet Service Manager, drill down in the file tree structure. In the subdirectories, the Default FTP Site and the Default Web Site are usually displayed. This depends on the configuration of the MS Internet Information Server.

3.2.3.4.1 Creating the Directory for Document Publication

UseThe documents of the product catalog are published to a separate directory, which has to be accessible using FTP and HTTP. For this reason a directory (for example called catalog) has to be a subdirectory of your HTTP root directory.

Procedure

Web Server Creating the Directory for Document Publication

1. To check whether the directory catalog exists, open the directory Default Web Site in the file tree structure. The MS Internet Service Manager displays the subdirectories and the virtual directories mapped to the Default Website.

2. If you do not find the directory catalog attached to the Default Web Site, you first have to find out the path of the HTTP root directory.

3. Select the directory Default Web Site, click the right mouse button and choose Properties.

The tab Home Directory shows the path to the HTTP root directory in the field Local Path, e.g. C:\Inetpub\wwwroot.

4. With the Windows NT Explorer, open the HTTP root directory and create a new subdirectory called catalog.

5. With the Windows NT Explorer, select the directory catalog and choose File Properties.

6. Choose tab Web Sharing.

7. Select the option Share this folder, enter Default Web Site in the field Share on and enter the alias catalog.

8. Choose tab Sharing.

9. Select option Share this folder and enter the alias catalog.

3.2.3.4.2 Maintaining Properties of the Default FTP Site

ProcedureWeb Server Maintaining Properties of the Default FTP Site

To check the access authorizations of the FTP service, carry out the following steps:

1. In the left window of the MS Internet Information Server, select the Default FTP Site.

© SAP AG of 46


2. Click the right mouse button and choose Properties. You find the authorizations in the Security Accounts tab.

3. Select the field Allow Anonymous Connections and choose OK.

ResultFor accessing the Default FTP Site the user ANONYMOUS can be used without a password.

You may create and maintain different users according to your security guidelines. In that case you have to note the logon information for later configuration settings.

3.2.3.4.3 Creating a Virtual FTP Directory

UseSince the root directories of the FTP and the HTTP services are different, you need to gain FTP-access to the directory catalog by creating a virtual FTP directory that maps to the directory catalog.

If the virtual directory catalog is not displayed as a subdirectory of the Default FTP Site in the MS Internet Information Server, you have to create it.

Procedure

Web Server Creating a Virtual FTP Directory

1. Select the entry Default FTP Site in the left window of the Internet Information Server, click the right mouse button and choose New Virtual Directory.

2. In the Virtual Directory Creation Wizard, choose next and then type the Alias name catalog.

3. Choose Next.

4. Type in the physical path of the ‘real’ directory catalog (for example, C:\Inetpub\wwwroot\catalog).Alternatively, you can choose Browse.

5. Choose Next.

6. Allow Read and Write access and choose Next.

7. Choose Finish.

3.2.3.4.4 Creating a Virtual HTTP Directory

UseSince the root directories of the FTP and the HTTP services are different, you need to gain Web access to the directory catalog by creating a virtual HTTP directory that maps to the directory catalog.

If the virtual directory catalog is not displayed as a subdirectory of the Default Web Site in the MS Internet Information Server, you have to create it.

Procedure

Web Server Creating a Virtual HTTP Directory

© SAP AG of 46


1. Select the entry Default Web Site in the left window of the Internet Information Server, click the right mouse button and choose New Virtual Directory.

2. In the Virtual Directory Creation Wizard, choose next and then type the Alias name catalog.

3. Choose Next.

4. Type in the physical path of the root directory catalog (for example, C:\Inetpub\wwwroot\catalog).Alternatively, you can choose Browse.

5. Choose Next.

6. Allow Read and Write access and choose Next.

7. Choose Finish.

3.2.3.4.5 Setting Product Catalog Parameters in WEB.XMLVarious parameters are available in the WEB.XML file for the configuration of product catalogs. You usually do not have to make any changes here. You only have to specify parameters when the connection data of the IMS server is not read dynamically from the CRM system; rather it is overridden using the statistical data in the WEB.XML file. This makes sense when catalog data has to be manually distributed to different IMS servers due to performance problems, and does not only have to be replicated to one of the IMS servers that are defined in CRM.

Edit the file web.xml in your JSP server installation. For the SAP J2EE Engine this file is located in the following directory:

<SAP-J2EE-root>\cluster\server\services\servlet_jsp\work\jspTemp\<CRM ISA Web Application Component>\root\WEB-INF

<SAP-J2EE-Root> is the installation directory of the SAP J2EE Engine Server

For example: C:\SAPJ2EE

<CRM ISA Web Application Component> is the CRM Internet Sales Web Application Component, that has to be installed.

For example, the complete path for B2B could be:

C:\J2EE\cluster\server\services\servlet_jsp\work\jspTemp\B2B\root\WEB-INF\web.xml

The parameter names are listed as follows: You only have to specify the last four parameters if false was specified for the first parameter.

useDynConnParam.ims.catalog.isa.sapmarkets.com

This parameter must contain the value false, if the connection parameters that are defined inCRM are to be overridden. In this case, the following four parameters must also be specified.The standard connection is still used if these parameters are missing or incomplete.

gwhost.ims.catalog.isa.sapmarkets.com

The gateway host of the IMS server is specified using this parameter.

gwserv.ims.catalog.isa.sapmarkets.com

The gateway service of the IMS server is specified using this parameter.

tphost.ims.catalog.isa.sapmarkets.com

The host name of the IMS server is specified using this parameter.

tpname.ims.catalog.isa.sapmarkets.com

© SAP AG of 46


The name of the program (ims_server_admin.exe) that is executed on the IMS server is specified using this parameter.

3.2.3.5 Setting Target for Publishing Catalog Contents (SAP CRM)

UseIn the CRM system you have to define the targets for publishing documents for catalog areas and product items. The necessary HTTP and FTP settings must be configured.


SAP CRM Setting Target for Publishing Catalog Contents


IMG Path Customer Relationship Management Master Data Product Catalog Set Targets for Publishing Catalog Contents

1. Choose New entries.


Field Entry

Publish. target <ID of the publishing target>,for example WEBSHOP

Host name <name of the Web server machine>, for example pgwdf049

HTTP port Port of the default web site, e.g. 80

See entries in your system landscape questionnaire for Web Server.

HTTP directory Describes the directory that is used for publishing documents on the Web server.

Enter the directory you have created in the activity Creating Directory for Document Publication.

Default: Catalog

RFC destination SAPFTPA

FTP Port Port of the default FTP site, e.g. 21

See entries in your system landscape questionnaire for Web Server.

User name Enter the user name of the user you have defined in the activity Selecting the Default FTP Site

© SAP AG of 46


Default: ANONYMOUS

Password No password if you have selected Allow Anonymous Connection in the activity Selecting the Default FTP Site.

Otherwise enter the password of the user you have defined for the access.

FTP directory Describes the directory in which the HTTP publication took place.

Enter the directory you have created in the activity Creating a Virtual FTP Directory.

Default: Catalog

3.2.4 CAT Server

3.2.4.1 Checking CAT Server Settings

UseThe CAT (CRM Application Tool) server is a prerequisite for qualifying leads using questionnaires. The CAT server is part of the Internet Pricing and Configurator installation although it is not used by the IPC. The CAT server has to be explicitly selected during the IPC installation.


SAP CRM Checking CAT Server Settings


IMG Path Customer Relationship Management CRM Cross-Application Components SAP CAT Server Setup

1. Check whether the CAT server is installed and configured according to the documentation of the IMG activity.

3.2.4.2 Defining RFC Destination for CAT Server


SAP CRM Defining RFC Destination for CAT Server


© SAP AG of 46






Field Entry

RFC Destination CONNECTOR_<CRM system name>_<Client>, e.g., CAT_CS7_240

Connection Type T (TCP/IP Connection)

Description CAT Server

3. Choose Enter.

Technical settings


Program ID CONNECTOR_<CRM system name>_<Client>

Gateway host Host name of the CRM system

Gateway service sapgw<CRM system number>


© SAP AG of 46

crm connectivity

Documents

sap products

sap group products

client sap r3

logical system sap r3

express permission of

rfc user sap r3

client administration

registered trademarks