XI 3.0 and BW 3.5 system type/logical component in Solution Manager

We are in the process of performing an upgrade for ERP 2004, XI 3.0 and BW 3.5. Initially this is being done in the sandpits. All systems are configured and connected our Solution Manager to download the packages.
We are unable to determine what type of system the XI 3.0 and BW 3.5 should be configured under. For example, previously we had an issue where ERP was configured as ECC 5.0 rather than ERP 2004. This was causing an issue in MOPZ where the upgrade option wasn't visible in a maintenance transaction. The same issue is now happening for XI and BW.
Please advise on the system type (logical component to use) for XI 3.0 and BW 3.5 in Solution Manager as SAP have made it very confusing. Currently both are under type Netweaver 04.
Regards,
-Rohan

Hi
I believe that SAP hasn't upgrade option for BW 3.5, Check link:
https://service.sap.com/solman-mopz
Upgrade
a "straight" upgrade for SAP Business Suite (upgrade from SAP ERP 2004 to SAP ERP 6.0, for example) is not supported by Maintenance Optimizer
Upgrade with an Installation of an Enhancement Package is supported for SAP ERP, SAP SCM, SAP SRM and SAP CRM
Regards
William Neira

Similar Messages

How to create System component in solution manager

Dear Experts,
How to Add a new (Custom) system component in solution manager which is used for service desk and also how to replicate the same component while creating support message (i.e., in F4-help for component filed).
Thanks in Advance.
Thanks and Regards,
*bold* Thirukumaran. R *bold*

check this blog:
/people/dolores.correa/blog/2007/10/06/service-desk-solution-database
basically it is at:
IMG under SAP Solution Manager -> Configuration -> Scenario-Specific settings -> Service Desk -> Solution Database
Nesimi

System Measurement: Measure and report license usage - System Type

