UME Actions in the Portal

 UME Actions in the Portal

The user management engine (UME) uses UME actions to enforce authorizations. An action is a collection of Java permissions that define which activities a user can perform. UME actions can be assigned to UME roles or portal roles. If a role with a UME action is assigned  to a user, the user gains the authorizations provided by the action. The UME verifies that users have the appropriate UME actions assigned to them before granting them access to UME iViews and functions. Other applications can also define or check for actions.

The following table lists the UME actions assigned to portal roles by default.

Portal Roles with Default UME Actions

Portal Role	Assigned UME Actions
Delegated User Administrator	UME.Manage_Users UME.Manage_Role_Assignments
Every User Core Role	UME.Manage_My_Profile
Standard User Role	UME.Manage_My_Profile
Super Administrator	UME.AclSuperUser UME.Manage_All
System Admin	UME.System_Admin
User Administrator	UME.Manage_All

Some UME actions are defined specifically for the portal environment:

·  UME.AclSuperUser

·  UME.Manage_Role_Assignments

·  UME.Remote_Producer_Read_Access

·  UME.Remote_Producer_Write_Access

Standard UME Actions in Portal

Standard UME Actions

The following table lists the UME actions delivered with the user management engine (UME). These actions are defined in the file UMErole.xml.

 Note:

In the identity management application, you can search for actions by entering either the UME action ID, such as Logon_Help, or the name of the relevant service or application, such as com.sap.security.core.ume.service.

UME actions available by default in the SAP NetWeaver Application Server (AS) :

Actions of the User Management Engine

UME Action ID	Description
AclSuperUser	(Relevant for SAP NetWeaver Portal only) Provides Owner permissions on all objects in the Portal Content Catalog. You cannot remove this permission in the permission editor. This action is designed for super administrators. Be restrictive with this action, as it provides extensive permissions on portal content. Only assign it to the Super Administration role in the portal. Do not assign it to any other roles.
Batch_Admin	Provides permissions to use the import and export functions using identity management. To import users, groups, or roles, or to import user, group, or role assignments, you must also have the permissions to change the relevant principals. To export, you must have read permissions for the relevant principals.
Logon_Help	Provides permissions to access the logon help Web Dynpro application.
Manage_All	Provides permissions required by an overall user administrator. These include: Administration of users belonging to any company and the possibility of assigning users to companies Group management Role management User mapping Import and export of user data UME configuration Consistency check and repair tools Refresh the user cache Full access to the Service Provisioning Markup Language (SPML) interface To set up delegated user administration, overall user administrators must belong to a role to which the Manage_All action is assigned. In portal installations, any role that includes the Manage_All action automatically has Role Assigner permissions on all portal roles in the portal installation.
Manage_All_Companies	Provides permissions to manage users in all companies.
Manage_All_User_Passwords	Provides permissions required by a user to change the password of other users independent of company. This also enables the user to view all user profiles.
Manage_Groups	Provides permissions to view, add, modify, and delete groups. To assign users or roles to a group, you must have permission to modify users or roles.
Manage_My_Password	Provides non administrator users with permissions to change their own personal password in their user profile. The action Manage_My_Profile includes this action. You must also set the Allow Users to Change Their Own Password radio button in the security policy. For more information, see Configuring the Security Policy for User ID and Passwords.
Manage_My_Profile	Provides nonadministrator users with permissions to display and change their own personal user profile.
Manage_Role_Assignments	(Relevant for SAP NetWeaver Portal only) Provides permissions to assign portal roles, for which you have Role Assigner permissions, to users within your company. With this action, you can neither assign roles to groups, nor change the actions assigned to a role. This is a default role for delegated user administration for the portal.
Manage_Roles	(Not relevant for SAP NetWeaver Portal) Provides permissions to view, add, modify, and delete UME roles. To assign users or groups to a role, you must have permission to modify users or groups. Be careful to whom you assign this action. Users with this action can assign themselves the Administrator role, which gives them wide-ranging administrator rights on the AS Java.
Manage_User_Passwords	With this action a user can manage the passwords of users belonging to his or her company. The user with this action can view the user profiles of other users in his or her company and even lock and unlock their accounts. Use this action to create a delegated password administrator.
Manage_Users	Provides permissions to manage users belonging to the same company as the administrator (such as search, create, modify, delete, lock, unlock, reset password, approve new user requests, and deny new user requests). To assign groups or roles to a user, you must have permission to modify groups or roles.
Read_All	Enable a user to read user, group, and role profiles in all companies. It also provides the permissions to refresh the user cache of the AS Java.
Read_Basic	For internal use only.
Read_My_Profile	Provides nonadministrator users with permission to display their own personal user profile.
Remote_Producer_Read_Access	(Relevant for federated portal only) Provides permissions for remote users to read roles available on this producer portal.
Remote_Producer_Write_Access	(Relevant for federated portal only) Provides permissions for remote users to assign roles available on this producer portal. Does not include read-access.
Selfregister_User	Provides permissions for users to enter data in the self-registration forms.
Spml_Read_Action	With this action a user can conduct searches and read the schema of the SPML interface.
Spml_Write_Action	Provides full access to the SPML interface.
System_Admin	Provides a system administrator with permission to change the UME configurations in the Web Dynpro user administration application, and the permissions to run the consistency check and repair tool.
User_Viewer	Provides permissions for users to view the public profiles of other users belonging to their own company with the user viewer iView.
User_Viewer_All_Companies	Provides permissions for user to view the public profiles of all other users with the user viewer iView. Source: sap.help.com

