Removing Actions From the UWL Display

How to Remove create task button from UWL.
How to Remove Alerts Configuration ,Claim, Complete, Complete Task, Create Ad Hoc Request, Create, Task, Decline, Delete, Edit, Follow-up, Forward, Forward, Manage Attachments, Open Task, Personalize View, Revoke Claim, Submit Memo, View Detail in SAP Gui from UWL.

     

There are a few ways to remove actions.  

You can customize the Views and ItemType (which can remove the actions from all UWL pages, Collaboration, My Task, and so on)

You can modify the iView and add the name of the actions under the Action to exclude from the UWL property. 

Suppose you do not want the Personalize View function on the UWL view. You can remove it by adding personalize to the iView property List of UWL Actions to Exclude.

Regarding Create Task Button:

the "Create Task" button in main UWL screen is not hidden.

This note may be of use to you as well: 1622327.
There was an issue with this in 730/731 systems and there is a correction delivered via patch to fix it.  Please ensure that you are on the correct level of the UWLJWF based on the note.  This explains why we are unable to hide and you were not....probably on a different version where the code wasn't affected.

For removing all other tabs than Tasks enter the following property "none" as shown when the UWL is in Preview mode with tasks tab selected.

 See table below for some of the common action names.

Action Display Text	Action Name
Alerts Configuration	AlertConfiguration
Claim	reserve
Complete	acknowledge
Complete Task	confirm
Create Ad Hoc Request	uwlTaskWizard
Create Task	defaultGlobalWizard
Decline	decline
Delete	deleteItem
Edit	editItem
Follow-up	followup
Forward	forward
Forward	forwardUsers *
Manage Attachments	manageAttachments
Open Task	launchSAPAction
Personalize View	personalize
Revoke Claim	reserve
Submit Memo	addmemo
View Detail in SAP Gui	launchSAPDetails

HowTo Find Software Component Patch Levels In SAP EP

So, you need to know the patch level of a Portal Software Component

Go to NWA 

http/s://<host name>:<port number >/nwa

Configuration > Infrastructure > System Information.

 OR

Go to Start Page.

http/s://<host name>:<port number >

following screen will be displayed.
select system information.

Select Components Info under System Information:

Then following screen will be displayed

The above picture shows the breakdown of the Version, Support Stack Level and Patch Level.

NWDS it's Installing and Configuring

1. Download and install JDK 1.6 from here:


http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html

2. Copy the file nwds-extsoa-7.3-SP00-PAT0000-win32.zip from:

<your download location>\51039309\DATA_UNITS\JAVA_IDE
\distros\com.sap.netweaver.developerstudio.distribution.complete.extsoa \8.30.0.101020102100
to a convenient folder.

3. Extract the content and you will have a folder with name “eclipse”.

4. Launch the Netweaver Developer Studio from folder eclipse, you may want to create a shortcut on the Desktop.

5. If you haven’t maintained JAVA_HOME property or if it’s pointing to some other java version, eclipse will complain about it. In the dialog window locate the JDK 1.6 installation. Path to JDK 1.6  should be something like

C:\Program Files\Java\jdk1.6.0_25\bin

6. Restart the NWDS after this and select a suitable workspace.

7. Set the run time engine in NWDS, by going through the menu path:

Window->Preferences->SAP AS JAVA

Hide/Remove Detailed Navigation in Classic Framework Page.

How to hide the Detailed Navigation from portal.



will be updated soon........

Classic Framework Page

Classic Framework Page:

The Classic Framework Page provides the navigational and structural components required to navigate and operate the portal.

You can modify the it or create your own framework pages to meet the requirements of your organization.

Location in PCD: 

Portal Content > Portal Users > Standard Portal Users > Classic Framework Page.

(pcd:portal_content/every_user/general/frameworkpage).

Note:

Do not modify the delta link source object of the above-mentioned framework page, which is located in a subfolder under the Content Provided by SAP folder.

    Classic Framework Page (com.sap.portal.frameworkpage)

