Using Service Groups

"Containers" for service groups (that is, multiple service groups) can be bundled within a single entity. This is relevant for applications accessing services provided by multiple systems, for example:

• One service group for consuming services from an ABAP ERP back end system.
• Another service group for calling services provided by a local Java application server.

To set the business scenario, use the following path: SAP NetWeaver Administrator → SOA Management → Application and Scenario Management → Business Scenario Communication.

The figure illustrates the required steps the create a new business scenario. To start the creation of a Business Scenario, you have to choose New in the relevant screen. This opens a wizard.

The figure illustrates, how you can add a service group.

The figure illustrates, how you can add a provider system to the service group.

To set provisioning, use the following path: SAP NetWeaver Administrator → SOA Management → Application and Scenario Management → Application Communication.

Web Services Configuration

You can apply runtime configuration settings to multiple service definitions of an application at one go. You decide which service definitions in an application to configure and expose for consumption with which runtime settings. Find and choose the application, which you want to configure. You can find applications by entering a string in the Search field.

The figure, Configuring Web Service Providers: Configure Applications, illustrates the process to configure a web service provider.

Shared service groups are defined with a dedicated development component. Shared service groups have the following properties:

• They can be deployed separately from the rest of the application.
• They can be referenced and used by multiple Business Process Management (BPM), Web Dynpro Java (WDJ), and Composite Application Framework (CAF) development components.

Development components that make use of shared service groups need to have a reference to the service group development component.

For CAF development components, the following applies:

• Deploy time and runtime dependency from CAF ear DC to service group DC.
• Design time dependency from CAF ebj module DC to service group DC.

BPM/WDJ development components must have, design time, deploy time, and runtime dependencies from the BPM/WDJ development component to the service group development component.

The figure shows the place in which the required settings for design time, deploy time and runtime will take place.

The processing of a service group in the provider system ABAP can fail when some of the services contained in the group are currently unavailable in the back end system (for example, due to a failed mass configuration run).

The processing of a service group in the provider system Java can fail due to the following situations:

• Services that are provided by a Java server initially do not support authentication.
• If an authentication method is specified for the service group, the processing fails because the services do not support the required security features.
• The authentication methods the Java services are meant to support have are not configured in SAP NetWeaver Administrator (NWA) after the services have been deployed. If this configuration does match the service group, the processing succeeds.

The path for troubleshooting is SAP NetWeaver Administrator → SOA Management → Application and Scenario Management → Single Service Administration.

The figures illustrates the steps and screens, which are required to perform troubleshooting.