Change Portal URL. 'http://hostname.domain.com:50000/irj/portal' to 'http://hostname.company.com'.

Change Portal URL

Purpose

This topic describes how to change the default portal URL to give users a more user friendly URL, e.g. to change from 'http://hostname.domain.com:50000/irj/portal' to 'http://hostname.company.com'.

Overview

To change the URL which users employ to access the portal, there are in general 3 approaches, which are discussed in turn below.

1. Change the instance configuration - for single-instance installations
2. Use a load balancer - for clustered installations
3. Use a reverse-proxy

1.  Change the instance configuration

1.1 Remove the Port from the URL:

For Enterprise Portal 7.0X: Update the AS Java Configuration

1. Open the Web AS Java Visual Administrator
2. Goto -> Cluster -> Dispatcher -> Services -> HTTP Provider
3. Choose Ports
4. Change the port number to 80 for HTTP and 443 for HTTPS (SSL) - as these are the default ports for these protocols, they don't need to be explicitly entered in the URL used to call the portal
5. Choose Update and save.

For Enterprise Portal 7.3X: Update the ICM Configuration

1. As 7.3 uses the ICM instead of the Java Dispatcher for accepting incoming HTTP requests, the port configuration now takes place in the instance profile via parameter icm/server_port_0
2. For example, to set the HTTP port to the HTTP default port 80 and the HTTPS port to the SSL default port 443 (so that the ports do not need to be explicitly stated in the URL), you would adjust the instance profile as follows:
   # Definition of the ports
   icm/server_port_0 = PROT=HTTP, PORT=80
   icm/server_port_1 = PROT=HTTPS, PORT=443

Note: On UNIX systems, you need root access to bind to ports less than 1024 - but you don't want to start your Application Server with the root user. You can achieve this by using the external program icmbnd, and updating the instance profile as follows:
# Use default ports
# icmbnd needs root permissions
# "chown root icmbnd" and "chmod 4755 icmbnd"
icm/server_port_0 = PROT=HTTP, PORT=80, EXTBIND=1
icm/server_port_1 = PROT=HTTPS, PORT=443, EXTBIND=1
exe/icmbnd = <path of executable>

1.2 Remove the irj/portal:

For Enterprise Portal 7.0X:

1. Goto Cluster-> Server-> Services-> HTTP provider
2. Enter /irj/portal in the start page text field
3. Choose the save properties button
4. Restart the instance.

For Enterprise Portal 7.3X:

