Create System Components and Assign them to Systems in Solution Manager

System components support non-ABAP main instances in the system landscape maintenance. A system component is always assigned to a type, e.g. J2EE or TREX, to identify its task or underlying technology.

A system component can belong to different systems. In the SAP Solution Manager, you capture the data for a system component once, independently of a system. Then assign the system component to the systems which use it. There are the following types of system components. SAP can specify more.

• ITS

• Java System

• TREX

Procedure

Create system component

Note

You can create system components manually. Some types can also be copied automatically from a connected System Landscape Directory (SLD).

End of the note.

1. Choose Landscape Components -> System Components in the overview tree.

2. Choose Create New System Component from the context menu.

3. Enter a name.

4. Choose a type.

5. Save your changes.

6. Enter the required data in the right-hand side of the screen, in the Header Data and Instances tabs.

7. In the Software Components tab, you can:

   • Select installed software components from the possible entries help.

   • Copy software components from a main instance of a product with From Main Instance.

   • Specify software component patch level.

8. You can enter values for the attributes you defined, in the Attributes tab.

9. Save your changes.

Assign system component to a system

Note

System components are not automatically linked to a system. To specify that a system component takes the role of a main instance of a system, you must explicitly assign the system component to this main instance. You perform this step manually.

End of the note.

1. Choose Landscape Components -> Systems -> -> -> Main Instance Selection tab, in the overview tree.

2. Set the System Component Assignment flag for the relevant main instances.

3. Choose the system component from the possible entries help.

   Note

   Information which you had previously captured for the main instance is discarded, i.e. wherever the Solution Manager gets data for the main instance, it gets it from the assigned system component. The system component replaces the information directly at the main instance.

   End of the note.

   Recommendation

   Create, for example, a TREX centrally as a system component and assign it to the main instances of the systems in which it is to be used.

4. You can assign further system components to a relevant main instance.

   Note

   There are main instances in SAP product definitions which cannot be classified, i.e. they are based on various technologies or perform various tasks. In this case, you can assign other system components to a relevant main instance. This extended assignment of system components to a main instance depends upon whether a system component is already assigned to the main instance.

   End of the note.

5. Save your changes.

Define and Edit System Roles in Solution 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

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.

ProcedureAssign a System to a Product/Change Product Version in Solution Manager

Procedure

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

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

   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

Procedure

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.

Delete RFC Connections in Solution Manager

Procedure

Caution

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

End of the caution.

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

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

Change Existing RFC Connections in Solution Manager

Procedure

Change 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 component system is shown at the top of the screen.

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

5. Make changes to the RFC connection.

   Note

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

   End of the note.

   Recommendation

   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 Assignments of RFC Destinations to Clients

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

Refresh RFC destinations

Note

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

For further information, see Delete RFC Connections.

Generate New RFC Connections in Solution Manager

Procedure

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

   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

   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

      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

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

Generate RFC Connections in Solution Manager

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 Sstem Lndscape, 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 (SMSY), and have saved your last change.

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

Procedure

You can:

• Assign an existing RFC destination to a client with Assign and Check RFC Destinations.

• Generate RFC destinations for your component systems

  For further information, see Generate New RFC Connections.

• Change existing RFC connections.

  For further information, see Change Existing RFC Connections.

• Delete RFC destinations.

  For further information, see Delete RFC Destinations.

• Resolve RFC Generation Errors

  For further information, see Resolve RFC Generation Errors.

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.

Create Systems in Solution Manager

You create systems to use in Solution Manager projects.

The system gets the displayed data automatically for ABAP-based SAP products, if you have set-up Automatic Data Capture for the System Landscape. You can enhance this data or switch the data source to manual maintenance.

For non-ABAP SAP products and non-SAP products, you must create the systems you use in your production system landscape, yourself .

Prerequisites

You are in the Solution Manager System Landscape transaction (SMSY).

Procedure

Create System with Assistants

