sap discovery system v4 enhanced quick guide discovery system quick guide sap discovery system v4...

SAP Discovery System Quick Guide

SAP Discovery System v4 Quick Guide September 2010 English

SAP Discovery System V4 enhanced Quick Guide

SAP AG Neurottstr. 16 69190 Walldorf Germany

Copyright © Copyright 2010 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®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic Server™ are trademarks of IBM Corporation in USA 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®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML 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. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information purposes only. National product specifications may vary.

SAP Discovery System V4 Quick Guide

© SAP AG of 77

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

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

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

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

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

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

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

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


© SAP AG of 77

Contents

SAP Discovery System Quick Guide ............................................................................................... 5

1. Purpose ........................................................................................................................................ 5

2. Licensing Options ......................................................................................................................... 5

3. Backup Recommendations .......................................................................................................... 6

3.1 Initial Backup .......................................................................................................................... 6

3.2 Maintenance Backup .............................................................................................................. 6

4. Network Configurations ................................................................................................................ 8

4.1 Network Configurations on the ESXi .................................................................................... 11

4.2 Network configurations on the Linux VM .............................................................................. 14

4.3 Network Configurations on the Windows VM ....................................................................... 32

4.4 Required DNS Settings ........................................................................................................ 34

5. Third Party Software on the Windows VM ................................................................................. 35

5.1 JAVA SDK Installation .......................................................................................................... 36

5.2 Adobe Reader Installation .................................................................................................... 39

5.3 Adobe Flash Installation ....................................................................................................... 40

5.4 Adobe SVG Installation ........................................................................................................ 41

5.5 Putty...................................................................................................................................... 42

5.6 Cryptographic files ................................................................................................................ 43

5.7 Microsoft Office ..................................................................................................................... 46

6. License Keys .............................................................................................................................. 47

6.1 Obtain the Hardware Key ..................................................................................................... 47

6.2 Request the License Keys .................................................................................................... 48

6.3 Apply the SAP License Keys ................................................................................................ 49

6.4 Apply the BusinessObjects License Keys ............................................................................ 63

7. Migrate the Secure Store in the ABAP system .......................................................................... 69

8. Finalize Installation ..................................................................................................................... 71

9. Deploy the OVF Template (Revert to Initial Settings). ............................................................... 72

10. Troubleshooting ....................................................................................................................... 75


© SAP AG of 77

SAP Discovery System Quick Guide

1. Purpose This quick guide provides the information you need to install, load and run the SAP Discovery

System v4.

Before proceeding with this guide, make sure that you purchased the SAP Discovery System V4

and not the earlier version of the system (V3)!

To check the version of the system you have, please refer to the following document: TBD

In case you find out that you have an earlier version of the SAP Discovery System, do not

proceed with this document. Instead, you can find the appropriate quick guide for the Discovery

System V3 under:

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/801dd54d-dd37-2a10-eca7-

94bce2de28bc&overridelayout=true

2. Licensing Options The SAP Discovery system is licensed for non-production use only. It can be used for evaluation,

test, demonstration, proof of concept, and other similar purposes only. Prior to purchasing the

Discovery system, please consult with your SAP Account Executive or local SAP subsidiary to

determine your specific licensing options.

As any other SAP system the Discovery system requires a license key to be fully operational.

Customer and Partners who have licensed all the software on the Discovery system previously can

use their existing licenses (see complete list of components on SDN). The necessary license keys

can then be downloaded from SAP Services Marketplace. If you have not yet licensed all the

software on the Discovery system but are an existing customer, you can receive a 180-day

evaluation license.

The same is valid for SAP partners with an existing SAP Test and Demo License. This evaluation

license will be granted during your registration process on SAP Services Marketplace. After 180

days customer and partners should contact their Sales Representative (customers) or local

Alliance Network (partners) for additional licensing information or use only the software

components they are licensed for.

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/801dd54d-dd37-2a10-eca7-94bce2de28bc&overridelayout=true

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/801dd54d-dd37-2a10-eca7-94bce2de28bc&overridelayout=true


© SAP AG of 77

3. Backup Recommendations

3.1 Initial Backup Backup the two VMs before making modifications to the Discovery System. Turn off all SAP services and then proceed in accordance with methods prescribed by hardware vendor.

