Show TOC

Procedure documentationConfiguring Business Process Management with the UWL Locate this document in the navigation structure


You can configure your system so that the tasks generated in Business Process Management (BPM), both on local and remote systems, are displayed in the Universal Worklist (UWL) together with the tasks pertaining to other SAP NetWeaver Portal work areas. You can either use a local BPM system or connect remotely to another BPM system. To connect remotely:

  1. Create a portal system, specifying the properties of the BPM task provider.

  2. Register the system as the item provider for UWL.

  3. Configure the provider (BPM) system to trust the consumer (UWL) system.

If you are using a local BPM system, the BPM UWL connector is automatically registered and you do not have to create a portal system.

You access the UWL at the top navigation level of the portal using Home Work. The Home tab is covered by the Every User Role portal role.

For more information: see Managing BPM Tasks in the Universal Worklist. PUT LINK

This graphic is explained in the accompanying text.

This section describes how you configure BPM for the UWL.


  • To create portal systems and aliases, you need to have the System Admin portal role assigned.

    For more information, see Administration Roles.

  • You have the Every User Core Role (eu-role, id: pcd:portal_content/every_user/general/eu_role) assigned in order to access UWL in the portal.

    For more information, see Configuring the Universal Worklist.

  • You know the parameters of the system from which you want to retrieve BPM tasks.

  • You have system administration permissions on the BPM provider system so you can establish a trusted relationship with the UWL consumer system.


Local Connection

When running both BPM and UWL on the same system, the BPM UWL connector is automatically configured. The successful registration of the connector is confirmed in the NetWeaver portal.

  1. Log in as an Administrator to the portal through http://<host>:<port>/irj.

  2. Open the System Administration tab page and navigate to   System Configuration   Universal Worklist & Workflow   Universal Worklist   Administration   .

  3. Under the Universal Worklist System table, check that BPEMUWLConnector is registered with the predefined SAP_LocalSystem system alias.

    Note Note

    In case the connector registration is not successful, you can manually register it without explicitly creating the SAP_LocalSystem.

    End of the note.
  4. From the initial portal page, navigate to   Work   Universal Worklist  .

  5. Open the dropdown menu in the top right corner of the worklist and select Display Connection Status. In the dialog that appears, check whether the connection to the provider system is successful.

Note Note

Each time you restart the UWL service or your engine, the BPM UWL connector is registered once again. To avoid automatic registration of the local system each time you restart the engine, disable this function in the UWL Administration.

For more information, see Restarting the UWL Service and Registering the Provider Systems.

End of the note.
Remote Connection

When connecting remotely to a BPM system, you need to manually configure both the provider and the consumer side. The communication between them is based on HTTP(S) connection. No explicit user mappings are necessary, but the administrator must ensure users on both systems have the same authorizations.

1. Set Up the Provider System
  1. Log on as an administrator to the SAP NetWeaver Administrator on the provider system (http://<host>:<port>/nwa).

  2. Navigate to   Configuration Management   Security   Trusted Systems  .

  3. Choose the Add Trusted System pushbutton and select By Querying Trusted System. On the dialog that appears, choose the Cancel pushbutton.

  4. As System Type choose JAVA.

  5. Fill in the required credentials of the BPM consumer system. Enter the host name, the port number, and the administrator user name and password of the consumer system.

  6. Choose the Next and then the Finish pushbutton.

    Your consumer system is now displayed in the list of trusted systems.

Caution Caution

If the consumer system SAPLogonTicketKeypair has the same Subject DN and Issuer DN as the provider system, a message is displayed like the following: You have chosen to upload a certificate that will replace the "SAPLogonTicketKeypair" certificate; this is not allowed.. You have to create a new SAPLogonTicketKeypair certificate on the consumer system. For more information about key pair and public key certificates, see Configuring Security and Creating a Key Pair and Public-Key Certificate.

End of the caution.
Configure the mail properties for federated portal scenario
  1. Log on as an administrator to the SAP NetWeaver Administrator on the provider system (http://<host>:<port>/nwa).

  2. Choose   Configuration   Infrastructure   Java System Properties  .

  3. On the Applications tab page, locate the tc~bpem~base~ear application.

  4. On the Properties tab page in the Extended Details table, set the following values for your remote system:


    http://<host>:<port> of the provider system


    http://<host>:<port> of the consumer system

2. Set Up the Consumer System
  1. In the portal, navigate to   System Administration   System Configuration   System Landscape  . Select a preferred location in the Portal Content catalog and choose a folder to create the provider system.

  2. From the context menu, choose   New   System (from template)  . Under Available Templates, select the SAP system with load balancing radio button. Enter the required base properties of the system such as ID, name, etc.

  3. Under Properties enter the following properties of the BPM (provider) system:

    • Web AS Hostname<host>.<domain>:<port>

    • ICM Protocolhttp or https

    • User Mapping Typeadmin,user

  4. Under System Aliases create a new system alias. It is used to register the connector with the provider system.

  5. Under Permissions search for the Authenticated Users group and add it to the table. Set a Read permission to it and check the End User checkbox.

    Note Note

    Users need the BPEM End User (pcd:portal_content/ portal role assigned on the BPM (provider) to open the task execution UIs.

    End of the note.
3. Register the System Alias as the Item Provider for UWL
  1. In the portal, navigate to   System Administration   System Configuration   Universal Worklist & Workflow   Universal Worklist – Administration  .

  2. Choose the New pushbutton and enter the system alias added in step 2.4 above.

  3. From the Connector Type dropdown menu, select BPEMUWLConnector.

  4. Save your settings. You can check the status of the connector as described in the Local Connection section.

The clocks on the UWL (consumer) and the BPM (provider) systems need to be synchronous. Otherwise, the single sign-on mechanism may fail and the connection between the system may not be established.

For information about using the Universal Worklist features, and definitions of key terms on the user interface, see Managing Tasks and Alerts in the Universal Worklist.