SolMan 7 to Ehp1

Hi,
Can we convert Solman 7.0 to Ehp1 via importing the latest support packages. Or we need to upgrade it.
Thanks,
Rohan

Hi,
For solamn upgrade to EHP1 you have to use SAINT/JSPM. Any how you have to study upgrade guide to uderstand all the things.
For more information check below link:
https://websmp210.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000065932
Also, check SAP Note 1169247 - Enhancements to Solution Manager 7.0 EHP1 upgrade (SPS18,19)
Thanks
Sunny

Similar Messages

Upgrading SolMan to EHP1

Hello Gurus,
Need a help,
I am in the process of upgrading the SolMan to EHP1.
I have read all the Docs available in SMP and also refered the Blogs.
Can any 1 please give the Brief steps that we need to follow to upgrade SolMan as i need to submit the request i need to specify the what all actions am going to perform. So i need the brief steps in order, that would of great help.
Our Kernel release is 700 SOlMan7. i know that we need to take SP to 17 before upgradation. But what abt Kernel level.
Here SP17 means is it only ABAP. Basis and Java or it it all the SP availabe in the system should be take to 17.
Please help.
Regards,
Sr

Hi Anjali,
Upgrade all components which are not upgraded by stack upgrade to highest level.
Does this mean i need to upgrade all the SP levels of all SP available in my system.
Upgrade Java to SP17 using JSPM
can you please let me know the path where i can download the Java SP17.
Download SPS tab file in XML from Marketplace for EhP1 and upload in /usr/sap/trans/EPS/in
As per the note sapnote_0001169247, there are 2 XML files SAP_SOLUTION_MANAGER_70_EHP1.xml and SPSTab.xml.
whats the main use of these files, whats the mai purpose, what they contain. How they are useful in upgrading SolMan to EHP1.
Please let me know.
Regards,
Sr

System Monitoring - Solman 7 EHP1

Hi
Solution Manager 7.0 EHP1 / Windows 2008 / Oracle
Satellite System R/3 Enterprise extn set 110 / Solaris on Sparc / Oracle
I am having trouble configuring System monitoring on solution Manager. Here is what I have done
Added the satellite system to SLD, Configured data collector (RZ70) in the satellite system, Pushed data from SLD to SMSYS (automatic transfer).
Installed CCMS agent + CCMSPING agent in satellite system. Checked connectivity in solman with RZ21. Connectivity is fine.
Created Monitor sets and monitors in CCMS for monitoring satellite system. Client data is visible in CCMS.
Created a solution in DSWP. Created logical component in SMSY. Assigned the logical component to the solution. Now I can see the data in DSWP.
Here are my questions
==================
1. In DSWP, everytime I have to view data, I have to click on "Setup System Monitoring" to view the alerts in the satellite system
I see a red alert reading for instance availability. Similarly,
In the system monitoring workcenter, I see the status of both the solution manager and the satellite system greyed out with a cross. When I move my mouse over it, it reads, no CCMSPING data available.
Any idea as to why this happens?
2. For what I see after I click on "Setup System Monitoring" I have parameters which I can configure. I see default values for these parameters. Is there like a recommendation or a template which can be used to setup these monitoring parameter values?
3. I have configured the ccmsping in the solution manager (for the solution manager) however the ccmsping service refuses to run. It throws a error reading "The system could not find the file specified". The ccmsping exe file is present in the location stated. Are there other files that this is looking for?
4. While registering the agent in the satellite system, I first registered with the CSMREG id. It failed with the message,
INFO: [SMG:040:CSMREG] connected to SMG, host sapsm.NA.XXX.NET, System Nr. 00, traceflag [ ]
INFO: SMG release is 701 , (kernel release 701 )
        RFC Error Info:
         message:
         status: EXCEPTION AUTHORITY_NOT_AVAILABLE RAISED
         intstat:
      Go Ahead anyway? n/[y] :
INFO: handling destination SAPCCM4X.SAPR3PR1.00
ERROR: can't register at SMG. RfcRc = 2, AUTHORITY_NOT_AVAILABLE
RFC Error Info for SALF_CSM_AGENT_REGISTER
message:
status: EXCEPTION AUTHORITY_NOT_AVAILABLE RAISED
intstat:
I then did this with a dialog user. That worked. Agent was registered in solution manager. Any idea on why this error would show up with the CSMREG? I am concerned about issues which can come up when the password for the dialog user changes.
I am not sure how to upload screenshots of what i see, probably if i do that, it will be easy to relate to the issue which I am mentioning here. Is there a way I can do that?
Let me know if you need any more information from my side to understand this.
Ideas will be appreciated.
thanks
Ravi

