EP 7 systems in Solution Manager 7 for EWA activation

Dear Expert,
Greetings from Partha.
I need to include our EP 7 systems in Solution Manager 7 for EWA activation. Current lanscape scenario
Solution Manger 7.00 Installed
EP 7.00 Installed
No central SLD configured and all the system have local SLD.
1. As per the installtion guide & SAP notes we need to install
a> SM Diagnostics Agent & Wilo Introscope in Solution Manager (manging system).
b> Diagnostics Agent in every manged system(s).
For managing system we can download Diagnostics Agent installation DVDs from SAP Service Marketplace
at: http://service.sap.com/swdc --> Download --> SAP Support Packages --> Entry by Application Group
--> SAP Technology Components --> SAP SOLUTION MANAGER --> SAP SOLUTION MANAGER 7.0
--> Entry by Component --> Agents for Managed systems --> DIAGNOSTICS AGENT 7.11
--> <choose operating system of managed>
Our Solution Manager 7 is already installed and @SPS 17. My question is
1. Can we use the same file for SMD installtion in Solution Manger or we need to download it from some other area ?
If it is different then kindly let me know what are the DVDs to be downloaded and from where?
2. In our Managed System SMD installtion we have decided for
--> Installation Strategy as Direct Solution Manager Registration
But what strategy we should take for SMD installation on Sol Man 7 that is
Local SLD (wrt Sol Man) Registration or Direct Solution Manager Registration
3. What is the need for the SAP Host Agent Installattion ? Is it mandatory ?
Help will be appreciated.
Regards,
Partha

1. As per the installtion guide & SAP notes we need to install
a> SM Diagnostics Agent & Wilo Introscope in Solution Manager (manging system).
b> Diagnostics Agent in every manged system(s).
For managing system we can download Diagnostics Agent installation DVDs from SAP Service Marketplace
at: http://service.sap.com/swdc --> Download --> SAP Support Packages --> Entry by Application Group
--> SAP Technology Components --> SAP SOLUTION MANAGER --> SAP SOLUTION MANAGER 7.0
--> Entry by Component --> Agents for Managed systems --> DIAGNOSTICS AGENT 7.11
--> <choose operating system of managed>
Our Solution Manager 7 is already installed and @SPS 17. My question is
1. Can we use the same file for SMD installtion in Solution Manger or we need to download it from some other area ?
If it is different then kindly let me know what are the DVDs to be downloaded and from where?
Check the pdf attached in note 1234387 - Inst. 7.1 EhP1 - Diagnostics Agent installation
If you have SP17, you must follow note 1357812 and install Diagnostics Agent 7.01 SR1
2. In our Managed System SMD installtion we have decided for
--> Installation Strategy as Direct Solution Manager Registration
But what strategy we should take for SMD installation on Sol Man 7 that is
Local SLD (wrt Sol Man) Registration or Direct Solution Manager Registration
It doesn't matter what strategy you'll decide. You could decide Direct Solution Manager registration
3. What is the need for the SAP Host Agent Installattion ? Is it mandatory ?
As you have solution Manager SP17, you can't install Saphostagent 7.11 and for this reason you can't use SAphostagent.
Agent 7.01 => No Saphostagent
Agent 7.11 => Must install saphostagent
Agent 7.20 => Already have SAPhostagent installed

Similar Messages

Solution Manager for EWA

I already configured my EWA (SDCCN), but then I realize that EWA need Solution Manager to run.
I need to know how to install Solution Manager for my EWA? Do I need to install in separate server? Or there are others option for me to consider?
Pls help me to figure this out

Hello Hazha!
I don't know how you can configure in SDCCN an EWA session without the Solution Manager, but if you did so, you can send your EWA data to sap, where they will be processed and where you can find them in your inbox.
You need a well functioning SAPOSS RFC destination (TA OSS1).
SDCCN -> Goto -> Settings -> Task Specific
You will get a window with a tree list. Open RFC-Destinations -> Settings and click on the settings icon.
In Dialog RFC destinations, Tab Destinations you might click on the Info-Icon (botton) and you will get documentation. Click now on the Change Icon.
You will now get a new icon "Create destination to SAP OSS". Please use it, it should generate the destination SDCC_OSS.
Please test the destination.
Now you can insert this RFC-destination into the task attributes of your EWA-Session, system-id should be O01.
Bye
PS.
You might also have a look at the documentation at http://service.sap.com/ewa -> Media Library
Message was edited by: Riccardo Escher

