Solution manager SP stacks

Hi All
Iam planning to upgrade my solution manger system to SP16 present level is SP12,i have applied latest SPAM level 34 and downloaded relevant SP stack 16 through MO and also SPSTab.xml file and solman.csv and pasted all downloaded fileS in EPS/in directory including the xml file, when i try to load the pathces from application level in tcode SPAM its saying error as "No OCS files were found for uploading"
My question
1:Do i need to uncar all the car files and then paste it in EPS/in directory ?then what is use of xml file?
2:Is there any method to uncar all the files at one shot rather then single patch?
3:Can any one provide me related document how to do it ?
Regards
Uday

> 1:Do i need to uncar all the car files and then paste it in EPS/in directory ?then what is use of xml file?
Yes.
cd /usr/sap/trans
SAPCAR <file>
This will place them directly to EPS/in
> 2:Is there any method to uncar all the files at one shot rather then single patch?
On Unix:
copy all files to a directory, then
cd /usr/sap/trans
for i in `ls <directory`; do SAPCAR -xvf <directory>/$i; done
Markus

Similar Messages

Installing the Solution Manager JAVA stack

Is it required to install the Sol Man Java stack in order to perform Java transports through ChaRM?
Thank you.

Hi,
for any java transport, you have to have java stack installed.
Thanks,

Can I install Solution Manager 7.0 in Window Server 2008 R2 Enterprise ed.?

Hi, SDN experts.
I am trying to install Solution Manager 7.0 in in Window Server 2008 R2?
I checked the the software requirement for SAP Solution Manager 7.0, it only mentioned Window Server 2003 and 2008 enterprise edition.
I am trying to install Solution Manager 7.0 in in Window Server 2008 R2 enterprise edition?
When I ran the Solution Manager Master Installer, the Pre-requisite Checker gave a warning message saying that it detected incompatible server version, that the server version is Windows NT 6.1 (Build 7601: Service Pack 1) (I guess it meant Window Server 2008 R2).
=======
The following Windows operating system version is supported: Windows Server 2003 (i.e. Version 5.2) and Windows Server 2008 (i.e. Version 6.0).
Current Windows version: Version 6.1, Service Pack 1.0, productive type: Server.
You can check the current version of you operating system by runningu2026u2026..
========
Can I actually install Solution Manager 7.0 in Window Server 2008 R2? Will this cause problem during the installation/post-installation if I ignore this message?
Thanks,
KC

Hi,
I think it is not straight forward to install SAP Solution Manager 7.0 in MS Window Server 2008 R2.
I am installing Solution Manager 7.0 , the installation encountered error on Create Java Users step (Phase 31 of 44). When I login to SAP solution Manager system through SAP GUI. I encountered this error:
"OS release Windows NT 6.1 7601 Service Pack 1 4x AMD64 Level 6 (Mod 44 Step 2) is not supported with this kernel (700)'
I found that it is because I am installing SAP Solution Manger 7.0 in MS Window Server 2008 R2, which the existing kernel version does not support.
Do you know which kernel I should install?
I browsed in:
SAP Application Components" SAP SOLUTION MANAGER" SAP SOLUTION MANAGER 7.0" Entry by Component" Solution Manager ABAP Stack
SAP KERNEL 7.00 64-BIT UNICODE --> Windows Server on x64 64bit -->MS SQL SERVER
I downloaded:
SAPEXEDB_291-20001361.SAR Kernel Part II (for Basis 7.00) 291
Is this the right Kernel patch I should use?
If it is the right kernel patch file, how do I apply the latest kernel to existing Solution Manager system? Can you give me some guidance on this?
Thanks,
KC

Production SLD in solution manager

Hi,
I have small doubt regarding SLD (System Landscape Directory) in Solution Manager.
We have an Production SLD in Solution Manager dual stack system, and our Production System (Portals, BI, ERP, PI) was configured to Production SLD in Solution Manger.
We are planning to apply patches for our live production Solution Manager System, I know that SLD will stop while doing the Patches on Solution Manager and this will make our production systems stop working.
Therefore I need to know the correct way around this to allow us to patches for our Solution Manager system.
Thanks and Regards
Pavan Morishetty.

Joshi,
Thanks for your quick reply.
But in our company we don't want to change our Production SLD from Solman system to any other System (eg. PI, Portal).
If you any other suggestion please update me for applying the patches in Solman System.
Thanks and Regards
Pavan

