Roles and Tool Access 

The scope of SAP Exchange Infrastructure functions can be divided into task areas: These task areas correspond to the user roles that the users require to perform the tasks in the respective areas. Following an overview of the task areas, this section includes information about how to access the tools for both Java and ABAP.

Task Areas

Administration

Setting up of the various SAP Exchange Infrastructure tools, system monitoring, user management. An administrator must be involved with the installation process. For more information about installation, see the SAP Exchange Infrastructure Installation Guide under http://service.sap.com/instguides.

Technical Configuration

Contains the configuration of the runtime components of SAP Exchange Infrastructure. This includes the settings for the Integration Engine and the adapters. This configuration depends on the implemented components in the existing system landscape; the components can be configured independently of the design and configuration of the business process by consultants, administrators or both. For more information about technical installation, see the SAP Exchange Infrastructure Configuration Guide under http://service.sap.com/instguides.

Design and Configuration

Includes the design and configuration of various business processes. This involves the maintenance of all information required for the integration of the applications (business scenarios, interfaces, mapping, routing, business systems). This information is also referred to as integration content.

Monitoring

Includes the monitoring of various business processes at runtime. Monitoring means the monitoring of message flow, the analysis and further processing of non-processed messages, and so on.

 

The transition from technical configuration (an administrative task) to the configuration of the business process, is continuous. Therefore, the IDoc adapter must access metadata that describes the structure of an IDoc, for example.  The business process (configuration) determines which IDocs are to be processed. To access the metadata of an IDoc, there must be an RFC connection to the system that needs to send the IDocs (technical configuration). The latter is the task of an administrator, the former that of a consultant.

User Roles

To access the functions of SAP Exchange Infrastructure, you require the authorizations that are connected to the user roles. They roughly correspond to the task areas described above.

Roles for ABAP and Java Tools

Role	Tasks
SAP_XI_DISPLAY_USER	Combination of the display authorizations of all tools in Exchange Infrastructure.
SAP_XI_DEVELOPER	Design of business scenarios, interfaces, mappings, proxy generation, and their implementation.
SAP_XI_CONFIGURATOR	Make settings for logical and technical routing, determine sender and receiver interfaces by using mapping relations, logon data, maintain business systems and configuration data for the IDoc adapter.
SAP_XI_CONTENT_ORGANIZER	Organize and structure the contents of the Integration Repository, Integration Directory, and System Landscape Directory, tasks not normally carried out by a developer. For example, maintenance of software components.
SAP_XI_MONITOR	Monitor XML messages (for example, their throughput), error handling, and status tracking. This also includes the monitoring of processed IDocs and RFCs in the corresponding adapters.
SAP_XI_ADMINISTRATOR	Administration and technical configuration, see above.

On the ABAP side, the transactions assigned to these roles can be accessed from the user-specific menus.

Technically speaking, the roles specified here are composite roles that each reference a single role for accessing Java applications and a single role for accessing the respective ABAP transactions. Users must only be assigned composite roles. You then have automatic access to the ABAP and the Java tools.

Since user-management is ABAP-based, every user must first log on to the ABAP side to change his or her initial password.

Accessing Tools

The tools of the Exchange Infrastructure are implemented both as ABAP transactions and Java applications.

·        SAP systems that were installed for the SAP Exchange Infrastructure Add-On provide ABAP transactions for the configuration of the Integration Engine and the IDoc adapter, for the generation of ABAP proxies, and for monitoring. When the user logs on to an SAP system of this type and they have been assigned one of the roles specified above, they can use their personal user menu to access the transactions they require. Alternatively, the user can access the same transactions from the area menu (transaction S_EXCH_INFRA).

·        The Java part of SAP Exchange Infrastructure is accessed from a start page. You can access this start page from the respective user menu, from the area menu, and from certain ABAP transactions (Start Integration Builder). Alternatively, you can access it directly by calling transaction SXMB_IFR.

If you know the HTTP address of the Integration Builder, you can also call this link directly in the web browser.

Integration Builder: Start Page

Besides being able to access the Integration Builder from the start page, you can also call the following: The Runtime Workbench, the System Landscape Directory (see also System Landscape Directory in SAP Exchange Infrastructure), and the Adapter Engine including the RFC adapter and the MarketSet adapter (if installed).

Functions of the Integration Builder

Phase	Functions	Link to Start Page
Design	Designing Business Scenarios, Interfaces and Mappings, as well as Java Proxy Generation.	Repository (Design)
Configuration	Routing Configuration, Defining Mapping Relations, Defining End Points, Defining Logon Data	Directory (Configuration)