You have deployed consumer applications on your client system.
You have configured connections to provider systems on which the Web services are running.
For more information, see Creating Connections to Provider Systems .
You have configured user accounts for all Web services that you want to consume.
For more information, see Creating User Accounts .
SAP NetWeaver Administrator allows you to create and configure the consumer side of business scenarios out of different consumer applications. To create a business scenario, you create a collection of Service Groups from the applications that are built in different tool sets and deployed on your client system. You create the collection and use it for a particular business scenario that may involve multiple applications.
When you configure the consumer side of a business scenario, you specify the runtime settings that apply to the applications in the scenario. You configure the consumer side of a business scenario by assigning a connection to a provider system to each of its Service Groups. The framework creates configuration entities (logical ports) for the consumer proxies that consume the Web services grouped in the Service Groups. The logical port contains the exact policies and settings and enables the applications in the scenario to consume a Web service. If the consumer application is not designed to call a specific logical port for a service, it calls the logical port that is marked as default . The newly created logical port is marked as the default one only if the application does not have an existing default logical port by the time of the configuration (the assignment of the Service Group).
You can configure RFC connectivity only to consumer applications that are created with the Business Process Management (BPM) tools or Service Composition tools. When you configure the client applications, you can consume remote function modules located on remote business systems. You cannot configure other consumer applications to use RFC connectivity and therefore consume the respective remote function modules.
Alternatively, you can use the quick link /businesscfg as follows:
The Business Scenario Communication screen opens.
Create a new scenario. For more information, see Creating Business Scenarios .
Edit an existing scenario. For more information, see Editing Business Scenarios .
Select a business scenario and activate or deactivate it using the corresponding button. The effects of performing each of these actions is as follows:
For every Service Group in the activated scenario to which an active provider system connection has been assigned, the system creates a logical port to the consumer proxy that refers to the Service Group. The logical port has the runtime settings of the connection to the provider system.
When you deactivate scenarios, the system considers them deleted. However, the business scenario and its assignments keep existing on the system, and you can activate and use them again at a later stage.
For every Service Group in the deactivated scenario, the system deletes the logical ports of the consumer proxies that refer to the service references.
After you save the business scenario, the system performs a background process. During the background process, the framework examines the connections to the provider systems that you assigned to the Service Groups, and creates configuration entities for the consumer proxies - logical ports. The system applies the settings from the provider system's connections to the logical ports.
The Processing State column of the Service Group table shows the state of the configuration. You can display more information about the processing state in the Log Viewer application.
You can display the logging and tracing information about a Service Group or a service provided in a consumer application by choosing the Show Log or Show Trace buttons, respectively. The system opens the log viewing application and displays additional information about the current assignment. For more information, see Log Viewer .
If the WSDL document of the service endpoint that the client application consumes (using a service reference) does not contain any policies or SAP-specific features, the security mechanism of a service endpoint cannot be determined. In this case, SOA configuration for connectivity examines only the security policies of the communication profile that is used in the system connection and the assigned user account. The system tries to consume the service endpoint using the available security mechanisms and creates a logical port for the successful attempts.
Despite the created configuration entities, it is possible that the logical port remains inconsistent with the security policies of the service endpoint and thus cannot consume the Web service correctly. In this case, the system displays the Processed with Warnings status of the Service Group assignment. This warning shows that the communication between the logical port and the service endpoint may be corrupted or even impossible. We recommend that you manually create configuration entities (logical ports) of the Service Groups (and the respective service references) which consume service endpoints whose security policies cannot be determined.
In Single Service Administration , you can browse the created logical ports only for Java EE consumers and Composite Application Framework (CAF) applications that consume Web services. You cannot browse configuration entities of the following consumer proxies:
Callable objects that are created with the Guided Procedures framework
Automated activities and events that are created with the Business Process Management framework
Adaptive Web service models that are created with the Web Dynpro framework
Web service operations that are created with the Visual Composer framework