3.2 Maintenance Backup Make sure to backup the Linux server VM and the Windows VM after completing installation instructions and whenever any major development milestones are achieved. Note: The instructions to download and install the VSphere client is described in section 5.1.1 below. The instructions to export the OVF is described below. 1. Log in to the ESXi using the VSphere client. Log in using root/VMware123 2. Shut down the Linux server VM 3. Select the SAP Discovery Server 4 on the left side

4. Click on FileExport OVF Template


© SAP AG of 77

5. Enter the name “SAP Discovery Server 4” and select the Web (OVF) in “Optimized for” drop down.

Note: If you want to import the OVF template, refer to section 9—Deploy the OVF Template


© SAP AG of 77

4. Network Configurations Discovery system V4 Architecture

The Discovery system V4 consists of two Virtual Machines—a Server VM (Novell SUSE Linux

Enterprise Server) and a client VM (Windows Server 2008), both of which are guest operating

systems installed on the VMware ESXi. The diagram below describes the architecture of the

system.

Discovery system V4 architecture

The users and passwords required for the Discovery system V4 is available in SCN. Download it

and have it ready, as it will be required throughout the set up process.

In order for the Discovery system to be accessible in your network, the following network

configuration steps have to be completed.

The steps below describe the outline of the process to set up the network configurations on the

Discovery system V4:

1. Connect the Discovery system v4 to a network and provide an IP address to the ESXi.

2. Install the vSphere client and connect to the ESXi

3. Configure direct access to external networks from the Windows based VM

4. Configure direct access to external networks from the Linux based VM

http://www.sdn.sap.com/irj/sdn/discoverysystem-user


© SAP AG of 77

The following diagrams describe the network configurations of the 2 virtual machines. Note that

after completing the Network configurations your settings should look like the one in scenario 2.

Scenario 1


© SAP AG of 77

Scenario 2


© SAP AG of 77

4.1 Network Configurations on the ESXi 1. Start the ESXi. An introduction screen is displayed after the ESXi is launched.

2. Press the ―F2‖ key to set up the ESXi server. Select the ―Configure Management

Network‖ and press ―Enter‖

3. Select ―IP Configuration‖ and press ―Enter‖.

4. Here, you can assign the IP address for the ESXi . If preferred, the ESXi server can be

renamed through the DNS Configuration.

5. Press the ―Escape‖ key to exit the Network Configuration Screen

6. Since changes have been made, you will be prompted to Save and restart the management

network. Choose ―Yes‖

7. Press ―Escape‖ to Log out


© SAP AG of 77

8. After logging out, you will be back at the original screen and the ESXi server’s IP address

is displayed.

4.1.1 Install the vSphere client and connect to the ESXi

The virtual machines on the system can be managed by using vSphere client installed

on any MS Windows based computer. The Windows machine should have internet

access and be able to access the ESXi host.

The vSphere client is used for connecting to the ESXi, administrating and monitoring

the two guest VMs—such as for starting and stopping the Linux VM and the

Windows VM. Download and install the vSphere client as described below.

This image describes the role of vSphere client:


© SAP AG of 77

1. Download VI Client and configure your ESXi Server.

Open a web browser and enter https://<ipaddressofyouresxi>/. This is the IP address

of your ESXi server, which was configured in step 4 of Section 5.1. Select the link

―Download VMware Infrastructure Client‖.

2. Install the VI Client and accept all defaults.

3. Navigate to your desktop and launch the VI Client

4. Log in with the following parameters:

Server: enter IP address of your ESXi server

Username: root

Password: VMware123

If you get any security

warnings, you can click

ignore.


© SAP AG of 77

4.2 Network configurations on the Linux VM

4.2.1 Assign an external IP address to Linux

Prerequisites: Any Windows System with VSphere client installed.

Information you need in advance from your IT:

Static IP for the VM

Corresponding Subnet mask

Standard Gateway IP address

DNS Nameserver IP address

In this example, we use:

Static IP for the VM: 172.16.5.183

Corresponding Subnet mask: 255.255.254.0

Standard Gateway IP address: 172.5.4.1

DNS Nameserver IP address: 172.17.121.30

1. Select the SAP Discovery Server 4 VM and open the console window from the

menu.


© SAP AG of 77

2. Login using root/ admin123


© SAP AG of 77

3. Click on the green icon to start YaST Administration Setting