Note

You can also let an assistant lead you through system creation. To call the assistant, select the landscape component Systems and choose Create New System with Assistant from the context menu.

End of the note.

Create Systems

1. Select the landscape component Systems and choose Create New System from the context menu.

2. Enter the system ID as system name in the next dialog box. If there are systems with identical names in your system landscape, extend the system names to distinguish them, e.g. system AAA_1 and system AAA_2.

3. Select a product, a product version and an installation number from the possible entries help.

4. Save your entries.

   Note

   In the system landscape, the Solution Manager derives the relevant main instances from the selected product, and displays them below the system in the overview tree. The SAP product definition of a main instance is an independently-installable entity. The ABAP-based main instance is automatically flagged as relevant.

   End of the note.

5. If the automatic flagging of the relevant main instance is not correct, select the system and set the following flags in the Main Instance Selection tab, as required:

   • for ABAP-based main instances: Relevant for the relevant ABAP-based main instance and Additionally Installed for all other ABAP-based main instances

   • for non-ABAP main instances: Relevant for several non-ABAP main instances

   Note

   • As not always all possible main instances in the SAP product definition are installed in an actual system, you can select the actually relevant main instances for an actual installation of a product.

   • Only relevant main instances are displayed in your operational solution landscape.

   • You can only assign system components to relevant main instances.

   • To avoid inconsistencies in the solution landscape, you cannot remove the Relevant flag if the system is used in a logical component.

   End of the note.

6. You can assign system components, e.g. an ITS, to the relevant main instances, in the Main Instance Selection tab:

   1. Set the System Component Assignment flag for the relevant main instances.

   2. Choose the system component from the possible entries help.

   3. You can Create New System Components with the Create System Components pushbutton.

7. You can enter further system information.

   You can flag a system, for example, as planned or production.

8. Save your entries.

Specify ABAP-based main instances for SAP products

Note

To be able to put several ABAP main instances in a logical component for a system, to use them in projects and solutions, flag these additional ABAP main instances as Also Installed. The system copies the flagged main instance in the left-hand side of the screen.

1. Select the ABAP main instance in the left-hand side of the screen, below the system to be defined.

2. To be able to generate RFC connections to this system, enter the system number and the message server in the Header Data tab.

3. Enter the clients for the selected main instance, in the Clients tab.

4. Enter a client number.

5. You can enter a client name.

6. You can select a role from the possible entries help.

7. Specify a logical system.

8. Save your entries.

9. To get RFC connections for the clients:

   • assign existing RFC connections to the clients:

     1. Select a client in the Clients tab.

     2. Choose Assign and Check RFC Destinations.

     3. Select an existing RFC connection from the RFC connection type possible entries help.

     4. To also use the RFC destinations in this client for central system monitoring, set the Assign RFC Dest. for System Monitoring flag. You only need to assign this flag to one client per system.

     5. Save your selection.

   • Regenerate the RFC connections for the clients.

     For further information, see Generate RFC Connections.

     Note

     You cannot generate RFC connections for planned systems.

     End of the note.

   You can also perform this step later.

10. You can specify the instances in the Instances tab. In the possible entries help for servers, the system offers you the servers which you defined previously in the landscape component Server.

11. You can see details of the installed software components, and specify/change their Support Package status, in the Software Components tab.

12. Save your entries.

    Note

    If there is an RFC connection for read access for at least one client, you can refresh system data with Read System Data Remotely. You can automatically refresh system data when you Generate the RFC Connections.

    End of the note.

End of the note.

Specify non-ABAP main instances of SAP products and main instances of non-SAP products

1. Select the system for which you want to describe the main instances in more detail, and set the Relevant flag for the desired main instances, in the Main Instance Selection tab.

2. Select the main instance, and enter the required data at the right-hand side of the screen.

3. Save your entries.

Set-up Possible Entries Help for Landscape Component Attributes in Solution Manager

