System not displying in graphical view in solution manager

Hello,
I added 10 system in solution manager for centralize monitoring but 8 of them are displaying in graphical views another 2 system are not displaying . all the systems adding procedure is same. but still 2 of them not displaying in graphical view can anyone tell me the chouses of this type of error .
Kindly guide me to short out this issue
Thank you
Deepak

Hi,
Open your Solution of the affected systems (12 Systems not appearing in your Monitoring). Go to Solution Landscape Maintenance (Under Solution Landscape).
Compare the Leading role of the solution with the role of the system in the logical component.
If these are different, right click on the system and select Put in Solution.
Hope this helps.
Feel free to revert back.
-=-Ragu

Similar Messages

System out of memory when exporting/migrating Solution Manager

Dear all,
since we decided to migrate our Solution Manager (win2003/sql server 2005) system to a more appropriate server, we started an export using the NW70sr2 installation master CD, the one we used to install this solution manager instance.
Everything went ok up to the Java export phase, here we caught an out of memory issue, here's the relevant part of the sapinst.dev.log file:
May 24, 2008 1:49:46 PM com.sap.inst.jload.Jload dbExport
SEVERE: DB Error during export of BC_SLD_CHANGELOG
May 24, 2008 1:49:46 PM com.sap.inst.jload.Jload printSQLException
SEVERE: Message: The system is out of memory. Use server side cursors for large result sets:null. Result set size:262,182,182. JVM total memory size:518,979,584.
May 24, 2008 1:49:46 PM com.sap.inst.jload.Jload printSQLException
SEVERE: SQLState: null
May 24, 2008 1:49:46 PM com.sap.inst.jload.Jload printSQLException
SEVERE: ErrorCode: 0
May 24, 2008 1:49:46 PM com.sap.inst.jload.db.DBConnection disconnect
INFO: disconnected
TRACE      [iaxxejsexp.cpp:199]
           EJS_Installer::writeTraceToLogBook()
2008-05-24 13:49:49.755 JavaApplication execution finished
TRACE      [iaxxejsexp.cpp:199]
           EJS_Installer::writeTraceToLogBook()
2008-05-24 13:49:49.755 NWDB._callJLoad(export) done: throwing
TRACE      [iaxxejsexp.cpp:199]
           EJS_Installer::writeTraceToLogBook()
NWException thrown: nw.syscopy.jloadRunFailed:
<html>Execution of JLoad tool 'C:\j2sdk1.4.2_14-x64\bin\java.exe -classpath F:\usr\sap\SMD\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx512m com.sap.engine.offline.OfflineToolStart com.sap.inst.jload.Jload
SMDCA/sapmnt/SMD/SYS/global/security/lib/tools/iaik_jce.jar;
SMDCA/sapmnt/SMD/SYS/global/security/lib/tools/iaik_jsse.jar;
SMDCA/sapmnt/SMD/SYS/global/security/lib/tools/iaik_smime.jar;
SMDCA/sapmnt/SMD/SYS/global/security/lib/tools/iaik_ssl.jar;
SMDCA/sapmnt/SMD/SYS/global/security/lib/tools/w3c_http.jar;F:/usr/sap/SMD/SYS/global/sltools/sharedlib/jload.jar;F:/usr/sap/SMD/SYS/global/sltools/sharedlib/antlr.jar;F:/usr/sap/SMD/SYS/global/sltools/sharedlib/exception.jar;F:/usr/sap/SMD/SYS/global/sltools/sharedlib/jddi.jar;F:/usr/sap/SMD/SYS/global/sltools/sharedlib/logging.jar;F:/usr/sap/SMD/SYS/global/sltools/sharedlib/offlineconfiguration.jar;F:/usr/sap/SMD/SYS/global/sltools/sharedlib/opensqlsta.jar;F:/usr/sap/SMD/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;F:\usr\sap\SMD\DVEBMGS00\exe\mssjdbc\sqljdbc.jar -sec SMD,jdbc/pool/SMD,
SMDCA/sapmnt/SMD/SYS/global/security/data/SecStore.properties,
SMDCA/sapmnt/SMD/SYS/global/security/data/SecStore.key -dataDir E:/EXPORT/JAVA/JDMP -remove_trailing_blanks "C:/Documents and Settings/administrator.ATRSAP/removeTrailingBlanks.txt" -convert_empty_LOBs "C:/Documents and Settings/administrator.ATRSAP/convertEmptyLobs.txt" -convert_empty_strings "C:/Documents and Settings/administrator.ATRSAP/convertEmptyStrings.txt" -convert_empty_binary "C:/Documents and Settings/administrator.ATRSAP/convertEmptyBinary.txt"' aborts with return code 1.<br>SOLUTION: Check 'jload.log' and 'C:/Documents and Settings/administrator.ATRSAP/jload.java.log' for more information.</html>
Actually we used a workaroud to complete the phase, ie we menually re-issued the command and changed the heap value from -Xmx512m to -Xmx1024m
Is there a way to defalut the sapinst to pass to the java export command an higher java heap value, ie -Xmx1024m ?
Thanks in advance and cheers.
Franco.

