Connect two Solution Manager systems.

Hello,
We are planning to couple two Solution Manager systems.
We want to get all the alerts ABAP+JAVA(Root Cause) from one Solution Manager to the other.
What are te steps to take?
Connect the SLD's?
Connect the systems thru RFC?
Point all the agents to the 2 Solution Manager systems?
Regards,
Mike Geluk

Hello,
It is possible.
For SLD, two options:
- Each Solution Manager can use its own SLD. Then you must define the other server in the SLD, and vice-versa.
- Each Solution manager can connect to a central SLD where the two are defined.
The rest is just like any other managed system configuration: follow the steps in solman_setup.
Best regards,
Guiilherme

Similar Messages

Quality Center Adapter - Connecting Multiple Solution Manager Systems

We are running Solution Manager 7/Enhp 1 and Quality Center 10 successfully using the Quality Center Adapter integration. My question is, can we connect multiple Solution Manager systems (i.e. SMP/SMS/SMX) to a single Quality Center server simultaneously? Or is there a one-to-one relationship restriction. Thanks.

I have answered this question in this post below:
http://forums.sdn.sap.com/thread.jspa?threadID=2110531&messageID=10962875#10962875
To quote myself
Each tie up is based on the logical ports at the Solution Manager end and the relationship between the two entities is between Projects. So if you set up the configuration like you would in a normal scenario and at the right moment, connect the projects in SolMans to the corresponding projects in HPQC, you should be fine.
Hope that helps.

Master Data synchronisation between two Solution Manager systems

Hi all,
does anyone know if it is possible to synchronise master data (smsy, ibase and such) between two Solution Manager systems with standard jobs?
Thanks!
Regards

I asked a likewise question on the OSS earlier and I was told
"Use MDM" (which is a separate product and must be licensed separately).
Markus

Question about how to connect two solution manager

Hello experts
one of our clients wants to connect his SOLMAN to our SOLMAN, that way
when they receive a case in his ICM we can monitor the case and respond
It, if the situation requires or they ask for our help.
Can you please tell me if theres a way to connect them and what is the
best way to do that?
Thanks for your help,
Regards,

You are going to connect a Solution Manager to another Solution Manager, so I think it is enough to use the RFC destination on the connection.
I suppose you want to send a message from 7.0 to 7.1, so you may:
In Solman 7.0 system:
1. T-code SM59   > Define an RFC connection to 7.1 system;
2. T-code ICTCONF   > Add an entry for the 7.1 service desk, specify
the RFC Destination as the one you defined   > Activate -> Generate default value mapping (you may find the button on the top of ICTCONF).
In Solman 7.1 system:
1. T-code SM59   > Define an RFC connection to 7.0 system;
2. T-code ICTCONF   > Add an entry for the 7.0 service desk, specify the RFC Destination as the one you defined   > Activate -> Generate default value mapping;
3. Customize your own value mapping including the transaction type. You will find the details in:
    IMG -> SAP Solution Manager -> Capabilities (Optional)    -> Application Incident Management (Service Desk)    -> External Integration -> External Service Desk
Most fields of SIVA and SMIV are the same (for example, priority) so you do not need to care about the value mapping if you do not have special requirement. However, some fields only exist in SIVA category, subject) and others only exist in SMIV (multilevel categories). You may need to implement your own code according to your requirement.
Thanks
Vikram

Business Objects connect to Solution Manager system?

Hi
1.How to Monitor Business Objects in SM?
2.How to Connet Business Objects to SM?
Please let me know if ther are any SIM or PDF for configuration of BOJ for SM.
Regards,
Neni

1)     Install the specified Microsoft security patch in accordance with the instructions in SAP Note 1375494 in BOBJ Server
2)     Download SAPHOSTAGENT711_56-20006321.SAR and uncared.
3)     The login user requires authorization to create a service. To set this specific authorization, do the following:
a.     On the Microsoft Windows host, choose Start Control Panel  Administrative Tools  Local Security Policy .
b.     In the navigation bar, choose Security Settings  Local Policies  User Rights Assignment , and then double-click the line Log on as a service.
c.     Add the login user to the list by choosing the Add User or Groupu2026 button and entering this user.
4)     SAP HOSTAGENT version 7.11 instead 7.20. Then again upgraded to 7.20 version
5)     Downloaded the attached file ewa4boe.zip in SAP Note 1393207 onto C:\EWA folder of BOBJ server and extracted. As administration user, executed the batch script enable_ewa_monitoring.bat by invoking enable_ewa_monitoring.bat
I hope this resolves

