Products Industries Support Training Community Developer Partner

About

Home / Community + Actions

Solution Manager 7.2 – Installation and

Configuration – II – Configurations
February 20, 2016 | 62,931 Views |

Yuksel AKCINAR
more by this author

SAP Solution Manager

sap solution manager | solution manager | solution manager 7.2

share share tweet share

Follow
Part 1: Solution Manager 7.2 – Installation and Configuration – I –
Installations

Part 2: Solution Manager 7.2 – Installation and Configuration – II –

Configurations

Part 3: Solution Manager 7.2 – Installation and Configuration – III – Changes

from 7.1 to 7.2

Part 4: Solution Manager 7.2 – Installation and Configuration – IV –

Managed System Config – General Info

Part 5: Solution Manager 7.2 – Installation and Configuration – V – Managed

System Config – ABAP System

Part 6: Solution Manager 7.2 – Installation and Configuration – VI –

Managed System Config – HANA DB

Part 7: Solution Manager 7.2 – Installation and Configuration – VII –

Managed System Config – Busines Objects

Part 8: Solution Manager 7.2 – Installation and Configuration – VIII –

Managed System Config – Java System

You will find the configuration details of Solution Manager 7.2 on this
blog.

Solution Manager 7.2 Configurations

I- CA Introscope Enterprise Manager Strategy

From Master Guide;

CA Introscope Enterprise Manager must be installed on the SAP

Solution Manager host or on a separate host.

For more information, see service.sap.com/instguides –> Installation

& Upgrade Guides –> SAP ComponentsSAP Solution ManagerRelease
7.2 –> 6 Additional Guides – Introscope –> Introscope Setup Guide
9.7.

Useful SAP Notes about Introscope Enterprise Manager

1565954 – Introscope 9 Release Notes

797147 – Introscope Installation for SAP Customers

2138309 – Introscope 9.7 Release Notes for changes and

open issues

1579474 – Management Modules for Introscope delivered

by SAP

Follow the Setup Guide for downloading and installing the

Interescope Enterprise Manager current version 9.7.

Install java package, Modify installer.properties first and run the OS

independent installer.

You can verify the successful installation checking the installation

logs from wily log directories.

You should carry on the post installation steps like adapting java
parameters, isntallaing sap modules etc.

After successfull installation you can reach the IEM webview or

workstation using the urls like http://emhost:8081/webview or
http://emhost:8081/workstation.

Or you can use Solution Manager Root Cause Analysis work_center.

Sample workstation screen;

 Sample webview screen;

II- SOLMAN_SETUP – Mandatory Configurations

These notes should be read carefully and applied before

configuring the system.

2236044 – SAP Solution Manager 7.2 Support Package 01: Dump in

transaction SOLMAN_SETUP

2229953 – Solution Manager 7.2 SP Stack 01: recommended

corrections

2154957 – Unified Rendering for SAP_UI 740

 2212887 – Corrections for unified rendering up to SAP_UI 740/14
Ia

1411980 – Comments about the implementation of unified

rendering corrections

There are 3 mandatory configuration scenarios; System Preperation,

Infrastructure Preperation and Basic Configuration.

Here are the detail steps for all these configuration scenarios.

1- System Preperation

Define the System’s Role in the firts step.

There are manual and automatic activities to perform in Check

Prerequisites Step. Each step  has its documentation. You can
Display the documentation and follow the instructions carefully.

There is a navigation link also for the related transaction or web

dynpro or related urls.
On Setup Connections to SAP step you have RFC Connectivity part
for creating SAPOSS and SAP-OSS-LIST-O01.

And there is Support Hub Connectivity part for below

functioanalities;

• Configure SOAP Runtime  : User SRT_ADMIN to configure SOAP

according to the documentation.
• Register new S-User in SAP’s PI System : You create a technical
user on SMP according to the notes “2174416 – Technical User for
Data Transfer with SAP Backbone System and 2174416 – Technical
User for Data Transfer with SAP Backbone System”
• Specify Configuration parameters

There are automatic activities Configure SSL Store, Configure

Consumer Proxies and Log. Port and Check Channel Configuration.

The help screen for this step explains us about the new 
communication channel of SAP with below paragraph.

“SAP will introduce a new infrastructure and data communication

