Getting Started with. SAP CRM rapid-deployment solution (V5.703) full-activated on SAP HANA

(1)

Getting Started with

SAP CRM rapid-deployment solution

(V5.703) full-activated on SAP HANA

(2)

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. National product specifications may vary.

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

SAP 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 other countries.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

(3)

Typographic Conventions

Type Style Description

Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, graphic titles, and table titles

Example text File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Example text User entry texts. These are

words or characters that you enter in the system exactly as they appear in the

documentation. <Example

text>

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

(4)

Overview

The pre-assembled SAP CRM system is delivered through a software appliance format, which is specifically optimized for Cloud deployment. The appliance not only contains a pre-installed system landscape and required software components (for example, SAP CRM), as well as the database (SAP HANA), but also partially pre-activated SAP CRM system configuration.

This guide provides the information you need to execute the last steps for the set-up of the cloud environment for the preassembled SAP CRM rapid-deployment solution powered by SAP HANA (V5.703).

As part of implementing the SAP CRM rapid-deployment solution, the SAP CRM system can be integrated with the customer’s existing SAP ERP system. The ERP system is not part of the pre-assembled system. However, it is also possible to deploy the SAP CRM rapid-deployment solution in a CRM standalone manner. In this case, the SAP ERP client is not required.

This document is intended for system administrators and basis consultants, responsible for system set up and preparation including troubleshooting, and who already have a sound knowledge of SAP Best Practices, including tools and documentation.

This document does not provide a general overview and explanation of SAP Best Practices. For more information about the Best Practices concepts, see the related documentation on http://service.sap.com/solutionpackages and follow the links to the Learning Maps.

Solution Information

The software appliance can be used to implement the scope of the SAP CRM rapid-deployment solution based on EHP3 of SAP CRM 7.0. It provides a 'semi-activated SAP Best Practices for CRM template’, which can be used as a jump start basis for implementation projects. In the semi-activated template a relevant portion of the required system configuration is already activated (subject to pre-assembly), with only a smaller portion left for activation during the actual project (subject to

(6)

assembly, e.g. connection to customer's SAP ERP system). This solution provides a full activated scope for evaluation pu

That means that the system is fully configured, i.e. can be used for evaluation purposes. SAP Best Practices Solution Builder guides implementation consultants through the post processing steps. This tool and the related ‘post-processing’ scope file is also part of the pre-assembled system.

For an overview of the solution package, refer to the Solution Details Presentation in the Step-by-Step Guide (Phase Start: Prepare Project) available within the download center on the SAP Market Place:

http://service.sap.com/rds-crm > Customer Relationship Management (CRM > Solution Deployment V5.703, Version 5 > open the area ‘Service- Step by Step Guide’ > select the option SAP CRM RDS HANA RDS Standard SBS Guide (download) > within the SAP Software Download Center selectSAP CRM rapid-deployment solution with SAP HANA > then SAP CRM HANA RDS > select SAP CRM HANA RDS V5.703  Installation  Download.

2.1 Business Processes

After fully activating the solution package according to the instructions of the solution package’s Quick Guide document, the following business processes are configured and documented by the respective business process documentation. The business process documentation provides detailed process step descriptions and can be accessed via the Step-by-Step Guide (Phase Deploy: Activate Solution > Business Process Documentation). Use the business process documentation to evaluate the processes in the system.

The following business processes are part of the SAP CRM rapid-deployment solution powered by SAP HANA (V5.703):

• Account and Contact Management • Activity Management

• Lean Campaign Management • Lead Management

• Opportunity Management

• Pipeline Performance Management

• Integrated ERP Order and Quotation Management (available with ERP integration only) • Interaction Center Service Request Management

• CRM Interactive Reporting

2.2 Sample Business Users in CRM System

The following sample users are available in the respective clients in the system and assigned to the corresponding organizational units to perform the preconfigured business processes as documented in the respective Business Process Documentation.

If you wish to evaluate additional functionality of CRM which is not covered by the SAP Best Practices for CRM Business Process Documentation, you will need to enhance the CRM and/or ERP configuration and user authorizations accordingly.

...

Purpose User ID Initial Password Name Last Name

Power User POWER_USER welcome Power User

Sales Manager SALES_MAN welcome Stone Jennifer

