This book is the synthesis of our experiences with SAP Exchange Infrastructure 3.0. As a component of the SAP Net Weaver ‘04 platform, SAP Exchange Infrastructure( SAP XI ) has become increasingly important since the fall of 2004. The advantages of the current Release 3.0 over Release 2.0 are apparent in many respects. Several well-known companies have since decided to use SAP XI to establish a stronger integration of the individual systems in their system landscapes and to begin the necessary consolidation procedures using this integration tool. Customizing the System Landscape Directory The System Landscape Directory ( SLD ) contains an over-view of all technical systems involved in the process, including the installed software components and versions.From the technical definition, an abstraction level called business system is defined. The business system reflects the individual clients of a technical system. A technical system is defined using the IP address, the server name,the dispatcher, and so forth. This technical system ( an R/3 system in our example ) uses a two-client structure.Both clients are to be provided with different data by the Exchange Infrastructure in future. Therefore, two business systems are created in the SLD for the technical system. In the following example, we assume that our technical system is T20 and the server is sapt20. The system is a 46C system functioning as a central vendor management system for a corporate group. Therefore, we call the system CVM ( Corporate Vendor Management ). In our example, this CVM system has the clients 100 and 131.To set up this technical system, we first have to log on to the R/3 system using SAP GUI. Call Transaction SXMB_IFR. Your locally installed web browser will open and dis-play the XI home page as shown in Chapter 2. Click on the relevant link to change to the SLD. The overview is displayed as shown in Figure 3.12. Software Catalog In the Software Catalog category, in addition to the in-formation about the technical and business systems, the software components involved in an interface or a business transaction are maintained. A software component is then regarded as a modular unit that can be implemented in different products of a software vendor. Aproduct is a composition of software components and can exist in different versions. In the SLD, the link between product versions and the component versions is mapped using objects of the software feature type.For the first interface, you should consider that soft-ware component versions are required during name space creation and are therefore a prerequisite for creating all dependent objects such as interface structures in the Integration Repository.From the main menu, we therefore go first to the Soft-ware Catalog category to define the necessary settings.The web page shown in Figure 3.13 is displayed.In the selection, you can now decide whether you want to create a new project or a new software component.

Download Mastering SAP XI Administration.