SAP EP – Netweaver Portal

Symptom
UWL Connector cannot read technical information from the backend. The error message that appears is one of the followings: “System <SYSTEM ALIAS> is not configured for optimized delta
pull. Check the uwl_service user configuration”
“No RFC authorization for function module <FUNCTION_MODULE_NAME>”,
“(Connector) :com.sap.mw.jco.JCO$Exception:Name or password is incorrect (repeat logon)”
Itemtype configured in SWFVISU is not available in the WebFlowConnector configuration xml.
View history is missing from ‘You can also’ list.
System does not support substitution methods.
Failed to create subsitution from provider.
Other terms
UWL Webflow, UWL BusinessWorkFlow, UWL Connector, Destination service, view history missing, not support substitution, create substitution failed, itemtype not available
Reason and Prerequisites
incompatible change in UME API and the UWL_SERVICE user cannot be used to connect to the backend and retrieve technical informations. Instead of this an RFC destination has to be configured.
Solution
In order to connect to the backend an RFC connection has to be configured in the Destination Service.
The following patches or service packs contain the fix for UWL_SERVICE user refactoring on the optimized delta pull of WebFlowConnector. It only applies for mentioned connector.
Netweaver 7.0 SP11 Patch 6 for software component UWLJWF needs to be applied.
Netweaver 7.0 SP12 Patch 4 for software component UWLJWF needs to be applied.
Netweaver 7.0 SP13 Patch 2 for software component UWLJWF needs to be applied.
Netweaver 7.0 SP14 Patch 1 for software component UWLJWF needs to be applied.
Netweaver 7.0 SP15 for software component UWLJWF needs to be applied.
Netweaver 7.0 SP16 Patch 1 for software component UWLJWF needs to be applied.
Starting with NW 7.0 SP17 the fix is part of the normal SP delivery.
RFC destination confiuration is required along with the fix in every case!!!
The UWL_SERVICE user was refactored for all connector types in Netweaver 7.01 SP00 (and in higher service packs). All connector types require the configuration of RFC destination.
In Netweaver 7.0 (former NW4s) version the following steps has to be performed to create RFC destination:
1. Open the Visual Administrator.
2. Navigate to the Cluster -> <INSTANCE ID> -> Server <SERVER NAME> -> Services -> Destinations.
3. Double click on Destinations node.
4. Under Destinations select RFC node.
5. Click on “New” button.
6. In the “Enter destination name:” input dialog give as destination name the following: <SYSTEM ALIAS>$<UWL CONNECTOR TYPE>
(e.g.: BXTCLNT100$WebFlowConnector )
7. Fill in the following fields: System ID, Message Server, Logon Group, Language, Client, Username, Password. The other fields remain default. (Make sure the user you specify has “SAP_BC_UWL_SERVICE” role assigned. This is needed to fetch the technical informations from the backend.)
8. Click on the “Save and Test” button
9. “Successfully connected to system <SYSTEM ID> as user <Username>” info dialog has to appear.
10. In other cases check the settings again and check the connection to the backend system.

The following patches contain the fix for UWL_SERVICE user refactoring in case of BTM connector.
Netweaver 7.1 SP2.PAT06 for software component UWLJWF needs to be applied.
Netweaver 7.1 SP5 for software component UWLJWF needs to be applied.

The UWL_SERVICE user was refactored for all connector types in Netweaver 7.10 SP5 Patch2 and 7.11 SP00 (and in higher service packs). All connector types require the configuration of RFC destination.
From Netweaver 7.1 on, the Netweaver Administrator should be used to create RFC destination:
1. Open the following portal page http://hostname:port/nwa
2. Go to Configuration Management -> Destinations. Here create the RFC destination using the following template: <SYSTEM ALIAS>$<UWL CONNECTOR TYPE> (e.g.: BXTCLNT100$WebFlowConnector ).
3. Fill in the following fields: System ID, Message Server, Logon Group, Language, Client, Username, Password. The other fields remain on default values. (Make sure that the specified user has “SAP_BC_UWL_SERVICE” right assigned. This is needed to fetch the technical informations from the backend.)
4. After the configuration of the RFC Destination a UWL Service restart is needed. Restart the UWL in NWA in the following section: Systems -> Start & Stop.
5. Here select Java EE Applications and in the Name filter write “uwl” and hit enter.
6. Select “com.sap.netweaver.bc.uwl” from the list and click on Stop -> On All Instances.
7. After that click on Start -> On All Instances.
8. Wait until the status of the uwl becomes “STARTED” in the Status column clicking on “Refresh” button.