It sounds like you may have a corrupt render file in your 7th episode. You can set in and out points in 5 minute increments and export those segments to narrow down which clip is the offending clip. Then re-render the offending clip.
I hope this helps.

All the properties are not displying for the View Object

i my one of the view Object it is only showing the properties
Values
Lable
Render values
I want to use text box (Input box )...but it is not showing in the property window
why it is not showing the all the properties for the that view Object.
Is it a read only view object ? if so then how to change it

This question is confusing.
You talk about properties, suggesting attribute properties are not showing up in the view object editor. Then you talk about a read-only view object, which suggests you talk about a running application?
Normally a view object is updatable when it is based on an entity object and when on the entity object tab of the view object editor (the page in which you select the entity object) the updatable checkbox has been checked.
But being updatable as such is not why attributes would not show up in a screen.
Can you be more specific, and also tell us what JDeveloper version you are working with?
Jan Kettenis

Distributed Application group relationships not displaying in health view (VSAE created management pack)

Hi there,
I am working through my first complex Distributed Application which I have been creating using VSAE. I have followed Brian Wren's training, but the result does not match what I am expecting.
I have created a single DA (based on the System.Service class) with four groups (base on System.Group) which will be populated with the core components of the application. Each of the groups (and the DA) is configured as a Public, Non-Abstract, Non-Hosted
Singleton, as per the MPAuthor.Stores example. Each of the four groups is linked via an Internal, Non-Abstract System.Containment relationship to the DA.
When I open the DA diagram view, I only get the DA class visible. Each of the four groups shows in the Groups node in the Operations Console. Based on the experience with importing the MPAuthor.Stores MP, I was not expecting to see the groups in the Groups
node, but linked in the DA diagram node.
I have configured dependency monitors for each of the groups, and these display in the Health Explorer but there is no health rolls up.
The only difference between the MPAuthor.Stores module and mine (that I am aware of) is MPAuthors.Stores is a 2007 R2 MP, and I have created a 2012 MP as I will be deploying to 2012 SP1 and there is no need for backwards compatibility.

Hi Vladimir,
Thanks again for your response. I'm not quite sure what you mean with your last post. My current DA model is:
| Dist App |
| System.Service |
|
| | | |
| Group 1 | | Group 2 | | Group 3 | | Group 4 |
| System.Group | | System.Group | | System.Group | | System.Group |
Where all the groups have discoveries for membership. Are you saying that I need another level of groups below these to house the objects?
I thought that the point of System.Group as a base class was that it did not appear in the console, but gave an automatic health rollup (as per TechNet). Interestingly I am not getting
the automated health rollup for the Groups for their members and it is displaying in the Groups list in the console.
I have also tried creating a new DA with a single group in an 07 MP, and have the same issue. The sample MPAuthor.Stores management pack works as expected.

SDM agent is not registered with SDM server of Solution Manager server

Hi,
We are in process of configuring EWA report for JAVA stack of SAP system along with ABAP stack. For ABAP stack the EWA report generation is straight forward and it is working fine. We are facing the problem while configuring EWA report for JAVA stack. Pls. find below the steps that we have followed and currently where we are stuck,
1) Installation of Willy introscope on Solman server.
2) Define JAVA component for each SAP system in SMSY
3) Installation of SDM Agent on all managed systems
4) Trying to attach SDM Agent to SDM server(solman) with the use of smdsetup.bat (managingconf & sldconf ).still we are getting error in smd agent log file as given below:
===============
Nov 24, 2011 6:16:09 PM [Thread[Connector,5,main]] Info       [p4://xxxx.xxxx.int:8103] Checking server availability...
Nov 24, 2011 6:16:39 PM [Thread[Connector,5,main]] Error      Failed to connect to SMD server - user: SMD_ADMIN
Nov 24, 2011 6:16:39 PM [Thread[Connector,5,main]] Warning    Connecting to SMD server p4://xxx.xxx..int:8103 failed - error counter: 0 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances
*     Nested exceptions are:*
*     com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: xx.xx.xx.xx and port: 8103*=================
5) The solman_setup t-code execution is successful in Solman server.
6) Trying to configure Technical system for JAVA system type through solman_setup : At this time we are getting another error as shown below:
========
The Managed System does not fulfil the Diagnostics prerequisites
Software with prerequisite are incorrect: Found SAP J2EE ENGINE 7.00 with sp level 0, minimum sp level required is 9: Please install or upgrade the required software component.========
I have gone through the SAP note: 1274287 : My solman system is already on the required patch level for LMservice and St 400 SP. Also, the managing systems Java patch level is more then sp06 which is minimum level required.
I need your help to know, why i am getting this SAP J2EE ENGINE 7.00 patch level error although my Java stack is up to date with the required patches.
Waiting for your reply friends.
Regards,

