SAP Real-Time Offer Management Release 7.1 SP02 Public

Installation Guide CONFIDENTIAL SAP Real-Time Offer Management Document Version: 1.0 – 2016-06-10

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

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

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER.

Document History

Caution To install SAP Real-Time Offer Management (RTOM), it is highly recommended that you follow the procedure described in SAP Note 1690163 -RTOM 71 Ehp1 Installation - Best Practice: http://service.sap.com/notes Number 1690163 . This note will provide you with the most up-to-date information for installing RTOM. Before you start, make sure you have the latest version of this document. You can find the latest version at the following location: http://service.sap.com/instguides Focused Business Solutions SAP Real-Time Offer Management . The following table provides an overview of the most important document changes.

Version Date Change

1.0 10-06-2016 Initial version

Table of Contents

1 Introduction ...... 5

2 Real-Time Offer Management Information...... 6 2.1 Language Support ...... 6 2.2 Real-Time Offer Management Installation Components Overview ...... 6 2.2.1 SAP Real-Time Offer Management Core ...... 6 2.2.2 SAP Real-Time Offer Management SAPIC or Telco ...... 7 2.2.3 SAP Real-Time Offer Management Utilities ...... 7

3 Installation Procedure ...... 8 3.1 Instance Components Prerequisites...... 8 3.1.1 Prerequisites Summary ...... 9 3.1.2 Prerequisites Details ...... 9 3.2 Verifying Language Settings ...... 17 3.3 Verifying Server Connections...... 17 3.4 Verifying Authentication Credentials ...... 18 3.5 Uninstalling SAP Real-Time Offer Management Core or SAPIC ...... 19 3.5.1 Uninstall Procedure ...... 19 3.5.2 Finalizing Actions ...... 20

4 Installation ...... 21 4.1 Component Installation ...... 21 4.1.1 Installing SAP Real-Time Offer Management Core ...... 21 4.1.2 Installing SAP Real-Time Offer Management SAPIC/Telco/Utilities ...... 27 4.2 Distributed Installation ...... 30

5 Post Installation ...... 32

1 Introduction

To install SAP Real-Time Offer Management (RTOM), it is highly recommended that you follow the procedure described in SAP Note 1690163 -RTOM 71 Ehp1 Installation - Best Practice: http://service.sap.com/notes Number 1690163 . This note will provide you with the most up-to-date information for installing RTOM.

Information Available in SAP Service Marketplace

Description Internet Address Title

SAP Notes http://service.sap.com/notes -

Released platforms http://service.sap.com/platforms -

System sizing http://service.sap.com/sizing Quick Sizer tool

Front-end installation http://service.sap.com/instguides Front End Installation Guide

Security http://service.sap.com/security -

2 Real-Time Offer Management Information

2.1 Language Support

SAP Real-Time Offer Management offers the following language support. The user interface of all RTOM applications (Log Viewer, Configuration Manager, and RTOM application toolkit) is available in the following languages:  English  German  French  Spanish  Japanese  Italian  Portuguese In the input fields and data processing (for example, business partner data), all single and double byte languages are supported.

2.2 Real-Time Offer Management Installation Components Overview

2.2.1 SAP Real-Time Offer Management Core

Run SAPInst.exe, provided on the CD, to execute the Real-Time Offer Management installation. The installation consists of the following installation options:  Install New System  Lifecycle Management Options These installation options are outlined in the following section.

Install New System

This is the SAP Real-Time Offer Management Core Installation and has the following components:  RTOM DB Installs the Real-Time Offer Management database  RTOM Server Installs the Real-Time Offer Management engine  RTOM CIC Adaptor

Installs the interaction center site adaptor that includes the Real-Time Offer Management router, which routes each individual event to the correct Real-Time Offer Management instance  RTOM App Toolkit Installs the Real-Time Offer Management Application Toolkit

Lifecycle Management Options

This option is the uninstall package.

2.2.2 SAP Real-Time Offer Management SAPIC or Telco

Install New System

This is the SAP Real-Time Offer Management SAPIC/Telco Installation and has the following components:  RTOM DB Update for SAPIC/Telco Creates configuration files on your local system. These configuration files are specific to the SAPIC/Telco integrations.  RTOM Integration for SAPIC/Telco Installs server components for Real-Time Offer Management integration with SAPIC/Telco  RTOM CIC Integration for SAPIC/Telco Installs the site adaptor, which is specific to SAPIC/Telco, which comprises the Real-Time Offer Management router, which routes each individual event to the correct Real-Time Offer Management instance

Lifecycle Management Options

This option is the uninstall package.

2.2.3 SAP Real-Time Offer Management Utilities

Run SAPInst.exe, provided on the CD, to execute the Real-Time Offer Management installation. The installation consists of the Install New System installation option.

Install New System

This is the SAP Real-Time Offer Management utilities installation, which includes the RTOM DB Update for Utilities component. It creates configuration files on your local system. These configuration files are specific to the SAP for Utilities integration. It is not possible to uninstall the database using SAPinst.

3 Installation Procedure

1. Design the landscape installation.

Note If you wish to have a distributed installation, you have to install all components for each package on the same machine. This means that you need to verify all prerequisites for all components in each installation package. If you are installing an SAP Solution (SAPIC, Telco, or Utilities), consider the following: o The RTOM DB Update component installation consists of configuration files that are specific for a solution. Therefore, it should be installed on the machine where the Real-Time Offer Management server is installed. o Each Real-Time Offer Management server, running the integration components, should have the RTOM core server installed. o The CIC adaptor and the RTOM server can be installed as many times as desired. 2. Verify the prerequisites for each component that is installed, such as the following: o Real-Time Offer Management Database o Real-Time Offer Management Server o Real-Time Offer Management CIC Adaptor o Real-Time Offer Management Application Toolkit o Real-Time Offer Management Database Update for SAPIC/Telco/Utilities o Real-Time Offer Management Integration for SAPIC/Telco o Real-Time Offer Management CIC Integration for SAPIC/Telco 3. Verify the following prerequisites: o Language settings o Server connections o Authentication credentials 4. Run the Real-Time Offer Management installation.

Note If you wish to install all components on the same machine, see Component Installation. If you wish to install components on a distributed environment, see Distributed Installation. 5. Execute the post-installation steps.

3.1 Instance Components Prerequisites

The prerequisites for each installation component are summarized in the Prerequisites Summary section. In the Prerequisites Details section, there is a detailed explanation of each prerequisite.

3.1.1 Prerequisites Summary