Hello Ravi,
Additionally you will want to look at SAP Note 1175058 - Problems with CCMSPING in SAP Solution Manager, especially
c) Ensure that the message server host name in the monitoring options of CCMSPING and the message server of the corresponding main instance of the relevant system is the same in the SAP Solution Manager landscape
(SMSY). Important: The monitoring options of CCMSPING must not be configured using an IP address.
Regards,
Paul

Is Wily Introscope a requirement with Solman 7 ehp1

We are finishing and upgrade from 3.2 to 7 EHP1.
Due to limited system capacity we have not installed the Wily Introscope product. At this time we were not planning on using its functionality. We are wanting to keep the basic functionality of solman 3.2 plus add the MOPZ piece.
I'm using the solman_setup tcode to go through the basic config wizard now. I've reached the Landscape Data step where it is asking for the Wily Introscope info. Since it doen't exist, can I bypass this step?
Thanks for your advice.
Laurie McGinley

Thanks Jarad,
That is what I thought (it isn't required), but needed to double check before I bypassed that bit of the setup.
Appreciate the quick response too!
Laurie

Upgrading Solman from SP 17 to EHP1 errors with the Kernel install

I've been trying to upgrade solman to EHP1 but I get errors when I try to install Kernel 7.01. After I have copied the kernel to \SYS\exe\uc\NTAMD64 I can start SAP and for a while it works. Then SAP stops working and both services stop. I've tried to restart the services but I get and error telling me its the wrong product version and to re-install the software. Its a 64bit unicode kernel on windows 2003 64bit and I have the right kernel. Any ideas anyone?

HI
I am having the same issues. when upgrading via JSPM or manually, the sap services won't start and keep saying the version is incompatable, and suggested to reinstall.
Did you manage to get around it?
Regards
Kevin

Applyed EHP4 in all system except SolMan,will this work or required in SolM

Hi Experts,
we have upgraded the SP13 to SP18 for ERP and NetWeaver. On to this we have upgraded the EHP4 for ERP and NW in ECC, BI and SRM and Portal system. We have not upgraded the EHPs in Solman System. Now my concern is that is it necessary to upgrade the SOlMan system with the EHP (same as other systems) or not required??
As we are having SLD in solman and lots of other configuration like CUA (Central User Administration). If we will not apply the EHP in solman and apply only in the other system will that work fine??
Thanks
Narpal Singh

Hi,
It is not necessary to upgrade to your solman to EHP1. But it is always recommended to upgrade to latest patch level.
Thanks
Sunny

SAP Solman Installation

I need to install SAP Solman 7 + EHP1; AS ABAP +DB on one server and java on other server, based on Windows 2K3 Ent Server 64bit and Oracle 10.2. This is because of the limited hardware resources on a single server.
Is it mandatory to have ABAP and JAVA on same box with Solman ? I know you can add dialog instances later.
When I try to install using sapinst --> SAP Systems --> --> --> Oracle and Central System; it asks me for Java component. It does not proceed further unless I mention the java export location. Same happens if I select a distributed installation ?
Can someone please help me understand this behavior ?
Thanks,

For Solution Manager it's not possible to separate ABAP + Java due to technical restrictions.
Markus

SSM upgrade to EHP1

Hi experts,
i need Your help and advise how to upgrade Sap Solution manager
Now i am working on :
SAP Solution Manager 7.0 + krenell 195 + Windows2003 + MSSQL
SAP_BASIS     700     0016     SAPKB70016     SAP Basis Component
SAP_ABA     700     0016     SAPKA70016     Cross-Application Component
PI_BASIS     2006_1_700     0006     SAPKIPYM06     Basis Plug-In (PI_BASIS) 2006_1_700
ST-PI     2005_1_700     0006     SAPKITLQI6     SAP Solution Tools Plug-In
SAP_BW     700     0018     SAPKW70018     SAP NetWeaver BI 7.0
SAP_AP     700     0014     SAPKNA7014     SAP Application Platform
BBPCRM     500     0012     SAPKU50012     BBPCRM
CPRXRPM     400     0013     SAPK-40013INCPRXRPM     SAP xRPM/cProjects/cFolders 4.00 (ABAP)
ST     400     0017     SAPKITL427     SAP Solution Manager Tool
ST-A/PI     01J_CRM500     0000          -     Application Servicetools for CRM 500 / 5
ST-ICO     150_700     0011     SAPK-1507BINSTPL     SAP Solution Manager Implementation Cont
ST-SER     700_2008_1     0005     SAPKITLOO5     SAP Solution Manager Service Tools
What do i need to apply EHP1 ?
Please advise .... in some simple steps )