Connection From Satellite System to Solution Manager for key users

Hi All,
Can anybody suggest which RFC connection/destination should be maintained in BCOS_CUST table under satellite system to connect to Solution Manager.
1. SM_SSMCLNT010_TRUSTED
2. SM_SSMCLNT010_BACK
I don't want user to Login to solution manager while creating a support message. They should create a support messsage seamlessly from satellite system.
Any help is greatly appreciated.
Thanks...

Thakur,
Sorry for the cryptic answer back there - read it myself and it didn't make much sense to me either so here we go with the seamless way to allow users to create service messages.
There are 2 ways to do this - 1 way is to use a connection like the 'BACK' connection but if you do this - all user tickets entered will have the username of the 'BACK' connection logon id as the message creator. The other way is to use the trusted connection so the userid of the person logging the message is transfered with the created ticket.
I will assume that you want to preserve the unique userid and use trusted connections. So here we go:
Step 1 - Go into BCOS_CUST on the Satelite and put in your TRUSTED RFC Connection as the detination for the Service Messages - either use the one that Solman created when generating or make your own ABAP Trusted Connection.
Step 2 - All users in Satelite and in Solution Manager need to have Authority Object S_RFCACL assigned to their userid's so they can use the Trusted RFC Connection (this is not in SAP_ALL or SAP_NEW).
Step 3 - All users that will use this method of creating service tickets need both a userID and a BP with the respective system keys to allow them to enter tickets for those Satelites.
That is all there is to it assuming that all issues with Trusted Connections have been worked through already (test this in SM59 by going to your 'TRUSTED' connection on the Satelite and execute the RemoteLogon button - you should be sent to the Solution Manager with out having to logon).
If this answers your question, please set this message to answered.
Edited by: David Milliken on Jan 25, 2008 1:55 AM

System Monitoring for Satellite System in Solution Manager

Hi,
I configured satellite system in solution manager through SMSY,and i created solution in dswp.I want to configure system monitoring through ccms agent,how to install ccms agent,how to configure system monitoring for satellite system in solution manager .Please guide me.
Thanku

Hi,
In Solution manager I did below steps. :
1) Activated background dispatching in Rz21 (Client : 000).
2) Created CSMREG user (In RZ21)
3) Generated the configuration file for agent (CSMCONF).
I down loaded the ccmagent_35-20001346.sar file.
What are the steps i have to do in satellite system.
Thanku

How to create Rfc for EP system in Solution manager

Dear experts,
I am doing ChaRM configuration for my EP system ( java only).
I also configured CTS+ successfully but we want to integrate this with Chram in solman.
I have done all configuration according to standard doc for ChaRM.
But when creating project from solar_admin it is giving "   NO RFC for DEP system"
so please suggest me how to create RFC for java system in Solution manager.
thanks in advance
dhiraj

Hello,
You need to setup an ABAP communication client and system, that's done through the TMS settings:
For source system:
- CTC                                              1
- CTS_SYSTEM_TYPE                          JAVA (others for a MDM system)
- NON_ABAP_SYSTEM                          1
- COMMUNICATION_SYSTEM:              (SAPSID of the ABAP communication system (e.g. the domain controller))
- NON_ABAP_WBO_CLIENT                    (Client of the ABAP stack on which the Transport Organizer Web UI (CTS_BROWSER) is activated and will run.)
- WBO_GET_REQ_STRATEGY                 TAGGED
- WBO_REL_REQ_STRATEGY                 MANUAL
For quality and production Java system (target systems):
- CTC                                              1
- CTS_SYSTEM_TYPE                          JAVA (others for a MDM system)
- NON_ABAP_SYSTEM                         1
- COMMUNICATION_SYSTEM:                 (SAPSID of the ABAP communication system (e.g. the domain controller))
- DEPLOY_WEB_SERVICE                       CTSDEPLOY
- DEPLOY_DATA_SHARE:
When this is done correctly, you will see the fields ABAP communication system and client populated in SMSY.
When ChaRM needs to operate on the non ABAP systems, it will take the RFCs for the communication system and client.
Best regards,
Miguel Ariñ

Questions on "FAQ - SAP Solution Manager for VARs"