Background job canceled in Solution Manager system

Dear all expert ,
Two background jobs canceled in solution manager system before some time.
details-
Background jobs :
                    1 - LANDSCAPE FETCH
    Program name : RSGET_SMSY
Job log : Job started
Step 001 started (program RSGET_SMSY, variant ,
The SLD server connection is inactive
Job cancelled after system exception ERROR_MESSAGE
                   2 - SEND_SYSTEM_RELATIONSHIP_TO_SUP
    Program name : AI_SC_SEND_SYSTEM_RELATIONSHIP
Job log :
                   Job started
Step 001 started (program AI_SC_SEND_SYSTEM_RELATIONSHIP, variant ,
SOL determined as monitoring Solution Manager system
SAP customer number unknown for installation number 0020606335
Job cancelled after system exception ERROR_MESSAGE
please help me , what should i do ?
I am waiting for your positive response.
Regards
Shubh

hi,
You can try following ....
For the job SEND_SYSTEM_RELATIONSHIP_TO_SUP
Program : AI_SC_SEND_SYSTEM_RELATIONSHIP
1. Up to Support Package 09:
a) Start transaction SMSY.
b) Choose Shft+F5.
c) Select the system named in the message.
d) Choose F6.
e) Select the "System Data in SAP Support Portal" tab.
f) Using the input help, fill the system number field with the correct system.
g) Save the data.
2. Up to and including Support Package 08:
a) Start transaction SOLMAN_CONNECT.
b) Select the system in question in the ID field and choose the filter pushbutton.
c) Select the system and select "Create configuration".
d) Fill the system number field using the input help with the correct system.
e) For example, select the "BW GUI Connection" service type.
f) Carry out all of the subsequent steps of the Configuration Assistant until you see the "Finish" pushbutton.
This establishes a unique relationship between your system in the Solution Manager and the system number in the SAP Support Portal. Problems no longer occur with this system when the SEND_SYSTEM_RELATIONSHIP_TO_SUPP job is next run. However, the problem may still exist for other systems (in these cases, you should follow the same steps).
Hope this will help to solve your issue..
Regards
Bhuban
RKFL

Syncronizing two Solutions Manager with One SLD

Hello Experts, we have this issue: I am having one Central SLD in PI and one productive Solution Manager (new one) that is pointing to that SLD, for incidents we are managing another ¨productive¨Solution Manager (old one) . There is a new system that I need it in my SMSY in my old Solution Manager and the best way to do it would be to point that old Solman to the same SLD that the new one is pointing. my question is: I only have to set the SLD in the old solution manager in the RZ70 and add that Solution Manager in the Central SLD?, so I would end with two solution manager pointing the same Central SLD, it doesnt mess with my new productive Solution Manager SMSY?, I want to be sure that some trash data in the old Solution Manager wont be present in the new Solman that is pointing the Central SLD right now.
Best Regards,
Paul

Dear Mr. Paul,
There are few things to understand:
1. RZ70 is used to feed SLD with system information.
2. landscape fetch job need to be scheduled within Solution manager system to update SMSY with the latest information available in SLD which you have configured during SOLMAN_SETUP.
Here with your description it is clear that you have central SLD at your PI system and your both Solution manager system ( New and Old) are connected to the central SLD.
Here what I understand if you want to add a new system say X in SMSY of your old solution manager.
In order to do so you need to configure your new system to the central SLD using RZ70. Once you did this, system details of your new system would be available with central SLD.
Now in next step to make that system available to your old solution manager, you need to rerun the smsy_setup job. This will referesh your SMSY and new system would be available in SMSY of your OLD solution manager.
In this case there is a catch. Since you have added the system to the central SLD, the new system X would also appears in the SMSY of your new Solution Manager as well once SMSY of new solman gets refreshed.
So if you just want to add this new system X to SMSY of your old solution manager only and not to the new one, you can add this system to the local SLD of old solution manager only not to the central SLD.
Also you need not to worry about the trash data available in your Old solution manager. It would not effect the central SLD if your local SLD of old solution manager is not synch with central SLD.
Regards,
Sachin

