Connection XI - SLD - Solution Manager

Hi everybody,
I am facing the following problem.
The SLD is installed in the Solution Manager Host. Solution Manager was installed before XI
was installed. So, the managing of the SLD is carried out in the SLD of the Solution
manager. However I can only import the objects from the SLD to the Integration Builder if I
create the objects in the Local SLD of the XI. How can I connect the XI system with the SLD
of the Solution Manager? I have the same problem with proxys in R/3 (SLDAPICUST).
So, Do I have to create the objects in SLD XI Host or by means of Solution Manager???
Thanks in advance.
Regards.
Carlos

Depends on your version of SAP...
I would say yes to be on the safe side...
PI7.0 creates these entries but does not use them.
XI3.0 does (i think upto a certain patch level...).
This is always a useful tool...
http://help.sap.com/saphelp_nw04s/helpdata/en/78/20244134a56532e10000000a1550b0/content.htm

Similar Messages

SLD Solution Manager & connections to other SAP productes in landscape?

Hi All
I have installed Solution Manager 4.0 SR3 in order to implement global monitoring across our landscape and I have decided to install and use the SLD.
I have set up the SLD and followed the post installation guide, however I now want to connect all of our sytems to it so that Stack , version Information, components etc can be transfered to the SLD automatically. Once this is done in Solution Manager (SMSY) I can then view all of my systems.
Firstly is this possible and does anyone have any information on how to do this?
Many Thanks
Phil

Hi Phil,
It is possible.
Firstly in satelite systems you need to enter your SLD server info using transaction SLDAPICUST. Here you specify your Solution Manager system as host, user usually j2ee_admin and j2ee_admin's password. The alias can be anything and default port is 5<instance no>00.
Secondly, you test the connection with transaction SLDCHECK. If it's green it's OK, you can ignore most warning messages.
Then last you setup data collection and job scheduling and you do this in transaction RZ70.
Sorry don't have any reference to notes or documentation but each transaction above should make sense of what I mentioned.
Hope this helps.
Regards,
Nelis
Message was edited by:
Nelis Lamprecht

Connection Establishment between Solution Manager and BW

Hi,
Could you pl let me know the steps to follow for establishing the connection between Solution Manager and BI 7 system?
Thanks & Regards,
Vijaya

Thanks!

Generate Remote Connection for our Solution Manager 7.1

Hi,
In order to complete installation of SAP Solution Manager 7.1, we need to send a message to SAP Support through SOLMAN but we still don't have a RFC connected to the SAP backbone.
Anyone get a process easy-to-understand and to set up, we're in France and it's very urgent.
Currently we've set up correctly installation of back-end and front-end, we can logon to solution manager and it's all.
If you have ever done an installation of Solution Manager with Remote Connection, please join me.
Best regards,
William

Hello,
Did you download and follow the Installation Guide?
http://solman_srv:8000
Is NOT a Fully Qualified Domain Name (FDQN)
A Fully qualified name would have the format
Host.Company.Domain
i.e. http://service.sap.com is fully qualified, while http://service is not.
This is the first problem you are having, but I suspect you have more, as at this point in the installation SAP* should already been disabled and your Admin user accounts setup. This would have been durng the post installation steps, which are performed prior to Solman_setup.
Yes, you need to defined parameter icm/host_name_full to equate with the FQDN of solman-srv.
Second thing is that client 000 and client 001 are reference clients provided by SAP. You don't want to be changing these clients. You want to be copying these reference clients to your clients and then configuring those clients, not your reference clients, as this will cause a problem when you need to create new clients.
Did you follow the installation guide carefully? I would recommend you review, because it covers off these things, so you shouldn't be running into these errors at this point in the configuration phase, if you followed the Installation guide (especially the POST Installation steps)
Regards,
Paul

Why NWA/SLD/ Solution manager redundancy

I am just curious why systems like SLD and Solution manager both contain the same information? Like systems, software componenets etc.
Another question, I was just reading the docs for NWA administrator and I see that they are suggesting to do some ccms monitoring through NWA. Doesnt solution manager do this already? How many places are there to do monitoring, which ones are best???
Does anyone have Project experience and best practices for this?
Thanks

Hello Jeremy,
please note that Solution Manager its own landscape information (tcode SYMSY), which can also be synchronized with the SLD.
Solution Manager is just another display option for monitoring data. The actual monitoring data is retrieved by the CCMS monitoring infrastructure, which is also used by the NWA.
Java-only monitoring data is also retrieved by NWA via JMX. Even in a Java-only landscape, you must have a double-stack system as central system in order to display availability data provided by the CCMSPING agent.
To monitor an ABAP-only landscape, you do not need NWA for the time being.
To monitor a "mixed" landscape, you should use NWA on a double-stack system.
For more information, you can use the following quick links in the SAP Service Marketplace: /nwa, /monitoring and /javamonitoring.
Regards,
Dieter