channels, starting with SAP Solution Manager 7.2. This new
framework builds the foundation for all future applications
exchanging data between SAP Solution Manager and the SAP Support
Portal in a secure, reliable, and controlled way. Existing applications
will not be affected by this change and they will be migrated to the
new platform gradually within the next few years without business
disruption.”

In Apply Recent Corrections step, you apply recent ABAP and Java
corrections to your SAP Solution Manager system

In Maintain Technical Users step you create or update dialog users,

technical users, or BW users, and assign roles to users, depending on
the scenario.

In the last Complete step you can see overall configuration of system
preperation steps. In need you can jump to the required step back.
2- Infrastructure Preperation

In this scenario you configure the infrastructure to run SAP Solution

Manager. There are 8 steps to succeed the configuration of the
scenario.

In the “1- Set Up Landscape Management” step you set up the

synchronization of the system landscape directories (SLDs) and SAP
Solution Manager, to keep the information about the system
landscape up-to-date. Each substep screens can be seen below.
In substep SLD Connnections you create a new connection like
below.

“2- Set Up Java Connectivity” step consists of Define HTTP

Connectivity, Enable Connectivity and Diagnostics Agent
Authentication substeps. You provide required field values
accordingly and execute automatic configurations as seen below.

Solution Manager is using SAP BW for reporting purposes. You can

use either the currnet client of Solution Manager or you can define
another SAP BW system. In “3- Set Up SAP BW” step you firstly
confirm the BW system, then create BW users and in the last substep
you execute automatic acitivities.

You must have defined the logical system name for your BW client.

In “4- Define CA Interescope” Step you discover and define your

Interescope Enterprise Manager. You must have installed Diagnostic
Agent (DAA) Instance on your Solution Manager System. You can
manage Interescope EM users in this step also.

In “5. Set up E-Mail Communication“  step you set up the

infrastructure that enables SAP Solution Manager to send
notifications using e-mail and text messaging (short message service,
SMS).

Some scenarios in SAP Solution Manager needs CRM infrastructure. In

“6- Configure CRM Basics” step you configure these infrastructure in
manual and automatic steps.
In “7- Enable Gateway Services” you activate OData services in SAP
Gateway for SAP UI5 applications and mobile applications. With this
activation you can use SAP Fiori applications for Solution Manager
services. For SAP Solution Manager, the SAP Gateway and SAP
Solution Manager share the same system.

As a prerequisite the user who performs this step has a task in the
customizing transport request. Activation of the services uses this
task.

After selecting the required services you prepare activation and then
with the help of the help text you Start Transaction and activate
OData services.

And in the final “8 – Complete” step you see the statuses of all
steps. If you have any red status steps you could go back and correct
the configuration.
 Now you can pass the Basic Configuration Scenarios.

3- Basic Configuration

There are five steps to fulfill in this scenario as you can see below
picture. In the first “1- Configure Basic Functions” step you
execute automatic configurations for creating logical ports,
activating services, enabling Solution Manager applications.

In “2- Schedule Jobs” step many important Solution Manager Jobs

are scheduled.
In “3- Configure Manually” step, you configure the following:

• Content update (SAP Solution Manager Content, service content)

• Connection from SAP to the SAP Solution Manager system

• Session housekeeping

In “4- Create Basic Dialog Users” step, you create or update dialog
users for root cause analysis (SAPSUPPORT) and service delivery
(SAPSERVICE).

This final “5- Complete” step provides an overview of the steps that
have been performed in this scenario, including information about
the users who made the changes, and the status of each step.
This is the end of Solution Manager 7.2 configurations.

Next topic will be about the changes from Solution Manager 7.1 to
Solution Manager 7.2 in terms of System Administration.

Thanks for your interests.

49 Comments
You must be Logged on to comment or reply to a post.

C. India Demo Enviroment

February 21, 2016 at 10:46 am

Nice job, Yüksel!

Do you have plans to post “upgrade and Java split to SM7.2” blog?

Thanks in Advance

Cheers,

Deeru
 Yuksel AKCINAR Post author

February 21, 2016 at 1:04 pm

Hello Deeru,

I haven’t done it yet but planning to do both.

Regards,

Yuksel AKCINAR

ramesh yad

February 23, 2016 at 6:41 am

Hello Yüksel,

Excellent Post.

Thanks for sharing.

Thank you

Ram

Yuksel AKCINAR Post author