Error in RFC & to Solution Manager System

Hi,
Error in RFC & to Solution Manager System
can anyone tells me why this error occurs???
With regards
kulwinder

FYI
We have just had same issue thaat in certain scenarios with RFC communication BACK to Solution Manager from Satellite system we got the error. We resolved this by looking at the RFC user used in the BACK connection (i.e. SOLMAN<SID>) on the Solution Manager and changing the user type from communications.
Hope this helps someone else, I spent ages digging around for an answer to such a simple fix
Paul

Solution manager system log - strange entries

Hi Everyone,
the problem we are facing in Solution Manager system log every five minutes appears a new error message:
2 Database error -30082 at CON
0 > SQL30082N Security processing failed with reason "24"
0 > ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
First of all the landscape: ECC, BI, CRM, PI and Solman. Each system is DEV, QUA, PRD - except Solution Manager.
Result of going to see the logs within work directory:
Connect to %_DCR_XXXXX as db2dcr with DB6_DB_NAME=DCR;DB6_DB_HOST=xxxxxx;DB6_DB_SCHEMA=SAPSR3;DB6_DB_SVCENAME=5912
C *** ERROR in DB6Connect[dbdb6.c, 1727] CON = 1 (BEGIN)
C &+***      DbSlConnectDB6( SQLDriverConnect ): [IBM][CLI Driver] SQL30082N Security processing failed with reason "24" ("USE
C &+***      RNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
C &+***
C &+***
C &+***      ABAP location info 'CL_SQL_CONNECTION=============CP', 337
C &+***
C *** ERROR in DB6Connect[dbdb6.c, 1727] (END)
C *** ERROR => DbSlConnect to 'DCR' as 'db2dcr' failed
[dbdb6.c      1732]
Some of the systems are being connected successfully and the error messages in SM21 are not related to those systems. But some of the systems like DCR cannot be reached. And this fact causing the error messages.
I haven't configured Solution Manager because I have joined the project later. I would like to know what job is trying to access the satellite system and for what purpose.
On solution manager side I have checked all the scheduled background jobs - all of them have been executed successfully.
There some of them are scheduled but it is hard understand what is purpose of the job.
I have checked and corrected system landscape through SMSY and have maintained all the RFCs. They all OK now.
What else could force to make a connection to satellite system? And where is the place where it is hardcoded local(satellite) db2 connection entry?
Like I said before, some of the systems are being connected but some not. The one which has not been connected - there was recently changed SAP master password. I believe this is the key to resolve the problem. But the system itself operating 100% correctly.
Perhaps it could be CCMS that makes some extra connections to collect the data from the monitored systems. But I have checked all the RFC's in SM59 and they were OK.
Any ideas or suggestions would be appreciated.
Thanks in advance,
Kind regards,
Artjom.

Kaustubh Krishna,
thank you for respond.
It was dbacockpit. The connection was maintained with old db2sid password. And it was causing problematic log entries.
Problem was solved.
Points awarded.
Thanks,
kind regards,
Artyom

Automatic creation of business partners in Solution Manager system in Charm

When I automatically create business partners in the Solution Manager system from the users in the satellite systems, they are created of type "Business Partner (Gen)" and they are not associated to the user with the same name id in the Solution Manager system, but they are connected to the remote users in the satellite systems. For this reason I change manually every business partner making it of type "employee" and connecting it to the user in the Solution Manager system. In this way I can use it like partner function. Is this the correct procedure to follow? If not, what do I have to do? Which is the correct way to generate business partners in the Solution Manager system from the users in the satellite systems?
Thanks
Antonello

Hi,
It is advisable to have the same login name for the satellite systems and SOLMAN user.
Business partner can be created thru tcode DSWP -> Select Solution -> Edit -> Create business partner.
You need to create a business partner only once by the above method, even if you have a number of satellite systems.
Once the BP is created , go to tcode BP -> select the business partner -- > In the Identification Tab, enter the systems which will be accessed by the user. Here you can also give the SLM system ID in addition to the other satellite systems.
The employee connection process which you do is correct
Rgds
Abhijit

Error importing SP in Solution Manager System (phase XPRA_EXECUTION)

Dear community,
I have a fresh installation of Solution Manager System 7.1 (central system) in a test environment.
During post-installation I wanted to apply SP (user DDIC, client 000), but my update queue via SPAM failed in phase 23 (XPRA_EXECUTION) and I have no idea how to handle that. Error message:
- Error in phase: XPRA_EXECUTION
- Reason for error: TP_STEP_FAILURE
- Return code: 0008
- Error message: OCS Package SAPK-70203INSAPBSFND, tp step R, return code 0008
To check the cause of the error it is recommended to choose Goto -> Log -> Queue.
Choosing Goto -> Action Log, I find:
Error during executing the tp command 'tp XPA ALL SOL ...'
tp return code: '0008' , tp message: 'A tool used by tp produced errors', tp output:
Choosing Goto -> Import Logs -> tp system logs, I find:
START EXECUTION OF REPORTS SOL R      20120104111325              DDIC         biss-labor01
START tp_getprots          SOL R      20120104111325              DDIC         biss-labor01
ERROR SAPK-70203INSAPBSFND SOL R 0008 20120104111331 SAPBSFNDUSER DDIC         biss-labor01
ERROR SAPK-70204INSAPBSFND SOL R 0008 20120104111331 SAPBSFNDUSER DDIC         biss-labor01
ERROR SAPKITL701           SOL R 0008 20120104111335 STUSER       DDIC         biss-labor01
STOP tp_getprots          SOL R      20120104111338              DDIC         biss-labor01
STOP EXECUTION OF REPORTS SOL R      20120104111338              DDIC         biss-labor01
An excerpt (3 lines) from ulog:
APServiceSOL 20120104122229 RFC: tp SHOWPARAMS SOL pf=
biss-labor01sapmnt     rans inTP_DOMAIN_SOL.PFL -Dtransdir=
biss-labor01sapmnt     rans (pid=6232)
APServiceSOL 20120104122229 RFC: tp CONNECT SOL pf=
biss-labor01sapmnt     rans inTP_DOMAIN_SOL.PFL -Dtransdir=
biss-labor01sapmnt     rans (pid=6232)
APServiceSOL 20120104122231 RFC: tp XPA ALL SOL pf=
biss-labor01sapmnt     rans inTP_DOMAIN_SOL.PFL -Dclientcascade=yes -Dstoponerror=8 -Drepeatonerror=8 -Dsourcesystems= -Dbuffreset=yes -Dbatch_proc=1 tag=spam -Dtransdir=
biss-labor01sapmnt     rans (pid=6232)
What I already tried:
- retry importing
- stop and start the system, then retry importing
- check for background jobs (rdd* ) that failed via transaction SM37, but there are none that have been canceled
- reset buffers via transaction /$sync
Any input, suggestions or help is highly appreciated!
Regards
Sönke

Hi Sönke,
it seems we are making progress at last.
I'm afraid I didn't make my suggestion about splitting items very clear. I meant to say try applying your SPAM queue in several parts splitting up the packages affected so they are applied individually.
SAPK-70203INSAPBSFND
SAPK-70204INSAPBSFND
SAPKITL701
SAPKB70207
I think default behaviour for SPAM/SAINT is to calculate the entire queue automatically based on EPSIN but you can override this behaviour and choose to split your queue into shorter ones, you simply choose carefully the last package, apply this queue, then choose the next queue and so on until you are done. There used to be special notes which had recommended split points for package queues
EDIT: I checked your link and I don't think it is helpful unfortunately.
Best regards,
Mark.
Edited by: Mark Birch on Jan 11, 2012 2:07 PM

Error in RFC SM_DM1CLNT800_BACK to Solution Manager System Message no. STMWFLOW025

Hi,
I am facing an issue in our Test landscape. One of our team member uninstalled solman system which was connected to all other system. CHarms was partly configured in it, so other technical team used to reach to solman for creating TR# and also release the TR from Solman. Now that the system was removed abruptly we are facing this issue and I have checked few things as below:
1) Checked for domain link entries in STMS and TP profile file, could not find anything. Nor there is any option to delete domain link as there is for create
2) Checked the RFC its was working as new Solman with the same host name and other details has been brought back with out any settings yet in it.
3) I deleted the RFC SM_DM1CLNT800_BACK in the managed system and had a backup copy created before deleting it. But still get the error "Error in RFC SM_DM1CLNT800_BACK to Solution Manager System" in more help I see this Message no. STMWFLOW025
4) Message no. STMWFLOW025 - It gives me an indication that this is something to do with the domain link and the Workflow of the TMS.
5) Checked BCOS_CUST table and it has an entry for this RFC. - Should I be removing this entry and will this resolve the issue?
I need help in resolving this issue and also if one of you could share a blog for the proper configuration removal process of a managed system from Charms and ITSM I think it would be very helpful. I could only find process and step towards configuration and not how to unconfigure the system.
Thanks in advance
Ashish

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

