Show TOC

Configuring the Task Gateway ServiceLocate this document in the navigation structure

The Task Gateway service provides an access point for consumer applications to different tasks using SAP Gateway. This OData service allows different task providers to expose tasks within one harmonized view.

For more information about role templates required for configuration, see User, Developer, and Administrator Authorizations.

Prerequisites
  • If you have an SAP NetWeaver Business Process Management (BPM) system, you must create a logical port to it before installing the Task Gateway service.

  • To integrate BPM, you require SAP NetWeaver 7.31 SP05 or higher.

To create a logical port:

  1. In your SAP Gateway system, open transaction SOAMANAGER.

  2. Select the Service Administration tab.

  3. Choose Single Service Configuration.

  4. From the Search by: by drop-down list, select Consumer Proxy.

  5. In the Search Pattern: field, enter TaskFacade.

  6. From the Field: by drop-down list, select External Name.

  7. Choose Go.

  8. In the Search Results table, select the consumer proxy.

  9. Choose Apply Selection.

  10. In the Details of Proxy Definition section, select the Configurations tab.

  11. Choose Create Logical Port. The SOA Management popup is displayed.

  12. In the Logical Port Name field, enter the port name.

  13. In the Description field, enter a description providing additional information about the connection.

  14. Under Configuration Type, select the Manual Configuration radio button.

  15. Choose Apply Settings.

  16. In the Configuration for Logical Port section, select the Transport Settings tab.

  17. In the URL Access Path field, enter TaskFacadeService/TaskFacade.

  18. In the Computer Name of Access URL field, enter the computer's name.

  19. In the Port Number of Access URL field, enter the relevant port number.

  20. Select the Consumer Security tab.

  21. Under the Authentication Settings section, select the SAP Authentication Assertion Ticket  radio button.

    Note

    For more information about SSO (Single Sign On), see the SAP NetWeaver documentation about Administration for User Authentication and Single Sign-On (SSO).

  22. Save the changes.

Installing the Service

To use the Task Gateway service:

  • If your system landscape is based on SAP NetWeaver 7.0, 7.01, 7.02, 7.03 or 7.31, you must first install the components IW_PGW and IW_BEP in your SAP Gateway system. To support the Business Workflow, you must also install the component IW_BEP in your SAP Business Suite system.

  • If your system landscape is based on SAP NetWeaver 7.40 or higher, it contains the core SAP Gateway component SAP_GWFND as standard and as such you do not need to install IW_BEP in your SAP Gateway system. However, you must install the component IW_PGW.

For more information, see Deployment Options.

Activating the Service

Activating the service consists of two main steps:

  1. Setting up the service in the SAP Gateway system:

    • Create a system alias.

    • Activate the service.

    • Assign the software version to the service.

  2. Connecting the service to the SAP Business Suite backend system where you want to have the SAP Gateway information displayed:

    • Add additional system aliases.

The service uses the multi-origin composition (MOC) component. For more information, see the Multiple Origin Composition section.

To create a system alias:

  1. In the SAP Gateway system, open transaction SPRO.

  2. Choose SAP Reference IMG .

  3. Select Start of the navigation path SAP Customizing Implementation Guide Next navigation step SAP NetWeaver  Next navigation step  SAP Gateway Next navigation step OData Channel Next navigation step Configuration Next navigation step  Connection Settings Next navigation step SAP Gateway to SAP System End of the navigation path.

  4. Open the Manage SAP System Aliases activity. TheChange View “Manage SAP System Aliases”: Overview page is displayed.

  5. Choose New Entries.

  6. In the Manage SAP System Aliases table, enter the following:

    • Under SAP System Alias, enter the new system alias. For example, GWQ_800_BEP.

    • Under Description, enter a description for the system alias.

    • Under Local SAP GW, make sure the checkbox is not selected.

    • Under For Local App, select the checkbox.

    • Under RFC Destination, enter the trusted RFC destination to the SAP system.

      Note

      If you have an SAP NetWeaver BPM system, set WS Provider System as the RFC Destination.

    • Under Software Version, press F4 and select the relevant data provider (software version), for example, /IWPGW/BWF or/IWPGW/BPM (for a BPM system).

  7. Choose Save.

  8. To create additional system aliases for other providers like BPM repeat steps 5 to 7.