Hi,
You can upgrade your solman to EHP1 via SAINT/JSPM. For more information how to upgrade check SAP Note 1169247 - Enhancements to Solution Manager 7.0 EHP1 upgrade
Note 1276895 - Add. info. about Upgrading to SAP Solution Manager 7.0 EHP1
And upgrade guide here https://websmp201.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000065932
You will get to know what is the pre-requisite and process for that.
Thanks
Sunny

CEN at Solman - which agent to install

Dear Gurus.
I have in my landscape SOLMAN 7 EHP1 , and different NetWeaver releases - 701 ,710 and 720 as monitored system,
When configured CEN at solman, which agent I need to install and configure on satellite systems? ccms agent+SAPOsCol or saphostagents, that installed togehter with 710/711 and 720?
Regards
Vladimir

Dear Vladimir,
As described in all the installation guides (chapter 2.2) attached to these SAP Notes, the official recommendation is as
follows (see SAP Note 1365123 for more details):
Solution Manager: Versions 7.00 (prior to EhP1)
Managed version: 6.40, 7.0, 7.0 EhP1 & 2, 7.1 EhP1
Agent to installl: 7.01 SR1 SAP Note 1357812
Solution Manager: Versions 7.0 EhP1 >= SP 18
Managed version: 6.40, 7.0, 7.0 EhP1 & 2, 7.1 EhP1
Agent to installl: 7.01 SR1 SAP Note 1357812
Solution Manager: Versions 7.0 EhP1 >= SP 20
Managed version: 6.40, 7.0, 7.0 EhP1 & 2, 7.1 EhP1
Agent to installl: 7.11 SAP Note 1234387 (*)
(*) The Diagnostics Agent 7.20 installer is not released for the time being (should be in the next few days). Therefore to install an agent 7.20, the only option is to download the standard SAP NetWeaver 7.20 DVDs (CE). Meanwhile, SAP recommendation is to install 7.11.
The fact that the release of the managed system has no impact on the Diagnostics Agent to install. Only the SOLMAN release is important. As of SOLMAN SP20 you can use either the Diagnostics Agent SAPinst 7.11 or the 7.20 one. There are no major differences between 7.11 and 7.20 (only bug fix u2013 e.g. host agent automatic installation - and SSL support).
If you choose to go with 7.11 please make sure SAP Host Agent is installed and running according to the Diagnostics Setup Guide available at http://service.sap.com/diagnostics -> media library.
Best regards,
Guilherme Balbinot

Understanding and using Logical Components for Managed System configuration

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

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

ChARM - Additional logical component does not show up in tasklist

Hi,
the Area is Change Control Management in SolMan with EhP1
Situation:
- SOLMAN_SETUP and configuration for ChARM (number ranges etc.)
- two transport routes: A and B with DEV, QAS, PPRD, PRD
- all systems are maintained in SMSY (PPRD, PRD are virtual)
- two logical components: logA, logB
- one project in SOLAR_PROJECT_ADMIN
-- system landscape - systems are maintained
-- img projects are created
-> Change Request -> Show tasklist
ONLY Systems from logA are available. Creation of transport requests for logA are fine.
Through different errors and changes logB was changed after creating tasklist for logA.
Has anyone an idea why the systems from logB are not in the tasklist?

senthilprakash selvaraj wrote:
> To be very specific,
>
> Login to SAP CRM system.
> Goto: SYSTEM-->status
>
> In there under SAP SYSTEM DATA group, you will be able to see a "Magnifying Lens" icon just below Component Version field --> click it
>
> there you will be able to see the exact version&level of the component.
Yes, that's where I copied that line
SAP_ABA 702 0009 SAPKA70209 Cross-Application Component
from.
senthilprakash selvaraj wrote:
> Now ask your basis team to deploy the same version&level in SAP PI as its shown in the CRM system.
Ah, the PI/XI content could be missing, even if this shows up in the list of products and software component versions in the SLD?
I have just checked in the ESR, that seems to be the problem, thanks.
senthilprakash selvaraj wrote:
> Note: Thou the release version might be same, the level of the component deployed in both the system might be different. hence the problem.
You mean if the service pack is different? I doubt that this would result in the SWCV not showing up in sproxy.
Monika.