The following table indicates the topics for which prerequisites are defined.

3.1.2 Prerequisites Details

1. Operating System Microsoft Windows 2003 x64 SP2 or Microsoft Windows 2008 for x64 version This operating system is required when installing any of the following components: o Real-Time Offer Management Server (RTOM Server) o Real-Time Offer Management Database (RTOM DB) o Real-Time Offer Management Application Toolkit (RTOM Toolkit) o Real-Time Offer Management CIC Adaptor (CIC Adaptor) o Real-Time Offer Management Integration for SAPIC/Telco (SAPIC/Telco Integration) o Real-Time Offer Management Database Update for SAPIC/Telco/Utilities (DB Update) o Real-Time Offer Management CIC Integration for SAPIC/Telco (SAPIC/Telco CIC) 2. .Net Framework Microsoft .Net Framework 2.0 SP02 This .Net Framework is required when installing any of the following components:

o Real-Time Offer Management Server (RTOM Server) o Real-Time Offer Management CIC Adaptor (CIC Adaptor) o Real-Time Offer Management Integration for SAPIC/Telco (SAPIC/Telco Integration) o Real-Time Offer Management CIC Integration for SAPIC/Telco (SAPIC/Telco CIC) 3. Microsoft Internet Information Services (IIS) Microsoft IIS (an optional component of Microsoft Windows 2003 Server – under Application Server) This IIS is required when installing any of the following components: o Real-Time Offer Management Server (RTOM Server) o Real-Time Offer Management CIC Adaptor (CIC Adaptor) o Real-Time Offer Management Integration for SAPIC/Telco (SAPIC/Telco Integration) o Real-Time Offer Management CIC Integration for SAPIC/Telco (SAPIC/Telco CIC)

Recommendation We recommend that you install security certification on the IIS and use HTTPS protocol and not HTTP. This will assure a higher level of security for RTOM Web applications.Put your recommendation here. 4. IDN Mitigation Microsoft Internationalized Domain Names (IDN) Mitigation APIs are required for the normalization process required by the SAP Normalization Standard. To install IDN mitigation, run idndl.amd64.exe for x64 OS. The idndl.amd64.exe is part of the idndlpackage.exe and is available at http://www.microsoft.com. This IDN mitigation is required when installing any of the following components: o Real-Time Offer Management Server (RTOM Server) o Real-Time Offer Management CIC Adaptor (CIC Adaptor) o Real-Time Offer Management Integration for SAPIC/Telco (SAPIC/Telco Integration) o Real-Time Offer Management CIC Integration for SAPIC/Telco (SAPIC/Telco CIC) 5. Visual C++ 2005 Microsoft Visual C++ 2005 SP1 Redistributable is required for the system code to be able to run properly. To install it, run vcredist_x64.exe for x64 OS. This version of Visual C++ 2005 is required when installing any of the following components: o Real-Time Offer Management Server (RTOM Server) o Real-Time Offer Management CIC Adaptor (CIC Adaptor) o Real-Time Offer Management Integration for SAPIC/Telco (SAPIC/Telco Integration) o Real-Time Offer Management CIC Integration for SAPIC/Telco (SAPIC/Telco CIC) 6. Active Server Pages (ASP) Make sure ASP is installed by doing the following: For Microsoft Windows 2003, perform the following steps: 1. Choose Control Panel Add or Remove Programs . 2. Choose Add/Remove Windows Components. 3. Choose Application Server IIS World Wide Web . 4. Select Active Server Pages. For Microsoft Windows 2008, perform the following steps: 5. Choose Control Panel Programs and Features .

6. Click Turn windows features on or off. 7. In the Server Manager window, choose Roles. In the list of roles, you must see that ASP is installed. ASP is required when installing any of the following components: o Real-Time Offer Management Server (RTOM Server) o Real-Time Offer Management CIC Adaptor (CIC Adaptor)

ASP.NET

ASP.NET is part of the .NET Framework. For Microsoft Windows 2003, perform the following steps: 1. Choose IIS Web Site . 2. Right-click Default Web Site and go to Properties. Make sure that the ASP.NET tab exists. For Microsoft Windows 2008, perform the following steps: 3. Choose Control Panel Programs and Features . 4. Click Turn windows features on or off. 5. In the Server Manager window, choose Roles. In the list of roles, you must see that ASP.NET is installed.

ASP.NET is required when installing any of the following components:  Real-Time Offer Management Server (RTOM Server)  Real-Time Offer Management CIC Adaptor (CIC Adaptor)  Real-Time Offer Management Integration for SAPIC/Telco (SAPIC/Telco Integration)  Real-Time Offer Management CIC Integration for SAPIC/Telco (SAPIC/Telco CIC)

Web Service Extension

Enable the following Web service extensions:  Active Server Page  Internet Data Connector  Server Side Includes  ASP.Net

For Microsoft Windows 2003, perform the following steps: 6. Choose Control Panel Administrative tools IIS Web Site Extension folder . The list of Web Service Extensions is displayed. 7. Right-click each Web service extension that is required and select Allow.