Hi,
please let us know your solman version.
check and apply the sap note
[Note 1277258 - Diagnostics prerequisite check failure|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1277258]
Thanks,
Jansi

Authentication did not succeed in Visual Admin On solution manager?

Hello friends,
   We are unable to log in in visual admin with j2ee_admin default connection. while log in we receiving authentication did not succeed error.
Please help me to solve this issue.
Regards,
Farkath C

Hello Friends,
   Still we are unable to login to visual admin using J2ee_admin user,
Please find the Security log,
If you find any idea to resolve this issue, Please help me.
#1.5 #001EC94523270053000001170000199000050333FB9C3FF5#1410896683295#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SLDDSUSER#895##E7B8C5FD3DD911E4AF340000002B7B0E#e7b8c5fd3dd911e4af340000002b7b0e-0#e7b8c5fd3dd911e4af340000002b7b0e#SAPEngine_Application_Thread[impl:3]_23##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SLDDSUSER
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module                                                               Flag        Initialize Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT ok          false      false
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true
3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true
Central Checks                                                                                                true                  #
#1.5 #001EC9452327004C0000011F0000199000050333FB9E05C9#1410896683405#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SLDDSUSER#896##E7C9690F3DD911E481880000002B7B0E#e7c9690f3dd911e481880000002b7b0e-0#e7c9690f3dd911e481880000002b7b0e#SAPEngine_Application_Thread[impl:3]_29##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SLDDSUSER
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module                                                               Flag        Initialize Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT ok          false      false
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true
3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true
Central Checks                                                                                                true                  #
#1.5 #001EC9452327004B000000EE000019900005033406875E27#1410896866503#/System/Security/Usermanagement##com.sap.security.core.persistence#J2EE_GUEST#0##54E022B53DDA11E48F670000002B7B0E#54e022b53dda11e48f670000002b7b0e-0#54e022b53dda11e48f670000002b7b0e#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.security.core.persistence#Java#User "{0}" is the communication user for the connection between User Management Engine and the ABAP backend system {1}. This user cannot log-on to the User Management Engine.##User "{0}" is the communication user for the connection between User Management Engine and the ABAP backend system {1}. This user cannot log-on to the User Management Engine.#2#J2EE_ADMIN#SLMCLNT100#
#1.5 #001EC9452327004B000000EF00001990000503340687960E#1410896866518#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#J2EE_GUEST#0##54E022B53DDA11E48F670000002B7B0E#54e022b53dda11e48f670000002b7b0e-0#54e022b53dda11e48f670000002b7b0e#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
User: N/A
Authentication Stack: SAP-J2EE-Engine
Login Module                                                               Flag        Initialize Login      Commit     Abort      Details
1. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   SUFFICIENT ok          exception             true       Authentication did not succeed.#
#1.5 #001EC9452327004B000000F4000019900005033412BB19D3#1410897071292#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SOLMAN_ADMIN#910##CEF7CEF83DDA11E498040000002B7B0E#cef7cef83dda11e498040000002b7b0e-0#cef7cef83dda11e498040000002b7b0e#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SOLMAN_ADMIN
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module                                                               Flag        Initialize Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT ok          false      false
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true
3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true
Central Checks                                                                                                true                  #
#1.5 #001EC9452327005700000144000019900005033412BBC3C3#1410897071339#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SOLMAN_ADMIN#911##CF03B6AC3DDA11E4A9C90000002B7B0E#cf03b6ac3dda11e4a9c90000002b7b0e-0#cf03b6ac3dda11e4a9c90000002b7b0e#SAPEngine_Application_Thread[impl:3]_34##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SOLMAN_ADMIN
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module                                                               Flag        Initialize Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT ok          false      false
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true
3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true
Central Checks                                                                                                true                  #
#1.5 #001EC9452327008900000005000019900005033417E870E1#1410897158131#/System/Security##com.sap.engine.services.keystore####4EF963E63DAE11E4A2050000002B7B0E#4ef963e63dae11e4a2050000002b7b0e-0#4ef963e63dae11e4a2050000002b7b0e#Thread[ExRun:SMD_MGR_26,10,SMD_MGR:ExecTG]##0#0#Error#1#com.sap.engine.services.keystore#Java###Source: com.sap.engine.frame.core.configuration.NameNotFoundException: A file entry with the name "SMDAgent-cert" cannot be found in the configuration "keystore/TrustedCAs/entries".; Description: EntriesStorage - readEntry(SMDAgent-cert) in configuration [keystore/TrustedCAs/entries] failed with unexpected exception; Consequences: ; Countermeasures:check log for details##
#1.5 #001EC945232700500000012800001990000503341E810CD6#1410897268826#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SM_INTERN_WS#918##001EC94523271EE48CE20FF9FB774D30#AC14008B0CDC54189574001F00000000-0#43DB3DE44884F13EB530001EC9452327#SAPEngine_Application_Thread[impl:3]_28##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SM_INTERN_WS
Authentication Stack: sap.com/tc~smd~ws~agent~monitoring*SMDAgentMonitoring_DataProvider
Login Module                                                               Flag        Initialize Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT ok          false      false
2. com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule    SUFFICIENT ok          exception false                 Received no SAP Authentication Assertion Ticket.
3. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   OPTIONAL    ok          true       true
4. com.sap.security.core.server.jaas.CreateTicketLoginModule               SUFFICIENT ok          true       true
Central Checks                                                                                                true                  #
#1.5 #001EC9452327007E0000011100001990000503341E81D7E9#1410897268873#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SM_INTERN_WS#919##001EC94523271EE48CE20FF9FB774D30#AC14008B0CDC54189574002000000000-0#43DB3DE44884F13EB530001EC9452327#SAPEngine_Application_Thread[impl:3]_33##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SM_INTERN_WS
Authentication Stack: sap.com/tc~smd~ws~agent~monitoring*SMDAgentMonitoring_DataProvider
Login Module                                                               Flag        Initialize Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT ok          false      false
2. com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule    SUFFICIENT ok          exception false                 Received no SAP Authentication Assertion Ticket.
3. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   OPTIONAL    ok          true       true
4. com.sap.security.core.server.jaas.CreateTicketLoginModule               SUFFICIENT ok          true       true
Central Checks                                                                                                true                  #
#1.5 #001EC94523270053000001280000199000050334253E502B#1410897381878#/System/Security/Usermanagement##com.sap.security.core.persistence#J2EE_GUEST#0##DC2A72A83DDA11E4CB770000002B7B0E#dc2a72a83dda11e4cb770000002b7b0e-0#dc2a72a83dda11e4cb770000002b7b0e#SAPEngine_Application_Thread[impl:3]_23##0#0#Info#1#com.sap.security.core.persistence#Java#User "{0}" is the communication user for the connection between User Management Engine and the ABAP backend system {1}. This user cannot log-on to the User Management Engine.##User "{0}" is the communication user for the connection between User Management Engine and the ABAP backend system {1}. This user cannot log-on to the User Management Engine.#2#J2EE_ADMIN#SLMCLNT100#
#1.5 #001EC94523270053000001290000199000050334253E5151#1410897381878#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#J2EE_GUEST#0##DC2A72A83DDA11E4CB770000002B7B0E#dc2a72a83dda11e4cb770000002b7b0e-0#dc2a72a83dda11e4cb770000002b7b0e#SAPEngine_Application_Thread[impl:3]_23##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
User: N/A
Authentication Stack: SAP-J2EE-Engine
Login Module                                                               Flag        Initialize Login      Commit     Abort      Details
1. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   SUFFICIENT ok          exception             true       Authentication did not succeed.#
#1.5 #001EC9452327008A00000102000019900005033431310D8E#1410897582354#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SLDDSUSER#931##FF9A34B63DDB11E4BB010000002B7B0E#ff9a34b63ddb11e4bb010000002b7b0e-0#ff9a34b63ddb11e4bb010000002b7b0e#SAPEngine_Application_Thread[impl:3]_3##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SLDDSUSER
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module                                                               Flag        Initialize Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT ok          false      false
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true
3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true
Central Checks                                                                                                true                  #
#1.5 #001EC94523270084000000FF000019900005033431329358#1410897582463#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#SLDDSUSER#932##FFAADBF23DDB11E4B6910000002B7B0E#ffaadbf23ddb11e4b6910000002b7b0e-0#ffaadbf23ddb11e4b6910000002b7b0e#SAPEngine_Application_Thread[impl:3]_6##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.OK
User: SLDDSUSER
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module                                                               Flag        Initialize Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT ok          false      false
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true
3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok          true       true
Central Checks                                                                                                true                  #
Regards,
Farkath C

