Defining Component Systems 

Use

The system landscape describes component systems that are connected to the portal. At present, this file is mainly used for SAP component systems. This information is stored in an XML file on the Java iView Runtime and is required for the following functions:

Procedure

Edit the systems.xml file as described in Editing System Landscape Files.

The minimal entries that you need to make for each system depends on what kind of applications you are accessing in the system from the Enterprise Portal, for example, transactions with SAP GUI for Windows, Business Server Pages or Internet Application Components. The minimum requirements are detailed in the section on Minimum Requirements for Systems.xml File.

System Name

If the system is an SAP R/3 System, the system name should be the same as the logical system defined in table T000 in the corresponding system, otherwise Drag&Relate will not work properly. Even if you are not implementing Drag&Relate initially, you should follow this convention.

Accessability

This can be used to temporarily 'hide' a system if, for example, maintenance work is being done on the system and it should not be available. This can be set as follows:

System Attributes

The following table lists predefined attribute names that are required by certain utilities, such as URL generation. As you can define your own additional attributes, it is not possible to provide a comprehensive list of attributes.

Attribute Name

Attribute Value

Required/Optional

SystemType
  • SAP_R3 if the system is a SAP R/3 System
  • Otherwise any other value

Required

ConnectionString

Connection string for GUI connections for a SAP application server. Examples of connection strings are:

/H/172.16.64.17/S/3200 or /H/iwdf8997.wdf.sap-ag.de/S/3200

where 3200 is the port number.

If the system is an SAP R/3 System, either ConnectionString, MessageServer or ApplicationServer must be entered with a value

MessageServer

Message server of the R/3 System

As above

ApplicationServer

Application server of the R/3 System

As above

ServerPort

Port number of the application server or message server

This attribute is required if the attributes MessageServer or ApplicationServer have been maintained

Group

For example: PUBLIC, SPACE

This attribute is required if the attribute MessageServer has been maintained

Client

For example: 001, 050

Required

r3usernamereference
  • "1" means that this system is used as the R/3 reference system for user data
  • Otherwise, do not include this attribute

For more information, see Defining an SAP Reference System for User Data.

 

For SAP component systems, you must maintain one of the following combinations of attributes:

In addition there is a range of attributes that you can define for the user mapping function. For detailed information, see Attributes for User Mapping.

 

Web Access Points

A Web access point is the combination of Web server, port, protocol and base URL path used to send HTTP requests to the system.

For SAP Systems, you should use the following naming conventions when describing the category of a Web access point:

'ITS ' Internet Transaction Server - required to start R/3 transactions

'WAS' Web Application Server

'DRS' Drag&Relate Server - required to enable system for Drag&Relate

In addition, you can provide the following details:

Tag

Description

Comments

Title

Optional. Title of the access point.

  

Description

Optional. Description of the access point

  

Protocol

Required. Protocol used by the access point.

  

HostName

Required. Host name of the access point.

This should include the port, if it is not the default port, for example, myserver.wdf.sap-ag.de:1083.

Path

Optional. Common path for the Web access point.

This path should include a leading slash, for example /scripts/wgate.

Attributes

Any attributes that you wish to define for the system.

  

 

Example

You have installed a portal and only access one SAP R/3 System from the portal. Your systems.xml file could look something like the following:

 

<?xml version="1.0" encoding="UTF-8"?>

<Systems xmlns="www.sapportals.com/portal/landscape" xmlns:pcd="www.sapportals.com/portal/" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" xsi:schemaLocation="wpl_systems_v10.xsd">

<!-- an R/3 system -->

<System name="SAP_CRM">

<Title multilingual="true">

<pcd:TitleText language="DE">SAP Customer Relationship Management</pcd:TitleText>

<pcd:TitleText language="EN">SAP Customer Relationship Management</pcd:TitleText>

</Title>

<Description multilingual="true">

<pcd:DescriptionText language="de">SAP Customer Relationship Management</pcd:DescriptionText>

<pcd:DescriptionText language="en">SAP Customer Relationship Management</pcd:DescriptionText>

</Description>

<Accessability value="true"/>

<Attributes>

<pcd:Attribute name="MessageServer" value=""/>

<pcd:Attribute name="LogonGroup" value=""/>

<pcd:Attribute name="Client" value=""/>

<pcd:Attribute name="SystemType" value="SAP_R3"/>

</Attributes>

<WebAccessPoints>

<WebAccessPoint category="ITS">

<Title multilingual="true">

<pcd:TitleText language="de">ITS-Webserver</pcd:TitleText>

<pcd:TitleText language="en">ITS web server</pcd:TitleText>

</Title>

<Description multilingual="true">

<pcd:DescriptionText language="de">ITS-Webserver</pcd:DescriptionText>

<pcd:DescriptionText language="en">ITS web server</pcd:DescriptionText>

</Description>

<Protocol>HTTP</Protocol>

<HostName>host.company.de</HostName>

<Path>/scripts/wgate</Path>

</WebAccessPoint>

</WebAccessPoints>

<LogonLanguages>

<LogonLanguage value="DE"/>

<LogonLanguage value="EN"/>

</LogonLanguages>

</System>

</Systems>