For Microsoft Windows 2008, perform the following steps: 8. Run the file webdav_x64_75.msi (you can download the file at http://www.microsoft.com). 9. Choose Control Panel Programs and Features .

You must see WebDAV 7.5 For IIS 7.0.

The Web service extensions above are required when installing any of the following components:  Real-Time Offer Management Server (RTOM Server)  Real-Time Offer Management CIC Adaptor (CIC Adaptor)

Message Queuing

Message queuing is an optional component of Microsoft Windows 2003 Server – under Application Server. To activate message queuing for Microsoft Windows 2003, perform the following steps: 1. Open Add or Remove Programs. 2. Select Add/Remove Windows Components. 3. Select Application Server Components. 4. Choose Details. 5. Select the Message Queuing checkbox. 6. Choose Details. 7. Select the Only Core Functionality checkbox. 8. Choose OK. 9. Choose Next. The installation starts.

To activate message queuing for Microsoft Windows 2008, perform the following steps: 10. Choose Control Panel Programs and Features . 11. Click Turn windows features on or off. 12. Choose Features Add Features . 13. Select Message Queuing and choose Install. 14. Choose Control Panel Programs and Features . 15. Click Turn windows features on or off. 16. In the Server Manager window, choose Features.

In the list of features, you must see Message Queuing. Message queuing is required when installing any of the following components:  Real-Time Offer Management Server (RTOM Server)  Real-Time Offer Management CIC Adaptor (CIC Adaptor)  Real-Time Offer Management CIC Integration for SAPIC/Telco (SAPIC/Telco CIC) .NET Directory

Note .NET directory is not required if the installation runs on Microsoft Windows 2008.

Add the .NET directory to the environment variable Path by performing the following steps: 1. Open the System properties window by right-clicking My Computer.

2. Choose the Advanced tab and choose Environment Variable. 3. Open the system variable Path. 4. Add the .NET directory path. For example, in a typical installation folder for .NET, add the path C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727.

Note If there is already another value, add a semicolon (;) before the directory path.

This .NET directory is required when installing any of the following components:  Real-Time Offer Management Server (RTOM Server)  Real-Time Offer Management CIC Adaptor (CIC Adaptor)

SAP Authentication Files

If you are using SAP NetWeaver authentication (this is the default) to run RTOM in an SAP CRM scenario, do the following: 1. Verify that saplogon.ini is installed on the server and has the relevant SAP system information to enable authentication with the correct SAP system. The file format used is that of SAP Logon 6.40 and up. This file must be located in the :WINDOWS folder and set to work with the correct SAP NetWeaver authentication. The SAP system information must be located under the attribute [MSSrvName] in the saplogon.ini file. If this attribute is not updated, a manual update is required. 2. Verify that sapmsg.ini is located in the :WINDOWS folder. This file contains the message server details for SAP CRM. 3. Verify that the service is located in the :WINDOWS\ system32\drivers\etc folder and contains the entry for the application to connect to the SAP CRM system. The entry must have the following format: sapms36/tcp. For more information about authentication configuration and settings, see the SAP Customer Relationship Management Security Guide.

These SAP authentication files are required when installing the Real-Time Offer Management Integration for SAPIC/Telco (SAPIC/Telco Integration) component.

SQL 2005

If you intend to install RTOM DB on SQL 2005, verify that Microsoft SQL 2005 is installed with the latest SP. This version of SQL 2005 is required when installing any of the following components:  Real-Time Offer Management Database (RTOM DB) of SQL server type  Real-Time Offer Management Database Update for SAPIC/Telco/Utilities (DB Update)

Oracle

1. Ensure that the Oracle database version 10.2 is installed with the database character set Unicode Standard UTF-8.

Note In the Oracle installation step where you select the template to create the database, choose Custom Database. This will allow you to set the UTF-8 parameter for the database character set (select the Use Unicode (AL32UTF8) radio button) and for the national characters set (select UTF8 - Unicode 3.0 UTF-8 Universal character set). To make sure that the character set is configured correctly, run the following SQL commands at the end of the installation: 1. SQL> select * from nls_database_parameters where parameter = ‘NLS_CHARACTERSET’ Ensure that the result is AL32UTF8. 2. SQL> select * from nls_database_parameters where parameter = ‘NLS_NCHAR_CHARACTERSET’ Ensure that the result is UTF8.

Note The tablespaces in the following steps are needed if you are installing an Oracle database for the first time. If you already have an Oracle database installed and have created the tablespaces, you do not need to perform the steps below. 1. Create the tablespace PSAPUSER by running the following SQL script: CREATE SMALLFILE TABLESPACE "PSAPUSER" DATAFILE 'F:\oracle\product\10.2.0\oradata\orcl\PSAPUSER' SIZE 100M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;.

Note The path F:\oracle\product\10.2.0\oradata\orcl\ must be changed according to your Oracle installation 2. To alter the tablespace that was created, run the following SQL script: ALTER DATABASE DEFAULT TABLESPACE "PSAPUSER"; 3. Create the tablespace PSAPTEMP by running the following SQL script: CREATE SMALLFILE TEMPORARY TABLESPACE "PSAPTEMP" TEMPFILE 'F:\oracle\product\10.2.0\oradata\orcl\PSAPTEMP' SIZE 100M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Note The path F:\oracle\product\10.2.0\oradata\orcl\ must be changed according to your Oracle installation.

4. To alter the tablespace that was created, run the following SQL script: ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "PSAPTEMP"; 5. Ensure that you have the Oracle administrator user (known as the super admin user) assigned. 6. Ensure that the sqlplus.exe utility has been installed as \oracle\CRM\102\BIN\sqlplusw.exe. 7. Set the ORACLE_HOME environment variable to the Oracle home path by performing the following steps: 1. Open the System properties window by right-clicking My Computer. 2. Choose the Advanced tab and choose Environment Variable. 3. Open the system variable ORACLE_HOME (if this variable does not exist, create it). 4. Set the Oracle home path (for example, C:\oracle\\102).

8. If the RTOM application server is running on a server that is different from the Oracle server, perform the following steps: 1. Copy the file tnsnames.ora from the database server to OracleInstalledDir\NETWORK\ADMIN on the RTOM application server. 2. Edit the file tnsnames.ora according to the installed platform (server name and database name).

Syntax For example: 1. DBName = 2. (DESCRIPTION = 3. (ADDRESS_LIST = 4. (ADDRESS = (PROTOCOL = TCP)(HOST = OracleServer address)(PORT = 1521)) 5. ) 6. (CONNECT_DATA = 7. (SERVICE_NAME = DBname) 8. ) 9. )

This Oracle version is required when installing any of the following components:  Real-Time Offer Management Database (RTOM DB) of the Oracle type  Real-Time Offer Management Database Update for SAPIC/Telco/Utilities (DB Update)

MaxDB

1. Ensure that the SAP MaxDB version 7.7.2.18b or 7.8.01.15 is installed. 2. Ensure that you have the MaxDB administrator user (known as the super admin user) assigned. This version of MaxDB is required when installing any of the following components:  Real-Time Offer Management Database (RTOM DB) of the MaxDB type  Real-Time Offer Management Database Update for SAPIC/Telco/Utilities (DB Update)

Path to loadercli

The path to loadercli must be set on the machine from which the installation is executed. To check if the path is set, in the command prompt, run the loadercli command. If the path has not been defined, the following message is displayed: 'loadercli' is not recognized as an internal or external command, operable program or batch file. In this case, contact your system administrator. The path to loadercli must be set when installing the Real-Time Offer Management Database (RTOM DB) of MaxDB type.

Database Client

The database client specified below is required when installing any of the following components: Real-Time Offer Management Server (RTOM Server) Real-Time Offer Management CIC Integration for SAPIC/Telco (SAPIC/Telco CIC) 1. If you are not installing the RTOM application server on the database server, run the client installation on the RTOM server to enable the connection between the RTOM server and RTOM database machines.

2. If you are using an Oracle database, run the Oracle client installation version 11.1.06.0 (if any previous Oracle client is installed, remove it) on the RTOM server and update tnsnames.ora. If you are using a different client version, the Open Database Connectivity (ODBC) connection has to be created manually as described in the post-installation steps. 3. After the client has been installed, do the following: 1. Verify that the folder Oracle11Client was created by the client installation. 2. Verify that the first system variable of the PATH system variable list is Oracle11Client, by performing the following steps: 1. Choose My Computer Properties Advanced . 2. Choose Environment Variable. 3. In System Variables, find the variable Path. 4. Verify that the first variable is \Oracle11Client. 4. Verify that the environment variables ORACLE_HOME and TNS_ADMIN are defined and they are set to \Oracle11Client, by doing the following: 1. Choose My Computer Properties Advanced . 2. Choose Environment Variable. 3. In System Variables, find the variables ORACLE_HOME and TNS_ADMIN. 4. Verify that the variable values are \Oracle11Client. 5. If any of the previous manual steps are required, reboot the server.

If you are using SAP MaxDB, install the same version of the SAP MaxDB (Unicode) client as the version of the SAP MaxDB server that is installed on the database server (7.7.2 or 7.8.01). If you are using Microsoft SQL 2005, install the SQL Native client. OLE DB Provider for ODBC

Note OLE DB Provider for ODBC is not required if the installation runs on Microsoft Windows 2008.

If you are installing RTOM DB on Oracle or MaxDB, install the Microsoft OLE DB Provider for ODBC (MSDASQL) by running WindowsServer2003.WindowsXP-KB948459-v2-x64-ENU.exe. The OLE DB Provider for ODBC is required when installing the Real-Time Offer Management Server (RTOM Server) component.

Ajax

To install Microsoft ASP .NET 2.0 AJAX Extensions 1.0, run ASPAAJAXExtSetup.msi. This version of Ajax is required when installing the Real-Time Offer Management Application Toolkit (RTOM Toolkit) component.

Path to RegAsm

The path to RegAsm must be set. To check if the path is set, in the command prompt, run the regasm command. If the path has not been defined, the following message is displayed: 'regasm' is not recognized as an internal or external command, operable program or batch file. In this case, contact your system administrator. The path to RegAsm must be set when installing any of the following components:  Real-Time Offer Management Server (RTOM Server)

 Real-Time Offer Management Database (RTOM DB)  Real-Time Offer Management Application Toolkit (RTOM Toolkit)  Real-Time Offer Management CIC Adaptor (CIC Adaptor)

3.2 Verifying Language Settings

All machines with RTOM package components installed should be configured with the same regional settings before installation. Refer to the procedure below for verifying that the regional settings are the same.

Caution Any changes to the settings after the system has started up will result in errors and may cause irregular behavior.

Procedure

1. Check that the settings in the following tabs are the same for all machines by performing the following steps: 2. Go to Start Settings Control Panel Regional and Language Options . o Under Regional Options, verify the following: o The language in the Standards and Formats area is the same on all the machines o All the formats for Customize are the same on all the machines o The Location is the same on all the machines 3. Under Advanced, verify that the language for non-Unicode programs is the same on all the machines.

3.3 Verifying Server Connections

1. After all prerequisites have been met, verify that you have a network connection between all servers in the platform. Web services communicate with the real-time decisioning (RTD) engine using Microsoft IIS.

Note This note only applies if you are using RTOM in an SAP CRM scenario. If the IIS on the RTD engine is installed with the default port (1080) and there is a firewall between the interaction center in SAP CRM and the RTD engine server, port 1080 may be blocked. If so, change the setting of the IIS port on the RTD engine server.

2. If you are installing a distributed environment, verify that a power user from the same domain is defined in all machines installed with RTOM. Otherwise, failures will occur when different RTOM servers attempt to communicate.

3.4 Verifying Authentication Credentials

Prerequisites

To install the RTD engine on a server, you need to use the following types of users:  An application administrator user assigned to the administrators group  An application user assigned to the users group and the IIS_WPG group on a Microsoft Windows 2003 server (IIS_USERS on a Microsoft Windows 2008 server).  A Web services user assigned to the users group In this document, these users are referred to as AppAdmin, AppUser, and WSUser. These users can be defined as local users on RTOM machines that have an RTOM component installed or as users that belong to the domain of the organization.

Procedure

1. Create the AppAdmin user by doing the following: 1. Choose Start Settings Control Panel Administrative Tools Computer Management . 2. Open Local Users and Groups Users . 3. Choose Administrative Tools. 4. Create the new AppAdmin user. 5. Open the user properties. 6. Under Member, add the user to the administrators group. 2. Give the AppAdmin user authorization to log on as a service user by doing the following: 1. Choose Start Settings Control Panel Administrative Tools Local Security Policy . 2. Open Local Policies User Rights Assignment . 3. Double-click Log on as a service and add the AppAdmin user to the list. 3. Create the AppUser user by doing the following: 1. Choose Start Settings Control Panel Administrative Tools Computer Management . 2. Open Local Users and Groups Users . 3. Choose Administrative Tools. 4. Create the new AppUser user. 5. Open the user properties. 6. Under Member, add the user to the IIS_WPG group on a Microsoft Windows 2003 server or IIS_USERS on a Microsoft Windows 2008 server. 4. Give the AppUser user authorization to log on as a service user by doing the following: 1. Choose Start Settings Control Panel Administrative Tools Local Security Policy . 2. Open Local Policies User Rights Assignment . 3. Double-click Log on as a service and add the AppUser user to the list. 5. Give the AppUser user full control for the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Security registry keys.

To do so, perform the following steps:

1. In the command prompt, run the regedit command. 2. Choose HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Eventlog , right-click on the registry key, and from the context menu, choose Permissions. 3. Add the AppUser user and allow full control. 4. Choose HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Eventlog Security , right-click on the registry key, and from the context menu, choose Permissions. 5. Add the AppUser user and allow full control. 6. Create the WSUser user by doing the following: 1. Choose Start Settings Control Panel Administrative Tools Computer Management . 2. Open Local Users and Groups Users . 3. Choose Administrative Tools. 4. Create the new WSUser user. 5. Open the user properties. 6. Under Member, add the user to the users group.

3.5 Uninstalling SAP Real-Time Offer Management Core or SAPIC

The following sections describe the process of uninstalling SAP Real-Time Offer Management Core or SAPIC/Telco.

3.5.1 Uninstall Procedure

Prerequisites

You have stopped all RTOM services and COM+.

Procedure

1. Double-click sapinst.exe. The Welcome to SAP RTOM Installation view is displayed. 2. Go to SAP RTOM Lifecycle Management Option . 3. Select Uninstall SAP RTOM Core or Uninstall SAP RTOM SAPIC and click Next. The RTOM Available Packages Components view is displayed. 4. Check all of the packages components and click Next. The RTOM Uninstall List with the checked packages components from the previous step is displayed. 5. Click Next and wait for the uninstall procedure to finish successfully. The RTOM server should now be uninstalled. 6. To uninstall the DB connection, do the following: 1. From the Windows start menu, go to Run, and enter regedit. 2. Go to HKEY_LOCAL_MACHINE SOFTWARE .

3. Select the Ingeneo node and delete it. 7. Delete folders SAP CRM and sapinst_instdir from insatll_dir\Program Files.

3.5.2 Finalizing Actions

To ensure that the uninstall procedure was completed successfully, check that the following have been removed:  RTOM Services from Component Services Services (Local)  RTOM COM+ from Component Services COM+ Applications  Ingeneo node by running the regedit command in the command prompt and then going to HKEY_LOCAL_MACHINE SOFTWARE  Default Web Site components from IIS Web Sites Default Web Sites  Folders SAP CRM and sapinst_instdir from insatll_dir\Program Files

Result

The server is ready for a new RTOM installation.

4 Installation

Caution You must not run more than one installation simultaneously as it may result in unexpected behavior. If you wish to install SAP Real-Time Offer Management Core and SAP Real-Time Offer Management SAPIC/Telco/Utilities, you must wait for one package installation process to complete before starting to install the other package.

4.1 Component Installation

The Real-Time Offer Management installation contains several components (see Real-Time Offer Management Installation Components Overview). Each component can be installed on a different server, unless it is specified otherwise in the steps to install the component.

4.1.1 Installing SAP Real-Time Offer Management Core

The following sections describe the process of installing SAP Real-Time Offer Management Core. The sections are as follows: 1. Initial actions 2. Installing Real-Time Offer Management Database 3. Installing Real-Time Offer Management Server 4. Installing Real-Time Offer Management CIC Adaptor 5. Installing Real-Time Offer Management Application Toolkit 6. Finalizing Actions

4.1.1.1 Initial Actions

1. Double-click sapinst.exe. The Welcome to SAP RTOM Installation view is displayed. 2. Expand nodes: SAP RTOM Install New System . 3. Select SAP RTOM Instance Installation and click Next. The RTOM Core Components view is displayed. 4. Select the component(s) that you wish to install and click Next.

Note The Real-Time Offer Management database can only be installed locally. If a check box is disabled, it indicates that this component is already installed.

4.1.1.2 Installing Real-Time Offer Management Database

1. If you selected the RTOM DB component, the RTOM Installation Root view is displayed. 2. Enter the desired installation root or click Browse... and browse to the desired location. Click Next.

The RTOM Database Creation view is displayed. 3. Select the database type that you wish to install and click Next. o If you select Microsoft SQL Server, the MSSQL Database Creation view is displayed. o If you select Oracle DB, the Oracle Database Creation view is displayed. o If you select SAP MaxDB, the SAP MaxDB Database Creation view is displayed. 4. In the Database Creation view, do the following: o If you selected Microsoft SQL Server in step 3, enter the following parameters: o In the Database Server Host Name/IP Address field, enter the name of the DB machine. o In the Database Name field, enter the name of RTOM database that will be created. o Enter the RTOM database schema. o In the Database User Name field, enter the user name of the AppUser user. Note that the user name is case sensitive.

Note If you wish to enter a local user that is defined on the same machine where you are running the installation, enter the full name of the machine, for example, ILINGENEO34\localUserName. o Click Next. The DB Administrator Account view is displayed. o Select the authentication type of the database user. For Microsoft Windows authentication, select Windows Authentication. If you select Database Authentication, enter the user ID and the password of the applicable user. o Click Next. o If you selected Oracle DB in step 3, do the following: o Enter the following parameters: o In the Database Server Host Name/IP Address field, enter the name of the database machine.

o In the Database Name (SID) field, enter the name of the Oracle database in which the RTOM database will be created. o In the RTOM Database Schema field, enter the name of the RTOM database that will be created and click Next. The DB Administrator Account view is displayed. o In the DB Administrator Account view, enter an Oracle DB administrative user name and password and click Next. o If you selected MaxDB in step 3, enter the following parameters: o In the Database Server Host Name/IP Address field, enter the name of the database machine. o In the Database Name field, enter the database name of the MaxDB database in which the Real-Time Offer Management database will be created. o In the RTOM Database Schema field, enter the name of the Real-Time Offer Management database that will be created and click Next.

Note The name of the schema should: Consist only of upper case letters Not have any spaces Be no longer than 8 characters

The DB Administrator Account view is displayed. o In the DB Administrator Account view, enter MaxDB administrative user name and password (in upper case letters) and click Next. 5. The Parameter Summary view is displayed. Continue to Finalizing Actions.

4.1.1.3 Installing Real-Time Offer Management Server

1. If you selected the RTOM Server component, the RTOM Installation Root view is displayed. 2. Enter the desired installation root or click Browse… and browse to the desired location. Click Next.

Note If there is an existing Real-Time Offer Management (RTOM) installation on this machine, the installation root field displays the existing RTOM installation directory, which cannot be changed. The RTOM Domain Controller Settings view is displayed. 3. Enter the server where the domain controller will be installed on and click Next. The Local Account Permissions view is displayed. 4. Enter a user name and password for the AppAdmin user. The AppAdmin user name is used to access some services and COM+ applications. Click Next. The Administrator Account view is displayed.

Note If you wish to enter a local user that is defined on the same machine where you are running the installation, enter the full name of the machine, for example, ILINGENEO34\localUserName. 5. Enter a user name and password for the AppUser user. The AppUser user name is used to access some services and COM+ applications. Click Next. The Web Service Permitted Account view is displayed. 6. Enter a user name for the WSUser user, as defined in the prerequisites. This user will be used for accessing secure RTOM Web services. Click Next. The Server Default Language view is displayed. 7. Select the default user interface language and click Next. The Instance Name view is displayed. 8. Enter any text to describe the Instance Name and click Next.

Note One instance must be named: Default. The Authentication view is displayed. 9. Select SAP or Windows authentication. 10. Proceed in one of the following ways: o If you chose to use SAP authentication, for SAP Client, enter the client number. For Destination Name, enter the SAP system ID, and click Next. o If you chose to use Windows authentication, enter a domain. The Database Type view is displayed. 11. Select the type of RTOM database to which the RTOM instance will connect and click Next. o If you selected Microsoft SQL Server, the Microsoft SQL Server Connection view is displayed. Enter the following parameters: o In the Hostname/IP field, enter the database server name. o In the Database Name field, enter the RTOM database name.

Note If a database is being installed as part of the same installation process, the Hostname/IP and Database Name fields are filled with the default host name and database name o Select the authentication type. If you choose Database Authentication, enter the User ID and Password of the applicable database user.

Note This dialog box defines the database connection and does not create the database itself.

o If you selected Oracle DB, the Oracle Database Connection view is displayed. Enter the following parameters: o For the Oracle Home Path field, browse to Oracle home (this can be found on Oracle server registry keys).

o In the Database Server Hostname/IP field, enter name of the machine where the Oracle database is installed. o In the RTOM Schema User ID field, enter the RTOM database schema. o In the Password field, enter the password corresponding to the RTOM Schema User ID. o Click Next.

Note This dialog box defines the database connection and does not create the database itself.

o If you selected SAP MaxDB, the SAP MaxDB Database Connection view is displayed. Enter the following parameters: o In the Hostname/IP field, enter the MaxDB server name. o In the Database Name field, enter the database name under which RTOM database was created. o In the User ID field, enter the RTOM schema. o In the Password field, enter the password of the User ID. o Click Next. 12. The Marketing Integration Mode view is displayed. If you are not integrating RTOM with marketing in SAP Customer Relationship Management, you have to use the RTOM application toolkit Business Logic Studio to create real-time offers. In this case, select the Standalone checkbox and choose Next. 13. The Parameter Summary view is displayed. Continue to Finalizing Actions.

4.1.1.4 Installing Real-Time Offer Management CIC Adaptor

1. If you selected the RTOM CIC Adaptor component, the RTOM Installation Root view is displayed. 2. Enter the desired installation root or click Browse… and browse to the desired location. Click Next.

The RTOM Domain Controller Settings view is displayed. 3. Enter the server where the domain controller will be installed and click Next. The Application Account view is displayed. 4. Enter a user name and password of the AppUser user. The AppUser user can access all services and COM+ applications. Click Next.

Note If you wish to enter a local user that is defined on the same machine where you are running the installation, enter the full name of the machine, for example, ILINGENEO34\localUserName.

The Web Service Permitted Account view is displayed. 5. Enter a user name of the WSUser user, as defined in the prerequisites. This user is used to access secure Real-Time Offer Management Web services. Click Next. 6. The Parameter Summary view is displayed. Continue to Finalizing Actions.

4.1.1.5 Installing Real-Time Offer Management Application Toolkit

1. If you selected the RTOM App Toolkit component, the RTOM Installation Root view is displayed. 2. Enter the desired installation root or click Browse… and browse to the desired location. Click Next.

Note If there is an existing Real-Time Offer Management installation on this machine, the installation root field displays the existing Real-Time Offer Management installation directory, which cannot be changed. The RTOM Domain Controller Settings view is displayed. 3. Enter the server where the domain controller will be installed and click Next. The Application Account view is displayed. 4. Enter a user name and password of the AppUser user. The AppUser user can access all services and COM+ applications. Click Next.

I Note If you wish to enter a local user that is defined on the same machine where you are running the installation, enter .\ before the user name instead of the name of the machine. The Web Service Permitted Account view is displayed. 5. Enter a user name of the WSUser user, as defined in the prerequisites. This user is used to access secure Real-Time Offer Management Web services. Click Next. The Parameter Summary view is displayed. Continue to Finalizing Actions.

4.1.1.6 Finalizing Actions

After completing the data entry, the Parameter Summary screen is displayed. On the Parameter Summary screen, you can view a summary of all parameters that you entered during the dialog process for each component you selected to install.

Procedure

1. If you do not wish to edit any of the parameters, click Next This action will start the installation. The Task Progress screen is displayed where you can view the progress of the installation. When the execution has finished, an information dialog box indicates the completion of the installation. Click OK to close the SAPInst dialog. 2. If you wish to edit any of the parameters:

o Select the checkbox of the parameter you wish to edit (this action enables the Revise pushbutton). o Click Revise (this action opens the relevant dialog box for editing). This action will display the corresponding wizard steps for the parameters that you selected to revise.

4.1.2 Installing SAP Real-Time Offer Management SAPIC/Telco/Utilities

The following sections describe the process of installing SAP Real-Time Offer Management SAPIC. The sections are: 1. Initial actions 2. Installing Real-Time Offer Management Database Update for SAPIC/Telco/Utilities 3. Installing Real-Time Offer Management Integration for SAPIC/Telco 4. Installing Real-Time Offer Management CIC Integration for SAPIC/Telco 5. Finalizing Actions

Caution You can only install one of the SAP Real-Time Offer Management solutions (SAPIC/Telco/Utilities) on a SAP Real-Time Offer Management core installation, and this should be done immediately after installation of the SAP Real-Time Offer Management core is complete and before any configuration changes are made. Each solution (SAPIC/Telco/Utilities) is provided on a separate CD.

4.1.2.1 Initial Actions

1. Double-click sapinst.exe. The Welcome to SAP RTOM Installation view is displayed. 2. Choose SAP RTOM Install New System . 3. Select SAP RTOM SAPIC/TELCO Installation and click Next. The RTOM SAPIC/TELCO Integration Components view is displayed. 4. Select the component(s) that you wish to install and click Next.

Note If a checkbox is disabled, it indicates that this component is already installed.

4.1.2.2 Installing Real-Time Offer Management Database Update for SAPIC/Telco/Utilities

1. If you selected the RTOM DB Update for SAPIC/TELCO/Utilities component, the RTOM Installation Root view is displayed. 2. Enter the desired installation root or click Browse... and browse to the desired location. Click Next.

Note If there is an existing Real-Time Offer Management installation on this machine, the installation root field displays the existing Real-Time Offer Management installation directory, which cannot be changed. The RTOM Database Update view is displayed. 3. Select the database type that was installed and click Next. o If you select Microsoft SQL Server, the MSSQL Database Update view is displayed. o If you select Oracle DB, the Oracle Database Update view is displayed. o If you select MaxDB, the MaxDB Database Update view is displayed. 4. In the Database Creation view: o If you selected Microsoft SQL Server in step 3, do the following: 1. In the Database Server Host Name/IP Address field, enter the name of the machine where the RTOM database is installed.

Note If the database was installed on the same machine, the Database Server Host Name/IP Address field will be initialized with (local). In this case, the field cannot be edited. 2. In the Database Name field, enter the name of the RTOM database to be updated and click Next. The DB Admin Account view is displayed. 3. In the DB Admin Account field, select the authentication type of the database user. For Microsoft Windows authentication, select Windows Authentication. If you select Database Authentication, enter the user ID and the password of the applicable user. 4. Click Next.  If you selected Oracle DB in step 3, do the following: 1. Enter the following parameters: o In the Database Server Host Name/IP Address field, enter the name of the database machine. o In the Database Name (SID) field, enter the database name of the Oracle database in which the RTOM database will be created. o In the RTOM Database Schema field, enter the name of the RTOM database that will be created and click Next.

3. In the DB Administrator Account field, enter an Oracle DB administrative user ID and password and click Next.  If you selected Max DB in step 3, do the following: 1. Enter the following parameters: o In the Database Server Host Name/IP Address field, enter the name of the database machine. o In the Database Name field, enter the database name of the MaxDB database in which the Real-Time Offer Management database will be created. o In the RTOM Database Schema field, enter the name of the Real-Time Offer Management database that will be created and click Next.

Note The name of schema should: o Consist only of upper case letters o Not have any spaces o Be no longer than 8 characters 2. The DB Administrator Account view is displayed. 3. In the DB Administrator Account field, enter the MaxDB administrative user ID and password (in upper case letters) and click Next. 5. The Parameter Summary view is displayed. Continue to Finalizing Actions.

4.1.2.3 Installing Real-Time Offer Management CIC Integration for SAPIC/Telco

1. If you selected the RTOM CIC Integration for SAPIC/TELCO component, the RTOM Installation Root view is displayed. 2. Enter the desired installation root or click Browse... and browse to the desired location and click Next.

Note If you want to enter a local user that is defined on the same machine where you are running the installation, enter .\ before the user name instead of the name of the machine. 3. Enter a user name and password of the AppUser user. The AppUser user can access all services and COM+ applications. Click Next. The Web Service Permitted Account view is displayed 4. Enter a user name of the WSUser user, as defined in the prerequisites. This user is used to access secure Real-Time Offer Management Web services. Click Next. The Parameter Summary view is displayed. Continue to Finalizing Actions.

4.1.2.4 Installing Real-Time Offer Management Integration for SAPIC/Telco

1. If you selected the RTOM Integration for SAPIC/Telco component, the RTOM Installation Root view is displayed. 2. Enter the desired installation root or click Browse... and browse to the desired location. Click Next.

4.1.2.5 4.1.2.5 Finalizing Actions

Procedure

1. If you do not want to edit any of the parameters, click Next. This action will start the installation. The Task Progress screen, where you can view the progress of the installation, is displayed. When the execution has finished, an information dialog box indicates the completion of the installation. Click OK to close the SAPInst dialog. 2. If you want to edit any of the parameters: o Select the checkbox of the parameter you want to edit (this action enables the Revise pushbutton). o Click Revise (this action opens the relevant dialog box for editing). This action will display the corresponding wizard steps for the parameters that you selected to revise.

4.2 Distributed Installation

1. Verify all prerequisites.

2. Install all components on the same server (as described in Component Installation).

Note If you install the Real-Time Offer Management server on more than one machine, only one server should be named as Default. The name of the server is required during the RTOM Server installation wizard. 3. Start the Real-Time Offer Management service: IngeneoAdministrator. 4. Export the configuration files using the Configuration Manager. For more information about the Configuration Manager tool, see the SAP Real-Time Offer Management Configuration Guide and the SAP Real-Time Offer Management Application Guide. 5. Open the RTOM application toolkit from the RTOM server that was named Default. 6. From the Integration Manager, go to the Deployment Parameters view. 7. Configure your system distribution according to the desired distribution of the installation required.

5 Post Installation

1. HTTPS: To support HTTPS with the Interaction Center (IC) in SAP CRM, an SAPNetCA certificate with a valid expiration date must be installed on the Real-Time Offer Management Server (RTOM Server). To add and view certificates, perform the following steps: 1. Choose Start Run and enter mmc. 2. Choose File Add/Remove Snap-in . 3. Choose Add, select Certificates, and choose Add. 4. Select the Computer account radio button and choose Next. 5. Select the Local computer: (the computer this console is running on) and choose Finish. 6. Choose Console Root Certificates (Local Computer) Trusted Root Certification Authorities Certificates . If the SAPNetCA certificate is not in the list, you must save the certificate file locally on the RTOM Server. 7. Right-click Certificates and choose All Tasks Import . 8. Browse to the certificate file and choose Next. 9. Select the Place all certificates in the following store radio button, browse to Trusted Root Certification Authorities, choose Next and then Finish. 10. The certificate is imported. 11. Make sure the expiration date is valid.

2. If you are installing Real-Time Offer Management Database (RTOM DB) on MaxDB, make sure that the driver name set by default during the installation is identical to the driver name of the MaxDB server. Perform the following steps: 1. Go to the MaxDB server and open the registry keys by running the regedit command. 2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI and look for the driver that has (Unicode) in its name. 3. If the driver name is not MaxDB (Unicode), copy the name of the driver and proceed to the next step. 4. Go to the Real-Time Offer Management Server (RTOM Server) and open the registry keys by running the regedit command. 5. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Ingeneo\Database. 6. Open the DSN key and change the driver name from MaxDB (Unicode) to the one you copied.

3. If you have installed Real-Time Offer Management Database (RTOM DB) on Oracle, create an Open Database Connectivity (ODBC) Source (required only if the ODBC connection was not created automatically during the installation): 1. Choose Start Programs Administrative Tools Data Sources (ODBC) . 2. Choose the System DSN tab and choose Add. 3. Select an Oracle driver and choose Finish.

4. In the Data Source Name field, enter RTOM_ORACLE. 5. In the TNS Service Name field, select the name that points to the RTOM database server and that is defined in the tnsname.ora file. 6. In the User ID field, the name of the RTOM schema that was created during the installation. 7. Choose Test Connection (by default, the password is identical to the schema name).

4. If you have installed Real-Time Offer Management Database (RTOM DB) on MaxDB or Oracle, give permissions to the AppUser user to update the Ingeneo registry keys by performing the following steps: 1. In the command prompt, run the regedit command. 2. Choose HKEY_LOCAL_MACHINE SYSTEM Software Ingeneo , right-click on the registry key, and from the context menu, choose Permissions. 3. Add the AppUser user and allow full control.

5. To integrate RTOM with SLD, see SAP Note 1490428. 6. Make sure that the Basic Authentication and Windows Authentication role services are installed on the machine where the RTOM server is installed. They are required for Microsoft Internet Information Services (IIS) authentication.

To make sure that the role services are installed, for Microsoft Windows 2008, perform the following steps: 1. Choose Control Panel Programs and Features . 2. Click Turn windows features on or off. 3. In the Server Manager window, choose Roles. 4. In the list of roles, you must see that the Basic Authentication and Windows Authentication role services are installed. 5. If the role services are not installed, in the Server Manager window, choose Add Role Services. 6. Select the Basic Authentication and Windows Authentication checkboxes and choose Install. 7. DCOM configuration permissions: Add permissions for the AppUser for each of the following DCOM services: o IngeneoAdministrator o IngeneoCache o IngeneoMCC o IngeneoQueuesMngr o IntentDC o PHOutEventsHandler To add the permissions for the AppUser, repeat the following steps for each of the DCOM services: o Choose Start Control Panel Administrative Tools Component Services . o Choose Component Services Computers My Computer DCOM Config . o Right-click on the corresponding service and from the context menu, choose Properties. o Choose the Security tab, under Launch and Activation Permissions, select the Customize radio button, and choose Edit. o Add the AppUser user. o Allow all permissions for the AppUser and choose OK.

Under Access Permissions, select the Customize radio button, and choose Edit. Allow all permissions for the AppUser and choose OK.

RTOM directory permissions:

1. Go to \Program Files\SAP CRM\RTOM, right-click on it and from the context menu, choose Properties. 2. Choose the Security tab and allow full control for the AppUser.

System root permissions:

1. Go to the TEMP directory of the root directory of your operating system. On a Microsoft Windows operating system, go to \WINDOWS\Temp. To find out what the system root directory is, in the command prompt, run the echo %systemroot% command. 2. Right-click on the TEMP directory and from the context menu, choose Properties. 3. Choose the Security tab and allow full control for the AppUser user.

Start the RTOM services:

1. On the RTOM server machine, choose Start Control Panel Administrative Tools Services . 2. Verify that the IngeneoAdministrator service startup type is Automatic. 3. Start the IngeneoAdministrator service (this service starts other services after about 30 seconds).

The following post-installation steps are relevant only for SAP solutions (SAPIC/Telco/Utilities): 1. If you have integrated RTOM with marketing in SAP Customer Relationship Management (SAP CRM), configure the marketing Web services by doing the following: 2. Open the SAP Real-Time Offer Management application toolkit using the following URL: http://:/RTOMAppsToolkitWS/Applications/Login/Default.aspx. 3. On the Integration tab page, click Landscape Configuration. 4. For each parameter in the list, except SAP System Landscape Definition, perform the following the steps: 5. Select the parameter from the list and choose Edit. 6. Enter a URL and password, confirm your password, and choose Save. 7. Choose Publish located in the right-top corner of the page. 8. This action restarts the RTOM services and commits the changes in the RTOM database. 9. Continue only when all RTOM services are started again.

1. To import the solution content into the RTOM database, proceed in one of the following ways: o If you have integrated RTOM with marketing in SAP CRM, run the report Program for Activation of Condition Attributes (CRM_MKT_RTOM_ACTIVATE_ATTR). o If you have not integrated RTOM with marketing in SAP CRM, import the condition groups by performing the following steps in the Configuration Manager: 1. Open the Configuration Manager by choosing Start Programs SAP RTOM Configuration Manager . 2. On the Export Files tab page, select the Export Condition Groups checkbox and choose Start Export.

3. For IC and SAP for Telecommunications, go to \Configuration\ConditionGroups and for SAP for Utilities, go to Installation DVD\DATA_UNITS\RTOM_UTILIC_CONTENT_WIN_X64\Configuration\ConditionGroups>. The condition groups for each language that is supported by RTOM is saved under the corresponding folder. For example, the ENU folder contains the condition groups in English. 4. Open the folder of the required language and copy the files to \ForEdit\ConditionGroups. 5. In the Configuration Manager, on the Import Files tab page, enter a description and reason for the import, and choose Add Files. 6. Browse to \ForEdit\ConditionGroups, select each of the files that were copied, and choose Start Import. During the import, a status message is displayed in the log area. 7. When all files have been imported, choose Update Server.

Note Importing the files may take several minutes depending on the size of each file. Updating the server takes a few minutes. To verify that the server has been updated, check if all RTOM services and COM+ are running. For more information about the Configuration Manager tool, see the SAP Real-Time Offer Management Application Guide.

2. If you have installed the IC or SAP for Telecommunications, configure the IC Web services by doing the following: 1. In the RTOM application toolkit, go to the Integration Manager - Data Sources view. 2. Repeat the following steps for each of the following data sources IC_AGENT, IC_CUSTOMER, and IC_SALE_ORDERS: o Select the data source and choose Edit. o In the Data Source Details view, enter the URL of the relevant Web service. o Enter the user name and password of the user authorized to access this Web service and choose Save. o Choose Publish for the changes to take effect. 3. Configure the RTOM Web service by doing the following: 1. In the RTOM application toolkit, go to the Integration Manager - Data Sources view. 2. Select Data Source RTOMWrapperForSAPIC_WS and choose Edit. 3. Enter the user name and password of the AppUser user who runs RTOM services. 4. Choose Save. 5. Choose Publish for the changes to take effect. 4. TCP/IP Parameter Registry Settings The TCP/IP parameter registry settings specified below are required when installing the Real-Time Offer Management Server (RTOM Server) component. Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters, add the following DWORD values: o MaxUserPort, value: 0x8000

o TcpTimedWaitDelay, value: 0x1e o SynAttackProtect, value: 0x0 You can do this by running the following from the command line: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters /v MaxUserPort /t REG_DWORD /d 0x8000 reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters /v TcpTimedWaitDelay /t REG_DWORD /d 0x1e reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters /v SynAttackProtect /t REG_DWORD /d 0x0 5. Integration Mode If you are integrating RTOM with marketing in SAP CRM, change the value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Ingeneo\Authenticator\IntegrationMode to Integrated.

Note Documentation in the SAP Service Marketplace You can find this document at the following address: http://service.sap.com/instguides

www.sap.com/contactsap

Material Number

© 2016 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System ads, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated 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. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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.