Skip to end of metadata
Go to start of metadata

Contents


 

How to create Fallback Logical Port

This article describes how to create a Fallback Logical Port in ABAP system.

Prerequisites

Incase there is an error in logical port generation during Business Scenario Configuration, logical port can still be created with this fallback method. Fallback logical port is necessary if you intend to use Service Group in the consumer application.

Service Group must be assigned to a Business Application before this method is used.

You need to have the following roles for this task: SAP_BC_WEBSERVICE_CONFIGURATOR
More information: SAP Note 1318883 (Introduction of new authorizations in Web Service)

Procedure

You configure a fallback logical port in the same way as for single service configuration. The only difference is that the logical port is set as the fallback logical port for a service group. The fallback logical port will overrule the logical port generated via business scenario configuration.

Creating a fallback logical port

  1. Start SOA Manager.
    Use transaction SOAMANAGER. SOA Manager is opened in a new window.

    The SOA Manager is an ABAP WebDynpro application. It is like each regular WD application using an ICF node for accessing it. You may use transaction SICF to check that the ICF node for SOA Manager transaction (/sap/bc/webdynpro/sap/appl_soap_management) is active.
    More information about this subject: SAP Note 1124553 and 1088717.

  1. Go to the Service Administration tab.
  2. Select Web Service Configuration.

  3. Select option ServiceGroup from dropdown Search by and Specify the service group. Press Go to search for the specified service group.

  4. Select the consumer proxy and choose Apply Selection.
    The configuration is displayed.

    To create a fallback logical port, the service group must first be assigned to a business application. If a service group is assigned to a business application, the business application and the consumer proxies are displayed.

  5. Go to the Configurations tab.
  6. Create and configure a fallback logical port.
    A fallback logical port is created in the same way as a manual logical port.

    You can specify only one fallback logical port for a fixed combination of service group, consumer proxy and business application. At runtime, only one service configuration can be used for fallback.

  7. Choose Save.
    The consumer proxy is now generated and configured.

  8. Activate the Pending Tasks for the service group.
    1. Go to the Service Administration tab.
    2. Choose Pending Tasks.
    3. An overview of configuration requests is displayed.
    4. Choose Start request queue processing.
    5. The requests are processed.

      If a fallback logical port exists for a service group, it will be used instead of the logical port generated via business scenario configuration. You can change the configuration for the fallback logical port in the same way as any other manual configuration. The assignment used in the service group remains unchanged. If you no longer need to use the fallback logical port, you need to delete it.

Deleting a Fallback Logical Port

If a fallback logical port exists, business scenario configuration cannot overwrite it. For this reason, you need to delete a fallback logical port manually.

  1. From the main screen of the SOA Manager, go to the Service Administration tab.
  2. Select Single Service Administration.
  3. Select the relevant service group.
  4. Select the consumer proxy below the business application and choose Apply Selection.
  5. The configuration is displayed.
  6. Go to the Configurations tab.
  7. Select the fallback logical port and choose Delete.

  8. Confirm.
    Fallback Logical Port is now deleted.
    When a fallback logical port is deleted, a new logical port can be generated via business scenario configuration if desired.
  9. Activate the Pending Tasks for the service group.
    1. Go to the Service Administration tab.
    2. Choose Pending Tasks.
    3. An overview of configuration requests is displayed.
    4. Choose Start request queue processing.
    5. The requests are processed.
  • No labels