Registering IDM to SLD and Solution Manager

Hi Everyone,
Is there any way to register IDM to SLD/Solution Manager?
Right now, I am having it as a Portal Component only for the UI, with a standalone server for the IDM Dispatcher.
Any idea,
Appreciated
Manuel

Hi Manuel,
This was recently discussed. Please take a look at these threads and see if they are helpful:
Identity Management 7.2 and LMDB and SAP IDM integration in SLD.
Hopefully they will be of some help.
Regards,
Matt

Is it possible to connect a DEV System to more than one SAP Solution Manage

Hello,
My system DEV is already connected to a first SAP Solution Manager, I would also like to reconnect the same system so that it communicates and will be monitored by a second SolMan.
Is it possible to do so and the do the operation involve any risks ?
Thanks for your help
Regards
Ben

Hello,
This is possible in many scenarios. Often this is done to distribute load, for example on Solution Manager will do the Service Desk Function, one may do ChaRM, one may be doing Monitoring & Reporting, one may be doing Diagnostics.
In these cases a managed ssytem can be connected to many Solution Manager systems.
However as Mateus has pointed out, you cannot connect one managed to two Solution Managers and do SMD on both Solution
Manager systems, but you can have more than one Solution Manager doing Diagnostics.
Even in the case of EWA, while you can connect a Managed system to multiple Solution Manager systems and have then generate a report, one of the Solution Manager systems must be defined as the Master.
So the specific scenario may place some restrictions on connecting a managed system to more than one Solution Manager,
but for most instances it can be done.
Regards,
Paul

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

SAP TAO connection to Solution Manager

Hi All,
I have installed SAP TAO 2.0 and I need to connect it to solution manager for license. In TAO configuration, in 'License' tab; all systems stored in SAP Logon are supposed to be listed to select solution manager instance. But in my case I can't find solution manager instance although its parameters are stored in SAP Logon and I have connected to it several times. How can I make TAO read all the systems from SAP Logon? or can I insert parameters of solution manager instance directly into TAO?
Regards,
Abdelaziz

Hello,
Navigate into SAP TAO
Click on the 'Expert' tab
Look for an option 'Further Settings'
Click on 'Use an alternate path to look for the saplogon.ini file'
then browse to where you have your saplogon.ini file saved.
Save this setting and exit out and come back into the application.
Regards,

Solution Manager 7.1 Integration into SAP Landscape

Hi All
I have a few questions for all the SAP Solution Manager experts out there and for anyone that would like to take a stab at these questions. An organization would like to implement a 3 system landscape for the following SAP Applications; SAP ERP, SAP CRM, SAP SRM, SAP Portal, SAP XI, SAP BI (SAP BW and SAP BOBJ) as well as SAP Solution Manager. They want to use all the functionality that is available in Solution Manager. The questions that I pose is as follows;
     1. How many Solution Manager systems must one implement? A 3 system landscape or will a 2 system landscape suffice? Bearing in mind that    functionality such as CHARM will be implemented.
     2. Where will the productive SLD reside? How would this SLD connect to the Solution Manager Systems?
     3. To which Solution Manager System will all the diagnostic agents connect to?
Your expert input would gladly be appreciated and points awarded accordingly.
Regards
Deen

Hi Deena,
I good approach would be to use a two system landscape.
Where - all sandbox and development systems are connected to develpoment solman.
and - all other systems, like quality, pre-prod, and prod are connected to production solman.
For CHARM, this is sufficient. Keep the hardware specs on the higher side of production solman.
You should use a separate SLD instance on your solution manager. WHY, incase you need to update the SP level, as SLD needs to be on the highest level, outage from SOLMAN or PI would be avoided.
You can also use, SLD of Solution manager, SYNC you dev sld with prod sld - uni directional sync - eg for stack generation.
SLD connect to your solution manager during solman_setup basic configuration and preparation of your landscape through LMDB.
Check.
SLD and LMDB Topology: Replacing the Source SLD for the LMDB
https://help.sap.com/saphelp_sm71_sp05/helpdata/en/a5/971735dd184f5c8d943c6cf423d13a/content.htm
Connect diagnostic agents to your producitve solution manager.
For more please reply back.
Good Luck !!
Regards,
Divyanshu