Use

You can use existing possible entries help in your system for user-defined attributes. You can, for example, set-up a list of your system administrators as possible entries help for the attribute „Person Responsible“, which you have defined.

You can set-up possible entries help for an attribute by specifying an existing values table or search help when you define the attribute. You can also define all the possible entries yourself.

When a user calls the possible entries help, the system first checks whether a value table and/or search help was specified when the attribute was defined. If so, the possible entries are the entries in the value table or search help.

If no value table or search help was specified, the system fills the possible entries help with the values specified individually in the attribute definition. If no values were specified, there is no possible entries help.

Prerequisites

You are in the Solution Manager System Landscape transaction (SMSY).

You have defined at least one landscape component attribute.

Procedure

...

1. Choose Utilities ® Attribute Definitions.

2. Switch to change mode.

3. Choose an attribute.

4. To use existing value tables and search help, you can either:

a. Enter a table name in the Value Table field,

b. Enter a field name from this table in the Values Field field.

or

...

a. Specify a search help in the Search Help Name field.

b. Specify the return parameter for this search help in the Search Help Field field.

If you only specify the search help name, the system shows the first parameter of the search help in the search help.

5. To define the possible entries help values for an attribute yourself:

a. Choose Possible Entries Help in the dialog structure.

b. Choose New Entries.

c. Enter the required data.

The system also shows text which you enter in the Description column in the attribute possible entries help. This text is language-dependent.

6. Save your entries.

Create and Assign Landscape Component Attributes in Solution Manager

You create attributes for servers, databases, systems, system components and main instances, to be able to assign additional properties to them, e.g. hardware attribute information or the person responsible for a system.

Prerequisites

You are in the Solution Manager System Landscape transaction (SMSY).

Procedure

Define Landscape Component Attributes

...

1. Choose Utilities ® Attribute Definitions.

2. Switch to change mode.

3. Choose New Entries.

4. Assign an attribute key in the customer namespace, i.e. beginning with Y or Z.

5. Enter the required data.

6. Specify the landscape component for which the attribute is to apply.

7. Set-up possible entries help for the landscape component attribute values.

8. Save your entries.

The system displays the newly-defined attributes of the landscape components, in the Other Attributes tab.

Assign values to the attributes of a landscape component

...

1. Choose a landscape component.

2. Choose a value for the attribute from the possible entries help for the Attribute Value column in the Other Attributes tab.

3. Save the changes.

Result

You can display the assignment of attributes to landscape components, graphically, in the overview tree, under Overviews.

Prepare Projects and Solutions

This process satisfies the prerequisites of the SAP Solution Manager.

Prerequisites

• To create the Solution Manager system landscape, you need authorization for the authorization object S_SMSYEDIT.

• To create system components, you need authorization for the authorization object S_SMSYSYST.

• To specify RFC connections, you have the authorizations required in the Solution Manager system and the satellite systems.

Process

1. Set-up automatic data capture for the system landscape, to read server, database and system data from the System Landscape Directory or the Landscape Information System, automatically.

2. Specify your system landscape in the Solution Manager System Landscape (transaction SMSY):

   1. Create systems or add the data to get systems automatically. The following system information is obligatory, to be able to generate RFC connections to this system:

      • Message server

      • Installation number

   2. Generate RFC connections to your systems or assign existing RFC connections to them.

   3. Combine related systems into logical components, e.g. the evaluation, development and test systems of a product, for an implementation project.

Result

You have set-up the system landscape to use the SAP Solution Manager.

You create projects or solutions and assign the logical components to the projects or solutions which you have created with this process.

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

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

      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.

Manual Data Source Maintenance in Solution Manager

Use

You cannot edit all data manually in servers, databases and systems which were determined automatically. You can set the data source to manual maintenance, to be able to edit all data in this landscape element manually.

