CPS on Solution Manager EHP1?

Folks,
Any idea whether we can install CPS in Solution Manager EHP1 (7.01) system with Java EHP1 (SP4)?
The CPS software is available under NW 7.0.
Regards
Chandu

Hello Cheeti,
you can install SAP CPS on SAP Solution Manager and SAP CPS is actually quite independent on Java support package (but choose the right NW release 7.01), i.e. you do not always have to update you SolMan system if you install a new CPS release.
However, if you read through the SAP CPS Installation Guide (Scheduling) you will find the recommendation to install SAP CPS on a separate server. That might not necessarily be the case for test or demo installations and of course also depends on your utilization of SAP CPS.
Have you considered these things:
Sizing: How does the ressource consumption of SAP Solution Manager influence you SAP CPS scheduler? Will important jobs be delayed?
Are there sufficient RFC resources for all application? (SolMan, Wiley, CPS all these application need to communicate with the managed systems)
Do you want to entangle the lifecylce management of SAP CPS with SAP Solution Manager? Which production do you want to update more/less frequently? Can you accept additional down times?
Kind regards,
Martin

Similar Messages

Big Problem With Solution Manager EHP1 ?

Dear all,
I have already installed SAP Solution Manager EHP1, after the installation sucessfuly. I check the function: Project Administration ( T code : Solar_Project_Admin), then select New project button.
The program inform that:
"Runtime Errors: Message Type Unknow
What happened:
Error in ABAP Application program
The current ABAP program "SAPLSPROJECT_SYSTEM_LANDSCAPE" had to be terminated because
it has come across a statement that unfortunately cannot be excuted.
etc
Do you know about this problem, what is the errors ?
Thanks all.

Dear all.
With Solution Manager EHP1
SAP Basis: SAPKB7001-SAPKB70016, SAPKB70101-SAPKB70102
SAP ABA: SAPKA7001-SAPK70016, SAPKA70101-SAPKA70102
Detail log as below:
Runtime Errors MESSAGE_TYPE_UNKNOWN
Date and Time 28.04.2009 16:47:15
Short text
Message type " " is unknown.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSPROJECT_SYSTEM_LANDSCAPE" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Only message types A, E, I, W, S, and X are allowed.
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_UNKNOWN" " "
"SAPLSPROJECT_SYSTEM_LANDSCAPE" or "LSPROJECT_SYSTEM_LANDSCAPEU28"
"SPROJECT_SYSL_CHECK_CENTRAL_SY"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Information on where terminated
Termination occurred in the ABAP program "SAPLSPROJECT_SYSTEM_LANDSCAPE" - in
"SPROJECT_SYSL_CHECK_CENTRAL_SY".
The main program was "SAPLS_IMG_TOOL_5 ".
In the source code you have the termination point in line 29
of the (Include) program "LSPROJECT_SYSTEM_LANDSCAPEU28".

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 of MOPZ on Solution Manager EHP1 ST 400 Patch 18

Dear Team,
Request you to let me know the Procedure to Configure MOPZ on Solution Manager EHP1 ST 400 Patch 18, i am struck in between, if any one can send me any document regarding this will be highly appreciated.
Regards,
Adarsh Kumar

Hello,
You can have a look at the Maintenance Optimizer quick startup guide at the Wiki:
https://wiki.sdn.sap.com/wiki/display/SM/Overview
Please let me know if you have any comments / feedback about the Wiki.
Best regards,
Miguel Ariñ

System monitoring configuration in solution manager EHP1

Hi all
I am in a bit of fix
We have upgraded our solution manager devlopment to EHP1
Now I have added one system through SMSY in solution manager to configure system monitoring
I have generated all the RFC's,I have created the logical component and solution and assigned the system to the solution
When I check my solution it is looking fine
Now when I go within solution and click on the tab system monitoring
It shows me on the left hand side -> Set up system monitoring
when I click on Set up system monitoring on the left part of SAP screen,strangely it doesnt take me to the activation of screen monitoring,it just shows me the best practices documents on the right side but nothing more than that
I have checked many guides,blogs and SAP tutors anfd have followed them but strangely I am not been able to go to the screen for activating system monitoring
Are there any activities that need to be done after upgrading to EHP1?
Are there any services to be activated for system monitoring?
Please advice
Rohit

I'm not 100% sure that it is necessary, but it won't hurt.
Perhaps the essential adjustment you need for system monitoring is being done in there.
It won't hurt

Solution Manager EHP1 and BW cubes

