Showing posts with label generate RFC Connection in Solution Manager. Show all posts
Showing posts with label generate RFC Connection in Solution Manager. Show all posts

Sunday, July 12, 2009

Creating RFC Destinations in the J2EE Engine

The RFC destination in the J2EE engine is an RFC server that is called by the BW system as an RFC client. The connection is necessary to display portal content in SAP BW. The RFC destination is then used when creating the RFC Destination for SAP EP 6.0.

You need this setting for all integration scenarios.

Procedure

Follow these steps to create an RFC destination in the J2EE engine:

1. Start the SAP J2EE Engine Administrator with \admin\go

2. Connect to the Portal Server.

3. In the tree, select /Server<…>/Services/Jco RFC Provider.

4. Maintain an RFC destination:

¡ Program ID: _PORTAL_ (see Creating an RFC Destination for SAP EP 6.0 in the Registered Server Program section)

¡ Gateway host: (see Creating an RFC Destination for SAP EP 6.0 in the Gateway Options section)

¡ Gateway service: sapgw

¡ Number of processes (1..20): 20

¡ Application server host: see Gateway host

¡ System number:

¡ Client:

¡ Language: EN

¡ User: (User in the BW system)

¡ Password:

5. Transfer the RFC destination to the available RFC destinations with the Set button.

6. Start the RFC server with the Start button.

Check

The RFC destination can be checked with the Display and Maintenance of RFC Destinations (transaction SM59) (see Creating an RFC Destination for SAP EP 6.0 in the Checking section).

End of Content Area

Wednesday, November 21, 2007

Synchronize System Data with SAP Support Portal

System data, e.g. information about software component versions used, and their patch level, and the servers and databases of a system, is saved in both the Solution Manager System Landscape (SMSY) and in the SAP Support Portal. This information is required in the SAP Support Portal, for example, to find notes and for service connections.

When you have set-up Automatic Data Capture for System Landscape, the Solution Manager updates the system data in the Solution Manager System Landscape automatically. The Early Watch Alert refreshes only system data for production systems, automatically, monthly, in the SAP Support Portal. You can update system data for all systems periodically (e.g. daily) in the Solution Manager System Landscape, and as required, in the SAP Support Portal.

Note Note

With this procedure, you can switch the automatic synchronization of system data between Solution Manager and SAP Support Portal by Automatic Data Capture for System Landscape, on or off, for one system or all

End of the note.

Prerequisites

You have a user with authorization to change system data, in the SAP Support Portal. For further information, see the SAP Solution Manager configuration guide.

In a manually-created system, you have entered an installation number in the Header Data tab.

Procedure

  1. Choose a system whose data is to be synchronized.

  2. Choose the System Data in SAP Support Portal tab.

  3. If the system displays a system number, continue with step 4.

    If the system does not display a system number:

    1. Choose Read System Number.

    2. If the system number is not determined, choose it from the possible entries help.

      The system gets the system number from the SAP Support Portal. The system number is uniquely assigned to the system installation number, and is required for the synchronization of system data.

  4. To change data which you can only maintain in the SAP Support Portal, e.g. Add-On product version and use type data, choose Installation Data or System Data.

    You go to the SAP Support Portal maintenance screen

  5. Synchronize the system data between SAP Solution Manager and SAP Support Portal:

    1. Choose the synchronization setting in the Synchronization frame.

      Recommendation Recommendation

      You should synchronize all systems.

    2. To test the synchronization or transfer changes to a system into the SAP Support Portal immediately, choose Synchronize.

    3. Save your changes.

    If relevant changes are made to the system data, the Automatic Data Capture for System Landscape synchronizes the systems to be synchronized, periodically, according to your settings.

Example

SAP Support wants to support you, but cannot logon to your development system ABC, because the server data for this system is not in the SAP Support Portal.

  1. Check in the Solution Manager System Landscape (transaction SMSY), whether the server data for system ABC is complete.

  2. Enhance the server data in the Solution Manager System Landscape.

  3. Synchronize the system data of system ABC with the SAP Support Portal, in the Solution Manager System Landscape

    SAP Support can log on to your system ABC

More Information

SAP note 993775 contains a list of system data which is synchronized between SAP Solution Manager and SAP Support Portal.

Define and Edit System Roles in Soluiton Manager

Use

You can define ten user system roles in addition to the existing system roles. The system flags SAP and user system roles with icons.

Procedure

Define/change system roles

Choose Utilities ® System Settings ® System Rolestab, to change user-defined system roles or define new system roles. You can change system role types, or their sequence, for the SAP Change Manager, e.g. as subsequent system in a transport path.

The new/changed system roles are displayed in the Project Administration ® System Landscape tab ® Systems tab, and in all role selection possible entries help in the Solution Manager, except: The unchanged system roles from the client definition are displayed in the role selection possible entries help for ABAP-based main instances, in the Clients tab in the Solution Manager System Landscape.

Delete system roles

Note