Create a Support Message in Production system showing up in Solution Manage

Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
Paul

Hi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role.

NWBC Reporting (Graphical View) Sequence of steps to activate.

Hi,
I am currently trying to configure NWBC reporting section in MDG6.1. It looks like Processing Time (List View) and Status Report Works fine but not Processing Time (Graphical View) which I uderstand BI Xcelsius dashboards. Currently when I click on Graphical View link, It goes to a page showing a button Change Lauchpad and a link under it as Processing Time. When I click Processing Time..it says Service not reachable.
I understand BI client not setup properly to link from dev system. I asked basis team to setup a BI client but I am not sure exact sequence to be followed here.. I search through SCN and did not find correct sequence.
Can anyone point me the right sequence to setup graphical view reporting? and the SAP Notes to refer on each sequense etc.
Thanks
Praveen

Hi Praveen,
Please go through the document Activating BI Content for Analysis of Change Re... | SCN this is the good document which talks in detail about the BI content setup.
Best regards,
Girish

Solution Manager EWA - cannot create session in satellite system

"Hi,
I want to configure EWA self service using Solman 4.0. I succesfully did the following :
a. Maintained SMSY and create the required trusted RFC connections from SM to satellite system. All connection and authorization passed in SM59. I used SAP_ALL/SDCCN_ALL role and assigned objects S_RFC*.
b. Assigned the system to a logical system.
c. Created the a new solution and activate "Solutions Monitoring > Earlywatch Alert"
d. Activated and maintained required RFC in SDCCN in satallite system.
My problem is that the create EWA alert request (Red Flag with a specific session number ) coulnd be pass to the satelitte system even though all the trusted RFC and authorization is set. When i execute the SESSION_REFRESH in the satellite system, the session is not created.
Did I miss out any steps. Can any one share any help ?
FYI, there is no connection to SAPOSS yet, so i did not manage to run RTCCTOOL completed, but i doubt this is required for EWA self service."
I have the same problem as Solution Manager EWA - cannot create session in satellite system
tried all of solutions, but it does not help... Created the CM (high) for SAP, but get 1 response for 1 week from them:(

Dear Sapbcer,
Have you tried the following option :
Execute SMSY and from the Server entry Execute the "Read System Data Remote" option in change mode.
Save the data captured and then try using Refresh Session Task from SDCCN of the satellite system. Do select the RFC for Solution Manager while performing this task.
Hope this helps.
Regards
Amit

Solution manager system log - strange entries

Hi Everyone,
the problem we are facing in Solution Manager system log every five minutes appears a new error message:
2 Database error -30082 at CON
0 > SQL30082N Security processing failed with reason "24"
0 > ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
First of all the landscape: ECC, BI, CRM, PI and Solman. Each system is DEV, QUA, PRD - except Solution Manager.
Result of going to see the logs within work directory:
Connect to %_DCR_XXXXX as db2dcr with DB6_DB_NAME=DCR;DB6_DB_HOST=xxxxxx;DB6_DB_SCHEMA=SAPSR3;DB6_DB_SVCENAME=5912
C *** ERROR in DB6Connect[dbdb6.c, 1727] CON = 1 (BEGIN)
C &+***      DbSlConnectDB6( SQLDriverConnect ): [IBM][CLI Driver] SQL30082N Security processing failed with reason "24" ("USE
C &+***      RNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
C &+***
C &+***
C &+***      ABAP location info 'CL_SQL_CONNECTION=============CP', 337
C &+***
C *** ERROR in DB6Connect[dbdb6.c, 1727] (END)
C *** ERROR => DbSlConnect to 'DCR' as 'db2dcr' failed
[dbdb6.c      1732]
Some of the systems are being connected successfully and the error messages in SM21 are not related to those systems. But some of the systems like DCR cannot be reached. And this fact causing the error messages.
I haven't configured Solution Manager because I have joined the project later. I would like to know what job is trying to access the satellite system and for what purpose.
On solution manager side I have checked all the scheduled background jobs - all of them have been executed successfully.
There some of them are scheduled but it is hard understand what is purpose of the job.
I have checked and corrected system landscape through SMSY and have maintained all the RFCs. They all OK now.
What else could force to make a connection to satellite system? And where is the place where it is hardcoded local(satellite) db2 connection entry?
Like I said before, some of the systems are being connected but some not. The one which has not been connected - there was recently changed SAP master password. I believe this is the key to resolve the problem. But the system itself operating 100% correctly.
Perhaps it could be CCMS that makes some extra connections to collect the data from the monitored systems. But I have checked all the RFC's in SM59 and they were OK.
Any ideas or suggestions would be appreciated.
Thanks in advance,
Kind regards,
Artjom.

Kaustubh Krishna,
thank you for respond.
It was dbacockpit. The connection was maintained with old db2sid password. And it was causing problematic log entries.
Problem was solved.
Points awarded.
Thanks,
kind regards,
Artyom

SAP NW 7.4 as java system sync with solution manager system 7.1 issue

Dear all,
I have installed SAP NW 7.4 system SP level is SP5 ,after that i have cheked in service marlket palce Now service market plkace latest SP level SP7.
For manula downlowd( directly from service market place) is difficult for java system and i have started sysnc with solution manager system to download patches through MOPZ.
Below are the activities completed:
1) Through template installed I have rgeisterd the system into Solman SLD.
2) Sync completed succfully exact product version is shwoing in solman SLD
3) after that I have checked in SMSY and LMDB its showing prefectly
4) But in SMSY its shwoing only under technical system,not showing product systems
5) I have assigned in product system in LMDB
Now the issues while selecting the system group and logical componensts I have created one logical componnets -but in that SAP NW 7.4 is not showing and I have assumed SAP NW 7.3 EHP1 after creating my newly create dsystem is not shwoing in drop down.
I ma getting belwo error.
No system found for this product/product instance
Message no. SOLAR_SPROJECT110
Please sugegst how to reslove the error ,and a;lso please let me know is there any way to download latest pathces to dpownload from service market place .
Advance Thanks