Adding existing systems to a new Solution Manager 7.0 Ehp1 system

Dear Experts,
We've just installed a new Solution Manager 7.0 Ehp1 system, we have a 3 system landscape in action, please need your help to connect these systems with this new Solution Manager system. The post installation Initial Configuration and Basic Configuration has been performed successfully. Also need your help with Maintenance Optimizer configuration and setting up EWA.
Please do share experiences, links and documents for the above.
Thanks in advance,
Best Regards,
basis-novice

Page 65-67 of Netweaver EHP2 Upgrade Guide found in service.sap.com/instguides.
You can use the explanation below to configure MOPZ and maintain systems in SMSY.
4.5.2Configuration of the Maintenance Optimizer
You have to configure the Maintenance Optimizer. For a list of configuration tasks, see the Maintenance Optimizer Configuration Guide.
Make sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully.
Related Documents
Available at...Maintenance Optimizer Configuration Guide http://service.sap.com /mopz (link at the bottom of the page)
4.5.3Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape. Therefore you have to maintain this data in SAP Solution Manageru2019s system landscape (transaction SMSY). In the following, you will find the description how to maintain this data. If you already have maintained the system landscape data, then check if the data is correct.
If you use the System Landscape Directory (SLD), then use it to capture the system data.
If you do not use the System Landscape Directory (for example, if you have a pure ABAP system), you use RFC connections to maintain the data.
Procedure
Maintaining the System Landscape Data Using SLD
1.
Register both Java systems and ABAP systems that you want to update in your central SLD.
The central SLD can either be on your SAP Solution Manager system, or you can have a separate system where you run the SLD (central runtime SLD). If you use a central runtime SLD, make sure that it is synchronized with the local SLD of your SAP Solution Manager system.
4.5.3Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape. Therefore you have to maintain this data in SAP Solution Manageru2019s system landscape (transaction SMSY). In the following, you will find the description how to maintain this data. If you already have maintained the system landscape data, then check if the data is correct.
If you use the System Landscape Directory (SLD), then use it to capture the system data.
If you do not use the System Landscape Directory (for example, if you have a pure ABAP system), you use RFC connections to maintain the data.
Procedure
Maintaining the System Landscape Data Using SLD
1.
Register both Java systems and ABAP systems that you want to update in your central SLD.
The central SLD can either be on your SAP Solution Manager system, or you can have a separate system where you run the SLD (central runtime SLD). If you use a central runtime SLD, make sure that it is synchronized with the local SLD of your SAP Solution Manager system.
4.
Create an RFC connection
1.
Choose the Client tab for your system.
2.
Maintain at least client 000.
3.
Create an RFC connection between the Solution Manager and the system you want to update using the RFC Assistant.
5.
Start the data transfer
To initiate the remote transfer of system data from the target system, choose the Read System Data Remote.
RECOMMENDATION
We recommend you to schedule automatic data transfers using transaction SMSY_SETUP.

Error while Regestring Enterprise portal system in solution manager

Dear Experts ,
recently we installed enterprise portal and now we required to register ep system in solution manager but i tried more and also checke in sdn & other sites but system is showing errors (system does not exist) i think i done mistakes in this process so ..
please give me steps for registering enterprise portel system in solution manager
Regards

Hello Swathi,
First get the EP system registered in the SLD connected to the Solution Manager system.
Then via Landscape Fetch job fetch the system data in SMSY. The system should automatically get created.
What are the errors that you are facing ?
Regards
Amit

ERROR while CREATING RFC FOR SOLUTION MANAGER DIAGNOSTICS

Dear all,
Hi,
I am configuring solution manager 7.0.
In SPRO>basic setting >operation>solution manager diagnostics > create RFC for solution manager diagnostics i am getting this error
program WEBADMIN not registerred.
can any one tell me how to register this program in sap gateway.
best regards
azeem

Hi Azeem,
Just before creating the rfc connection do this step.
Set-Up Solution Manager Connection to Solution Manager Diagn
Use
Check the connection to function Solution Manager Diagnostics.
Default Settings
The function Solution Manager Diagnostics is installed on the Java instance of the Solution Manager system by default.
Activities
If the default values are correct, save the settings.
To run the Solution Manager Diagnostics in another system, enter the required data and save.
Also check that your java is active.
Regards
Ashok

System Monitoring in Solution Manager 4.0

Hi all,
I want to set up system monitoring for landscape BW, ECC and SCM systems using Solution Manager 4.0 and am new to Sol Man.
So could anyone please help me with the steps.
Thanks in advance,
Sandeep.

