SAP Discovery System for Enterprise SOA Quick Guide

SAP Discovery System for Enterprise SOA

Quick Guide SAP Discovery System V2 Quick Guide August 2008 English

SAP Discovery System Quick Guide for Enterprise SOA

SAP AG Neurottstr. 16 69190 Walldorf Germany

SAP Discovery System for Enterprise SOA Quick Guide

SAP AG Page 2 of 26

Copyright Copyright 2007 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 AG Page 3 of 26

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.

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


SAP AG Page 4 of 26

Contents SAP Discovery System for Enterprise SOA Quick Guide ......................................................... 5 1 Purpose .............................................................................................................................. 5 2 Licensing Options & Migration Key .................................................................................... 5 3 Critical Factors.................................................................................................................... 6

3.1 Hostname................................................................................................................. 6 3.2 Database Server ...................................................................................................... 6

4 Backup Recommendations ................................................................................................ 6 4.1 Initial Backup............................................................................................................ 6 4.2 Maintenance Backup................................................................................................ 6

5 Installation .......................................................................................................................... 6 5.1 Initial Database Setup .............................................................................................. 6 5.2 Third Party Software ................................................................................................ 8

5.2.1 JAVA SDK Installation ......................................................................................... 8 5.2.2 Adobe Reader Installation ................................................................................... 9 5.2.3 Adobe Flash Installation. ................................................................................... 10 5.2.4 Adobe SVG Installation...................................................................................... 12

5.3 License and Migration Keys................................................................................... 13 5.3.1 Apply a Migration Key........................................................................................ 13 5.3.2 Request a License Key...................................................................................... 15 5.3.3 Apply the License Key ....................................................................................... 17 5.3.4 Clean-up ERP Instance ..................................................................................... 20

5.4 Additional Installation Steps................................................................................... 21 5.4.1 Attach Northwind Database ............................................................................... 21 5.4.2 Apply Adobe Rights Credentials ........................................................................ 21 5.4.3 Restart MDM service ......................................................................................... 23 5.4.4 Finalize Installation ............................................................................................ 24

6 Troubleshooting................................................................................................................ 24 7 Users name & Passwords ................................................................................................ 25


SAP AG Page 5 of 26


1 Purpose This quick guide provides the information you need to install, load and run the SAP Discovery System for enterprise SOA V2. It also explains how to do basic troubleshooting.

Before proceeding with this guide, make sure that you purchased the SAP Discovery System V2 and not the new version of the system (V3)! To check the version of the system you have, please refer to the following document: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/7914 In case you find out that your system is not of version 3, do not proceed with this document. Instead, you can find the appropriate quick guide for the Discovery System V3 under: https://www.sdn.sap.com/irj/sdn/esoadiscovery?rid=/webcontent/uuid/a1016c89-0d01-0010-8faf-f15f3c4f0e5f

2 Licensing Options & Migration Key

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.

You will also need to request a no-cost migration key through the Migration Key Request Form. It is highly recommended that you start by applying for the migration key.

Request a migration key through the Migration Key Request Form. Use the following information:

For HP customers use the following link: http://www.sap.com/community/survey/index.epx?SurveyID=542

For Fujitsu-Siemens customers use the following link: http://www.sap.com/community/survey/index.epx?SurveyID=541 In case that you have completed the form successfully and have not got an email with the migration key after 24 hours, please open a SAP CSS message with the following information: CSS Component: CA-SOA-DS

Short Text: SAP Discovery System Migration Key Copy/paste below into message Company Name:


SAP AG Page 6 of 26

Contact Person Name: Contact Person Email Address Contact Person Phone Number: Hardware Provider [HP or Fujitsu-Siemens]: Reseller Name [If system was not bought directly from one of the Hardware Partners above, please provide the Reseller name]:

3 Critical Factors

3.1 Hostname While configuring the SAP Discovery System, preset scripts are run. They are based on the predefined hostname. DO NOT CHANGE THE HOSTNAME. This will cause loss of system usage!

3.2 Database Server DO NOT CHANGE THE PASSWORD OF YOUR DATABASE. Installation scripts use embedded passwords!

4 Backup Recommendations

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

4.2 Maintenance Backup Immediately, backup your two operational drives after completing installation instructions and whenever major development milestones are achieved.

5 Installation

5.1 Initial Database Setup Important: Please follow the steps carefully.

1 Make sure the Discovery System is connected to the network.

2 Logon to the server using user: Administrator password: sap123.

3 Run the script D:\SQL_EVAL\SQL2005\SQL4SAP.vbs


SAP AG Page 7 of 26


SAP AG Page 8 of 26

Note: Installation will take some time.

4 After installation is complete please reboot Windows.

5 Run Script D:\SQL_EVAL\attach_dbs.bat

6 Verify that a

D:\SQL_Eval\dbs_attach.log file has been created.

5.2 Third Party Software The following the software is utilized by NetWeaver and many of the demonstration scenarios will not work without them.