4. Select ―Network Devices‖ and single click ―Network Card‖


© SAP AG of 77

5. Keep default selection as shown in the screenshot here, click ―Next‖


© SAP AG of 77

6. Select the entry beginning with ―VMWare Abstract‖ as shown in the screenshot

and click on ―Edit‖


© SAP AG of 77

7. Here you can choose between DHCP or enter a fixed network address


© SAP AG of 77

8. After entering your IP address (e. g: 172.16.5.183 ) and your Subnet Mask (e. g:

255.255.254.0) select ―Hostname and Name Server‖


© SAP AG of 77

9. Here you enter the different name servers for your company (e.g. 10.17.121.30).

Click ―OK‖ to continue.


© SAP AG of 77

10. Click on the ―Routing‖ button to configure the Gateway


© SAP AG of 77

11. Here you enter the standard gateway for your company (e.g. 172.16.4.1). Click

―OK‖ to continue


© SAP AG of 77

12. In the next window, accept defaults and click ―Next‖


© SAP AG of 77

13. Click on ―Finish‖


© SAP AG of 77

4.2.2 Configuring an internal IP address for the Linux VM

The following steps describes the process to connect the Linux VM to the Windows VM to enable

communication between the two VMs inside the ESXi.

1. Log in to the Linux VM and open the ―Network Card‖ from the YaST control center as

described in section 5.2.1 above.

In the ―Network Setup Method‖ window, choose the option ―Traditional Method with ifup‖


© SAP AG of 77

2. In the next window, select the option ―VMWare Abstract PRO/1000 MT single Port Adapter‖

and click on ―Edit‖


© SAP AG of 77

3. In the next screen, enter your IP address and in the ―Detailed Settings‖ section, choose

―Additional Addresses‖ in the ―Advanced‖ drop down menu


© SAP AG of 77

4. The fields in this screen have fixed values. Enter the following values as shown the screenshot

and click ―OK”

Alias Name: sapds4

IP Address: 192.168.101.23

Netmask: 255.255.255.0


© SAP AG of 77

4.2.3 Hosts file settings on the Linux VM

NOTE: Follow the instructions exactly as described below to configure the hosts file. If

the hosts file is incorrect, the system will not function as expected and the demo scenarios

will not work.

1. Log in to the Linux VM using root/admin123 and start the YaST tool as described in

the steps before.

2. Click on ―Network Services‖ and then ―DNS and Hostname‖. Add the Hostname and

Domain Name as shown in the screenshot.

3. From the desktop, double click on the My Computer icon. Navigate to Root Folder/etc.

Scroll down and open the hosts file. Change the IP address to 192.168.101.23 in the

sapds4 entry.

The hosts file should look like this:

192.168.101.23 sapds4.sap.ds.com sapds4 iwdfvm2222 iwdfvm2222.wdf.sap.corp

cdi6boe


© SAP AG of 77

To check if the network settings on the Linux VM is correct, log in to Putty (instructions

to download Putty are given in Section 5) with username root and password admin123.

Type ―ping –c 5 sapds4‖ at the prompt and you should see a ping response.


© SAP AG of 77

4.3 Network Configurations on the Windows VM 4.3.1 Assign an external IP address to the Windows VM 1. Login to the ESXi and open the Windows console

2. Open SettingsControl PanelNetwork and Sharing CenterManage

Network ConnectionsLocal Area Connection Network. Right click and select

Properties. Select Internet Protocol Version 4 and click on ―Properties‖.

Change the local area settings: Obtain the subnet mask, default gateway and

the DNS address from your IT. Please note that the IP address must be a fixed IP.

DHCP is not supported.

In this example, we use:

Subnet mask: 255.255.254.0

Default gateway: 172.16.4.1

DNS NameServer: 10.17.121.30

This enables direct connection to the system from your network.


© SAP AG of 77

4.3.2 Assign an internal IP address to the Windows VM

1. From the Windows VM, open a command prompt.

2. Type the following and press Enter:

netsh interface ipv4 add address name=”Local Area Connection”

192.168.101.22 255.255.255.0

Note: In our example the name of the primary network adapter is ―Local Area Connection‖.

This might be different in your windows version, type ―ipconfig‖ and look for the string after

―Ethernet adapter‖, to get the name of your primary network adapter.