J2SE 1.4.2 for Windows x64 bit download link

Dear All,
Can any one give me the link to download J2SE 1.4.2 for Windows x64 bit architecture?
Your help is highly appreciated.
Regards,
Syed

There should be no issues with using SAP JVM from the start.
Probably no notes because is straightforward:
- Extract the SAP JVM (e.g. c:\sapjvm_4)
- Set JAVA_HOME (c:\sapjvm_4)
And start installation as per guide.
We have done this recently with Solman 7 EHP1 and NW 7 EHP1 (J2EE stack).
We did have issue on central instance install where the J2EE instance would not start part way through installation (server0 continually crashed and restarted with memory issues) so we had to adjust the instance settings as per SAP Note#1603093, before retrying in SAPINST and continuing.
We had this problem with both Solman & NW 7 EHP1.

Documents in solar01

hi all
I`ve transported my projects from SolMan 3.2 to SolMan 7 EHP1. When I tried to open any transported documents, have a message "No document opened ". Any idea!?

Multiple causes for this..
Is this is the problem with all the documents or only few
it is opening from other people machine and not only on ur machine.
Check SAP GUI version..
It should me SAP Logon 710 Patch level latest...more than 6 or so..
actually there are some bugs in earlier patch level of 710 so might be it is because of this
1023083 Registry functions did not work
Please check for more SAP Notes in addition
Note For information about the expected release date of the patch please view note 578944.
Hope it helps
Regards
Prakhar

Sol man upgrade!

Dear All,
Could you please guide me in upgrading solution manager from 4.0 SR2(Patch level 11) to Solman 7 EHP1...
Can i upgrade it through EHPi or i have to deploy patches first through (SPAM/SAINT)
Any prompt help related to this is appreciated......
Regards,
Sohal....

Hi Harvinder,
In order to upgrade solman to EHP1. You cannot use EHPI installer. You have to do this via SAINT/JSPM.
Also, check 1169247, 822380
Also, link https://websmp201.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000065932
Thanks
Sunny

Number Range BU_PARTNER & CRM_SERVIC

Hi,
We have newly Installed the Solman 7 EHP1. I have configured Standard Service Desk & CHARM.
But when I created first support message its number is 8000000074 next number is 8000000075. After this next ticket number is 8000000080, 8000000082.
There is no continus numbers.
Even in Business Partner number also I am not getting the sequence. Randomly system is assigning numbers.
What coud be the reson.
objects BU_PARTNER & CRM_SERVIC
Regards
PK

Hi PK,
I see two reasons for this not so randomly assignements :
1. If you create a support message, a number is reserved within the number range you define, but if you don't save the message, the number will be lost.
2. there a buffering system for reserving numbers in the application server this buffer can be the reason why there is a gap in ticket numbers (Tx SNRO).
Hope it helps.
Regards,
Stéphane.

SMSY Issue: systems are re-assigned incorrectly

Hello,
I'm running Solman 7 EHP1, and since upgrading to SPS 20 I've been having the following issue:
After the nightly refresh of my landscape in SMSY, via my Solution Manager's SLD, the systems are re-assigned to the Solution Manager Product Version (when they're actually XI/PI, ERP, and BW 3.5 type systems). I manually change them back, but its no use, becuase at the next SLD refresh, they'll be changed back.
This is causing other issues, such as changing the layout in my iBase structure. Which also leads to more issues...and so on!
Any ideas?
Jose

Jose,
Here is what I would do.
Go to SLD > Admin > Technical systems > all > remove systems that has wrong product version. Re-register from RZ70 from each technical system to SLD. See if it shows correct version. If it doesn't then do following:
Go to SMSY_SETUP and replace SLD with Transport Sync. That will stop over riding your product version.
Update SLD Data model and CR to latest.
and change back SMSY_SETUP to get satellite system data from SLD.
See if that works.
Good Luck,
Digesh Joshi

SolMan 7 to Ehp1

Similar Messages

Maybe you are looking for