Default password of SAP * in Solution Manager

I have created a new client in solution manager.
I could not login to the client wiht user sap* and PASS as password.
Pls help

Hi Balaji,
Just an additional info in case you dont have that parameter. Please create it.
http://help.sap.com/saphelp_NW04s/helpdata/en/c4/3a6247505211d189550000e829fbbd/frameset.htm

Similar Messages

SAP NW Solution Manager 4.0 Administrator/J2EE_ADMIN password locked out

Guys,
I was successfully able to install SPA Solution Manager v4.0(ECC 6.0) JAVA+ABAP Stack.
Post Installation, I am tried to logon to the SolMan (User Management & SAP Netweaver Adminsitrator) through HTTP (IE) URL http://<localhost>:port
The homepage displays just fine. When try to authenticate to User Management & SAP Netweaver Adminsitrator using following commbinatioln, the authentication fails.
user = J2EE_ADMIN password = <ADMIN>
OR
user = user = J2EE_ADMIN password = <admin> (Not sure if the password is case sensitive)
Now, I looked at the alerts and found that J2EE_ADMIN user is locked.
Does anyone of you know how to unlock this id and what its password should be ?
Any alternative user id/password can be used to login ?
Should I have to install SAP GUI for Java or ABAP ?
Please help me login to solution manager.
Thanks for your help!!
Chris.

Hello,
as far as I know you can login with a sapgui to your installed system. If you did an standard installation, then the J2EE stack is bound the client 001. Therefore logon as DDIC or SAP* to the ABAP part with SAPGui and unlook the J2EE_ADMIN user.
You had tp specify the passwort of all users during the installation process of SOLMAN 4.0. If you did an standard installation, you only specified one password for all kind of users.
HTH
Frank

How to post message from SAP to solution manager

Dear Friends,
We have configured solution manager service desk and the users were able to send messages so that we can view it in solman ITSM.
Now we want to bifurcate the messages from different people, hence we woule like to use of Problems in incident management of solman.
How a end user can create a message so that it comes and fall in problems folder of incident management,
Normally create support message from SAP will make the message to be visible in incidents of solman ITSM, but we want the message to fall in problems section of ITSM in solman.
Please help.
Thanks
Suresh

Hi,
In 7.1 we do have dedicated services as Problem management, with the transaction type SMPR. you can create ZMPR and proceed similar to SMIN ( incident) in ITSM.
also refer here Problem Management in SAP Solution Manager 7.1 - Part 2
Thanks
Jansi

Upgrade process to SAP Solution Manager 7.1

Hello!
We use SAP EHP 1 for SAP Solution Manager 7.0 (SPS 26) and plan to upgrade to the new SAP Solution Manager 7.1.
We currently do not have Java Stack there.
Some questions about Upgrade process
1) Can a direct Upgrade from SAP EHP 1 for SAP Solution Manager 7.0 (SPS 26) to SAP Solution Manager 7.1 be realized?
2) Should we first install Java Stack and then proceed with the Upgrade or otherwise?
3) Will Windows 32 Bit and None-Unicode Version of SAP Solution Solution Manager be supported?
It will be great to get some helpful information.
kind regards