3. To make sure that IP addresses have been assigned correctly, check if they are active by using

the ipconfig command.

For example:


© SAP AG of 77

4.3.3. Hosts files settings on the Windows VM

NOTE: Follow the instructions exactly as described below to configure the hosts file. If

the hosts file is incorrect, the system will not function as expected and the demo scenarios

will not work.

1. Log in to the Windows VM and open notepad.

2. Open C:\windows\system32\drivers\etc\hosts and make sure that the IP address in the sapds4

entry is set to 192.168.101.23. This is the IP you gave the Discovery system in the previous step.

The hosts file should look like this:

192.168.101.23 sapds4 sapds4.sap.ds.com iwdfvm2222 iwdfvm2222.wdf.sap.corp cdi6boe

4.4 Required DNS Settings

The out-of-the-box scenarios on the Discovery System use a fixed naming convention to access

the system. To make sure the scenarios run correctly from any remote client, apply the following

instructions.

Add the following server names to your company DNS configuration, together with the IP

address of the Discovery System:

sapds4

sapds4.sap.ds.com

iwdfvm2222

iwdfvm2222.wdf.sap.corp

To check if the DNS settings is working, open a command line window, and ping sapds4. The

ping should be successful.

Note: The iwdfvm2222 and iwdfvm2222.wdf.sap.corp entries are required for some of the

demo scenarios to work correctly. Make sure you add these values to your company DNS

settings.


© SAP AG of 77

5. Third Party Software on the Windows VM The following the software is utilized by different components and many of the

demonstration scenarios will not work without them.

The IE security settings have to be modified before third party software can be downloaded

and installed.

Modify the IE browser security settings to Custom Level by navigating to ToolsInternet

OptionsSecurity. Check the Prompt attribute for both ―Download Signed ActiveX

Controls‖ and for ―Run ActiveX controls and plug-ins.‖

Note: To transfer files from between the Windows VM and the Linux VM, use the ―Linux

VM File System‖ shortcut on the Windows desktop.


© SAP AG of 77

Alternately, navigate to StartRun. Type in \\sapds4\sapdata and click on ―OK‖ to open the

Linux file system.

5.1 JAVA SDK Installation 1 Download and run the standard Windows Platform installation of J2SE v 1.5.0_X SDK from

Sun. X stands for the latest version of J2SE 1.5.0 available. In February 2010, this version

was 1.5.0_22. The JDK can be installed from

http://java.sun.com/javase/downloads/index_jdk5.jsp

2 Scroll down the page and click on ―Download‖



© SAP AG of 77

3 Enter the required details in the form and continue with the download.


© SAP AG of 77

4 Select the folder C:\Program Files (x86)\Java:\jdk1.5. 0_22

5 Continue with the rest of the installation.


© SAP AG of 77

5.2 Adobe Reader Installation 1 Download and run the standard installation of the Adobe Reader, version 9.2, from Adobe:

http://get.adobe.com/reader/?promoid=BUIGO

2. Click on ―Install‖ in the popup window and continue with the rest of the installation.

http://get.adobe.com/reader/?promoid=BUIGO


© SAP AG of 77

5.3 Adobe Flash Installation 1 Modify the IE browser security settings to Custom Level. Check the Prompt attribute for

both ―Download Signed ActiveX Controls‖ and for ―Run ActiveX controls and plug-ins.‖

2 Download and run the standard installation of the latest Adobe Flash Player from www.adobe.com. Click on ―Install‖ in the in the popup window and continue with the rest of

the installation.

http://www.adobe.com/


© SAP AG of 77

5.4 Adobe SVG Installation 1 The Adobe SVG viewer is required if you plan to use the SAP Visual Composer.

Download and run the standard installation of the latest Adobe SVG Viewer from http://www.adobe.com/svg. Select ―Viewer download‖, you can use the version for Window

98-XP.

http://www.adobe.com/svg


© SAP AG of 77

5.5 Putty A telnet/SSH client such as Putty is required for the administration of SAP

BusinessObjects components installed on the Linux VM.

1. Download Putty from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html.

2. Install Putty and open the program to

complete the configuration. Add

„sapds4.sap.ds.com― as the Host Name and

22 for the port number.

http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html


© SAP AG of 77

5.6 Cryptographic files

5.6.1 Third party cryptographic file Third party provided cryptographic files are required for the SAP PI, SAP NetWeaver

