Managed System Configuration: SSO setup failed for Solution Manager 7.1 sp11

Hi Folks,
While doing Managed System Configuration for Soman system i am getting error in SSO Setup
Currently I am in
8. Configure Automatically :Single Sign On Setup
This is i am going for managed System (Solution Manager System Itself)
Below is error log..
SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
Screen shot attached.
Found SID for SSO ACL entry : SMP
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
The SSO ticket Certificate <OU=J2EE,CN=SMP> has been successfully imported into ticket Keystore
SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
The SSO ticket Certificate <CN=SMP> has been successfully imported into ticket Keystore
SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Exception
java.rmi.RemoteException: Caller not authorized.; nested exception is:
java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:160)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
at com.sap.engine.services.security.exceptions.BaseSecurityException.writeReplace(BaseSecurityException.java:349)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:910)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1024)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1344)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1316)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1260)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1065)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:282)
at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:147)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:338)
... 8 more
Regards,
San

Hi Sandeep,
It seems authorization issue. Please check the below SAP Note :
1988642 - Warning 'caller not authorized' in Step 'Single Sign On Setup'
Hope this helps.
Thanks & Regards,
Nisha

Similar Messages

Setup BPC for Solution Manager

Hi expert
I need to setup at configuration (SOLAR02) in order to do the BPC configuration via Solution Manager (SOLAR02). Anybody cna give the steps to setup BPC into SOLAR02.
Thanks a lot

Hi David,
In addition to aboce reference i would like to inform that you need to install Diagnostic Agent on all servers whereever interface for web and application servers are installed. The installation files are available in service market place. Please refer to the installation file for detailed procedure.
Hope this helps.
Regards,
Poonam

Wily Introscope Version for Solution Manager 7 SPS 17

Hi
We have a solution manager 4 (now 7) running on an ABAP stack only, this was recently upgraded from Solution Manager 3.2 which was installed 3 years ago as ABAP stack only, this server was never powerful enough to have the Java stack added and the project did not require it.
I am now looking to migrate this ABAP Solution Manager 7 to a new server, using ABAP & JAVA so I can make use of Solution Managaer tools like Diagnostics, RCA, WILY etc.
On a sandpit copy I have migrated the ABAP instance to a more powerful server and added the Java Instance from the Solution Manager 4 Installation Master, so I now have a dual stack SM 4, I have patched this to SP17.
I am looking to install Wily Introscope for monitoring, I have read Note 797147 - Wily Introscope Installation for SAP Customers, where it says you should always use the latest version of Wily, which is 8.0.2, but looking at the note, the downloads for Introscope Enterprise Manager and Introscope Workstation are from SAP SOLUTION MANAGER 7.0 EHP 1, but I am not running Solution Manager on EHP1, I am on SP Stack 17.
Looking in the SWDC there are downloads in SAP SOLUTION MANAGER 7.0 -> Entry by Component -> Solution Manager JAVA Stack -> WILY INTROSCOPE ENTPR MGR 8
Is this what I should be using for my SP Stack 17, or should I use the EHP1 version?
Also, setting up the Solution Manager Diagnostics, is there a setup PDF for Solution Manager 7 SP17 ? I cannot find a setup guide for this release, most are for EHP1, I would rather not have to implement EHP1 as part of this migration !
Thanks for any help.
Paul.

Hi Bhudev
Thanks for the reply, I presumed it was the Wily introscope 8 without the EHP1 I required.
As for installation guide, I have think you have misunderstood my question, I already have the wily installation guide from the note location, I wanted to know if there is any Solution Manager Diagnostics setup guides for SP17 ?
When I use transaction SOLMAN_WORKCENNTER --> System Monitoring --> Solution Manager Diagnostics --> Diagnostics System --> Diagnostics Setup --> Setup Wizard
the first 2 (of 23) setups are failing :
SSO The value of profile parameter login/accept_sso2_ticket could not be checked
BI Cannot invoke CCMSBISETUP on host localhost
Warning :
User(BI) Role SAP_BI_E2E does not exist
Then it says :
To complete the Diagnostics Setup, you should perform the following operations as documented in Diagnostics Setup Guide
I cannot find this Diagnostics Setup Guide for SP17 ?
The installation guides are mainly for EHP1, media library under sap-ag.de/diagnostics does not show this setup guide, Master Installation guide does not mention it, so was wondering if anyone could point me in the right direction for this guide ?
Thanks,
Paul.

Managed System configuration for SAP NW Java system in Solution Manager 7.1 SP10