Hi,
re-check if the 7.4 system is correctly registered in the solman SLD system.
Re-check LMDB definition for your 7.4 as JAVA system. you have to manually created the Product system. Ensure all the Component and definitions are correct.
Also do a verrification run within the LMDB. This will confirm whether all the information is correctly defined.
Please note - SLD -> LMDB -> SMSY.
So, if the first 2 don't have the correct information, you wont have much joy with smsy.
Rgds
Deepak

System Monitoring with Solution Manager Ehp1

Hi,
I'm Tomas Piqueres, and I'm working in a VAR SAP with Solution Manager.
Recently, we installed Solution Manager Ehp1 and we are trying to configure it for System Monitoring. When I worked with Solution Manager SP17 I used to go to transaction RZ21 to add the system I wanted to monitoring and then put the SID and RFCs of the system.
Now with Solution Manager Ehp1, when I create the system in transaction RZ21, first I have to set the Component Type to Be Monitored and then the SID, Message Server Logon Group, the client and user are set automatically, and the password I've set to user CSMREG.
when I fill all the entries, I can see the RFCs used for the monitoring of the system. Those RFCs are set automatically:
<SID>_RZ20_COLLECT
<SID>_RZ20_ANALYZE
I can't edit those RFCs, so I have to create it manually. I check that RFCs destination works fine and both pass the authorization test, so when I try to save the system at transaction RZ21, I see the following errors:
<SID>_RZ20_COLLECT_123539Error when opening an RFC connection
Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Error when opening an RFC connection
Error during remote call of SALC function: Error when opening an RFC connection
Error during remote call of RFC1 function: Error when opening an RFC connection
I've been looking for information about those errors and how to monitoring with Solution Manager Ehp1, but I haven't found anything usefull.
Please, Could you help me?
Thanks and regards,
Tomas.

