bb installation guidesapidp/... · web viewcovered in this configuration guide. carefully read the...

SAP Hybris Marketing 1.2 (1511)

January 2016

English

Basic Settings for Hybris Marketing (CEB)

SAP SEDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices Basic Settings for Hybris Marketing (CEB): Configuration Guide

Copyright

© 2015 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© SAP SE Page of


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 SE Page of


Content1 Purpose............................................................................................................................. 52 Preparation........................................................................................................................ 5

2.1 Prerequisites............................................................................................................52.2 SAP Notes...............................................................................................................52.3 Business Warehouse (BW) Client Definition............................................................52.4 SAP HANA Database Configuration........................................................................62.5 ABAP-Related Prerequisite Settings.......................................................................62.6 Users and Authorizations.........................................................................................6

3 Configuration.....................................................................................................................83.1 Client and Connectivity Settings..............................................................................8

3.1.1 Defining Logical System......................................................................................83.1.2 Maintaining Client Settings..................................................................................83.1.3 Creating RFC Destination....................................................................................93.1.4 Allowing BW Namespaces to be Modified.........................................................103.1.5 Allowing LOCAL Software Component to be Modified......................................113.1.6 Creating ABAP Package for BI Content............................................................113.1.7 Creating ABAP Package for OData Services....................................................12

3.2 Checking Virus Scan Profiles................................................................................133.3 Integration Settings for SAP CRM (Optional).........................................................14

3.3.1 Creating RFC User in SAP CRM for Hybris Marketing (Optional).....................143.3.2 Creating RFC Destination in Hybris Marketing for SAP CRM (Optional)...........15

3.4 Configuration of Operational Analytics and Easy Query Environment...................163.4.1 Activating SICF Services...................................................................................173.4.2 Configuring Operational Data Provisioning........................................................183.4.3 Configuring Easy Query Environment...............................................................19

© SAP SE Page of


Basic Settings for Hybris Marketing

1 PurposeThis building block provides the necessary steps to carry out the basic settings for SAP Hybris Marketing, such as creating a logical system and an RFC destination, as well as settings for SAP NetWeaver Gateway and the Business Warehouse client. Important: Prerequisite steps that are described in sufficient detail in the SAP Hybris Marketing installation guide are not covered in this configuration guide. Carefully read the Preparation chapter below with all its sub chapters and carry out all mentioned and relevant steps as described in the SAP Hybris Marketing installation guide before implementing the Basic Settings for Hybris Marketing configuration guide.You can find the SAP Hybris Marketing installation guide here: http://help.sap.com/mkt ® Installation and Upgrade Information ® Installation Guide. Make sure to download the published version at the same time that you receive the SAP Hybris Marketing version you want to implement.