Portal and the SAP NetWeaver CE instances to function correctly.

NOTE: Copy the cryptographic files to the correct folder as described below. Copying the

cryptographic files to the wrong location will result in some SAP instances not starting up

correctly and/or the BusinessObjects applications not working as expected.

1. SAP Note 81008 describes the JVM information for Linux servers. The JCE policy

files can be downloaded from

https://www14.software.ibm.com/webapp/iwm/web/reg/pick.do?source=jcesdk&lang=en

_US

2. Place the downloaded zip JCE policy file in \\sapds4\jce\ibmvmjce

3. Download the Sun JDK JCE policy files from http://java.sun.com/javase/downloads/index_jdk5.jsp. Scroll down the page to “Other Downloads”

4. Place the JCE policy file in \\sapds4\jce\sunvmjce

5. To install the JCE policy files, log in to the Linux server using Putty.

https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=810008

https://www14.software.ibm.com/webapp/iwm/web/reg/pick.do?source=jcesdk&lang=en_US

https://www14.software.ibm.com/webapp/iwm/web/reg/pick.do?source=jcesdk&lang=en_US



© SAP AG of 77

User: root

Password: admin123

At the Linux prompt

switch to JCE folder

by entering

cd /sapdata/jce.

Press ―Enter‖

At the prompt type ./installjce.sh. Press ―Enter‖. The policy files will be installed.

Note: After executing the script, you may see the message ―/ ’ is not a directory: No such

file or directory….‖. These messages can be ignored.


© SAP AG of 77

5.6.2 SAP Cryptographic Software SAP Cryptographic files are required following reasons:

Enable secure collaborative business scenarios to mySAP.com customers by using

asymmetric cryptography and digital certificates

Allow customers to perform single sign-on to all internal and external systems

Provide secure access to current and future marketplaces on the Internet

No administration is necessary as the registration and authentication processes are

fully automated

You are part of the SAP Trust Community, that is founded on SAP's existing

customer base

1. The SSO libraries can be downloaded from http://service.sap.com/tcs

SAP Download Area SAP Cryptographic Software

More information on the SSO libraries can be found in the SAP Notes 662340 and

455033

2. Copy the ticket to folder /usr/sap/<SID>/DVEBMGS<Nr>/sec

3. Copy the libraries to folder $DIR_EXECUTABLE and make sure they have 775

read/write access

4. Restart the DS4 Instance to have the SAPCryptoLib for SSO/SSF become active

5. Create the SSL Tickets by executing the transaction ―STRUSTSSO2‖ in the ERP

(DS4) instance

http://service.sap.com/tcs


© SAP AG of 77

Check the SSO/SSF configuration with transaction STRUSTSSO2

System PSE and Certification List:

Go to Menu Environment Display SSF Version

Go to Menu Environment SAP Logon Ticket check with the default RFC

destination NONE

Optionally, you can use the settings from Note 1249794 to verify your installation

6. Restart the ERP (DS4) instance.

A complete documentation can be found in the following SDN article

http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70bd59d6-

3a4b-2b10-bfab-d0c3bd8abf15

5.7 Microsoft Office BusinessObjects solutions such as Xcelsius and LiveOffice require Microsoft Office. If you

intend to use Xcelsius or LiveOffice, install Microsoft Office on the Discovery system before you

install the BusinessObjects software.

http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70bd59d6-3a4b-2b10-bfab-d0c3bd8abf15

http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70bd59d6-3a4b-2b10-bfab-d0c3bd8abf15


© SAP AG of 77

6. License Keys

This section describes the process for requesting license keys for the SAP instances and the

BusinessObjects Components and the steps to install them on the system.

SAP and BusinessObjects licenses

The SAP instances that require license keys are the ERP, Process Integration (PI), Composition

Environment (CE), Portal and Solution manager instances.

The BusinessObjects components that require license keys are BOE Premium, Live Office,

Xcelcius Enterprise 2008, Data Services, Data Federator and SAP IK.

The following section describes the steps to obtain and install the required licenses.

6.1 Obtain the Hardware Key The hardware key is required to request the license key for all the SAP instances. To obtain the

hardware key:

1. Open the SAP MMC and start the DS4 instance. If prompted, enter the username as

Administrator and no password..

