FunctionService Connections in Solution Manager

This function uses assistants to set-up service connections to SAP for the systems in your solution. You can open a service connection for a specified period, for an SAP Support staff member to logon to your system and perform support.

Integration

The SAP Solution Manager exchanges service connection and system data with the SAP Support Portal. The Service Connection Overview function in your Solution Manager system corresponds to the http://service.sap.com/access-support function in the SAP Support Portal.

Prerequisites

In Solution Manager system settings customizing, you have:

• made Basic Settings SAP Solution Manager System User/Authorizations settings, and assigned an S user to the user who wants to set-up or open service connections.

• made Basic Settings SAP Solution Manager System System Landscape settings.

Setting-up a solution is optional for this function.

Features

• Overview of your service connections (can be filtered), by installation numbers

• Edit service connections with assistants:

  • Connection:

    You can:

    • open or close one or more systems (multiple selection with CTRL or SHIFT).

    • Update the connection status of all displayed connections. The system re-reads all status information buffered in the SAP Solution Manager, from the SAP Support Portal.

    • Specify date and time, to open system connections later.

  • Configuration:

    You can:

    • set-up a new connection for a system, change, display or delete existing connections.

    • refresh the active connections of a selected system, in the SAP Support Portal.

    • add new server and IP addresses for server, and change IP addresses.

  • System access:

    You can allow or refuse access to a system. If you refuse access, service connections can temporarily not be opened. This function corresponds to entering NO_CONNECTION in the SAPRouter field in the system data of a system in the SAP Support Portal.

  • Update:

    You can update the service connections and the authorizations. When you update the service connections, you copy the current status of the service connections and systems from the SAP Support Portal into the Solution Manager system. When you update authorizations, you copy new user or authorization data which was maintained in the SAP Support Portal user administration, into the Solution Manager system.

  • SAP Solution Manager:

    You can open, change, close or create connections to the SAP Solution Manager.

  • Solution Manager Diagnostics:

    You can open, change, close or create connections to the Solution Manager Diagnostics.

Activities

You can call the service connection overview:

• in the Solution Manager (SOLUTION_MANAGER) transaction:

  1. Choose the solution for which you want to edit service connections, in the transaction Solution Manager (SOLUTION_MANAGER).

  2. Choose Operations Setup Solution Landscape tab Service Connections .

• Via your Favorites in the SAP Easy Access menu:

  1. To put the function in your Favorites, choose: Favorites Add Other Objects Web Dynpro Application in the SAP Easy Access menu.

  2. Choose AI_SERVICE_CONNECTIONS from the possible entries help for the field Web Dynpro Application, in the following screen.

  3. Enter the required data:

     • If you choose the start mode SAPGUI, you do not need to logon to the system again when you call the transaction.

     • If you choose the start mode Browser, you must logon with your Solution Manager user. You remain logged on as long as the browser window is open. You can put the generated URL directly in your browser Favorites.

     • To only show the systems of one solution, choose the parameter IF_SOLUTION_ID from the possible entries help, and enter the solution ID as the value of this parameter. If you do not specify a solution ID, all systems which you have maintained in the Solution Manager system landscape, are displayed.

  4. Choose the transaction Service Connections Overview (SOLMAN_CONNECT). in the role menu

Displaying and Changing Distribution Routes in Solution Manager

Use

You want to display or change distribution routes in your system landscape or project landscape.

Procedure

If you want to	Choose the following on the System Landscape screen	Comment
Display the transport routes in the Change Request Management system landscape	Environment ® Domain Controller Overview
Check that the set-up of the TMS configuration is Change Request Management-compliant	Environment ® Domain Controller Overview 1. In the System Landscape group box, select a transport domain. 2. Choose TMS Configuration. 3. Double-click any system to display the current configuration.	If you need to make any changes, you can do so by switching to change mode. The recommended TMS settings are described in Customizing for SAP Solution Manager (SV-SMG): SAP Solution Manager ® Scenario-Specific Settings ® Change Request Management ® Standard Configuration ® Transport Management System (TMS).
Display the transport routes that have been configured for the whole system landscape	Environment ® Domain Controller Overview 1. In the System Landscape group box, select a transport domain. 2. Choose System-Specific Transport Routes.	If you need to make any changes, you can do so by switching to change mode.