Sales Employee SALES_EMPL welcome Curtis Michael

Sales Director SALES_DIR welcome Seller Peter

Marketing Manager MKT_MAN welcome Richard Melanie

Marketing Employee MKT_EMPL welcome Lion Richard

(7)

Interaction Center Manager IC_MAN welcome Lucata Angela Interaction Center Service Agent IC_AGENT_SRV welcome Anderson Ann

2.3 Master Data

As mention above, in this semi-activated template, a relevant portion of the required system configuration is already activated, with only a smaller portion left for activation during the actual project. This means with regard to available master data that some example data exist, but not to the full extent that allows the full evaluation of all processes.

After post-assembly, you can copy and/or create master data to fit your business processes. If you need guidance, refer to the business process description of all pre-configured scenarios available in the Step-by-Step Guide as described above.

Using the SAP Cloud Appliance Library

3.1 Prerequisites

A fully configured SAP system requires network connections defined within each of the systems (SAP basis configuration) in order to interconnect these systems. These network configurations are applied within appliances using virtual hostnames (FQDN’s).

3.1.1 AWS Configuration

You will need the following information for the Amazon Web Services (AWS) account because when configuring the account of SAP Cloud Appliance Library you will be asked to specify the cloud provider details to establish the communication between SAP Cloud Appliance Library and the cloud computing environment:

1. The Access Key and the Secret Key of your AWS account.

To view your AWS access key and secret key, use the following procedure: 1. Navigate to http://aws.amazon.com.

2. Logon to your account.

3. Choose Account  Security Credentials. 4. In the Access Credentials section:

• To see your access key, choose the Access Keys tab.

• To see your secret key, choose the Secret Access Key tab and then choose the Show link.

2. The virtual private cloud parameter (VPC) VPC is needed to be configured in the AWS location where you will be deploying your solutions. Some solutions are restricted to a specific region, for example US-East (Virginia).

We recommend defining a domain name in a DHCP Option Set and accessing the VPC subnet via a secure VPN connection. For more information how to setup a VPN connection with OpenVPN, see this amazon VPC tutorial.

(8)

You can check the DHCP Option Set for your VPC as shown in the following screenshot:

3.1.2 Configurations in SAP Cloud Appliance Library

Follow the link to your SAP Cloud Appliance Library tenant provided to you in the confirmation e-mail. The next steps to configure your SAP Cloud Appliance Library console are:

1. Create an account in SAP Cloud Appliance Library. As the user who has created the account, you become an account owner and can assign other users to your account.

2. Browse for the solution you would like to evaluate in the Solutions tab page and activate it for the SAP Cloud Appliance Library account.

3. Select the activated solution and create a solution instance from it.

For more information about these three steps, see the official documentation of SAP Cloud Appliance Library (choose Related Links & Help  Documentation and choose (expand all) button to see all documents in the structure). You can also use the context help in SAP Cloud Appliance Library by choosing the Help panel from the right side.

An SAP Software Appliance comes with a lot of data on the shipment media. You don’t want to run your SAP system (hence the SAP virtual appliance) on this shipment media, so the data from the shipment media has to be copied somewhere for enterprise usage to the enterprise storage. Mount this enterprise storage folder (for intial setup) to a <temp_folder>.

In order to deploy the SAP software appliance, please create the following folders on your 2 empty Linux servers:

SAP System (CI) node: /usr/sap

/sapmnt /<temp_folder>

(9)

HANA DB node: /hana

/usr/sap /<temp_folder>

Make sure, that there is ENOUGH DISKSPACE configured underneath these file systems! Typical figures are e.g. approx. 200 GB for the database in /hana and 25 GB each for /usr/sap/ and /sapmnt, 250 GB for <temp_folder> to hold all the copied data of the virtual appliance.

For the exact size of the file systems, look in the SAP software appliance folders and get the values from the “sap_virtappliance_metadata.xml” files. Each folder has its own

“sap_virtappliance_metadata.xml” file. Look for the values in the tags <SizeUnpacked>.

Note that you have to add the values for “dbexe”, “dbdata” and “dblog” to get the full size of the /hana file system (it holds the data of the SAP HANA database).

You can use any available data store or enterprise storage subsystem for NAS or SAN or a locally attached storage device.