Configuration EWA in clien with two solution manager

Hello
I have a question I am activating EWA ¡on SOlman but I have two solman fo the same company, el first is for management r3 system and second is for management xrpm,bw,portal system.
The EWA is running in the first solman, and the saprouter I think is here too. So I want to activate the EWA in the second solman in the guide I have this note 33135 an this talks about connetion with SAP.
Is possible that the EWA in two solman for the same client.
Addionaly the Should the rscctool report run in the satellites systems too?
Thanks
DS

Hello Danny,
There should be no conflicts providing you keep a few things in mind.
On the Satellite, in SDCCN > Setting> Task>Specific> RFC Destination
Please make sure that you define one Solution Manager system as the Master. This will be the Solution Manger system that will schedule an SDCCN EarlyWatch Allert task automatically on the Satellite, throught the Maintenance Package, so it needs tol be the one specificed in the Mainatence Package task. In other words you set up the recommended EWA Activation as documented at http://service.sap.com/ewa for one Solution Manager system.
Then for additional Solutioin Manager systems you would create an SDCCN Task in the same way you would generate an ad hoc EWA report, only you would choose the RFC Destination for the second ( and/or subsequent) Solution Manager systems, and you would specify it as a periodic task so it would reschedule itself each week, so to affect automation of the sending of the SDNNC session data to the other Solution Manager Systems.
This way you will not have conflicts between the solution manager systems.
Regards,
Paul