If your user-defined system roles are used in your system landscape, you can change their names, but not delete them.

You can neither change nor delete SAP system roles.

Transport system roles

You can transport system roles with the Transport pushbutton.

End of Content Area

Assign a System to a Product/Change Product Version

After upgrading manually-created systems, which are not automatically updated, you can assign another product or product version to a system, e.g. you change the product assignment of the system when upgrading from R/3 4.6C to R/3 Enterprise 4.7.

Note Note

Automatically-captured systems can appear more than once in the landscape components, if your components cannot be assigned automatically, unambiguously to a product, e.g. the automatic data capture cannot determine whether SAP APO or SAP BW is installed in a system. In this case, the system appears under both SAP APO and SAP BW in the Solution Manager System Landscape. Flag one product as leading. (Item 4).

End of the note.
  1. Choose Other Object...

  2. Specify the system.

  3. Choose Installed Product Versions.

  4. Choose the new product data from the possible entries help.

    or

    If the new product/product version is not in the possible entries help, set the Free Product/Product Version Selection flag and enter the product data.

    or

    If an automatically-determined system is assigned to several products, set the Leading Product Version flag for a product.

  5. Save your entries and choose Continue.

    The system is shown in the new position with the landscape components, at the left-hand side.

  6. If the instances of the system have already been maintained for another product, you can copy them for the new system:

    1. Select the main instance of the product in the overview tree, and go to the Instances tab.

    2. Choose Copy Instances.

    3. Choose an Instance.

    4. Save your selection.

Create Non-SAP (Java) Systems in Solution Manager

You create systems in which non-SAP products are installed, to be able to monitor these systems, e.g. Java systems, in operational processing.

Procedure

  1. Create the non-SAP product which runs on the system which you want to create.

    Caution Caution

    Set the Active flag for this product. Only an active product can be used for the system definition.

    End of the caution.
  2. Create a system:

    1. Choose Landscape Components · Systems in the overview tree.

    2. Choose Create System from the context menu.

    3. Enter the system ID as system name in the next dialog box.

    4. Choose the product which you created in step 1, from the possible entries help, and choose a product version.

    5. Save your entries.

      The system is displayed at the left-hand side of the screen, under Landscape Components · Systems , below its non-SAP product.

    6. To be able to display and use a main instance in operational processing in your solution landscape, set the Relevant flag in the Main Instance Selection tab, for this main instance.

      The system copies the flagged main instance under its system, in the left-hand side of the screen.

    7. You can enter further system information (see Create Systems)

    8. Select the relevant main instance/the main instance at the left-hand side of the screen, and enter the required data at the right-hand side of the screen.

    9. Save your entries.

Result

You have created a system in which a non-SAP product runs. You have satisfied the prerequisites for monitoring this system in operational processing.

Resolve RFC Generation Errors in Solution Manager

Resolve errors

If RFC generation errors occur:

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

  2. 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.

  3. You can repeat the generation by deleting the old RFC connection and generating again.

Sources of error/symptoms

The servers of a trusted RFC connection have changed

You want to generate an RFC connection of type Trusted. The following symptoms occur:

  • The RFC log shows:

    • The RFC connection was generated outside the Trusted/Trusting RFC connection.

    • Error message: Function group SCCA not found.

    • The RFC generation return code in the RFC log is 1.

  • You have satisfied and checked all prerequisites for the RFC connection to work:

    • You have tested the RFC connection in the transaction SM59, and the RFC connection works

    • You have authorization.

    • The authorization S_RFC contains the function group SCCA

Proceed as follows:

  1. Delete the RFC destination with the Clean-Up RFC Destinations pushbutton, in the Solution Manager System Landscape transaction (SMSY), in the Solution Manager system.

  2. Check the server data in the RFC connection in the component system. If the server data is not correct, delete the RFC destination with Extras · Trusting Systems in the transaction SM59 in the component system.

  3. Delete the RFC destination with Extras · Trusted Systems in the transaction SM59 in the Solution Manager system.

For further information about defining trusted/trusting connections, see Trusted/Trusting between SAP Systems.

User already exists

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. To solve the problem:

  • 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.

Insufficient Support Package status

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

Missing authorization

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.

ProcedureGenerate New RFC Connections in Solution manager

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

  2. Go to change mode.

  3. Select a client in the Clients tab.

    Note Note

    You can also generate RFC destinations using an assistant. To call the assistant, choose Generate RFC with Assistant in the Clients tab.. Or proceed from 4).

    End of the note.
  4. Choose Generate RFC Destinations.

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

    Recommendation Recommendation

    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 details of the RFC connection to be generated, are shown 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:

    1. 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.

    2. You can specify an IP address.

    3. 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

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

      Note Note

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

      • Detailed routing information (e.g. /H/1.2.3.4/H/5.6.7.8/)

        If there is none:

      • Server IP address

        If there is none:

      • Server name

      End of the note.
    5. 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.

    Note Note

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