5.2.1 JAVA SDK Installation 1 Download and run the standard Windows Platform installation of J2SE v 1.4.2_X SDK

from Sun. X stands for the latest version of J2SE 1.4.2 available. on June 2007 this version is 1.4.2_14


SAP AG Page 9 of 26

2 IMPORTANT!!! You must install it in folder D:\j2sdk1.4.2.

Select Run.

5.2.2 Adobe Reader Installation 1 Download and run the standard installation of the Adobe Reader, version 7.0.9, from

Adobe: http://www.adobe.com/products/acrobat/readstep2_allversions.html


SAP AG Page 10 of 26

5.2.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



5.2.4 Adobe SVG Installation 1 Download and run the standard installation of the latest Adobe SVG Viewer from

www.adobe.com/downloads. You can use the version for Window 98-XP.



5.3 License and Migration Keys 5.3.1 Apply a Migration Key

1 Start the ERP instance using the SAP Management Console located on the desktop and right clicking on ERP and selecting start. The password is sap123 (the process will take about 5 10 min.) You will find that the J2EE engine will not fully start because of the missing license but the ABAP engine will start fine.

You can verify that the ABAP engine was started successfully by clicking on the ABAP WP Table node and check that all processes are started (see image below)

2 Open up SAP Logon and logon to the discovery system. Then logon to the ERP client

001 , User ID: sap* Password: pass

3 Apply the migration key to the Secure Store. Enter transaction code SECSTORE in the top left corner search box and click enter ( )

In order to complete this step you must have the migration key you have requested for via the Migration Key Requests Form as described in the beginning of this guide (Step 2: Licensing Options and Migration Key).



4 Click on execute.

5 You will notice that the status of all entries is red.

6 Click Back ( ), choose System data changed tab and apply the information

according to the table below:

Server Vendor Old System Name

Old Installation Number

Release Key (Migration Key)

Hewlett-Packard

0120003411

Fujitsu-Siemens

ERP SAP-INTERN

Sent by SAP in an email as a response to the CSS request in the previous steps



7 Click Execute Please note that the entries will change from red to green only after applying the license key in the next steps and restarting the server.

5.3.2 Request a License Key 1 Apply for a license key on SAP Support Portal service.sap.com/licensekey

2 Select Request license key to display your installation overview.

3 Select your installation number with SAP product SAP ERP or SAP R/3 to display your system overview.

4 Select New system.

5 Add the required system data.

6 Click on Continue. 7 If you receive no warning icon choose Continue to go on with the request.



7.1 If you receive the warning icon, you may want to try a different installation number for SAP ERP or SAP R/3(providing you have more than one). If you do not have another installation number for SAP ERP or SAP R/3, proceed as described in the popup and notify your Account Executive.

8 Add the hardware key, choose license type Standard. Save the data and Continue.

9 On the submit page check and confirm your email address and choose Submit to send your request to SAP.



5.3.3 Apply the License Key

1 After you receive your license key, open SAP Logon and choose the ERP ESA Discovery instance.

2 Logon with the following information and push enter:

Client: 000 user: sap* password: pass

3 Enter transaction code SLICENSE.

4 Choose New Licenses.



5 You will see that there is no license installed. Apply the valid license and install it by choosing the Install button.

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

7 This will be the resulting message.



8 Log off client 000. Then Stop and Start the SAP instance by right clicking ERP 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, push the refresh button).

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

9 If you go back to transaction SECSTORE (ERP client 001, User ID: PISUPER

Password: sapides123), entries that were previously red should become green.



5.3.4 Clean-up ERP Instance 1 Click the back button and go to the original page, and then go to Transaction SMQ1.

Delete all the existing jobs in client 001. If there are no existing jobs, ignore this step

2 Go to transaction SU01 (if it doesnt work, click back and go back to the original page and then type in SU01). Unlock the user WF-BATCH. If the user is not locked, ignore this step.

3 Logon to client 200 user: PISUPER password: sapides123. Go to Transaction SMQ1. Delete all the existing jobs in client 200.

4 Go to Transaction SU01. Unlock the user RFCUSER. If the user is not locked, ignore this step.



5.4 Additional Installation Steps 5.4.1 Attach Northwind Database 1 Open Microsoft SQL Server Management Studio and attach the Northwind database.

User: sa Password: sapides123

2 Right-click on the Databases node Attach Add

5.4.2 Apply Adobe Rights Credentials 1 Adobe Document Services require access to a credential in SAP Web AS to assign

usage rights to PDF documents. This is typically the Adobe Reader Rights credential. For more information on the configuration, please refer to http://service.sap.com/adobe -> Media Library -> Documentation

-> Adobe Document Services - Configuration Guide NW 2004s

2 There are two options for obtaining an Adobe Reader Rights Credential.

2.1 Option 1 Trial (for immediate use): Download a limited trial credential and password from SDN (expires on August 31st 2007): https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70aa75cc-6ac3-2910-c78c-ade192ec861e

2.2 Option 2 Permanent: http://service.sap.com/licensekey.

