[#solman] - Solution Manager - Diagnostic/verification for Managed Infrastructure

[Lluis]

Update:   System landscape from a great wiki page by Michael Kloeffer,

I'm working on a set of documents for help us on Solution Manager implementation and management, trying to reduce the implementation time of that system and connection problems. My first post is a collection of a lot of text files with usually users, rfc connection and a little description to understand how work each user and RFC within Solution Manager system and others components for solman landscape, managed systems, diagnostics, etc...

The document is not extended, because y try to simplify on a single table to simplified the information and allow to find the solution for usually connection problems in solution manager, i will update as i get the information.

Index:

Connections	Diagnostics Agents	Authorizations	BI/BW	CRM
own jobs	Central Correction Note	Saprouter	Services SICF	SLD/LMDB
Solution Manager	SP Components status	Communication ports	java stack	System LandScape
VAR

Solman Experts Useful Content:

prakhar_saxena -> Upgrade Roadmap -> link

Connection Checks:

Managed Landscape Side	User	RFC	Description
SAP support backbone	S000…	SAPOSS	That connection is created from OSS1 transaction setup
	S000…	SAP-OSS	Connection is created as a copy from SAPOSS from solman_setup wizard
	S000…	SAP-OSS-LIST-O01	that connection is created as a copy from saposs from solman_setup/itsm or dswp old transaction
	S000…	SDCC_OSS	that remote connection if manager from sdccn transaction and is a copy from SAPOSS
Solution Manager ABAP	SM_SMP	SM_<SM-SID>CLNT<CLNT>_BACK	Connection to send information from solution to own solution manager, it's usually changes for NONE rfc connection on Solution manager but you can use that name definition
		SM_<SM-SID>CLNT<CLNT>_TRUSTED	That connection is used to access to each managed system within a trusted connection that no't required any user or password, that connection us used to access remotely to sdccn, user management, transport routes, etc… from solution manager
	SM_STMS	SM_<SM-SID>CLNT<CLNT>_TNMW	for solution manager remote transport management options and cange managements / charm functionality
	SEP_WEBSRV	SM_<SM-SID>CLNT<CLNT>_READ	solution manager read information from each managed system with that rfc
	SOLMAN_BTC	SM_<SM-SID>CLNT<CLNT>_LOGIN	an useless connection that ask you user and password for access to managed system, if you can don't use it
	CONTENTSERV		user for access to solution manager content server, no connection needed if CS is on same system
	SMD_RFC	soa manager	access for some web service that are required for solution manager, as diagnostic setup, etc…
Solution Manager Java	SM_INTERN_WS	soa manager	internal web service options from solution manager access
	SMD_ADMIN	soa manager	internal web service options from solution manager access
Soution manager Diagnostic Agent	OS user	-	user that run diagnostic on solution manager server
Willy  EnterpriseManager	GUEST	port 6001	for view  access, solution manager don't use that user or connection is only for administrators / operators
	ADMIN	port 6001	for admin access, solution manager don't use that user or connection is only for administrators / operators
Managed system - ABAP	SM_PRD	SM_SMP PRD_<CLNT><CLNT>_BACK	managed system send sdccn information to solution manager for ewa processing trugh that remote connection
	SMTMSMP	SM_<SM-SID>CLNT<CLNT>_TNMW	for solution manager remote transport management options
Managed System - Java	SM_PRD	port p4 and message server	admin user for java part on managed system
Diagnostic Agent	OS user	p4 port / saprouter	user that run diagnostic on managed systems
SAP Host Agent	OS user	local connection	local OS user
SAPOSCOL	OS user	local connection	local OS user

Additional information:

• Check SSO connection trough sap note 1121248 and http://service.sap.com/security
• Check ports as indicated on guided "Performing end-to-end root cause Analysis using Sap Solution Manager", pag.72
• ADS connection information can be found on sap note 944221
• MDX parser does not start; check note 944221
• Check ICM connection parameters trough sap note 737625

Index:

Index:

Connections	Diagnostics Agents	Authorizations	BI/BW	CRM
own jobs	Central Correction Note	Saprouter	Services SICF	SLD/LMDB
Solution Manager	SP Components status	Communication ports	java stack	System LandScape
VAR

Hope that table can help you when found any communication problems inside your system landscape within solution manager.

Best Regards,

Luis