Step by step guide to connect Satellite systems to SOLMAN....

Hi all,
Can you provide a Step by step guide to connect Satellite systems like (SAP CRM, SAP ECC 5.0 Etc..) to SOLMAN and also what are the major config steps involved in connecting a satellite systems to Solman.
The connection is basically to monitor key performance issues of the satellite systems through Solman....
Need ur inputs on this...
Thanks and Best regards,
Subba

Hi,
In a system landscape you can only add logical components. Please double click on the name of the logical components. You will arrive in the maintenance area for logical components. There you can add systems to your logical components.
Check the following links also.
satellite system
Solution Manager - How to connect to satellite system ( refer this)
Re: Service desk RFC destination in the Satellite system
Re: Satellite Logon
Regards,
Note: Points always encourage me to reply !!

Similar Messages

No IBase/Component transferred in SLFN from a satellite system to Solman

Dear all,
We have Solution Manager 4.0 with SPS18 with working ChaRM and Service desk.
I have the following problem : a support message (created from the menu   Help->Create Support Message in a satellite system) arrives to Solman, but the fields Ibase and Component are filled by zeros and are inactive so I canu2019t change them manually.
The question is: are these values transferred from the satellite system to SolMan or not?
I have debuged the program calling under Help->Create Support Message   and have not found such functionality.
From the other hand, all forum messages implicitely imply this.
Due to technical reasons I canu2019t use notif_create transaction, where there are Ibase and component fields.
   From the SolMan configuration side everything is OK:
System landscape is correct, Ibase and components are generated and active, they have the correct external names. The functionality of ChaRM that utilises Ibase and components is working well, so I donu2019t see any problems from this side. OSS 449330 (delete the record from BCOS_CUST table with the value u201CTST_CUSu201D in Application field ) is not the case.
Please advice.

Hi,
In this case, could you please kindly verify the points mentioned in this note has been verified ?
note #824640
Hope this helps.
Cheers
SH

Any standard RFC there to communicate between satellite system and Solman?

Hi Gurus,
Any standard RFC there to communicate between satellite system and Solman?
Thanks in advance.
Regs,
BBR.

following four RFCs are created so as to initiate the communication between the satellite system and the solman system
_READ, _TRUSTED, _BACK, _TMW
but, you have to Read the Links and the Notes too to understand their names and their meaning
http://help.sap.com/saphelp_sm310/helpdata/en/48/647e3ddf01910fe10000000a114084/content.htm
http://help.sap.com/saphelp_sm310/helpdata/en/b3/dd773dd1210968e10000000a114084/frameset.htm
http://www.slideshare.net/wlacaze/sap-solman-instguide-initial-customizing-presentation

Step-by-Step Guide for connecting CRM with SAP R/3 system Server

Hi Experts,
For my ongoing project , I am in the need of connecting the CRM server with
SD server.
Can u share any Step- By Step guide for doing that.
I know that the RFC connection has to be established between the system.
Logical system must be create and all such stuffs.
It is definitly helpful, If u can help me out.
I would to thank, appreciate and reward for your help
Best Regards,
Maniprabu

Hi Mani,
Follow the following steps :
1. Create RFC destination for both the systems on CRM and R/3 in SM59.
2. Create the logical systems and assign clients to logical system in SALE transaction both on CRM and R/3.
3. Create a user in the R/3 table CRMCONSUM with the name CRM.
4. Maintain the Middlware Parameter tables on CRM : Table SMOFPARSFA:
 Create an entry for following parameter entry:
 Key - R3A_COMMON
 Para name - CRM_DEFAULT_DESTINATION
 Value - R/3 logical system
5. Maintain the parameter tables on R/3 system : CRMRFCPAR, CRMPAROLTP
 CRMRFCPAR :
 Create new entry with following data:
 User - CRM
 Object name - *
 RFC Destination - RFC destination for CRM
 Load types - All Load Types
 In Queue flag - X
 Send XML No XML
 CRMPAROLTP :
 Create the following parameter entry:
 Para name - CRM_DEFAULT_DESTINATION
 User - CRM
 Value - Name of the CRM logical system