Does solution manager 4.0 require SMD Agent?

we have solman 4.0 abap+java with sp11.we are in the process of configuring sol mananager diagnostics for sattlite systems.
for monitoring solution manager java stack it self from solution manager do we need to install SMD AGENT even thogh solution manger it self has SMD server ? still solution manger need SMD AGENT ?

Hi,
SMD Agents are mandatory to run Diagnostics on sattelite systems.
Each Agent is connected to SMD Server and is able to run task or collect information from central request (SMD Server).
If you do not have them, you will not be able to run any tools in Diag.
SMD Server is one sub-component of Solution Manager 4.0.
Regards,
Frederic

Where has to be defined the SLD? PI/XI or Solution Manager?

Hello,
We have a PI production system, already configured and working. Now we are implementing the solution manager system. In both cases we only have productive systems. In which one should we define the SLD?
Thanks and kind regards,
Ana

Hi
Generally I would not recommend to have a Solution Manager Central SLD also used for Productive PI operations
although this is possible to do
We have seen situations whereby issues on the Solution Manager J2EE could affect PI operations generally the Solution Manager J2EE will be used for different purposes and may require different system administration. The dual purpose may also
have performance or sizing implications - technically any sizing done would have been for separate purposes.
The SLD for PI is needed for productive runtime (although there is a XI cache - even so I have seen situations whereby
this cache has limitations)
Customers often opt for the following
Central SLD running on the Solution Manager J2EE stack
Local PI SLD running on a PI J2EE stack
This is because the SLD service is available on any J2EE installation
You can then sync the local PI SLD to the Central SLD in order to build a full system list of all systems in the landscape
see the SLD planning guide at System Landscape Directory (SLD) for details
Best wishes
Stuart

Wily Introscope Version for Solution Manager 7 SPS 17

Hi
We have a solution manager 4 (now 7) running on an ABAP stack only, this was recently upgraded from Solution Manager 3.2 which was installed 3 years ago as ABAP stack only, this server was never powerful enough to have the Java stack added and the project did not require it.
I am now looking to migrate this ABAP Solution Manager 7 to a new server, using ABAP & JAVA so I can make use of Solution Managaer tools like Diagnostics, RCA, WILY etc.
On a sandpit copy I have migrated the ABAP instance to a more powerful server and added the Java Instance from the Solution Manager 4 Installation Master, so I now have a dual stack SM 4, I have patched this to SP17.
I am looking to install Wily Introscope for monitoring, I have read Note 797147 - Wily Introscope Installation for SAP Customers, where it says you should always use the latest version of Wily, which is 8.0.2, but looking at the note, the downloads for Introscope Enterprise Manager and Introscope Workstation are from SAP SOLUTION MANAGER 7.0 EHP 1, but I am not running Solution Manager on EHP1, I am on SP Stack 17.
Looking in the SWDC there are downloads in SAP SOLUTION MANAGER 7.0 -> Entry by Component -> Solution Manager JAVA Stack -> WILY INTROSCOPE ENTPR MGR 8
Is this what I should be using for my SP Stack 17, or should I use the EHP1 version?
Also, setting up the Solution Manager Diagnostics, is there a setup PDF for Solution Manager 7 SP17 ? I cannot find a setup guide for this release, most are for EHP1, I would rather not have to implement EHP1 as part of this migration !
Thanks for any help.
Paul.

Hi Bhudev
Thanks for the reply, I presumed it was the Wily introscope 8 without the EHP1 I required.
As for installation guide, I have think you have misunderstood my question, I already have the wily installation guide from the note location, I wanted to know if there is any Solution Manager Diagnostics setup guides for SP17 ?
When I use transaction SOLMAN_WORKCENNTER --> System Monitoring --> Solution Manager Diagnostics --> Diagnostics System --> Diagnostics Setup --> Setup Wizard
the first 2 (of 23) setups are failing :
SSO The value of profile parameter login/accept_sso2_ticket could not be checked
BI Cannot invoke CCMSBISETUP on host localhost
Warning :
User(BI) Role SAP_BI_E2E does not exist
Then it says :
To complete the Diagnostics Setup, you should perform the following operations as documented in Diagnostics Setup Guide
I cannot find this Diagnostics Setup Guide for SP17 ?
The installation guides are mainly for EHP1, media library under sap-ag.de/diagnostics does not show this setup guide, Master Installation guide does not mention it, so was wondering if anyone could point me in the right direction for this guide ?
Thanks,
Paul.