After a 'system copy' to create new DEV and QAS PORTAL systems from a copy of PROD the USMM (System Measurement: Measure and report license usage) process identifies the System Type of the new systems as PROD.
This was first noticed when performing a 'License Audit'.
System Type: PROD
(Ex: URL http://<server>:<port>:50000/usmm)
Where can the 'System Type' be changed after a 'system copy'?

Hi,
You can change the System Type in Visual Admin under service Licensing Adapter.
Thanks
Sunny

Logical systems while implementing charm in solution manager

Hello Everybody,
I just wanted to know how many logical systems we need while implementing charm in solution manager 7.0. I have 3 clients in development , 3 clients in Quality and 1 client in production.
Thank you,
vikram.

Hi Vikram,
Yes, i1n ChaRM we always work with logical systems, I mean clients.
The standard is:
DEV -> QAS -> PRD
However, you can also use:
- Minimum
DEV -> PRD
- Target groups
DEV -> QAS -> PRD
- > TST
DEV -> QA1 -> QA2 -> PRD
DEV -> QA1 -> PR1
-> QA2 -> PR2
There are a lot of combination possible.
BR
Fernando

Required "/" (root) file system size on UNIX for Solution Manager.

Hello SAP Gurus,
   I am setting up SAP Solution Manager 3.2 on HP-UX. It is asking me about 350MB free sapce on "/" file system for Central Instance installation and about 120MB free sapce on "/" file system for Database Instance installation.
   I am installaing everything on to shared disk which mounted under /usr/sap. Why it needs free sapce in "/" file system. Is there any workaround to get rid of this requirement, as I have very less free sapce on "/" file system and I don't want to take the risks involved in increasing this size.
   Are there any SAP recommended sizes for "/" file system?
   I stuck in the middle of setting up SAP landscape on HP-UX (11.23). I searched through the Installation documents but I couldn't find any thing helpful in this regard. It is urgent requirement to set up this so please let me know any solution or workaround ASAP.
   Any help is greatly appriciated.
Thanks in advance.
Regards,
cvr/

Hi Vaibhav.
Normally "canonical path not available for (folder name)" means:
1. Wrong username/password. Please double check you credentials.
2. The resource cannot be linked from the portal server. Please be sure that you can connect to the next ports in windows server from the Unix Server:
a. NetBIOS Session Service TCP 139 This port is used to connect file shares for example.
b. TCP 445 The SMB (Server Message Block) protocol is used among other things for file sharing in Windows NT/2000/XP. In windows NT it ran on top of NetBT (NetBIOS over TCP/IP), which used the famous ports 137, 138 (UDP) and 139 (TCP). In Windows 2000/XP/2003, Microsoft added the possibility to run SMB directly over TCP/IP, without the extra layer of NetBT. For this they use TCP port 445.
I hope these things help somebody.
Best Regards,
Jheison A. Urzola H.

Can't assign system to logical component

Hello everybody,
I try to configure my Maintenance Optimizer. I have created a system with main instance SAP ECC Server. In view Landscape components i can see my system in node systems->sap erp. When i try to assign a Logical component SAP ECC an a massage "Logical component SAP ECC cannot be assigned to this main instance" is displayed and component is not assigned.
What have I wrong made? What should I check/configure?
Regards
Bogdan

If you go to help.sap.com and SOlution Manager and look for the assign logical components menu item you will find instructions on this. Basically from SMSY click on the system then on top left menu tree select "Other Objects"
when the popup comes up enter the system id in the "System field"
Then at the bottom of that popup you should see an icon like to pieces of paper called"Intalled product versions" click on that and you get another popup to show products installed on the box. If it is not listed in the bottom , you can use the top section to select the product using free product selection , then you should see this error disappear as you have identified the main instance it is talking about and furthermore you should be able to then assign it to a logical component

Managed System Setup / Configure Diagnostics for Solution Manager itself

Hello,
I'm trying to run the "Managed System Setup" for the Solution Manager itself and
I got a problem in the step 4 (Diagnostics Configuration / Configure Diagnostics):
In the new opened window is only the ABAP stack displayed and the Java stack
is missing.
Does somebody know how to make the java stack visible?
From my point of view seems the configuration of the SMSY ok. The java stack is also
as "relevant" set.
The Solution Manger 7.0 EHP1 is on SP25.
Thanks in advance for your help!
Kind regards,
Joern

Hi Jorn,
I dont think its happening just because of your CR Content.
Still If you want to update it,then go to Administration Tab in SLD->>Import the latest CR Content from there.
As the latest CR Content is :SAP CR Content Version (sld/active): SAP_CR 7.6 (produced 11/17/2011)
And Jorn if you are stucked in the Diagnostic Agent registration then Go to Agent Candidate Administration->>In connection
Parameters Tab go to->>Custom SLD Connection Parameters->>Apply->>Mark the Diagnostic Agent you want to
connect->>Attach->>Give the password of the SMD_ADMIN->>Apply->>This way you will connect to the available Diagnostic
Agent.Hope this will help your problem.
Thanks & Regards
Ajitabh
Edited by: jitu001 on Dec 23, 2011 5:47 PM

Mismatch in system number on Solution manager and SMP

Hi All,
I found System Id is different in Solution manager and Service Market Place. But where as System number is same in Satellite system and Solution manager. Because system is not same we are unable to send he solution to SAP. Please suggest how to make system id same on SMP and both satellite system and solution manager.
Regard's
Sai

HI,
Some what similar to thread .. How to change the system no | SCN

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 in Solution Manager

Friends
1.System monitoring for one of the satellite systems has been configured in solution manager (through DSWP - Setup system monitoring) using RFC connections(Read and Trusted RFCs generated in SMSY).
2.Installed CCMS Agent on the satellite system and registered to solution manager system.
RZ21 -> Remote Agent Status shows online.
Should something else to be done (settings, background jobs, configuration )in Solman or satellite system to make communication to satellite via CCMS agent primary for system monitoring?
How do i get to see the satellite system's monitoring context in Solution manager?
Please help me out
Thanks
Gnana

Friends
1.System monitoring for one of the satellite systems has been configured in solution manager (through DSWP - Setup system monitoring) using RFC connections(Read and Trusted RFCs generated in SMSY).
2.Installed CCMS Agent on the satellite system and registered to solution manager system.
RZ21 -> Remote Agent Status shows online.
Should something else to be done (settings, background jobs, configuration )in Solman or satellite system to make communication to satellite via CCMS agent primary for system monitoring?
How do i get to see the satellite system's monitoring context in Solution manager?
Please help me out
Thanks
Gnana

1 Solution Manager System - Mulitple Companies.

Hi All,
Please provide some input/information regarding one Solution Manager system with multiple companies.
Situation:
We currently have one Solution Manager system(SMP) that belongs to a main company. Under this company there are 5 separate companies. Each company including the main company has multiple SAP systems with different landscapes. Main Company - ECC6 landscape, BI 7.0, Portal, XI and HR Landscape. All other companies have their unique systems/landscapes with their own support personnel.
Issues at hand:
How do we setup Solution Manager to run multiple companies? Do we setup different Solution Landscapes and add each company systems to their own landscapes. How does this effect Service Desk/Charm setup ?
We also want to implement Service Desk / Charm / EWA and all the other functionality that is available in Solution Manager. Is there any advise on this issue and what are the potential pitfalls.
Is it possible to be setup multiple clients and have each company work in its own client.
I would appreciate any advice and information that will assist us with making an informed decision on the best way to proceed with this. I have done research and cannot find any information pertaining to this type of scenario. I'm hoping there are other customers that have a similar problem/issue.
Thanks and regards,
Ricky

Dear Ricky,
You are right. You sould create multiple solutions u2013 a solution for each company. Each solution comprises the landscape (systems) relevant.
I don't think setting up multiple clients and have each company work on its own client is a good idea. The solution manager supports monitoring and managing multipal solutions. By creating multiple clients you are loosing the advantage of one-point-of-entery. Besides, a lot of the customization in the SolMan is cross client.
Regarding the service desk:
You may create a sold-to-party business partner for each of the companies (transaction BP) and assign each sold-to-party only to the relevant system/iBase in transaction IB52. This will allow you to screen the messages in the service desk by a sold-to-party/company.
Regarding the EWA:
The EWA monitors the systems in the solutions. You may have as many solutions as you want.
Regarding the Charm:
Sorry, we didnu2019t implement it yetu2026 you should keep asking abour that.
If you would want to use Business Process Monitoring - this is solution based, so I don't see any problem there.
Hope it was helpful.
Good luck!
Adi Skutelsky

Evaluation system with Solution manager

has anyone added an evalaution system where a user who logged a support message can evaluate the Solution given, with Solution manager. Basically the same thing like SAP have. When you close a call you have to rank the messageeg in regards of qaulity of answer etc etc..,
Anyone that might have any ideas how to do this, could you please give me some direction to how I can implement an evaluation system.
I thought of having a URL added to confirmation message, where the user can click on to take him to some area where he could evalaute the message. This systems is then linked to Solution manager so that I can report on these messages and the evealuation received for these support answers.
I will appreciate any feedback and any ideas would be most welcome to help me to get to a method of implementing such a evaluation system or developing such a system.

Dear Johan,
Firstly the kind of scenario that you are trying to implement is not possible via the standard configuration of Support Desk.
What I can think of is probably creating an action while closing the message which generates a form for the user to be filled and saves the values into an custom table for questions based on evaluation of the solution.
Later you can generate reports based on this table.
Regards
Amit

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

System Monitoring Setup in Solution Manager

Hello Experts,
We are going to implement and configure Solution Manager - System monitoring setup for pre testing purpose
Currenly we have installed below SAP Systems
1.Solution Manager Server
2.ECC server (Without Ides) - Abap
3.CRM Server (Without Ides) -Abap + Java
We need to setup below tasks in Solution Manager
1.Early watch alert
2.System Monitoring
3.Central System Administration
4.Business Process Monitoring
5.Service Level reporting
1.Is it possible to setup the solution manager -above mentioned tasks without Ides system ?
Could you please someone give input reg this.
Thanks
Thirumal
Edited by: Thiru Thirumal on Aug 6, 2008 4:56 AM
Edited by: Thiru Thirumal on Aug 6, 2008 4:57 AM

Hi,
Q. Is it possible to setup the solution manager -above mentioned tasks without Ides system ?
A. Yes.
Check with links for
1.Early watch alert
This process helps you to identify potential problems early, avoid bottlenecks, and monitor the performance of your ABAP and JAVA systems and your most important business processes, regularly, automatically and effectively. The data collection infrastructure comprises the ABAP Service Data Control Center and the JAVA function module Data Provider. The SAP EarlyWatch Alert in the SAP Solution Manager is a service provided by SAP.
To be able to use it, you have:
maintained the non-ABAP systems correctly in the system landscape maintenance (transaction SMSY)
RFC u2013 Connections between: and an RFC u2013 Connections established.
your satellite systems and the SAP Solution Manager system
SAP Solution Manager and the SAP Service Marketplace
Solution Manager system and Solution Manager Diagnostics
Cf: Solution Manager IMG (transaction SPRO).
checked the availability of the tools required for the SAP Service sessions (add-on ST-A/PI), with the report RTCCTOOL.
activated Alert Monitoring and set-up the Automatic Session Manager (ASM) in the Service Data Control Center (SDCCN) of your satellite systems, for all SAP satellite systems and the central SAP Solution Manager of your solution
set-up your systems in a solution landscape in the SAP Solution Manager
configured Solution Manager Diagnostics
2.System Monitoring
The system monitoring in the SAP Solution Manager is, as described above, like a system-wide central CCMS. It can also contain the central CCMS (CEN) of satellite systems. These CENs can then monitor other components.
The graphical display in the SAP Solution Manager gives you access to the alerts of all systems in a solution. You can go to the local or central CCMS of the satellite systems.
The system proposes the most important alerts in the CCMS monitor collection, according to SAP experience, and their alert thresholds, for each system in the solution, in the system monitoring Session. You can activate or deactivate these alerts. The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager, overwriting the values in the local CCMS.
3.Central System Administration
You activate the customizing for business processes in your solution, in the Business Process MONITORING session in the SAP Solution Manager. A monitoring tree element (MTE), or a monitor collection, u201EBPMu201C of several monitoring objects, is created in the local or central (CEN) CCMS of the satellite system.
The data is collected for the monitoring types of the business process monitoring in contrast to system monitoring, as follows:
● The system collects performance (dialog transactions), posting cancellations (V1 and V2) and u201EOther CCMSu201C and interface data, in the local CCMS of the satellite systems.
● The system collects background processing, application list, application monitors, delivery lists, and document size data, in the central SAP Solution Manager CCMS.
The SAP Solution Manager system copies the data from the local CCMS.
The graphical display in the SAP Solution Manager simplifies access to the alerts for the business processes, business process steps or the interfaces between the systems in a solution. You can go to the local CCMS of the satellite systems.
The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager. These overwrite the values in the local CCMS.
4.Business Process Monitoring
The system and business process monitoring (including interface monitoring) in the SAP Solution Manager, both use the Computing Center Management System (CCMS) (transaction RZ20) architecture. This means that system alerts which occur in the local CCMS, are passed to the SAP Solution Manager via RFC connections between the SAP Solution Manager and the satellites. The system shows these alerts in a graphic or in Sessions. You can also handle the alerts centrally, without having to go to the local CCMS of the satellite systems.
You can see the alerts from several systems in a solution landscape in the SAP Solution Manager, in a graphical overview, in contrast to the local CCMS of the SAP Solution Manager satellite systems. This is the view of a central CCMS (CEN). You can also monitor non-SAP systems in a central CCMS (CEN) of a satellite system
5.Service Level reporting
http://service.sap.com/solutionmanager for all solman tasks as given below.
http://www.asap.net.cn/homepage_en/Solution%20Manager%20EN.pdf
http://help.sap.com/saphelp_sm32/helpdata/en/1b/f02c41ab78f66fe10000000a1550b0/content.htm
http://help.sap.com/saphelp_sm32/helpdata/en/9f/1f46570f8a4a268b3154e0e0f07280/content.htm
Regards,
Srini Nookala

Adding systems with same SID in SMSY - solution manager

Dear All,
We are having systems with same SID's which belongs to different landscape created for various customers.
Currently We are having only one solution manager.
I consider this example for explanation.
Customer 1 : DEV --> QAS --> PRD ( SID's)
customer 2 : DEV --> ACC --> PRD ( SID's)
I would like to add these 6 systems in a solution manager. For Customer 1 , I have included the systems in SMSY . But when i tries to add DEV, PRD for customer 2 , it fails since this SID's are already present.
Is there any other way to include by giving the different SID's DE2 but with correct IP and host Or we need to have one more solution manager ? Please anyone suggest me on this
Thanks
Raj

Dear Juan ,
We can add systems with same SID in smsy. I have attached the way in which i have done. This may help others. Thank you all for your suggestion
Only use more than three characters if your landscape contains multiple systems with the same system ID (if you have a mirrored backup system that has the same ID as the original system, for example).
If multiple systems in your landscape have the same system ID, choose as system name the system ID with a suffix of up to 5 characters (a sequential number, for example) to create a unique system name.
The system accepts a system name of more than 3 characters if you choose Enter to confirm.
Thanks
Raj

XI 3.0 and BW 3.5 system type/logical component in Solution Manager

Similar Messages

Maybe you are looking for