How to Set Up Connection Between Solution Manager and Solution Builder

How To Documentation

Technical Configuration of SAP Solution Manager and SAP BestPractices Solution Builder Integration:Prerequisites

CUSTOMER

Document Version 1.10 (March 07, 2013)

SAP Documentation March 07, 2013

2

Copyright Copyright 2013 SAP AG. All rights reserved.

SAP Library document classification: CUSTOMER

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may bechanged without prior notice.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may bechanged without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registeredtrademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture,Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC,BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF,Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet aretrademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registeredtrademarks of Adobe Systems Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin aretrademarks or registered trademarks of Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C, WorldWide Web Consortium, Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.


3

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerryTorch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry AppWorld are trademarks or registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android aretrademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, SAP HANA, and other SAP products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks of SAP AG in Germany andother countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks ofBusiness Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybaseproducts and services mentioned herein as well as their respective logos are trademarks orregistered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks ofCrossgate AG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.

These materials are subject to change without notice. These materials are provided by SAPAG and its affiliated companies ("SAP Group") for informational purposes only, withoutrepresentation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products andservices are those that are set forth in the express warranty statements accompanying suchproducts and services, if any. Nothing herein should be construed as constituting anadditional warranty.


4

Icons in Body TextIcon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types ofinformation at a glance. For more information, see Help on Helpo General InformationClasses and Information Classes for Business Information Warehouse on the first page of anyversion of SAP Library.

Typographic ConventionsType Style Description

Example text Words or characters quoted from the screen. These include fieldnames, screen titles, pushbuttons labels, menu names, menupaths, and menu options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, andtable titles.

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

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

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

Variable user entry. Angle brackets indicate that you replacethese words and characters with appropriate entries to makeentries in the system.

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


5

Technical Configuration of SAP Solution Manager and SAP Best Practices Solution BuilderIntegration: Prerequisites ...................................................................................................... 1

Copyright........................................................................................................................ 2

Icons in Body Text .......................................................................................................... 4

Typographic Conventions ............................................................................................... 4

Prerequisites for the Technical Configuration of SAP Solution Manager and SAP BestPractices Solution Builder Integration ................................................................................. 6

Introduction .................................................................................................................... 6

General Prerequisites ..................................................................................................... 6

SAP Best Practices Solution Builder tool ..................................................................... 6

SAP Solution Manager tool and content ...................................................................... 6

SAP Solution Manager system landscape (SMSY) ...................................................... 6

Use case-dependent prerequisites ................................................................................. 6

SAP Solution Manager/SAP Best Practices Solution Builder SU01 ........................... 7

SAP Solution Manager SU01 ................................................................................... 7

SAP Best Practices Solution Builder System SM59 [authoring only] ......................... 8

SAP Solution Manager System PFCG [authoring only] ........................................... 10

SAP Solution Manager System/SAP Best Practices Solution Builder System SICF. 14

SAP Solution Manager System SOAMANAGER .................................................... 15

SAP Best Practices SAP Best Practices Solution Builder System SICF .................. 18

SAP Best Practices Solution Builder System SE80 ................................................. 19

SAP Best Practices Solution Builder System SOAMANAGER ................................ 20

SAP Best Practices Solution Builder System /n/SMB/BBI ....................................... 22

SAP Best Practices Solution Builder System /n/SMB/PROXY_MAIN [consumptiononly].......................................................................................................................... 25


6

Prerequisites for the Technical Configuration of SAPSolution Manager and SAP Best Practices SolutionBuilder IntegrationIntroductionAs of Solution Manager 7.1 SP05, SAP Solution Manager and SAP Best Practices SolutionBuilder for SAP Business All-in-One are integrated to handle combined Solution Packages.

This How To documentation describes the prerequisites provided by the technical ITadministration before the authoring steps in the integrated tool landscape start, or theresulting packages can be consumed.

General PrerequisitesThe following are prerequisites to be able to use the SAP Solution Manager and SAP BestPractices Solution Builder integration for implementation.

Usethe newest versions of SAP Solution Manager and SAP Solution Builder for authoring usecases which realize their own solution packages

SAP Best Practices Solution Builder toolAvailable in SAP Software Download Center

x The SAP Best Practices Solution Builder add-on, providing the latest integrationfunctionality, is required in the delivery system of the solution package developmentsystem landscape, i.e. the SAP Best Practices Solution Builder solution package finalassembly systems

x SAP Best Practices Solution Builder tool Addon BP-SOLBLD 70V6 or higher

SAP Solution Manager tool and content

x Available in SAP Software Download Center SAP Solution Manager 7.1 SP05 orhigher