Hi,
I just got through the FAQ - SAP Solution Manager for VARs, but have some further questions:
For me it is not quite clear which connections are necessary for which VAR scenrio.. currently we have setup the service desk in our solman. Customer's aren't linked to the solman yet - we have saprouter-saprouter connections. Connecting them via SAP support backbone is an interesting option, especially for incident management. To get this working we should follow note 1124718 right?
But what about the other scenarios like maintenance optimizer and ewa monitoring? I guess for that we definitly need to build up RFC connections to each relevant customer system (~300+x)?! I think it will be hard to handle so many connections - just consider if a customer is cancalling the maintenance contract, everything needs to be removed again... best would be to have a central communication point...
For MOPZ we need up-to-date system information. So everyone is talking about SLD. Do you also recommend this option? There we need again a connection (direct to SolMan SLD or via external SLD on customer side).
According to the FAQ there is a workaround for ewa monitoring for customers with security doubts.. is this also working for non-ABAP components? We need SMD and WI for generating ewas for JAVA systems...
With regards to Enterprise Support contract: ewa only need to be monitored for productive systems? Can a customer be charged if they want to have ewas monitored for other sytems too? How long do we need to keep the ewas (1 month, 3 months, half year) before they are deleted? Are there any specific requirements?
All the work to get these scenarios working.. is this covered within the Enterprise Support contract? Can the customer be charged for work thats done by the VAR in their system (e.g. RFC connections, SDCCN, SLD,...)?
Sorry for this long text.. hope you have some helpful ideas!
Regards,
Richard