2. Log in to the ERP (DS4) using SAP GUI. Use client 001, sap*/admin123

3. Enter transaction code ―SLICENSE‖

4. The hardware key is displayed. Copy it to the clipboard.


© SAP AG of 77

6.2 Request the License Keys 1 Request license keys using the form from SCN:

https://www.sdn.sap.com/irj/sdn/discoverysystem-license

Note that an S-user is required to obtain the license keys.

2 Review the SAP 180 day evaluation license agreement and accept it at the bottom of the

page.

3 Provide the hardware key obtained in the previous step.

4 Complete the rest of the form.

5 The email address field will be pre-filled with the address maintained with your current S-

User. Confirm this address or adjust as needed. Make sure that you provide a valid email

address, as the necessary license keys will be emailed to the address specified.

https://www.sdn.sap.com/irj/sdn/discoverysystem-license


© SAP AG of 77

6 After you have completed all the required fields, click on the ―Submit‖ button at the end of

the form.

7. The license keys will be emailed to the address specified.

Note: All license key requests are processed automatically. Usually you will receive the license

keys via email in a short time — about 1 hour, maximum 3 working days. Please refrain from

sending multiple requests for the same system.

6.3 Apply the SAP License Keys This section describes the steps to install the licenses on the system.

6.3.1 Apply the ERP license key

1 Start the ERP instance using the SAP MMC. Username is Administrator and no password.


© SAP AG of 77

2 Expand the tree and wait until all the ABAP processes are running. Use the refresh button to

check the status

3 Open SAP Logon and choose the SAP Discovery Server ERP.


© SAP AG of 77

4 Logon with the following information and press Enter:

Client: 001

user: sap*

password:

admin123

5. Enter transaction code ―SLICENSE‖.

6. Choose New Licenses.

7. You will see that there is no license installed. Click on the Install button.


© SAP AG of 77

8. Then browse to your license file, select it, and click on Open.

9. This will be the resulting message.

9. Log off client 001. Then Stop and Start the SAP instance by right clicking DS4 in the SAP

MMC. After stopping you have to wait until the icons under the SAP instance section turn

gray (this will take a little time, and to see if it is done, click the refresh button).

Starting the instance back up takes a couple minutes as well (the icons should also be colored

again).


© SAP AG of 77

6.3.2 Apply the PI License Key

1. Start the DM8 instance using the SAP MMC. Username is Administrator and no

password

2. Expand the tree and wait until all the ABAP processes are running. Use the

refresh button to check the status

3. Open the SAP Logon and choose the SAP Discovery Server PI instance

4. Logon with the following information and press enter:

client:001

user: sap*

password: admin123

5. Enter transaction code ―SLICENSE‖

6. Choose New Licenses

7. You will see that there is no license installed. Apply the valid license and install it

by choosing the Install button.

8. Then browse to your license file, select it, and click on Open

9. This will be the resulting message

10. Log off client 001. Then Stop and Start the PI instance by right clicking DM8

and clicking stop then start afterwards. After stopping you have to wait until the

icons under the SAP instance section turn gray (this will take a little time, and to

see if it is done, click the refresh button).


© SAP AG of 77

6.3.3 Apply the CE license key

1. Start the CEM instance using the SAP MMC. Username is Administrator and

no password

2. Expand the tree and wait until all the Java processes are running. Use the

refresh button to check the status

3. Open the URL http://sapds4:51000/nwa in Internet Explorer

4. Login with username Administrator and password admin123

5. Navigate to Configuration ManagementInfrastructureLicenses

6. Click on the ―Install from file‖ button and select the CEM license key.

7. After you add the license, the status should read ―Valid‖.

http://sapds4:51000/


© SAP AG of 77

6.3.4 Apply the Portal License Key

1. Start the portal (EP4) instance in the SAP MMC. Username is Administrator and

no password. Wait for the icon to turn completely green.

2. Log in to the Linux VM using root/admin123 as explained above in section

4.2.1. Select the SAP Discovery Server 4 on the left side, and click on the

―Console‖ tab to open the Linux VM console.


© SAP AG of 77

3. Open a ―Command Prompt‖ window. Launch the Visual Administrator by

typing the following:

Switch to the root directory by typing

cd..

cd usr/sap/EP4/JC70/j2ee/admin

go and press Enter


© SAP AG of 77