Hi,
In solution manager , we have used the productive client as the BW client also. But we would like to know how the cubes are loaded.
I dont see any source systems in RSA1. Also all cubes look like Real time cubes.
So is there a concept of process chains in solution manager ?
Can someone provide more insight into it.
Thanks,
Tanuj

Hi Tanuj,
It depends on which function area you are using. Incident Management reports, Test Workbench, Root Cause Analysis, Business Process Monitoring, and so on. But most of the case, data are loaded into BW Real-time Cube by using BAPI, which called from scheduled Solution Manager jobs.
For example, in case of RCA reports, the job named "EFWK Resource Manager" triggers BW data extraction.
Regards,
Kazuhisa

Kernel Update from 7.00 to 7.01 - SAP Solution Manager EHP1

Can anyone give me some information about update sap kernel?
How must I proceed?
Thanks!

Login to service market place www.service.sap.com>downloads>supporpackages and patches>My company applicationsselect sap solution manager>SAP SOLUTION MANAGER 7.0 EHP 1>Entry by component>solution mangaer ABAP stack>select sap kernel 7.01 64 bit unicode-->select widows
server on X64bit>select database indendent>just scroll download you can see list of pathces select SAPEXE_23 which is the lates one and selet the check bot to add to download manager now select database dependant patch based on your database you have installed(Ex oracle or MS SQL)
select the same patch SAPEXEDB_23 and download the 2 patches through download manager
uncar the 2 patches throught sapcar command
sapcar -xvf <and give the patchnameSAPEXE......SAR>
sapcar -xvf <and give the patchnameSAPEXEDB......SAR>
Now take the backup of existing kernel
Drive:/usr/sap/SID/SYS/exe/uc
once the backup of kernel is finshed stops SAP and releated services
start>cmd>services.msc-->stop the service sap<SID_instance number> and saposcol service
now copy all the uncar newfiles to original run directory and replace all.If you face
problem like some service is still running then stop all the oracle services also and
try again.
Once all the files are copied then start the services and SAP
Let me know if needed more information
Regards
Uday

Error while upgrading to Solution Manager EHP1 from 3.2

Hi All,
I am trying to upgrade the solution manager3.2 to EHP1.
OS: Linux RHEL 4
DB: Oracle 10.2.0.2
I am in the Prepare phase.....
When I try to run the JPREPARE command( /dump/smrtest/SMR_UP/51036444/JPREPARE) I get the following error message
An unrecoverable error has occured:
Could not execute dialog SelectModulDialog. See previous messages.
Input output exception while processing dialog SelectModulDialog. See previous messages.
Could not send dialog message. See previous messages.
Could not bind to port 6240.
java.net.BindException: Address already in use
Can anyone help asap?

> I am in the Prepare phase.....
> When I try to run the JPREPARE command( /dump/smrtest/SMR_UP/51036444/JPREPARE) I get the following error message
You have a Java instance installed on 3.2?
> An unrecoverable error has occured:
>
> Could not execute dialog SelectModulDialog. See previous messages.
> Input output exception while processing dialog SelectModulDialog. See previous messages.
> Could not send dialog message. See previous messages.
> Could not bind to port 6240.
> java.net.BindException: Address already in use
Read the documentation about SAPJup - you have to change the default port (because most likely your ABAP part uses that one).
Markus

Recieved error during Solution Manager EHP1 Java Components installation.

I successfully installed EHP1 ABAP components but I'm have a problem with the Java components. I recieved the following error. Import aborted during ADSSAP02_0-20002778.SCA
Feb 20, 2009 3:17:59 PM Error: Aborted: development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.20071213024549.437972'/'1', grouped by software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application com.adobe/DocumentServicesLicenseManager..
Reason: Exception during generation of components of application com.adobe/DocumentServicesLicenseManager in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application com.adobe/DocumentServicesLicenseManager in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Feb 20, 2009 3:17:59 PM Info: Starting to save the repository
Feb 20, 2009 3:18:01 PM Info: Finished saving the repository
Feb 20, 2009 3:18:01 PM Info: Starting: Update: Selected software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1' updates currently deployed software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.16.0.20080610114809''/'0'.
Feb 20, 2009 3:18:01 PM Error: Aborted: software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
Failed deployment of SDAs:
development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.20071213024549.437972'/'1' : aborted
Please, look at error logs above for more information!
Error: Aborted: development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.200712
13024549.437972'/'1', grouped by software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application com.adobe/DocumentServicesLicenseManager..
Reason: Cannot load one of the bean interfaces or the bean class of bean LicenseEJBBean.; nested exception is:
com.sap.engine.services.ejb.exceptions.deployment.EJBXMLParserException: Cannot load one of the bean interfaces or the bean cla
ss of bean LicenseEJBBean.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Feb 20, 2009 11:25:59... Info: Starting to save the repository
Feb 20, 2009 11:26:01... Info: Finished saving the repository
Feb 20, 2009 11:26:01... Info: Starting: Update: Selected software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634'
'/'1' updates currently deployed software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.00.16.0.20080610114809''/'0'.
Feb 20, 2009 11:26:01... Error: Aborted: software component 'ADSSAP'/'sap.com'/'SAP AG'/'1000.7.01.2.0.20080930104634''/'1':
Failed deployment of SDAs:
development component 'DocumentServicesLicenseManager'/'com.adobe'/'Adobe Systems'/'802.20071213024549.437972'/'1' : aborted
Edited by: Darrell Kirklen on Feb 23, 2009 5:03 PM