To activate the service:

  1. In the SAP Gateway system, open transaction SPRO.

  2. Choose SAP Reference IMG .

  3. Select Start of the navigation path SAP Customizing Implementation Guide Next navigation step SAP NetWeaver  Next navigation step SAP Gateway Next navigation step OData Channel Development with IW_BEP Next navigation step Registration End of the navigation path.

  4. Open the Activate and Maintain Services activity.

  5. Choose Add New Service. The Add Service page is displayed.

  6. In the System Alias field, press F4 and select the system alias you created in the procedure above.

  7. Press Enter. The Add Service table is populated.

  8. From the Technical Service Name column, double-click /IWPGW/TASKPROCESSING. The Add Service page is displayed.

  9. Copy the name that appears in the Technical Model Name field, you will need it to assign the software version to the service.

  10. In the Package field, enter the package to which you want to assign the service.

  11. Choose the checkmark. The Activate and Maintain Services page is displayed.

  12. Under the ICF Nodes section, make sure the ODATA node status is set to Active.

  13. Under the System Aliases section, make sure the system alias we activated is displayed.

To assign the software version to the service:

  1. In the SAP Gateway system, open transaction SPRO.

  2. Choose SAP Reference IMG .

  3. Select Start of the navigation path SAP Customizing Implementation Guide Next navigation step SAP NetWeaver  Next navigation step  SAP Gateway Next navigation step OData Channel Development with IW_BEP  Next navigation step Registration End of the navigation path.

  4. Open the Assign Data Provider to Data Model activity. TheChange View “Assign Data Provider to Data Model”: Overview page is displayed.

  5. Choose New Entries.

  6. In the Assign Data Provider to Data Model table, enter the following:

    • Under Model Identifier, enter the technical name you obtained in the previous step (To activate the service) followed by _0001_BE. For example, <model identifier name>_0001_BE.

    • Under Type, select (Adaptation) Data Provider from the drop-down list.

    • Under Software Version, press F4 and select the relevant software version for example /IWPGW/BPM or /IWPGW/BWF.

    • Under Class/Interface, enter /IWFND/CL_MGW_RUNT_RCLNT_PRXY.

    • Under Description, enter a description of the data model.

    • Under Model Name, enter enter the technical name you obtained in the previous step (To activate the service).

  7. Choose Save.

  8. To create additional software versions, repeat steps 5 to 7.

To add additional system aliases:

  1. Create a new system alias as described in the procedure above.

  2. In the SAP Gateway system, open transaction SPRO.

  3. Choose SAP Reference IMG .

  4. Select Start of the navigation path SAP Customizing Implementation Guide Next navigation step SAP NetWeaver  Next navigation step SAP Gateway Next navigation step  OData Channel  Next navigation step OData Channel Development with IW_BEP Next navigation step Registration End of the navigation path.

  5. Open the Activate and Maintain Services activity. The Activate and Maintain Services page is displayed.

  6. In the Service Catalog table, search for TASKPROCESSING in the External Service Name column and select the entire line.

  7. In the System Aliases section, choose Add System Alias. The Change View “Assign SAP System Aliases to OData Service”: Overview page is displayed.

  8. Select an existing SAP system alias and choose Copy.

  9. In the SAP System Alias field, press F4 and select the System Alias you have created.

  10. In the Default System field, the checkbox does not need to be selected. If the checkbox is selected, the corresponding SAP system will be called by default.

  11. Choose Copy.

  12. Choose Save.

Note

For the role template /IWPGW/RT_WF_USR, you must maintain the authorization object S_SERVICE with the object types IWSG and IWSV. For more information, seeRoles in the SAP Gateway Landscape, section Assignment of Authorization Objects.

Once your service is activated you can navigate to the Task collection to get all your inbox tasks from the implemented providers, such as Business Workflow and BPM. For example: http://<Server>:<Port>/sap/opu/odata/IWPGW/TASKPROCESSING;mo/TaskCollection

Adding New Providers

Task SAP Gateway service has two providers out-of-the-box: a provider for SAP Business Workflow, and one for BPM.

If you require an additional provider, you must add it manually.

To add a new provider:

  1. In your SAP Gateway system, open transaction SPRO.

  2. Choose SAP Reference IMG.

  3. Select Start of the navigation path SAP NetWeaver Next navigation step SAP Gateway Service Enablement Next navigation step Content Next navigation step Task Gateway Service  Next navigation step Registration End of the navigation path.

  4. Open the Provider Implementation activity and follow the instructions described in the activity's documentation.