4. Login using username J2ee_admin and password admin123

5. Select the Server node. Navigate to ServicesLicensing adapterInstalled

Licenses

6. In the General tab, click on ―Install from file‖ button. Select the EP4 license key

and add it. The message ―License Successfully Installed‖ should be displayed.


© SAP AG of 77

7. Restart the EP4 instance from the SAP MMC ( in the Windows VM). The icon

will become green

6.3.5 Apply the Solution Manager License Key

1. Start the SOL instance using the SAP MMC. Username is Administrator and no password

2. Expand the tree and wait until all the ABAP processes are running. Use the refresh button to

check the status

3. Open SAP Logon and choose the SAP Solution Manager instance.


© SAP AG of 77

4. Logon with the following information and press enter:

Client: 001

user: sap*

password: admin123

5. Enter transaction code ―SLICENSE‖.

6. Choose New Licenses.


© SAP AG of 77

7. You will see that there is no license installed. Apply the valid license and install it by

choosing the Install button.

8. Then browse to your license file, select it, and press Open.

9. This will be the resulting message.

10. Log off client 001. Then Stop and Start the Solution Manager instance. After stopping you

have to wait until the icons under the SAP instance section turn gray (this will take a little

time, and to see if it is done, push the refresh button). Starting the instance back up takes a

couple minutes as well (the icons should also be colored again).


© SAP AG of 77

6.4 Apply the BusinessObjects License Keys

6.4.1 Start the BOBJ servers

Before applying the license keys, the BOBJ servers have to be started. The following section describes the steps to start the servers.

6.4.1.1 Starting the BOBJ Enterprise XI 1. Launch Putty and log in to the Linux VM using root/admin123

2. At the Linux prompt switch the using by typing

su bouser

3. In the command line, type

source ~/.bash_profile

4. Change directory to bobje by typing

cd /sapdata/bo/xir3/bobje


© SAP AG of 77

5. Start the MySQL server by typing

mysqlstartup.sh

6. After MySQL starts, start the servers by typing

startservers

7. Once the servers are start, start Tomcat by typing

tomcatstartup.sh

6.4.1.2 Starting the Data Federator 1. Launch Putty and log in to the Linux VM using root/admin123 if not already logged in

2. At the Linux prompt switch the using by typing su bouser

3. Switch to the Data Federator directory by typing

cd /sapdata/bo/xir3-datafedarator

10. Change to the bin directory by typing

cd bin

11. Start the Data Federator by typing

startup.sh

6.4.1.3 Starting the Data Services

1. Launch Putty and log in to the Linux VM using root/admin123 if not already logged in

2. At the Linux prompt switch the using by typing su bouser

3. Switch to the bobj3 directory by typing

cd /sapdata/bo/xi3-dataservices/bobje

4. Start Tomcat by typing

tomcatstartup.sh


© SAP AG of 77

6.4. 2 Apply the BOBJ Enterprise XI License Key

1. The BOBJ Enterprise XI license key is listed in the license key email you received.

Copy the license key to the clipboard.

2. Open Internet ExplorerFavoritesBusiness ObjectsCentral Management

Console.


© SAP AG of 77

3. Log in with administrator/no password.

4. Select ―License Keys‖ under Manage

5. Enter (or paste from clipboard) the license key and click on the Add button


© SAP AG of 77

6.4.3 Apply the BOBJ Data Federator License Key

1. The BOBJ Data Federator license key is listed in the license key email you received.

Make a note of the license key. 2. Open the Linux file system using the shortcut available on the Windows desktop.

3. Navigate to sapds4sapdataboxir3-datafederatorkeycode

4. Open the keycode folder. Select the licence file, right click and open it with Notepad.

5. Enter the license key followed by a colon (:) and the expiration date of the license in

the format yyyymmdd and add a semi-colon (;) at the end of the license key. Save and

close the file.

6. Restart the server by switching back to Putty and typing shutdown.sh and then

startup.sh.

6.4.4 Apply the BOBJ Data Services License Key

1. The BOBJ Enterprise XI license key is listed in the license key email you received.

Make a note of the license key. 2. Login in to the Linux VM using root\admin123 as described in section 4.2.1.

3. Open a shell prompt by double clicking on the icon on the status bar.


© SAP AG of 77

4. Switch user to the BOBJ user by typing su bouser