1. In 7.3x, this is done via the NetWeaver Administrator: 'http://<host>:<port>/nwa'
2. Follow menu path: Configuration > Connectivity > HTTP Provider Configuration
3. Enter /irj/portal in the default start page property
4. Click save

Alternate approach for Enterprise Portal 7.3X:

1. You could also achieve this at the ICM level using a redirect rule like the following:
   icm/HTTP/redirect_0 = PREFIX=/,TO=/irj/portal,HOST=hostname.company.com

Note: Both of these approaches will result in a redirect response being issued to the browser, redirecting from 'http://hostname.company.com' to 'http://hostname.company.com/irj/portal', so users will still see /irj/portal in the adress bar - it just won't appear in the link provided to the users. If you want to avoid that it appears in the address bar, consider using a reverse proxy instead.

2. Use a Load Balancer

The above configurations take effect at the instance level. If you use a cluster, you need to use a load balancer in front of the portal, and you should perform any configuration on this component instead. You can use many types of software or hardware load balancer with the portal, the most common is probably the SAP Web Dispatcher, so the below example is for the Web Dispatcher. Configuration of the Web Dispatcher is similar to configuration of the ICM for the instance (since they are based on the same technology). So, to have the web dispatcher listen for HTTP requests on port 80, and redirect requests with no path to /irj/portal, you would use the following configuration:
icm/server_port_0 = PROT=HTTP,PORT=80,HOST=hostname.company.com
icm/HTTP/redirect_0 = PREFIX=/,TO=/irj/portal,HOST=hostname.company.com
Note: The comments above about using icmbnd for ports less than 1024 on UNIX systems still apply. It's also worth noting that you could use a Web Dispatcher even for a singe-instance system for exactly this use case: if you want to accept requests on port 80 on UNIX systems.

3. Use a Reverse Proxy

You can use a fully featured reverse proxy in addition to a load balancer, or the reverse proxy can also perform load balancing functions. There are several software solutions that can act as a reverse proxy. The most often used software is probably Apache. The general solution looks like this:
Browser <
-> Reverse Proxy <
-> Portal
The user connects to the URL 'http://reverseproxy.company.com', whereas the Reverse Proxy connects to the portal with 'http://hostname.company.com:50000/irj/portal'. This access is transparent for the user. If your reverse proxy is configured to perform URL rewriting, then the /irj/portal path can also remain invisible to the end user.

Related Content

Related Documents

SAP Help (Web Dispatcher):
SAP Help (Sample Profiles for the ICM on 7.30):
SDN Article on Apache Reverse Proxy

Blogs:

• The Reverse Proxy Series – Part 1: Introduction
• Setup SAP Web Dispatcher with URL Filter on SuSE Linux 9.0
• How to...Configure SAP Webdispatcher as a reverse proxy

Change of Branding image in Welcome page of portal

  In simple, search for the image file with the name "branding_image" in the usr folder. Replace that image file with your company logo file with the same name.

Restart the server which inturn will change the image of welcome page.

or else

You can just enter the location in the below parameters.
In config tool.
Go to:
-> Global configuration.
-> Server.
  -> Services
   -> UME Provider.
       -> ume.logon.branding_image
       -> ume.logon.branding_text

try to copy the image to :
/usr/sap/<SID>/JC00/j2ee/cluster/server0/apps/sap.com/com.sap.security.core.admin/servlet_jsp/logon/root/layout

Portal login page modification

Branding Image and text in Portal logon page

This document basically explains how to change the branding image/branding text which appears in the /irj portal logon page .

Inorder to decide the path from which these images are taken , please perform the the following steps

1. http://<hostname>:<port>/irj/portal

2.donot login

3.Right click the image in the logon page and check the properties , this will provide the information of where ther the image is taken from as well as pixel size

4. you should find some thing like this
Address : https://<hostname:port>/irj/portalapps/com.sap.portal.runtime.logon/layout/branding-image.jpg

 5.this information above it basically tell us, from where this image is called upon , so this image is called upon from