6. Create Sites and attach subscriptions in Admin Console : Tcode SMOEAC
 Create a Site as CRM and another as R/3. Attach the required subscriptions to the R/3 site.
7. Register the queues in SMQR and SMQS transactions.
PS : For detailed steps refer the Middlware Base Customizings(CR500 and CR100)
Reward points if it helps.

Connecting satellite system through Sol Man

Dear friends,
I am working on Sol Man 4.0 SP 12.
I have properly set the T-RFC roles to users in both satellite system as well as in Sol Man system.
Now i want to execute the transaction MM01 (creation of material master) from Sol Man. If i execute the transaction, i am getting the message that
"The new session will be created in SD1 system".
The SD1 system is my R/3 dev system. But the new session is not at all getting displayed.
I could not find the reason. If there is a problem in RFC, system will clearly tell the message.
Could anyone suggest me reason for this kind of system behaviour?
Regards
Senthil

Dear Senthil,
Have you defined any user for the RFC's specially the Trusted RFC ? If yes is it an Dialog user or an communication user ?
Also does the userid in Satellite system have the authorization to execute MM01 ?
Regards
Amit

Unable to register a satellite system in solman

Hi,
I am trying to register our stage system in solman using t-code SMSY but I am unable to do so. I do not get any errors. My RFC connection tests between the solman and the stage systems are successfull.
I came to know that the stage system is not registered in the solman while trying to create a new maintenance transaction.
In the Maintenance Optimizer transaction, under step 1, I am not able to see the SID of my stage system under 'System'.
How can one check all the satellite systems that are configured in the solution mananger. I am able to see the SID of my stage system in t-code SMSY under the components 'server' , 'databases' & 'systems'. How can I narrow down the cause of this issue. Please help.
regards,

Hi Sunny,
I have assigned our stage system to the logical component SAP ECC under 'system groups and logical components' tab in SMSY
options available are
SAP ECC -> SAP ECC Server -> SAP ECC. I select SAP ECC and I see 'System Assignment' screen on the right hand side. I see the already configured systems. The various tabs under 'System Assignment' are as follows
Product version Development system Quality assurance system Production system
I see our development system under the tab 'Development system'. I added my stage system under 'SAP Reference System'. Now I am unable to view my system while I create a new maintenance transaction under Operations > Change Management > Maintenance Optimzer ,
If I change the role of my stage system to the role 'Production' then I am able to see my stage system when I create a new maintenance transaction. Pls note that the role that I selected for my stage system during the configuration was 'SAP Reference System'
Hi Amit,
I followed your step but still unable to view my stage system under Operations > Change Management > Maintenance Optimzer ,
Create new maintenance transaction. Are only systems with 'Production Role' visible in Maintenance optimizer. Pls note that the leading role of the Solution is 'Production System' as seen under System groups and logical components - Solution Landscapes
- SAP ECC.
regards,

ChaRM - Change Request where to raise? Is it in Satellite system or Solman

Hi Friends,
For creating the change request( TCode: charm_create) is it necessary to login to solman & then raise CR ?
Is is possible to raise Change Request in satellite systems ?
If I have done development configuraion in BI & Now I want to move it to QA. What is the process steps for the same?
Many Thanks
Praveen K

