Universal Worklist - Delta Pull Configuration Applies to: This article applied to SAP Netweaver 7.01 SP06 Portal, SAP ECC 6.0 EHP4. For more information, visit the Portal and Collaboration homepage Summary The purpose of this article is to explain the various steps involved in performing SAP Portal Universal Worklist (UWL) Delta Pull Configuration. Delta Pull Configuration is an optional task in the UWL Configuration task for the Portal Administrators. This is instrumental in Performance Optimization. Delta Pull mechanism of UWL enables new items to be fetched from the back end SAP systems every 60 seconds. You can configure UWL to refresh its task and alerts lists at time periods different than the minimum 60 second period. The user does not need to use the refresh function to update the inbox. Once items are retrieved, timestamps are updated for the users whose items are successfully retrieved. These retrieved items are updated in the UWL cache. Tasks and alerts are fetched only when the user is logged on to the system. Author: Dhanya Nayak Company: Accenture Created on: 29 th March 2011 Author Bio Dhanya Nayak is a SAP Enterprise Portal SME and Portal Development Lead working in Accenture. She is a SAP certified Enterprise Portal Development Consultant since 2005 and has extensive experience on various Portal implementation projects. 2011 SAP AG 1
Table of Contents Prerequisites... 3 Step 1: Default Portal System Alias... 4 Step 2: RFC Destination... 5 Step 3: Create ECC Delta Pull Background Jobs... 6 Create Variants... 6 Check the scheduled Jobs Status... 7 Step 4: Check if UWL is detecting Delta Pull Jobs... 8 Step 5: Provider Systems... 8 Step 6: Re-Register Provider Systems... 9 References... 9 Related Content... 10 Disclaimer and Liability Notice... 11 2011 SAP AG 2
Prerequisites 1. As a starting point the UWL Mandatory Configurations needs to be performed Mapping Portal Users to the System User Registering of Provider System Register Work Item Types 2. UWL_SERVICE user should have right authorization in the Provider Systems e.g. ECC 3. Check the ECC Spool for any SPOOL_INTERNAL_ERROR. Clear the Spool through regular ECC housekeeping activity (as required) for the ECC Delta Pull Jobs to work correctly. 2011 SAP AG 3
Step 1: Default Portal System Alias Default Portal System Alias need to be same format as Portal ECC System Object e.g. DE1CLNT200. 2011 SAP AG 4
Step 2: RFC Destination RFC Destination needs to be defined as below If this not defined already like specified below UWL Delta pull configuration won t work. RFC Destination is case-sensitive Needs to be same as default System Alias set for the Portal ECC System Object. For example If default system alias is DE1CLNT200, then RFC destination to be maintained is DE1CLNT200$WebFlowConnector Note: This can be done from Visual Admin / Netweaver Administrator (NWA). Preferred method is via NWA. In the above procedure user mapping to be done for UWL_SERVICE user. 2011 SAP AG 5
Step 3: Create ECC Delta Pull Background Jobs You need to define 2 jobs for Delta Pull One in FULL mode running once a day and Second in DELTA mode every 1-3 mins depending upon the performance of the backend system. Examples - ZHTRUWLECCFL -> For ECC: ABAP report RSWNUWLSEL in FULL mode, using ZHTR_UWLECC_FL variant. Run the job once a day. ZHTRUWLECCDL -> For ECC: ABAP report RSWNUWLSEL in DELTA mode (default). Run the job every three minutes. Create Variants Using TCODE SE38 Variants can be created. Note: Only for FULL mode custom Variant is required. DELTA is default mode for the program RSWNUWLSEL already, so no need to create a VARIANT. 2011 SAP AG 6
Check the scheduled Jobs Status Use TCODE SM37 and check the status of UWL Jobs. If running successfully it will display Finished status. 2011 SAP AG 7
Step 4: Check if UWL is detecting Delta Pull Jobs From SE37 execute the SAP Standard Function Module - UWL_DETECT_BWF_DELTA_JOB. If the Jobs are scheduled correctly it will return the counts as displayed below. This will validate the same. Note: If the count of NUM_TOTAL_JOBS is returned with value 0; this means that Job is not set up correctly and from Portal UWL Delta Pull Config won t work. You need to revisit the jobs set up and rectify the same to proceed. Step 5: Provider Systems Provider systems should reflect using Default System Alias e.g. DE1CLNT200 with Connector Type as WebFlowConnector If above is not the case: Not required in all scenarios - Please assess your specific case. Delete the existing ECC UWL WebflowConnector Provider System defined with a different ALIAS. Delete the Custom XMLs (Optional) Bounce the Portal Cluster. Note: Portal recycling is required in case of any ECC Config changes or RFC destination changes. Recreate the Provider Systems for ECC using the correct default ALIAS e.g. DE1CLNT200 after Portal bounce is completed. 2011 SAP AG 8
Step 6: Re-Register Provider Systems 1. Re-register the Provider Systems successfully e.g. DE1CLNT200 for ECC. 2. Set the Delta Pull values after successfully re-registering. Click on Edit and enter values as per the DELTA job frequency set up and save. Upon successful configuration message is displayed Delta Pull Channel Refresh Period (in Seconds) : VALUE Note: In this case the frequency of the DELTA Job ZHTRUWLECCDL is 3 mins (180 secs) 3. Upload the Custom XMLs against the systems (Optional). Note: This is typically after the Portal Configurator has performed customization activity on the XMLs as per customer requirement. In general Delta Pull configuration has no impact on the custom XMLs. References Special thanks to Beth Maben from SAP Support for giving good insight. This article gives you hints to solve the error: The backend of system XXXX is not configured for optimized delta pull. This article explaining the technique should be helpful to Portal Administrators/Configurators. 2011 SAP AG 9
Related Content Enabling Delta Pull Mechanism UWL FAQ UWL WIKI UWL_DETECT_BWF_DELTA_JOB returns Delta Pull is not configured UWL Destination Service configuration For more information, visit the Portal and Collaboration homepage 2011 SAP AG 10
Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document. 2011 SAP AG 11