Hi All,
I am doing Managed system configuration for my SAP NW 7.01 Java system and getting below error in step 6 create users SAPSUPPORT & SM_COLL_SID.
"An unexpected error occured. An error occured while processing the UME command READ_USER from agent <hostname> : Server returned: 302 Found "
I have checked my DAA as well as host agents are up and running fine. My Solution Manager is 7.1SP10.
Please suggest.
Regards,
Manish

Manish,
Which UME you are using? portal/ABAP/LDAP
Are you using the SOLMAN_ADMIN user while configuring.
Also check the below forum.
https://scn.sap.com/thread/1167282
Regards,
Raja. G

Managed system Configuration Diagnostics Prerequisites check fail

Dear All,
My solman_setup initial configuration part and basic configuration part all passed without error. And when I do the managed system configuration part , first I choose the solution manager itself and the client 001 to config , and then the maintain connection passed OK , but in the next step , check Prerequisites, it fails. The Navigation Button just open a link to the SAP Service Market Place, and the IMG documentation just let me to see the note 1010428. The deatl part of the execuation result of the Prerequisites open a page but with error statement as below :
Service cannot be reached
What has happened?
URL https://sapsolmgr.centurydsp.com:8000/webdynpro/dispatcher/sap.com/tcsmdnavigation/StandaloneApp call was terminated because the corresponding service is not available.
Note
The termination occurred in system SM2 with error code 404 and for the reason Not found.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-https-c:000-u:SAPSYS-l:E-i:SAPSOLMGR_SM2_00-v:0-s:404-r:Notfound
HTTP 404 - Not found
Your SAP Internet Communication Framework Team
Any comment will be appreciated.
Enddy.

Hello Enddy,
This sounds as if you have yet to configure the HTTP services in SPRO or have misconfigured them. Please review your configuration for the HTTP Services as it should resolve your issue.
Please review the diagnostics URL to see if it helps you out:
http://service.sap.com/diagnostics
Also, please review the following SAP Notes which will also guide you through diagnostics and solution manager setup/installation:
1010428 End-to-End Diagnostics
1145779 SAP Solution Manager 7.0 Installation
1163836 Solution Manager Diagnostics required for troubleshooting
Also pay attention to the relevant notes listed on the bottom of these. If you follow these documents, I'm sure you will have your issue resolved.
Hope this helps you out!
Thanks,
Mark

Managed system configuration step 8: No Admin User Id provided for TS SID

Hello experts,
I face the following problem in step 8 of managed system configuration (Configure automatically, SolMan 7.1 SPS 3):
All Activities fail (except Activate services) with the following Details message:
No Admin User Id provided for TS <SID> (ABAP)
Any hint?
Thanks and best regards, Basti

Hi Sunny,
I don't find anything where I can provide the user information. It just uses the actual user (SOLMAN_ADMIN). Can you tell me where to provide the user for this step?
Managed system configuration -> step 8 Configure automatically -> SSO Setup
Thank you, Basti

How to configure CTS+ for Solution Manager for XI 3.0

Hi ,
We are working on XI 3.0 SP 20 and Doing a file system based transport of .TPZ files. We observed that there is a possibilit of misssing the objects while tranporting. So we are planning to set CTS+ with our Solution Manager.
Question:
1. Can we configure CTS+ through the latest version of Solution Manager for XI 3.0 landscape?
If Yes .. How? If No... Why?
2. Is there any way to make the the transport automated like ABAP tranports.
If there is.... Please send the link or documents..
Thanks
Manoj

Hi Venkat,
Thank you for the Demo. The Demo gives me information about the CTS+ setup. I am looking for the compatability of CTS+ for XI 3.0.
We have Solution Manager 7.1 setup in place.
Please let us know if we can setup CTS+ on solution Manager (7.01 EHP1) and use it to transport XI 3.0 SP20 IR/ID objects across the XI landscape.
Regards,
Manoj

SQL Error 0 during DBACockpit setup in Managed System Configuration

Hi All,
I'm getting SQL Error 0 during DBA Cockpit setup in Managed system configuration. I'm trying to connect MsSQL 2005 from Linux system(Solution Manager 7.1 SP10). I have installed necessary ODBC and microsoft drivers. Any suggestions will be appreciated.
Regards,
Pragadees

If I've understood you correctly, you are trying to setup a remote database connection from an SAP Solution Manager system running on Linux with a database which is NOT MSSQL to a database which is MSSQL running on Windows.
In that case have you checked these SAP notes ?
1265134 - DBA Cockpit: Connecting a remote database
1388700 - SolMan 7.0 EHP1 Database Warehouse for MSSQL
Regards
RB