Once you have created the above mentioned filesystems, copy ALL THE SOFTWARE APPLIANCE DATA from the shipment media to the /<temp_folder> on each of the two Linux nodes for deployment.

This can take a while, since the entire data of the SAP Software Appliance is being copied (up to several 100 GBs!)

3.2 Working with Solution Instances

You can find the solution instances you created on the Instances tab page of the SAP Cloud

Appliance Library. For more information, see the Working with Solution Instances document from the official documentation of SAP Cloud Appliance Library (choose Related Links & Help 

Documentation and choose (expand all) button to see all documents in the structure). You can also use the context help in SAP Cloud Appliance Library by choosing the Help panel from the right side.

3.2.1 DNS Settings

SAP software appliances – and the resulting SAP systems are built on their own DNS domain and virtual hostnames. In order to run a SAP system from a SAP software appliance, this DNS domain and the related virtual hostnames are required in the target infrastructure for deployment. The DNS domain used for this SAP Software Appliance is:

cic4h.dummy.nodomain

Add this DNS-domain to your network. Alternatively, if this is not possible, local host entries on the servers that run the SAP system and database are required. However, this procedure is not as reliable as using a DNS domain entry.

Experienced customers can reconfigure the domain name for SAP standalone systems (SAP Startup / Instance profiles). Be aware that these manual steps are not trivial and may need additional SAP consulting effort.

The specific virtual hostnames used with this SAP Software Appliance in this DNS zone are listed in the “sap_virtappliance_metadata.xml” files. Watch out for the tag <VirtualHostname>:

Specific virtual hostnames used for this SAP Software Appliance:

(10)

grep VirtualHostname sap_virtappliance_metadata.xml <VirtualHostname>dbc3h</VirtualHostname> <VirtualHostname>cic4h</VirtualHostname> <VirtualHostname>scsc3h</VirtualHostname>

So, in our example we would need to add 3 virtual hostnames to DNS: • dbc3h

• scsc3h • cic4h

DNS Zone: cic4h.dummy.nodomain

These virtual hostnames must be resolvable by nslookup from each of the servers that you would like to deploy the SAP software appliance on (SAP HDB and SAP System node).

Alternatively the virtual hostnames can be added to /etc/hosts file locally on each of the servers used for deployment, but this is error-prone and not recommended!

3.2.2 Server Preparation

SAP HANA software appliances run on SAP HANA certified hardware ONLY! There is NO support to run a SAP HANA System on non-certified hardware. Also refer to SAP’s Product availability Matrix (PAM) via https://service.sap.com/pam.

Each SAP HANA software appliance is divided into two sub-software appliances. One is the SAP HANA Database (DB) Appliance and one is the SAP Central Instance (CI) Appliance.

These two different SAP HANA system instances have to run on two different physical Linux servers. So it is necessary to prepare 2 physical Linux servers, each with a SuSE Linux Enterprise Server (SLES) 11.1 Linux as Operating System running on it.

The SAP Virtual Appliance is a pure SAP software appliance. In order to run, it needs to be connected (“attached”) – to a SAP HANA certified physical server with SuSE Linux Enterprise Server (SLES) 11.1 Linux as Operating System running on it. So hence provide a SAP HANA certified hardware with a SLES 11.1 Linux installed. SAP DOES NOT support any other Linux distribution other than the above mentioned!

System tools like perl, tar, gzip, ping, nslookup, and tput have to be installed on the OS!

A minimum machine size for a SAP HANA DB server is: 4 CPU with 64 GB RAM. A minimum machine size for a SAP HANA CI server is: 4 CPU with 4 GB RAM.

For further details regarding recommended machine sizes, refer to the

“sap_virtappliance_metadata.xml” file – watch out for the tag <MinimumMachineSize>.

The two Linux servers for HANA DB and HANA CI should be in the same network and should “see” each other.

Communication between the two servers needs to be possible – NO firewall must block this communication.

Again, the virtual hostnames for this SAP Software Appliance must be resolvable by nslookup.

For deployment of a SAP HANA software appliance, use the SAP Software Appliance Tools, such as SAP SWPM, VAFUtil, or Appliance Agent. Follow guides provided with the SAP Software Appliance Tools for further reference.

...

(11)

