Backdrop: Errors present us (user bases) with a wide range of functional issues which can pose threats in terms of loss of functionality, operational performance, application setups and everyday work processes.
While operating through a NW (Netweaver) Java Application Server environment error exceptions can occur on occasion for a whole hos of different reasons and pinpointing the root source of such occurrences is the key to their subsequent resolution and future prevention.
Tracing: If you have experience with the Enterprise Portal and have encountered an issue in the past you will most likely be familiar with being requested to gather, obtain and collect trace info (Information) for a Knowledge Management (KM) WebDAV or a Portal Drive Scenario.
Tracing is not restricted only to KM, WebDAV or Portal Drive.
Tracing can be used across the entire Portal to view underlying system operations and error exceptions
KM:Through the KM functional unit, SAP NetWeaver provides a central, role-specific point of entry to unstructured information from various data sources.
WebDav:Generally, access to resources (documents, folders, and links) in Content Management is performed by a WebDAV servlet.
Portal Drive: used in the assignment of KM folders to Windows drive letters
In order to troubleshoot issues accessing KM Content via WebDAV it is necessary to gather debug tracing on the engine as well as getting a HTTP trace of the scenario involved. This will show the requests and responses that are sent to the WebDAV server in order to determine where the issue occurs. You can gather both traces simultaneously. It is important that this additional tracing is only carried out when you are reproducing the issue to avoid any performance problems.
If a location doesn't already exist you need to add a new controller by selecting 'New' at the bottom of the screen
Type in the name of the new controller, e.g. com.sapportals.wcm.protocol.webdav.server.WDGetHandler
After you have added the above locations with severity 'All', save your changes making sure you apply them to the relevant server(s)
Set the severity of WDServlet to 'All'
Reproduce the issue accessing a resource via WebDAV or Portal Drive
Attach the resulting defaultTrace.X.trc file to your customer Incident which can be found at \usr\sap\<SID>\<instance_name>\j2ee\cluster\server\log
Remember to reset the trace locations back to their original severity in order to avoid any performance issues
HTTP Trace
Clear the cache from your web browser
Open the Visual Administrator tool
Navigate to the HTTP Provider of the Dispatcher opening the Properties tab
Set the HttpTrace property to 'enable'
Set the HttpTraceTime property to 'true'
Reproduce the issue accessing a resource via WebDAV or Portal Drive
When you have finished you should disable the HTTP tracing again, i.e. set the HttpTrace property to 'disable' and set the HttpTraceTime property to 'false' .
Attach the resulting req-resp.trc file to your customer Incident which can be found at \usr\sap\<SID>\<instance_name>\j2ee\cluster\dispatcher\log\services\http\req-resp.trc
It is important when reproducing the issue that you take note of the KM resource that is being accessed as well as the time you reproduced the issue, you should include this information in your customer Incident.
I have found a lot of discussions related to this subject, but could not find any which has been answered and where the solution has been shared.
The issue is very simple, I have some ABAP WebDynpro iView in my Portal, and for alle these iViews I want to use the NW Portal theme sap_bluecrystal. Or if this theme could be the standard for whole Portal will also be fine.
I have tried different things both in the Content administration and System administration in the NW Portal, but have not succed yet.
As a work around I've created one iview as a URL link, where i give the direct link to the WebDynpro eg.
Backdrop: When running a KM (Knowledge Management) Setup alongside the EP (Enterprise Portal) environment you find yourself being unable to access KM Resources when using anonymous access due to error references e.g. 404/403 Image may be NSFW. Clik here to view.
What functionality is affected?
It is not possible to access a Knowledge Management resource using a link from an email notification.
Anonymous Access - What is it?
Put simply anonymous access is a mechanism that permits and allows User Bases to access content without the need to authenticate (via the standard login process) via the Enterprise Portal.
Click on a link to a KM resource sent via a notification email
Do you encounter any error exceptions here preventing you from gaining access to a resource?
You might be encountering a "Error 404 Resource not available" or "access forbidden(403)".
What could be causing this error?
Firstly its imperative to ensure that the resource itself (trying to be accessed) is maintained in a consistent state i.e. it exists.
Secondly if you have anonymous access configured this means users can only access resources via links for which anonymous users have read permissions.
Rule Out Possible Root Causes
If you have experience with the Enterprise Portal and have encountered an issue in the past you will most likely be familiar with being requested to gather, obtain and collect trace info (Information) for a Knowledge Management (KM) WebDAV or a Portal Drive Scenario.
In order to troubleshoot issues accessing KM Content it might necessary to gather debug tracing on the engine as well as getting a HTTP trace of the scenario involved. This will show the requests and responses that are sent to the resource and can help you determine to determine why the issue occurs.
Log information pertaining to Knowledge Management is stored by the system in the defaultTrace.trc file.
This file is stored in the .../j2ee/cluster/server<n>/log directory.
Limitations with Anonymous Access
Once you have configured the KM prerequisites you need to then create a role for your anonymous users.
You can then assign iViews to this role to display your anonymous content to your end users.
If you still encounter the "Error 404 Resource not available" or "access forbidden(403)" we need to remember that anonymous access does have limitations.
Users can still use their UWL (Universal Worklist) inbox to view notifications or access resources for which notifications have been created
If you wish to provide users with a direct link to a resource you can also manually send a link to it using a different servlet path e.g.
When including it into a portal desktop this does not result in any visible change.
What else:
The Import of a 7.40 TE based theme only imported half the attributes (and of course were not reflected in "run preview" or when activated via portal desktop)
Changes of colors resulted in spacing errors (of course only in the inplace preview)
Images are missing (in the inplace previews)
...
This looks so broken that I cannot imagine I am the first one to experience this. I do not know where to start with opening incidents...
I am not able to find any notes relating to the main error at EP-PIN-TOL-UTD.
So back to my question:
Has somebody already managed to build and apply a custom theme using 7.50 SP2? If yes, which SP/PL?
I am new to Biller Direct,we have a requirement where i need to activate and deactivate the link to open pdf or to open an enquiry on click under Action column.
Right now i need to activate it as i see a blank column under action
Attached is the screen shot of the same. Also if possible please also share the configuration guide for biller direct.
Description: When you create a customized theme, sometimes it gives an issue involving in checkboxes disappearing. The checkboxes start disappearing on mouse(cursor)over on them and appears on mouse down. To resolve this issue follow the steps provided in the solution.
Download the theme for System Administration ----> Transport ----> Transport Themes .Click on theme and save.
Extract the <themename>.zip file which is saved on your local machine. It should have the following contents in it.
Now traverse to ur---->common---->checkbox
Delete the two images(cb_chk_hv and cb_hv).
Now, open the metadata file.(this file will be available in your extracted theme folder in the starting itself).
Change the id and name in the metadata file.
save the changes and add the folder contents to a zip file.
select all the contents in the theme folder and then right click to add to zip.
Note: while creating a zip do not directly create a zip of the theme folder. Selelct all the content in the theme folder and then right click to add to zip and follows the same way while creating a zip for ur folder(ur.zip has to extracted to deleted the images).
Upload this zip file in portal. (System Administration----> Transport----> Transport Themes ----> Import
Assign this new theme to your framework page and then check for the issue.(100% sure your issue will be solved).
We are setting up the Fiori Launchpad in Portal, all the iviews properties are maintained to be displayed as tiles. We would like to change the icon displayed on the right hand side of the tile, to something from web resource repository.
The image type property is maintained as 'Image(small)" and the ICOn URL is maintained as - com.sap.portal.resourcerepository/repo/com.sap.wrr/Mobile/application_icons/sapstore-tablet.png
But it does not work. Does anybody have any inputs on how the icon should be referenced from the WRR
I have a requirement to mask the forward button for a particular task (TS90*******) in UWL. I was able to mask it by uploading a custom XML file with a high priority. However the hover button dropdown next to the workitem in Subject has the Forward, Resubmit buttons. Can anyone let me know how to disable the Forward option under this hover button. Please let me know if this can be done. Thanks in advance Please see the screenshot below
We are using SAP NW Portal 7.4 and we are checking on a new requirement of consuming RESTful APIs from a 3rd party application in WebDynpro Model component or possibly in EJB. We already have implemented consuming a SOAP WSDL from a 3rd party application in our WebDynpro but using RESTful API is a new one for us. Is it even possible to import/consume REST services in WebDynpro just like consuming a SOAP WSDL? If yes, how? I've been looking for answers from Google but most discussions I can find is going through PI where PI converts JSON to XML format. Can't WebDynpro Java consume REST services directly?
At first we thought that it could be a rendering issue in IE/ Compatibility issue( Any way its a compatibility/rendering issue but we have not got any solution when we check with some settings of IE)
But at last we have got solution by changing the iview and page settings.
For this Go to --> Content administration-->portal content--> Project folder--> And your BO iview and page properties
Change the values of the iview and page to the following, so that the issue will get resolved.
Initial values of the iview and Page were as follows:
Starting in a new window: Display in separate window portal (headerless)
initial status of navigation panel: close
Change the values as follows:
Starting in a new window: Display in a separate window
with the introduction of sap fiori it seems that all the portal content are going to be presented as ui5 application and serve like odata service. is that correct? are portal services going to be accesible via odata? will km, rooms, etc have an ui5 presentation or, at least, an odata services?
will we deploy an odata service on portal just like we are doing with web services??
in resume, whats the future direction of portal applications and portal custom applications in order to fit with the fiori design??
Part One of this blog series covered the fundamentals behind the SAP Fiori Development and touched base on the makeup behind Fiori, Fiori Applications and the utilization of SAP Fiori Launchpad on Portal.
In this blog we will cover the integration between the Fiori Launchpad& the Enterprise Portal. As Fiori is relatively new & "fresh" in terms of large scale utilization it is beneficial to cover the basics before delving into anything too complex Image may be NSFW. Clik here to view..
As with any installation and system landscape one of the core recommendations is to always ensure that you have the latest SP's (Support Packages) and Patch Level Releases applied to ensure potential issues are avoided and put to one side Image may be NSFW. Clik here to view..
Now the SAP Fiori Launchpad on Portal is available only for newer Product Version(s) Release(s)
Netweaver (NW) 7.31 Support Package (SP) 12+
Netweaver (NW) 7.4 Support Package (SP) 7+
To cross reference compatibility and technical release information for further insight a review of the SAP PAM (Product Availability Matrix) is encouraged and recommended: https://support.sap.com/pam.
Configuration Setup (Step By Step)
Phase 1 - Overview
The first point of configuration in terms of setting the SAP Fiori Launchpad on Portal up is to enable the property settings accordingly and this will be performed by a validated System Administrator who holds valid authorizations.
To permit the enable of the Launchpad a new URL alias needs to be created and maintained.
This "URL Alias" is used in association to the Fiori Desktop and "Master Rule Collection".
Through creating the new URL Alias for the "Fiori Desktop" you then need to set the conditions via the "Master Rule Collection".
For comprehensive guidance on the URL Setup and Master Rule Collection the following help documentation can be cross-referenced:
Now after the URL Alias has been defined and the Master Rule Collection has been reviewed and checked in accordance to business standards and requirements the next steps are regarding the iView and Page Setup.
The SAP Fiori Launchpad adds a fresh dimension to iView display as such a presentation is returned to the End-User in the form of Fiori Tiles as opposed to the familiar Portal iView standard.
In this phase we define which iViews & Pages are going to be defined and returned to End-Users in the form of Tiles & Catalogs. There are two types of tiles which can be defined in association to iView displays with each offering their own sense of suitability for business preference:
Static Tiles: consistent and standard information which maintains a defined display.
Dynamic Tiles: as the name suggest the setup here is based on regularly changing information through oData.
In order to determine the Tiles (iViews) and define the setup:
Navigate to "Content Administration" & then "Portal Content Management".
Locate the "Portal Catalog"
Select the iView of interest (from Portal standpoint) and open the context menu.
Open the iView properties through "Open", "Properties" and make the change for FLP (Fiori Launchpad) display.
Once the change is made you need to select "Modify Properties" and Save your changes.
Phase 3 - Catalogs & Categories
In high level terms we can refer to "Catalogs" & "Categories" as the means of grouping applications. Let us revert back for a second and re-reference the types of applications we can use in association to SAP Fiori.
Analytical Applications
Transaction Applications
Fact-sheet Applications
The three application types are diverse and can be tailored dependent on your own business requirements within an organizational establishment.
20 Categories can be holstered within the Properties Editor (2 of which are default standard).
There are two application listing types here:
General: unassigned applications which are not explicitly defined in correlation to a category.
Recommended: suggested and advocated applications which appear as potential tags.
From personal experience there is a very important point to highlight here.
A category will not be displayed if there is no applications defined in its association.
Within the editor you need to ensure that each of the following are defined:
Category ID which is the unique identifier.
Category Order which determines the precedence and order of categories within the tile catalog.
Category Title i.e. the name of the catalog.
Now you need to assign an iView to the category which has just been defined in order to get it to display and return it to end-users.
Open the iView properties through "Open", "Properties".
Select "Personalized Launcher" within "Category Assignment" and fill in the identifier ID's
Any category definition should be separated through the use of a semi-colon.
Phase 4 - Navigation & the FLP
In this section we are going to determine the way in which the FLP returns its element in window display to our end users. From a high level perspective we need to consider this in terms of work feasibility and requirement suitability.
Some of the options available here include:
FLP within the Portal Content Area (central window element of the Enterprise Portal) where standard applications are rendered.
Display within a separate Window (newly opened tabular window)
Separate headerless Window (conjoined to the Portal Session, but opened within a headerless framework window) quirks mode (older)
Separate headerless Window (conjoined to the Portal Session, but opened within a headerless framework window) standards mode (newer)
Navigate to "Content Administration" & then "Portal Content Management".
Locate the "Portal Catalog"
Select the iView of interest
Open the "Properties Editor" and select "Show Category" and click "Navigation"
Determine and define the navigation means of preference as described above and save your changes.
Phase 5 - Resetting User Displays Personalization
If you wish to reset the display settings for users i.e. personalized settings this can be done through property editing or removing the personalization property data for com.sap.portal.navigation.flp.pl.UserData.
This needs to be performed by System Administrators
In my next Fiori blog posting I will be covering the FFP (Fiori Framework Page) and its association to the Enterprise Portal.
We are receiving an error in our SAP Enterprise Portal 7.4 (NWA) log. Its says
Fail to add Node to HistoryService
[Exception]
java.lang.RuntimeException: Secuirty error: failed to validate parameter window ID :
at com.sapportals.portal.navigation.HistoryService.validatewindowID(HistoryService.java:464)
at com.sapportals.portal.navigation.HistoryService.addNavNode(HistoryService.java:291)
at com.sapportals.portal.navigation.HistoryService.addNavNode(HistoryService.java:391)
etc.
I don't know what this means.
Or what we should do to stop it "trying" to make a HistoryService..
Or what security to add to allow it to have a HistoryService?
We are running a single node in the portal. And it is in a DMZ part of the network, so lots of restrictions around it, but this message still means nothing to me.
we are currently trying to move from classic frameworkpage to AFP.
Now I found out that parts of my Detailed Navigation are shown as Contextual Navigation Panel (CNP) in AFP and I wonder why. I found out because I was unable to adjust our theme (see changing the text color in detailed navigation) and because all 4th-level items are shown as "services" below all 3rd-level items.
AFAIK there is nothing special to the relevant parts of the relevant role. I think I scanned through all possible and impossible attributes without success.
So what makes navigation nodes appear as CNP and 4th level appear as Services?
Thanks a lot!
Lutz
PS: Troy Cronin is doing so many great introductory blogs currently. How about a blog about CNP?
Hello experts. Error occurs only in completed tasks option. If I pick active task - error do not occurs, parameters transfer succesful to webdynpro application.