Just resolved problem. While reviewing the sdmlog20090310.log I found
error "java.lang.UnsupportedClassVersionError?" when I goggled this
error "How do I resolve a java.lang.UnsupportedClassVersionError? I
found the following solution:
http://support.codegear.com/article/35846 : This exception can occur
when the source is built targeting a JDK that is not supported by the
JDK attempting to run it. In the above example, if the servlet was
built targeting only JDK 1.5, but the web server runs JDK 1.4, the
above exception will occur. Check, Project Properties | Build | Java |
Target VM, and verify that the Target VM indicates a JDK compatibility
that is appropriate for the JDK that is running it. It is recommended
to set this field to 'All Java SDKs' for the most compatibility. The
only reason you would want to specify a particular version is if your
code uses language features that only appear in a particular version of
the JDK, and you want to ensure that users use only a compatible JDK.
Also check, Project Properties | Build | Java | Language Features, and
verify that the Language Features are applicable with JDK that is
running it
A this point I checked the java -version at the os level and it showed
1.5.0_17 we are aware the supported version of java should be 1.4.2_16
our Unix team (Solaris) recently installed new patches and didnu2019t
remember to leave the java version at 1.4.2_16 after their were done.
Once the java version was set back to 1.4.2_16 I was able to complete
the java portion of EHP1 using the JSPM successfully.
Edited by: Darrell Kirklen on Mar 13, 2009 4:37 PM

Solution Manager EHP1

Hi.
We're thinking in an upgrade to EHP1, but we're asked about the SPAU....
We want to know, what a kind of things we need to take care, before starts this upgrade.
Thanks in advance.

Hi,
if you did not do any development change to SAP dfault, SPAU will not worry you. SPAU only prompts when you have repaired objects in your workbench (customer modification). In your case, the only thing will be SNOTE-corrections, but you can set them all to back to SAP default.
Concerning customizing and your "solman business" processes: Keep your eye on testing them after applying EHP1 has finished.
From my experience, there were no major changes to ChaRM or ServiceDesk, so testing effort should not be too much.
And please be aware: before applying EHP1, you should be on SPS17!
Hope this helps you.
Kind regards,
Dirk

Solution Manager 7 EHP1 green/demo install

I am trying to set up a standalone SAP BI server with the demo content so I can test a product that queries InfoCubes. Windows 2003/SQL Server 2008 platform.
I am trying to follow the docs, but they assume some prerequites that are not clearly defined. I have a central system running with a license installed, but I cannot apply SNOTEs because I get an error in connection to destination SAPOSS.
Obviously I am missing something fundamental but I can't find a simple guide on what to do. The documentation seems to run in circles telling me to do things that don't work because I don't have the right SNOTEs installed.
Is there an easy way to get a SAPOSS connection for a non-production system?
Is there a guide that walks you through all the prerequisites for a Solution Manager 7 EHP1 install?

> Is there an easy way to get a SAPOSS connection for a non-production system?
In order to download the SAP Note via SNOTE, the SAP OSS RFC connection should work. If your SAP Router is working fine, then add necessary entries in Tcode OSS1>technical Parameters . Add the router in the system data of the particular system in service market place.
> Is there a guide that walks you through all the prerequisites for a Solution Manager 7 EHP1 install?
Refer the installation guide in service.sap.com/instguides > SAP components > Solution Manager EHP1 .
Regards,
Nibu Antony

Solution Manager - Logical Component for SAP Netweaver EHP2