Generate Installation Key for SAP ECC

Use

To install, or upgrade to, SAP ECC from Release 5.0, you need an installation key.

Procedure

SAP Solution Manager System

...

1. Call the System Landscape Maintenance (transaction SMSY) in your Solution Manager system.

2. Create your SAP ECC System in the system landscape:

a. Select the landscape component Systems, and choose Create New System, in the context menu.

b. Enter the system ID as the system, in the following dialog box.

c. Choose the product SAP ECC, and the product version SAP ECC 5.0 or higher, from the possible entries help. Save.

d. Complete the system data, as far as possible.

e. Save your entries.

3. Generate the key:

a. Choose System Landscape ® Other Object....

b. Set the System flag, and choose the system which is to be installed or upgraded, from the possible entries help. If you have created a system in the SAP Solution Manager, in the previous step, choose it.

c. Choose Generate Installation/Upgrade Key.

d. Enter the required data and choose Generate Key.

The system displays the key.

Installation/upgrade tool

Specify this key in the installation or upgrade tool.

Adaptive Computing Settings in Solution Manager

Use

Adaptive Computing controls the load of your servers by assigning servers to systems dynamically.

You set-up Adaptive Computing in the Solution Manager after the Adaptive Computing Controller, the Adaptive Computing control console, has registered in the Solution Manager.

Prerequisites

You have installed SAP NetWeaver and the Adaptive Computing Controller has registered in the Solution Manager. For further information, see the Adaptive Computing installation guide, under www.service.sap.com\instguides.

Adaptive Computing is only visible in the Solution Manager System Landscape (SMSY) if you have installed it.

Procedure

...

1. Call the Solution Manager System Landscape (transaction SMSY).

2. Specify the Adaptive Computing networks:

a. Choose Adaptive Computing ® Networks, in the overview tree.

b. Switch to change mode.

c. Choose New Entries.

d. Enter the required data.

e. Save your entries and go back.

3. Create computer pools:

a. Choose Adaptive Computing ® Computer Pools List, in the overview tree.

b. Switch to change mode.

c. Choose New Entries.

d. Enter the required data.

e. Save your entries and go back.

4. Add servers to the dynamically-assignable servers:

a. Go to the server in the overview tree, via Landscape Components ® Servers.

b. Set the Managed by Adaptive Computing flag in the Server Description tab.

c. To assign the server to a computer pool, choose a computer pool from the possible entries help.

d. Enter the required data in the AC Port Definitions tab.

e. Save your entries.

5. Change the settings of the systems to which you want to assign servers dynamically, as follows:

¡ For systems with ABAB-based main instances:

i. Go to the system in the overview tree with Landscape Components ® Systems ® .

ii. Go to the detail view of the main instance by double-clicking on it.

iii. Set the Adaptive Enabled flag for the main instance in the Header Data tab.

iv. Assign a computer pool in the Header Data tab.

v. Save your entries.

vi. Choose the change icon next to the instance to be changed, in the Instances tab.

vii. Enter the service data.

viii. Save your entries.

¡ For JAVA systems:

...

i. Go to the system via Landscape Components ® System Components ® JAVA System, in the overview tree.

ii. Continue from 5 iv).

Result

You can now control the load of your servers dynamically.

You call the dynamic server assignment (Adaptive Computing) with Adaptive Computing ® Adaptive Computing Controller in the overview tree in the Solution Manager System Landscape (transaction SMSY).

Overviews in Solution Manager

Use

This function shows the assignment of attributes to the following landscape components, graphically.

· Servers

· Databases

· Systems

Prerequisites

You have created and assigned attributes for landscape components.

Features

Graphical overview of landscape components and their attributes. You cannot make changes

Activities

Go to the overview with Overviews ® ®.

Example

You have created the location and the person responsible attributes of a system. You can now see in the overview, which systems belong to a location or person.

Landscape Component Graphic in Solution manager

You can display the details of the following landscape elements in your system landscape, graphically:

• Servers

• Databases

• Systems

Features

• Graphical overview of information about the landscape components in the tabs