Tomas,
I need to configure EWA from my Solman system and I completed the steps (defining and creation of RFC destinations to the target systems from my Solman system). I downloaded the lates ccmsagent file from the market place based my target system configurations.
Herewith attaching the logs while I'm trying to check the profile parameter.
tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sappfpar check pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
================================================================================
==   Checking profile:     /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
================================================================================
***WARNING: Unexpected parameter: DIR_EPS =/usr/sap/trans/EPS/----
***WARNING: Unexpected parameter: SAPSECULIB =/usr/sap/TQA/SYS/exe/run/libsapsecu.o
***WARNING: Unexpected parameter: abap/buffersize_part1 =1200000
***WARNING: Unexpected parameter: auth/auth_number_in_userbuffer =5000
***WARNING: Unexpected parameter: dbs/io_buf_size =100000
***WARNING: Unexpected parameter: rsau/local/file =/usr/sap/TQA/DVEBMGS30/log/audit/audit_++++++++
***WARNING: Unexpected parameter: rsau/selector1/class =35
***WARNING: Unexpected parameter: rsau/selector1/severity =2
***WARNING: Unexpected parameter: rsdb/rclu/cachelimt =0
***ERROR: Size of shared memory pool 40 too small
================================================================
SOLUTIONS: (1) Locate shared memory segments outside of pool 40
               with parameters like: ipc/shm_psize_<key> =0
SOLUTION: Increase size of shared memory pool 40
          with parameter: ipc/shm_psize_40 =1472000000
Shared memory disposition overview
================================================================
Shared memory pools
Key:   10 Pool
            Size configured.....:   642000000 ( 612.3 MB)
            Size min. estimated.:   637597428 ( 608.1 MB)
            Advised Size........:   640000000 ( 610.4 MB)
Key:   40 Pool for database buffers
            Size configured.....: 1048000000 ( 999.4 MB)
            Size min. estimated.: 1468229308 (1400.2 MB)
            Advised Size........: 1472000000 (1403.8 MB)
