Registering the Provider Systems (SAP Library

Registering the Provider Systems

Procedure

Each UWL iView can retrieve work items from multiple business workflow back-end systems. Register each back-end connection to be used with the following procedure:

On the port...

1. On the portal, choose System Administration ® System Configuration.

2. In Detailed Navigation choose Universal Worklist and Workflow ® Universal Worklist.

3. Choose UWL Systems Configuration ® Universal Worklist Systems.

The Universal Worklist Systems list appears. Here you can define connectors and systems as item providers for the Universal Worklist.

4. To add a new entry, choose New.

See the following table for a description of your entries.

Parameter	Description and Use
Name	A unique name for this back end system configuration entry.
Connector	This is the identifier with which the connector is registered. For example: WebFlowConnector. For systems with WebFlowConnector as the connector, after defining a new system its item types have to be registered with the UWL service through the Universal Worklist Webflow Type Admin iView. For more information, see UWL Connectors.
Configuration Groups	Leave this blank, when working with the default UWL iView. If you are configuring a large system landscape, see the next section, Configuring a Large System Landscape for more information.
System Alias	The name of the alias for the back end system, as defined in the system landscape. The length of the system alias cannot exceed 25 characters.
Web Dynpro System	Enter the Web Dynpro system name if the Web AS for the system is not the same as that running the Web Dynpro. Leave empty otherwise. For more information see, SAPWebDynproLauncher .
User Roles	Restricts who can get work items via the user role. For example, you can assign a portal role here, such as buyer. Only users with the role buyer will see items from the provider system in UWL. You can have multiple user roles separated by semi-colon. For more information, see *User Roles* below.

5. You can add a new system, and/or duplicate, edit and delete existing ones. To save the current system registration, choose OK.

6. Multiple system connections are defined by repeating the above steps 1 to 4.

The above registration procedure is usually sufficient to use a UWL iView.

Note

After configuration changes in the back end system, you must re-register the system. For example, if you use the transaction SWFVISUto change the visualization, then you must register the item types again.

Continue with Register the Work Item Types, unless you have a large system landscape.

User Roles

By specifying user roles for the portal users, it can be restricted as to who gets the work items in UWL. For example, you can assign a portal role to a user, such as buyer. Only users with the role buyer will see items from a system, for example, B7QCLNT000in UWL.

Note

User roles and configuration groups are not mutually exclusive.

Example Scenario

The following description and figure illustrate the purpose of the Universal Worklist Systems list registration. It shows the case where two UWL iViews have been defined.

The following figure illustrates the connections and access rights for the two types of users:

This graphic is explained in the accompanying text

Suppose you have three back-end servers: A, B, and C. Each server has a business workflow application running.

Users with role 1 are given access to servers A and B, but not C.

But only, users with role 2 have access to C.

User 1 with role 1, logs onto the default UWL iView and must be connected to back end servers A and B. User 2 with role 2, logs onto the UWL iView and must be connected to back end servers B and C.

To achieve this scenario, the Universal Worklist System Systems list can be configured as shown in the following table.

Roles	Connector	System Alias
Role 1	WebFlowConnector	A
Role 1, Role 2	WebFlowConnector	B
Role 2	WebFlowConnector	C

Configuring a Large System Landscape

When UWL is first installed, one UWL iView is defined. The Configuration Group property for that iView is empty (blank). This means that no System Configuration Group is named, but in effect there is only a single group. The default behavior for the blank setting is this: when any user logs onto the UWL iView, UWL tries to log that user onto all registered backend systems.

There is a limitation with the blank setting. When a large number of systems are accessed during log on, the overall portal load is increased. Also, the user receives error messages from those backend systems that have no user account for the particular UWL user.

For large system landscapes do the following:

...

1. Partition backend systems into groups. This is accomplished by creating additional UWL iView instances, each of which refers to a specific group of back end systems.

The group is defined, using the System Configuration Group iView property.

2. Then use the value of the System Configuration Group property when registering back end systems by placing it in parameter Configuration Group, when you register the SAP system.

Example Scenario

The following description and figure illustrate the purpose of the Universal Worklist Systems list registration. It shows the case where two UWL iViews have been defined.

Suppose you have three back end servers: A, B, and C. Each server has a Business Workflow application running.

Regular users are given access to servers A and B, but not C. Only managers have access to C. Managers also access B in the course of their work.

Two UWL iViews are configured:

The default iView with the Configuration Groups property set to the value regular.
An added iView with the Configuration Groups property set to the value restricted.

The following figure illustrates the connections and access rights for the two types of users.

This graphic is explained in the accompanying text

User 1 logs onto the default UWL iView and must be connected to back end servers A and B. User 2 logs onto the Manager UWL iView and must be connected to back end servers B and C.

To achieve this scenario, the Universal Worklist System list can be configured as shown in the following table.

Configuration Group	Connector	System Alias
Regular	WebFlowConnector	A
Regular	WebFlowConnector	B
Manager	WebFlowConnector	B
Manager	WebFlowConnector	C