Hello!
Trying to answer your question
1) As described in note 1244225, there no restriction to upgrade the Solman EHP1 to solman 7.1. Refer to the section:
In case you do not participate in this current Solution Manager 7.1 beta shipment there are no restrictions for implementing now SP stack 25 and upgrading in the future to an equivilant SP stack of release 7.1."
2) The Solman EHP1 must always be a dual stack system, I am not sure, how you are running the Solman EHP1 without a Java Stack, you should have one.
3) I am not sure if there will be a Solman 7.1 32Bit Non-UNICODE version. But, SAP recommends to run Solution Manager on Unicode (see also customer letter on http://service.sap.com/Unicode). At solman EHP1 there are some issues when running the system as Non_UNICODE, refer note 1383407.
I am not sure if I could clarify all your doubts.
You may check the following URL:
http://service.sap.com/instguides
- SAP Components
- Solution Manager 7.1
As this is a very new software there is few documents in it, but soon you should see a upgrade guide here.
Regards,
Allam

SAP Solution Manager Certification Examination

Hello,
I am planning to take up 'SAP NetWeaver - Solution Manager Implementation Tools' Certification Examination during SAP TechEd 06. I wanted to get some kind of sample qusetion/test papers for the same.
I would be grateful if anyone could guide me as to how to go about the preparation and where to get the sample paper & other study material from?
Also, I wanted to know what level of knowledge do they expect us to have?
Regards,
Kavitha

Hello,
I've tried to get to some Sample Questions here on Forum, but I couldn't get any.
I passed an exam on 14.11.2006 and I suggest to you to use course materials as suggested by SAP (SMI310). That is sufficient to pass the certificate. All the answers are there.
My general opinion: not easyYou have to be pretty much concentrated as there were questions put in negative expressions.You have to be really, really carefull.
They are taking a lot of details on subjects like Type of projects (Template projects, Roll out implementations, customer satisfaction) including its Roadmaps. (e.g. roll-out project phases and its content.)
I only saw 3 or 4 questions familiar to me (from Test your knowledge, SMI310 book), others were really related to course materials but spoken in their own words
If you have any questions, dont hesitate to contact me.
Good luck to you and best regards.
Nikolina

SAP NetWeaver Application Server ABAP 7.4 on SAP MaxDB - default password

Hello colleagues,
I have deployed this app.server (see subject) on the AWS cloud but unfortunately I cannot log-in. I've tried all known default passwords for SAP* and DDIC with no result. The documentations says - "You specify the master password during instance creation in the SAP Cloud Appliance Library"... It didn't ask me to specify the password ((
Hence, I have a few questions:
- What's the default password and where should I change it;
- How to unlock blocked accounts in SAP instances (SAP* and DDIC are blocked due to lots of failed attempts);
- How I can access the file system (this VM is on Linux), so... Putty???

Hi,
You can unlock them:
update <schemauser>.usr2 set uflag='0' where bname like 'username what you want to unlock' ;
You can use emergency SAP* user if you are totally lost with the passwords.
Like this:
update <schemauser>.usr2 set bname='SAPP*' where bname like 'SAP*' ;
and you need to change the parameter:
login/no_automatic_user_sapstar to value of '0'
If you do these steps you can logon with SAP* user and 'pass' password....
after you finished you should change back login/no_automatic_user_sapstar to value of '1' in the profile !
Hope this helps,
Krisztian

Does somebody have experience to manage SAP project with solution manager?

Hi friends,
I will implement new project for my client. As I know, solution manager is already part of SAP Netweaver. To install SAP NetWeaver, solution manager must be installed. Meanwhile, solution manager provides a project management tool, for example, the business process definition, blueprint...
But I never use it to manage project. Could somebody share experience in this area?
Regards,
Watson

Hi Ragu,
Thanks for your posting. I will implement a SAP APO project. What I need is the methods to use solution manager, for example, configuration manual, step by step guide. I'm also interested in the advantages of SAP solution manager.
Regards,
Watson

Is Solution Manager mandatory for getting support for SAP 4.7?

Hi,
We received a letter from SAP regarding Solution Manager which stated:
"Commencing on April 2, 2007, SAP Solution Manager will be the only source from which customers receive maintenance updates for SAP NetWeaver 2004s and beyond, as well as applications based upon it (including mySAP Business Suite 2005 applications)."
We are still using SAP 4.7. We do not use Solution Manager. Does this statement mean that for getting any updates / support patches on 4.7, we will need to implement Solution Manager?
Can anybody clarify your understanding or SAP's stand on this?
Regards,
Ashish

To add to Dolores point, The link in market place...
https://websmp206.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000689446&_SCENARIO=01100035870000000202&
The link also contains the SAP Tutor file explaining the process. Hope it helps you.
Br,
Sri
Award points for helpful answers

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.

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

Solution Manager 7.1 IT Service Management: IRT, MPT new status

Hello everyone,
I am wondering, if in SAP Solution Manager 7.1 IT Service Management I can customize new status into SLA measurement, for example 'Customer action' duration time at Web browser (similiar fuctionality as IRT(The initial response time) and MPT(maximum processing time)).[IRT & MPT|http://pokazywarka.pl/ysrkhe/]
Equally, new SLA status should be calculating duration for the other incident status for example "In process". If anyone has idea, please advice.
Best regards,
SAPFan
Edited by: SAPFan on Feb 6, 2012 10:48 PM

Hi,
Under the System Prepration section I have 2 questions I need additional clarification:
1. Under 6.2 Prepare Outside Discovery -> Establish trusted connection-> /usr/sap/hostctrl/exe/host_profile of solution manager server:
a. I added service/admin_users = daaadm. Am I suppose to include the password? what should the formate be?
What you have entered is fine. Would not need to provide the password as well. Check the External discovery troubleshooting guide sections.
https://websmp207.sap-ag.de/~sapidb/011000358700000486362011E
2. Under 6.3 Connect Diagnostic Agent -> ran the following command on my ECC server:
./smdsetup.sh managingconf hostname:"solutionmanager.FQN" port:"50004" user:"ddaadm" pwd:"password1"
a. Is the user/password referring to SolutionManager admin account?
b. How do I check if it's running correctly?
c. How to get my solution manager to see my Ecc server's diag agent?
The user password should be a Solution Manager Java user like SMD_ADMIN or J2EE_ADMIN
How to check for diagonstic agents, again check the trouble shooting guide referred above.
I checked the following:
Start Visual Administrator and navigate to: Server node -> Services -> Security Provider. Please also make sure that the MBeanAdmin is mapped to the Administrators Security role on both: com.adobe/AdobeDocumentServicesADS-EJB and com.adobe/DocumentServicesLicenseManagerADS-License
I don't see the Adminstrator role to add to the above. Am I suppose to just enter "administrator"?
Yes, just add the role "Administrators"
2. Solution Manager Internal Connection -> Setup DPC/DCC Web Service URL
a. I'm supposed do the following: You have started the Agent Administration:
b. How do I start the Agent Administration?
Make sure you have the role SAP_SMWORK_DIAG assigned to your user ID via SU01. Then call solution_manager tcode and goto the RCA tab. Agent Administration link should be available.
Regards,
Srikishan

Solution Manager.

Hi SolMan Experts,
I am working in an SAP implementation project, which is in its project planning phase.
Since i am new to Solman ,i have few things in my mind to clear.
How is Solman used while Implementation ?
Can Solman store multiple project docs centrally in 1 server ? Can it have a link to other SAP
   systems ?
In post-implementation support activity ,can we log problems in Solman for getting solutions
directly from SAP support ? If yes then how it is done ?
Can we apply new patches directly from SAP market place into multiple SAP systems linked to
SolMan?
Thank your for your answers.
These will help me while using SolMan in our project.
Thanks and Regards,
Umesh Karane.
Mobile - 98196 25133.

Hi Umesh,
How is Solman used while Implementation ?*
     During implementation you can use projects to manage your implementation.
             solar_project_admin -> To create projects
     You can use it build blueprint of the project and basing on the blue print you can configure the target system.
           SOLAR01 - Blue printing SOLAR02 - Configuration.
for more information please check http://help.sap.com/saphelp_sm40/helpdata/en/9a/90b441b60e3331e10000000a155106/content.htm
Once the blueprint is in place you can configure Business Process Monitoring later on this blue print during support.
Can Solman store multiple project docs centrally in 1 server ?*
           You can store all the documentation you create during blue printing in solution manager under project documentation.
        Can it have a link to other SAP
        It can connect to target system which is to be configured ( After configuring some RFCs) .
       If this doesnot answer your question please explain what you are looking for ?
In post-implementation support activity ,can we log problems in Solman for getting solutions*
directly from SAP support ? If yes then how it is done ?
The support messages raised in satellite systems will be created in Solution manager once you configure support desk and there is automated workflow through which you can send messages to SAP and you can get the replies of SAP in solution manager itself.
for more info please look at http://help.sap.com/saphelp_sm40/helpdata/en/ff/6ea7a870ac469ea54cedd12666cc5d/content.htm
Can we apply new patches directly from SAP market place into multiple SAP systems linked to
Now you can only download the Support packs once you approve them through Maintenance Optimizer. After approving you still need to download through Download manager and apply them in systems. It is not handled by solution manager.
you can appy notes through SNOTE in all system through solutioin manager. You need to select the system where you want to apply from solution manager itself and it will apply that note in that system.
The complete documentation of Solution Manager 4.0 can be accessed at http://help.sap.com/saphelp_sm40/helpdata/en/45/51fbdbd4941803e10000000a1553f7/frameset.htm
regards
Mrutyunjay

How to install the Solution Manager

Hi Gurus,
any one can help me out i want to install the Solution Manager 4 any one can help me out like what is the minimum HDD & RAM is required, and how many exports wil required this Solman. Can i download from Market place please gurus help me out.
Cheers

Download Solution Manager from
http://service.sap.com/instguides
--> Technology Components
Find the installation guide at
http://service.sap.com/instguides
--> SAP Components
--> Solution Manager
For sizing and other questions see note
1088980 - Documentation: SAP Solution Manager 4.0
Markus

Problem in installation of Business Content for Solution Manager

Hi all,
I have a problem while trying to install the Business Content for Solution Manager. In detail, I cannot install/ see the Process chains. I am not much familiar with Business content installation, so maybe I missed and /or some step.
Following the instructions from SAP IMG (SPRO/ SAP IMG / Solution Manager / Configuration / Scenario-specific settings / Solution monitoring / BI Reporting / BI Client) , I activated the Datasource 0SM_SMG_ROOT , performed all the steps and installed all the relevant Business Objects (Infoobjects, Datasources, Infocubes, Infopackages, etc.). All the objects seen from transaction RSA1 seem correctly installed and activated.
The last step is the installation/activation of the Process chains. This step is executed, but the installation job terminates with messages like Infopackage 0SM_XXXX does not exist in D version; activation not possible. It seems like Process chains are looking for some Infopackage, and these are not present. They are not present indeed, and I dont know why. The result is that no Process chain is visible from transaction RSPC.
Am I missing some step, or doing a wrong/ incomplete procedure ?
Thanks a lot

HI Saravanan,
For Solman Service Desk, the following objects are used :
Cube : 0CSRV_C01
DSO : 0CRM_PROH
DataSource : 0CRM_SRV_PROCESS_H
And apart from this there are some MD datasources, for BPARTNER, USER STATUS, CATEGORY etc.
Regards
Mahesh Kumar

Regarding Monitoring Service for Solution manager

We need to configure "Monitoring" services in SAP solution manager 7.0.
Could somebody suggest us what are the main tasks we need to consider for doing Monitoring settings.
How many Minimum servers required to configure Monitoring services in solution manager system.
Also if any good document reference for this?
Thanks

Hi Jai,
welcome to sdn.
COMPONENTS & TOOLS OF SAP NETWEAVER
SAP Solution Manager
The SAP Solution Manager application management solution facilitates technical support for distributed systems u2013 with functionality that covers all key aspects of solution deployment, operation, and continuous improvement. A centralized, robust application management and administration solution, SAP Solution Manager combines tools, content, and direct access to SAP to increase the reliability of solutions and lower total cost of ownership.
With SAP Solution Manager, you can be sure your entire SAP solution environment is performing at its maximum potential. The toolset addresses your entire IT environment, supporting SAP and non-SAP software and covering current and forthcoming SAP solutions. And, as a customer of SAP, you have full access to the core SAP Solution Manager for no extra charge.
SAP Solution Manager targets both technical and business aspects of your solutions, focusing strongly on core business processes. It supports the connection between business processes and the underlying IT infrastructure. As a result, it eases communication between your IT department and your lines of business. And it ensures that you derive the maximum benefits from your IT investments.
SAP Solution Manager features and functions include:
SAP Business Suite implementation and upgrades u2013 SAP Solution Manager provides content that accelerates implementation. Configuration information and a process-driven approach to implementation speed the blueprint, configuration, and final preparation phases. SAP Solution Manager enables efficient project administration and centralized control of cross-component implementations.
Change control management u2013 SAP Solution Manager controls all software and configuration changes of the IT solution. This includes the approval process for change requests, the deployment of changes, and later analysis of changes. This ensures quality of the solution and enables traceability of all changes.
Testing u2013 SAP Solution Manager speeds test preparation and execution. It provides a single point of access to the complete system landscape and enables centralized storage of testing material and test results to support cross-component tests.
IT and application support u2013 The service desk included in SAP Solution Manager helps you manage incidents more efficiently and eases the settlement of support costs. Centralized handling of support messages makes the support organization more efficient.
Root cause analysis u2013 The diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution of problems, even in heterogeneous environments. This helps to isolate general performance bottlenecks, to isolate exceptional situations, to record the activity of single users or processes, and to identify changes to the productive landscape. As a result, problem resolution is accelerated and business availability increased.
Solution monitoring u2013 SAP Solution Manager performs centralized, real-time monitoring of systems, business processes, and interfaces, which reduces administration effort. It can even monitor intersystem dependencies. Proactive monitoring helps you avoid critical situations, while automatic notifications enable fast response to issues.
Service-level management and reporting u2013 SAP Solution Manager allows easy definition of service levels and provides automated reporting. Service reporting covers all systems in the solution landscape and provides a consolidated report containing the information you need to make strategic IT decisions.
Service processing u2013 SAP Solution Manager makes appropriate service recommendations and delivers SAP support services. These include SAP Safeguarding, which helps you manage technical risk; SAP Solution Management Optimization, which helps you get the most from your SAP solutions; and SAP Empowering, which helps you manage your solutions.
Administration u2013 Administration tasks are mainly executed locally on the involved systems, but can be accessed and triggered from a central administration console. The administration work center in SAP Solution Manager offers a central entry point and unified access to all SAP technology.
SAP Solution Manager as the name suggests is for managing the whole gamut of SAP and Non-SAP solutions in the IT Landscape of an organisation. It provides you the tool, content and gateway to create, operate, manage and monitor your solutions over time.
It provides a range of scenarios to support this. Extending from project management to Solution Monitoring to Service Desk to E-learning Management, it provides an efficient way to carry out a plethora of business tasks.
SAP Solution Manager is the successor to ASAP ValueSAP. SAP Solution Manager helps in implementing and managing complex system landscapes. Globally systems are getting distributed across geographies and business processes cover more than one system. In such complex scenarios, integrating technical and business requirements is important for the success of IT. SAP Solution Manager provides SAP customers with an efficient means of handling both the technical and business process side of solution implementation .
As part of SAP Solution Management Solutions, the customers receive best practices relating to:
- Global Strategy and Service Level Management
- Business Process Management
- Management of MySAP Technology
- Software Change Management
- Support Desk Management
SAP delivers this using support programs during implementation of the system solution. Some of the benefits of using SAP's Solution Manager are that it helps:
- Manages the technical risk associated with the implementation of the solution ensuring technical robustness
- Helps leverage users core competencies in implementing solutions
- Ensures solution works as intended with best practices built in.
see these links...
http://www.ne-sap-solution-manager.com/
http://www.saptechies.com/category/sap-solution-manager/
thanks
karthik
reward me if usefull

Default password of SAP * in Solution Manager

Similar Messages

Maybe you are looking for