Configure EP into Solution Manager...

Dear All,
We are trying to configure EP(NW04s-SPS16) into Solution Manager-7.0(SP16). I was installed SMD Agent in EP-Side. and Deployed LM-Service-17(SMD) in Solution Manager JAVA Stack side..
After that i was exported JAVA Technical system from EP SLD and Imported in Solution Manager SLD and observed SLD agent is running in SMD Server.
At this place i strucked. i am not able to get the solution in SMD from SMSY and ABAP connectiviy is not there in SMD and if I run the UPGRADER option i am getting error.
I am getting confusion to read different different SAP Notes and improper guides.
Any one please suggest one proper source about configuration settings in EP side for SMD Agent,SLD,RFC Connections etc and Configuration settings in SMD Server(SOLUTION Manager side),UPGRADER,ABAP Settings,SOLMAN SLD side,etc all.
Kind Regards
Sudhakar

Thanks Samuli,
I tried it..its working for solman but in my ECC (NW 7.31) its not working for web dynpros. Its going to hostname:8001 port and not redirecting to webdispatcher.
Pleae let me know if I am missing something.
Thanks & Regards,
Satyabrat

Multiple Solution Manager Connectivity to 1 Satellite system

HI..
I have a requirement. There is already an existing landscape with solution manager ECC, BI etc. The solution manager is configured for EWA, Maintenance optimizer etc. I now have to install a new solution manager and connect it to the same set of satellite systems so that I receive the EWA, configure MOPZ again. Will this create any kind of a problem and technically how can we do it? I have two ideas for this scenario
1. Connect the new solution manager to the same satellite systems and do configuration as normal. Got this idea from the below link but not sure how it will work.
Re: send EWA report to more than one solution manager
2. Is it possible to push data from the existing solution manager to the new solution manager?
Would highly appreciate technical suggestions. Thx in advance for your help.

Hello,
You need the SMD Agent in order to have ABAP data going to the Solution Manager. Some RFCs are established directly from Managed System to the Solution Manager to extract E2E Change Analysis, Exception Analysis. The Workload Analysis and Host Information (SAPOSCOL) is extracted from WIly EM
Having that said, you can imagine that you cannot have only RFCs and you cannot have only data extracted from WIly EM.
I suggest you to take a look at the FWK Administration in the solman_workcenter, choose the Managed System tab, and start looking into the details of each extractor. Some have an RFC destionation, others have SOLMANDIAG. The SOLMANDIAG are coming from the Solution Manager Java stack, which is responsible to poll the Wily EM.
The reason you need two SMD Agents is because the SMD Agent connects to the ABAP stack, retrieves data, and then connects to the Wily Enterprise Manager. The Solution Manager polls data from the Wily EM and persists it in the BW.
The SMD Agent doesn't support connecting to two Wily EMs at the same time.
So it is required to have TWO SMD agents polling data from the ABAP stack, at the same time, one of them reporting to one Wily EM, and the other reporting to the other Wily EM.
Each solution manager has it's own Wily EM, and it will pull the ABAP data from the Wily EM.
It is not possible to make the two Solution Manager's connect to one Wily EM, since the setup framework needs to see a SMD Agent available to run the setup wizard and to create the destinations. So each Solution Manager needs a SMD Agent running in the physical host.
I hope it is clear for you.
Best regards,
Guilherme
Edited by: Guilherme Balbinot on Feb 6, 2012 9:44 PM
Edited by: Guilherme Balbinot on Feb 6, 2012 9:49 PM

MOPZ has issues calculating stack XML file in SOLUTION MANAGER

Hello,
We have a SOLUTION MANAGER system on NW 7.0 EHP1 SP stack level at initial support stack (ISS).
Recently we upgraded all our R/3 systems to ECC6.0 EHP4 SPS04 and now we are trying to upgrade the stack level to EHP4 SPS07. So we are trying to get a XML file from MOPZ but no luck.
The backend system has all the correct data updated in SMSY and all looks fine but while we try to calculate the stack for EHP4 SPS07 it ends with error like below mentioned.
Please look into the errors and throw some light if anyone has come across the same.
Error details:
System Messages
Type Message Text
Error The Installation/Upgrade Package for Add-on EA-APP L rel. 600 is not available
Error ABAP queue check failed
But the backend system has EA-APPL level at 604, we do not know why it is looking for installation/upgrade package for
EA-APPL 600.
Regards,
Yoganand.V

