Connect Solution Manager to which client for SMD

Hi all,
do I have to connect the solution manager to the productive client of the sat. system?
We have systems with more than one productive client. Can we connect the SDM to more than one client? How can we do this?
Thank you
Timm Funke

Hi,
thank you for this quick response!
So it is possible to configure the landscap with client 000.
Then, when all sat. systems are working fine within SMD, I can configure the producitve clients in smsy (the rfc destinations to the producitve clients). then I can access these clients from SMD.
Is this right?
Kinde regards
Timm

Similar Messages

Connect solution manager to OSS - guide

Hi,
I couldn't find any notes or guide for the process. Can someone guide me
to a guide or note of How to connect solution manager to the oss ?
Best regards,
Dimitry haritonov
Message was edited by:
Dimitry Haritonov

Hi,
I hope below links will help you.
PDF link
https://websmp206.sap-ag.de/~sapidb/011000358700006381312006
SAP Tutor link
https://websmp206.sap-ag.de/~sapidb/011000358700006477102006E.sim
In order to connect solution manager to OSS means you need to configure the systems in solution manager using T-code SMSY.
After configuring you need to configure maintanace optimizer in solution manger.while configuring you need to specify the your S user id.
The above links will help you.
kiran kumar.v

Connecting solution manager to Hp quality center

Dear friends ,
could someone please give me the steps involved in connecting Solution manager to Hp quality center to be used for testing purposes , any documents or links describing this configuration will be greatly appreciated
thanks
Harsha

Hi Harsha,
Check Note: 1059350 - Installing SAP Adapter for SAP Quality Center by HP.
Here you will find all the steps required.
Thanks & Best Regards,
Raghavendra.

Does Solution Manager support Service Report for non-abap?

Does Solution Manager support Service Report for non-abap?
We can schedule and view reports for ABAP but for all the non-ABAP such as J2EE stack (PORTAL) we can not pull out a report.
If the answer is yes please let me know where I can get the documentation of how to setup SLA for PORTAL or non-ABAP.
I found a document on EWA non-abap but non for SLA.

Hi
actually i am in task of setting up ewa for portal.
i had already done with abap components (ewa and sla)
i stronly believe one of the pre-requiste to get sla is EWA.
so i think if u can setup ewa for portal then you can get sla too.
Regards,
Vijay.

Connect Solution Manager to Portal search

Hi Experts,
currently we have the requirement to connect our Netweaver Portal Search to SAP Solution Manager. The search should find documents saved in the Solution Manager.
After searching the SDN I found some hints but came to the opinion that there does not exist any standard approach. Is this true?
Following some more details describing my problem:
The Solution Manager is also used to save project related documents like concepts etc. These documents have to be found if the user enters a query in the NetWeaver Portal. The documents should only be saved in the Solution Manager, so it will be no solution to save the documents in KM.
The hints that I currently found:
Indexing documents - SolMan Document-Management Search
SolMan and Portal - Accessing Solution Manager 4.0 documents using KM
Using KM in Solman (the other way around) - KM in Solman
Any suggestions are welcome.
Kind regards,
Jan Tilo

Hi,
I hope below links will help you.
PDF link
https://websmp206.sap-ag.de/~sapidb/011000358700006381312006
SAP Tutor link
https://websmp206.sap-ag.de/~sapidb/011000358700006477102006E.sim
In order to connect solution manager to OSS means you need to configure the systems in solution manager using T-code SMSY.
After configuring you need to configure maintanace optimizer in solution manger.while configuring you need to specify the your S user id.
The above links will help you.
kiran kumar.v

Using saprouter in solution manager 4.0 environment with SMD

I am currently using Solution manager 3.2 (on SAP basis 6.20 technology). We have not used any Solution Manager functionality that necessitated using the internal ITS, thus all access to solution manager SAP has been through sapgui or RFC. Both these protocols can be routed through saprouter and we make use of this fact, having placed non-natting firewalls between both sapgui users ans SAP; and some ccmagents and SAP.
Now we want to move on to solution manager 4.0 with the JAVA stack and also run SMD. We need SMD because we have also begun using SAP Netweaver 04 Enterprise Portal (Java only SAPs) which we wish to monitor with SAP solution monitor. The portals are all on an internet facing eithernet segment outside the non-natting firewall protecting our ABAP SAPs (including Solution Monitor host).
Is it possible to route SDM agent connections to SDM through saprouter? If so, are there any examples?
What about sapwebdispatcher? Can it also be routed through saprouter? examples?
What about SLD? same questions...
What about Mercury Loadrunner?

