Set-Up Automatic System Landscape Data Capture

Use

You set-up the automatic data transfer from the Landscape Infrastructure Server (LIS) and the System Landscape Directory (SLD), to get system data for the Solution Manager System Landscape.

The SAP Solution Manager can get host, database and system data automatically with this data.

Prerequisites

You have assigned the Solution Manager to a transport domain or defined the Solution Manager system as the new domain controller, in the Transport Management System (STMS), to be able to use the Landscape Infrastructure Server (LIS).

Procedure

...

...

Choose the transaction Setup System Landscape (SMSY_SETUP).

Choose the source for the automatic data transfer.

You should choose the System Landscape Directory (SLD) as the source for the data transfer, if SLD is set-up in your system landscape. The Landscape Infrastructure Server (LIS) only gets data about system names, clients and software components in the systems, for systems in the transport domain. SLD gets host and database data independently of the transport domain.

To access the System Landscape Directory (SLD):

a. Choose Edit ® Expert Settings.

b. Specify the host from which SLD data is to be read, as SLD Host.

c. You can change the other options.

You can also change these options when setting-up the System Landscape Directory.

d. You can write data back into SLD by entering a value for Write Data Back into SLD.

e. Choose Continue.

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

Choose Schedule Automatic Data Transfer.

Enter the start time in the following screen. You can choose whether you want the job to run once, or periodically.

For further information, see Automatic Data Capture.

Save your entries.

The system copies your data into the initial screen. The system logs each data transfer. You can call the logs in the Set-Up System Landscape (SMSY_SETUP) and Solution Manager System Landscape (SMSY) transactions with Logs ® Update Logs.

· To delete data transfer logs:

· Choose Logs ® Update Logs ® Delete in the Set-Up System Landscape (SMSY_SETUP) or Solution Manager System Landscape (SMSY) transactions.

· Choose options.
A log expires after 14 days (Expiry Date group box).

· Choose Execute.

Result

You haveset-up data transfer to automatically get system data for further use in the Solution Manager system landscape. After data collection, the automatically identifiable systems and hosts in the Solution Manager System Landscape are visible.

Solution Manager System Landscape

You create and manage the system landscape centrally in the Solution Manager, to use it in your implementation and template projects, in the Customizing Synchronization (Customizing Scout, Customizing Distribution) and in operational processing (Solution Monitoring, Services, Support Desk).

Integration

The SAP Solution Manager is based on the system landscape. A correctly maintained system landscape is a prerequisite for the Solution Manager functions:

· Generate Project IMGs in the Project Administration

· Go to the component systems in the Configuration phase

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

· Maintainc the solution landscapes for the operational processing of your solutions

Features

· Create landscape components (hosts, databases, systems)

· Define non-SAP products for use in the system landscape maintenance

· ABAP main instance reads and saves data automatically

· Overview of system groups

· Generate RFC destinations for the component systems; RFC connection errors are logged

· Manual data capture, e.g. for servers, non-ABAP systems and planned systems

Define System Landscape

Use

You must define the system landscape for your project, before you can access the component systems in subsequent project phases.

Prerequisites

You are in the Project Administration transaction in change mode.

You have setup automatic data capture for the system landscape. This enables you to use the possible entries help when you select your logical systems.

You are in the Project Administration and have selected the System Landscape tab.

Procedure

Systemstab

Define logical components

A logical component in an implementation project refers to a product in an SAP environment, without specifying systems or versions of the product. A logical component can also be a non-ABAP product.

· Choose the Scenario Selection pushbutton to copy the logical components, on which the scenarios which you selected in the Template Selection tab are based, into the Systems tab.

· To copy more logical components, choose them, and their products/main instances, in the possible entries help for the Logical Components column.

The system copies the logical components, their Products/Main Instances and the highest Product Version.

· To create a new logical component, choose the possible entries help ® Create New Entry.

You can create a non-SAP product in the next dialog box. The Define Non-SAP Products section in Setup Editing Products contains further information about creating a non-SAP product.

· You can assign another product version to the product/main instance in the possible entries help.

· Choose Replace Log. Component to replace a logical component by another throughout the project structure.

· To go to the component systems in the project phases, assign logical systems to the logical components for the system roles, from the possible entries help for the Evaluation System, etc. columns.