x SAP Solution Manager content ST-RDS 100

SAP Solution Manager system landscape (SMSY)

x To manage access to the SAP Best Practices Solution Builder system from SAPSolution Manager

x Provide a logical component to connect the SAP Best Practices Solution Buildersystem to Solution Manager (system ID, etc.) to be able to call the SAP BestPractices Solution Builder system

Use case-dependent prerequisitesThe following prerequisites depend on the SAP Solution Manager and the SAP Best PracticesSolution Builder integration use case. We distinguish between the consumption and authoringof solution packages.

If ase the paragraph is only needed for one use case, this is specified as a restriction inparentheses at the end of the header line.

The names of technical objects to be realized are proposed. Accept them because some ofthem are reused in the creation of the subsequent object.


7

SAP Solution Manager/SAP Best Practices Solution Builder SU01

Create User (IT Admin User) to Configure Web Service Connectivity

1. Create a dialog user in the SAP Solution Manager and SAP Best Practices SolutionBuilder system to configure the Web Service to use the SAP Solution Manager SAPBest Practices Solution Builder integration.

2. Assign role SAP_BC_WEBSERVICE_CONFIGURATOR and standard roles to this user(according to SAP note 1318883).

IMPORTANT: Check if the role is up to date and update it with the role assigned to thenote.

3. This Web Service has to be configured in the SAP Solution Manager and SAP BestPractices Solution Builder systems, so this role has to be assigned to the users in bothsystems.

4. The following pages illustrate how to configure the Web Services in SOAMANAGER inthe SAP Solution Manager system and in the SAP Best Practices Solution Buildersystem.

Figure: Assign Role SAP_BC_WEBSERVICE_CONFIGURATOR

SAP Solution Manager SU01

Create User to connect SAP Solution Manager and SAP Best Practices Solution Builderfor Web Service and RFC Destination

1. Create generic connectivity user of type SYSTEM, e.g. RFCWEBUSER in the SAPSolution Manager system, to call the SAP Solution Manager from SAP Best PracticesSolution Builder using Web Service and RFC, during authoring and consumption.

2. This generic user will be announced in the Web Service definition in the SAP BestPractices Solution Builder system.The user will also be assigned to the RFC connection from SAP Best Practices SolutionBuilder to SAP Solution Manager.

3. The authorization role is assigned when creating the role.


8

Figure: Maintain User and User Type

SAP Best Practices Solution Builder System SM59 [authoring only]

Maintain RFC Connection to SAP Solution Manager (for each authoring system)

1. Create an RFC connection type of 3 (ABAP) from SAP Best Practices Solution Builder tothe SAP Solution Manager client.

2. This RFC connection transfers documentation links from SAP Solution Builder to tabs inSAP Solution Manager. the documentation is transferred in two steps:

a. Transfer of the SAP Help Portal link to the SAP Solution Manager internalKnowledge Warehouse via RFC (using SAP Solution Manager KW functionmodule).

b. Transfer of the link URL via SAP Solution Manager Web Services, for alldocumentation assignments, to the tabs on Business Process level.

3. Technical Settings tab:Specify target host ldcirdx.wdf.sap.corp, system number 80, and save as host name. DoNOT use the IP address, which could change.

4. Logon & Security tab:Assign the generic user RFCWEBUSER as RFC user in this RFC destination (how tocreate this user in the SAP Solution Manager system is described below). The user nameis a proposal which is also used for subsequent objects.


9

Figure: Create RFC Destination Technical Settings

Figure: Create RFC Destination Logon & Security


10

SAP Solution Manager System PFCG [authoring only]

Maintain Authorization (PFCG) Role for Connectivity User (for each authoring client)

1. The generic connectivity user (e.g. RFCWEBUSER) requires authorization to execute

x SAP Solution Manager Web Services for SAP Solution Manager ProjectMaintenance

x SAP Solution Manager Knowledge Warehouse function modules for documenthandling

x RFC connections accessing the SAP Solution Manager system

2. These authorizations are bundled in an authorization (PFCG) role in SAP SolutionManager.

3. Call transaction PFCG to create the Single RoleZ_SOLMAN_SOLBUILD_CONNECTIVITY.

4. Maintain the authorization data and assign the following authorization object:

x S_RFC, S_SERVICE, S_PROJECT, S_CTS_ADMI, S_CTS_SADM, S_IWB,AI_SA_TAB

5. Assign values to the fields of these authorizations objects.

6. Generate the authorization profile.

7. Assign the role to the generic connectivity user in the SAP Solution Manager system.The following figures show the assignment, with object S_RFC as example.