Hello Richard,
(1) regarding network connections see document [Draft:Technical Support Network Connections for VAR Scenario|http://service.sap.com/~form/sapnet?_SHORTKEY=00200797470000089947&_OBJECT=011000358700000880802009E] as overview and with a lot of detailed information.
(2) yes, you have to setup once all your customer connections at the beginning but then only add/remove with customer contract changes
(3) the workaround by sending by email can handled a anexception. EWA has to be done for productive systems like nowadays done by SAP. Additional EWA services could meas additional business case for a VAR - that's contract between VAR and customer.
(4) whatever you think may be a business to sell - do it ! (and get a monetary bonus from your boss
Kind regards
Heinrich

Using more than one Solution Manager for different usages

Dear all,
we are using a solution manager system with >100 connected systems.
The system should primarily be used as service desk system, but is also used for BC issues (e.g. MOPZ,...) at the moment.
We have to implement a central monitoring system (CEN) using the CCMS infrastructure.
It is recommended to use a seperate system for this issue, because of high performance requirement and the requirement to have the newest support packages for CEN+MOPZ.
Because of that recommendation we are thinking about installation of a second solution manager system which should handle all BC and Monitoring (CEN+SolutionManager-Monitoring) issues.
Do you have any experience with such a landscape? Are there known problems respectively is such a landscape possible/workable? How should the systems be connected? ( client system<=>solman / solman<=>solman )
I regret that I could not find any official landscape recommendations from SAP for big landscapes (VAR environment)?
If you know any applicable documents, please let me know.
Thank you for your help.
Best regards,
Sascha

Hi Sascha
Technically Solution Manager is being billed as the Central system for everything Service Desk, MOPZ and CCMS - one central location for all scenarios
One of the reasons for this is lifecycle management -- monitoring or EWA scenario finds a problem, service desk raises the issue, charm or mopz implements the solution and it is tested and distributed and the whole lifecycle is documented one system. Indeed I am aware of no functionality to integrate scenarios between Solution Manager systems - each Solution Manager system in your proposal will be standalone for each scenario
I can't provide guarantees because SAP recommend 1 Solman PRD only, but it might be possible to use another PRD Solution Manager system (or client) for scenarios that not already setup in the existing Solution Manager system - this certainly is the most possible way to have 2 PRD Solution Manager systems (or clients) running in parallel.
The key thing to be aware of is RFC conflicts - as each scenario usually has its own RFC this might be avoided - however
do watch out for situations where scenarios share RFCs or you if find RFCs existing with the same name OR client and SID in any systems in the following landscape
Landscape 1 - Satellite System 1 to Solman System 1 Service Desk, MOPZ
Landscape 2 - Satellite System 1 to Solman System 2 CCMS, EWA
Best wishes
Stuart

FAQ - SAP Solution Manager for VARs

You can find further technical questions around configuration & functionalities in a comprehensive
FAQ to SAP Solution Manager for VARs.
This FAQ covers questions and answers around:
    > SAP Solution Manager, enterprise edition
    > SAP Solution Manager VAR setup: configuration of Service Desk
    > Work Center Service Desk: functions & configuration
    > Work Center System Monitoring: setup of SAP EarlyWatch Alert
You can access the FAQ directly thru the following link [FAQ - SAP Solution Manager for VARs|http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000722612&_OBJECT=011000358700000490172009E].
Navigation path: SAP Service Marketplace > SAP Support Portal > SAP Support Infrastructure > SAP Solution Manager > SAP Solution Manager for Partners > Information for Service Provider > Training and HowTo Documents > Administrator
Please notice: The FAQ will be updated from time to time.
Edited by: Susanne Schlehf on May 4, 2009 2:48 PM
Edited by: Susanne Schlehf on May 18, 2009 12:56 PM

Hello Richard,
(1) regarding network connections see document [Draft:Technical Support Network Connections for VAR Scenario|http://service.sap.com/~form/sapnet?_SHORTKEY=00200797470000089947&_OBJECT=011000358700000880802009E] as overview and with a lot of detailed information.
(2) yes, you have to setup once all your customer connections at the beginning but then only add/remove with customer contract changes
(3) the workaround by sending by email can handled a anexception. EWA has to be done for productive systems like nowadays done by SAP. Additional EWA services could meas additional business case for a VAR - that's contract between VAR and customer.
(4) whatever you think may be a business to sell - do it ! (and get a monetary bonus from your boss
Kind regards
Heinrich

Add sap R/3 enterprise system in solution manager SLD

Dear All
Required solution manager configuration documents.
We have DEV QAS and PRD server on SAP mySAP ERP 4.7 ( SAP R/3 Enterprise )
And during the installation of solution manager I select u201CConfigure a Local SLD u201C
Which steps I follows to connect or configure my sap system with solution manager ( SLD ) then I will configure central monitoring, TMS management, Helpdesk etc
Who to Configure SLD Bridge ( in SLD Server ) ?
in which system Run Transaction RZ70 ( In SAP R/3 Enterprise ) ?
and how to Verify that my system is connected and working fine With SLD
Please help me regarding u201C configuration solution manager u201C
Regards
Shahid

Hi
Visit for step by step details of Standard Configuration of Basic Settings
http://service.sap.com/rkt-solman-->SAP Solution Manager 7.0->Technology Consultants & System Administrators->Technical Configuration->just drill out there you can find lot of simulator how to install and configure solution manager
http://www.wilsonmar.com/sap_solution_manager.htm
/people/federico.babelis2/blog/2006/04/14/service-desk-configuration-guide-for-dummies
Regards
Uday

Transport Management System with Solution Manager

Dear all,
Do you know the function transport management system(TMS) with solution manager, I already search in SAP document but not found this function.
Do you know how to config solution manager for TMS and documents related with this function please guide for me!
Thanks all very much !

Hi,
Check this link.
https://websmp103.sap-ag.de/~sapdownload/011000358700000508502008E/ChangeRequestManagement.pdf
Hope this answers your questions.
Feel free to revert back.
-=-Ragu

How to add EP(DEV and QAS and PRD systems in solution manager)

Dear Gurus,
I want to include EP dev and qality and prodution systems in solution manager .
While installation of EP(only ASJAVA it is not having ASABAP) i selected solution manager as a Central SLD. But i deleted the systems in solution manger and recreated it again. I created all the systems and datatabae and logical components but in maintenane optimizer it is showing only production system but it is not showing development and quality systems in maintenance optimizer.
How to see developmnet and quality systems in maintenace optimizer.
Same thing for ECC also.
ECC dev and quality systems installed in the same server.
In maintenace optimizer it is showing only dev sysetm it not showing quality sysetm.
Can any body help this probelm.
Thanks & Regards
Rao.

I think you need to adjust your filter settings in the initial screen of MOPZ.
It's in the right top corner.

Add BI System in Solution manager

Hi All,
I need to add BI DEV, BI PRD Systems to solution manager. As per my understanding first i need to create logical systems, after wards i have to add this system in SMSY.
I will be glad if some one can post ur suggestions and procedure to add this
Thanks

Hi,
this is same for all the system. only you have to select appropriate product instance
please refer this screenshots here [SMSY Set Up|http://www.way2sap.com/sap-article/adding-a-sap-system-to-smsy-of-solution-manager-1907/]
get the other set up guides on service.sap.com -> release and upgrade info -> installation and upgrade guide -> SAP components -> SAP Solution Manager -> Operation guides.
Thanks
Jansi

How to configure CTS+ for Solution Manager for XI 3.0

Hi ,
We are working on XI 3.0 SP 20 and Doing a file system based transport of .TPZ files. We observed that there is a possibilit of misssing the objects while tranporting. So we are planning to set CTS+ with our Solution Manager.
Question:
1. Can we configure CTS+ through the latest version of Solution Manager for XI 3.0 landscape?
If Yes .. How? If No... Why?
2. Is there any way to make the the transport automated like ABAP tranports.
If there is.... Please send the link or documents..
Thanks
Manoj

Hi Venkat,
Thank you for the Demo. The Demo gives me information about the CTS+ setup. I am looking for the compatability of CTS+ for XI 3.0.
We have Solution Manager 7.1 setup in place.
Please let us know if we can setup CTS+ on solution Manager (7.01 EHP1) and use it to transport XI 3.0 SP20 IR/ID objects across the XI landscape.
Regards,
Manoj

Monitoring a non-SAP satellite system in Solution Manager

Hi Folks,
I have two quick questions.
1.) What is the proper procedure/tool for monitoring a non-NW system in Solution Manager? Should I be able to use sapccmsr and saposcol on these systems?
2.) What is the proper way to connect a non-NW system to the SLD? Should I be able to use saposol and sldreg for these?
Background:
- My Solution Manager system is a NW70 EHP1
- Solution Manager Diagnostics is installed and monitoring my ABAP and Java systems
- I have my CCMS agents registered back to my CEN for the ABAP and Java systems
Satellite systems:
- Multiple Wintel servers (both IA32 and x64) that are running;
o standalone SQL server databases
o BOE/BOBJ
o BPC for Microsoft
Section 4.8 of the Monitoring Setup Guide (CEN SAP Netweaver 7.0 SPS18) states that I should be able to monitor a standalone database.
My confusion isu2026 in the absence of an SAP filesystem (kernel) and the standard SAP environment variables that get set during an install, how do I register the agents? The executables do not want to launch.
Thank you,
Bill

Dear William,
Monitoring of NON-SAP systems is not actually done on the solution manager system itself. The solution manager system gets its feed of alert information from the satellite, specifically CCMS. For SAP systems, alerts from CCMS are set up and activated by default. For Third-Party systems you have to be ablke to set up the interface to feed monitoring information from your non-SAP software to SAP's CCMS infrastructure.
You can get more information on CCMS agents via the website at http://service.sap.com/monitoring.
Go to "system Monitoring and Alert Management" > "Monitoring in Detail".
I hope this information is helpful.
Regards,
Paul

One Solution Manager for different customers

Hi Guys!!
I am configuring a Solution Manager for different customers wich have a different S-users and different users to manage the solution manager system.
My problem is that there is only one SAP-OSS RFC destination where I can fill the data only for one of the S-users. From "solution_manager" transaction you can indicate the S-user too (Edit - Global Settings) but the same problem occurs, I can fill the gap only with one S-user and I have to change this one when I want to work with different S-user.
Can i configure the system to indicate different S-users depens on the user who I use to logon to solution manager system?
Thank you very much in advanced,
Edorta.

Hi Edorta,
you did not mention, which scenarios do you plan to use.
Functionality to use the SolMan for many customer numbers is already available or will be added in future Support Package Stacks.
It has been already added for
- Maintenance Optimizer
Note 1021275 - Maintenance Optimizer: RFC Destinations for Partners
- Forwarding SAP Messages (with different S-Users resp. customers)
IMG: Solution Manager -> Scenario-Specific Settings -> Service Desk -> Value Added Reseller
Check for SAP Notes on component SV-SMG* with key word "VAR" (as Valued Added Reseller), "Service Provider"
Best regards,
Ruediger Stoecker
SAP Notes added
Message was edited by: Ruediger Stoecker

EP 7 systems in Solution Manager 7 for EWA activation

Similar Messages

Maybe you are looking for