February 23, 2016 at 11:24 am

Thanks Ram.

Anand Yadav

February 23, 2016 at 4:14 pm

Nice blog !!
 Yuksel AKCINAR Post author

February 25, 2016 at 12:07 am

Thanks Anand.

Aniket Singh

March 2, 2016 at 8:29 am

Nice Blog.

In our case, we have installed the EM on a separate server. Can you please
suggest the required steps that we need to perform so that we can integrate
EM with Solman instance.

Regards,

Aniket

Yuksel AKCINAR Post author

March 2, 2016 at 8:49 am

Hello Aniket,

I think you have installed IEM already. If not you coud check the
setup guide link.

In “2- Infrastructure Preperation” step “4- Define CA Interescope”

there are prerequisites.

You should install DAA on IEM host also. In order to discover IEM
configuration uses DA.

After discovery SM will be connected to IEM anymore.

“
Prerequisites

•Diagnostics Agents are active on all hosts of your CA Introscope

Enterprise Managers (stand-alone IS EMs, MoMs, Collectors). For
more information, see SAP Note 1365123.

•The OS user that executes the Diagnostics Agent has read/write

authorization for the Introscope Installation directory and files.

Regards,

Yuksel AKCINAR

Aniket Singh

March 2, 2016 at 9:12 am

Hi Yuksel,

Thanks for your insight.

Yes, we have already installed IEM’s (one MOM and

2 Collectors) running on Windows boxes.

The installation of SMD agents on IEM’s will follow

the same steps as we do it while installation of SMD
on SAP managed systems through SWPM. Or it will
be different.

Regards,

Aniket

Yuksel AKCINAR Post author

March 2, 2016 at 9:48 am

Hello Aniket,

Yes, the same procedure for SMD

installation.
 Regards,

Yuksel AKCINAR

Ning Tong

June 21, 2016 at 12:19 pm

Hi Yuksel,

Nice document, it helps me to configure SLM 7.2.

Regards,

Ning

Andrey Ivanov

June 22, 2016 at 2:35 pm

Hello Yuksel!

I install Solution Manager 7.2 ABAP (SM4 with 00 and 01) and Solution
Manager 7.2 ABAP (SM5 with 02 and 03) like your steps from previous section I –
Installations

But now try to do tx SOLMAN_SETUP on my GUI and when open browser I

see error:

What need install and setup on ABAP stack to run this function?
 Yuksel AKCINAR Post author

June 23, 2016 at 5:55 am

Hello Andrey,

Check the note 1451753 – Filtering administration requests for

AS Java.

I could answer your questions but it is better to open discussion to

SAP Solution Manager space. Many people can see your question
there.

Regards,

Yuksel AKCINAR

Andrey Ivanov

June 23, 2016 at 8:51 am

I open new disscution Solman_setup not work on

ABAP stack

Hernan Henriquez

July 21, 2016 at 3:07 am

Is EEM (End User Expirience Monitoring) featureavailable in Solman 7.2?

Yuksel AKCINAR Post author

July 21, 2016 at 8:34 am

Hello Hernan,
 I am not sure about EEM.

Can you check roadmap document for SM 7.2?

And also you can open a discussion on Solution Manager area for
getting help from other scn guys.

Regards,

Yuksel AKCINAR

Tom Cenens

August 22, 2016 at 7:19 am

Hi Herman,

Yes

Best regards

Tom

Welvis Douglas Moretto

August 5, 2016 at 2:33 am

Hi Yuksel AKCINAR,

I’m using your blog to install a solman 7.2. In solman_setup ->

infraestructure Prep. in step 1.1 but I receved the message and a do not to next
step: :

SLD connection test fails

Error in processing of HTTP request: (110)HTTPIO_PLG_CANCELED

Yuksel AKCINAR Post author

August 5, 2016 at 3:16 am

Hello Douglas,

Can you check 1822831 – Web Service Soap Errors in solman_setup?

And also you can open a discussion on Solution Manager area for getting
help from other scn guys.

Regards,

Yuksel AKCINAR

Hauke Ihnen

November 16, 2016 at 12:21 pm

Hi,
you need to add a HTTP service to ICM (smicm->services for
 temp, default profile for permanent), seems like connecting from
https to http isn’t possible.

By default there is only HTTPS and SMTP after install.

Welvis Douglas Moretto