Figure: Create Single Role


11

Figure: Change Authorization Data

Figure: Add Authorization Objects


12

Figure: Assign Values to Authorization Objects

The following figure lists the authorization objects, including their field values. Add theseobjects to the PFCG role, as described above for object S_RFC.


13

Figure: Authorization Objects and their Field Values


14

Figure: Generation of the Authorization Profile

Figure: Assignment of the Role to the Generic Connectivity User

SAP Solution Manager System/SAP Best Practices Solution BuilderSystem SICF

Web Service Connectivity (client-independent)

1. Some HTTP services in the SAP Solution Manager and the SAP Best Practices SolutionBuilder systems are prerequisites for configuring the Web Service connectivity.

2. Start transaction SOAMANAGER.

3. If the SOA Management environment starts without error messages, all relevant servicesare already active. Otherwise proceed with the next steps.

4. Start transaction SICF.

5. Choose Execute.

6. In the Virtual Hosts/Services hierarchy, search for the following services:

a. sap public myssocntl

b. sap bc webdynpro sap APPL_SOAP_MANAGEMENT

c. sap public bc icons

d. sap public bc icons_rtl

e. sap public bc pictograms

f. sap public bc ur


15

g. sap public bc webdynpro

h. sap public bcwebicons

7. In case a service is not active (gray) choose Service/Host Activate.

Figure: Maintain Services with Transaction SICF (HTTP Service Hierarchy Maintenance)

Figure: Activation of a Service

SAP Solution Manager System SOAMANAGER

Web Service Connectivity (client-dependent)

1. SAP Solution Manager system is part of Web Service connectivity.

2. Start transaction SOAMANAGER in SAP Solution Manager system.

3. Choose tab Service Administration.


16

4. Choose Web Service Configuration (or Single Service Configuration in older releases).

Figure: Choosing Web Service Configuration on Service Administration Tab

5. Search for service definition BSIPROJECTDIRECTROYINTERFACE.

6. Choose from result list and choose Apply Selection.

7. On Configurations tab, choose Create endpoint if no endpoint exists. Otherwise proceedwith step On Overview tab

Figure: Web Service Configuration

Figure: Applying Building Information

8. Configure the security settings (like User/Pass Authentication on Transport Level).


17

Figure: Configuration of Security Settings

9. Choose Save.

10. On Overview tab select the created binding from the drop-down list on the right-handside.

11. Click the link Open WSDL document for selected binding or service.

Figure: Selection of the Created Binding

12. The WSDL you need for runtime tests (or generation of logical ports) is displayed in yourbrowser.

13. Save the WSDL as file.


18

Figure: Saving the WSDL as file

14. ONLY if you have to re-create the endpoint (e.g. changed structure in new release):Leave SOAMANAGER after deleting former endpoint and call transaction again, to avoidinconsistencies. Download the new WSDL document

SAP Best Practices SAP Best Practices Solution Builder System SICF

Web Service Connectivity - Check proxy settings

1. Call transaction SICF in SAP Best Practices Solution Builder system/client.

2. Choose F8.

3. Choose Client Proxy Settings.

4. Check whether the properties in the following figure are populated:

Figure: Checking Proxy Configuration


19

SAP Best Practices Solution Builder System SE80

Web Service Connectivity Regeneration of client proxy definition

1. Call transaction SE80 in SAP Best Practices Solution Builder system ( 70V2).

2. Select Package /SMB/ and choose Enterprise Services Service Consumer/SMB/CO_BSI_PROJECT_DIRECTROY1In older releases, use path Enterprise Services Client Proxies.

3. Switch to change mode and click on button Generate.

4. In the dialog box, select Local File as Service Consumer and click on Continue.

5. Select the saved WSDL file which you are got from SAP Solution Manager system andclick on Continue and then on Complete.

6. If the definition needs to be updated, save and activate all changes after regeneration.DO NOT save again after activation, to avoid problems.

7. ONLY in case of structural changes within WebService:Re-generate and reactivate, using new WSDL document.

Figure: Regeneration of client proxy definition


20

Figure: Selection of WSDL from a Local File

SAP Best Practices Solution Builder System SOAMANAGER