No! No! I am not interested in using a saprouter between OSS and my http connection that is effectively http://myhost:5xx00/smd. I am wondering about the SMD agent connection to SMD server (and vise versa). The hosts I want to monitor cannot ping the solution monitor diagnostics machine, but ccmsping via saprouter is possible. Can the SMD agent talk to the SMD server via saprouter? Examples? Can the SMD server talk to the agent via saprouter (perhaps different saprouter)?
SMD agent ---> firewall1 --> intranet --> firewall2/saprouter --> SMD server
SMD server --> firewall2/saprouter --> firewall1/saprouter --> SMD agent

Connection Solution Manager - Wily Enterprise Manager

Hi all,
we want to use SOlutionDiagnostics to monitor our abap and java instances. First, we would like to connect a abap system
to our Enterprise-Manager and watch the results in solution manager.
In transaction http//solutionmanagerhost:port/smd we are able to connect manually to our enterprise manager und log in, but solution manager didn't find the enterprise manager. ( we got the message: all the enterprise manager are offline ).
What could be the reason ?
How is an abap system registered in Enterprise Manager ? For java systems you have to add addiontianl java parameters in configtool. But for abap systems ?
is there any howtoguide, how to connect systems to diagnostic and wathc the results in solman_workcenter für E2E ?
the solution manager diagnostic instance ist already installed and registered over http://>SOLMANHOST>:/smd/go/ADMIN_AGENT
kind regards
andreas

Hello,
Are you using versin 8.0? If not use version 8.0.
Regards,
Paul

Solution Manager 4.0 client copy

Hi all,
We have installed solution manager 4.0 SP 12. We have also done a client copy from 001 to 100 in order to work exclusively in the client 100. I have also changed the client reference in RSADMINA table and the UME from 001 to 100. Finally, when I wanted to implement Solution Manager Diagnostics, I have run the "Setup Wizard" and it created automatically the RFC destination "WEBADMIN" but with client 001. I tried to check everywhere where the old client is still mentioned in both ABAP and Java parts, but no way. Could you tell me please if I forgot something to do after the client copy? Where can I change definitively the reference of the old client?
Thanks in advance for your action.
Regards,

Did you use client 000 as your source client (001 as the user master)? You should not client copy from source 001 as of solman 4.0.
Reference point 6 of note: 1041351
https://service.sap.com/sap/support/notes/1041351
Thanks.
Edited by: Phil May on Aug 26, 2008 7:07 PM

What can Solution Manager 7.0 provide for PI 7.1?

I work with PI 7.1 EHP 1 and have been asked to determine if time/resource should be invested to setup Solution Manager 7.0 EHP 1 to provide monitoring/management of PI. I attended SAP TechEd 2011, and there was a lot of discussion that SM 7.1 would be a significant part of monitoring for PI 7.3. However, since I'm not on those platforms, can you help me understand what SM 7.0 can provide me as a PI Administrator/Support over what I use now (Runtime Workbench & SXMB_MONI)?
The Solution Manager resource on the BASIS team mentioned that SM takes a lot of configuration and I'd have to learn about Business Process Management to make it do anything useful. What I saw at TechEd showed a nice start page that showed data volume, errors, and nice graph. Perhaps that is only for SM 7.1, but it seemed like a nice data view capability.

Hello Tadd,
Wily Introscope will provide you with nice (also real-time if you want) metrics for your PI system (dashboards). You can check for some details here:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f0b96675-87cf-2c10-b489-dee0ac03f782
Solution Manager requires additional steps in order to be able to configure this monitoring scenario. Once your solution manager is installed and running you have to perform initial configuration -> basic configuration -> managed system configuration
In the last step you'll actually configure diagnostics and willy for your PI system.
If the number of managed systems that you have to connect is small this "3 step" configuration can be done in a couple of weeks.
Cheers,
Diego.

Solution Manager on 32-Bit for ECC-6