Managed System Configuration Error for MDM 7.1 SP09

Greetings, Needed your expert advise. We are getting an error while configuring our MDM Servers (Version 7.1.08.196) in Solution Manager. As suggested in SAP Note 1798643 , I have manually filled the required details and transferred through sldreg.exe to SLD. Now when i try to perform Managed System Configuration, it is throwing the below error. The definition of Technical System '~MDM' is not correct: '~MDM': No Path found in Installed Technical System 'SID~MDM~'. I'm not sure how to manually update the Install Path for our MDM Servers. Since, the data to LMDB is automatically supplied, I might not be able to manually edit anything. Could you please advise if there is any step to solve this issue. Thanks, Haseeb Ahmed.

Dear ,
Haseeb,
I had the exact same problem with MDM managed system setup . I was on MDM 7.1 SP10.
1940337 - RCA template for Solution Manager 7.10 SP10
This note should resolve your problem. This note has the updated template for MDM.
It did for mine
Thanks
Amit

Change Request Managment setup for Solution Manager 4.0

Hi guys! Can someone help me on how to setup the Change Request Management in Solution Manager 4.0? I have already have checked the SAP Marketplace for any documentation about this topic but found none. I am configuring the two test servers (1 prod and 1 dev) in tcode SMSY. I have also configured the system role for each server. When I try executing /TMWFLOW/CMSCONF in SE38, no clients appear in the CRITICAL OBJECTS pane. Did I miss a required step in the implementation? I hope you guys can help me. Thanks in advance...
Regards,
Ronald Navarro

Hello Ronald,
Following the spro configuration will setup the Change Request Management scenario, each spro point has associated the corresponding documentation.
Also in service.sap.com/rkt-solman>solman 4.0>CCC profile you will find valuable information about how to use this scenario.
Hope this helps,
Dolores

Service desk configuration for solution manager

hi this ,
sudheer i have configured the service desk configuration on my solution manager system with all satellite system, i have mapped all business partners in my satellite systems to solution manager , and also iam able to see all messages are send by business partners using DSWP transaction, but how to see reply from solution manager sytem to satellite system ( message inbox of satellite system)
can any body tell the configuration of satellite system to see reply message from solution manager ?
thanks and regards
sudheerkoppala@ g ma il .com

>
sudheer koppala wrote:
> sudheer i have configured the service desk configuration on my solution manager system with all satellite system, i have mapped all business partners in my satellite systems to solution manager , and also iam able to see all messages are send by business partners using DSWP transaction, but how to see reply from solution manager sytem to satellite system ( message inbox of satellite system)
> can any body tell the configuration of satellite system to see reply message from solution manager ?
There is no "message inbox" in satellite systems, but you can use the SAP Solution Manager to have a central access to all reported messages.
Configure Work Center "Incident Management" in SAP Solution Manager and grant access for message reporters.
See answers to similar question in accessing the service desk message from satellite system
Best regards,
Ruediger

Understanding and using Logical Components for Managed System configuration

Experts.....
I am embarking on a fresh installation of SolMan 7 EhP1 SPS25 and after a few bugs along the way, I am finally nearing the end of including the first Managed System. Somewhat related to {forum:id=10293771] I am hoping I can get some advice, but specifically with regards to Logical Components.
General question - I have a slide from SAP that shows a picture from Product->System->Instance->Logical System (client)->Logical Component. I am confused because it shows that Client 100 of a given ABAP system could be assigned to Logical Component A, whereas Client 200 of the same system could be assigned to Logical Component B. This seems wrong to me?
I am at the last step of the managed systems configuration wizard : "create logical components" and only want to ensure that I set things up to hopefully ensure that later usages (Maintenance Optimizer, etc) will handle things correctly!!!
- Our SAP landscape is not very complex
1. only ERP and EP (Dev/Test/Prod).
2. We are utilizing HR Self Service (XSS).
3. The ERP ABAP systems are on Netweaver 7.01.
4. EhP4 has been installed, however we only activated the HCM business functions. Therefore SAP_HR is on 604 whereas SAP_APPL is on 600. I think this might be driving some of the confusion in SMSY
For the DEV ABAP system I am trying to configure:
1. The system is showing up in two products : "SAP ERP" and "SAP ERP Enhancement Package" with the header data for both showing "EHP4 FOR SAP ERP 6.0 / NW7.01" and "SAP ERP 6.0"
2. Under "SAP ERP" the "product instance selection" shows only "SAP NW - Adobe Docu. Service" and "SAP ECC Server" as relevant
3. Under ""SAP ERP Enhancement Package" the "product instance selection" shows only "Human Capital Mgmt" as relevant by default. I manually flagged the development portal system as "relevant" for "SAP XSS (Self Services)"
4. The RCA DBA Cockpit system is complaining "No data available for extractor activation. Please check product mapping and Software Components in SMSY"
5. In the Managed System wizard, there is no logical component for any of the "EHP4 FOR SAP ERP 6.0 / NW7.01" selections
From what I can tell, I think this is correct:
1. Create a Z_EHP4 logical component and assign the DEV/QAS/PRD systems to them
2. Also assign the DEV/QAS/PRD to the existing SAP logical component "SAP ERP ECC SERVER"???
3. For the Solutions, my plan is to create
a. Non-Production ERP : with the dev/test erp/ep systems, but test system as the leading system
b. Production ERP with the prod erp/ep systems only
Thanks for any advice/guidance to help me avoid future problems!!
Edited by: Eric Poellinger on Jun 15, 2011 6:32 PM