Shared memories inside of pool 10
Key:        1 Size:        2500 (   0.0 MB) System administration
Key:        4 Size:      523648 (   0.5 MB) statistic area
Key:        7 Size:       14838 (   0.0 MB) Update task administration
Key:        8 Size:    67108964 ( 64.0 MB) Paging buffer
Key:        9 Size:   134217828 ( 128.0 MB) Roll buffer
Key:       11 Size:      500000 (   0.5 MB) Factory calender buffer
Key:       12 Size:     6000000 (   5.7 MB) TemSe Char-Code convert Buf.
Key:       13 Size:   200500000 ( 191.2 MB) Alert Area
Key:       16 Size:       22400 (   0.0 MB) Semaphore activity monitoring
Key:       17 Size:     2672386 (   2.5 MB) Roll administration
Key:       30 Size:       37888 (   0.0 MB) Taskhandler runtime admin.
Key:       31 Size:     4806000 (   4.6 MB) Dispatcher request queue
Key:       33 Size:    39936000 ( 38.1 MB) Table buffer, part.buffering
Key:       34 Size:    20480000 ( 19.5 MB) Enqueue table
Key:       51 Size:     3200000 (   3.1 MB) Extended memory admin.
Key:       52 Size:       40000 (   0.0 MB) Message Server buffer
Key:       54 Size:    20488192 ( 19.5 MB) Export/Import buffer
Key:       55 Size:        8192 (   0.0 MB) Spool local printer+joblist
Key:       57 Size:     1048576 (   1.0 MB) Profilparameter in shared mem
Key:       58 Size:        4096 (   0.0 MB) Enqueue ID for reset
Key:       62 Size:    85983232 ( 82.0 MB) Memory pipes
Shared memories inside of pool 40
Key:        2 Size:    31168040 ( 29.7 MB) Disp. administration tables
Key:        3 Size:   114048000 ( 108.8 MB) Disp. communication areas
Key:        6 Size: 1064960000 (1015.6 MB) ABAP program buffer
Key:       14 Size:    28600000 ( 27.3 MB) Presentation buffer
Key:       19 Size:    90000000 ( 85.8 MB) Table-buffer
Key:       42 Size:    13920992 ( 13.3 MB) DB TTAB buffer
Key:       43 Size:    43422392 ( 41.4 MB) DB FTAB buffer
Key:       44 Size:     8606392 (   8.2 MB) DB IREC buffer
Key:       45 Size:     6558392 (   6.3 MB) DB short nametab buffer
Key:       46 Size:       20480 (   0.0 MB) DB sync table
Key:       47 Size:    13313024 ( 12.7 MB) DB CUA buffer
Key:       48 Size:      300000 (   0.3 MB) Number range buffer
Key:       49 Size:     3309932 (   3.2 MB) Spool admin (SpoolWP+DiaWP)
Shared memories outside of pools
Key:       18 Size:     1792100 (   1.7 MB) Paging adminitration
Key:       41 Size:    25010000 ( 23.9 MB) DB statistics buffer
Key:       63 Size:      409600 (   0.4 MB) ICMAN shared memory
Key:       64 Size:     4202496 (   4.0 MB) Online Text Repository Buf.
Key:       65 Size:     4202496 (   4.0 MB) Export/Import Shared Memory
Key:     1002 Size:      400000 (   0.4 MB) Performance monitoring V01.0
Key: 58900130 Size:        4096 (   0.0 MB) SCSA area
Nr of operating system shared memory segments: 9
Shared memory resource requirements estimated
================================================================
Nr of shared memory descriptors required for
Extended Memory Management (unnamed mapped file).: 64
Total Nr of shared segments required.....:         73
System-imposed number of shared memories.:       1000
Shared memory segment size required min..: 1472000000 (1403.8 MB)
System-imposed maximum segment size......: 35184372088832 (33554432.0 MB)
Swap space requirements estimated
================================================
Shared memory....................: 2050.4 MB
..in pool 10 608.1 MB,   99% used
..in pool 40 999.4 MB, 140% used !!
..not in pool:   34.4 MB
Processes........................: 716.8 MB
Extended Memory .................: 8192.0 MB
Total, minimum requirement.......: 10959.2 MB
Process local heaps, worst case..: 1907.3 MB
Total, worst case requirement....: 12866.5 MB
Errors detected..................:    1
Warnings detected................:    9
After checking the profile parameter I tried to run sapccm4x in /run directory but got the below error and I'm not able tomove further.
Pls have a look at these two and let me know what could I do to proceed further.
tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sapccm4x -R pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
INFO: CCMS agent sapccm4x working directory is /usr/sap/TQA/DVEBMGS30/log/sapccm4x
INFO: CCMS agent sapccm4x config file is /usr/sap/TQA/DVEBMGS30/log/sapccm4x/csmconf
INFO: Central Monitoring System is [SMP]. (found in config file)
      additional CENTRAL system y/[n] ?   :
INFO: found ini file /usr/sap/TQA/DVEBMGS30/log/sapccm4x/sapccmsr.ini.
INFO:
      CCMS version 20040229, 64 bit, multithreaded, Non-Unicode
      compiled at   Jun 28 2010
      systemid      324 (IBM RS/6000 with AIX)
      relno         6400
      patch text    patch collection 2010/1, OSS note 1304480
      patchno       335
INFO Runtime:
      running on    saptqa01 AIX 3 5 00069A8FD600
      running with profile   /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
INFO profile parameters:
      alert/MONI_SEGM_SIZE = 200000000
      alert/TRACE          = 1
      SAPSYSTEM            = 30
      SAPSYSTEMNAME        = TQA
      SAPLOCALHOST         = saptqa01
      DIR_CCMS             = /usr/sap/ccms
      DIR_LOGGING          = /usr/sap/TQA/DVEBMGS30/log
      DIR_PERF             = /usr/sap/tmp
