SolMan 7.1 - Setup Guide

DMZVM040 Dagwin Stox +32 – (0)2 – 6903746 [email protected] March 20th 2012

Your business technologists. Powering progress

© For Internal Use

FOR INTERNAL USE

DMZVM040 - SAPCC SOLUTION MANAGER 7.1

AUTHOR(S)

NUMBER OF PAGES

: : : : : : :

OWNER

: Dagwin Stox

DOCUMENT NUMBER VERSION STATUS SOURCE DOCUMENT DATE

Dagwin stox sapCC-1WOW-0001 1 Draft Atos 20 March 2012 163

© Copyright 2012, Atos Belgium S.A./N.V. All rights reserved. Reproduction in whole or in part is prohibited without the prior written consent of the copyright owner. For any questions or remarks on this document, please contact Atos, +32-(0)2-6903746.

DMZVM040 - sapCC Solution Manager 7.1 For internal use

version: 1

document number: sapCC-1WOW-0001

Contents 1

About .............................................................................................................................................7

1.1 1.2 1.3

Scope / Purpose .......................................................................................................................7 Document Control ...................................................................................................................7 Contact Information ...............................................................................................................7

2

Preparation .................................................................................................................................8

2.1 2.2 2.3 2.4 2.5

Server details.............................................................................................................................8 Server Preparation ..................................................................................................................8 Documentation ...................................................................................................................... 10 Software .................................................................................................................................... 10 Prerequisite checks ............................................................................................................. 10

3

Installation............................................................................................................................... 12

3.1 3.2 3.3

JAVA Runtime ......................................................................................................................... 12 MS SQL Server 2008 R2 ..................................................................................................... 13 Solution Manager ................................................................................................................. 17

4

Post-Installation Steps SAP .............................................................................................. 24

4.1 Logging on to the application server ......................................................................... 24 4.2 Configuring User Management ..................................................................................... 27 4.3 Installing the SAP License ................................................................................................ 27 4.4 Configuring Remote Connection to SAP Support ................................................. 33 4.5 Configure the OSS Connection ...................................................................................... 36 4.6 Installing Online Documentation ................................................................................. 38 4.7 Post-Installation Steps ABAP .......................................................................................... 39 4.7.1 Consistency Check .............................................................................................................. 39 4.7.2 Maintain Company Address ............................................................................................ 39 4.7.3 Configure TMS ....................................................................................................................... 40 4.7.4 Import profiles ...................................................................................................................... 41 4.7.5 Setup Operation Modes ..................................................................................................... 41 4.7.6 Logon Groups......................................................................................................................... 43 4.7.7 Schedule Background Jobs .............................................................................................. 43 4.7.8 Install a printer...................................................................................................................... 43 4.7.9 Central Logging .................................................................................................................... 44 4.7.10 Configure Kernel Parameters ......................................................................................... 44 4.7.11 Installing Languages .......................................................................................................... 45 4.7.12 SAP ITS ....................................................................................................................................... 46 4.7.13 Configure SSL ......................................................................................................................... 47 4.7.14 FQDN .......................................................................................................................................... 47 4.8 Post-Installation Steps JAVA ........................................................................................... 47 4.8.1 Creating an Additional Administrator User ............................................................ 47 4.8.2 JAVA VM Memory Settings............................................................................................... 48 4.9 Apply Latest Kernel and Support Package Stack .................................................. 51 4.10 Network Level Security ...................................................................................................... 60 4.11 Remove Installation Directory ....................................................................................... 60 4.12 Perform a Full Backup ........................................................................................................ 60

Atos

20 March 2012

3 of 163

DMZVM040 - sapCC Solution Manager 7.1 version: 1

For internal use


4.13 4.14 4.15 4.16

Configuring the Connection to the SLD .................................................................... 61 Post-Installation for the Host Agent ........................................................................... 63 Additional Post-Installation Steps................................................................................ 63 Configuring Solution Manager ...................................................................................... 64

5

Post-Installation Steps sapCC ........................................................................................ 65

5.1 5.2 5.3 5.4 5.5 5.5.1 5.5.2 5.5.3

Enable McAfee Virus Scan ................................................................................................ 65 Remove the Installation Directory ............................................................................... 65 Remove the Installation User ......................................................................................... 65 Enable Single Sign-On for the sapCC Portal ............................................................ 66 SQL Server Post-Install....................................................................................................... 68 Make sccadm DB Owner ................................................................................................... 68 Set the Recovery Mode to Simple and Set Log File Size .................................... 69 Move the TEMPDB ................................................................................................................ 70

6

Pre-Requisites Check .......................................................................................................... 72

6.1 6.2 6.3 6.4 6.5 6.6

SAPOSS Connections ........................................................................................................... 72 S-User for Solution Manager ........................................................................................... 72 Check Support Package Levels ...................................................................................... 72 Client Copy .............................................................................................................................. 73 BW Client................................................................................................................................... 74 Client Settings........................................................................................................................ 74

7

System Preparation Wizard ............................................................................................. 75

7.1 7.2 7.3 7.3.1 7.3.2 7.3.3 7.4 7.5 7.5.1 7.5.2 7.5.3 7.6 7.6.1 7.6.2 7.6.3 7.6.4 7.7

Step 1 – Create Users ......................................................................................................... 78 Step 2 – Check Installation .............................................................................................. 79 Step 3 – Implement SAP Note ......................................................................................... 81 Step 3.1 - Download ............................................................................................................ 81 Step 3.2 - Import ................................................................................................................... 82 Step 3.3 – Post-Process ...................................................................................................... 82 Step 4 – Configure ABAP ................................................................................................... 83 Web Service Configuration .............................................................................................. 83 Step 5.1 – Configure Web Dispatcher ......................................................................... 83 Step 5.2 – Configure Authentication Types ............................................................. 84 Step 5.3 Logical Ports Configuration .......................................................................... 85 Step 6 – Prepare Landscape ............................................................................................ 85 Step 6.1 – Select SLD ........................................................................................................... 86 Step 6.2 – Prepare Outside Discovery ........................................................................ 87 Step 6.3 – Connect Diagnostics Agents..................................................................... 89 Step 4 – Set Up LMDB.......................................................................................................... 89 Step 7 – Complete ................................................................................................................ 93

8

Basic Configuration ............................................................................................................. 95

8.1 8.2 8.2.1 8.2.2 8.2.3

Step 1 – Specify Solution................................................................................................... 95 Specify User and Connectivity Data ............................................................................ 95 Step 2.1 – Specify Connectivity Data .......................................................................... 95 Step 2.2 – Specify SAP BW System ................................................................................ 96 Step 2.3 – Setup Credentials ........................................................................................... 96

Atos

20 March 2012

4 of 163


version: 1


8.2.4 8.2.5 8.3 8.3.1 8.3.2 8.3.3 8.4 8.5 8.6 8.7

Step Step Step Step Step Step Step Step Step Step

2.4 – Create Users ...................................................................................................... 96 2.5 – Solution Manager Internal Connectivity.............................................. 97 3 – Specify Landscape Data .................................................................................. 97 3.1 – Configure CA Wily Introscope .................................................................. 97 3.2 – Configure SAProuter ..................................................................................... 99 3.3 – Configure SAPconnect .................................................................................. 99 4 – Configure Manually ........................................................................................ 100 5 – Configure Automatically .............................................................................. 105 6 – BI Manual configuration............................................................................... 105 7 – Complete ............................................................................................................. 106

9

Diagnostics Agent and Host Agent .......................................................................... 107

9.1 9.2 9.3

Re-Install Diagnostics Agent ....................................................................................... 107 Removing Obsolete Agents from the SLD ............................................................ 115 Upgrading the Host Agent ............................................................................................ 116

10

Wily Introscope ................................................................................................................... 117

10.1 10.2 10.3

Installing Wily Introscope ............................................................................................. 117 Installing Wily Introscope Agents ............................................................................. 120 Wily Introscope Information ........................................................................................ 121

11

Managed Systems Configuration .............................................................................. 127

12

Incident Management...................................................................................................... 128

12.1 Prerequisites........................................................................................................................ 130 12.1.1 Solution Manager 7.1 SP03 Installed ....................................................................... 131 12.1.2 Central Note Implemented ........................................................................................... 131 12.1.3 RFC connection SAPOSS Working .............................................................................. 132 12.1.4 Verify Connections SAP-OSS and SAP-OSS-LIST-O01 ........................................ 132 12.1.5 S-User Authorizations ..................................................................................................... 133 12.1.6 Piece List Activation......................................................................................................... 133 12.1.7 Activation of Services ..................................................................................................... 134 12.1.8 Schedule Background Jobs ........................................................................................... 134 12.1.9 Managed System Configuration ................................................................................. 137 12.1.10 Check Table for Customer Data .......................................................................... 137 12.2 IT Service Management Wizard .................................................................................. 138 12.2.1 Step 1 – Check Prerequisites ....................................................................................... 138 12.2.2 Step 2 – Copy Transaction Types .............................................................................. 138 12.2.3 Step 3 – Automatic Configuration ............................................................................. 150 12.2.4 Step 4 – Manual Configuration ................................................................................... 151 12.2.5 Step 5 – Additional Configuration ............................................................................ 160 13

Logbook ................................................................................................................................. 163

13.1

18/05/12 – Download latest version of all already implemented notes ........................................................................................................................................ 163

Atos

20 March 2012

5 of 163


version: 1


List of changes Version

Date

Description

Author(s)

1

08 - 02 – 2012

Initial Draft

Dagwin stox

2

Atos

20 March 2012

6 of 163


1 1.1

For internal use


About Scope / Purpose ▶ The purpose of this document is to describe the installation and configuration of the Solution Manager 7.1 demo system DMZVM030. This demo system will serve to demonstrate the usage of Solution Manager within Atos and to perform customer demo’s. The purpose of this initiative is also to create a working document that can be used throughout Atos for setting up a Solution Manager 7.1 system.

1.2

Document Control ▶ Please submit your contributions, insights and lessons learnt to the sap Competence Center. See contact information in section 1.3.

1.3

Contact Information ▶ Contact Persons at the sap Competence Center

•

•

Atos

Dagwin Stox Team leader sapCC Brussels Tel: +32 – (0)2 – 690 3746 Mail: [email protected] Shishir Dongaonkar Senior consultant sapCC India Tel: ? Mail: [email protected]

20 March 2012

7 of 163


2 2.1

For internal use


Preparation Server details A virtual machine has been deployed at the sapCC for the installation of this system. System specs: ▶ Physical host: Dell M610, 2 quad core Intel Xeon CPU’s, 24GB RAM, Windows 2008 R2 Enterprise ▶ Virtual Machine: 4 CPU cores, 7GB RAM, 1 NIC:

▶ Disk space: C:-drive: OS + Paging – 61 GB E:-drive: usr/sap – 38 GB F:-drive: SAP data files – 95 GB G:-drive: TEMPDB – 38 GB ▶ Paging file: 24GB ▶ System name: dmzvm040 System FQDN: dmzvm040.atosorigin-ica.com ▶ Member of domain: ATOSORIGIN-ICA ▶ IP-address: 212.190.195.176

2.2

Server Preparation Prepare the server for the installation of Solution Manager.

Atos

20 March 2012

8 of 163


For internal use


▶ Windows Firewall disabled on domain level:

▶ Power Plan: change to High Performance:

▶ Create a new local user account “sapinstall” and make it member of the local “Administrators” group -> this account will be used for the installation.

Atos

20 March 2012

9 of 163


For internal use


▶ Disable and stop the Virus Scan services via services.msc (for the duration of the installation):

2.3

Documentation Go to https://service.sap.com/instguides to download the Solution manager 7.1: ▶ Master Guide ▶ Installation Guide ▶ Media List ▶ Configuration Guide ▶ Wily Introscope 9 Installation Guide Read the Master Guide and the notes mentioned in the Master Guide. Go through the Installation Guide and read the notes mentioned in this guide.

2.4

Software Download the installation DVDs from https://service.sap.com/swdc: ▶ Installation Master DVD ▶ SAP Kernel DVD ▶ JAVA DVD ▶ Installation Export DVD ▶ MS SQL SERVER 2008 R2 RDBMS DVD ▶ SAP SOLUTION MANAGER 7.1 SPS 04 Download the latest J2SE and JCE policy files from https://java-partner.sun.com/support using these credentials: User: [email protected] Password: DZwqphsV Copy the installation DVDs and additional files needed for the installation to a local drive on the server.

2.5