Hi Gurus,
We need to bring our 32-Bit ECC-6 system on EhP4 as soon as possible.
From installtion documents I found that its two step installation. First install EhP3 and then EhP4 using SAINT.
To install EhP we need use Solution Manager. Currently we dont have Solution Manager installed. Our first step would be installing Solution Manager. There are two options available:
1. SAP Solution Manager 7.0 including SAP Enhancement Package 1.
2. SAP Solution Manager 7.0.
As everywhere its written we can not install solution manager on 32-bit but some some threads say we can do.
Confirm that Solution Manager 7 cannot be installed on a 32-bit windows sys
Assuming that we can still install Solution manage on 32 bit, first we need to install EhP3, which solution manager version should we use 1 or 2?
Thanks in advance
Regards
Shreeshail Ganiger
Edited by: ssganiger on Nov 5, 2009 6:48 AM

Hi Shreeshail,
Please use opton 1. This way you can choose to install either EHP3 or EHP4 (as your case maybe).
Also, you wouldn't need to upgrade solman to ehp1, as ehp1 comes with a lot of corrections which otherwise you will have to manually implement on a Solution Manager 7.0 system.
Cheers
Rishi

Solution Manager as an aid for ASAP

Hi Folks,
I am new to solution manager, can anyone let me know how these are helpful, is there any material which I can refer.
Your help would be highly apprecited.
Regards,
Ravi

HI Ravi,
PL EXPLORE service tons of material is there...
Please have a look at:
Self Training Matrials:
http://service.sap.com/rkt-solman, then click on your Solution Manager release, then "Solution Consultant"
Online Documentation:
http://help.sap.com/saphelp_sm40/.../frameset.htm

Which clients for certain functionalities

Hi all,
I'm configuring SAP ERP 6.0 SR2 after installing. I use 2 physical servers, one for DEV+QAS, one for PRD.
My 2 SAP systems contain ABAP+Java with all software units installed.
In my DEV+QAS system, I don't know whether or not I should use client 001. As DEV role, it should have 1 client for GOLD, 1 for Sandbox, 1 for Unit-Test; and as QAS role, it should have 1 client for Integration-Test.
- Should I use client 001 as any client above or I use client 000 as source client of copying?
- Because client 001 is the client for J2EE portal, should I use it as portal or change the portal client to another client? I don't know how to make another client as a QAS portal client (I'm not sure it's right or wrong, may be wrong). Or we're ONLY able to use 1 client for J2EE portal? If yes (1 portal client only), do I have to configure portal manually in the PRD system's portal also without any transport?
- If possible, someone please let me know your current System Landscape with Transport for reference.
Thanks,
Toan Do

Toan,
Use 000 as the default client when setting up the first new client in the DEV system. Subsequent new clients can and should be created from the new customizing client you create by copying 000.
You will want at least one master customizing client (which you call 'gold') and one integration test client in QAS. On whether you need to create the remaining clients that you mentions depends on your organization (for larger organizations your answer is probably a yes).
Hope that helps.
J. Haynes
Denver

Solution Manager 4.0, waiting for response

Hi,
I successfully installled SAP Solution Manager 4.0 with SAPDB and Windows 2003.
My problem: SAP System is running (looks all fine in sapmmc), but if I connted to the system with SAP GUI I get the message "waiting for response..." . This message is still there after one hour. So the logon isn't successful, any help?
Thanks.

Hi Andreas,
from the DB perspective, please take a look into the SAP DB knldiag file (found in the Rundirectory of the DB). You can run 'xinstinfo <DB-SID>' from the commandline to find out the path of your Rundirectory.
For example, maybe your SAP DB instance's log is full.
Additionally, I'd take a look into the workprocess trace files (on the R/3 - application- side) to see if there are any errors there.
Regards,
Roland

Which client for BI in NW2004 ?

Hello,
after upgrading a ERP to 2004 there is the question to integrate the BW system in a client of the ERP.
I heard about recommandations to use a different client and not the ERP client for BI functions. (We did not activated the BI client via customizing)
What are the reasons for not using the ERP client for BI or is there no restriction and I can drive ERP functions (in this case EC-CS) and BI functions together in a client ?
Kind regards, Hinrich Benitt

Hi Wai-Hon,
In general, we recommend to keep the SAP BI system on a separate box, due resource consumption, etc.
There is technically no restriction to run the SAP BI system also on the same box, yet it has to be in a dedicated (separated) client. This is necessary for the loading mechanisms (logical system) and for some client-dependant tables used by the SAP BI system.
Cheers
SAP NetWeaver BI Organisation

"Connection refused" when using Java client for Web Service

