Generate/Change RFC Connections 

Use

RFC connections to the component systems are a prerequisite for the following Solution Manager functions:

·        Generate Project IMGs in the Project Administration

·        Go to the component systems in the Configuration phase

·        Customizing Synchronization (Synchronization Group Editor, Customizing Scout, Customizing Distribution)

·        Read system data via the Service Data Control Center

·        Monitor change requests (Change Management)

You can only generate RFC connections for ABAP-based main instances.

Prerequisites

·        You are authorized to logon to the target system and create a user there. You are also authorized to create RFC connections of type Trusted System connection, in the local and target systems, if required.

·        The satellite systems are reachable.

·        The message servers are reachable under the name and system number specified in the Header Data tab.

·        If you use routers, or you must specify the Distributed Name Service name (DNS name) to generate an RFC connection, in your network, the generation of RFC connections has the following prerequisites:

¡        You have created the satellite system message server as a server, in the Solution Manager system landscape, and specified routing information for it.

¡        You have specified this server as the message server when you created its system.

·        You are in the Solution Manager System Landscape transaction, and have saved your last change.

·        The system for which you want to generate RFC destinations, is not flagged as Planned.

Generate RFC destinations

...

...

       1.      Choose the ABAP-based main instance of the system for which you want to generate RFC connections, in the left-hand frame.

       2.      Switch to change mode.

       3.      Choose a client in the Clients tab.

You can also generate RFC destinations under the guidance of an assistant. To call the assistant, choose Generate RFC with Assistant, in the Clients tab.

Or proceed from 4).

       4.      Choose Generate RFC Destinations.

       5.      Choose the type(s) of the RFC connections in the following dialog box.

Choose the RFC connection type Trusted System for the SAP Solution Manager, whenever possible. This avoids having to logon again every time that you go to a component system when using the SAP Solution Manager.

The system shows the details of the RFC connection to be generated, at the bottom of the screen.

       6.      Choose the user options. If, for example, you use the central user management, you can assign existing users in the component system.

       7.      You can specify a server group for load sharing, in the RFC Destination Attributes group box.

       8.      If the specification of the message server is not sufficient to set-up an RFC connection in your network, or your network contains routers:

                            a.      Choose Routing Information in the RFC Destination Attributes group box.

The following dialog box displays the message server data. If you have not yet created the system message server as a server, it is created automatically and displayed at the left-hand side under Landscape Components, when you restart the Solution Manager System Landscape transaction.

                            b.      Specify any IP address.

                            c.      Specify the routing information for the direction Solution Manager -> Router -> Server, e.g. /H/1.2.3.4/H/5.6.7.8/H/9.10.11.12

                            d.      Specify the routing information for the direction Server -> Router -> Solution Manager , e.g. /H/1.2.3.4/H/5.6.7.8/H/9.10.11.12

The Solution Manager System Landscape calls information to generate RFC connections in the following sequence:

·         Routing information (e.g. /H/1.2.3.4/H/5.6.7.8/)
If this is not available:

·         Server IP address
If this is not available:

·         Server name

                            e.      Save your entries.

       9.      Remote read is the default for system data, because the SAP Solution Manager requires current system data, for example, to read the data of imported Support Packages. You should not reset the flag in the Actions after Generation group box.

   10.      Set the Assign RFC Dest. for System Monitoring flag to use the RFC destinations which you generate in the Solution Manager System Landscape in central system monitoring (transaction RZ21) and in the Solution Manager for operating your solution landscape. You only need to set this flag for one client per system.

The system enters the RFC destination data in the overview of the monitored remote SAP systems, in central system monitoring (transaction RZ21) ® Techn. Infrastructure ® Display Topology.

   11.      Choose Generate RFC Destinations.

You go to logon screens for each of the systems involved, consecutively, depending on the connection type selected.

   12.      Logon to the systems.

The system generates a log with information about the checks made, and all messages sent while making the connection.

   13.      If generation errors occur:

                            a.      The message long texts contain details of the errors.

                            b.      Resolve the errors, if possible.
Click on the RFC connection in the Generate RFC Destinations dialog box, or double-click on the RFC connection in the Clients tab, to go to the detail view of the RFC connection in the Edit RFC Destinations transaction. You can test the RFC connection there, and make any changes.
For further information, see the Resolve RFC Generation Errors section.

                            c.      Repeat the generation if necessary, by deleting the old RFC connection and generating again.

   14.      Go back.

The system shows the RFC connections generated, on the Clients tab.

Refresh RFC destinations

You cannot overwrite existing RFC connections from the Solution Manager. To regenerate existing RFC connections, delete them first manually with Cleanup RFC Destinations, and create them again.

Cleanup RFC connections

...

       1.      Select a client for a main instance, in the Client tab.

       2.      Choose Clean-Up RFC Destinations.

       3.      Check whether the correct RFC connection from the Solution Manager to the satellite system is shown at the top of the screen.

       4.      To refresh the data display, choose Read Information (<system>).

       5.      Make changes to the RFC connection.

To delete an RFC user, first delete the user, and then the RFC connection to the system.

You should use one user for all RFC connections.

       6.      To delete RFC connections to the satellite system, choose the RFC connection by double-click. You go to the transaction Edit RFC Destination (SM59) in the satellite system.

Change RFC Destination Assignment

You can assign existing RFC destinations to a client with the Assign and Check RFC Destinations pushbutton.

Delete RFC destinations

Delete Row only deletes the selected row in the Clients tab, it does not delete the RFC connection to a system.

To delete existing RFC connections, choose the RFC connections by double-click in the Clients tab, or select them and choose Clean-Up RFC Destinations.

For further information about deleting RFC connections, see Edit RFC Destinations in the SAP Library.

RFC generation error handling

·        The generation of the RFC connection can fail because the user specified in the Generate RFC Destinations dialog box already exists in the target system, and cannot be created again. You can solve the problem as follows:

¡        If this user is not otherwise used, you can delete it in the target system, and regenerate the RFC destination.

¡        Change the user to be created, in the Generate RFC Destinations dialog box, and regenerate the RFC destination.

¡        If you know the password, or can change it, delete the RFC destination, and regenerate it with the user option Use Existing User, Specify Password.

·        The Support Package status in the component systems must be sufficient. The error log long text tells you the required Support Package status.

·        The generated user may not have all necessary authorization in the target system. The generation log indicates this. Assign the required authorization to the generated user in the target system, manually.

Result

The system shows the RFC connections generated, on the Clients tab.

Give the users which RFC connections to the component systems want to use, the appropriate authorization in the component systems and in the Solution Manager system. Recreate the authorization profile, if necessary. For further information about the authorization objects and profiles required, see:

·        the SAP Solution Manager configuration guide

·        System Settings for Customizing Distribution and Scout, for Customizing Synchronization.