Prerequisite checks Check that the system meets the hardware requirements (as specified in the Installation guide): ▶ Disk space: OK ▶ Min. 6GB RAM: OK ▶ Min. paging file (calculated according to note 1518419) = 21.3 GB: OK ▶ Operating System: OK (Windows 2008 R2 Enterprise) ▶ Database Software: OK (SQL Server 2008 R2) ▶ Windows firewall disabled: OK ▶ Filesystem is NTFS: OK ▶ Power plan set to “High Performance”: OK ▶ Local user account “sapinstall” and make it member of the local “Administrators”: OK

Atos

20 March 2012

10 of 163


Atos

For internal use

20 March 2012


11 of 163


3

For internal use


Installation IMPORTANT: During the installation, always log on with the local account you created! In this case, the account is DMZVM040\sapinstall. This account can be deleted when the installation has finished.

3.1

JAVA Runtime The current recommended version of the JSDK is 1.4.2.35. To install, double click on the file j2sdkfb-1_4_2_35-windows-amd64.exe. When prompted by UAC (user Account Control), click Yes:

REMARK: On Windows systems, you might see this error:

Click on OK, and retry the installation. Go through the installation wizard:

Atos

20 March 2012

12 of 163


3.2

For internal use


MS SQL Server 2008 R2 We will be installing MS SQL Server 2008 R2 Enterprise with the installation script SQL4SAP.vbs supplied in the root of the RDBMS installation media. Relevant documentation: ▶ SQL4SAP_Docu.pdf (in the root of the installation media) ▶ Latest version of sql2008r2_upgrad.pdf (v1.20) from the marketplace ▶ SAP Note 1152240 - Up Microsoft SQL Server 2008 (R2) Double click on the file SQL4SAP.vbs to start the installation. When prompted by User Account Control, click Yes:

Atos

20 March 2012

13 of 163


For internal use


Create a default instance (SAP recommendations) and click OK:

Click on OK to start the installation:

The installation starts. REMARK: DO NOT close the CMD window:

Atos

20 March 2012

14 of 163


For internal use


Click on OK to finish the installation:

Now go to Start -> All programs and start the SQL Server Management Studio:

Connect to the database engine:

If you see this error close all windows:

Atos

20 March 2012

15 of 163


For internal use


Re-launch the SQL Server Management Studio as administrator. Right click on the entry in the programs list and choose “Run as Administrator”. Click Yes on the UAC prompt. Now connect to the database engine. Right “SQL Server Agent” and choose “Properties:

Set the History settings as recommended in the installation guide:

Close the SQL Server Management Studio.

Atos

20 March 2012

16 of 163


For internal use


Run Windows Update and install any available updates for MS SQL Server and MS Visual Studio. Restart the server if required. This concludes the installation of MS SQL Server. Follow-up actions after the installation of Solution Manager: ▶ Move the temporary database and datafiles, see SAP Note 363018 ▶ Verify the version of the JDBC driver as described in SAP Note 1152204 and 639702

3.3

Solution Manager We are ready to start the installation of Solution Manager with SAPinst. Locate the x64 version of SAPinst in the subdirectory IM_WINDOWS_X86_64 fo the installation master DVD. Double click on sapinst.exe to start the installation. Click on Yes when prompted by the UAC. The SAPinst GUI starts. On the first screen, we select the option to install a central instance of Solution Manager 7.1:

Click on Next to continue.

Atos

20 March 2012

17 of 163


For internal use


We will perform a Typical installation:

Click on Next. You get a prompt that SAPinst needs to log you off to set permissions for the installation account:

Click on OK. You are logged off. Log on again, SAPinst will resume after you click on Yes when prompted by the UAC. Set the location of the JAVA DVD and click on Next:

Set the location for the JCE policy files and click on Next:

Atos

20 March 2012

18 of 163


For internal use


Set the SID, choose the installation drive (for the usr/sap/ folder) and click on Next:

Specify the Master Password and click on Next:

You will get a warning from the pre-requisites check that the English language pack is not installed. Since the OS is English, we will click on Cancel to continue anyway with the installation:

Atos

20 March 2012

19 of 163


For internal use


Select the location of the Kernel DVD and click on Next:

Select the location of the folder EXP1 on the Installation Export DVD and click on Next:

Do the same for the EXP4 folder and click Next:

Select the number of data files and click on Next:

Atos

20 March 2012

20 of 163


For internal use


Enter the location of the JAVA DVD and click on Next:

Enter the location of the Kernel DVD and click on Next:

REMARK: I got this error message:

After some searching, I found that the DVD SAPinst was asking for appeared to be the SL Controller DVD, which carried the same DVD number as the Kernel DVD. I selected the SL Controller DVD and SAPinst continued. Provide the path the the SAP crypto lib (do not unpack!) and click Next:

Atos

20 March 2012

21 of 163


For internal use


Choose to register the system in an existing SLD and click on Next:

Enter the SLD host and supply the password for the JAVA and ABAP SLD user:

REMARK: For the registration of the JAVA Engine, you have to supply the userID and password of the central SLD user! The SLD ABAP API User is a user on your Solution Manager System, we specified the same password (Master password) as for all other users. Change the SID to “DCC” (Diagnostics connected to sapCC SolMan) for the Diagnostics Agent and click on Next:

Atos

20 March 2012

22 of 163


For internal use


Review the information on the parameter summary screen and click on Next:

REMARK: If you want to change an entry, mark the checkbox and click on Next. The installation starts now:

When the installation is complete, you should see a message that the installation was successful. Click on OK:

SAPinst will close now.

Atos

20 March 2012

23 of 163


4

For internal use


Post-Installation Steps SAP This chapter will cover the post-installation steps as mentioned in the Solution Manager Installation Guide. The next chapter will cover the post-installation steps specifically related to the sapCC.

4.1

Logging on to the application server Make sure you have installed the SAPGUI on your workstation. Create a new entry for the Solution Manager system:

Launch the connection and check if you can logon with user sap* and the master password you specified during the installation:

Acknowledge the message about the license expiration:

Atos

20 March 2012

24 of 163


For internal use


If you are logged on successfully, you see the initial SAPGUI screen:

Atos

20 March 2012

25 of 163


For internal use


Now check if you can logon to the JAVA instance. Go to http://dmzvm040.atosorigin-ica.com:50000. Check that you see the start screen of the JAVA instance:

Click on “System Information” and check that you can logon with the default administrator account “J2EE_Admin” and the master password you supplied during installation:

Atos

20 March 2012

26 of 163


For internal use


If logon is successful, you will see the System Information:

And finally, start a Remote Desktop connection and make sure you can logon with the local account ADM created during installation: User: sccadm Password: the master password you supplied during installation.

4.2

Configuring User Management We will keep the default, which is that the UME (User Management Engine) uses the ABAP instance as the data source.

4.3

Installing the SAP License To request a license, go to http://service.sap.com/licensekey. Click on “Search an installation”:

Atos

20 March 2012

27 of 163


For internal use


Enter the installation number to which you want to add the system:

REMARK: All SAP Test & Demo licenses fall under the T&D license contract between SAP and Atos, which is managed by the sapCC. To request new licenses (installation numbers), you can send a mail to [email protected]. Keep in mind that it is company policy to have all SAP demo systems hosted by the sapCC! Click on “New System”:

Enter the SID that you want to use for the system and click on “Continue”. There is a background check that verifies that this SID is not in use yet for this installation number:

Atos

20 March 2012

28 of 163


For internal use


Enter the rest of the system details and click on “Continue”:

Use the SAPGUI to log on to your newly installed system and execute transaction SLICENSE. Not e the hardware key:

Atos

20 March 2012

29 of 163


For internal use


Return to the marketplace and supply the hardware key. Click on Save to save the entry. You will see a second entry for the maintenance certificate. Click on Continue:

Supply your e-mail address and click on “Submit”:

When prompted if you are sure to submit, click on Yes. After about 30 minutes, you will get an e-mail with the license file attached, in this case it’s called SMD_multiple.txt. Save the file locally. Return to the SAPGUI to transaction SLICENSE. Click on “New Licenses”:

Click on the “Install” button and provide the location of the license file you save locally:

You should get a message now that 2 licenses were installed successfully. Confirm the message.

Atos

20 March 2012

30 of 163


For internal use


Check that the installation number, the hardware keys and the license dates are correct:

To install the JAVA license, open a Remote Desktop connection to the system. Logon with the account sccadm and open the Visual Admin tool: go to E:\usr\sap\SMD\DVEBMGS00\j2ee\admin and double click on go.bat. Choose the Default connection and click on Connect:

Supply the password for J2EE_ADMIN and click on “Connect”:

Atos

20 March 2012

31 of 163


For internal use


Browse to server 0 -> services -> Licensing adapter. Click on “Install license from file” and browse to the location of the license file:

If you receive any warnings or messages, click on OK until you are back on the license screen. Make sure the license for the JAVA instance is valid:

Atos

20 March 2012

32 of 163


For internal use


Close the Visual Admin tool.

4.4

Configuring Remote Connection to SAP Support For more information, see http://service.sap.com/remoteconnection. Go to http://service.sap.com/system-data and do a search on the SID of our system:SCC. Select the correct sytem from the list (SolMan 7.1 Atos Demo Sytem) and click on the link SCC. The System Details page opens. Click on the link “Edit System”:

In the section “SAP Router”, select your SAP Router from the list and fill in the service port:

Now switch to the tab “DB Server” and fill in the system details (screenshot is for different system !!!):

Atos

20 March 2012

33 of 163


For internal use


On the bottom of the page, click on “Save System”:

Click on OK for the pop-up message that warns you that the system details will be replaced by the new details you entered. Now go back to the “System” tab and click on “Maintain Service Connection” in the SAP Router section:

The window to maintain the service connection opens. Click on the link “Download Service Connector”:

A new page opens. Read the information about the service connector and click on the “Install” button:

Run the installer and go through the wizard to install the service connector. Go back to the page to maintain service connections and click on the link “R/3 Support”:

A new window opens, click on the “Save” button:

Do the same for “Windows Terminal Server”:

Atos

20 March 2012

34 of 163


For internal use


“R/3 Support” and “Windows Terminal Server” now appear in the section “Open/Close Connection”. Click on “R/3 Support” again:

In the window that opens, specify how long this connection should remain open and click on “Open Connection”:

You can see that the “R/3 Support” connection is defined now. Adjust the SAP Routestring and click on “Connect”:

Atos

20 March 2012

35 of 163


For internal use


You will get a prompt for a file stfk.oez. This file is used by the service connector you just installed to open the service connction. Choose to open the file:

You will get a message that the service connector was started, click OK:

And now you should receive a message that the service connection was opened successfully:

Click on OK. If you click on the “Refresh” button now, the connection status should be “Connected” and the remaining time for the connection should be indicated:

4.5

Configure the OSS Connection Logon to client 000 as sap* and call transaction OSS1. From the menu, choose Parameters -> Technical Settings:

Click on the “Change” button and provide the details for the OSS connection:

Atos

20 March 2012

36 of 163


For internal use


Click on the “Save” button. Call transaction SM59. Select ABAP connection “SAPOSS” and click on “Change”:

Go to the tab “Logon and security” and set the password to CPIC:

Make sure the logon group is set to “EWA”:

Atos

20 March 2012

37 of 163


For internal use


Click on “Save”. Click on the button “Connection Test” and verify that the connection was successful:

From the menu, choose Utilities -> Test -> Authorization test and check that it is successful:

You can find detailed information about the RFC connection SAPOSS in SAP Note 812386. Please refer to SAP Note 33135 for more information about the usage of the transaction OSS1.

4.6

Installing Online Documentation Instead of installing the online documentation, we always configure SAP Help to use the SAP online documentation at the sapCC. Call transaction SR13. You will get a warning that the table is cross-client, click OK to continue:

Select the tab “PlainHtmlHttp” and click on the button “New Entries”:

Atos

20 March 2012

38 of 163


For internal use


Enter the information as shown here:

Click on Save. When prompted to select a request, create a new request with short description “SAP Help Configuration”. Save the request. Test your settings by selecting Help -> Application Help from the SAPGUI menu:

This should direct you to the SAP Help site with Solution Manager 7.1 as the starting point.

4.7

Post-Installation Steps ABAP Logon to the ABAP instance client 001 (default production client) with user sap* and the master password you supplied during installation. REMARK: Since all transactions are run for the first time, there will be a lot of compiling.

4.7.1

Consistency Check First, call transaction SICK to perform a consistency check. Make sure the check returns no errors:

4.7.2