Web Service Connectivity/Create Logical Port (for each authoring or consumptionclient

1. SAP Best Practices Solution Builder system is part of Web Service connectivity.

2. Start transaction SOAMANAGER in SAP Best Practices Solution Builder system.

3. Choose tab Service Administration tab.

4. Choose Web Service Configuration (or Single Service Configuration in older releases).

Figure: Transaction SOAMANAGER with Service Administration Tab

5. Select Consumer Proxy from drop-down list Search by: and enter Search Pattern:BsiProjectDirectroyInterface case-sensitive.

6. Choose from result list and choose Apply Selection.

7. On Configurations tab, choose Create Logical Port.


21

Figure: Selection of Consumer Proxy

8. Enter a logical port name, e.g. SAP_SOLUTION_MANAGER__ and a.

9. Select Logical Port is Default.

10. Choose Configuration Type WSDL-Based Configuration.

11. Choose WSDL Base via File.

12. Browse for WSDL file downloaded from SAP Solution Manager, and choose ApplySettings.

Figure: Creation of Logical Port


22

Figure: Applying WSDL Document Settings

13. On the Consumer Security tab, enter the Web Service user (e.g. RFCWEBUSER) andpassword to logon to SAP Solution Manager

Figure: Entering User Name and Password For Web Service

14. Check WebService via button Ping Web Service in Configuration tab.

15. ONLY in case of structural changes within WebService:Delete Logical Port and recreate it, as described above (using new WSDL Base).

SAP Best Practices Solution Builder System /n/SMB/BBI

Assign Logical Port (for each authoring or consumption client)

1. Choose Solution SAP Solution Manager Integration General Setup Logical Port.

2. Enter the logical port name created in the preceding step, using input selection help.


23

Figure: Logical Port Assignment

Figure: Entering the Logical Port Name Created in the Preceding Step

Assign RFC Destination (for each authoring client)

1. Choose Solution SAP Solution Manager Integration General Setup RFCDestination.

2. Enter the RFC connection to SAP Solution Manager, created previously, using inputselection help.

Figure: RFC Destination Assignment


24

Figure: Entering the RFC Connection to SAP Solution Manager Created Previously

Check Connection to SAP Solution Manager

1. To check the setup of the logical port and RFC destination, choose

a. Solution Solution Manager Integration General Setup Check LogicalPort and

b. Solution Solution Manager Integration General Setup Check RFCDestination

2. The result of the check is displayed in the status bar.

Figure: Checking Connection to SAP Solution Manager


25

SAP Best Practices Solution Builder System /n/SMB/PROXY_MAIN[consumption only]

Proxy Maintenance for Offering Server

1. This step is necessary to enable the system to reach the Offering Server for download(SAP Best Practices Solution Builder solution files and installation data).

2. Call transaction /n/smb/proxy_main.

3. Specify Host Address PROXY.WDF.SAP.CORP

4. Specify Host Port 8080.

5. Choose Execute.

See SAP note 1584363 for more details.

Figure: Proxy Maintenance for Offering Server

Technical Configuration of SAP Solution Manager and SAP Best Practices Solution Builder Integration:PrerequisitesCopyrightIcons in Body TextTypographic Conventions

Prerequisites for the Technical Configuration of SAP Solution Manager and SAP Best Practices Solution Builder IntegrationIntroductionGeneral PrerequisitesSAP Best Practices Solution Builder toolSAP Solution Manager tool and contentSAP Solution Manager system landscape (SMSY)

Use case-dependent prerequisitesSAP Solution Manager/SAP Best Practices Solution Builder SU01Create User (IT Admin User) to Configure Web Service Connectivity

SAP Solution Manager SU01Create User to connect SAP Solution Manager and SAP Best Practices Solution Builder for Web Service and RFC Destination

SAP Best Practices Solution Builder System SM59 [authoring only]Maintain RFC Connection to SAP Solution Manager (for each authoring system)

SAP Solution Manager System PFCG [authoring only]Maintain Authorization (PFCG) Role for Connectivity User (for each authoring client)

SAP Solution Manager System/SAP Best Practices Solution Builder System SICFWeb Service Connectivity (client-independent)

SAP Solution Manager System SOAMANAGERWeb Service Connectivity (client-dependent)

SAP Best Practices SAP Best Practices Solution Builder System SICFWeb Service Connectivity - Check proxy settings

SAP Best Practices Solution Builder System SE80Web Service Connectivity Regeneration of client proxy definition

SAP Best Practices Solution Builder System SOAMANAGERWeb Service Connectivity/Create Logical Port (for each authoring or consumption client

SAP Best Practices Solution Builder System /n/SMB/BBIAssign Logical Port (for each authoring or consumption client)Assign RFC Destination (for each authoring client)Check Connection to SAP Solution Manager

SAP Best Practices Solution Builder System /n/SMB/PROXY_MAIN [consumption only]Proxy Maintenance for Offering Server

Documents

How to Set Up Connection Between Solution Manager and Solution Builder