hi
can you check the sap note
1. Note 1277035 - Solution Manager: EHP4 product data missing
might be this could be the reason for your issue
or
check the thread already discussed the same and the solution also provided
[EHP4 upgrade error on SAPK-603DHINEAPS|EHP4 upgrade error on SAPK-603DHINEAPS]
////////////////It seems that there is a small bug in teh software vector for EA-PS.
Essentially, SAINT prevents you from going forward because it thinks that you don't have the correct version of EA-PS installed.
The solution for this is described in OSS Note: 1143022
"To import EA-PS in a system that already has the level EA-APPL 604, load the attached file ACP_EAPS.SAR into your system (SPAM-> Support Package -> Load Packages -> from Frontend) before you start the import using SAPehpi. Otherwise, an error may occur in the queue calculation, which can be solved by reloading the ACP"////////////////////////
check and update
Jansi

How to add SAP PI 7.1 JAVA stack in solution manager

Hi,
I just added PI system in solution manager.For ABAP stack it is working fine.
Could you please help me that, how can I add java stack of PI system in solution manager?
If it is through NWA in PI what will be the steps?
Regards
Amit

Hi,
could you please more specific as I am new to this one?
In my PI system SLD Data supplier is already configured for other system.
How can I do this using NWA for solution manager.
regards
Amit

Problems with Stack 27 for Solution Manager

We are trying to install the stack 27 ,on Solution Manager based on Nw 701, but despite we downloaded all the packages listed with the MOPZ the SPAM transaction continue to arise consistency problems with the queue.
The package affected seems to be the SAPKITL437, but it's not clear why.
I'm not able to find any Oss notes for that.
Any advise ?

Hi,
Did you check SAP Note No. 1274287 at section for your ST 400 version?
Attention: The Prerequisites for Managing sytem from
SAP Note No. 1274287 must be fulfilled at any time.
Regards,
Aidan

License for Java stack in SAP Solution Manager

Hello!
I installed SAP Solution Manager (ABAP+Java), have ordered the SAP License and applied the license for ABAP part (Tcode: slicense).
Do I also need to update/license the Java Part of my system in Visual Administration?
(Server 0 0_30826 .. --> Licensing Adapter --> choose Tab "Installed Licenses")
Thank you very much!
regards
Thom

Extract from OSS note 953302
In a double-stack installation, only the license keys in WebAS ABAP is relevant. You do not require a license key for WebAS Java for a double-stack installation.
If a license key was installed in WebAS Java, it does not have an effect on the function of the system. You can ignore warnings about expired or soon to expire license keys in WebAS Java.

Solution Manager information for Java stack systems

Hi,
Could someone please help with the setup of Solution Manager, and how to connect to the backend of a Java stack system. For our ERP systems this is working via RFC, but I was hoping to get more information on the procedure for java. I can specify manually via SMSY, but I am sure there must be a setup that can pull the information for the system itself. Could anyone shed some light on this if possible please.
Regards,
Chris

Dear Chris,
ABAP Stacks use RFC as you know for inter system communications.
Java stack systems use Solution Manager Diagnostics.
You will need to run Solman_Setup > Managed System Configuration
First you should visit the link http://service.sap.com/diagnostics
There you will see a link to the media library, and there you will find complete documentation.
Hope you find this information Helpful.
Regards,
Paul

Solution Manager Stack upgrade

Hi,
I am downloading patches for Solution Manager 4.0 from stack 06 to stack 09.
However in the step 3 of download I am not getting new levels of components ST-SER.
Where as if I try to move from stack 06 to stack 08 I get 2 new levels of components ST-SER.
In the schedules for SP Stack 07 and 08 I can see levels SP04, SP05 and SP06
and in SP Stacks 09 it shows levels 700_2006_2 SP00 and 700_2006_2 SP01.
Any idea why I am not getting components of ST-SER when I try to upgrade from stack 06 to stack 09.
Thanks
Parvez Khan

Hello,
It indicates that your solman has java stack installed and you have to download java stack patches as well.
Please follow the solman ehp1 upgrade guide from service marketplace path given in following links and try to understand the process through some other links/search as well
Query related to Solution Manager 7.0 Upgrade to EHP1
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f09c8455-4036-2c10-c7a7-bc3c0879462b?quicklink=index&overridelayout=true
Solution Manager EHP1 Upgrade
Thanks

Solution manager SP stacks

Similar Messages

Maybe you are looking for