2 Preparation2.1 PrerequisitesBefore executing the configuration instructions described below, the following activities must be performed: 1. You have identified the relevant deployment scenario (refer to the SAP Hybris

Marketing installation guide, chapter Deployment Scenarios: http://help.sap.com/mkt ® Installation and Upgrade Information ® Installation Guide).

2. The appropriate system landscape is installed and configured. For details regarding the software components and support package levels used to build the rapid-deployment solution, refer to the Software and Delivery Requirements document that you find at http://service.sap.com/rds-ymkt ® scroll down to Check Requirements; for details regarding the installation itself refer to the SAP Hybris Marketing installation guide (chapters 4 and 5 including all sub chapters).

2.2 SAP NotesAfter system landscape installation, make sure that the SAP Notes referred to in the SAP Hybris Marketing release information note 1885803 or 1933146, depending on your Software component level, have been implemented. Implement those SAP Notes that are listed in the Notes to be installed before executing Chapter 6/Installation Guide or after you have executed all steps in Chapter 2/Upgrade Guide section before implementing this building block.

Make a note of the SAP Notes listed in the Notes to be installed after you have finished the Installation Guide or Upgrade Guide section. Implement these notes only after you have implemented the Initial Setup of Hybris Marketing (CED) configuration guide, and depending on which solutions of SAP Hybris Marketing you actually use.

2.3 Business Warehouse (BW) Client DefinitionSAP Hybris Marketing requires a BW client in the Hybris Marketing system to enable the activation of Business Intelligence (BI) content. The BW client can be the same one that is used for SAP Hybris Marketing, or it can be a separate client. Make sure that your system administrator has set up a BW client. To check whether the BW client has been set up, you can:

© SAP SE Page of

https://css.wdf.sap.corp/sap/support/notes/1933146

https://service.sap.com/sap/support/notes/1885803

http://service.sap.com/rds-ymkt

http://help.sap.com/mkt



Verify in the RSADMINA table (display its content via transaction SE16) that the BW client has been entered in the BWMANDT field

Verify that a logical system (display via transaction SCC4) and RFC connection (display via transaction SM59) have been set up for the BW client

Verify that when logged on to the BW client, you can access transaction RSA1

2.4 SAP HANA Database ConfigurationBefore executing the configuration instructions described in in chapter 3 – Configuration, your system administrator must have implemented the following SAP HANA-related settings as described in the SAP Hybris Marketing installation guide: http://help.sap.com/mkt ® Installation and Upgrade Information ® Installation Guide:

Configuring SSL for SAP HANA XS Engine (chapter 7.3.1) SAP HANA User for Technical Configuration (chapter 7.3.2) Authorization Enhancement for _SYS_REPO User (chapter 7.3.3.1). This is only

required for deployment scenario C. If you implement another deployment scenario, skip this chapter.

2.5 ABAP-Related Prerequisite SettingsBefore executing the configuration instructions described in in chapter 3 – Configuration, your system administrator must have implemented the following ABAP-related settings as described in the SAP Hybris Marketing installation guide: http://help.sap.com/mkt ® Installation and Upgrade Information ® Installation Guide:

User for Application Setup (chapter 7.4.1)

We strongly advise you not to update SAP business roles, but to create copies of the standard SAP business roles, for example, Z_BC_BASIS_ADMIN and enhance the Z-roles only.

Setting the Fully Qualified Domain Name (chapter 7.4.2) Configuring HTTPS (chapter 7.4.3) Configuring the Secure Sockets Layer Protocol (chapter 7.4.4) File Extensions Excluded from HTTP Compression (chapter 7.4.5) Installation of the SAP HANA Rules Framework (HRF) – if relevant for your selected

scope (chapter 7.6.1) Prerequisites for SAP Cloud for Customer Integration – only relevant if you use SAP

Cloud for Customer and want to integrate it with SAP Hybris Marketing (chapter 7.6.2)

User Configuration for XS-based Apps (chapter 7.10) Configuring the SAP Web Dispatcher (chapter 7.12)

2.6 Users and AuthorizationsUsers for installationCreate the following users to execute the implementation steps:

System User Authorizations

SAP Hybris Marketing (NetWeaver ABAP)

<installation user>

To avoid authorization issues, we recommend assigning SAP_ALL to the installation user. If due to security reasons this is not allowed in your organization, create one or several installation users as

© SAP SE Page of




described in the SAP Hybris Marketing installation guide, chapter Prerequisites in AS ABAP System: User for Application Setup.

We strongly advise you not to update SAP business roles, but to create copies of the standard SAP business roles, for example, Z_BC_SIW_DEV and enhance the Z-roles only. If you update the SAP default business roles and not create a copy of them, your changes to the SAP business roles will be overwritten once you upgrade the SAP Hybris Marketing solution.

In the BW client, ensure that the installation user has the authorizations of the following default roles assigned:

SAP_BC_SIW_DEV SAP_BC_WEBSERVICE_DEBUGGER SAP_BC_WEBSERVICE_ADMIN_TEC SAP_BC_BGRFC_SUPERVISOR

SAP HANA <installation user for Hybris Marketing>

Create a specific user for the technical configuration (TC_USER) as described in the SAP Hybris Marketing installation guide, chapter SAP HANA User for Technical Configuration: http://help.sap.com/mkt ® Installation and Upgrade Information ® Installation Guide.

SAP HANA SAP<SID> This user is used for the SAP NetWeaver server (hosting SAP Hybris Marketing) to access the SAP HANA database. By default, it is named SAP<SID>. (SID stands for System ID, for example, if the SAP NetWeaver server is named NW1, then the user is named SAPNW1.)It may have a different name, assigned during NetWeaver server installation. To check the correct name:

1. Logon to the NetWeaver server using SAP GUI.2. Open menu System ® Status.3. In System:Status window, under Database

Data area, read the Owner field.This user is only required to execute the activation procedure for the deployment scenario C (Hub-Deployment With Shared SAP HANA System of SAP Business Suite).

Installation users are only used for initial configuration and content activation activities. For security reasons, after completing the activation, we recommend that you remove the authorizations you have given to the users who have performed the implementation steps, or that you set a new password for generic users.

© SAP SE Page of



3 Configuration3.1 Client and Connectivity Settings3.1.1 Defining Logical System

UseIn this activity you define a logical system for the Hybris Marketing system. In SAP terms, a logical system corresponds to a client.

Optionally you can set up one client for the SAP NetWeaver Business Warehouse (BW) content, and a separate client for the SAP Hybris Marketing application. In this case, create a logical system for the BW client and one for the Hybris Marketing client.

Procedure1. Access the transaction using the following navigation options:

Transaction code SPRO

SAP IMG menu Integration with Other SAP Components ® Event Management Interface ® Define System Configuration ® Define Logical System

2. Choose New Entries (F5).3. Enter the following data:

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

Log.System Name

<system>CLNT<Client number>(for example, CEICLNT100)

For example, Hybris Marketing

4. Save your entries (Ctrl + S) and choose a workbench request, if required.

If you have chosen the option of two clients, repeat the steps for the BW logical client.

3.1.2 Maintaining Client Settings

UseWith this activity you assign the logical system to the relevant client.

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

Transaction code SCC4

SAP Menu Tools ® Administration ® Administration ® Client Administration ® Client Maintenance

2. Choose Display ® Change.3. Confirm the message Caution: The table is cross-client.

© SAP SE Page of


4. Highlight your relevant client and choose Details.5. On the Change View “Clients”: Details screen enter the following data:

Field / Area Entry

Logical system <Enter the logical system which you created in the previous chapter>, for example, CEICLNT100

Std currency <Enter the standard currency>, for example, USD

Client role <Select the relevant role>, for example, Test

Changes and Transports for Client-Specific Objects

<Select the relevant entry>, for example, Automatic recording of changes

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

Client Copy and Comparison Tool Protection

Protection level 0: No restriction

CATT and eCATT Restrictions eCATT and CATT Not Allowed

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

If you have chosen the option of two clients, repeat the steps for the BW logical client.

3.1.3 Creating RFC Destination

UseA Remote Function Call (RFC) destination has to be defined for the SAP Hybris Marketing system.

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

Transaction code SM59

SAP Menu Tools ® Administration ® Administration ® Network ® RFC Destinations

2. On the Configuration of RFC Connections screen, choose Create (F8).

3. Enter the following data:

Field Entry

RFC Destination <system name>CLNT<client number>, for example, CEICLNT100

Connection Type 3 (Connection to ABAP System)

Description 1 <Enter a description>, for example, System CEI client 100

4. Choose Enter.

Technical Settings

© SAP SE Page of


Load Balancing No

Logon & Security

Language <Relevant language>, for example, EN

Client <Relevant client>

User <Leave empty>

Password <Do not enter a password>

Trust Relationship No

Status of Secure Protocol

Inactive

Unicode

Communication Type with Target System

Set Unicode flag if Unicode test has been executed successfully. This test can be performed by choosing Utilities ® Test ® Unicode Test in the menu. The RFC destination has to be saved first before the test can be performed. An information message appears (for example: Target is a Unicode system (character size 2)).

5. Save (Ctrl + S) your RFC destination.6. You can now test your newly created RFC connection using the Connection Test button.

You can also test the RFC connection using the menu path Utilities ® Test. Then you can choose Connection Test or Authorization Test. The connection test performs only a technical test (Host, IP Address) of the target system as the authorization test performs an invisible logon to the target system using the maintained user and password of the RFC destination.

If you have chosen the option of two clients, repeat the steps for the second logical client.

ResultYou have successfully created the RFC destination for the Hybris Marketing system.

3.1.4 Allowing BW Namespaces to be Modified

UseTo allow system changes for BW content, make sure that the namespaces /BI0/ and /BIC/ are modifiable.

Procedure1. Log on to the SAP Hybris Marketing system using the SAP GUI.2. Access the transaction choosing the following navigation option:

Transaction code SE03

3. On the Transport Organizer Tools screen, select the folders: Transport Organizer Tools ® Administration ® Set System Change Option.

4. Choose Execute (F8).5. On the System Change Option screen, for the Global Settings field, choose the

Modifiable option. 6. In the lower list, look for namespaces /BI0/ and /BIC/, and set their status to

Modifiable.

© SAP SE Page of


7. Choose Save.8. Choose Back.

ResultThe /BI0/ and /BIC/ namespaces are modifiable.

3.1.5 Allowing LOCAL Software Component to be Modified

UseIn a production system, you must set the system settings for the LOCAL software component to modifiable. This activity is only relevant in production systems. For development and test systems you can skip this activity.



3. On the Transport Organizer Tools screen, select the folders: Transport Organizer Tools ® Administration ® Set System Change Option.

4. Choose Execute (F8).5. On the System Change Option screen, in the Software Component list, look for LOCAL

(Local Developments (No Automatic Transport)), and set its status to Modifiable.6. Choose Save.7. Choose Back.

ResultThe LOCAL software component is modifiable.

3.1.6 Creating ABAP Package for BI Content

UseIf your system is a development and configuration system, create an ABAP package to store and transport runtime generated during BI Content activation.



Application menu Tools ® ABAP Workbench ® Overview ® Object Navigator

3. On the Object Navigator screen, choose the Repository Browser.4. Select the type Package from the dropdown list.5. Below the Package field, enter the package name, for example, ZCEI_BW_CONTENT.6. Choose ENTER.7. On the Create Pack. dialog box, choose Yes.8. On the Create Package dialog box, maintain the following values:

Field name Value

Package ZCEI_BW_CONTENT

© SAP SE Page of


Short Description

Package for yMKT BI Content

Software Component

HOME

Transport Layer <choose an appropriate transport layer so that you can transport your settings to the relevant systems.>

Package Type Development Package

9. Choose Continue (Enter).10. On the Prompt for local Workbench Request dialog box, select a workbench request.11. Choose Continue (Enter).12. Choose Back.

ResultAn ABAP package has been created to store runtime objects generated during BI content activation.

3.1.7 Creating ABAP Package for OData Services

UseIf your system is a development and configuration system, create an ABAP package to store and transport runtime objects generated during OData services activation.

If your system is a quality or production system, you can skip this chapter. Also, if you are activating this solution in a demo environment and you don’t plan to transport configurations to other systems, you can skip this chapter and use the local temporary package $TMP.



Application menu Tools ® ABAP Workbench ® Overview ® Object Navigator

3. On the Object Navigator screen, choose the Repository Browser.4. Select the type Package from the dropdown list.5. Below the Package field, enter the package name, for example, ZCEI_ODATA.6. Choose ENTER.7. On the Create Pack. dialog box, choose Yes.8. On the Create Package dialog box, maintain the following values:

Field name Value

Package ZCEI_ODATA

Short Description

Package for Hybris Mkt. OData Services

Software Component

HOME

Transport Layer <choose an appropriate transport layer so that you can

© SAP SE Page of


transport your settings to the relevant systems.>

Package Type Development Package

9. Choose Continue (Enter).10. On the Prompt for local Workbench Request dialog box, select a workbench request.11. Choose Continue (Enter).12. Choose Back.

ResultAn ABAP package has been created to store runtime objects generated during OData services activation.

3.2 Checking Virus Scan ProfilesUseSAP NetWeaver Gateway is included in the SAP Hybris Marketing installation and by default installed on the system. For the purpose of the SAP Hybris Marketing rapid-deployment solution, the local SAP NetWeaver Gateway is used. It is activated automatically during initial setup of SAP Hybris Marketing.

If you must implement an alternative scenario (for example, using SAP NetWeaver Gateway on a different server), refer to the SAP Help Portal:http://help.sap.com/nwgateway ® Configuration and Deployment Information ® Configuration Guide ® SAP NetWeaver Gateway Configuration Guide ® OData Channel Configuration ® Connection Settings on the SAP NetWeaver Gateway Hub System ® Connection Settings: SAP NetWeaver Gateway to SAP Systems.

In this activity you make sure that an appropriate virus scan profile is defined. Virus scan must be correctly configured to grant proper system security. Make sure that your system administrator has defined an appropriate virus scan profile. Details how to define a profile can be found in the security guide at http://help.sap.com/mkt ® Security Information ® Security Guide ® Securing Information ® Virus Scan Profile (ABAP).

Procedure1. Log on to the SAP Hybris Marketing system using the SAP GUI.2. Access the activity using one of the following navigation options:


SAP IMG menu SAP NetWeaver ® SAP Gateway ® OData Channel ® Administration ® General Settings ® Define Virus Scan Profiles

3. On the SAP NetWeaver Gateway Virus Scan Profile Configuration screen, check that the profile defined by your system administrator is specified in the Virus Scan Profile field.

In particular cases, such as test or demo systems, after careful evaluation of system security risk, you may decide not to install virus scan software.In this case, disable the virus scan:

a. Choose Virus Scan Switched Off.b. Choose Execute (F8).

This practice is strongly discouraged in case of production systems.

© SAP SE Page of


http://help.sap.com/nwgateway


ResultVirus scan is properly configured.

3.3 Integration Settings for SAP CRM (Optional)

3.3.1 Creating RFC User in SAP CRM for Hybris Marketing (Optional)

UseThis activity is only relevant if you want to integrate SAP Hybris Marketing with SAP CRM so that you can, for example, replicate target groups from SAP Hybris Marketing to SAP CRM. To enable SAP Hybris Marketing to access SAP CRM, you must create an RFC user in the SAP CRM system.

This chapter is only relevant if you want to use the integration scenario between SAP CRM and SAP Hybris Marketing. If not, skip the chapter. You can set up the integration to SAP CRM at a later point in time by implementing the Integration into SAP CRM for Hybris Marketing (CEM) building block. The RFC user is also described in that building block.

Procedure1. Logon to SAP CRM, using the SAP GUI.2. Access the activity using one of the following navigation options:

Transaction code SU01

SAP CRM menu Architecture and Technology ® System Administration ® Administration ® User Maintenance ® Users

3. In the User field, enter CEI_USER.4. Choose Create (F8).5. On the Maintain User screen, maintain the following values:

Address

Last Name CEI_USER

Function RFC User for SAP CEI

Logon Data

User Type Communications Data

Password <Define your password>, for example, remote

Repeat Password <Repeat your password>

Defaults

Logon Language EN

Profiles

Profiles SAP_ALL, SAP_NEW

The SAP_ALL profile grants all SAP authorizations. It is not a mandatory profile for the RFC user. Instead of SAP_ALL, you can assign other authorization profiles according to your security concept

© SAP SE Page of


for RFC users.

6. Save your entries (Ctrl + S).

Alternative settings are possible concerning authorizations of this user. The proposed security setup will be sufficient in many cases, since the user has full rights, but cannot perform a dialogue logon.The data exchange concerning target group integration happens via the SAP CRM Middleware, in a way that is similar to the one used in the communication between SAP CRM and SAP ERP.

ResultYou have successfully created an RFC system user in SAP CRM.

3.3.2 Creating RFC Destination in Hybris Marketing for SAP CRM (Optional)

UseTo enable target group replication between SAP Hybris Marketing and SAP CRM, an RFC destination has to be defined in the SAP NetWeaver server for SAP Hybris Marketing, pointing to the SAP CRM system.

This chapter is only relevant if you want to use the integration scenario between SAP CRM and SAP Hybris Marketing. If not, skip the chapter. You can set up the integration to SAP CRM at a later point in time by implementing the Integration into SAP CRM for Hybris Marketing (CEM) building block. The RFC destination is also described in that building block.

The RFC destination described below is different from the one described in the SAP Landscape Transformation Server Settings (CET) building block. If you use both the integration to SAP CRM scenario, and the data replication via SAP Landscape Transformation Replication Server, you need both RFC destinations.

Procedure1. Log on to the SAP Hybris Marketing system using the SAP GUI.2. Access the activity using one of the following navigation options:


Application menu Tools ® Administration ® Administration ® Network ® RFC Destinations

3. Choose Create (F8).4. Maintain the following values:

Field Entry

RFC Destination <CRM system name>CLNT<client>_CEI, for example, CS7CLNT200_CEI

Connection Type 3 (Connection to ABAP system)

Description <Enter a description>, for example, SAP CRM Destination

© SAP SE Page of


5. Choose Enter.

Technical settings

Load Balancing No

Target Host <Enter the target SAP CRM system>

Instance No. <Instance No. of the SAP CRM system>

Logon & Security

Language <Relevant language>, for example, EN

Client <Relevant CRM client> for example, 100

User <Enter the previously created user in SAP CRM> for example, CEI_USER

Password <Enter the password for the CEI_USER user> (for example: remote)

Trust Relationship No

Status of Secure Protocol

Inactive

Unicode

Communication Type with Target System

Set Unicode flag if Unicode test has been executed successfully. This test can be performed by choosing Utilities ® Test ® Unicode Test in the menu. The RFC destination has to be saved first before the test can be performed. An information message appears (for example: Target is a Unicode system (character size 2)).

6. Save (Ctrl + S) your RFC destination.7. You can now test your newly created RFC connection using the Connection Test button.

You can also test the RFC connection following the menu path Utilities ® Test. Then you can choose Connection Test or Authorization Test. The connection test performs only a technical test (Host, IP Address) of the target system as the authorization test performs an invisible logon to the target system using the maintained user and password of the RFC destination.

ResultYou have successfully created the RFC destination in CEI for the SAP CRM system.

3.4 Configuration of Operational Analytics and Easy Query Environment

This chapter describes the implementation steps required to configure operational analytics and the easy query environment. These capabilities are required to activate SAP NetWeaver BI content for SAP Hybris Marketing. You only must implement the settings described in the following sub chapters if your BW client is not the same as the one in which Hybris Marketing is set up. If you use the same client for both BW and SAP Hybris Marketing, skip this chapter including all sub chapters, as the CUAN_INITIAL_SETUP task list (“technical configuration”) will carry out these steps automatically.

Only if you have one client for BW and another client for Hybris Marketing, maintain the relevant settings manually as described in the following sub chapters.

© SAP SE Page of


3.4.1 Activating SICF Services

UseTo enable the activation of the BI content that is required for SAP Hybris Marketing, you must first activate certain services within the Internet Communication Framework to enable the access to the needed browser based (Web Dynpro) configuration views.

Procedure1. Log on to the SAP Hybris Marketing system (Hybris Marketing client) using the SAP GUI.

2. Access the transaction choosing the following navigation option:

Transaction code SICF

Application menu Tools ® Administration ® Administration ® Network ® HTTP Service Hierarchy Maintenance

3. On the Maintain Services screen, choose Hierarchy Type: SERVICE.4. Choose Execute.5. On the Maintain service screen, expand the service nodes listed below one after the

other.6. Right-click the service and choose Activate Service (or Activate Link).7. Activate the following services (or links) for default_host:

/sap/bc/webdynpro/sap/appl_soap_management/sap/bc/webdynpro/sap/esh_admin_ui_component/sap/bc/webdynpro/sap/esh_eng_modelling/sap/bc/webdynpro/sap/esh_eng_wizard/sap/bc/webdynpro/sap/esh_search_results_ui/sap/bc/webdynpro/sap/WDA_EQ_manager/sap/bc/webdynpro/sap/wdhc_help_center/sap/es/cockpit/sap/es/saplink/sap/es/search/sap/sap/public/bc /sap/public/bc/ur /sap/public/bc/icons /sap/public/bc/icons_rtl /sap/public/bc/webicons /sap/public/bc/pictograms /sap/public/bc/webdynpro/sap/public/bc/webdynpro/adobeChallenge/sap/public/bc/webdynpro/mimes/sap/public/bc/webdynpro/ssr/sap/public/bc/webdynpro/ViewDesigner/sap/public/myssocntl

Instead of activating these services manually in transaction SICF, alternatively you can make use of the SAP_BASIS_ACTIVATE_ICF_NODES task list in transaction STC01.

ResultThe Web Dynpro services for the required configuration views have been activated.

© SAP SE Page of


3.4.2 Configuring Operational Data Provisioning The following sub chapters provide the configuration steps to enable Operational Data Provisioning.

For more information, see the SAP Help Portal: http://help.sap.com/netweaver ® SAP NetWeaver Platform ® Application Help ® Function-Oriented View ® Search and Operational Analytics ® Operational Data Provisioning ® Configuring Operational Data Provisioning.

3.4.2.1Basic Configuration for Operational Analytics

UseThe purpose of this activity is to execute the basic configuration for operational analytics.

Procedure1. Log on to the SAP Hybris Marketing system (Hybris Marketing client) using the SAP GUI.2. Access the activity using the following navigation options:


IMG menu SAP NetWeaver ® Search and Operational Analytics ® Operational Data Provisioning for Operational Analytics ® Basic Configuration for Operational Analytics

3. On the Basic Configuration for Operational Analytics screen, in the BW Client field, enter the client number of the BW Client in the current system.

If you have separate clients in your system, one client for BW and one client for Customer Engagement Intelligence, enter the number of the BW client.

4. Choose Execute (F8).5. In the Display Logs screen, review the log and verify that no errors occurred.6. Choose Back twice.

ResultThe basic configuration for operational analytics has been performed.

3.4.2.2Specifying the Client for Modeling

UseThe purpose of this activity is to specify the client for modeling.

Procedure1. Log on to the SAP Hybris Marketing system (Hybris Marketing client) using the SAP GUI.2. Access the activity using the following navigation options:


IMG menu SAP NetWeaver ® Search and Operational Analytics ® Operational Data Provisioning for Operational Analytics ® Specify Client for Modeling

© SAP SE Page of

http://help.sap.com/netweaver


3. On the Define Modeling Client screen, in the Modeling Client field, enter the client number of the BW Client in the current system.

4. In the Destination field, maintain the RFC destination for the BW client.5. Choose Execute (F8).6. Confirm the dialog box that appears.7. Choose Back.

ResultThe client for modeling has been specified.

3.4.3 Configuring Easy Query Environment

3.4.3.1Checking Configuration of the Service Implementation Workbench

UseIn this activity you define the settings for the Service Implementation Workbench (SIW).

Procedure1. Log on to the SAP Hybris Marketing system (Hybris Marketing client) using the SAP GUI.2. Access the activity using the following navigation option:


3. On the Maintain Table View: Initial Screen, in Table/View field, choose the VSIW_LANDSCAPE view.

4. Choose Maintain.5. Make sure that the following entry exists. If required, create a new entry, or modify an

existing one.

Field name Value

Landscape ID LOCAL_WO_ESR

Description Local without ESR

RFC Destination <blank>

6. Choose Save. 7. Choose Back.

On the Maintain Table View: Initial screen, in Table/View field, choose VSIW_CONFIG view.

8. Choose Maintain.9. Make sure that the following entries exist. If required, create a new entry or modify an

existing one.

Field name Value

Configuration ID EQ_LEVEL_SPACE

Description Configuration for easy queries

Config Setup Class CL_EQ_SIW_LEVEL_SPACE_CFG

Landscape ID LOCAL_WO_ESR

Display Only <unchecked>

10. Choose Save. 11. Choose Back.

© SAP SE Page of


ResultThe required Service Implementation Workbench settings are maintained.

3.4.3.2SOAP Settings for Easy Query Management

UseA standard profile must be configured in the Service Oriented Architecture (SOA) Manager.

Procedure1. Log on to the SAP Hybris Marketing system (Hybris Marketing client) using the SAP GUI.2. Access the activity using one of the following navigation options:

Transaction code SOAMANAGER

3. On the SOA Management screen, choose Technical Administration Tab.4. Choose Profiles. 5. Check if a DEFAULT_PROFILE entry exists. In case it does not exist, create a new profile

using the following data:

Field name Value

Name DEFAULT_PROFILE

Description Local Default Profile

Authentication Method Single Sign-on using SAP Assertion Ticket

6. Choose Save. 7. Close the browser window.

ResultThe default profile is configured.

3.4.3.3Settings for Background Processing

UseIn this activity you perform the basic settings required for Easy Query Management.

If you have separate clients in your system, one client for BW content and one client for Hybris Marketing content, execute this activity in the BW client.

Procedure1. Log on to the SAP Hybris Marketing system (BW client) using the SAP GUI.2. Access the activity using one of the following navigation options:

Transaction code SBGRFCCONF

3. On the bgRFC Configuration screen, choose the Define Supervisor Dest. tab page.4. On the Define Supervisor Dest. tab page, choose Create.5. In the Create RFC Destination for Supervisor dialog box, maintain the following data:

Field name Value

Destination Name BGRFC_SUPERVISOR

Create User <checked>

© SAP SE Page of


User Name BGRFC_SUPER

Password <Enter a password> for example, remote

6. Choose Save.7. On the bgRFC Configuration screen, choose Save (Ctrl+S).

A user BGRFC_SUPER has just been created. The assigned authorization role is SAP_BC_BGRFC_SUPERVISOR.

8. On the bgRFC Configuration screen, choose the Define Inbound Dest. tab page.9. On the Define Inbound Dest. tab page, choose Create.10. On the Configure Inbound Destination screen, maintain the following settings:

Field name Value

Inb. Dest. Name QD_EQ_LOCAL

Add Queue Prefix EQQD_

11. In the Add Queue Prefix screen area, choose Add 12. Choose Save.13. On the Scheduler: Destination tab page, choose Create.14. In the bgRFC Configuration dialog box, choose Inbound.15. On the Create Scheduler Settings for Inbound Destination screen, choose the

QD_EQ_LOCAL destination.16. Choose Save.17. Choose Save (Ctrl+S) again.18. Choose Back.

ResultYou have maintained the basic settings for easy queries.

© SAP SE Page of

bb installation guidesapidp/... · web viewcovered in this configuration guide. carefully read the...

Documents