Hello,
I installed the newest SAP Netweaver Ehp2 (with usage type AS ABAP only) for a future integrating with BI_CONT (SAP BI requirement). So... what I want to know is... I want to do an update of support packages to the latest Stack (SPS) and in this product version (NW EHP2) the latest stack is stack 06 !! But I ´m facing with a problem which is, because I have to maintain this system in Solution Manager (for Maintenance Optimizer activity)...so what I want is configure this new system on Solution Manager Ehp1 (with SPS 23) but in tcode SMSY I didn´t found this Product in Logical Components for I can apply this system to my Solution... I only see SAP Netweaver with EHP1 and not with EHP2 which is the version that I want to apply this new system. (This is mandatory task, because without it, I will not be able to download the support packages for NW 7.0 EHP2)
Tell me two things... first if this level version of Solution Manager that I have here (SPS 23) have this product in logical components, and two... if not it, is necessary to raise the level of Solution Manager support packages (to latest stack SPS 25) for I can see that logical component SAP Netweaver EHP2?!
Thank you very much
João Dimas - Portugal

Hi João,
You can verify if the EHP2 is available (if) in your system, this can be done once you are in SMSY -> Product Definitions -> SAP Netweaver where you should able to see the EHP2. If so, then it's a matter of marking the leading Product & Product Version under the Header Data ->Change Product Assignment where you can use the drop down arrow to select the Product and Product Version. If it's not available, then by checking the 'Free Product / Select Product Version' then use the drop down arrow to select the product & Product Version, once you selected that then click on copy and mark that as active and save.
Then you need to create a new logical component in System Group & logical Component under SAP Netweaver, then assign the system to the logical component. Once this is done you can use the logical component in a solution and create a maintenance transaction.
I hope this help you to proceed further, thanks.
Jay Soma.

EWA on Non-ABAP System with Solution Manager EHP 1

Hi Experts,
We have recently updated our solution manager from SP Stack 16 to EHP1 (sp 18). we are now planning to set up EWA for non-abap components (EP 7.0). however, the only SAP note that i have been able to find is "976054 - Availability of EWA for Non ABAP components" but this is only limited up to SP 17. I have not been able to find any guides relating to EWA thru Solution Manager EHP1.
I would greatly appreciate if anyone can refer any documents or SAP notes that would enable setting up EWA for non-abap components thru Solution Manager EHP1.
We have also gone through the note 1332428, but we have'nt found it useful. We are still struggling to generate EWA report on Non-ABAP system.
Looking forward to your kind help.
Thanks and Regards,
Sarthak Syal

Hi Sarthak,
Good!!
Please do the following:
1) include the system in the Solution and scheduled the EWA session.Logical component should refer to the Non-ABAP System with no ABAP instance as relevant under the SID definition in SMSY-systems.
2) Is the Non -ABAP ( assuming its java) has the Software component defined and is mentioned as relevant under the SID with the component name and type.
3) Having said that SMD - Root cause Analysis functionality is configured-> check whether you are getting the Details for the Non-ABAP systems in the analysis Tabs of Root Cause Analysis.
This should be good to go. Wait for the session to get completed.
Thanks,
Jagan

System registered in SLD invisible in solution manager configuration

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

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

What are configurations required on Solution Manager 7.0

Dear Sir,
I have asked to my Implementation Partner to implement Solution Manager with following details.
Maintenance Optimizer Configuration, Usage, Hands on and Training. Patching using Solution Manager.
a. Configuration Maintenance Optimizer
b. Installation of Software Lifecycle Manager u2013 SLM
c. Software Logistics Controller u2013 SLC
d. SLD Registration
e. Configuration for Transport Directory
f. Support Package Manager u2013 SPAM (Specially on SM)
g. Java Support Package Manager u2013 JSPM (Specially on SM)
h. Usage of MO and Demo
i. EWA Scheduling Using SM.
j. EWA Recommendations Implementation
Please let me know If I am forgeting any thing or needs to be configured for smooth running of our setup. What are thing to be configured??
Please also let me give a brief(in addition to notes) about Usage of SLC, SLM, SLD, Transport Directory and How it will help in transport management system.
Is it possible to apply patches from Solution Manager to all systems?
Regards
Dharmendra

Dharmendra,
There are many features with Solution Manager EHP1 SP 04. See if you ask them to upgrade to latest level.
Also following more features are available. Depending on your company and your requirement you could configure it.
- System Monitoring via central auto alert
- System Availability monitoring (CCMSPING)
- Central system administration
- DBA Cockpit
- CPH (Central Performance History)
- Job Management
- Project Administration
and many more things are available. Go through Link: [www.service.sap.com/solutionmanager] for more information
Thanks,
Digesh Joshi

CPS on Solution Manager EHP1?

Similar Messages

Maybe you are looking for