INFO:
      pid           4165682
INFO: Attached to Shared Memory Key 13 (size 200141728) in pool 10
INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for application server saptqa01_TQA_30, created with version CCMS version 20040229, 64 bit single threaded, compiled at Oct 3 2008, kernel 6400_20020600_254, platform 324 (IBM RS/6000 with AIX)]
        segment status     ENABLED
        segment started at Tue Sep 14 09:35:56 2010
        segment version    20040229
ERROR: Shared Memory misconfiguration ==> can not monitor SAP application server saptqa01_TQA_30
       Dispatcher Admin Shared Memory (Key 01) and CCMS Shared Memory (Key 13) both in pool 10.
       Please change configuration with profile parameters
           ipc/shm_psize_01 = -<different pool nr>
       xor
           ipc/shm_psize_13 = -<different pool nr>
EXITING with code 1

Configuration for Central Monitoring System in SAP Solution Manager.

Hi Folks,
I am trying to setup Central System Monitoring in SAP Solution Manager, I am following the document which mention the step by step instructions.
There are couple of items on which I am really confused.
In the documentation it says to activate Background Dispatching & Central System dispatching in 000 client of Solution Manager,
it also mentioned about creating CSMREG user, but it did not say in which client this activity needs to be performed, and there are lot many steps in which there is no mention about the client of solution manager in which we have to perform the configuration.
Can you guys please help me to configure properly?
One set document which I saw talks about the configuration using RZ21 and other document discuss about Configuration using System Monitoring Work Center, which one do we need to follow, are both methods are 2 different options doing the same thing, can you please clarify?
Also, is there any document which clearly explains the setup of Central System Monitoring in SAP Solution manager using both approaches and also to test the monitoring?
I have SAP Solution Manager 7.0 EHP1.
Thanks.
Jennifer

Hi,
>
> it also mentioned about creating CSMREG user, but it did not say in which client this activity needs to be performed, and there are lot many steps in which there is no mention about the client of solution manager in which we have to perform the configuration.
>
You should created this user in working client.
> Can you guys please help me to configure properly?
>
> One set document which I saw talks about the configuration using RZ21 and other document discuss about Configuration using System Monitoring Work Center, which one do we need to follow, are both methods are 2 different options doing the same thing, can you please clarify?
>
You can use RZ21 or System monitoring through work center. From Solution manager 7.1, you need to use work center only. So, I would suggest you to use work center only.
Thanks
Sunny

Solman system not shown RCA Change reporting for ABAP_Transport store

Hi,
We have configured RCA in Solman system.
We try to get Change reporting comparison of ABAP_transport for Dev and
Qas system.
But it shows error as Different technical system in Reference and CustomValue.
SAP Solution Manager 7.01 SP20
Regards,
Karthik

Jansi,
After selecting my QAS and DEV system in System Analysis for Change Reporting.
Select ABAP_Software(6store) of both system and then i click Comapre
And the status displayed as u201Cu2260u201DChanges were detected of Dev system, then i select the Dev system showing
Name                                                                 Reference Value                          Status                         Custom Value Details
   ABAP-SOFTWARE
   ABAP_NOTES
   ABAP_PACKAGES
   ABAP_SWITCH_FRAMEWORK
   ABAP_TRANSPORTS                                Different Technical System    Not allowed/Not Relevant    Different Technical System
I am comapring ABAP_Transport of QAS and Dev system. but its showing not relevant status.
Regards,
Karthik

"Error in Solution Manager Self Check While performing System Monitoring"

Hi All,
I'm running Solution Manager 7.1 SP8. We are running SOLMAN_SETUP Activities in Client 800, we are
not using the default client i.e. 001
I'm performing the "Solution Manager Self Check" in System Monitoring. When I execute
the Solution Manager Self Check option I'm getting an error message
Text = BI Setup check
'MYSELF_DEST' failed - Reason: ;Incorrect client 800; use BI client 001
Action = The CCMSBISETUP job was not completed successfully. Please run CCMSBISETUP again from the
transaction solman_admin and/or adjust the corresponding BI objects in RSA1 if
necessary.
Any Pointers, I am new to solution Manager, Will really appreciate your help.
Regards
Zohaib

Hi Amit,
This is what info I could see in the table RSBASIDOC
for Client 800
SLOGSYS        RLOGSYS       OBJSTAT BIDOCTYP TSIDOC3X TSPREFIX
XXXCLNT001   XXXCLNT001    ACT        ZSRA002                             RA
and for client 001
SLOGSYS        RLOGSYS       OBJSTAT BIDOCTYP TSIDOC3X TSPREFIX
XXXCLNT001   XXXCLNT001    ACT        ZSRA002                             RA
I could see the same info in both the clients.
@ Amit: Could you please provide me any inputs
Regards
Zohaib

System not displying in graphical view in solution manager

Similar Messages

Maybe you are looking for