General question - I have a slide from SAP that shows a picture from Product->System->Instance->Logical System (client)->Logical Component. I am confused because it shows that Client 100 of a given ABAP system could be assigned to Logical Component A, whereas Client 200 of the same system could be assigned to Logical Component B. This seems wrong to me?
Client 100 could be assigned to any number of logical components, client 200 could be assigned to those same ones or none of them. A logical component is just a grouping of systems used to accomplish some task in SolMan.
For example with ChaRM you could have 2 logical components.
ZCHARM_DEV development (100) -> QA (200) -> prod (300)
ZCHARM_SEC security (900) -> QA (200) -> prod(300)
One is used to show the path for moving development changes to prod, the other for security changes. 200 belongs to both, but 100 only to one.
Set them up in whatever way meets you needs. It looks like for you, you could just use the default one and assign your clients to the various system roles. Not all functionality in SolMan uses the logical components though.

System registered in SLD invisible in solution manager configuration

Hi
I have installed Solution Manager EHP1 / Oracle 10g / Win2003 on a VM. I ran into a issue in the Managed system configuration. The first step in the maanaged system configuration would help us select the satelllite systems which and configured in the SLD. Since systems were not yet added to SLD just the solution manager system shows up.
Here is the problem
I have added one system to the SLD using "Add Technical system" from http://localhost:50000/sld. This is a ABAP sysystem. The addition went through successfully however this does not reflect when I check the same in solution manager configuration "Managed system configuration"
As per the guide in the same page, I have checked on "Maintain Technical systems" Here too when I search for the system I created in SLD , I am not able to find it. Is there another way of manually maintaining the system in the SLD?
Any ideas as to why this might happen? Does one have to bounce the instance after adding systems to SLD/.... just wondering?
Ideas?
thanks
Ravi

Hi Rajeev
Thanks for your response however I fixed it. It looks like I had incorrectly mentioned the host in RZ70. Instead of mentioning the hostname of the solution manager I had mentioned the host name of the satellite system
The below link helped me fix the issue
http://help.sap.com/saphelp_nwpi71/helpdata/en/e7/01503ede925441e10000000a114084/content.htm
thanks
ravi

MAnaged system configuration error in solution manager

Hi,
While doing managed system configuration getting the error, below versions are using.
MDM 7.1 SP10 Import server and Solution manager 7.1 SP10.
Can anyone help me?.
Regards
Chandra

Two cases you have
1) Satellite system
Re-install The DIA agent and give correct (port numbers )SLD details
Once you re-install the DIA agent, run Rz70 from satellite system
data will pull from satellite system to central SLD.
2)Run SLD check from Solman system , check its successful or not
Go to LMDB and check satellite system
After re-Synchronize technical system from SLD
Thanks ,
Rahul yedapally

System refresh for solution manager

Hi All,
Do you think its possible to do a system refresh for solution manager?
Even though we do, wont there be a lot of inconsistencies between satellite system and with new solution manager?
Ideally i need do system refresh of X solution manager to Y solution manager
Thanks
Gopal

Hi,
How about the consistency between your two X and Y systems. Are they in single TMS. Requests properly transported from X to Y? If its positive, then go ahead you can make System Refresh..
Feel free to revert back.
--Ragu

Managed System Configuration: SSO setup failed for Solution Manager 7.1 sp11

Similar Messages

Maybe you are looking for