Maintain Company Address Now call transaction SU01. From the menu, choose Environement -> Maintain company address. Specify a company name (Atos) and click on the button Create:

Maintain the company address details:

Atos

20 March 2012

39 of 163


For internal use


Now set this as the standard address:

Click on Save. Repeat this for client 000.

4.7.3

Configure TMS REMARK: From here on, we log on to client 000 as user sap*. Call transaction SE06 and click on “Perform Post-Installation Actions”:

Atos

20 March 2012

40 of 163


version: 1


Click “Yes” on the confirmation prompt:

Call transaction STMS. A popup window appears, click on the “Save” button to save the proposed configuration:

4.7.4

Import profiles Call transaction RZ10. From the menu, choose Utilities -> Import profiles -> Of active servers:

And click on the “Back” button:

4.7.5

.

Setup Operation Modes Call transaction RZ04. Click on the button “Create”:

Atos

20 March 2012

41 of 163


For internal use


Define an operation mode Normal and click on the “Save” button:

Now click on “Instances/operation modes”:

Click on the “Create” button. Maintain the instance data and click on “Save”:

Atos

20 March 2012

42 of 163


For internal use


If you get a profile check log, click on continue. Select the operation mode Normal you created and click on “Save” to save the work process distribution:

When asked to assign work process distribution to other operation modes, click No. Back in the CCMS screen, click on the “Save” button.

4.7.6

Logon Groups Since we have only one instance, we will not setup logo groups (now).

4.7.7

Schedule Background Jobs Call transaction SM36. Click on the button “Standard Jobs”:

Now click on “Default Scheduling”:

You should see a message at the bottom that all default jobs have been successfully scheduled:

4.7.8

Install a printer We will define a printer for front-end printing. Call transaction SPAD. From the menu, choose Configuration -> Output devices:

Atos

20 March 2012

43 of 163


For internal use


Click on the “Change” button and then the “Create” button. Specify the output devices and device settings:

Set the Access Method:

And click on “Save”.

4.7.9

Central Logging We will not configure central logging.

4.7.10

Configure Kernel Parameters More information can be found in SAP Note 146289 and the notes mentioned in this note. We only need to change parameter ztta/roll_area on the instance profile. Call transaction RZ10. Choose the instance profile and open it in extended maintenance mode. Add parameter ztta/roll_area with a value of 6500000:

Atos

20 March 2012

44 of 163


For internal use


Save and activate the profile. The change will become active after a restart of the ABAP instance. We will also add some background processes. Open the instance profile again in Basic Maintenance mode and increase the number of work processes to 6:

Save and activate the profile, restart the instance for the changes to take effect.

4.7.11

Installing Languages Call transaction I18N and go to I18N Customizing -> I18N System Configuration:

Atos

20 March 2012

45 of 163


For internal use


Add English (EN) and German (DE), click on Activate:

Click on “Yes” when prompted to confirm the NLS activation.

4.7.12

SAP ITS The Internet Transaction Server (ITS) is integrated now in NetWeaver. The ITS is mainly used for SAPGUI for HTML. Since the SAPGUI for HTML is used by the wizards for the initial system preparation and configuration, we will enable it. Call transaction SICF. Go to the service /sap/bc/gui/sap/its/webgui, right click the service and activate it:

Click on the second “Yes” button to activate all higher services too:

Do the same for ▶ sap/public/bc/its/mimes ▶ sap/bc/bsp/sap/system ▶ sap/bc/echo ▶ sap/public/bc/ur Call transaction SE80 and open the internet service WEBGUI. Right click on the service and publish it:

Atos

20 March 2012

46 of 163


For internal use


You should see a message at the bottom that the service was published successfully to site INTERNAL:

Verify that the SAPGUI for HTML works by browsing to: http://dmzvm040.atosorigin-ica.com:8000/sap/bc/gui/sap/its/webgui

4.7.13

Configure SSL In order to use SSL, the SAP Cryptographic Library must be installed and a Server Certificate must be requested. At this time, we will not configure SSL.

4.7.14

FQDN Open transaction RZ11 and display parameter icm/host_name_full. Verify that the FQDN name is correct:

4.8 4.8.1

Post-Installation Steps JAVA Creating an Additional Administrator User The JAVA UME is configured after installation to use ABAP client 001 as source. Log on to client 001 with user sap* and copy user sap* to a new user (in my case, I created BE03155D). Set an initial password, the name and assign role SAP_J2EE_Admin. Save the user and log off. Log on with the new user and specify a new password when prompted. Log off.

Atos

20 March 2012

47 of 163


For internal use


Now go to http://dmzvm040.atosorigin-ica.com:50000/useradmin and verify that you can logon with the new user. Check that it is an administrator user:

4.8.2

JAVA VM Memory Settings SAP Note 723909 is the basis for setting the recommended JAVA parameters. SAP Note 739788 mentions the template config tool for setting JAVA parameters for new installed systems. To open the tool, open a Remote Desktop to your server and navigate to E:\usr\sap\SCC\SYS\global\TemplateConfig and execute cfgtemplategui.bat. For more information about the usage, see http://help.sap.com/saphelp_dimp50/helpdata/DE/29/932929681c463cb1cb3d4faf1df049/content. htm This will start the template wizard:

Click Next.

Atos

20 March 2012

48 of 163


For internal use


Select “Apply” and click Next:

Select template “J2EE-engine-only.zip”, set the profile directory of the JAVA instance and click Next:

: The system dependencies are detected automatically, click Next:

Atos

20 March 2012

49 of 163


For internal use


Review the hardware dependencies, set the usage factor to 0.4 and click Next:

Select the Backup option and click Next:

Atos

20 March 2012

50 of 163


For internal use


You can preview the settings here, click Next to continue:

Click on Finish to apply the template:

Review the output log and click on OK to close the wizard. Use the config tool to verify that all settings have been applied as described in SAP Note 723909.

4.9

Apply Latest Kernel and Support Package Stack The procedure to upgrade the kernel and to apply the latest SPS stack is described in SAP Note 1577909. We already downloaded the SPS4 DVD. Copy the JAVA files and XML files from the DVD to the transport directory. Unpack all ABAP files from the DVD (*.SAR) into the transport directory. To download the kernel, go to https://service.sap.com/swdc and browse to Support Packages and Patches -> Browse our Download Catalog -> SAP Technology Components -> SAP Solution Manager -> SAP Solution Manager 7.1 -> Link to SP Stack Application. In the SP Stack Application, select the initial release and SPS4, than click on “Next Step”:

Atos

20 March 2012

51 of 163


For internal use


Select only the relevant kernel and IGS components and click on “Next Step”. On the next page, deselect all components except the kernel and IGS files. Add those to your download basket and download the files. Copy the files to the transport directory: E:\usr\sap\trans\EPS\in, DO NOT extract them. Logon to client 000 with user sap*. Create a copy of user sap*, set an initial password and the name/address. Log off. Logon with the new user (in my case BE03155D) and set the final password. Call transaction SPAM. Load packages from the application server:

Calculate the queue. REMARK: I got an error message saying that at least SPAM/SAINT version 43 was required for one of the support packages. The download of SPAM support packages must be approved via maintenance optimizer, so you can’t download it from the marketplace like we did with the kernel files. As a workaround, I used MOPZ on another Solution Manager system to confirm the download of the latest SPAM version (version 45). After that, I downloaded the file and updated SPAM/SAINT. REMARK: It was wrong to try and use SPAM, you have to use SAINT for the upgrade. In SAINT, you can specify an XML file for the upgrade. Now, call transaction SAINT and point to the maintenance XML file on the SPS4 DVD (you might have to copy this to your workstation):

Atos

20 March 2012

52 of 163


For internal use


Check that the calculation of the queue was successful and click on Continue:

Check that the extended queue has been calculated successfully and click on Continue:

Atos

20 March 2012

53 of 163


For internal use


When prompted to add Modification Adjustment Transports to the queue, click No. You get a pop-up window with a number of notes to review. At least one of these notes contains a password, which you have to supply here. Click on OK to continue:

This is a large queue, therefore change the startup option of all phases to “background”. Click OK to continue:

Atos

20 March 2012

54 of 163


For internal use


Use the “Refresh” button to update the status of the queue. You can also check the log files from this window:

If the installation stops during phase IMPORT_PROPER, just click on “Continue” to restart the process. At the end, you’ll get a message that the installation is finished, click on “Finish” to complete the installation:

Atos

20 March 2012

55 of 163


For internal use


The JAVA stack and kernel will be upgraded with JSDM. Open a remote desktop connection to the server and execute E:\usr\sap\SMD\DVEBMGS00\j2ee\JSPM\go.bat to start the JSPM. Enter the SDM password (=master password) and click on “Log On”:

With the option “Support and Enhancement Package Stack” selected, click on Next:

Atos

20 March 2012

56 of 163


For internal use


JSPM scans the inbox and reads the maintenance stack file. There are 2 options presented, choose the option SolMan 7.1 and NW EhP2 and choose Next (if you check the details, both options contain the same components to deploy):

JSPM now starts loading all the .SCA archives and validates all components. Click on “Start”:

After clicking start, the J2EE engine is re-started and deployment starts. JSPM will first update itself. After that, you need to exit JSPM:

Atos

20 March 2012

57 of 163


For internal use


Now restart JSPM. You will need to logon again. On the next screen, you see an overview of the components that have not been deployed yet, click “Next” to continue. You can follow the progress in the Status column. When all components have been deployed, click on Exit:

As a final step, we will update the kernel. Start JSPM again and logon. Choose “Single Support Packages” and click Next:

This time you see the Kernel and the IGS, click Next:

Atos

20 March 2012

58 of 163


For internal use


If you have other packes in the inbox, make sure you skip them, we will implement them after the kernel upgrade. Click on “Start” to begin deployment:

Since this is a kernel upgrade, the SAP instances will be stopped during deployment. After deployment, I got this message:

Atos

20 March 2012

59 of 163


For internal use


Use the SAP management console to start SCC. This will trigger the copy of the new executables to the kernel directory. When SDM has started, including the JAVA processes, you can click on “Resume” in JSPM. On the last screen, click “Exit” to exit JSPM:

Now both the ABAP and JAVA stack have been upgraded to SPS4 and the kernel has been updated to the latest version too.

4.10

Network Level Security SAP recommends that you implement network encryption before using a system in Production. We will not do this (for now).

4.11

Remove Installation Directory For security reasons, the installation directory should be stored in a save location and removed from the server. Move the directory C:\Program Files\sapinst_dir to another location.

4.12

Perform a Full Backup Before we continue, we will take a full offline backup of the system. At the sapCC, we use CommVault Simpana for backups. We installed the CommVault File System Agent and SQL Server Agent. Open a remote desktop connection to the server, log on as user sccadm (with the master password). Use the SAP mmc to stop SCC and the diagnostics instance DAA. Use the Services console services.msc to stop all SAP services and MS SQL Services:

Atos

20 March 2012

60 of 163


For internal use


Finally, log off the server. By bringing both SAP and SQL Server completely offline, we can take a full file system backup. When the backup is complete, restart the server and restart the SAP instances.

4.13

Configuring the Connection to the SLD We already made the connection to the SLD during installation, we will verify the settings now. Logon to client 000 and call transaction RZ70. Verify the SLD Bridge information. Activate the configuration. Then start the data collection and schedule the background jobs:

When prompted if you want to start the data collection ,click Yes:

Atos

20 March 2012

61 of 163


For internal use