The systems which you specify for the system roles are used by default in the following project phases:

Use of systems

System role	Phase
Evaluation	Business Blueprint
Development	Realization
Quality assurance	Test

You can change the system roles and their assignment to the project phases, with Role Assignment in the Project Administration. You can also change the test system selected, at any time, in the Test Organization

Edit system roles

You can change the sequence of the system roles, select additional system roles, define up to ten user system roles and delete system roles from your project, with Role Assignment in the Systems tab.

You cannot delete system roles which are use in your system landscape

Solution Landscape tab

You can assign a production solution landscape to your project on the Solution Landscape tab. If you create your project structure in the Business Blueprint phase, you can later put structure elements from the selected solution landscape in your project structure. The system shows the project in the Solution Manager Operations in the solution whose production solution landscape you assign here. You can copy processes from your project into your solution landscape, in the Solution Manager Operations.

IMG Projects tab

If you have defined logical components in the System Landscape tab, the system displays their IMG projects in this tab, i.e. all subprojects in the component systems which belong to your Solution Manager project.

Generate the IMG projects in the component systems, and distribute the following central project data into the component systems:

· Project standards:

¡ Status values which do not yet exist in the component system

¡ Keywords

· Project Team Members

· Country selection

When the Project IMGs are generated in the component systems, everything is initially set in scope.

The green and red traffic lights indicate whether Project IMGs have already been generated and distributed.

· Red (square): Project does not yet exist

· Green (dot): Project exists in the specified logical components and the assigned logical systems.

Generate IMG projects in the component systems

To generate and distribute a project:

...

...

1. Choose the system role for IMG Projects.

2. Select the IMG project.

The generation and distribution is started in the component systems.

As soon as the project exists, the green traffic light symbol appears. You also get a system message in the component system as soon as generation is finished.

3. To go to the project IMG later and regenerate, select the subproject.

You go to the header data of the project.

You can also go to the project header data by selecting Display Project in the context menu (right mouse click on the IMG project).

Assign another IMG project in the component systems

To assign another IMG project from the component system instead of the default IMG project:

...

1. Position the cursor on the IMG project.

2. Choose Assign Other Project in the context menu.

3. Enter the name of the project to be assigned.

4. Log on to the component system.

5. You can create a transport request in the subsequent dialog box. You can assign tasks in this request to other project team members.

6. Choose Continue to save your entries.

The newly-assigned IMG project appears on the IMG Projects tab.

System Landscape Check

Use

This function checks the consistency of the system landscape of a project. It ensures that you can navigate among the component systems in the system landscape.

Integration

You can check the system landscape in the Business Blueprint, Configuration or Test Plan Management, in the Project Administration.

Prerequisites

You have created a project and its system landscape in the Project Administration.

Features

The system landscape check checks:

· have logical components been specified for the project?

· are the logical components and the logical system based on the same product version (release)?

· are the releases and the Support Package statuses of the logical systems sufficient to be able to navigate in the component systems with the SAP Solution Manager?

· do the logical systems have RFC connections?

· do the RFC connections work?

Only the systems for which the check generated an information or error message are displayed.

Running the System Landscape Wizard

Prerequisites

● The portal is installed and configured.

● For creating systems based on connectors provided by SAP:

The application connector and its PAR file are installed to the Web application server and the PCD, respectively, and configured.

● For creating systems NOT based on connectors provided by SAP:

You have edited an existing PAR file, or written your own, to contain a portalapp.xml file where you define a non-SAP system to which you want to connect, and you have deployed it.

Procedure

...

...

1. From top-level navigation, choose System Administration ® System Configuration ® System Landscape.

2. In the Portal Catalog, right-click a folder in which to store the new system and choose either New From PAR ® System,or New ®System.

3. Follow the instructions for each screen of the wizard, as detailed in the table below and on the wizard interface. An asterisk indicates the mandatory fields in any screen.

Whether you create a new system from a PAR file or from a template, the SAP_ConnectionString is not supported for RFC iViews.

The template SAP system using connection string is not supported for RFC iViews.

System Landscape Wizard