5. In the command line, type source ~/.bash_profile

6. Switch to the bin directory of the Data Services by typing

cd..

cd xir3-dataservices/dataservices/bin

7. Install the license key by typing LicenseManager --add <yourlicensekey> and press Enter

You can ignore the message ―The environment variable BOE_REGISTRYHOME has not

been set in your environment‖ if it is displayed.

6.4.5 Install XCelcius and apply the License Key You need to install SAP BusinessObjects XCelcius if you plan on using it. To apply the

license key, launch XCelcius and click on the ―Enter Keycode‖ button. Enter the key

(listed in the license key email) in the License Manager window and click on ―OK‖ to

continue with the rest of the installation.


© SAP AG of 77

7. Migrate the Secure Store in the ABAP system When there is any change to the SAP NetWeaver 7.x system, including change in SID,

installation number or installation of new license keys, the transactions in the Secure Store are

locked. The secure store must first be migrated before continuing to use the system. The 32-bit

migration key is provided by SAP and can be downloaded from the SAP Service Market place.

1. Log in to the SAP Service Market place—http://service.sap.com

2. Switch to the Keys & Requests tab and click on Migration Keys

3. In the Migration Key for the Secure Store, click on the „Request migration key― link.

4. Enter the requested details and obtain the migration key.

5. After you have received the migration key, log in to the DS4 and execute transaction

SECSTORE

6. Switch to the ―System data changed‖ tab and install the migration key


© SAP AG of 77

8. The secure store entries should be green

8. Finalize Installation Apply all corrections that have posted in the Discovery System Central Note 1431318


© SAP AG of 77

9. Deploy the OVF Template (Revert to Initial Settings).

Note: Follow the instructions below only if you want to go back to the state of the VM

when you took a backup of the VM (initial settings). All changes made to the system

after backup will be lost!

1. Log in to the ESXi using the VSphere client. Log in using root/VMware123

2. Shut down the Linux server VM

3. Select the SAP Discovery Server 4 on the left side

4. Click on FileDeploy OVF Template.


© SAP AG of 77

7. Enter a unique name and complete the import by clicking on ―Next‖ and ―Finish‖ in the

following windows.


© SAP AG of 77

10. Troubleshooting The section below lists solutions to common problems. For the most recent updates refer to the

Discovery System Central Note 1431318 1. If you are not able to access the Linux VM, check the Network Configurations on the Linux.

1. Log on to the Linux VM.

2. Open a shell prompt enter cat /etc/hosts and check if the hosts file looks like this:

# # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname # 127.0.0.1 localhost # special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback fe00::0 ipv6-localnet ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 192.168.101.23 sapds4 sapds4.sap.ds.com iwdfvm2222 iwdfvm2222.wdf.sap.corp


© SAP AG of 77

2. When executing the BOBJ demo scenarios if you get the message ―There is no AA analytics

Server Available…..‖, follow the instructions below:

1. Log in to the BOBJ Central Management Console (from the IE favorites or using the Administration page http:<yourIPaddress:8080>/starthere/admin.jsp). Click on the “Servers” link.


© SAP AG of 77

2. Select the “Disabled” servers (multiple servers can be selected using the Shift or Control key), right click and choose “Enable Server”

3. When connecting to the MDM repositories, if you get the message ―Invalid repository‖, follow

the instructions below:

1. Log in to MDM using the SAP MDM console.

2. Select the repository. Right click and select ―Unmount Repository‖.

3. Now re-mount the repository by selecting the repository, right click and select ―Mount

Repository‖. Use SAPMDMDB /SAP as the credentials.

You will now be able to connect to the repositories.

4. If the shortcut to the Linux file system is missing in the Windows VM, you can access the

Linux file system by navigating to StartRun and typing \\sapds4\sapdata.

5. If the NetWeaver Administrator URL or any of the other application web pages do not open,

follow the instructions below:

1. FromIE 8 menu, navigate to ToolsInternet OptionsSecurity. Uncheck the „Enable

Protected Mode― checkbox. This can be repeated for each zone as needed.

2. Navigate to StartAdministrative ToolsServer Manager. In the „Security Information―

section, click on „Configure IE ESC―. Uncehcl the radio button for Administrators and/or

Users.

sap discovery system v4 enhanced quick guide discovery system quick guide sap discovery system v4...

Documents