Review the output. See also SAP Note 584564 for more information. REMARK: In this case the output showed that the RFC call wasn’t successful: Error when opening an RFC connection (CPIC-CALL: '). When doing a connection test for the TCP-IP connection SLD_UC in transaction SM59, we also got a connection error, saying that the gateway was not responding. To check the SLD gateway, we logged on to the SLD site as administrator and browsed to Administration -> Details -> Data Suppliers. Here’s what we saw:

So we went back to transaction RZ70, changed the gateway to sapgw01, activated the configuration and restarted the data collection and job scheduling. This time there were no errors.

To verify the SLD settings for the JAVA engine, open a remote desktop connection to the server and start the Visual Administrator. Go to Server 0 -> Services -> SLD Data Supplier:

Atos

20 March 2012

62 of 163


For internal use


Check that the configuration is valid, that the latest send result was a success and check when the last send activity appeared.

4.14

Post-Installation for the Host Agent Open a remote desktop connection to the server and check that you can logon with user sapadm and the master password. When logged on, check that the services SAPHostControl and SAPHostExec are running:

4.15

Additional Post-Installation Steps The next steps are not listed in the installation guide, but are mentioned in SAP Notes. SAP Note 1639266 describes two additional JAVA patches to deploy after implementing SPS4: ▶ Patch 5 (or higher) for SP 9 of SAP JAVA TECH SERVICES 7.02 ▶ Patch 6 (or higher) for LIFECYCLE MGMT TOOLS 7.02 SP 9 Download these patches from the Service Market Place and place them in the inbox: E:\usr\sap\trans\EPS\in In addition, from experience we know you should also deploy patches for JEE, JEE Core and IS Agent to avoid problems during Basic Configuration. Use JSPM to install these patches, choose the option “Single Support Packages”:

Atos

20 March 2012

63 of 163


For internal use


Also make sure you read SAP Note 1483508 “Solution Manager 7.1: Root Cause Analysis prerequisites”. This note describes the required patch levels for managed systems.

4.16

Configuring Solution Manager We have to perform an initial basic configuration of Solution Manager and scenario specific configuration for our newly installed SAP Solution Manager system. This is done with transaction SOLMAN_SETUP, for more information see the next chapters: ▶ Chapter 7: System Preparation ▶ Chapter 8: Basic Configuration

Atos

20 March 2012

64 of 163


5

For internal use


Post-Installation Steps sapCC In addition to the post-installation steps mentioned in the installation guide, we have a number postinstallation steps that are required within the sapCC.

5.1

Enable McAfee Virus Scan In the Services console, set the startup setting for the McAfee services back to “Automatic”:

The services will be restarted automatically the next time the server is restarted.

5.2

Remove the Installation Directory Open explorer and copy the installation directory to a safe location if you want to keep it: C:\Program Files\sapinst_instdir Delete the directory.

5.3

Remove the Installation User Logon to the system. Right click on “My Computer” and select Manage. Go to Configuration->Local Users and Groups->Users and delete the local account you created for the installation:

Acknowledge the warning to delete the account:

Acknowledge the second warning:

Atos

20 March 2012

65 of 163


For internal use


The account is now deleted. Close Server Manager. Right click again on “My Computer” and choose Properties. Select the Advanced tab and go into the settings for the user profile to delete the profile of the installation user:

Since we already removed the account, we see an entry “Account Unknown”. You can delete all profiles that are listed as “Account Unknown”. Open explorer and go to C:\Users. Make sure the folder for the installation account no longer exists. In our case, there should be no folder “sapinstall”.

5.4

Enable Single Sign-On for the sapCC Portal Call transaction STRUSTSSO2. Click on the “Import” button in the certificate section:

Atos

20 March 2012

66 of 163


For internal use


Browse to the SSO certificate of the portal and confirm the import:

Verify the Validity of the certificate and add it to the certificate list:

Add the certificate to the ACL:

Atos

20 March 2012

67 of 163


For internal use


You have to logon to each client for which you want to enable SSO from the portal and add the imported certificate to the ACL. For this system, this was done for client 001 only.

5.5 5.5.1

SQL Server Post-Install Make sccadm DB Owner Because we deleted the sapinstall user, no user has the role db_owner for the SAP database. This leaves the database with an empty field for the property db_owner. Logon to the server with the local administrator account adm, in our case sccadm. Open the SQL Server Management studio as Administrator:

Connect to SQL Server:

Atos

20 March 2012

68 of 163


For internal use


Right click on the database to start a T-SQL window (New Query), enter these commands and execute: USE SCC EXEC sp_changedbowner 'DMZVM040\sccadm'

5.5.2

Set the Recovery Mode to Simple and Set Log File Size To avoid running out of disk space because of a transaction that keeps growing, set the recovery model to Simple. In the SQL Management Studio, right click on the database and select “Properties”. Click on Options and set the Recovery Model to “Simple”:

Now you can set the size of the log file. Right click on the database and select “Task->Shrink files”. Select the log file and set the size for the log file to 10240 MB:

Atos

20 March 2012

69 of 163


5.5.3

For internal use


Move the TEMPDB The TempDB database is used constantly. To improve performance, we will move it to a separate disk. In SQL Management Studio, right click on the tempdb database and select “New Query”:

To determine the current file names, execute the query shown here:

Atos

20 March 2012

70 of 163


For internal use


We will use the G:-drive to store the new tempdb. Create a new folder on the G:-drive called TEMPDB. Now execute the query shown here:

Verify that you see in the lower part of the screen that the files have been modified in the system catalog. To make the change active SQL Server has to be restarted. Stop SAP using the management console, restart SQL Server and start SAP. Verify that the new files have been created in the new location and delete the old TEMPDB folder and it’s content on the F:-drive.

▶ SAP user security ▶ Move SQL log

Atos

20 March 2012

71 of 163


6

For internal use


Pre-Requisites Check First of all, we need to make sure the system meets the pre-requisites.

6.1

SAPOSS Connections If setup and tested as described in chapter 4.6, your connection is good.

6.2

S-User for Solution Manager Your Solution Manager needs an S-user to post information to and retrieve information from the SAP Service Marketplace. Best practice is to create a dedicated S-user for this linked to the customer number that the installation number is linked to. Make sure the S-user has at least these authorizations:

6.3

Check Support Package Levels Solution Manager should be at least at SP03, we have installed SP04. From the EGI slides:

Atos

20 March 2012

72 of 163


6.4

For internal use


Client Copy By default, Solution Manager is delivered with client 000 and client 001. We use client 001 as production client. From the EGI slides:

REMARK: After you created a new productive client you need to convert the Java user store to the new productive ABAP client. This is needed if you want to use Root Cause Analysis.

Atos

20 March 2012

73 of 163


For internal use


You can find a detailed description in the IMG (Implementation Guide - transaction SPRO) in the tree Technical Settings -> Client Copy -> Convert UME. Note that the Java engine will need to be restarted afterwards.

6.5

BW Client We used the recommended scenario of enabling BW in the SolMan production client. From the EGI slides:

6.6

Client Settings Some configuration steps make customizing changes in the productive client and the BW client. Therefore ensure the following client settings for the production client (in this case 001) in transaction SCC4 during the configuration activities:

Atos

20 March 2012

74 of 163


7

For internal use


System Preparation Wizard Run transaction SOLMAN_SETUP. If you start the transaction SOLMAN_SETUP for the first time, you will be asked to activate Web Dynpro Services to display the wizard in your browser screen:

A browser window will start. I got a pop-up asking to create a SolMan administrator user. Click on “Create or Update User”:

Provide a password and click on Execute:

Atos

20 March 2012

75 of 163


For internal use


REMARK: At the sapCC, we set the password for the SOLMAN_ADMIN user to the same value as the “master password” entered during the installation. Creation of the user can take a few minutes. Check in the log that all is green when finished and click on “Close”. In the previous box about creating the user, click on “Continue”:

REMARK: When using Internet Explorer 9, the pages is not showing correct (see screenshot). To rectify this, you have to enable Compatibility view. Press the ALT key, this will show the menu bar in IE. From the menu, choose Tools -> Compatibility View Settings:

Atos

20 March 2012

76 of 163


For internal use


Mark the checkbox to enable compatibility view for all sites and click on “Close”:

The page will reload and appear correctly now. You will get the message again about creating the SolMan Administrator user, click on Continue. Now click on “System Preparation” from the left menu to start the wizard:

Atos

20 March 2012

77 of 163


7.1

For internal use


Step 1 – Create Users The wizard has started. Click on the Edit button:

Click on the button “Create Users”. Note that the SOLMAN_ADMIN user already exists because we just created it:

For some of the users, you will be prompted to provide a password. Enter a password (e.g. the master password) and click on OK:

Verify that all users are created and have the correct roles:

IMPORTANT: Close the browser. Log off, then log on with user SOLMAN_ADMIN before proceeding to next step. From the EGI slides:

Atos

20 March 2012

78 of 163


7.2

For internal use


Step 2 – Check Installation Make sure you are logged on as SOLMAN_ADMIN and start transaction SOLMAN_SETUP. Click on System Preparation and click on “Edit”. All users should be in green in Step 1. Click on Next to proceed to Step 2, this steps checks if the system meets the pre-requisites.

Atos

20 March 2012

79 of 163


For internal use


IMPORTANT: The check only verifies the presence of parameters, NOT the values !!! FIRST create all parameters mentioned in the documentation for the step “Check profile parameters” with the values mentioned in the documentation. SECOND apply the parameter recommendations mentioned in SAP note 1582842! THIRD -> restart the system. Click on the Display link for the step “Check profile parameters”:

Go back to the SAPGUI and execute transaction RZ10. Open the instance profile in “Extended Maintenance” mode. Adjust the parameters according to the documentation:

No check note 1582842, I changed these parameters in addition to those above: rdisp/elem_per_queue -> 5000 csi/enable -> 0 system/type -> DS (REMARK: I ignored the warning that the parameter doesn’t exists) abap/buffersize -> 500000 abap/shared_object_size_MB -> 100 rsdb/ntab/entrycount -> 30000 rsdb/ntab/ftabsize -> 60000 rsdb/ntab/irbdsize -> 15000 rtbb/buffer_length -> 60000 rsdb/cua/buffersize -> 10000 zcsa/table_buffer_area -> 100000000 zcsa/db_max_buftab -> 10000 zcsa/presentation_buffer_area -> 20000000 sap/bufdir_entries -> 10000 rsdb/obj/buffersize -> 50000 (remark: I ignored a warning that the value was greater than 10x the default value) rsdb/obj/max_objects -> 20000

Atos

20 March 2012

80 of 163


For internal use


Now Save and Activate the profile. Close the browser and logoff from the SAPGUI. Restart the SAP instance. ADJUSTING THE PROFILE PARAMETER IS IMPORTANT! WE HAD NUMEROUS PROBLEMS ON OUR FIRST SOLMAN INSTALLATION THAT WERE SOLVED AFTER ADJUSTING THE PROFILE PARAMETERS. Now logon again as SOLMAN_ADMIN, run transaction SOLMAN_SETUP and start the System Preparation wizard. Go in to Edit mode and go to Step 2. Click on “Execute all” and verify that the status for all checks turns green:

When all is green, click Next:

7.3

Step 3 – Implement SAP Note In this step, you download and install the central note for your SolMan release. REMARK: The download button in step 3.1 is not working. To fix this, implement note SAP Note 1630074. Restart SOLMAN_SETUP and go to System Prepatrion -> Step 3. Switch to Edit mode.

7.3.1

Step 3.1 - Download In step 3.1 click on Download:

When the note has been downloaded. Click on Next to go to step 3.2.

Atos

20 March 2012

81 of 163


7.3.2

For internal use


Step 3.2 - Import IMPORTANT: OPEN THE NOTE AND FOLLOW THE INSTRUCTIONS IN THE NOTE !!! The central note contains 3 types of notes: ▶ Notes that you need to apply manually first ▶ Notes that can be applied with the central note but that require manual steps ▶ Notes that can be applied with the central note and for which the post-processing can be done automatically via step 3.3 The most convenient way to implement all notes from the central note is to use transaction SNOTE from the SAPGUI. REMARK: You will have to generate a developer key for the user SOLMAN_ADMIN on the SAP Service Marketplace, as you will be modifying SAP object and programs. You will also have to generate object keys for several objects. To register developer and object keys, go to http://service.sap.com/sscr. TIP: During the implementation of notes you can be prompted for workbench requests. I choose to include all note implementations after the installation of SolMan into 1 new request (as recommended by SAP):

REMARK: Note 1690516 gives an error. The central note describes the solution: launch SDCCN and create and run the task to refresh the service definitions. But before you can create the task, you must activate SDCCN via the menu -> Utilities -> Activate. Set the status of the note implementation to “Performed”:

Click on Next to go to step 3.3.

7.3.3

Step 3.3 – Post-Process Click on “Execute” to perform the post-processing for the central note:

Atos

20 March 2012

82 of 163


For internal use


Click Next. Before going to Step 4, return to the SAPGUI and transaction SNOTE. Mark all the notes that were implemented as “Completed”. Some new notes might exist that can be implemented after the implementation of the central note. Review those and implement them if they are relevant.

7.4

Step 4 – Configure ABAP In Step 4, the ABAP instance is configured. All actions are performed automatically. The Help sections describes the activities (see screenshot). Click on “Execute” to perform the actions:

Check in the log (bottom part of the screen) that the step was successful and click on Next.

7.5

Web Service Configuration In this step, you will perform the required configuration for Web Services related to Solution Manager.

7.5.1

Step 5.1 – Configure Web Dispatcher This step is only required if at least one dialog instance exists:

From the EGI slides:

Atos

20 March 2012

83 of 163


For internal use


Just click on Next for this step.

7.5.2

Step 5.2 – Configure Authentication Types In this step, you explicitly allow SAP Solution Manager to create web services using the specified authentication types. Open the Display link to see what actions you need to take, then open the Web Dynpro link to perform the action. Set the status to “Performed” when done:

You have to enable the 3 authentication types and click on Save:

The warning just means that we haven’set up HTTPS (yet). Click on Next to go to step 5.3

Atos

20 March 2012

84 of 163


7.5.3

For internal use


Step 5.3 Logical Ports Configuration In this step, you c Create logical ports and end points for web services communication between the ABAP and Java stack of SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager. Click on the “Execute All” button.

This step takes a little while. After completion, open the Display link and follow the instructions to make sure the actions were performed, then open the Web Dynpro link to verify. Here is the result of the first web service as example:

Click on Next to go to step 6. REMARK: You have to perform this step each time you change the users created in the step 1.

7.6

Step 6 – Prepare Landscape From the EGI slides:

Atos

20 March 2012

85 of 163


7.6.1

For internal use


Step 6.1 – Select SLD REMARK: ONLY configure the local SLD in SAP Solution Manager if you have no other (runtime) SLD in your landscape! (SAP Recommendation). Since we have a central SLD, this is what we configure. Enter the details of the central SLD and click on the “Save” button:

Atos

20 March 2012

86 of 163


For internal use


If you receive this message, just click on OK:

If the SLD is the only SLD or the central SLD, make sure the “Target of SAP Solution Manager DS” field is selected and the status is green:

Click on Next to go to the next step.

7.6.2

Step 6.2 – Prepare Outside Discovery In this step you prepare the connection of CA Wily Introscope Enterprise Managers, third party solutions or stand-alone databases to SAP Solution Manager. Note: On each host, perform the following steps before continuing on the next host: ▶ Install Diagnostics Agent ▶ Install SAPHost Agent

Atos

20 March 2012

87 of 163


For internal use


▶ Establish trusted connection REMARK: You only need to establish a trusted connection if the Diagnostics agent version is below 7.30 SP 01. -> I recommend using Diagnostics Agent 7.30 SP02. Detailed installation steps for the installation of the diagnostics agent on a managed system can be found in the SolMan wiki: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Installation+of+SMD+Agent Open the Display link and follow the instructions in the documentation for each step:

Turn off maintenance mode:

You install a Diagnostics agent on all hosts on which one or more of the following systems is running: ▶ Managed system which should be connected to SAP Solution Manager ▶ CA Wily Introscope Enterprise Manager ▶ Standalone database ▶ Third party product not registered to an SLD REMARK: You need to ensure that the user which is executing the Diagnostics Agent has read/write authorizations to the managed system installation directory REMARK: If you use the diagnostics agent 7.30 installer, to install a diagnostics agent, the SAP host agent is installed simultaneously. BUT you still need to upgrade the host agent, as the included host agent doesn’t meet the rperequisites! It is also recommended to enable the automatic upgrade function of the SAP host agent. For more information, see SAP Note 1473974. For more information about upgrading/installing the Diagnostics Agent and Host Agent, see chapter 9. If you use Diagnostics Agent 7.30SP02 on all your managed systems, you can set the activity “Establish Trusted Connection” to performed.

Atos

20 March 2012

88 of 163


For internal use


REMARK: SAP RECOMMENDS NOT TO REGISTER THE HOST AGENT IN THE SLD BUT CONNECTING IT DIRECTLY TO SOLUTION MANAGER !!! FOR SOLUTION MANAGER AND OTHER INSTALLATION WHERE YOU REGISTERED WITH THE SLD DURING INSTALLATION, YOU HAVE TO UNINSTALL THE DIAGNOSTICS AGENT AND RE-INSTALL IT TO REGISTER THE AGENT WITJ YOUR SOLUTION MANAGER SYSTEM ! For more information about upgrading/installing the Diagnostics Agent and Host Agent, see Chapter 9. For more information about removing a previously registered agent from the SLD, see Chapter 9. AT THIS POINT, RE-INSTALL THE DIAGNOSTICS AGENT ON THE SOLUTION MANAGER SYSTEM AS DESCRIBED IN CHAPTER 9.1. REMOVE THE PREVIOUSLY INSTALLED AGENT FROM THE SLD AS DESCRIBED IN CHAPTER 9.2 UPGRADE THE HOST AGENT AS DESCRIBED IN CHAPTER 9.3. Click on Next to go to the next step.

7.6.3

Step 6.3 – Connect Diagnostics Agents REMARK: This step is only necessary if you registered diagnostics agents in the SLD. If you followed the recommendation and registered all agents directly with Solution Manager, there are no agents to add here. REMARK: This step will remain gray if there are no agents to add, this is normal behavior (thanks SAP…). Click Next to go to the next step.

7.6.4

Step 4 – Set Up LMDB In this step, you set up the Landscape Management Database (LMDB). From the EGI slides:

Atos

20 March 2012

89 of 163


For internal use


You will get a warning when you go to step 6.4, click OK to confirm:

Click on “Configure Object Server”:

Enter a name for the Object Server:

Atos

20 March 2012

90 of 163


For internal use


REMARK FROM SAP: If the local SLD of SAP Solution Manager is used, do not use the host name of SAP Solution Manager as LMDB Object Server Name. You can use LMDB_ instead. Although we have no local SLD on the SolMan system, I followed the proposed naming convention from SAP and used LMDB_SCC. Click on OK. Click on the “Add” button to add a Synchronization Connection between SLD and LMDB:

Fill in the required fields, the click on “Save and Activate”:

Atos

20 March 2012

91 of 163


For internal use


Verify that the sync connection is added and that synchronization has started:

REMARK: THIS PROCESS CAN TAKE SEVERAL HOURS !!! Use the “Refresh” button to follow the progress. When synchronization is compete, make sure the status is green:

REMARK: To avoid errors during LMDB-SLD sync, make sure your SLD content is up-to-date. If you have newer products installed in your landscape, the min. required level is not enough and you have to import the latest content version. Error example:

Refer to SAP note 669669 for upgrading SLD content. Refer to SAP Note 1555955 for information regarding the performance during SLD content synchronization.

Atos

20 March 2012

92 of 163


For internal use


For further information including troubleshooting refer to the LMDB Setup Guide in Media Library -> Technical Information at SAP Service Marketplace (Solution Manager). Click on Next to go to the final step.

7.7

Step 7 – Complete In this step, the status of all steps of the System Preparation scenario is displayed:

REMARK: Not all steps have to be green for your Solution Manager system to be configured correctly. As said before, step 6.3 will remain grey if you have no agents registered in the SLD, therefore the status for step 6 remains yellow. If a newer version of the central note has been released, step 3.1 will be yellow. Click on the “Finish” button to conclude the system preparation. This takes you back to the overview page. In the overview page, you see immediately if updates are needed in System Preparation and/or Basic Configuration (example screenshot from another system):

Atos

20 March 2012

93 of 163


For internal use


The next chapter will explain the Basic Configuration.

Atos

20 March 2012

94 of 163


8

For internal use


Basic Configuration The Basic Configuration wizard helps you to do the minimum configuration to start using your solution manager. It also serves as the basis if you want to configure additional usage scenario’s like e.g. Incident Management or Charm. Basic Configuration will also configure Solution Manager to use Wily Introscope. REMARK: It is recommended to install Wily Introscope BEFORE starting the basic configuration! See Chapter 10 for the installation of Wily Introscope Enterprise Manager and the Wily Introscope Agents. Open SAPGUI, logon to the system as SOLMAN_ADMIN and open transaction SOLMAN_SETUP. Switch to Edit mode.

8.1

Step 1 – Specify Solution In this step, you create a project for the configuration of SAP Solution Manager. In the project, the system saves all status information of the configuration, so you can create only one project for the configuration. SAP Solution Manager automatically includes all production systems of your landscape which are known to the solution and which are not already part of another solution. This makes sure that: ▶ You can perform Service Delivery for all production systems. ▶ SAP EarlyWatch Alert is scheduled for all production systems. By default, SAP proposes to name the solution “SAP Solution”. I propose to adjust it so it remains clear that this is the default solution if more solutions have been created in the system. Click on the “Create” button:

This step can take a few minutes. Click on Next to go to the next step.

8.2

Specify User and Connectivity Data In the sub-steps of this step, you make sure that SAP Solution Manager can be connected to SAP and to other systems.

8.2.1

Step 2.1 – Specify Connectivity Data Specify the S-User for your solution manager system and click on “Maintain Connections”:

Atos

20 March 2012

95 of 163


For internal use



8.2.2

Step 2.2 – Specify SAP BW System In this step you specify how the SAP NetWeaver Business Warehouse (BW) is set up. There are 3 possible scenario’s: ▶ BW in the SolMan client ▶ BW in a separate client ▶ BW in a separate system SAP RECOMMENDED: Install BW in the same client as your solution manager client. The other option are more complicated, require more admin effort and only have advantages if there are extra security requirements and/or sizing reasons (very large landscapes). Choose the standard option and click on Next:

8.2.3

Step 2.3 – Setup Credentials In this step you assign or create administrator users which can be used for further automatic activities. RECOMMENDED: Use SOLMAN_ADMIN. Enter the user SOLMAN_ADMIN and the password, click on “Test Connection” to make sure the user is able to login:

REMARK: If you choose the standard BW environment, the option to specify a BW Administrator is greyed out. Click on Next to go to the next step.

8.2.4

Step 2.4 – Create Users In this step, several dialog and system users are created. For more information about the individual users created select “Display” in the Documentation column next to each user. Click on “Create all Users” and make sure they were created successfully:

Atos

20 March 2012

96 of 163


For internal use


For some users, you will be prompted to supply a password. I used the master password. Click on Next to go to the next step.

8.2.5

Step 2.5 – Solution Manager Internal Connectivity This step performs the following activities automatically and checks the results: ▶ Create RFC connections between ABAP and Java stack on the Solution Manager. ▶ Create URL for the web services and store the URLs in the configuration store of the Diagnostic Agents. ▶ Switch off the maintenance mode of SAP Solution Manager so that the Diagnostic Agents can connect to the SAP Solution Manager. Click on “Execute All” to perform the steps and verify they were successful:

This step takes a while, use the “Refresh” button to monitor progress. Click on Next to go to the next step.

8.3

Step 3 – Specify Landscape Data In the sub-steps of this step you set up CA Wily Introscope Enterprise Manager(s) and enable SAP Solution Manager to send notifications via e-mail and SMS.

8.3.1

Step 3.1 – Configure CA Wily Introscope In this step, you connect existing CA Wily Introscope Enterprise Managers to SAP Solution Manager. We already installed Wily Introscope, see chapter 10 for more details. To maintain the connection between Wily Enterprise Manager and Solution Manager, click on the button “Import Existing Installation”:

Enter the path of the Wily installation directory (check on your system!), select the diagnostics agent from the host where Wily is installed (in our case the SolMan system) and click on “Discover Installation”:

Atos

20 March 2012

97 of 163


For internal use


From the EGI slides:

Select the discovered installation and click on the button “User Management”:

Enter the password for the user Admin (default is Admin89) and click on OK:

Then click on Save (DO NOT SKIP THIS!):

Check the status of the messages on the top of the web page:

Click on the “Refresh” button, the status should now be green:

Atos

20 March 2012

98 of 163


8.3.2

For internal use


Step 3.2 – Configure SAProuter In this step you can allow SAP Solution Manager to access the permission table saprouttab on the SAProuter server via FTP. In this case you do not need to maintain the permission table manually. REMARK: This step is optional, it is usually not performed. We did not perform this step. IMPORTANT: Click on the “Save” button, even if you don’t enter anything !!! Click on Next to go to the next step.

8.3.3

Step 3.3 – Configure SAPconnect In this step you set up the infrastructure which enables SAP Solution Manager to send notifications via e-mail and SMS. We only configured SMTP. Enter the host name and port of the SMTP server and click on “Create”:

Now go back to the SAPGUI and start transaction SCOT. Click on the button “Send Jobs” and create a new scheduled job for type INT:

Keep the proposed values and click on “Continue”:

Atos

20 March 2012

99 of 163


For internal use


This will schedule a job to send e-mails (internet addresses) every 10 minutes. Click on the “Save” button. The job is scheduled now:

Return to the Basic Configuration wizard and click on Next to go to the next step.

8.4

Step 4 – Configure Manually In this step you perform manual configuration activities. From the EGI slides:

REMARK: it is important to execute these two steps IN ADDITION TO the steps listed!!! From the EGI slides:

Atos

20 March 2012

100 of 163


For internal use


Remark: Since we enabled BW in the SolMan client, perform the above action in client 001 or the client that you are using as productive SolMan client. Remark: I got the prompt with “Replicate as well” directly after running transaction RSA1. Remark: Selecting the data source as shown below takes several minutes. After that, I got the prompt to select the source system, as shown above.

Atos

20 March 2012

101 of 163


For internal use


Remark: The job BI_TCO_ACTIVIATION can take quite a while to finish.

Step - Maintain logical components. SOLMAN_ADMIN doesn’t have authorizations to perform this action. Logon with sap* and go to transaction BD54. Maintain the description for logical client SCCCLNT100:

Atos

20 March 2012

102 of 163


For internal use


Save your change, create a new request when prompted and provide a description. Go to transaction SCC4, double click on client 001 and verify the logical system is assigned:

Set the status of this step to “Performed”. Step – Service Content Update Configuration Click on the WebDynpro link for this step. Activate the automatic download and the schedule as background job, then click on “Confirm”:

Set the status of the step to “Performed”. Step – Delete Sessions, Documents and Downloads

Atos

20 March 2012

103 of 163


For internal use


Click on the “Display” link to display the documentation for this step. Click on the link “Start transaction” for this step. Execute the job:

Refer to the documentation of this step to schedule this as a job. REMARK: I currently have no recommendation for the retention period for solution documents and EarlyWatch reports ! Set the status of this step to “Performed”. Step – Setup BMC AppSight You only need to set this up for end-to-end client troubleshooting. This is currently out of the scope for this implementation. For more information about BMC Appsight please refer to SAP note 1034902. Leave the status of the step on “Not Performed”. Step – Migrate Installed Product Instances Data This step is only relevant after upgrading from SolMan 7.0 to 7.1. If you did a fresh installation of SolMan 7.1, you can set the status of this step to “Performed”.

Atos

20 March 2012

104 of 163


For internal use


Step – Migrate Custom Attributes in LMDB Again, this step is only relevant after upgrading from SolMan 7.0 to 7.1. If you did a fresh installation of SolMan 7.1, you can set the status of this step to “Performed”. REMARK: Since we did not perform the installation of BMC ApSight, the status of step 4 will remain yellow. This is normal and doesn’t affect the proper functioning of your Solution Manager. Click on Next to go to the next step.

8.5

Step 5 – Configure Automatically In this step, SAP Solution Manager automatically schedules batch processing jobs. REMARK: The automatic execution of the configuration activities will take several minutes. After the configuration, messages and other detailed information are displayed in the log area. Click on the button “Execute All” to perform the steps, check that the status of each step is green after execution:

Remark: Executing all step can take 15-30 minutes to complete. Remark: to see the logs of 1 step, select that step from the list. When all statuses are green, click on Next to go to the next step.

8.6

Step 6 – BI Manual configuration In this step you perform manual configuration activities related to BW. Click on the Display link to see the documentation for each step. Click on “Start transaction” to perform the activity for each step. Result for the first activity:

Atos

20 March 2012

105 of 163


For internal use


Result for the second activity:

Set both steps to performed when done:


8.7

Step 7 – Complete In this step all of the steps of the basic configuration of your Solution Manager are displayed.

Remark: The step “Configure Manually” remains yellow because we didn’t perform the installation of BMC AppSight. This has no influence on the correct functioning of your solution manager system. Click on “Finish” to complete the Basic Configuration. This will take you back to the overview page:

Atos

20 March 2012

106 of 163


9

For internal use


Diagnostics Agent and Host Agent From the EGI slides:

9.1

Re-Install Diagnostics Agent T latest version is Diagnostics Agent 7.30 SP02, copy the installation CD to your system. Launch sapinst.exe located in the folder SMD730_00_IM_WINDOWS_X86_64 of the CD. Click on Yes when prompted by UAC. Go to software life cycle options -> uninstall:

Atos

20 March 2012

107 of 163


For internal use


Select the profile of the diagnostics agent and click Next:

Next step:

REMARK: If you plan to use a different SID for the diagnostics agent, it is recommended to delete the OS users too. Click Next on the parameter summary page:

Atos

20 March 2012

108 of 163


For internal use


Click OK to complete the uninstall:

To install the latest version of the Diagnostics agent start sapinst.exe again. There is only one installation option, the diagnostics agent:

Set the host name and click Next:

Atos

20 March 2012

109 of 163


For internal use


Keep the default SID, the installation directory is fixed (where you installed your SAP solution). Click Next:

Install in a local domain:

Supply passwords for the Administrator and Service user:

Atos

20 March 2012

110 of 163


For internal use


The latest PRERUIQISITE_CHECK_DATA.XML is attached to SAP Note 855498. Download the file and point the installer to it:

Specify the password for the sapadm user:

Click on Yes to add the diagnostics agent user to the trusted user list:

Atos

20 March 2012

111 of 163


For internal use


Leave the default instance number and click Next:

VERY IMPORTANT: In the next step, select “No SLD destination”. Contrary to the what you see mentioned here, the recommendation is NOT to register diagnostics agents in the SLD!

Atos

20 March 2012

112 of 163


For internal use


Click Next to configure the SolMan connection:

Keep the default connection type (P4):

Specify the SolMan connection information:

Atos

20 March 2012

113 of 163


For internal use


Click Next to have sapinst unpack the necessary archives:

On the Parameter Summary page, you can review all information and adjust if needed. Click Next to start the installation. The installation starts. Click on OK to finish the installation:

Atos

20 March 2012

114 of 163


For internal use


You can verify in the SAP mmc that the diagnostics instance is running:

9.2

Removing Obsolete Agents from the SLD If a diagnostics agent was registered in the SLD, the entry will remain in the SLD even if you uninstall the agent. You need to remove the entry manually from the SLD. Log on to the (central) SLD as admin, go to Administration -> Maintenance:

Go to “Automatically Updated Data”:

Atos

20 March 2012

115 of 163


For internal use


Set the Data supplier type to “DiagnosticsAgentInstance” and click on go:

Remove the correct diagnostics entry from the list. You will receive a warning that the operation cannot be undone, click OK to confirm. REMARK: I don’t know how to determine the correct entry if multiple entries exist, other than trying to find the exact date/time that the agent last update the SLD…

9.3

Upgrading the Host Agent Download the archive SAPHOSTAGENT.SAR from the SAP Service Marketplace, and extract the archive into a temporary directory. The archive contains the saphostexec program. Open an elevated CMD prompt (Run as Administrator). Perform the upgrade by switching to this temporary directory and running the command: saphostexec -upgrade The upgrade process will stop the host agent service and saposcol service, copy the new files to the host agent directory and restart the services. After the upgrade, you can delete the temporary directory again.

Atos

20 March 2012

116 of 163


10

For internal use


Wily Introscope This chapter describes how to install Wily Introscope and the Wily Introscope agents.

10.1

Installing Wily Introscope RECOMMENDED: Before running basic configuration, install the Wily Enterprise manager. We will install it on the SolMan host. RECOMMENDED: To install Wily Introscope, logon to the server as user adm to install Wily Enterprise Manager, in our case this is sccadm. Check SAP Note 797147 – “Wily Introscope Installation for SAP Customers” for the packages and files that you need to download. The .SAR file for the Enterprise manager needs to be extracted. Copy the EM installation folder locally and copy the External Component zip file and eula.txt file into this directory:

Open the files eula.txt and ca-eula.txt and replace “reject” on the very last line of each file with “accept”. If you don’t do this, the installation will fail. Now open the installer.properties file. For our system, these lines were edited: ▶ USER_INSTALL_DIR=G:\\usr\\sap\\ccms\\apmintroscope\\ ▶ externalComponentPackage=osgiPackages.v2.1.2.windows.zip Doubleclick on the installation file:

Click Yes on the UAC prompt. The installation runs silent, so there is no indication when it is done. You can check the task manager to see if the installer is still running:

Atos

20 March 2012

117 of 163


For internal use


REMARK: The installation would start and stop after about 30 seconds. The folder G:\usr\sap\ccms was created, the folder apmintroscope appeared briefly and disappeared again. After a lot of searching the issue appeared to be a trailing space in the installer.properties file in the line with USER_INSTALL_DIR. So make sure you DON’T have a space at the end of this line… If the installer disappears from the task manager, check that the installation directory exists and contains content. Open the installer log G:\usr\sap\ccms\apmintroscope\install\Introscope_9.1.0.0_InstallLog.log and verify that you see this:

Open services.msc and verify that the Introscope service exists and is started. The startup type must be “Automatic”:

Stop the service to prevent getting an Access Denied message when changing the JAVA parameters.

Atos

20 March 2012

118 of 163


For internal use


To adjust the JAVA parameters, open the file G:\usr\sap\ccms\apmintroscope\bin\EMService.conf and adjust these lines:

Copy the file WILY_IS_MM10_0-10010973.SAR to G:\usr\sap\ccms\apmintroscope. Open a CMD prompt with Administrator privileges with focus on this folder and extract the file (sapcar –xvf WILY_IS*.SAR). Now restart the Introscope service with services.msc. Open the link http://dmzvm040.atosorigin-ica.com:8081/webview and logon with user Admin and password Admin89 (default). Click on the Console tab. Open the dropdown list, there should be a lot of dashboards available now (default is 7 dashboards):

Atos

20 March 2012

119 of 163


10.2

For internal use


Installing Wily Introscope Agents Download the latest agent installation SCA files for Wily 8 and Wily 9 and copy them in the transport directory. Although not recommended, I used JSPM with the option “Business Packages” instead of SDM:

Specify the queue:

Click on Start to begin deployment:

When deployment has finished, click on Exit:

Atos

20 March 2012

120 of 163


For internal use


Remark: ISAGENTJ510_0.SCA -> do search on marketplace for the file, it is not available in normal location on the marketplace. This file is needed if you want to deploy the latest agent for new SAP systems with the new JVM.

10.3

Wily Introscope Information From the EGI slides: Remark: The slides are for Introscope 8, Introscope 9 is already released and free for production use. New install -> version 9 recommended.

Atos

20 March 2012

121 of 163


For internal use


Remark: Webview requires the MS Silverlight plug-in.

Atos

20 March 2012

122 of 163


For internal use


Remark: SAP note 797147 is for both version 8 and 9. The guide attached to the note also contains some sizing information.

Atos

20 March 2012

123 of 163


For internal use


Remark: The new installation path for Wily 9 is \user\sap\ccms\apmintroscope -> apm is the database used for Wily.

Remark: It is recommended to make backup of your Wily directory before uninstalling it.

Atos

20 March 2012

124 of 163


Atos

For internal use

20 March 2012


125 of 163


For internal use


Remark: Agent version 9 is used for newer SAP releases that bring their own JVM. With Wily Enterprise Manager 9 you can deploy both agents version 8 and 9 as they use different packages.

Atos

20 March 2012

126 of 163


11

For internal use


Managed Systems Configuration The wizard “Managed Systems Configuration” helps you connect your managed systems to your Solution Manager.

Atos

20 March 2012

127 of 163


12

For internal use


Incident Management The Service Desk from Solution Manager 7.0 has been replaced with a totally renewed application and is now called Incident Management. See also SAP Note 1567003 - FAQ: ST710 Incident Management Frequently Asked Questions. REMARK: From the Security Guide: You can configure the basic technical settings using transaction SOLMAN_SETUP, running the guided procedure for Incident Management for ITSAM Service Management. When you configure these settings and you use user SOLMAN_ADMIN, you need to assign single role SAP_SUPPDESK_CONF_DELTA to this user. REMARK: To avoid problems during Step 2 of the IT Service Management Wizard, adjust the authorizations for role SAP_SUPPDESK_CONF_DELTA to include transactions CRMC_UI_NBLINKS and AI_CRM_CPY_PROCTYPE:

Logon as user sap* to adjust the role and assign it to user SOLMAN_ADMIN. From the EGI slides:

Atos

20 March 2012

128 of 163


Atos

For internal use

20 March 2012


129 of 163


12.1

For internal use


Prerequisites To check the prerequisites, logon to client 001 as SOLMAN_ADMIN. Launch transaction SOLMAN_SETUP. We will be using both the SAPGUI and the browser window for SOLMAN_SETUP to check the prerequisites. REMARK: From the Security Guide: You can configure the basic technical settings using transaction SOLMAN_SETUP, running the guided procedure for Incident Management for ITSAM Service Management. When you configure these settings and you use user SOLMAN_ADMIN, you need to assign single role SAP_SUPPDESK_CONF_DELTA to this user. From the EGI slides:

Atos

20 March 2012

130 of 163


For internal use


System Preparation, Basic Configuration and Managed System Configuration should performed completely and error free. System Preparation In this guided procedure, you make settings preliminary for the Solution Manager configuration, such as creation of dialog users with the required authorizations, implementation of the central correction note and web service configuration. Basic Configuration This guided procedure leads you through all configuration steps which you must perform to enable basic scenarios in the SAP Solution Manager. As part of the basic configuration, you set up the connection to SAP, schedule relevant background jobs and activate piece lists which contain important settings, such as standard customizing for the new transaction type Incident (SMIN). Managed System Configuration It is relevant for the usage of the Feedback functionality, i.e. to be able to create incidents / support messages from satellite systems. In the Managed System Configuration, you connect satellite systems to the Solution Manager via RFC.

12.1.1

Solution Manager 7.1 SP03 Installed We have Solution Manager 7.1 SP04 installed as described in this guide.

12.1.2

Central Note Implemented Check in the System Preration wizard that step 3 is all green:

Atos

20 March 2012

131 of 163


For internal use


Each Solution Manager System 7.1 Support Package Stack has a corresponding Central Correction SAP Note: ▶ SAP Solution Manager - Basic functions 7.1 SP1 - 1552585 ▶ SAP Solution Manager - Basic functions 7.1 SP2 - 1584162 ▶ SAP Solution Manager - Basic functions 7.1 SP3 - 1613410

12.1.3

RFC connection SAPOSS Working In the SAPGUI, open transaction SM59 and expand the ABAP Connections. Double click on connection SAPOSS. From the menu, choose Utilities->Test->Authorization Test and check that it is successful:

You can find detailed information about the SAPOSS configuration in SAP Note 33135. For information about the service connection see SAP Note 35010.

12.1.4

Verify Connections SAP-OSS and SAP-OSS-LIST-O01 These RFCs are used by Service Desk scenario: ▶ SAP-OSS (send service desk message to SAP Service and Support Backbone) ▶ SAP-OSS-LIST-O01 (update service desk messages with SAP Service and Support Backbone) In Step 2.1 of the Basic Configuration you specified the connectivity data (S-User) for these RFC’s and you create these connections. In the SAPGUI, open transaction SM59 and expand the ABAP Connections. Double click on connection SAP-OSS. From the menu, choose Utilities->Test->Authorization Test and check that it is successful.

Atos

20 March 2012

132 of 163


For internal use


Repeat for SAP-OSS-LIST-O01.

12.1.5

S-User Authorizations The S-User is required for SAP Collaboration. S-User authorization allows the user to send incident message to SAP Service & Support Backbone. This is also required for synchronization of incident messages between SAP Service & Support Backbone and Customer Solution Manager. These S-User authorization are required for message processor of Application Incident Management: ▶ Confirm Customer Messages ▶ Create Customer Messages ▶ Send Customer Messages to SAP ▶ Open Service Connections (optional, if your Processor should be authorized to open Service Connection for SAP Collaboration) ▶ Maintain System Data (SOLMAN_BTC) We created S-User S0009459423 specifically for this Solution Manager installation. Here are the authorizations on the SAP Service Marketplace (for the sapCC customer number 208245):

12.1.6

Piece List Activation The import of piece lists is required by SAP Solution Manager. These piece lists contain the default configuration, for example Maintenance Optimizer, Service Desk or Change Request. The SAP default customizing will be copied from client 000 to your logon client and overwrite only SAP customizing. REMARK: This activity has no effect on customer configuration and has to be run after each Support Package import. Activating the piece lists was done during the activity “Activate Piece Lists” during Step 5 – Configure Automatically of the Basic Configuration. Go to the wizard “IT Service Management”, switch to Edit mode and execute step 1 to check the activation:

Atos

20 March 2012

133 of 163


For internal use


Remark: Activating the piece lists can also be performed by starting transaction SCC1 and entering transport request AI_CUSTOMIZING.

12.1.7

Activation of Services Activating services lists was done during the activity “Activate Services” during Step 5 – Configure Automatically of the Basic Configuration. Go to Basic Configuration step 5 and select this activity. Verify the logs for this activity to check that all services were created:

12.1.8

Schedule Background Jobs Make sure these jobs are scheduled: ▶ REFRESH MESSAGE STATUS -> at least twice a day (default: hourly) ▶ SOLMAN_ISSUE_STATUS_REFRESH -> monthly ▶ REFRESH_ADMIN_DATA_FROM_SUPPORT -> daily ▶ SEND_SYSTEM_RELATIONSHIP_TO_SUPPORT ▶ SERVICE_CONNECTION_LISTENER ▶ AI_SDK_FILL_FILE_TYPE_TABLE ▶ SM:CSA SESSION REFRESH ▶ SM:CSA UPDATE TASKSTATUS Background Job Frequency REFRESH MESSAGE STATUS At least twice a day (default: hourly) REFRESH_ADMIN_DATA_FROM_SUPPORT Daily SOLMAN_ISSUE_STATUS_REFRESH Monthly SEND_SYSTEM_RELATIONSHIP_TO_SUPPORT Daily SERVICE_CONNECTION_LISTENER 10 Minutes AI_SDK_FILL_FILE_TYPE_TABLE Quarterly SM:CSA SESSION REFRESH Daily SM:CSA UPDATE TASKSTATUS 30 minutes SM:GET CSN COMPONENTS At least quarterly (default: weekly)

Atos

20 March 2012

SAP Note 1566108 1490774

1080131

134 of 163


For internal use


Scheduling background jobs was done during the activity “Schedule Background Jobs” during Step 5 – Configure Automatically of the Basic Configuration. In the SAPGUI, go to transaction SM37. Enter a job name and click on Execute:

The result list is displayed:

Press the F2 key to check the job details and verify the schedule:

Repeat these steps for all background jobs.

Atos

20 March 2012

135 of 163


For internal use


If a job doesn’t exists, create it via transaction SM36. REMARK: Job AI_SDK_FILL_FILE_TYPE_TABLE did not exist in our system. Start transaction SM36. Specify a name for the job and click on Step, then specify the ABAP program:

Click on “Start Condition”, the click on “Immediately” and specify a period value of every 3 months:

Atos

20 March 2012

136 of 163


For internal use


Save your settings. Repeat this for all jobs that don’t exist.

12.1.9

Managed System Configuration This is relevant for the usage of the Feedback functionality, i.e. to be able to create incidents / support messages from satellite systems. Make sure that your managed systems are registered correctly in the SLD. For ABAP systems make sure that the RFC connections have been maintained and that the Back-RFC connection is created. This is done in step 3 of the Managed Systems Configuration wizard for an ABAP system. Logon to the managed system, call transaction SM59 and perform an authorization test on the backRFC. Remark: A Back-connection is required for ?????

12.1.10

Check Table for Customer Data In the SAPGUI, call transaction SM30. Open the table V_AISAPCUSTNOS in Maintenance mode:

If the table is empty, click on the button “New Entry”. Enter your customer number and Save:

Click on the Back button. Go to transaction SM36 and run the job REFRESH_ADMIN_DATA_FROM_SUPPORT. After the job has completed, launch transaction SM30 again and check that table V_AIINSNRS is filled with the installation numbers for your customer number:

Atos

20 March 2012

137 of 163


For internal use


Remark: If you are looking after many SAP customer numbers and are registered as a value-added reseller (VAR) or Customer Competence Center (CCC) at SAP, you can determine all managed SAP customers from the SAP Support Portal. To do so, start transaction SE38 and run the report AI_SC_GET_SAP_CUSTOMER_NUMBERS. Remark: In transaction SE16 you can view the contents of table AICONTACTS, which holds the user contact data information.

12.2

IT Service Management Wizard This wizard is a guided procedure to help you configure Incident Management. Start transaction SOLMAN_SETUP and click on “IT Service Management” in the left navigation menu.

12.2.1

Step 1 – Check Prerequisites This step was already performed while checking the prerequisites. Go in Edit mode, make sure the status is green and click on Next:

12.2.2

Step 2 – Copy Transaction Types In this step you copy the transaction profile and optionally the Business Role SOLMANPRO.

12.2.2.1

Copy Transaction Profile Transaction SMIN is used for Incident Management, SMPR is used for Problem Management. REMARK: If an ABAP dump occur during copy report please have a look to SAP Note 1640226. REMARK: Recommended reading and VERY useful literature to have along this document is the guide “Business and Authorization Roles (ITSM)” for Solution Manager 7.1. Click on the link “Start Transaction” to copy the transaction profile:

Atos

20 March 2012

138 of 163


For internal use


In the SAPGUI for HTML, enter SMIN as the source and ZMIN as the target and click on the “Execute” button. In the preview, click OK to confirm:

This can take a few minutes. In the next screen, click on the button “Start Copying Process”:

When prompted for a transport request, create a new one:

Atos

20 March 2012

139 of 163


For internal use


And confirm:

Confirm also the next prompt:

You will also be prompted for a workbench request, create a new one and use it when prompted for a workbench request (2-3 times). Repeat the same procedure to copy transaction SMPR to ZMPR.

12.2.2.2

Copy Business Role Next is to create a copy of the business role SOLMANPRO. From the EGI Sildes:

Atos

20 March 2012

140 of 163


For internal use


First we will need to copy the authorization roles. After that we create copies of the technical roles. Finally we create a copy of the business role and at the same time assign our technical roles and authorization profile to it. REMARK: The standard business role (Z)SOLMANPRO is assigned to the PFCG role (Z)SAP_SM_CRM_UIU_SOLMANPRO. This means, that each user who has this role assigned is also assigned to the business role (Z)SOLMANPRO. REMARK: The composite role SAP_SUPPDESK_PROCESS_COMP contains the role SAP_SM_CRM_UIU_SOLMANPRO!

12.2.2.3

Copy Roles Following SAP delivered roles should be copied to the customer namespace: ▶ SAP_SUPPDESK_ADMIN_COMP -> ZSM_SUPPDESK_ADMIN_COMP ▶ SAP_SUPPDESK_PROCESS_COMP -> ZSM_SUPPDESK_PROCESS_COMP ▶ SAP_SUPPDESK_CREATE_COMP -> ZSM_SUPPDESK_CREATE_COMP Logon to the SAPGUI with user sap* and go to transaction PFCG. Enter SAP_SUPPDESK_ADMIN_COMP and click on the Copy button:

Change the name of the target role to ZSM_SUPPDESK_ADMIN_COMP and click on “Copy Selectively”:

Atos

20 March 2012

141 of 163


For internal use


Confirm to copy only Personalization:

Click on Yes to copy and re-enter the singles roles:

Adjust the names of the single roles by changing “SAP_” into “ZSM_”:

Check the log and confirm:

Atos

20 March 2012

142 of 163


For internal use


Go into change mode for the copied role:

Go to the “Roles” tab:

Double click on a role, it will open in a new session. Go into change mode and select the authorizations tab. Click on the Edit button to change the authorization data:

Atos

20 March 2012

143 of 163


For internal use


Make sure all objects are green and click on “Save”. When prompted, confirm to create the profile:

Hit the “Back” button, click on “Generate” when prompted to generate the profile:

The “Authorizations” tab should be green now. Save the profile and hit the “Back” button:

Atos

20 March 2012

144 of 163


For internal use


This brings you back to the roles tab of the composite profile. REMARK: when you come across an authorization that has a status yellow, click on the yellow triangle. This will assign a “*” as value to any open field:

If you use organizational levels, you will want to maintain the organizational levels, this falls outside the scope of this guide. REMARK: Repeat this for each single role of the composite role, EXCEPT for ZSM_SM_CRM_UIU_SOLMANPRO and ZSM_SMWORK_INCIDENT_MAN. These are strictly navigation roles linked to business role SOLMANPRO and only need a user comparison! When all single roles are maintained, go to the “Users” tab and perform a user comparison:

Atos

20 March 2012

145 of 163


For internal use


Make sure all roles are green, you can ignore the warning for the navigation role. Repeat the same procedure for the composite roles SAP_SUPPDESK_PROCESS_COMP and SAP_SUPPDESK_CREATE_COMP. REMARK: A number of the single roles will already exist and the copy of those roles will fail. Make sure you note all the single roles assigned to the composite role and add the ZSM_* single roles manually after the copy of the composite role. IMPORTANT: Assign the role ZSM_SUPPDESK_ADMIN_COMP to user SOLMAN_ADMIN and/or the user you will use to do any further customizing that requires the use of the CRM web UI !

12.2.2.4

Copy Technical Roles This section describes how to copy the technical roles. For this section, make sure you logon as SOLMAN_ADMIN again! In the SAPGUI, start transaction SPRO. In the IMG, navigate to Customer Relationship Management -> UI Framework -> Technical Role Definition:

We will work through these transactions one by one.

12.2.2.5

Define Navigation Bar Profile Click on the button in the IMG to start the transaction.

Atos

20 March 2012

146 of 163


For internal use


Select on the left “Define Navigation Bar Profiles”, highlight the profile SOLMANPRO and choose “Copy As”:

Change the name to ZSOLMANPRO and hit Enter to confirm. In the pop-up, click on “Copy All”:

You will get a screen where you are asked to enter a.o. object type and object action. You can ignore these for now, just hit the “Skip” button:

You will have to hit the “Skip” button several times (5 in our case) until the rest of the dependencies have been copied and you see this message:

Atos

20 March 2012

147 of 163


For internal use


Confirm and Save. When prompted for a customizing request, create a new one, provide a description and click on “Confirm”:

Hit the “Back” button to return to the IMG.

12.2.2.6

Define Role Configuration Key Click in the IMG to perform the activity. Click on “New Entries” and enter ZSOLMANPRO with description “Key Role for ZSOLMANPRO”:

Click on Save. Choose the same customizing request. Hit the “Back” button to return to the IMG.

12.2.2.7

Define Technical Profile Click in the IMG to perform the activity. Highlight DEFAULT_SOLMANPRO and click on “Copy As”:

Change the name to ZDEFAULT_SOLMANPRO and hit Enter to confirm:

Atos

20 March 2012

148 of 163


For internal use


Save your changes, use the same customizing request. Hit the “Back” button to return to the IMG.

12.2.2.8

Define Layout Profile Click in the IMG to perform the activity. Highlight CRM_UIU_MASTER and click on “Copy As”:

Change the name to ZCRM_UIU_MASTER and hit Enter to confirm. Select “Copy All” when prompted and save your changes. Use the same customizing request. Hit the “Back” button to return to the IMG.

12.2.2.9

Copy Business Role Go back to the browser window of SOLMAN_SETUP. Click on the link “Start Transaction” next to the activity “Optional: Copy Business Role”:

The SAPGUI for HTML opens the IMG, click on “Define Business Role”:

Select business role SOLMANPRO and choose “Copy As”:

Atos

20 March 2012

149 of 163


For internal use


Adjust the names of the technical profiles to the ones you created as mentioned above. Adjust the name of the business role to ZSOLMANPRO and press ENTER:

When prompted select the customizing request you created for “Incident Management Customizing”. Save and exit the SAPGUI for HTML session. REMARK: Here you link the authorization role ZSM_SM_CRM_UIU_SOLMANPRO to the business role ZSOLMANPRO. Set the step to status performed:

Click on “Next” to go to Step 3.

12.2.3

Step 3 – Automatic Configuration In step will be checked if the following entry exists in table BCOS_CUST: OSS_MSG W NONE CUST620 1.0 If not, it will be created. Secondly, the role "Contact Person" is created for all existing Business Partners of type "person" in your system.

Atos

20 March 2012

150 of 163


For internal use


Click on “Execute All” to perform the activities and verify in the logs that they were successful:

Click on “Next” to go to step 4.

12.2.4

Step 4 – Manual Configuration In this step, you perform manual configurations needed for Incident Management. For each step, review the documentation! REMARK: It is VERY useful to have the document “Application Incident Management Configuration and Upgrade Guide” for Solution Manager 7.1 along with this document for reference!

12.2.4.1

Specify Transaction Type for Incidents Click on the link to start the transaction in the SAPGUI for HTML. Remark: In case you would like to use more than one transaction type, you can create several entries with Field Name PROCESS_TYPE_ADD and enter the transaction types as Field Value. In the table, change the values for these entries and then click on Save: ▶ PROCESS_TYPE: SMIN -> ZMIN ▶ PROCESS_TYPE_ADD: SMDT -> ZMPR

Remark: Beyond the SOLMAN_SETUP activity you can call transaction DNO_CUST04 to specify transaction type for incidents and problem in customizing. When prompted, select the customizing request you created for Incident Management Customizing:

Atos

20 March 2012

151 of 163


For internal use


Set the activity status to “Performed”.

12.2.4.2

Classify Transaction Types This activity specifies the transaction types you want to use in the Incident Management. Remark: You can also maintain the relevant table AISDK_PROCTYPE with transaction SM30. Click on the link to start the transaction in the SAPGUI for HTML. Confirm the warning:

Click on the button “New Entries” and create two entries for ZMIN and ZMPR, set the Scenario to “Standard” and click on Save:

When prompted, select the workbench request you created earlier:

Set the activity status to “Performed”.

12.2.4.3

Maintain SAP Customer Number We covered this in chapter 12.1.10. Launch the transaction and verify that the entry with your customer number exists:

Atos

20 March 2012

152 of 163


For internal use


Exit the transaction, set the activity status to “Performed”.

12.2.4.4

Maintain S-User for SAP Backend You have to assign an SAP Support Portal contact person to the Solution Manager users who communicate with the SAP Support Portal. Remark: you can use transaction AISUSER to do this. Click on the link to start the transaction. You will already see two entries for SOLMAN_ADMIN and SOLMAN_BTC, this was done during “Step 2.1 – Specify Connectivity Data” of the Basic Configuration wizard:

Exit the transaction and set the status of this activity to “Performed”. REMARK: If you have multiple customer numbers, refer to the documentation of this step!

12.2.4.5

Create Product Hierarchy In this IMG activity, you define the basic hierarchy for the product type service with assignment of set types. Click on the link to start the transaction and click on “Execute”:

Atos

20 March 2012

153 of 163


For internal use


Remark: Do not change the default values in the fields! Remark: the names for hierarchies and categories are created automatically only in the logon language. You will get this error:

Apparently this has already been performed, but I couldn’t find back where exactly… Exit the transaction, set the activity status to “Performed”.

12.2.4.6

Generate Sample Categorization Scheme Multilevel categorization is a powerful feature which enables you to design individually the categorization of business transactions, such as incidents or change requests. Furthermore, it integrates the functions auto completion and item determination based on categories. By using multilevel categorization in business transactions, it is also possible to search for related problems, knowledge articles and change requests. In this step, we will activate the default Categorization Schema delivered by SAP. REMARK: It is VERY useful to have the document “Multilevel Categorization” for Solution Manager 7.1 along with this document for reference! For even more information, see the online help: http://help.sap.com/saphelp_crm70/helpdata/EN/48/bbe9add6b3356be10000000a421937/framese t.htm Click on the link to start the transaction. Select the option to activate the schema and click on “Execute”:

Atos

20 March 2012

154 of 163


For internal use


Remark: Ensure that there is no active categorization schema for the transaction types listed above before you run the report! You should get a success message:

Now switch to the SAPGUI and call transaction SPRO. Open the Reference IMG and navigate to: SAP Solution Manager -> Capabilities -> Application Incident Management -> Multilevel Categorization. Execute the step “Assign Transaction Types to Catalog Categories”:

Atos

20 March 2012

155 of 163


For internal use


Mark the line where the Trans. Type is SMIN and click on the copy button:

Enter ZMIN as the Trans. Type and hit the ENTER key:

Remark: I got a warning saying to choose from the list of allowed entries. Apparently we already executed this, I guess is step 12.2.4.2 “Classify Transaction Types”. Now execute the step “Define System Proposals for Related Transactions”. Mark the line where the source transaction type is SMIN and the target is SMPR and click on the Copy button:

Atos

20 March 2012

156 of 163


For internal use


Enter ZMIN and ZMPR as the new source and target and hit ENTER:

Click on Save. When asked, choose the customizing request you created for the Incident Management customizing:

Now launch transaction SM_CRM in the SAPGUI. This launches the CRM web UI. Remark: This requires the role ZSM_SUPPDESK_ADMIN_COMP! Navigate to Service Operations -> Categorization Schema’s:

Atos

20 March 2012

157 of 163


For internal use


Enter as search criteria for the Name field SAP_SOLUTION_MANAGER_TEMPLATE and click on Search:

Select the schema and click on the “Copy Schema” button. (Before we start customizing, we will copy the default schema into the customer namespace.) Click on the “Copy” button:

Enter ZSM_SAP_SOLUTION_MANAGER_TEMPLATE for the Schema ID and Name and enter a description:

Save the template. REMARK: I got 13 warning messages “Schema overlaps with other schemas in application area”. I don’t know yet where these come from and how to solve them…. REMARK: You are supposed to assign the ZMIN transaction type in Application Areas of your Z* schema. Same procedure should perform for copied Problem transaction type and copied Knowledge transaction type -> I was unable to do this, don’t know why yet… Open the template in Edit mode. In the “General” section, set the status to “Released” and save the template:

REMARK: to perform changes on a schema create a new schema version. In the Incident Management wizard, change the Execution Status of the step to “Performed” and check that the step is in green.

Atos

20 March 2012

158 of 163


12.2.4.7

For internal use


Generate BP Automatically In this IMG activity, you create a business partner type (key user end user) in the SAP Solution Manager system for the users that only have user accounts in managed systems.

This method to create system user and business partner is often used to create the Incident Reporter. Every Reporter should have the same user right rights (authorization) in Solution Manager. You require AIM system user and Business Partner in the SAP Solution Manager System. All user from the managed system(s) should be created as a system user (SU01) and business partner (+ updating). All user from date ‘Users changed since’ are taken. You can create a Reference User with specific authorizations and use this to assign these authorizations to every new created system user. REMARK: We will not perform this step, as we will create users and their business partners automatically in Solution Manager via a WebDynpro program on our Enterprise Portal.

12.2.4.8

Generate Users and BP Automatically In this IMG activity, you can create and/or update users and business partners by means of mass maintenance using report AI_SDK_USER_BP_GEN. This allows every user who creates a message in the managed system to track their processing status in the Solution Manager system.

Atos

20 March 2012

159 of 163


For internal use


REMARK: We will not perform this step, as we will create users and their business partners automatically in Solution Manager via a WebDynpro program on our Enterprise Portal.

12.2.5

Step 5 – Additional Configuration In this step you can perform additional configurations. The activities listed in this step are not mandatory, but provide access to optional configuration transactions and guides.

12.2.5.1

Maintain Problem Categories In this Customizing activity, you define problem categories. Problem categories are used to classify problems. The problem categorization can be set after a final solution has been found. It has mainly reporting benefits to analyze the efficiency of the Problem Management. Click on “Start Transaction”:

Click on “New Entries”:

Enter the new problem categorie(s) and description(s) and click on Save:

Atos

20 March 2012

160 of 163


For internal use


When prompted, select the Incident Management Customizing request you created earlier and confirm:

In the overview of added entries, click on Save again and then on Back:

Check that your new entry is in the overview and exit the transaction. Set this step to Performed:

12.2.5.2

Maintain Organizational Model An organizational model models the functional organizational structure of your company. Organizational units represent functions such as department, group, etc. Positions show how tasks are assigned to jobs, e.g. end user, purchaser or message processor. REMARK: User SOLMAN_ADMIN has by default not enough authorizations. Use an account with SAP_ALL to perform this action. REMARK: I was unable to find out which authorizations were required. If you click on “Start Transaction”, the IMG opens. You can also do this from within the SAPGUI, by launching transaction SPRO and then choose “SAP Reference IMG”. Drill down to: SAP Solution Manager -> Capabilities -> Application Icncident Management -> Organizational Model.

Atos

20 March 2012

161 of 163


For internal use


Click to launch: Enter or confirm the validity date for the root organizational object:

….

Atos

20 March 2012

162 of 163


13

For internal use


Logbook The logbook will contain any actions/modifications/configurations that are performed after the initial setup and configuration. Create a sub-chapter each time and always mention the date and the activity performed in the chapter title.

13.1

18/05/12 – Download latest version of all already implemented notes In preparation to download and implement the newest release of the central note, go to transaction SNOTE, open the note browser and download the latest version of all notes already implemented.

Atos

20 March 2012

163 of 163

SolMan 7.1 - Setup Guide

Recommend Documents