Screen	From a PAR File	From a Template
Portal Archive Selection	Select the PAR file on which to base the system, and click Next. The PAR files installed with the portal are: · com.sap.portal.httpconnectivity.urlsystem System created from this PAR provides authentication and user mapping information to URL iViews · com.sap.portal.systems. datasource System created from this PAR represents an EP5 data source that has been migrated to EP6 · com.sap.portal.systems.EP5 System created from this PAR contains all the connectivity details needed to migrate an EP5 portal into EP6 · com.sap.portal.systems.jdbc · com.sap.portal.systems.sap · com.sap.portal.systems. webservices ● com.sap.portal.unification50. template	N/A
Portal Component Selection	Select the component you want and click Next. The properties in each component provide the system with the necessary information for connecting to its back-end application. ● .httpconnectivity.urlsystem connects through url_system ● .systems.datasource connects through DataSource_System ● .systems.EP5 connects through: EP5_system ● .systems.jdbc connects through jdbc_system ● .systems.sap connects through: ¡ SAP_R3_ConnectionString – URL string ¡ SAP_R3_Dedicated – application server ¡ SAP_R3_LoadBalancing – message server ● .systems.webservices connects through webservice_system ● .unification50.template connects through unifier_system	N/A
Template Selection	N/A	Select one of the templates installed with the portal and click Next. ● EP 5.0 System ● HTTP System ● JDBC System · SAP system using dedicated application server · SAP system using connection string · SAP system with load balancing · Web Service System The template name indicates the type of connection.
General Properties	Enter the basic properties and click Next. The Back option is currently not available in this screen. To change your portal component selection, choose Cancel and restart the procedure.
System Name	Display name that appears in the Portal Catalog, title bars, and any form, dialog box, and window displaying a list of systems
System ID	The unique system identifier that will be registered in the PCD; may include any of the following characters: ● a-z ● A-Z ● 0-9 ● . _ - % ~ ( ) The ID must not exceed 100 characters.
System ID Prefix	If you want all your systems to follow a specific naming convention, add a uniform prefix to each system you create.
Master Language	Defines the language on which all translations are based
Description	Optional description intended for portal users; appears in the tooltip when you hover over the page name in the Portal Catalog and in search results
Summary Details	Review the options you selected for the new system. To make changes, choose Back until you return to the appropriate screen; otherwise, click Finish.
Next Step	Choose your next step and click OK. ● The system may need editing before it can connect properly to its back-end application. ● If you want to define the new system to be a template, in the System Landscape Editor set the Object is a Template property to Yes.

Result

You have created a system through which you can access a back-end application or an HTTP source, and retrieve its data. This system is now part of the portal system landscape and should appear in the System Landscape Overview iView.

System Landscape

Purpose

The portal system landscape is a collection of systems. A system is a portal object comprised of a set of properties that represent an external, or back-end, application. Systems enable a connection to these applications and the retrieval of data from their information stores.

Integration

· During portal installation, a Portal Archive (PAR) file containing a portalapp.xml is uploaded and stored in the Portal Content Directory (PCD).

The portalapp.xml is a profile of an external application, providing all the necessary connectivity information to the application. The file can hold the definitions of numerous systems.

You can create a new system directly from the PAR file or from an existing system template. It is also possible to generate a system template based on the PAR file and then use that to create systems.

● Some external applications to which you want to connect must have in the portal system a representative connector, the middleware through which the portal content accesses the application.

The portal provides an SAP connector for accessing SAPsystems and a Database (JDBC) connector for accessing generic databases. These two connectors are automatically installed to the Web application server during portal installation.

● It is possible to see the system landscape of any portal in the System Landscape Overview iView

System Landscape Overview

Definition

An iView that displays all the systems defined in a specific portal and all relevant information about each system.

Structure

The System Landscape Overview iView provides, in table form, a snapshot of your portal’s system landscape. Each system entry in the table displays its PCD ID and its alias information. The table is sorted by the System ID column.

· Selecting the Display system templates checkbox adds system templates to the table.

· Clicking the Refresh button updates the iView to reflect new information.

· If you delete a template on which a system is based, the System icon changes to an Unresolved Link icon. See the legend on the Overview tab of the System Landscape Editor in your portal for an explanation of all the icons.

Use the tooltips provided to guide you through the interface.

Integration

The System Landscape Overview iView is accessed through the navigation structure of the portal as follows: from Top-level Navigation ® System Administration ®System Configuration ® Detailed Navigation ® System Landscape Overview.