Configuring Guided Procedures with the Universal Worklist (SAP Library

Configuring Guided Procedures with the Universal Worklist

Use

You can configure your system so that the tasks generated in Guided Procedures (GP) workflows, 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 GP system or connect remotely to another GP system. If you are connecting remotely to the GP system, you first have to create a portal system and then register it and assign a system alias. If you are using a local GP system, you directly create the system alias without creating a portal system.

You perform the configuration steps on the consumer side:

...

1. Create a portal system, specifying the host name, HTTP port of the GP tasks provider and, if available, the WSDL of the relevant service.

You execute this step only if you are connecting remotely to the GP system.

2. Register the system as the item provider for UWL and configure it for remote access.

You establish the connection between GP and the UWL by assigning a system alias.

3. In UWL, browse all pending GP tasks assigned to your user.

You can only view tasks assigned to your user, that is, the logon ID of the user on both systems must match.

This graphic is explained in the accompanying text

Prerequisites

● You have been assigned the System Admin portal role to be able to create portal systems and aliases. For more information, see Administration Roles.

● You have been assigned the Standard User role to be able to access UWL in the portal. For more information, see Default Portal Content for Standard Users.

● You know the host name of the system from which you want to retrieve GP tasks.

Procedure

...

1. Create a Portal System

You need to create a portal system only if you are connecting remotely to the GP system. If you are using a local GP system, you directly register a system alias.

...

1. In the portal, navigate to System Administration ® System Configuration ® System Landscape.

2. Select a preferred location in the Portal Content catalog and create a new system.

From the context menu, choose New ® System (from PAR).

3. In the following steps of the System Wizard, select:

a. com.sap.portal.systems.webservices portal archive (PAR)

b. webservice_system portal component

4. On the General Properties screen, enter System Name, System ID and Master Language for the new system and choose Next.

5. Choose Finish and open the system object for editing.

6. From the Property Category dropdown box, select Web Services.

a. In the WSDL URL field, enter the host name and port of the GP task service in the format http://<host>:<port>/GPWorkItemProvider/Default?wsdl or http://<host>:<port>/.

Caution

To be able to access and use the GPWorkItemProvider Web service, you have to configure the relevant Web service security options first:

i. In the Visual Administrator tool, navigate to Cluster ® <system ID> ® Server <instance number> ® Services ® Web Services Security.

ii. Under Web Services, select Security Configuration ® Web Service Clients ® sap.com caf~eu~gp~model~uwlproxy ® com.sap.caf.eu.gp.model.uwl.proxy.facade*DefaultPort_Document.

iii. Set the authentication type to BASIC and provide a username and password. These credentials must match the administrator’s username and password on the provider system.

Make sure that you have assigned the portal role GP Administrator to the user that accesses the Web service.

More information: Portal Roles

iv. Save the changes.

b. Choose Save.

7. From the Display dropdown box, select System Aliases.

a. Enter an arbitrary but meaningful name for the system alias, for example GPremote.

b. Choose Add and save the changes.

8. Optionally, you can test the connection on the Connection Tests screen.

For more information about creating portal systems, see Running the System Landscape Wizard.

2. Register a System Alias as Item Provider for UWL

...

1. In the portal, navigate to System Administration ® System Configuration ® Universal Worklist & Workflow ® Universal Worklist – Administration.

2. Create an alias by choosing New and enter a name of the system alias.

Note

If you are connecting remotely to the GP system, you must use the name of the portal system you created previously as a system alias name.

3. From the Connector Type dropdown box, select the GuidedProceduresConnector and choose Save.

4. To configure UWL item behavior, use the Click to Administrate Item Types and View Definitions link.

a. From the Current Configurations tab page, download the uwl.gp.config file and add an item type for the alias you have created.

The name of the item type must be a concatenation of the uwl.task.gp string and the alias name, for example uwl.task.gp.GPremote.

Note

For remote systems, you have to use the UrlLauncher handler and provide an external URL to access the runtime. For more information, see the example below.

b. Save the file and upload it using the Upload New Configuration tab page.

Specify uwl.gp.config as the configuration name and browse to find the file on your file system.

c. Choose Upload.

For more information about UWL provider systems administration, see Registering the Provider Systems.

3. Access GP Tasks in the UWL

...

1. Access the UWL at the top navigation level of the portal using Home ® Work ® Universal Worklist.

2. Select a task from the list and launch it.

Tasks on remote machines open in a separate browser window.

Example

In the example XML configuration below, replace <host>:<port> with the host name and port of the item provider.

For each item type, you may use a different system alias as long as it matches the one specified for the remote provider system from which you want to retrieve GP tasks.

XML Configuration for Local and Remote System Aliases

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE UWLConfiguration PUBLIC '-//SAP//UWL1.0//EN' 'uwl_configuration.dtd'

<!-- configuration node for local system gp portal,

where _SystemAlias_for_local_system_ is the alias of the local system -->

</Properties>

</Action>

</Actions>

</ItemType>

</Properties>

</Action>

</Properties>

</Action>

</Properties>

</Action>

</Actions>

</ItemType>

<!-- configuration node for remote system,

where _SystemAlias_for_remote_system_ is it's alias,

_host_ is the host of remote system and _port_ is it's port -->

</Properties>

</Action>

</Actions>

</ItemType>

</Properties>

</Action>

</Properties>

</Action>

</Properties>

</Action>

</Actions>

</ItemType>

</ItemTypes>

<Views>

</ShortDescriptions>

</Descriptions>

</ShortDescriptions>

</Descriptions>

</DisplayAttribute>

</ShortDescriptions>

</Descriptions>

</DisplayAttribute>

</DisplayAttributes>

</View>

</Views>

</UWLConfiguration>