3.2.3 Included Product Versions and Software

Components

For detailed documentation refer to the Software Requirements document for this solution package, also available in the Step-by-Step Guide (Phase Start: Confirm Installation).

In a nutshell the following software components are part of this software appliance: • EHP3 FOR SAP CRM 7.0 (SP01) / NETWEAVER 7.40

• SAP HANA 1.0 (SP07)

o SAP HANA Live for SAP CRM 1.0 (SP03)

o SAP HANA CRM IC Inbox Accelerator 1.0 (SP00)

• SAP Best Practices Solution Builder and SAP Best Practices for CRM activation content

Software components included in the appliance:

Component Release Support Package

SAP_BASIS

740

3 SAP_ABA

740

3 SAP_GWFND

740

3 SAP_UI

740

3 PI_BASIS

740

3 ST-PI

2008_1_700

8 SAP_BW

740

3 MDG_FND

747

1 SAP_AP

700

29 SAP_BS_FND

747

1 WEBCUIF

747

1 BBPCRM

713

1 BP-CRM

713V1

n.a.

BP-CANW

740V3

n.a.

BP-SOLBLD

70V9

n.a.

Installation documentation

The SAP Best Practices which have been used to pre-configure this solution were implemented based on the information provided by the following SAP Note and the related configuration guides available in SAP Service Market Place:

SAP Note 1900297: SAP CRM rapid-deployment solution powered by SAP HANA V5.703

Content Versions

[BEST Practices Add-On = PV] BP-SOLBLD 70V9 [Main Component = PV] BBPCRM 713 [Stack-No. of Main Component] SPS 1

[Localized Country] USA

Languages

All business processes and the related SAP Best Practices content are provided for the following languages:

(12)

- English (EN) - German (DE) - Spanish (ES) - Portuguese (PT) - Chinese (ZH) - French (FR) - Japanese (JP) - Russian (RU)

3.2.4 Additionally Required Product Versions and

Software Components

If the scope item Interaction Center Service Request Management is in scope, specifically the TREX-based search for Knowledge Articles, the following component is additionally required, i.e. needs to be installed additionally:

• SAP NetWeaver Search and Classification (TREX) – SAP NetWeaver 7.1, latest revision

An SAP ERP system is not part of the software appliance. Still the SAP CRM rapid-deployment solution can be integrated with an SAP ERP system. Note that the solution was specifically developed and tested with the following SAP ERP release:

• EHP7 FOR SAP ERP 6.0 (SP01)

For the implementation of the solution package, a SAP Solution Manager system is recommended. In the context of SAP rapid-deployment solutions, specific implementation content is delivered via SAP Solution Manager templates. It is assumed that a productive SAP Solution Manager system is available in the customer’s system landscape.

• SAP SOLUTION MANAGER 7.0 EHP1 (SP18 or higher) or 7.1 (SP01 or higher) or 7.1 on HANA (SP00 or higher)

• Solution Manager Content Add-On ST-RDS 100, latest SP level

For detailed documentation refer to the Software Requirements document for this solution package, also available in the Step-by-Step Guide (Phase Start: Confirm Installation).

Installing Client Software

The SAP CRM user interface runs in a compatible browser, without any special installation.