2.2.1 Select Third Party Products.



2.2.2 Select Adobe

2.2.3 Create a message for your system using the Message Wizard and the component

BC-SRV-FP. Please also refer to SAP note 736902

3 With both options, the credential you will receive is a PKCS (.pfx)-file that you need to

install.

4 Copy the credential file (.pfx) to the directory: D:\usr\sap\ERP\SYS\global\AdobeDocumentServices\TrustManagerService\trust\credentials

5 Restart the WebAS (by stopping and starting the ERP instance)



6 Configure the credential attributes:

6.1 Log on to the Visual Administrator by going to D:\usr\sap\ERP\DVEBMGS10\j2ee\admin and opening the file go.bat.

User: j2ee_admin password: sapides123

6.2 On the cluster node, choose Server 0 10. -> Services -> Document Services Configuration

6.3 On the Runtime tab, select Credentials

6.4 From the Type field, select the type of credential you are configuring (here: P12 Record)

6.5 In the Alias Field, enter ReaderRights

6.6 Choose Browse to search for the name of the credential and then select it

6.7 In the password field, enter the password you received together with the credential file (the password is stored in the text-file)

6.8 Confirm the password and then click Add

7 Restart the WebAS

8 For more information on the configuration of the Adobe Document Server, please refer to http://service.sap.com/adobe -> Media Library -> Documentation -> Adobe Document Services - Configuration Guide NW 2004s

5.4.3 Restart MDM service 1 Open the SAP MDM Console, double-click the desktop icon.

2 Select the SAP MDM Servers

node. Then from the menu, choose MDM Servers > Mount MDM Servers.

3 Select IWDFVM2160 from the dropdown and choose OK.

4 Select the IWDFVM2160 node.

5 Right-click the IWDFVM2160 node and choose Stop MDM Server > Immediate.



6 Right-click the IWDFVM2160 node and choose Start MDM Servers > Immediate.

7 Wait for the status icon to turn green.

5.4.4 Finalize Installation 1 Apply all corrections that have posted in the Discovery System Central Note 1023661.

6 Troubleshooting

Issue Resolution

Before logging into the DS you receive a Service Control Manager popup appears saying "At least one service or driver failed during system startup..." After logging in you are presented with a Hardware Installation popup for the Smart Array P400 Controller.

See note 1023661

You finished the installation but the j2ee engine doesnt start

Make sure the computer name was not changed (should be iwdfvm2160).

Make sure the SAP license is installed and valid. Make sure the JDK is installed under D:/j2sdk1.4.2 Apply note 990538

Cannot see Portal Portal has not been fully loaded. Make sure you have started the ERP instance in the SAP MMC.

Restart the ERP instance using the MMC.

Cannot save Visual Composer models

Restart the ERP instance using the MMC.

Cannot update backend from Goods Received or Sales Order PDF forms

Ensure Acrobat reader is version 7.05 and above.

Purchase Order tables do not populate

Redo step number 5.4.3



Cannot submit Goods Received or Sales Order form because Period is not closed

This error will occur during demonstrations when a month-end has passed and no demonstration has successfully occurred in the new month. Error example:

Submission failed. Posting only possible in periods 2006/11 and 2006/10.

Login as UserID/Password: proc_admin / sap123.

Choose Procurement > ERP Transactions > R3 Close Period MMPV

Complete:

From Company Code BP01

To Company Code BP01

Date MM/01/YYYY (where MM is month number, 01=January, etc. and just one month later than that shown in error message and YYYY is the year in which the MM occurs )

Select Check and Close Period radio button

Choose Execute

If error continues, it may be since previous months have not been closed before the month you are attempting to close.

During the scenario received error: Application has not started

Go to the SAP Management Console and restart the entire ERP node

The java stack starts with errors related to memory

Increase the page file size of the server to 12 GB

7 Users name & Passwords All users name and passwords for all different systems can be found in the following document: https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/16bf7a3b-0e01-0010-748a-855a7b2c9f6f



CopyrightIconsTypographic ConventionsSAP Discovery System for Enterprise SOA Quick Guide1 Purpose2 Licensing Options & Migration Key3 Critical Factors3.1 Hostname3.2 Database Server

4 Backup Recommendations4.1 Initial Backup4.2 Maintenance Backup

5 Installation 5.1 Initial Database Setup5.2 Third Party Software5.2.1 JAVA SDK Installation5.2.2 Adobe Reader Installation5.2.3 Adobe Flash Installation.5.2.4 Adobe SVG Installation

5.3 License and Migration Keys5.3.1 Apply a Migration Key5.3.2 Request a License Key5.3.3 Apply the License Key5.3.4 Clean-up ERP Instance

5.4 Additional Installation Steps5.4.1 Attach Northwind Database5.4.2 Apply Adobe Rights Credentials5.4.3 Restart MDM service 5.4.4 Finalize Installation

6 Troubleshooting7 Users name & Passwords

Documents

SAP Discovery System for Enterprise SOA Quick Guide