• Go to the details by mouse click

Activities

Go to the landscape component graphic with Switch Display.

Analyzing the System Landscape by Landscape Components in Solution Manager

Use

This function provides a tabular overview of your system landscape.

Features

Selection

· Servers

· Databases

· Systems

· System components

Default variants

· You can create your own default variants of the report, i.e. the selection rules.

· You can create default variants of the layouts in the SAP List Viewer (ALV), i.e. the results display.

You should create several layouts for each type of landscape component in the ALV Grid Control. For example, for systems to display all SCM systems in your system landscape or the Support Package statuses.

A layout restricts the output view: It may not show details which you have selected in the selection screen, because their columns are hidden in the current output layout. Do not make a restricted layout the default display for all users.

Output

The system displays the analysis with the SAP List Viewer (ALV). You can print, filter, or sort the analysis, or export it into a spreadsheet such as MS Excel, with the SAP List Viewer.

Activities

Call the system landscape analysis with Utilities -> Analyses.

Clean-Up Inconsistent Logical Components in Solution Manafer

The product versions of systems in a logical component can differ during an upgrade, making the logical components inconsistent.

Recommendation

You should only increment the product version when upgrading a logical component in the Solution Manager System Landscape (SMSY), when you have upgraded all production systems.

Case A:

The product versions of the system and the logical component do not match

Check that the product version is correct.

There are the following cases:

• The system is being upgraded:

  Ignore the inconsistency until after the upgrade, and then resolve the inconsistency

• The system is not being upgraded:

  To resolve the inconsistency, assign the same product version to the logical components and all systems used in it.

Case B:

The logical component is internally inconsistent

A logical component can be inconsistent if not all main instances exist in all product versions.

Note

Existing main instances have the Main Instance Exists flag in the product version possible entries help.

End of the note.

Example

The main instance E-Selling for product SAP CRM exists only in the product version SAP CRM 4.0. If a logical component contains the main instance E-Selling with another product version than SAP CRM 4.0, z.B. SAP CRM 3.0, this logical component is inconsistent.

End of the example.

Use another logical component, with a main instance which exisits in this product version:

1. Create a logical component

2. Choose an existing main instance for this logical component.

3. Generate a where-used list for the old, inconsistent logical component.

   The Solution Manager shows in which system groups of projects and solutions the logical component is used.

4. Replace the old logical component with the new one in these system groups, with Replace Logical Component.

5. Delete all systems from the old, inconsistent logical component.

   The old logical component is no longer used. The inconsistency flag in the overview tree (exclamation mark) disappears.

Clean-up Inconsistent Systems in Solution manager

Case A: Inconsistent system is NOT used in a logical component

1. Choose Installed Product Version in the System Header Data tab.

2. Change the system product version.

3. Save your changes

Case B: Inconsistent system is used in a logical component

Case B1: The product stays the same and the product version has changed

1. Choose Installed Product Version in the Header Data tab.

2. Choose the new system product version.

   The logical component is inconsistent because not all its systems have the same product version as itself.

3. Generate a where-used list.

   Go to the logical component.

4. Put the new product version into the logical component.

5. Save your changes

Case B2: The product version and the product have changed; the system is used

Example

System ABC is being upgraded. The product of system ABC changes from SAP Web AS with product version SAP WEB AS 6.20 to SAP NetWeaver with product version SAP NETWEAVER 2004S.

End of the example.

1. Choose Installed Product Version in the Header Data tab.

2. Choose the new system product version.

   The old and new products are shown in the Installed Product Versions frame.

3. Flag the new product version as Leading Product Version.

   The system shows a warning.

4. Generate a where-used list for the product.

   Go to the logical component.

5. There are the following cases:

   • For logical components which you created:

     1. Choose the new product version of the system, in the logical component.

     2. Flag the new product version as Leading Product Version.

   • For logical components delivered by SAP, only versions of the same product are offered in this dialog. Proceed as follows:

     1. Create a new logical component with the new product and version

     2. Assign the systems which were assigned to the old logical component, to the logical component.

     3. Generate a where-used list for the old logical component.

     4. Swap the new logical component for the old one.

     5. Delete the systems from the old logical component.

6. Save your changes