\usr\sap\<SID>\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\portalapps\com.sap.portal.runtime.logon\layout\

6.replace the sap image with customized image for all the server nodes , pixel size information can be obtained from looking in to the property as mentioned in step 3

7.usually if you replace bandimgimage it doesnt require a restart , but for branding text it requires a restart

Exporting and Importing Themes in SAP EP

You use the Transport Themes tool to import and export themes as compressed files.

Procedure

1. Go to System Administration >Transport >Transport Themes.
   
   
   Your custom themes are listed under Export Themes.
   

   
   
   
2. To export a theme, choose the theme to be exported and specify a target folder for the compressed file.
   
   
3. To import a theme:
   1. Specify the path to the theme that you want to import or choose Browse to select the compressed file of a theme.
   2. If you want the imported theme to overwrite existing themes, select Overwrite Existing Theme.
   3. Choose Import.
       
      You can also transport themes by including them in a standard portal transport package. For more information, see Transporting Portal Objects.
      
      

Change the image of Loading in Portal

1. Export the theme.
2. Open the saved file:

How to find number of logged in users on NW04s?

we can check logged users in AS JAVA using ..

Visual Administrator -> Server -> Services -> Security Provider -> Login Sessions.

U can view currently active server sessions at

System Administration -> Support -> Wed Dynpro Test Tools -> User Management.

Check all Users who have logged into portal - webdynpro appl

Check all Users who have logged into portal - webdynpro appl




Get Portal users from WebDynpro

//Get user Logon Id who has logged in the current session-I

To run this code successfully, we need to add security.api.jar file by using following setps
Right Click on project->Java Build Path>Add Variables>WD_Runtime>Extendsàcom.sap.security_2.0.0>lib->com.sap.security.api.jar







public void GetLogonID()

Unknown macro: {//@@begin GetLogonID()String LogonID;try{ /* create an user object from the current user */ IWDClientUser wdUser=WDClientUser.getCurrentUser(); IUser user=wdUser.getSAPUser(); if(user!=null){ IUserAccount acct=user.getUserAccounts()[0]; if(acct!=null) LogonID=acct.getLogonUid(); else LogonID="acct null"; }

else

Unknown macro: { LogonID="user null"; }

wdComponentAPI.getMessageManager().reportSuccess(user.getFirstName()+" "+user.getLastName());
wdComponentAPI.getMessageManager().reportSuccess(LogonID.toUpperCase());
}catch(Exception e)