This is a page that contains the following iViews and pages:

      1)   iView: Masthead iView

      2)   iView: Tool Area (This iView is assigned to the Classic Framework Page, but is by default in a hidden state. To display it, change the Visible property of this iView by editing it in the Classic Framework Page.)

Changing Logon Page on Netweaver 7.3

As you know Netweaver 7.3 is released on 30 May 2011.

First get war file of logon application.

Its' location is: <drive>:\\usr\\sap\\<SID>\\J00\\j2ee\\cluster\\apps\\sap.com\\com.sap.security.core.logon\\servlet_jsp\\logon_ui_resources\\tc~sec~ume~logon~ui.war

(In 7.3 version there is no more PAR files!)

 

UME Configuration (Identity Management)

In this post lets discuss about UME Configuration of SAP EP Portal

SAP Portal cache's and How to clear .

The SAP Portal has several caches to speed up the portal experience and to minimize the impact of the portal on the Server (load time, database, PCD lookups, etc.). This has many benefits, but it complicates debugging for developers and support staff. There, you don`t want to see cached results, you need to get the actual changes.

End-user

When the user is accessing the portal for the 1st time, the browser loads all necessary files and caches them locally. 1st access with no cache:

Important URLs, Transaction Codes, ABAP Reports in Process Integration 7.1

Hi, I would like to share important URLs, Transaction Codes and ABAP Reports that are used in Process Integration PI 7.1

I) Process Integration PI 7.1 URLs

A	Design Time Tools URLs
1	http://<host>:5<sys#>00/dir/start/index.jsp	Process Integration PI 7.1 tools
2	http://<host>:5<sys#>00/sld/index.html	System Landscape Directory (SLD)
3	http://<host>:5<sys#>00/rep/start/repository.jnlp	Enterprise Services Repository (ESR)
4	http://<host>:5<sys#>00/dir/start/directory.jnlp	Integration Directory(ID)
5	http://<host>:5<sys#>00/sr	Service Registry(SR)

B	Runtime Tools URLs
1	http://<host>:5<sys#>00/rwb	Runtime Workbench(RWB)

Leave Request UWL Trouble shooting

Leave Request Approval screen is popping with blank header.
Remove task TS12300097 from UWL.
Calling WebDynpro ABAP application as work item through workflow.
Error: Opening Leave Request from Manager UWL.

The Solution is :


1) First Configure the UWL as in the following LINK.

UWL Configuration SAP EP 7.3


2) Check the following System aliases whether created.
       a) SAP_ERP_HumanResources
       b) SAP_WebDynpro_XSS
       c) SAP_ECC_HumanResources

3) Check the Webdynpro launch System alias WAS property.


4) Check whether proper roles are assigned in backend.


5) Check whether proper authorizations assigned to enduser for PCD objects.

6) Please check the note 1618269 and 1600953.

How to Show Role ID and Workset ID in Editor

New functionality to configure Role and Workset editors released with NW Portal 7.3 SP 9.

By default, objects in the Role Editor and the Workset Editor are displayed using the object name. 

You can also configure the editors to display the atomic ID of each object, or to display a combination of both the object name and the object ID.

Next views (role example) are the same for role and workset editors: 

Role by Title

Role by ID

SAP System startup Problems

One of the most sought after topic for a BASIS guy is to troubleshoot startup problems. Below is the list of some basic startup problems with solution. I am sure you will be find it very useful.

SAP System startup Problems:

Two places you need to check: Event Viewer (Application and System logs) and the SAP Management Console (MMC). Event Viewer can provide useful information and it may help you pinpoint where the problem resides. The SAP MMC gives you the ability to visually see the system status (green, yellow or red lights), view the work processes status and view the developer traces, which are stored in the "work" directory. Example: /usr/sap/TST/DVEBMGS00/work.

For a central SAP instance to start successfully, both the message server and the dispatcher need to start. If one of them or both fail to start, users cannot log in to the system. The following scenarios will illustrate possible causes of why an SAP instance might not start and the reason of the message:

"DISPATCHER EMERGENCY SHUTDOWN ".

Developer Traces:
dev_disp Dispatcher developer trace
dev_ms Message Server developer trace
dev_wp0 Work process 0 developer trace

The "services" file, which contains TCP and UDP services and their respective port numbers. This plain-text configuration file is located under winnt/system32/drivers/etc.Windows Task Manager (TASKMGR.exe), Event Viewer (EVENTVWR.exe).

Dispatcher Monitor (DPMON.exe), which is located under /usr/sap//sys/exe/run. Database logs.

Exit codes in JAVA stack and it's significance

Here are the exit codes in JAVA and it's reason. Also for some of the return code you can refer to the snote mentioned with the exit code:

Common exit codes

0    =Normal exit.
11  =Cannot initialize xml parser (Service Manager) or error reading properties (likeyinst tool).
666=Out of memory.

Engine exit codes

1        =Forced shutdown.
888    =Engine shutdown cannot finish for “haltTimeout” the VM is halted with this exit code.
999    =Error occurs during AS Java shutdown.
-1501 =Framework error.
-333   =Missed broadcast due to network problems (MSLib).
333    =Missed broadcast due to network problems (MSLib).
-334  =Error getting confirmation during reconnectng. (MSLib).
334   =Error getting confirmation during reconnecting. (MSLib).
-335  =Timeout reconnecting (MSLib).
335   =Timeout reconnecting (MSLib).

The Analyse Option for Portal Content

Well, we have always liked any software which tells us what is to be done as best practice.

It was fun and we could also tell our bosses, see this is the recommendation of the Tool and we have to implement.

Now when it comes to Portal, there is nice option called Analyse.

Log in to the Portal and Hit the Content Administration ==> Portal Content.

Select the Folder in which you need to analyse.

Right Click on the Folder and select Analyse.

AS JAVA Troubleshooting : Bootstrap Stops Due to Configuration Problems

Symptom:

AS Java bootstrap fails to synchronize the system’s files and stops with one of the following exit codes: 501, 502, 510, 545.

Scenario Type: Error analysis

SAP NetWeaver Component: Application Server Java (AS Java)

Analysis:

The bootstrap can fail to synchronize the engine's files due to problems with the configuration of the module.

Solution:

1. Find a detailed description of the problem in the bootstrap log files, which are located in /usr/sap/<SID>/JC<XX>/work/ folder. The log files are:

○       dev_bootstrap* - logs from the Java Startup and Control Framework that shows the parameters with which the bootstrap was started.

○       log_bootstrap* - logs from the execution of the bootstrap that show the execution flow from the last session and the possible errors.

○       jvm_bootstrap* - logs from the JVM output for the bootstrap process that show possible JVM problems during the bootstrap execution.
      

2. Proceed depending on the particular exit code.

Difference between Copy and Delta Link

Both Copy and Delta Link has same functionality i.e.to make a duplicate of an iView and Page.

Copy and Paste:

1) Changes to the source iView do not affect the target iView. Both source and target iViews are independent siblings, having a delta link relationship to the same parent iView.

2) When we copy an iView, the iview id will remain same i.e.the source iview id will be same as target iview id.

Delta Link:

1) Changes to the source iView are updated to the target iView. Changes made to the target iView have no effect on the source object. Once a property of the target iView has been overwritten, changes to the same property of the source iView are no longer updated.

2) When we Delta Link an iview, the iview id will change i.e. the source iview id will change.


For more information please check the below links:

http://help.sap.com/saphelp_nw73/helpdata/en/04/65543ef544489c822597a0e6ff2abe/content.htm

http://help.sap.com/saphelp_nw74/helpdata/en/49/7a5a678cda11aae10000000a421937/frameset.htm

Troubleshooting Universal Worklist Configuration

Overview:

This post shows you a briefly of this tool called “Universal Worklist Configuration Troubleshooting”. 
 This feature allows the user to retrieve some information about an UWL configuration.
 The document has the purpose of introducing the following features of this tool:

• Checking which XML configurations are available for such user, role or group.
• Conflicting ItemTypes.
• Looking for ItemTypes and locating the Configurations (XMLs) where they are defined.

Prerequisites:

• SAP Netweaver Enterprise Portal
• The UWL must be correctly configured based on the steps of the help link below:
  http://help.sap.com/saphelp_nw73/helpdata/en/4b/03fab265322590e10000000a42189b/content.htm

Troubleshoot locking sessions in EP 7.3

Overview :

If any sessions running for long time , it is possible to observe locked sessions and kill them manually if needed . Without kiling them , it is also possible to generate thread dump or heal dump based on the situation to find root cause of the issue.
Version : EP7.3

Technical Details :

If any sessions locked after running for long time or If any lock exceptions generated , log-in to NWA using http://host:port/nwa and navigate to Troubleshooting -> Java  and choose Locks.

Downloading and deploy ESS and MSS

ESS and MSS - What to deploy ?
To deploy ESS and MSS on Portal 7.0 and ERP 2005 (also called ERP 6.0 or ECC 6.0), you totally need 6 files.

Download
The Business Packages for ESS/MSS are no more downloadable from SDN Content Portfolio. You need a SMP Login id to download the Business Packages and application components from Service Marketplace. Go to the address: http://service.sap.com/swdc

1. BP for ESS :  Click on Download -> Support Packages and Patches -> Entry by Application Group -> SAP Application Components -> SAP ERP -> SAP ERP 6.0 -> Entry by Component -> Portal Content -> BP ERP05 ESS 1.0 -> Click it and select #OS independent --> Select the SCA file depending on your SP Level

2. BP for MSS : Click on Download -> Support Packages and Patches -> Entry by Application Group -> SAP Application Components -> SAP ERP -> SAP ERP 6.0 -> Entry by Component -> Portal Content -> BP ERP05 MSS 1.0 -> Click it and select #OS independent -> Select the SCA file depending on your SP Level

What is IRJ

The SAP NetWeaver Portal is a J2EE application that is designed to handle HTTP requests for portal components. A portal component is a Java class written and packaged specifically to run in the portal. The portal application is deployed under the URL /irj. Therefore, IRJ is the SAP Enterprise Portal running under SAP NetWeaver Java Application Server.

 IRJ --> iView Runtime Java

Unblock UWL attachements

By default UWL will not allow to attach or view any attachments to work items in the UWL inbox
i.e. User will not be able to view any attachments for Leave Request /Purchase Order and Purchase Requisition.

To make the user view the attached documents we need to make changes to a property of UWL iview.
Open the UWL iview and check for the property "List of Preview sections to hide" and make sure the column is empty so that it will not block any of the sections mentioned.

check the attachment for clear understanding.

Portal System Object Properties SAP System with Load Balancing Template

How to create a System Object with SAP System with Load Balancing Template
 

Purpose:

This document will outline where to obtain each parameter for the Connector definition in the portal system object. This document refers to the system object of type 'SAP system with load balancing'. This is the most common system template used for portal connectivity to the backend.
Note: While some connector properties such as SID and Client are relevant for all types of integration with the backend, the Connector Test for Connectors is only relevant for JCO/RFC connections. This test is not relevant for application integration scenarios - i.e. integration of BW Reports, BSPs, IACs, Transactions using SAP GUI for Windows or SAP GUI for HTML, WebDynpro for Java or WebDynpro for ABAP.

Overview:

To integrate backend content into the Enterprise Portal, a System Object needs to be created in the Portal System Landscape. The connector properties of the system object, enables connection via RFC/JCO calls to the backend system. This connection type is primarily used in connecting the UWL to a workflow system. It is also used to connect the Portal to non-SAP systems.

How to change SAP enterprise portal runtime mode

Purpose 

The aim of this wiki is to facilitate the changing of the SAP enterprise portal runtime mode. Depending on the usage of the portal, the server administrator makes a call regarding this parameter and introduces a added level of security. This steps for all relevant SAP netweaver releases are depicted.

Overview

As mentioned in " Configuring the Portal Runtime ", the property "portal.runtime.security.mode" determines the access behaviour of the portal. For example in highly critical servers, the parameter  "portal.runtime.security.mode" must be set to "production", so that this introduces a limitation that the portal components do not start directly. Other possible values as the help link mentions, are "development" or "test". In this particular wiki, the mode is being changed from "development" to "production".

Settings on SAP release 6.40 and 700

Portal Security SSO

Portal Security:

SAP Enterprise portal offers a single point of access to all applications, information, and services needed to accomplish their daily tasks. Links to back-end and legacy applications, self-service applications, company intranet services, and Internet services are all readily available in the user's portal. Because the borders between company intranets and the Internet are blurring, comprehensive security is vital to protect the company's business.

•  Portal User Administartion and authentication
•  Authorizations

          Authorizations define which objects users can access and which actions they can perform.
            The portal has an authorization concept that is implemented using permissions, security zones, and the AuthRequirement property.
             In the portal, roles are only indirectly linked to authorization. Portal roles group together the portal content required by users with a certain role in the company. In addition, the role structure defines the navigation structure that a user sees in the portal. Users and groups assigned to a role inherit the permissions of the role. By default this is end user permission.

•  Network and communication security
•  Data Storage Security
•  Operating System security

SSO Mechanism:

SAP Transaction iView - Transfering code page parameters to start SAP GUI

Applies to:

SAP EHP2 FOR SAP NETWEAVER 7.0 SP10
SAP NETWEAVER 7.3 SP5

In new EP versions there is a parameter on the SAP Transaction iView that allows you to concatenate these values named:
"Additional parameters to start SAP GUI". It's a property on the iView under the category "Content - Transaction"
To add more than one parameter you will need to separate the values with " /" (space and then slash).
For example: UPDOWNLOAD_CP=8000 /SOMETHING_ELSE=2000.

Great, What should I do if I've got an older portal version?

About Knowledge Management Administration

Knowledge Management and Collaboration:

Overview of KM:

Knowledge Mangement Consists of Contenet Management ,Collaboration and TREX.
Collaboration:

1.Asynchronous Collaboration
2.synchronous Collaboration
3.Partners


TREX:

About SSO What it is and types

What is single sign on (SSO)

Once a user has authenticated to the SAP EP, he doesn't need to enter his credentials again to access all the systems and backends (SAP and Non-SAP, ESS, MSS and services) integrated into the EP. SSO can be achieved in 3 ways:

JSESSIONID: The JSESSIONID cookie is used for achieving SSO on the Server Node.

User Mapping: The user or administrator assign for a specific backend system the userid and password. These settings will be used to achieve SSO to the specified backend. If the user is using a different userid for a backend, this is the prefered solution to achieve SSO.

SAP Logon Ticket: This is a session cookie named MYSAPSSO2 stored in the browser cache and is used to achive SSO to the backends, using the same userid for every backend system.
When talking about SSO, normally the SAP Logon Ticket is meant.

What is the SAP Logon Ticket?

SAP Logon Ticket (token) is a session cookie, stored inside the browsers cache. It get's permanently deleted from the cache after the user logs out or the token is expired. The Logon Ticket contains:

• Highest Authentication Scheme
• Validity
• Issuing System
• Digital Signature
• One Mapped ABAP User ID
• User ID

It doesn't contain the password.

TOP SAP Notes Every Web Dynpro Java Developer Must Know

http://scn.sap.com/people/bertram.ganz/blog/2007/01/08/the-top-12-hottest-sap-notes-every-web-dynpro-java-developer-must-know
All listed SAP Notes are valid for NW04 and NW04s.