You should only set the data source to manual maintenance if the automatically captured description does not match the actual definiton of the landscape component. This can, for example, be the case if a system temporarily has an additional server, which is recognized by the automatic data capture, but should not be in the system description because it is only temporary.

Prerequisite

You are in the Solution Manager System Landscape (SMSY).

Procedure

...

1. Choose Landscape Components ® Other Object, or

2. Choose the landscape component from the possible entries help, or enter the name of the landscape component.

3. Choose the Set Data Source to Manual Input pushbutton.

4. Confirm the confirmation prompt.

Automatic Data Capture in Solution Manager

You cannot manually edit all data in servers, databases and systems which was captured automatically. You can neither delete automatically-captured landscape elements, nor change their automatically-captured data. You can enhance this data.

To be able to edit all data in these landscape elements manually, set the data source to manual maintenance.

Update automatically-captured data

You can choose whether the system automatically overwrites manually-created data, or informs you when newer data is available. In the latter case, the last person to change the data to be updated gets an express mail. The obsolete data is flagged in the Solution Manager System Landscape with an exclamation mark. You can compare the data and choose to copy the new data.

Temporarily unavailable data

If data for instances in the System Landscape Directory (SLD) is temporarily not available, or a system is currently not reachable by RFC, e.g. because an instance is in maintenance, the Solution Manager automatically sets the Inactive flag in the Instances tab. When the instance is available again, the Solution Manager clears the flag. You can analyze this flag in the analyses.

If the instance is permanently unavailable, delete it manually.

Set-Up Automatic Data Capture for System Landscape

You set-up automatic data capture from the Transport Management System (TMS) and the System Landscape Directory (SLD), to collect system data for the Solution Manager system landscape. With this data, the SAP Solution Manager can automatically get server, database and system data.

Prerequisites

• To use the Transport Management System (TMS):

  • You have assigned the Solution Manager to a transport domain, in the Transport Management System (STMS)

  • Or you have defined the Solution Manager system as the new domain controller in the Transport Management System.

• To use the System Landscape Directory (SLD):

  You have set-up the System Landscape Directory (SLD).

Procedure

1. Choose the transaction Set-Up System Landscape (SMSY_SETUP).

2. Select the source for automatic data capture.

   Recommendation

   Select the System Landscape Directory (SLD) as data source, if SLD is set-up in your system landscape.

   • The Transport Management System (TMS) gets only system names, clients and software components in the system, for systems in the transport domain.

   • To get additional data about servers and databases, set-up RFC connections from the Solution Manager to the satellite systems.

   • By default, SLD gets system names, clients, software components in the systems, servers and databases, independently of the transport domain.

   For further information, see System Landscape Directory in the SAP Library.

3. To make SLD settings, choose Edit Expert Settings :

   1. To read data from several System Landscape Directories (SLD), specify the value X for the option Several SLD Servers.

   2. If you use Adaptive Computing, specify the value A for the option Write Data into SLD.

4. Choose Schedule Automatic Data Transfer.

5. Enter the start date in the next screen. You can choose whether the job runs once or periodically.

   Recommendation

   We recommend daily.

   For further information, see Efects of Automatic Data Capture.

6. Save your entries.

   The system puts your data in the initial screen.

Result

• The Solution Manager collects the system data automatically at the specified time, or periodically, and displays it in the Solution Manager System Landscape (transaction SMSY).

  After data collection, the automatically identifiable systems and servers are visible in the Solution Manager System Landscape.

• You can then switch automatic synchronization of system data between Solution Manager and SAP Support Portal, on or off.

• The system logs each data transfer. You can call the logs with Logs Update Logs , in the transactions Set-Up System Landscape (SMSY_SETUP) and Solution Manager System Landscape (SMSY).

  Note

  To delete data transfer logs:

  1. Choose Logs Update Logs Delete in the transaction Set-Up System Landscape (SMSY_SETUP) or Solution Manager System Landscape (SMSY).

  2. Choose the options.

  3. Choose Execute.