August 5, 2016 at 1:56 pm

Hi Yuksel AKCINAR

I set http port and now are ok the connection.

Can you say who ports http/https in solman 7.2?

regards,

Welvis Moretto

Yuksel AKCINAR Post author

August 5, 2016 at 2:03 pm

Hello Welvis,

I could not get your question.

If you are asking about which port http or https, it changes

according to your choice.

You can use either of them. As you know https is more secure.

Regards,

Yuksel AKCINAR

Tom Van den Broeck

August 10, 2016 at 9:13 am

Nice blog Yuksel !

Gagandeep Singh

August 18, 2016 at 10:49 am

Nice blog Yuksel, We are facing issue configuring Introscope EM.. Both EM &
solman 7.2 are on same host. DA Agent discover the same and showing green
but after few minutes it becomes red, & in error log “enterprise manager :6001
is offline” & in backend EM is up & running.. can you help me to find out the
issue in it… Regards, Gagandeep Singh

Yuksel AKCINAR Post author

August 18, 2016 at 11:12 am

Hello Gagandeep,

I had the same issue with SM 7.1 and EM 9.7. It didnot run and I
reinstalled EM 9.5 successfully.

What is the version of your EM?

Regards,

Yuksel AKCINAR

Gagandeep Singh

August 19, 2016 at 3:34 am

But we are testing the same on SM 7.2, LM-Services

are on 1000.7.20.1.0.2015093012000… In
Compatibility LM-Service 10.7.20.1 is compatible with
EM 9.7.. Regards, Gagandeep
 Yuksel AKCINAR Post author

August 19, 2016 at 12:24 pm

Hello Gagandeep,

My case was the same with SM 7.1. EM 9.7

was compatible with my LM SERVICE version.

But unfortunately I was getting the error you

get. hostname:6001 is offline.

You can see the details on blog Which one is

bigger 9.7.1 or 9.5.6?

Regards,

Yuksel AKCINAR

Gagandeep Singh

August 21, 2016 at 7:29 am

Thanks Yuksel.. Thanks for

the reply..

Nizar Fanany

September 6, 2016 at 7:25 am

Nice Blog Yuksel, very helpful…

rafael salazar

October 13, 2016 at 8:54 pm

Hi Yuksel,
I install Solution Manager 7.2 ABAP SP3 like your steps from previous section
II – Installations

But now try to do tx SOLMAN_SETUP on my GUI and when open browser I

see error in the step Define HTTP Connectivity

Error

In the st22 trx I see error

Error analysis
An exception has occurred which is explained in more detail below. The
exception, which is assigned to class ‘CX_WD_CONTEXT’ was not caught and
therefore caused a runtime error. The reason for the exception is:
Invalid index 1 when setting lead selection; context node:
V_WEB_DISPATCHER.1.ABAP_INTERNAL_ICM
Regards,
Rafael

Agus Widjaja

November 10, 2016 at 8:05 am

Hi Rafael,

could you has been solved your issue?

I’m getting same error.

Thanks
Agus

rafael salazar

January 17, 2017 at 8:45 pm

Hi Agus,

Please you delete the ítem SAP Netweaver 7.4 and delete SLD of the stack
java and créate el LMDB of the stack java
Regars,
Rafael

Klaus Paschke

February 1, 2017 at 8:43 am

Hello

You wrote:

Register new S-User in SAP’s PI System : You create a technical user on SMP
according to the notes “2174416 – Technical User for Data Transfer with SAP
Backbone System and 2174416 – Technical User for Data Transfer with SAP
Backbone System”

The same note mentioned twice…

Daniel basis

June 2, 2017 at 3:31 pm

Hi Yuksel,

Can we schedule the jobs directly from SOLMAN_SETUP with user

SOLMAN_ADMIN?
(or) Below should be followed.

Requirements

You have created a user to schedule jobs for background processing. For more
information, see USER_SOLMAN_BTC.

Thanks in advance

Yuksel AKCINAR Post author

June 3, 2017 at 12:25 pm

Hello Daniel,

Use SOLMAN_ADMIN user to run SOLMAN_SETUP.

Follow the instructions and it will schedule jobs.

You donot need to do any manual schedule.

Regards,

Yuksel AKCINAR

Daniel basis

June 9, 2017 at 4:42 am

Hi Yuksel.