hi
Change Request have to raised in Solman. You might be aware all change requests will be connected to a maintenace project / Implementation project in Solman.
In that project, your satellite system landscape have to be maintained.
refer the below help doc for the process flow
[http://help.sap.com/saphelp_smehp1/helpdata/en/2b/614e1cb8204f35b477eac703073589/content.htm]
Suppose for doing a configuration change in your BI system, you have a raise a CR in Solman and choose the appropriate maintenance cycle of BI landscape and continue process. Refer the solman rkt documents also.
regards
Naveen

/BDL/TASK_PROCESSOR not getting triggered in satellite system from Solman

Hi,
We have scheduled EWA report in Solution Manager for one of the satellite system.
Solution Manager has sudddenly stopped creating of job /BDL/TASK_PROCESSOR0000002218 (ie job which is created immediately as EWA is scheduled in Solution Manager)
/BDL/TASK_PROCESSOR is running correctly and on hourly basis in satellite.
The EWA report is getting generated in Solution Manager after long time and without job /BDL/TASK_PROCESSOR0000002218 (is sessin specific job) being triggered.
Kindly help.
Regards,
Trupti M

Hi Paul,
My problem is solved.
Actually the Task: EarlyWatch Alert for Solution Manager under 'To Do' view of sdccn of satellite system was somehow getting scheduled as Back dated(ie instead of 30.04.2020 it was getting scheduled at 28.04.2010)
Due to this when we would do 'Start now' for the Task 'EarlyWatch Alert for Solution Manage' it was not getting triggered.
So I manually did refresh session which was mentioned under steps for manully sending data to SolMan under solution_mamanger tcode.
Due to this job BDL/TASK_PROCESSOR0000002237 got created.After this job got completed Task ''EarlyWatch Alert for Solution Manager ' got automatically generated.
I back dated the date for Task ''EarlyWatch Alert for Solution Manager" and started it.
Due to this the job /BDL/TASK_PROCESSOR0000002238 got created in satellite system for sending data to SolMan (This was not happening earlier.)
Extract from Solution_Manager tcode when scheduling:
When the Session Refresh task has been processed, a new task with the appropriate session type and session number appears in the To do view. This task collects and sends the data for your session. If a new task does not appear, search in the task-specific log for errors that ocurred during the Session Refresh task and make any necessary corrections.
To start the task immediately, select it and right-click to call up the context menu.
Choose Start Now. When the task has been processed successfully, it appears in the Done view. The data has been sent to your SAP Solution Manager system. You can check this in the task-specific log.
Thanks for all your help. Hoping my post will also be helpful for others.
Regards,
Trupti M

Creating Support Messages from Satellite System without SolMan user account

Hi
We are having some problems with users "creating support message" from our ECC system to SolMan, if the user does not have a user account in Solution Manager.
It is not correct, that users from Satellite systems can create support messages from these systems, without the user having an account in Solution Manager? And that the user is identified by the business partner for the user, that must exist in the Solution Manager system ?
We have set up the RFC for the supportmessages between SolMan and the ECC system as trusted RFC, with the "Current user" as the user, but how should this be set up, if the user does not have an account in the Solution Manager system. If we enter a user with the right authorizations in the RFC, will the messages that come through not just appear as created by that user, instead of the ECC user and corresponding business partner ?
Regards
Lars

Hi,
you can use the use the user for the RFC-Connection in that case. I have customizied a similar scenario. In my scenario the System from which the message was created, is the business partner (SOLD-TO-PARTY). For that you have to create a communication user (i.e SOLMAN<SYSID>). In TA SM59 in the satellite-system you assign this user for the connection. (Don't forget to assign the user to the role "SAP_SV_FDB_NOTIF_BC_ADMIN"). Now, it schould be possible to create messages from the satellite system to the solution manager. Additionally you should create business-partner for each user of the satellite system, by using TA DSWP>EDIT>CREATE BUSINESS PARTNER.
With this TA, it is easy to create BP for each satellite system.
Best regards
Marc

To view the list of users in Satellite Systems from Solman

Dear Friends,
We wish to view the list of users in a satellite system (say ECC5.0) from solution manager 4.0, can anyone help us to find the same.
Regards
Senthil

Hello Senthil,
You mean the list of BP associated to the satellite users already created? If this is the case
in DSWP, choose a Solution that has your satellite as system and go to Edit->BP
Add the satellite system to the list and if I don´t remember wrong you will get the
BP for the satellite users already created in the righ chart.
Sory if I don´t get the correct question?
Best regards,
Dolores

Is there a step by step guide to connecting a Drupal website with SQL Azure?

The company is upgrading the Drupal website and the goal is to have a live database by connecting the Drupal SQL database with he SQL Azure database. Does anyone have guide/step by step process for implementing connectivity between Drupal and SQL Azure?

Hi,
Thanks for posting here.
Recommend you to see "
Best Practices for Drupal CMS on Azure Websites " written by Sunitha Muthukrishna which talks about How to migrate existing Drupal site to Azure Websites and Copy database to MySQL in Azure Web Sites
" Mysqldump " tool is one of the preffered approaches to Copy database to MySQL in Windows Azure Web Sites
Here is another document that talks about Migrating Drupal to azure and
Copy the Database which might help.
Hope this helps you.
Girish Prajwal

Any performance impact on satellite systems?

Hello,
Our productive solution manager are setup to connect to all the ECC, XI & R/3 systems, as central monitoring system.
So far we only use Solman for monitoring & EWA, not even BPM is configured yet.
in SMSY, it's configured to use our XI SLD, to auto collect all the database, server & system data for solman system landscape.
My question is: If there is downtime on Solman system, will it have any performance (slow transaction) on satellite system, especially on my XI system (as solman access the XI SLD).
The reason I post this question here is: recently we have downtime for solution manager due to SP upgrade, during the downtime, we noticed there are a lot (thousand) IDOCs processing messages to R/3 system stucks in XI for 1 of our application. Users starting to make complaints, and we try to find the root cause in XI, in R/3 ... involve our basis guy & also XI admins, but no one able to find why.
By the time PSM is up (after 2-3 hours), ALL the stuck messages in XI are manage to clear/process at once. And until now, on one able to explain why. They are suspecting my solution manager system downtime has the impact on those satellite system.
Solman is setup to use PXI's SLD.
Anyone has feedback on this, is it coincidently, or ?
Please share if you have knowledge on this topic
Thank you

Hi,
As per your description I would say it is pure coincidential.
When you configure Solution Manager for system monitoring and/or EWA, all Solution Manager does is to collect the relevant data from the sattelite systems. Just this.
So, when solution manager is not available there should be no reason for any impact on the sattelite systems side.
Also, from your description, I would say your XI is getting SLD information from Solution Manager. This is the only reason I could figure out that IDOCs are getting stucked in XI.
Is it possibel to ask your XI guys to recheck which SLD XI is using?
Regards
Valdecir

Migrate config to Solar02 from Satellite Systems

Hi Gurus
I need to know if there is a way to bring in the config form the Satellite systems in to Solman Solar02. The Solaman system up till now has only been used to gererate the installtion keys and System Monitoring. I am busy with the process of setting up change management and service desk. However I have also been tasked with setting up the business blueprint. The original config was never setup in regards to the blueprint. Is the a way to bring this across to Solman or do i manually have to enter enter the business scenarios in Solar02.
Santosh

Hi,
Bringing configuration details from Satellite System to SOLMAN
This is one of the Myths about SOLMAN.
SOLMAN helps/guides/enables your to manage your project in a better/efficient manner.
You define your process, document them. Proceed to SOLAR02 to maintain your IMG with corresponding transactions.
Feel free to revert back.
--Ragu

CHARM:   Logon restriction to satellite system

Hi
With CHARM functinality, users are allowed to logon satellite system via Solman only when logon action is approved. This is great control, but how can we prevent users from loging directly to satellite system?
In short, I would like to accomplish this
User > SAPGUI　> Satellite (i.e ECC)    Not possible
User --> SAPGUI --> Solman --> Satellite   Possible when approved in Solman
I tested this with changing user type in SU01 (dialog, communication, system, service...), but none of them solved my problem.
Maybe, I should post this question in BASIS forum, but though this was common problem in CHARM envirnment.   Thanks in advance.
Regards

Hi, Xavier
Thank you for your reply.   End users will continue to log on satellite system. No change for them.
What I meant is that I want to control developers / testers' logon activities.
They can logon DEV / QA servers only when approved by Solman.
Problem is that their users need to exist in satellite system, and they can still directly log on to DEV / QA.　This is why I want to accomplish such a functionality.   I wonder if any configuration solve this.
Regards
Koji

Step by step guide to create a RFC connection and data transfer

hi
could i get a step by step guide to transfer/read data from SAP and legacy system using the concept of RFC.
Regards
Shiva

hi
Here are the steps.
SM59 Transaction is used for Connection Establishment with Destination.
When you establish a connection to a client through a destination, the HTTP connection must first be entered in transaction SM59.
There are two types of HTTP connection in transaction SM59: Call transaction SM59 to display the different RFC destinations.
The HTTP connection to the external server (connection type G) and the HTTP connection to the R/3 system (connection type H) are different only in their logon procedures. Their technical settings are the same. To display the technical settings, double-click a connection.
You can choose from three tabs. Under Technical Settings, you can specify the following:
· Target Host: The host to which you want to connect.
Note that if you are using HTTPS as a protocol, you have to specify the full host name (with domain).
· Service No.: Here, you specify the port. The destination host must of course be configured in such a way that the specified port understands the corresponding protocol (HTTP or HTTPS). See Parameterizing the ICM and the ICM Server Cache.
· Path Prefix: At the time when the connection to this destination is initiated, the system inserts this sub-path before ~request_uri.
· HTTP Proxy Options: Here, you can configure a proxy for HTTP connections: You can determine the proxy host and service, as well as users and passwords for the HTTP connection.
The tab page Logon/Security will be different depending on whether you have selected a HTTP connection to an external server (connection type G) or a HTTP connection to an R/3 system (connection type H).
HTTP Connection to an External Server (Connection Type G)
Choose the connection you want to use. You can choose from the following logon procedures:
· No Logon: The server program does not request a user or password.
· Basic Authentication: The server program requests a user and password. Basic Authentication is a standard HTTP method for authenticating users. When a user logs on to the target system, he or she provides a user ID and password as authentication. This information is then sent in a header variable as a Base 64-encoded string to the server, through the HTTP connection.
· SSL Client Certificate: If you use client certificates for authentication, the client authentication is performed through the Secure Sockets Layer (SSL) protocol. In this case, you must also select the SSL Client PSE of the SAP Web AS that contains the relevant certificate for the authentication. The target system must handle the issuer of the SAP Web AS client certificate as a trusted system.
Under Logon/Security, you can also activate SSL to ensure that HTTPS is the protocol used (if you select SSL, make sure that the correct port is entered under Technical Settings). In the security transaction STRUST you can determine which type of SSL client is used. (Getting Started with the Trust Manager, Trust Manager).
The field Authorization for Destination has been implemented as an additional level of protection. We recommend that you specify a user and password for the RFC destination.
HTTP Connection to an R/3 System (Connection Type H)
Here, you can specify more settings for authentication in the target system.
The settings under Technical Settings and Special Options are the same as for connection type G. Under Logon/Security, the connection type H has additional logon procedures. As with external servers, you can activate and deactivate SSL and specify an authorization.
Because the target system is an SAP system, you can set the client and language for the logon as well as the user name and password. If you check Current User, you have to specify the password.
The following authentication procedures are available: Basic Authentication, SAP Standard, and SAP Trusted System, and SSL Client Certificate.
· HTTP Basic Authentication: Logon with user and password
· SAP Standard: This procedure uses an RFC logon procedure. The RFC Single Sign-On (SSO) procedure is valid within the one system. The same SAP user (client, language, and user name) is used for logon.
· SAP Trusted System: Trusted RFC logon to a different SAP system (see Trusted System: Maintaining Trust Relationships Between SAP Systems)).
· SSL Client Certificate: The SSL protocol enables you to use client certificates for the logon.
Type G/H (SM59)
Timeout:
When sending a HTTP request, you can use this parameter to specify the maximum response time for the connection.
HTTP Setting:
You can use the HTTP version to specify the protocol version of the HTTP request (HTTP 1.0 or 1.1).
Compression:
You can use this option to activate the gzip compression for the request body. This can only be activated in HTTP Version 1.1.
Compressed Response:
In the standard setting, the SAP Web Application Server sends the Accept Encoding field as a header field with the value gzip, if the application server can handle this compression. This notifies the partner that the caller can handle gzip decompression, and that the partner can send compressed data. If you want to prevent a compressed response being sent, choose the option No.
HTTP Cookie:
You can use this option to control the way received cookies are handled.
You can specify the following for cookies:
· Accept them automatically
· Reject them automatically
· Accept or reject them in a prompt
· Use a handler for the event IF_HTTP_CLIENT~EVENTKIND_HANDLE_COOKIE to process the cookies in the program.
· In the next section, you can read about the parallelization of requests.
Thanks,
vijay
reward points if helpful

Step by step guide to connect Satellite systems to SOLMAN....

Similar Messages

Maybe you are looking for