Define Service Desk Destination in the Solution Manager System (Dump creen)

hi,
in SPRO when i click on Define Service Desk Destination in the Solution Manager System
i got dump screen with the error below
any help?
Runtime Errors         SAPSQL_EMPTY_TABNAME
Except.                CX_SY_DYNAMIC_OSQL_SYNTAX
Date and Time          13.07.2008 14:05:57
Short text
    A dynamically specified FROM clause has an unexpected format.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSHI2" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX', was not
     caught in
    procedure "STREE_READ_NODE_GENER" "(FUNCTION)", nor was it propagated by a
     RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    The running ABAP program attempted to execute an Open SQL statement in
    which a FROM clause was specified dynamically in the field "TABLE_NAME". In
     this
    FROM clause, either a table name after a join operator is missing, or an
     alias name after the key name "AS". The field "TABLE_NAME" could be empty as
    well.
regards

Hi,
I am facing the same problem. What is SP15 ?
Is there any SAP Note that can be applied to correct this ?
Thanks.

Support message not getting reflected in Solution manager system

Hi,
In satellite system support message is getting created, message number"...." successfully created in service desk.
When i check in solution manager system in crm_dno_monitor the message that i created in satellite system is not getting reflected in solution manager. I removed the varients and then executed . The result is still the same.
Service desk was configured from our Development system (Client 320) to solution manager. I wanted the support desk to work from my another cleint in same system to Solution manager.
What can be the possible problem.
Thanks & Regards,
Balaji.S

Hi Gurus,
Issue got resolved, the problem was with the variant which was assigned as default for the tcode.
Thanks & Regards,
Balaji.S

Connect two Solution Manager systems.

Similar Messages

Maybe you are looking for