Good work..Much appreciated !

Could you please upload Business process monitoring document also. It could
be a great help to everybody.

Warm regards…..
Sigit Ari Wibowo

June 21, 2017 at 4:31 am

Hello Yuksel,

Is CA Introscope mandatory for Solman 7.2?

Thank you

Uday Bhaskar Raghupatula

July 19, 2017 at 2:13 am

Hi Sigit Ari Wibowo,

I don’t think it is mandatory, it is required if you want to

see/analyze in far better way.

Thanks,

Uday.

Harini Nittala

August 8, 2017 at 7:30 am

Hi Yuksel,

I am doing Infrastructure preparation for first time. Just want to check what is
runtime SLD ? is it compulsory to add runtime SLD or source for LMDB is
sufficient? and what is the difference between PI and runtime SLD?
 Yuksel AKCINAR Post author

August 8, 2017 at 7:42 am

Hello Harini,

source for LMDB is sufficient.

The aim is to provide systems’s data to LMDB.

Regards,

Yuksel AKCINAR

Jurij Moisejenko

November 9, 2017 at 10:11 am

Hi Yuksel,

we can’t access:

Part 3: Solution Manager 7.2 – Installation and Configuration – III – Changes

from 7.1 to 7.2

Part 4: Solution Manager 7.2 – Installation and Configuration – IV – Managed

System Config – General Info

Jan-Niklaas Linhart

November 27, 2017 at 10:39 am

Part 1
Part 2

Part 3 (missing)

Part 4

Part 5

Part 6

Part 7

Part 8

@YukselAkcinar Thanks for sharing!

Daniel basis

December 11, 2017 at 5:21 am

Hi Yuksel,

I have one query on defining SLD roles.

I have configured local SLD on the solution manager 7.2 and performed role
mapping as well.But there is no plan to use the Local SLD for solution
manager.

In this case, Can I use the PI system central SLD for runtime SLD and source
for LMDB roles and set up connections?.

if the central SLD is down for maintenance, except LMDB other functionalities
of solution manager can work with local SLD though its not configured
anywhere?

Please clarify.

Thanks in advance.
 Yuksel AKCINAR Post author

December 11, 2017 at 5:42 am

Hello Daniel,

Below document explains SLD in detail. And it has the answer of

your question in the below given section. You can use you PI
system’s SLD as source of LMDB.

Please go through teh document. It is very informative.

https://www.sap.com/documents/2015/07/7e559111-537c-0010-
82c7-eda71af511fa.html

3.4.2 Recommendations: SLD and SAP Solution Manager 7.1

Regards,

Yuksel AKCINAR

Daniel basis

December 11, 2017 at 6:48 am

Hi Yuksel,

What about runtime SLD..Can it assign it to the PI

system central SLD?

Thanks in advance

Daniel basis

December 11, 2017 at 5:54 am

Hi Yuksel,

There are so many details on the document.

Could you please answer my first question alone.

I have configured local SLD on the solution manager 7.2 and performed role
mapping as well.But there is no plan to use the Local SLD for solution
manager.

In this case, Can I use the PI system central SLD for runtime SLD and
source for LMDB roles and set up connections?.

Thanks in advance

Yuksel AKCINAR Post author

December 11, 2017 at 6:54 am

Hello Daniel,

I have never used any other SLD for source of LMDB but as I
understood from the document you can use PI system’s SLD as
source of LMDB.

AFAIK, SAP recommends to use one central SLD. It could be PIs,

too. (Unfortunately, I cannot give the related link)

Regards,

Yuksel AKCINAR

Daniel basis

December 11, 2017 at 6:43 am

Hi Yuksel,
 My next question is on defining system role.

if the solution manager system role is defined as “production system” in

SOLMAN_SETUP.
Will it allow to perform all the config activities manually without looking for
transport request from development system.? (or) would it still look a transport
request from development system?

Can it be defined at the end of all config activities by setting another role and Is
it possible change it any time?..any impacts?

Thanks in advance

Yuksel AKCINAR Post author

December 11, 2017 at 6:58 am

Hello Daniel,

I have no experience about, this.

You can open an incident on Solution Manager area. There could

be more experienced guys.

Regards,

Yuksel AKCINAR

Share & Follow

Privacy Terms of Use Legal Disclosure Copyright Trademark Sitemap Newsletter