General Configuration Steps
You must make certain settings before you can execute the demo examples. There are general cross-integration-scenario settings and integration-scenario-specific settings.
This section gives you an overview of all the general cross-integration-scenario settings.
You can find a detailed introduction explaining those general settings that are required for SAP's standard configuration in the SAP Community Network (SDN) under https://www.sdn.sap.com/irj/sdn/soa-servicebus. Under Previous Releases, choose SAP NetWeaver Process Integration 7.0 and on the following page, choose the SAP NetWeaver Process Integration Demo Examples - Configuration Guide document.
The integration-scenario-specific settings that you need to make for the individual integration scenarios are located in the description of the integration scenarios.
It is assumed
that the installation and
technical
configuration of SAP NetWeaver in the usage type Process Integration has
been completed correctly.
Defining a System Landscape – SAP Standard Configuration
To use the demo examples, you need application systems for the travel agency and the airlines. A prerequisite is that you use SAP systems that contain SAP Web Application Server (SAP NetWeaver 2004s).
SAP has provided a standard configuration for the demo examples. This comprises the following application systems:
· An application system for the travel agency (called TravelAgency) that uses the proxy runtime for communication
· An application system for the airline Lufthansa (called Airline_LH) that also uses the proxy runtime for communication
· An application system for the airline American Airlines (called Airline_AA) that either uses the proxy runtime or, if required, the RFC and IDoc runtime for communication
· An application system for the airline United Airlines (called Airline_UA) that serves as an external partner and that makes a Web service available for communication
Technically speaking, these application systems can be different SAP systems, but it is simpler to use several clients of one SAP system.
We recommend that you use the SAP standard configuration. Since the demo examples are only intended to demonstrate Process Integration and are not scenarios for productive use, SAP only provides support for the standard configuration.
The detailed setting instructions in the configuration instructions for the demo examples assume that you are using the standard configuration.
In addition, you need an SAP system with SAP NetWeaver 2004s installed. This system contains the Integration Server and the Integration Builder.
The application systems TravelAgency, Airline_LH, Airline_AA, and Airline_UA communicate using the Integration Server of the XI system. This is illustrated in the following graphic:
Connecting Application Systems to the Integration Server
To connect the application systems (for the travel agency and the airlines) to the central Integration Server and enable them to communicate, you must make all the relevant settings. This includes the following settings:
● Configuring the local Integration Engines in the application systems
● Defining the involved application systems as technical systems and business systems in the System Landscape Directory
● Defining the three business systems as business system services in the Integration Directory. You must also generate and define the corresponding communication channels.
For more detailed information, see the general SAP XI configuration guide.
Application-Specific Settings
You must also make the following settings (specific to the flight booking example) in the application systems.
● The demo examples require appropriate data in the flight data tables. You must generate this data in all the involved application systems.
● A Business Server Page is available for the travel agency functions. You must activate this in the travel agency system.
For more detailed information (for the SAP standard configuration), see the configuration guide for the demo examples.