End users access SAP CRM via their local web browsers. For the latest information about supported Web browsers, refer to SAP’s Product Availability Matrix, which bundles technical information on SAP components for quick reference (http://service.sap.com/pam; enter EHP3 FOR SAP CRM 7.0) and SAP Note 1876371: Browser compatibility of SAP CRM 7.0 EhP 3.

4.1 ABAP Client Software

Ensure that you have installed the latest and appropriate SAP frontend components. The following download path below leads you to an overview on how to install SAP frontend

components and how to apply patches. On the navigation level SAP Frontend Components, you can select the SAP frontend components depending on your requirements.

To download the SAP frontend components, go to the Software Distribution Center (SWDC) on the SAP Service Marketplace:

(13)

4.1.1 SAP GUI

Ensure that you have installed the latest version of SAP GUI and of the SAP Scripting Engine. https://service.sap.com/swdc, then choose Support Packages and Patches  Browse our Download Catalog  SAP Frontend Components

4.1.2 ABAP Development Tools (ADT) (optional)

The installation package for the ABAP Development Tools (ADT) can be found at

https://tools.hana.ondemand.com/ . You can use the HANA Studio (Revision 67 or higher) as Eclipse platform.

4.2 HANA Client Software (optional)

For detailed instruction please refer to http://help.sap.com/hana_platform. Please check especially the SAP HANA Client Installation Guide. The SAP HANA Client has to be installed for all the users who will access the data in HANA by using some kind of frontend tools, for example Excel, BOBJ Clients etc.

4.2.1 HDB Studio and HDB Client

The software package containing the SAP Hana Studio contains the SAP HANA Administration and Modeling tool.

The software package containing the SAP HANA Client contains SDK's for JDBC, ODBC, ODBO and Python DB API, so you can build client applications.

You can download the SAP HANA Studio and Client for all available operating systems from the SAP Service Marketplace by using the following procedure:

1. On your browser enter the following URL for the SAP Service Marketplace:

http://service.sap.com/support Choose Software Downloads  Search for Software Downloads (link in the navigation pane on left hand side)

2. In the Search Term field, enter the following string a. for the SAP HANA Studio: IMC_STUDIO100 b. for the SAP HANA Client: IMDB_CLIENT100 3. Choose Search.

4. From the list of archives, download the archive according to your OS and the latest revision ( e.g. IMC_STUDIO100_nn – nn is the revision number).

5. Unpack the files with SAPCAR and run the hdbsetup.exeinstallers.

Connecting to Your Solution

5.1.1 Available Pre-Configured System Clients

CRM standalone

Client 100 in the SAP CRM system has been configured for a CRM standalone implementation.

Integration with SAP ERP

For the integration of CRM with SAP ERP client 200 has been pre-configured with SAP Best Practices for CRM for integrated usage. This client is not supported

(14)

5.1.2 Connecting to Your Appliance

It takes approximately 45 minutes to prepare the solution instance for first time use.

Procedure

Run the following activity to complete the system configuration. 1. Start SAP GUI Logon application

2. Choose the Create a new entry action. 3. Select the User Specified System option.

4. On the System Connection Parameters screen, make the following entries: ...

Parameter ID Parameter Value Note Connection

Type

Custom Application Server

Description <your description> Create a description for the new system entry to be shown in your SAP Logon overview

Application Server

You can find the IP address of your instance in the instance details screen

Instance Number

10 Default value for SAP Cloud Appliance Library DEMO / Evaluation Appliance

System-id C4H

5. Save this new entry in the SAP Logon entries for future logon.

6. Continue with the specific activities described in the next chapter of this document.

After the configuration is complete, you are able to access the SAP CRM WebClient UI by using a Uniform Resource Locator (URL). The URL of the CRM Web Client UI has the following structure (default configuration):

http://<fully qualified host name of the system>:8000/sap/crm_logon?sap-client=<client number>

5.1.3 You will need to ensure full DNS resolution of the

URL in order to access the system. Mapping hostnames

to IP address

Your Amazon VPC setup needs to have a DHCP Option Set which defines a domain-name <Domain Name>. If this is not the case then create the DHCP Option set and terminate your CAL instance and create a new one. This is necessary as <Domain Name> is used in the CAL instance creation process.

When creating a CAL instance the solution is deployed to a server with the predefined names cic4h dbc3h scsc4h . You are also provided <IP Addresses> with which you can access the servers. You can find the <IP Address> of the respective servers by clicking on the name of your instance in the SAP Cloud Appliance Library. ABAP application server CRM reaches the HANA server HDB with the help of an entry for dbc3h in it’s local /etc/hosts file.

You still need to publish a mapping between the server names and the IP address in your network. You could do this within your Domain Name Service (DNS) setup or adjust the hosts file on the client.

(15)

5.1.4 Specific Activities in SAP CRM System

5.1.4.1 Transaction SICK

Purpose

Check the health of the system.

Executed already: Yes To be executed (again): Yes Actions

Run transaction SICK.

Expected Result

SAP System Check: “no errors reported”

5.1.4.2 Transaction DB59

Purpose

Set the correct DB passwords for the application server.

Executed already: No To be executed (again): Yes Actions

1. Call transaction DB59.

2. Click the Integration Data button.

3. Set the password to the master password that was specified when the solution instance was created.

4. Go back to the previous screen. 5. Perform a connection test.

6. On the next screen, mark the server line and click the Check Selected Servers button.

Expected Result

The application server should have established a database connection.

All check results should be successful (green status). In case of a warning or error (red status), ensure that you have selected the right system and the correct master password.

5.1.4.3 Transaction DB50N

Purpose

Monitor the availability of the database.

1. Call transaction DB50N.

2. Select your SID for Name of Database Connection. 3. Choose Execute (F8) and select No on the pop-up screen.

(16)

Expected Result

Successful result – your database is shown.

5.1.4.4 Transaction SE06

Purpose

Post- installation actions for Transport Organizer.

Executed already: Yes To be executed (again): No Actions

None, because this transaction has been executed.

5.1.4.5 Transaction SECSTORE

Purpose

Administration of Secure Storage.

5.1.4.6 Transaction STMS

Purpose

Configure Transport Organizer.

5.1.4.7 Transaction RZ10

Purpose

Import profile parameters.

5.1.4.8 Transaction SMLG

Purpose

Change Logon Group.

(17)

5.1.4.9 Transaction RZ12

Purpose

Change Logon Group.

5.1.4.10 Transaction STRUSTSSO2

Purpose

Set up Single Sign-On for the system.

1. Call transaction STRUSTSSO2.

2. Right mouse click for the following entries to create/replace/delete PSE: a. SNC SAP Cryptolib

b. System PSE

c. SSL server Standard d. SSL client (Standard) Expected Result

Single Sign-On is configured correctly.

5.1.4.11 Transaction RZ04/RZ03

Purpose

Define instances/operation modes

5.1.4.12 Transaction SM59

Purpose

Configure ABAP and RFC connections.

(18)

5.1.4.13 Transaction SGEN

Purpose

Generate ABAP resources.

5.1.4.14 Change SAPFQDN Parameter

Purpose

Change the SAPFQDN parameter values in the profiles and configure the host names in /etc/hosts so that you can access CRM Business Client via the Browser.

Actions

1. Log in to your Amazon instance as ‘root’ user name where the CRM system is running using tools such as PuTTY. Refer to Amazon Elastic Compute Cloud documentation for detailed information on connecting to Linux/UNIX instances.

2. Create a shell script file as follows to execute the commands at the operating system level for

your solution instance. Replace the value for NEWDOMAIN. OLDDOMAIN corresponds to the current SAPFQDN parameter value in the profile.

#!/bin/bash

OLDDOMAIN=dummy.nodomain

NEWDOMAIN= please change to your customer domain SID=CRM

sid=`echo $SID | tr '[A-Z]' '[a-z]'` hostname=cic4h

sed -i.bak -e "s@^[ \t]*SAPFQDN[ \t]*=.*@SAPFQDN = $NEWDOMAIN@g" /sapmnt/$SID/profile/DEFAULT.PFL

sed -i.bak -e "s@^[ \t]*SAPFQDN[ \t]*=.*@SAPFQDN = $NEWDOMAIN@g" /sapmnt/$SID/profile/${SID}_DVEBMGS00_${hostname}

sed -i.bak -e "s@$OLDDOMAIN@$NEWDOMAIN@g" /etc/init.d/updatehosts-network /etc/init.d/updatehosts-network start

su –c stopsap - ${sid}adm su –c startsap - ${sid}adm

3. Assign the execute permission to the script file; e.g. chmod 755 <script file name>. Execute the script. Note that you may see a ‘.. failed’ message in the output. You can ignore this message.

4. Review each affected profile and confirm that the SAPFQDN parameter value is updated to the value of NEWDOMAIN. In the example script file above, the affected profiles are DEFAULT.PFL and CRM_DVEBMGS00_cicrm under /sapmnt/CRM/profile.

5. Review /etc/hosts file and confirm that the host names contain the value of NEWDOMAIN as part of the host names.

For example,

(19)

10.79.22.1 sid-c4h cic4h.wdf.sap.corp cic4h cic4h.wdf.sap.corp saphost saph ost.wdf.sap.corp sid-c4h sid-c4h.wdf.sap.corp

5.1.4.15 Resolve “host.domain” in Local System

Purpose

Since “host.domain” might not be a registered DNS or a Web address, it is necessary to make modification in the local operating system to resolve the “host.domain” to the belonging IP address of the SAP system.

Actions

1. You have to configure the hostnames also inside your local hosts file. In the Windows operating systems the path to the hosts file is:

<windowspath>/system32/drivers/etc/hosts. In the UNIX operating systems the path is: /etc/hosts.

The entry to the local host file contains following values: IP Address to VM <tab> hostname.domainname specified in the SAP system.

For example:

10.79.22.1 cic4h.dummy.nodomain cic4h

5.1.4.16 Transaction SICF - Test Access to CRM WebUI

Purpose

After configuring a separate domain in the SAP system and resolving it locally in your local /etc/hosts file, you are now able to test if the changes are working correctly.

Option 1: Access the CRMUI via Web browser

The URL using the external alias for the CRMUI has the following structure (default configuration): http://<fully qualified host name of the system>:8000/sap/crm_logon?sap-client=<client number> For example,http://cic4h.wdf.sap.corp:8000/sap/crm_logon?sap-client=100

You will need to ensure full DNS resolution of the FQHN in order to access the system.

Option 2: Navigate to the CRMUI via Transaction SICF a. Open the transaction SICF.

b. Choose Hierarchy Type "SERVICE" and choose execute. c. Open Tree Element default_host.

d. Select sap. e. Select /crm_logon.

f. Select Test link from the context menu.

Expected Result

The CRM Business client opens inside the browser window and is ready for logon.

(20)

5.2 System Administration Users in SAP CRM System

...

The following system administration users are available:

Purpose User ID Initial Password

Client 000: for system administration tasks

DDIC SAP*

Password is set to master password provided by you at Instance creation Client 001: for system

administration tasks

DDIC Password is set to master password provided by you at Instance creation Client 200: for system

DDIC _{Password is set to master password}

provided by you at Instance creation Client 100: for system

BPINST Welcome1

Licenses

6.1 Installing a License

This SAP software appliance, as well as the SAP HANA database and CI System that you have just successfully deployed and started come WITHOUT a license from SAP. Since the HANA database comes without a license, the SAP system that runs on top will not start, because a connect to a non-licensed SAP HANA database is not possible. In order to license BOTH the SAP HANA database and the SAP CI System, you have to get your own customer license from SAP Service Marketplace (http://service.sap.com) by logging on with your own S-User.

To license the SAP HANA database follow the instructions given in SAP Note 1644792 - License key req./installation SAP HANA databases.

On the HANA DB machine become <sid>adm user and run SAP HANA studio: /hana/shared/<SID>/hdbstudio/hdbstudio.

If you do not have direct console access to a Linux machine, export the DISPLAY variable and open the exported graphical X-window on another machine that is running X-window client tools like e.g. Exceed, VNCViewer, Xming, etc.

(21)

Once the SAP HANA Studio has opened, press right mouse button in left column -> new system and give details about the SAP HANA system, like e.g. HANA DB SID, DB Hostname, and Instance No. For getting all this information run the SAP Hostagent:

/usr/sap/hostctrl/exe/saphostctrl –function ListInstances Inst Info: C3H – 08 – dbc3h – 720, patch 441

Finally provide the user authentication data. Logon with user “SYSTEM” and the master password for this user.

(22)

For license information, right-click on the system in the left column -> Properties -> License.

This will give you the hardware key that you will need to request a new SAP HANA License Key at http://service.sap.com.

(23)

Once you have requested a valid SAP HANA license, an email with the new License key will be sent to you. For installing the new SAP HANA license, open the SAP HANA studio again, logon as user “SYSTEM” and open a SQL console.

In the SQL console, type SQL command: SET SYSTEM LICENSE ‘

and copy and paste the content of the SAP HANA License Key file, end with ‘

(don’t forget to place the ‘ at the beginning and at the end of the content of the license key file). Finally press “Play” (run SQL command).

Now, your SAP HANA database is registered.

To enter the license for the SAP system, logon to the SAP system with the SAP* User in client 000 and run transaction SLICENSE. Find the related hardware key and request your own license at http://service.sap.com.

Once you have received your customer specific license key, enter the key (Install NEW License).

In general, follow the guidelines for SAP system license installation provided here: http://www.service.sap.com/licensekey

SAP Note 94998 - Requesting license keys and deleting systems SAP Note 870871 - License key installation

SAP Note 1644792 – License key installation for SAP HANA Databases

(24)

Additional Information for Your Solution

7.1 Configure SAP Secure Store Settings

The SAP-System CI ABAP that you have successfully installed by provisioning a SAP software appliance uses a secure data vault for encrypted user and password information. This data vault is called the “SAP Secure Store”. In order to work properly, the SAP Secure Store of this SAP system needs to be configured.

The following SAP applications use the SAP Secure Storage to store passwords:

· RFC destinations

· Exchange Infrastructure (XI)

· LDAP integration

· SAPphone

· SAPconnect

· CCMS (Generic Request and Message Generator)

For legal reasons the SAP secure storage is used by SAP applications only. However, SAP provides the Secure Store & Forward interface for the integration of non-SAP applications.

7.1.1 Configuration of RFC-destinations

Log on as user DDIC to the client of the SAP System that runs your application data (e.g. client 100). Run transaction “SECSTORE”

There are some entries, mainly RFC-destinations, marked in “red”, indicating a wrong or missing configuration. To correct, select the RFC-destinations one by one and enter the correct username / password combination.

(25)

Open the RFC-destinations that are marked in “red” one by one in Transaction “SM59” for editing.

Find out the correct password for the user associated with this RFC-destination and set this password here in Transaction “SM59”.

(26)

Save the data once you are done with editing. Test the connection.

Do this for ALL RFC-destinations that are marked in “red”.

7.1.2 Configuration of DB-connection

Another common error related to incomplete SECSTORE entries is an error-message shown in transaction “DB02”. This is due to missing user/password entries for the database connection.

To

(27)

To correct this issue open transaction “DB02” and select the DB-connection. Enter the correct password for the DB-connection user “DBACOCKPIT”.

Save your changes and re-run transaction “SECSTORE”. The DB-connection should now be ok.

7.1.3 Configuration of STMS

The last errors in SECSTORE are related to the SAP Transport Management System, so open transaction “STMS”.

(28)

Switch to “System Overview”.

Go to menu “Goto” and regenerate RFC-destination SAPOSS.

Switch to transaction “SM59” and select RFC-destination “SAPOSS”. Check, if RFC-destination to SAP OSS is successful.

If necessary enter the following parameters: Target System: OSS

MSG Server: Customer dependent

Example: H/172.19.136.11/H/203.13.155.17/W/xijkb3d/H/147.204.2.5/H/oss001 (your SAPRouter string)

Group : EWA Language : EN Client : 001 User : OSS_RFC Password : cpic

Save and check the RFC-destination SAPOSS in transaction “SM59”. Run transaction “SECSTORE” again. Everything should be “green” now.

(29)

7.2 Install Master password in CRM

You need to run sap-gui and open the client 100 with the user bpinst password Welcome1. Start transaction dbco and enter your instances master password into corresponding fields and press save. Now you can use interactive reporting based on SAP HANA Live.

Security Aspects

This section provides an overview of the security-relevant information that applies to this solution package.

To access the latest version of the general security guide for SAP CRM, log on to SAP Service Marketplace (http://service.sap.com) and follow the path Products > Security > SAP Security Guides > SAP Business Suite Applications > SAP CRM > Security Guide enhancement package 3 for SAP CRM 7.0.

Security related aspects specific to this solution package are documented in the Quick Guide document, attached to SAP Note 1900297 - SAP CRM rapid deployment solution powered by SAP HANA V5.703.

(30)

Troubleshooting

<TEXT>

For more information about how to use the SAP Cloud Appliance Library, you can read the official documentation of the product by choosing the following navigation from SAP Cloud Appliance Library: Related Links & Help  Documentation. If you cannot find the needed information in the

documentation, you can open a normal support ticket within the SAP Cloud Appliance Library (BC-VCM-CAL) component and your ticket will be processed by the SAP Cloud Appliance Library Operators.

If you have AWS related problems, you can report them directly to AWS support or alternatively on the BC-OP-LNX-AWS component in SAP Service Marketplace.

Getting Started with. SAP CRM rapid-deployment solution (V5.703) full-activated on SAP HANA