Sandeep,
Trust me, there is no one resource that you can refer to and complete this system monitoring project. I recently configured this a couple of days ago. I can tell you that I haven't completed it yet. I have only completed the configuring the 'System Monitoring' part of it. I am yet to define monitors so that, I can monitor what I want of the satellite systems. So far, it took me about 4 days. Let me point out the basic steps you need to follow. Beyond that, please refer to the links I paste below:
Steps to configure 'System Monitoring' in Solution Manager:
1. Follow the 'Solution Manager Preparation' found under SPRO --> Solution Manager --> Read Me.
2. Make sure you have the latest ST-ICO and ST-SER installed in your Solution Manager (Note: 892412).
3. Make sure the Solution Manager has the latest support packages applied.
4. Prepare the 'Satellite Systems' as per note 455356:
     a. Create the role 'SAP_BC_CSMREG' (if it doesn't exist) with the following authorization objects
          --> S_CCM_RECV (with the objects and values mentioned in the above note)
          --> S_RFC (with the objects and values mentioned in the above note)
          --> S_RZL_ADM (with the objects and values mentioned in the above note)
          --> S_CUS_CMP (with the objects and values mentioned in the above note)
     b. Create a 'communication' user CSMREG (if it doesn't exist) and assign the profile S_CSMREG
5. Create the user CSMREG in Solution Manager using RZ21 transaction
          -->RZ21 --> Technical Infrastructure --> Configure Central System --> Create CSMREG user (Provide the required password and confirm).
6. An agent needs to be registered in all the satellite systems that collects the monitor statistics and pass on to the Solution Manager. Before registering the agent in the satellite system, a 'CSMCONF' file has to be generated in the Solution Manager and store it in a central location which, will be used by the CCMS agent while registration. This CSMCONF file holds the communication details for the agent to talk to the Solution Manager. To create CSMCONF file, proceed as follows:
          --> RZ21 --> Technical Infrastructure --> Configure Central System --> Create Start CSMCONF for Agents
          --> Store the file in a central location that can be accessed by the satellite system/s.
7. In the satellite system, copy the file 'CSMCONF' to the working directory of SAPCCM4X (F:\usr\sap\PD1\SYS\DVEBMGS01\log\sapccm4x - for example. If the 'sapccm4x' folder does not exist, create one).
8. Copy the downloaded 'SAPCCM4X.exe' file to the kernel directory on the satellite system.
9. Execute "sapccm4x -R pf=<path of the instance profile>". This should ask for the 'CSMREG' password and the admin user password on the solution manager system. Please input the same and confirm other questions. Upon confirmation, the CCMS agent should be registered in the satellite system.
10.Make sure you establish the trusted RFC connection on the Solution Manager to the satellite system you would want to monitor. This you can do from 'SMSY' transaction.
11.After successfully creating the RFC connections, and assigning the system to a logical component, please go to transaction, 'SOLUTION_MANAGER'. You can see the monitored system in the System Overview.
Below are the reference links:
Weblogs Related to Solution Manager
Hope this helps. Award with relevant points if my response is helpful.
Thank you.

Solution Manager - Error Message DSWP349 - No IBASE Components Exist ...

The subject error DSWP349 occurs when using transaction Notif_Create for a new Service Desk Message.
The error message points to the use of IB52/IB53 which has already been correctly (as far as I can tell) used to set up the IBASE components.
The error message also point to Note 824640 which I have checking out and also points to Note 1059271 from SAP Service Marketplace.
I am going to try and apply some of those notes' recommendations but as they do not seem directly relevant, am looking for any other suggestions in the meantime; for example, if anyone has an printout example of how the IBASE and its lovely components should look in IB52/IB53 that would be most appreciated !
Last point. Maybe part of the problem is that our SAP Solution Manager only links to one other internal SAP system and is not 'connected' to SAP AG (as it is an external system - this for security reasons), however we do have, for example, some external RFCs entered as part of the configuration.
Thanks all.

Hi
The issue is now resolved, this is how I did it.
1) Removed entries from BCOS_CUST from client 000 for OSS_MSG which was pointing to the RFC name
Then got another error:
No RFC connection to the central lock information management system.
The project lock functionality is active in the local system, but there is no RFC connection to the Solution Manager system.
2a) Ran the report in SA38 TMW_CONTROL_PROJECT_LOCK with selection for Deactivate the "project lock functionality".
2) Filled the "Deactivate Project Lock" field with "X" then clicked EXECUTE.
Problem got Solved.
Thanks
Ashish

Connection XI - SLD - Solution Manager

Similar Messages

Maybe you are looking for