Unknown macro: { e.printStackTrace(); } //@@end
}
//@@begin javadoc:GetCurrentUser()
/*Declaredmethod./
//@@end
*Get user who has logged in the current session-II{*}public void GetCurrentUser()

Unknown macro: {//@@begin GetCurrentUser()String LogonID;try{ // create an user object from the current user IWDClientUser wdUser=WDClientUser.getCurrentUser(); IUser user=wdUser.getSAPUser(); LogonID=user.getUniqueName(); wdComponentAPI.getMessageManager().reportSuccess(user.getFirstName()+" "+user.getLastName()); wdComponentAPI.getMessageManager().reportSuccess(LogonID.toUpperCase()); }

catch(Exception e)

//@@end
}
//@@begin javadoc:CheckAllUsers()



*Declaredmethod ./

//@@end


//Check all the users method to get current logged in users from the portalpublic void CheckAllUsers(){
//@@begin CheckAllUsers()
IWDClientUser currentUsers[]=WDClientUser.getClientUsers();
//Displaying the count of logged on users
wdComponentAPI.getMessageManager().reportSuccess("Number of logged on Users in the portal - "+(currentUsers.length-1));
for(int i=0;i<currentUsers.length;i++)

Unknown macro: {if(currentUsers[i]!=null){ // Displaying the logged on users; if(!currentUsers[i].getLastName().equals("Guest")){ String first= currentUsers[i].getFirstName(); wdComponentAPI.getMessageManager().reportSuccess("User - "+currentUsers[i].getFirstName()+" "+currentUsers[i].getLastName()); }

}
}



//@@end
}
//@@begin javadoc:LogOffUser()
/*Declaredmethod./
//@@end
Log off the userpublic void LogOffUser(){
 //@@begin LogOffUser()                   
WDClientUser.forceLogoffClientUser("http://koldxp-pigoswam:50000/irj/portal");
//@@end
}

Frequently used Tcodes in SAP

Frequently used Tcodes in SAP

Serial No	Transaction Code	Function
1	ABAPDOCU	Example Library
2	ABAPHELP	Keyword Documentation
3	AL03	Operating system Alert Monitor
4	AL05	Workload Alert Monitor
5	AL08	List of all Users Logged ON (about all Instances/Servers of the System)

FAQ s

FAQs on SAP Enterprise Portal - (Knowledge Management)

Q) How is SAP NetWeaver Knowledge Management integrated into the SAP Enterprise Portal?

Technically speaking, the SAP NetWeaver Knowledge Management (KM) services are installed by a separate choice in the installer, but then run on the same server(s) as the SAP Enterprise Portal (EP). KM relies on some services of SAP EP as e.g. the user management. Only the Search and Classification Engine (TREX) should run on a separate server.

From a user's and/or content manager's perspective, the KM functionalities are accessed through delivered standard iViews, the default search field in the portal header, etc. The user interfaces to KM are highly configurable and can thus be adjusted to almost any desired navigation strategy and/or corporate design.

Q) How much does SAP NetWeaver Knowledge Management cost?

SAP NetWeaver Knowledge Management is included in the SAP NetWeaver license and was previously included in the SAP Enterprise Portal license. Nevertheless, please consult your SAP sales contact to identify special cases such as e.g. external facing portals.

Q) Can SAP NetWeaver Knowledge Management integrate other systems?

SAP NetWeaver Knowledge Management has an open framework to allow access to additional document storage strategies. These "repositories" are connected into the framework by so called "repository managers". SAP delivers some of these "repository managers"; Of course the integration of 3rd party repositories is an option only and not a mandatory approach. SAP NetWeaver Knowledge Management does also provide its own storage solution.

Q) Which sources can Search and Classification (TREX) index and search?

Search and Classification (TREX) within SAP NetWeaver Knowledge Management can index and search any document that is connected into the repository framework (see above). Future developments will add business objects and additional repositories to the search scope.

Q) What is the difference between SAP NetWeaver Knowledge Management and the SAP Knowledge Warehouse (KW)?

The SAP KW is specialized in managing SAP-related training and documentation in an R/3 environment.

SAP NetWeaver Knowledge Management is specialized in collaboratively managing information and documents in disparate repositories within an organization via the SAP Enterprise Portal.

SAP EP External Facing Portal FAQ

Q: What is an external-facing portal?

A: An external-facing portal is an implementation of the SAP NetWeaver Portal as a public Web
site.
An external-facing portal is open to the internet, providing content to anonymous users, internal
employees and business partners and enabling users to self-register in order to access additional
content and to personalize the portal.
An external-facing portal uses features of the portal that provide Web-like behavior (for example,
use of the browser navigation buttons) and reduce the amount of resources required to view
portal pages.
Although not always appropriate for certain resource-rich applications, the external-facing portal
can boost ROI by using the same platform for the company's internet and intranet
implementations.

Q: What version of NetWeaver do I need to implement an external-facing portal?
A: SAP NetWeaver 2004 SPS 14 or higher, or SAP NetWeaver 7.0 SPS 06 or higher.

Change the ICON of SAP EP Portal

Change the ICON of SAP EP Portal

After Changing the SAP Title every one tries to modify the SAP ICon this can be done by the following way.

Step by Step How to Change Title of the SAP Enterprise Portal

Step by Step How to Change


In this blog we will cover step by step how to change the title of the portal. Below you can find all the needed steps with screenshots.

1) First thing you need to do is logon to your portal with your user. Your user should have a super_admin role. If not you will not be able to implement following steps.

2) After logging to your portal you should go to the System Administration tab.

How to Change html header in Portal 7.3

Change Portal title name (where is "portal.html.head.title" in 7.3)

Change text of Browser Tab

Step by Step How to Change Title of  the SAP Enterprise Portal 

 

                                   In EP 7.0 :

PCD Path of

Portal Personalization:

pcd:portal_content/com.sap.pct/every_user/general/worksets/com.sap.portal.portal_personalization PCD> content provided bysap>end user content>standard portal users> Portal Personalization

SAP Enterprise Portal – Configuration to make Custom Page as Default Logon Page

SAP Portal Log on page customization is an essential requirement to align SAP Portal’s appearance to enterprise branding. It becomes urgent when SAP Portal is exposed to outer world for business transactions. Customized Portal page provide uniform end user experience while providing secured contents using authentications.
To achieve Portal Log on Page customization, it involves SAP Portal Developer and Basis support for development and configuration activities respectively. This post elaborates more on configuration part (after development and deployment) which involves Config tool and thus require involvement of Basis support. This post will enable Portal developer to do these configurations by their own if they have rights to access these tools.

Platform
Configurations mentioned in this post are applicable for SAP NW 7.0 (2004s) as .par files are used to customize portal branding. SAP NW CE (Composition Environment) uses .war files which makes .par files obsolete. But still there is a provision to import .par files to CE based platforms and reusing old investments.

Prerequisites
It is assumed that you have already customized standard .par file under your custom name. e.g. com.<company-name>.logon.par. This custom project must be deployed to portal system.
J2EE server should be stopped to make configuration changes.

Configuration
After deploying .par file to your Portal system, you need to change default authentication scheme for portal. This is required because portal is still pointing to default authentication scheme. This approach will preserve original configurations and allow you to modify these configurations as per requirement. You can revert back to default settings at any point of time, which follows best practice and is very effective without fearing any loss.
Following are the steps to perform post development customization -
Go to Config tool using following path \usr\sap\<SID>\JC00\j2ee\configtool. Click on change mode button.

To Reset Administrator Password through Config Tool

How to Reset Administrator Password through Config Tool
How to reset J2EE_ADMIN password.
How to Activate SAP* user in SAP portal/ config tool.



It may sometimes happen that a user enters the wrong password a number of times (by default, 3) and if that user is the administrator, then the administrator user is locked. This prevents all sorts of things happening. To unlock the administrator, use the following process
You need to use the Config Tool and the process is:
1) Go to the Server Installed path i.e. usr\sap\<systemid>\<system instance>\J2EE\configtool\
2) Choose configtool.bat and start it.

Portal login page modification

Modifying Portal Initial logon page 

This procedure applies for EP 6.0 SP3 and higher.


The logon user interface (UI) of SAP Enterprise Portal is delivered in a portal archive (PAR file) named com.sap.portal.runtime.logon.par which contains all the logon UI's code and resources.

In a deployed portal, the PAR file is located at

<J2EE_Engine_Instance>\j2ee\cluster\server<X>\apps\sap.com\irj\servlet_jsp\irj\root\WEBINF\deployment\pcd.

During initial portal deployment, it is renamed to com.sap.portal.runtime.logon.par.bak.
To customize the logon UI, we recommend the following procedure:

Modify the PAR file containing the logon UIs

1. Make a copy of com.sap.portal.runtime.logon.par.bak and rename it. In this example, it is renamed to my.new.logon.par.

How to check the EHP of Portal and ECC.

How to check the EHP of Portal and ECC.

For ECC

Login to SAP GUI.

go to System> status> component information (click on help icon just below Component version)

check for SAP_APPL .

if it is,
604 then  ECC 6 with Ehp4.
605 then  ECC 6 with Ehp5.

606 then  ECC 6 with Eh6.

Nice one.

Show Multiple UWL s in SAP Portal

Business Scenario:

Different business users ( Example : HR / SRM ) want to see their work items/tasks in portal under different roles with different navigation's if possible.
Version : EP7.01 SP8

Assumptions :

 Business users already using the UWL. UWL Configuration already done with the back end systems.

Technical Details:

Portal Transport Package

How to create a transport package.
How to add objects to transport package.
How to export it and download it.
How to import it to the other environment like Development/Quality/Production.
How to transport the portal objects from one environment to other. 

Exporting the Transport Package.

Go to Portal>system Administration>Transport>Export

How to Upload Photo in to content server.

How to Upload Photo in to content server.

If Content server configuration is done then.

Go to OAAD Tcode and click on Store and Assign button.

Logon Page Configuration EP

How to change the logon page of EP.

Simple way to change the branding image and logo in logon page of SAP EP.

Simple way is:

1. Download the par file com.sap.portal.runtime.logon.par
2. Go to the layout folder in the par file to find the branding image.
3. Replace it with the new image.
4. Upload the par file.

Creating Custom Theme, Desktop, Framework Page and assigning it to User/group.

The following question's will be answered in the post.

How to create and  assign a desktop to a user/group.

How to create a custom desktop.

How to create a custom theme.

How to create a new desktop and  add framework page and theme to it.

How to change the portal look and feel.

To start, lets talk about Portal Desktop.

 

Portal desktop is a collection of portal themes and default framework page.

Portal desktop can be assigned to user/group by rule collection.

Rule collection is a collection of if then expressions for assigning portal desktop to users/ groups.

Portal theme:

Sys Admin -> portal display -> select one theme -> change some styles (background colors, font, logo, welcome area branding image etc) ->save as -> provide theme name and id -> save ok.

Theme will be store din .css (cascading style sheet) format.

Single sign on setup for AS Java NW 7.3 using Logon Ticket mechanism

Single sign on setup for AS Java NW 7.3 using Logon Ticket mechanism

The SSO concept based on Ticket is similar to the previous versions of NW.

Only difference with NW 7.3 is the UI and things which can be achieved using the NWA.

Below is the step by step procedure to configure the Single Sign-on in NW 7.3.

1) First thing we need to do is Export the certificate from EP and  Import  it in Backend.
2) Secondly to add the Backend system as trusted system in EP JAVA NW 7.3.

UWL Configuration SAP EP 7.3

UWL Configuration SAP EP 7.3

Universal Worklist with SAP NetWeaver Portal is a centralized access point for business workflow items across heterogeneous systems. SAP UWL enables Portal Users to manage workflow items via centralized UWL inbox.

SAP Universal Worklist being a part of standard SAP Enterprise Portal installation requires no prerequisites. UWL establish connection to various provider systems using comprehensive configuration. Using provider system specific connectors, it fetches tasks using pull mechanism to feed inbox, serving portal users their work-list items at a centralized workplace.


Configuring UWL for Guided Procedure on Local CE


Portal users can get access to Universal Worklist inbox by assigning ‘Every User Core Role’.
Guided procedure is prominent workflow provider in SAP CE (Composition Environment). To obtain Guided Procedure work items in UWL, a simple configuration is required.

Configuration steps:

Go to Content Administration -> Portal Content -> Content Provided by SAP -> End User Content -> Standard Portal Users -> iViews -> com.sap.netweaver.bc.uwl.iviews -> Universal Worklist

PCD Path:

pcd:portal_content/com.sap.pct/every_user/general/iViews/com.sap.netweaver.bc.uwl.iviews/com.sap.netweaver.bc.uwl.uwl_iview 

Assign this standard UWL IView to role.

Now there will not be any Item Under tasks Tab. (cause we have not configured the uwl yet)

After Finding the IView.

How to hide alerts, notifications, tracking, sapoffice mails tabs in UWL.

If  we want to hide these tabs from UWL,

The easiest way is:

Open the properties of uwl iview in the portal content.

There is a property called "UWL Navigation Property / Style".

By default it is selected as "Tab".

You can change it to "None".

Before doing this change make sure you had Selected the "Tasks" tab from the UWL.
(you can do this by previewing the iview and selecting task tab in it)


After saving this property, only the Tasks tab will be shown in the UWL.

In this way we are actually hiding the tabs area in the uwl.