I deployed a web service to Weblogic Server 7.0 running on Windows 2000. I can
use IE browser to see its WSDL perfectly but when I run the Java client, the proxy
method call generates the following error:
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:426)
at java.net.Socket.connect(Socket.java:376)
at java.net.Socket.<init>(Socket.java:291)
at java.net.Socket.<init>(Socket.java:119)
at weblogic.webservice.binding.soap.HttpClientBinding.createSocket(HttpC
lientBinding.java:412)
at weblogic.webservice.binding.soap.HttpClientBinding.createSocket(HttpC
lientBinding.java:390)
at weblogic.webservice.binding.soap.HttpClientBinding.send(HttpClientBin
ding.java:246)
at weblogic.webservice.core.handler.ClientHandler.handleRequest(ClientHa
ndler.java:34)
at weblogic.webservice.core.HandlerChain.handleRequest(HandlerChain.java
:131)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:417)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:359)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:225)
at weblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
181)
at weblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
207)
at CenterWSClient.main(CenterWSClient.java:73)
javax.xml.rpc.JAXRPCException: Failed to send request:java.net.ConnectException:
Connection refused: connect
at weblogic.webservice.core.handler.ClientHandler.handleRequest(ClientHa
ndler.java:37)
at weblogic.webservice.core.HandlerChain.handleRequest(HandlerChain.java
:131)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:417)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:359)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:225)
at weblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
181)
at weblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
207)
at CenterWSClient.main(CenterWSClient.java:73)
Exception in handler's handleRequest().
java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: Conn
ection refused: connect; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: Connection refused: connect
at weblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
186)
at weblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
207)
at CenterWSClient.main(CenterWSClient.java:73)
Caused by: javax.xml.rpc.soap.SOAPFaultException: Connection refused: connect
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:459)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:359)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:225)
at weblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
181)

In your client program, when you do "new XXX_Impl(String wsdlurl)", did you
pass in the wsdl you were hitting with browser?
-Neal
"Ray Yan" <[email protected]> wrote in message
news:[email protected]...
>
I deployed a web service to Weblogic Server 7.0 running on Windows 2000. Ican
use IE browser to see its WSDL perfectly but when I run the Java client,the proxy
method call generates the following error:
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
atjava.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:426)
at java.net.Socket.connect(Socket.java:376)
at java.net.Socket.<init>(Socket.java:291)
at java.net.Socket.<init>(Socket.java:119)
atweblogic.webservice.binding.soap.HttpClientBinding.createSocket(HttpC
lientBinding.java:412)
atweblogic.webservice.binding.soap.HttpClientBinding.createSocket(HttpC
lientBinding.java:390)
atweblogic.webservice.binding.soap.HttpClientBinding.send(HttpClientBin
ding.java:246)
atweblogic.webservice.core.handler.ClientHandler.handleRequest(ClientHa
ndler.java:34)
atweblogic.webservice.core.HandlerChain.handleRequest(HandlerChain.java
:131)
atweblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:417)
atweblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:359)
atweblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:225)
atweblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
181)
atweblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
207)
at CenterWSClient.main(CenterWSClient.java:73)
javax.xml.rpc.JAXRPCException: Failed to sendrequest:java.net.ConnectException:
Connection refused: connect
atweblogic.webservice.core.handler.ClientHandler.handleRequest(ClientHa
ndler.java:37)
atweblogic.webservice.core.HandlerChain.handleRequest(HandlerChain.java
:131)
atweblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:417)
atweblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:359)
atweblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:225)
atweblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
181)
atweblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
207)
at CenterWSClient.main(CenterWSClient.java:73)
Exception in handler's handleRequest().
java.rmi.RemoteException: SOAPFault:javax.xml.rpc.soap.SOAPFaultException: Conn
ection refused: connect; nested exception is:
javax.xml.rpc.soap.SOAPFaultException: Connection refused: connect
atweblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
186)
atweblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
207)
at CenterWSClient.main(CenterWSClient.java:73)
Caused by: javax.xml.rpc.soap.SOAPFaultException: Connection refused:connect
atweblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:459)
atweblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:359)
atweblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:225)
atweblogic.jws.proxies.CenterWSSoap_Stub.update(CenterWSSoap_Stub.java:
181)

Connect Solution Manager to which client for SMD

Similar Messages

Maybe you are looking for