Background:


You are utilizing the Universal Worklist and notice than upon logging into the Enterprise Portal (EP) and loading the UWL (GUI) Interface the Inbox is empty and no work-items are being displayed.From the end-users perspective the empty Inbox means no work-items or work-tasks become visible thus affecting business operations .e.g. approval of sales orders, tracking purposes or travel requests.




UWLInboxEmpty.PNG

High Level Analysis


As with any issue the first investigation steps are in true essence the most vital. From a high level perspective you can easily eliminate probable causes and root sources with a few simple analysis points to follow:


  • Has there been recent UWL Changes or System Upgrades, could this have played a role?
  • Is the issue occurring for all users (if not are we dealing with permissions or authorizations)?
  • Are the Connectors currently maintained in association to the UWL being maintained correctly (check the status column)?

 

Examine the Default Trace


When we are dealing with missing work-items or work tasks the default trace becomes a vital source of reference. When viewing a default trace file you are examining the underlying operations of a system setup. From the perspective of the UWL if there is a small discrepancy in the configuration this will become apparent in the trace itself and return error exception highlights or warnings.


Common Culprits


Depending on what the error exception being returned is most cases of missing work-items can be sourced down to mis-configurations of the smallest proportions. Ordinarily you will see highlights such as the following:


  • Problem occurred while creating JCO for client destination SAP_SRM
  • Problem occurred while creating JCO for client destination SAP_ECC etc
  • User is missing credentials for connecting to alias "ABCXYZ".

 

Remember

 

Here we need to remember the underlying core function mechanism through which the UWL Functions and operates which is that of the UWL Destination Service Configuration. All of the above error exceptions are making direct reference to this configuration setup and indicates a small discrepancy in the settings and parameters being maintained.

 

Solution

 

The core baseline note to follow here (carefully) is that of SAP Note: 1133821 - UWL Destination Service Configuration.

 

By following the documentation above we can ensure that the RFC destination is missing or is not configured properly.

 

After the note is implemented and the WebFlowConnector re-created the cache should be cleared and the backend re-registered.

 

Solution Part 2


Check that after applying Note 1133821 the destination names and the UWL connector names exactly match, even considering case-sensitiveness.


If your portal system alias (=UWL connector name) is for example XYZCLNT100, then the RFC destination name should be exactly XYZCLNT100$WebFlowConnector. Please correct the RFC destination accordingly.


After you have checked/prepared the RFC destination for the future use:


  • Please delete that connector in the UWL config UI (Portal->SystemAdministration->System Configuration->Universal Worklist) with which you would like to use this RFC destination.

 

After that


  • Restart the portal cluster
  • Recreate and Re-Register connector.
  • Now retest.  Are you still seeing the issue?

 

I must stress that this particular documentation note and the steps outlined above need to be followed precisely and carefully to resolve this particular error exception and the surrounding issue.

Backdrop: You are running a setup involving the Enterprise Portal (EP) & Knowledge Management (KM).

 

Details: You have recently upgraded the Enterprise Portal e.g. from 7.00 to 7.3 or 7.3 to 74 and have performed a delta copy of the content currently maintained within the Collaboration Rooms (older version).

 

After performing this action you noticed that the "Room Structures" i.e. the general room makeup markers have indeed been transported correctly however the Room contents have not been carried over

 

What are we dealing with here: Essentially here in this instance you have managed to transport and bring in the previously utilized Collaboration Room setup into the newer Portal Version although the Rooms themselves are blank and missing the core content required for business operations.

 

 

kmblog.PNG

 

 

 

 

 

 

 

Question:

 

What content KM Content do you need to export from the old system to the new system so the collaboration rooms are displayed correctly?

 

Answer:

 

All content located in the collaboration rooms is stored in the 'room_extensions' repository. You should transport the content of this repository if you wish to make the same available in the destination system.

 

Select Content Administration - KM Content • Navigate to folder path /root/room_extensions

 

Core Guidance Points

 

For a reference overview a similar overview is also provided in Transport of Collaboration Room Templates: https://scn.sap.com/thread/495322

 

ICE

 

The KM ICE Distribution guide is accessible via the link below therefore the first recommendation would be to ensure the process is being followed carefully:

 

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/802c1739-d270-2910-ad9f-f369de07c1bf?QuickLink=index&overridelayout=true&10204842398447

 

 

There is also an additional guidance document available below for additional reference purposes "Getting Started with ICE":

 

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0883c3b-ca84-2910-c0ad-80f8e8756275?QuickLink=index&overridelayout=true&10453950474380

Now as we discussed in parts 1 & 2 with each evolving version of Internet Explorer as a Web Browser Platform comes a different set of configuration settings which need to be maintained accordingly in order to support optimal performance.

 

If you missed Part 1 & 2 you can check them out using the links below:

 

  1. http://scn.sap.com/people/troy.cronin2/blog/2016/02/25/ep-browsers-rendering-troubleshooting-support--a-simplistic-overview-part-1
  2. http://scn.sap.com/community/enterprise-portal/blog/2016/03/07/ep-browsers-rendering-modes-troubleshooting--common-issues-part-2

 

In terms of performance we are not making reference to the speed of the browser in any way, shape or form . Instead we are referring to the browser makeup it's associated operations, rendering and interchangeability.

 

The list of reported issues alongside the Utilization of Internet Explorer (IE) can be vast and seem endless. We know to well from our own experiences all of the different issues that can occur whether its browser freezing, missing scroll-bars and incomplete display of icons. If we take these known issues into consideration and combine it alongside the running of an Enterprise Portal and numerous applications the likelihood of browser sourced issues increases drastically.

 

In this blog posting we focus solely on Internet Explorer and all of the different versions. For each version you will see the settings which are both required and recommended to support optimal performance.

 

Internet-Explorer-Cover.jpg

 

Older Versions: Internet Explorer (IE) 7 & 8 & 9

 

Perhaps the three versions listed here are among-st the most popular still being utilized by user bases within organizations. As with any process or product change is inevitable and on some occasions arrives with a sense of uncertainty. One key point to note from the beginning of of January 2016 is a change between what is supported and what is no longer supported.


As of January 12, 2016 only the most recent version of Internet Explorer available for the supported operating systems will receive technical support and security updates.


For more details and additional reference points you can checkout the official Microsoft posting below:


http://blogs.msdn.com/b/ie/archive/2014/08/07/stay-up-to-date-with-internet-explorer.aspx


For Windows 7, 8.1 operating systems and server 2012 R2 this will be IE11. Older versions of IE are no longer supported by MS therefore it is of vital importance that you check the PAM.


These "changes" in support highlights the reasoning behind checking the Product Availability Matrix (PAM) on a regular basis.


Internet Explorer (IE) 8 arrived in 2008 and came into widespread adoption and was followed by IE9 in 2010. These browsers may from a high level perspective not seem that classic or old in terms of usage but the reality is that they are heading towards being almost 10 years old. Both IE8 & 9 offered security advancements, higher efficiency and modern display revolutions.


Enterprise Portal & IE 7,8,9

 

Now in part 2 of this blog series we mentioned "Quirks" and its utilization towards aiding the rendering of displays in an "older-feel" format. Quirks follows the notion of simplicity and with simplicity means easy maintainability.

 

If we take the Enterprise Portal as an example and its markup running in quirks was straight forward. Although again to make reference to term of "evolution" when we begin to add fancy applications and operation mechanisms to our Portal environments "simplicity" is a word which becomes less apparent.

 

IE8/9 & Standards Mode.

 

With Internet Explorer two of the most common terms we hear about are "Quirks Mode" & "Standards Mode". Now we already mentioned "Quirks" and how it relates to and "Older/Classical" type of feel and rendering. With the evolution of the Internet came the evolution of Web Standards thus the term "Standards".

 

To find out what you are currently running you can simply check your current mode setting via F12 and checking the "Document Mode" space.

 

For example

 

quirksandstandards.png

 

As you can imagine when IE8 presented Standards and changes in configuration occurred i.e. switching from Quirks to Standards issues began to become apparent. The default mode for a freshly utilized IE8 or IE9 version remains "Quirks" but on some occasions in order to support desired setups the configuration of "Standards" was required.


If a widespread setting of "Standards" came into effect within an organization issues began to be noted quickly and the resolution is to adjust the browser to re-render in "Quirks".


IE10 & Quirks Mode Emulation


Evolving Web Standards meant a requirement for change was inevitable in terms of the browsers themselves and IE10 introduced the newly titled QME (Quirks Mode Emulation).


IE11 & Standards Mode


Unlike older web browser platform versions IE11 runs in "Standards" Mode as opposed to "Quirks Mode". With IE11 each navigation call across the Portal in terms of opening applications follows the default concept i.e. each window is opened within "Standards". Applications and processes which do not support "Standards" will most likely encounter rendering and select-ability issues.


IE Versions & Which Mode to Use


  • Internet Explorer browsers are not supported in all modes when using the SAP NetWeaver Portal.

 

IE8 Recommended Setup - Changing the browser & document mode to the recommended settings

 

  • Browser Mode = IE8 Compatibility View.
  • Document Mode = Quirks.

 

IE9 Recommended Setup - Changing the browser & document mode to the recommended settings


  • Browser Mode = IE9 Compatibility View.
  • Document Mode = Quirks.

 

IE10 Recommended Setup - Changing the browser & document mode to the recommended settings


  • Browser Mode = IE10 Compatibility View.
  • Document Mode = Internet Explorer 5 Quirks.

 

IE11 Recommended Setup - Changing the browser & document mode to the recommended settings

 

  • Document Mode = 5. To set this configurations please do as follow:
  • Open IE browser.
  • Press F12 (or 'Tools' -> 'Developer Tools').
  • At the top right corner you will be able to set the Browser Mode and Document Mode.

In the last blog posting we highlighted and provided a brief overview on the different complexities which can arise with various web browser platforms and the parameter settings which support them. Catch Part 1 http://scn.sap.com/people/troy.cronin2/blog

 

Now with browser related issues the key towards their resolution is simplification and maintaining a high level analysis viewpoint.

 

In this blog posting we are going to discuss the parameters themselves with a brief overview on each.

 

 

BROWSERDOCUMENT.PNG

 

Navigation & Different Mode (Parameters)

 

From a purely navigation approach we are dealing with two key modes which are that of Browser & Document Mode.

 

  • Browser Mode: A user agent string sent to the server (which affects the User Agent only).

 

    • When compatibility mode is selected the the User Agent is set to the oldest supported setting for the current browser.
    • Tools > Compatibility View > F12 > Navigation > Navigation.UserAgent
    • IE10, IE10 Compatibility View, IE9, IE8, IE7.

 

  • User Agent: essentially a string (textual) which identifies the Browser & OS to for the Web Server.

 

  • IE5 Quirks: oldest document mode. IE tells the server its browser mode. According to the browsers mode the server decides which resources CSS/JS should be sent back to the Browser.

 

  • Document Mode: Determines how the browser (IE) renders the page.

 

    • Essentially tells browsers how it wants it to be rendered.
    • Browser decides which rendering engine should be used.

 

  • Quirks: displays webpages as if users view them with older versions of the browsers.

 

  • Standards: HTML 5 engine, new features are only supported in this mode.

 

Important Points to Remember.

 

As we mentioned with so many different setting highlights at play its quite easy to confuse one setting from another.

 

From a high level perspective let us remember that Document Mode determines how Internet Explorer is rendered. Quirks Mode displays the webpages as if they are within older IE versions while Standards Mode follows the HTML5 Engine with new features supported. The Quirks Mode syntax is different from the Standards Mode syntax.


browsersandserver.PNG

DOCTYPE is only in standards mode.

 

hierarcy.PNGPart 3 Coming Soon

This blog is for portal end-users and content administrators who would like to learn about the new features developed in the latest Enterprise Portal SP for FLP on EP, their added value, and the configuration required.

Prerequisite: Minimum required SP for ABAP FES server is SAPP_UI750 SP02 component, which includes SAPUI5 1.34.x For additional information please refer to SAP note 2031108.


1 Sync Home Page

This new action on Options Menu allows an end-user getting the updated content on the Home page after portal administrator changes it.

SyncOptionMenu.JPG

SyncPopUp.JPG

 

Detailed information on each selected option behavior can found here.

To enable this feature portal administrator should check-in the following parameter on the Framework Page configuration page:

 

AdminSync.JPG

 

 

2 News Tile (via RSS feeds)

This feature allows your portal server to access the external websites and update the tile content constantly:

NewsTIle.JPG


To enable this feature an administrator has to fulfil the following steps:

  • Define proxy host and port for portal server http service and restart it
  • Download the RSS feed xml file from a news site and save in on portal server under C:\usr\sap\<server ID>\J00\j2ee\cluster\apps\sap.com\irj\servlet_jsp\irj\root
  • Create a news tile using News iView template and set the properties as described here. An example is shown below:


     AdminNews.JPG

  • Check in the news iView property Default App in Home Page, assign the news iView to the end-user role (usually it is also shown in a locked group).


3 Theme Change Using User Preferences Option

An end-user can set the preferred theme using Options Menu (User Preferences option).

 

ThemeDropdown.JPG

After the end-user chooses a theme and presses Save,  the UI is refreshed and displayed in a new theme.

 

To learn more:

In the Enterprise Portal we can create content structure directly in the Portal Role Editor.

When a portal role is created we can add content from the Portal Content Catalog as a delta link or as a copied object.

The content is being added with the original object ID and a serial suffix in case this ID already exist.

 

Content administrators want to be able to add objects with specific ID for different useful reasons (search, management, etc.)

 

In this blog I want to share "how to enable object ID change" during the add action.

This is useful functionality disabled by default and we need to enable it in configuration NWA UI.

1. Open NWA (SAP NetWeaver Administrator) http(s)://<server>:<port>/nwa

nwa1.jpg

2. Navigate to "Operations" -> "Systems" -> "Start & Stop"

nwa2.jpg

3. Select "Java Applications" and filter by "com.sap.portal.appdesigner.contentcatalog" and select "Portal Service Configuration"

nwa3.jpg

4. Change the Value for "Enable changing properties" to True and "Save"

nwa4.jpg

 

5. From "More Actions" select "View Corresponding to Application"

nwa5.jpg

6. In the "Portal Service Details About com.sap.portal.appdesigner.contentcatalog" view select "Stop Service" for "contentcatalog" service "On All Instances"

nwa6.jpg

7. In the "Portal Service Details About com.sap.portal.appdesigner.contentcatalog" view select "Start Service" for "contentcatalog" service "On All Instances"

 

Result is that during addition of an object from the Portal Content Catalog to the role in the Portal Role Editor  - the popup "Mofify Properties" appears with an option to change object ID.

result.jpg

Background

 

A trypical scenario for many Portal administrators is the need to update multiple object properties for different reasons, be it document Rendering modes, assignments, navigation modes etc.

Fortunately there are tools available under both Netweaver 7.0X and higher which enable the batch setting of these parameters, saving considerable time that it may take to make these changes individually.

 

Under Netweaver 7.0X systems, the tool is called the "Multiple Property Replacement", while under Netweaver 7.X systems, the tool has been renamed the "Find & Replace" tool.

findnreplace.png

 

Caution!: This blog post contains instructions on using a very powerful tool. Incorrect use of this tool may result in content inconsistencies. Please take care while using the tool. The SAP Help documentation regarding this tool, containing more information may be found at the URL below:

http://help.sap.com/saphelp_nw73/helpdata/en/76/7a4d2984c54338aeb9531a758d3405/frameset.htm

 

Introduction

 

For this tutorial, I will be demonstrating under a Netweaver 7.40 system using the "Find & Replace" tool. The objective for this tutorial will be to change the Navigation Mode (NavMode) for multiple iViews from "Display in Portal Content Area" (NavMode0) to "Display in seperate headerless portal window (standards mode)" (NavMode10).

It should be noted there are slight differences between the two tools, however, each tool will support the scenarios that are illustrated below.

 

Tutorial

 

  1. We first go to the Content Administration area of the Enterprise Portal. We must have the Portal Super User roles (or equivelent permissions) to access this area
  2. Expand the Portal Content Catalog so that you have visible the folder(s) with the objects contained inside that must be changed in bulk. In this scenario we are going to set the Navigation Mode property in bulk for the iView object type
  3. Right click on one of these folders, hover over Search -> click Find and Replace as below:
    far1.png
  4. Under the Search and Replace wizard: for name, we are going to enter asterisk '*' to show all items, and for Object Type we are going to choose iView as below:
    far2.png
  5. After hitting Next, the tool will display all the iViews maintained under this Folder. At this point any iViews you wish to exclude may be removed from the list. When happy click next.
    far3.png
  6. At this point we must enter the Property Type for the property we want to set in bulk. To locate this, in a new browser tab call your Portal and navigate to Content Administration. Open any of the affected iViews Properties you wish to change. Make sure all properties are shown.
    Now we must locate the iView property we want to set in bulk, in this tutorial this is the "Launch in new window" property:
    iview property.png
  7. Under Attributes, click the Show attributes button. The attribute window appears, displaying the Property ID, and descriptive text about possible entries:
    linwprop.png
  8. From the above we can see the Launch in New Window Property ID is com.sap.portal.navigation.ShowType, and the possible values under the description. Now Close the iView.
  9. Navigate back to the Find & Replace wizard, enter the Property ID as above, and we are setting the value to equal 10 (NavMode10). We are also setting the Replacement Method to Overwrite the current value:
    far4.png
  10. At this point the wizard will confirm the iViews to be changed, it will also display the objects current property value. Click the Finish button to confirm the property changes:
    far5.png
  11. Sucess! The properties should now have been changed in bulk! Check the iViews you have changed to ensure the changes have been made successfully.

When utilizing the Enterprise Portal or running with a Netweaver environment we can all agree that upgrades, SP Deployments, Patch Level applications and browser changes are a normality. For example in a business scenario and in accordance to business requirements you may be moving from one NW Version to another e.g. NW 7.01 to NW 7.4 or changing between Web Browser Platform versions.

 

 

With each different Web Browser Platform comes a set of different configurations which need to be maintained in order to ensure optimal performance.

 

By performance here we are making reference to the actual display (rendering) of the Portal Setup and the navigation output (selectability).

 

 

If you are dealing with different web browser platforms and product versions its quite easy to encounter different rendering modes and display issues.

 

 

 

 

browsers.jpg

 

 

 

From my experience I have seen multiple scenarios with all different types of issues. The one common characteristic which became apparent during troubleshooting is "complexity" there are numerous parameters, settings and properties at play which can make the scenario quite confusing from the offset.

 

 

The whole purpose of this next blog series is to break everything down and create a troubleshooting baseline that can be followed on a step-by-step basis towards identifying the solution.

 

 

The First Point of Call - Am I Supported?

 

If you've recently encountered some form of display issue whether it is with the Portal itself or an application rendering within the Portal Content Area one of the first analysis steps to follow is to check out whether this setup is supported. A simple way of checking this is through the SAP Product Availability Matrix or PAM for short. On the PAM we are given a comprehensive and detailed overview on what Product Versions support which types & versions of Web Browser Platforms and vice versa. The PAM will also help you highlight any potential issues (if any) that would be expected.

 

On the PAM you can check your current setup and its support compatibility via the following path:

 

 

Commonly Used Browsers

 

  • Internet Explorer 8, 9, 10, 11
  • Mozilla Firefox
  • Google Chrome

 

A Point on Internet Explorer


As of January 12, 2016 only the most recent version of Internet Explorer available for the supported operating system will receive technical support and security updates (see IE blog http://blogs.msdn.com/b/ie/archive/2014/08/07/stay-up-to-date-with-internet-explorer.aspx). For Windows 7, 8.1 operating systems and server 2012 R2 this will be IE11. Older versions of IE are no longer supported by MS therefore it is of vital importance that you check the PAM.

 

What Type of Issue am I dealing With?

 

If you encounter an issue whether its to do with rendering of applications, general display or peculiar behavior from the Portal's perspective one quick and easy means of analysis is to determine whether it is solely browser related. Here all you need to do is attempt to reproduce the issue in various web browser platforms. Certain business requirements may only allow specific web browser platforms but if feasible you should try and test the issue in IE, Chrome & Mozilla. If the issue pertains to only one web browser platform then you have successfully indentified the problematic source and can troubleshoot from this aspect.

 

Note Search

 

If you managed to trace the issue to only one browser platform the next step is to conduct a note and documented fix search as the likelihood as the issue has arisen previously and a fix should be readily available.

 

 

Part 2 coming soon - Internet Explorer (IE) & Modes, A Simple Overview - Part 2

Backdrop: In the interest of using a practical example as a baseline for understanding let us assume that you are using an Enterprise Portal Setup which incorporates a lot of information with Knowledge Management (KM) repositories.

 

Storage Purposes - What is a CM Repository Manager ?


  • A CM repository is used as the main repository for storing documents and folders that are managed by CM.

 

 

h-00100010000_image002.gif

 

 

Throughout your review of the various material and options available you come across the three different modes in association to KM-CM.

  • DB Mode
  • DBFS Mode
  • FSDB Mode

 

You want to export information from a database to a file-system is this possible?


Firstly these "modes" outlined above are feasible options for CM Repository mode choices and ordinarily are selected via preference by different customers depending on their setup and landscape. You may on some occasions see this "modes" labelled as "persistence modes" as this is another associated term.

 

Now back to question: Q: Can you export all information from a DB to File System?


A: In short the answer to this query is yes that this is indeed a feasible option and can be achieved via a transport package. Although from a high level perspective I would encourage diligence and to ensure that essential information is backed up as a general guidance rule of thumb.

 

In order to aid you in the transport and export you can make use of the following guidance documentation which provides a comprehensive and information overview:

 

 

DB VS DBFS VS FSDB

 

Let us work through the different modes and summarize what each are below (you may already be aware of the following based upon your previous analysis).

 

1: DB Mode:  All data (documents, folders, and metadata) is stored in the database. If there is a large number of write requests in your CM usage scenario, set up the CM repository in database mode. Since all documents are stored in the database, this avoids unintentional external manipulation of the data. Another advantage of storing all data in the database is that the procedure for data backup and restore is easy since only the database needs to be backed up.

 

2: DBFS Mode:  Metadata and folders are stored in the database, but documents are stored in the file system. This mode is faster than the database mode if you have large documents since there is no database data streaming. This mode also enables the size of the database to be controlled more easily since documents are stored in the file system.  The documents and metadata are stored in different places, so you have to take into account both the database and the file system and synchronize them both when backing up and restoring data.

 

3: FSDB Mode:  Folders and documents are stored in the file system, but metadata is stored in the database. In this mode, the file system is predominant. File systems are not transactional, so this mode has restrictions and affects performance. If read and write operations take place for one document in the file system at the same time, these operations have to be coordinated by the repository manager. This happens by recording both write accesses and read accesses in the database. This affects performance.

Hi Gurus,

 

Stuck in Portal 7.31 roles assignment to end user. please help me to release from this, Thanks in Advance.....

 

 

Portal 7.31 Attached the 10 common roles to more than 20 end users, try to run with super administration role is working.

 

Try to run without super administration role is showing Error:

 

Portal runtime error

An exception occurred while processing your request. Send the exception ID to your portal administrator.

Exception ID 09:17_08/02/16_0066_21596950

See log file for details about this exception



LOG file:



Error loading embedded application (componet - com.sap.tc.lm.itsam.co.ui.xi.msg.ximessagedetailed.XIMessageDetailed.
[EXCEPTION]

com.sap.tc.webdynpro.services.exceptions.ApplicationFaultException: wdDoInit: exception thrown in this user coding area
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:164)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:227)
at com.sap.tc.webdynpro.progmodel.components.Component.initController(Component.java:258)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:206)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:418)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:352)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.loadEmbeddedApplicationInternal(FloorPlan.java:2211)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.loadEmbeddedApplication(FloorPlan.java:449)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.init(FloorPlan.java:666)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.loadProfessionalApplication(FloorPlan.java:1214)
at com.sap.lm.itsam.ui.floorplan.FloorPlan.navigateNFtoEmbeddedApplication(FloorPlan.java:1851)
at com.sap.lm.itsam.ui.floorplan.wdp.InternalFloorPlan.wdInvokeEventHandler(InternalFloorPlan.java:975)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.invokeEventHandler(DelegatingComponent.java:248)
at com.sap.tc.webdynpro.progmodel.components.Component.fireEvent(Component.java:492)
at com.sap.tc.lm.co.ui.nwa.workcenter.overview.wdp.InternalWorkCenterOverview.wdFireEventNavigateToEmbeddedApplication(InternalWorkCenterOverview.java:315)
at com.sap.tc.lm.co.ui.nwa.workcenter.overview.WorkCenterOverview.fireEventNavigateToEA(WorkCenterOverview.java:381)
at com.sap.tc.lm.co.ui.nwa.workcenter.overview.wdp.InternalWorkCenterOverview.fireEventNavigateToEA(InternalWorkCenterOverview.java:222)
at com.sap.tc.lm.co.ui.nwa.workcenter.overview.WorkCenterOverviewView.onActionNavigate(WorkCenterOverviewView.java:440)
at com.sap.tc.lm.co.ui.nwa.workcenter.overview.wdp.InternalWorkCenterOverviewView.wdInvokeEventHandler(InternalWorkCenterOverviewView.java:221)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:101)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sap.aii.utilxi.prop.api.PropertiesException$InitFailed: Unable to read configuration data (ExchangeProfile/aii.properties)
at com.sap.aii.utilxi.prop.api.PropertySourceFactory.initServerMode(PropertySourceFactory.java:221)
at com.sap.aii.utilxi.prop.api.PropertySourceFactory.getPropertySource(PropertySourceFactory.java:56)
at com.sap.aii.utilxi.prop.api.AIIProperties.sync(AIIProperties.java:859)
at com.sap.aii.utilxi.prop.api.AIIProperties.<init>(AIIProperties.java:578)
at com.sap.aii.utilxi.prop.api.AIIProperties.getInstance(AIIProperties.java:603)
at com.sap.tc.lm.itsam.co.ui.xi.msg.ximessagedetailed.XIMessageDetailed.wdDoInit(XIMessageDetailed.java:321)
at com.sap.tc.lm.itsam.co.ui.xi.msg.ximessagedetailed.wdp.InternalXIMessageDetailed.wdDoInit(InternalXIMessageDetailed.java:1206)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:161)
... 77 more
Caused by: com.sap.rprof.dbprofiles.DBException: dbconnect.prop: failed to load properties file .\dbconnect.properties
at com.sap.rprof.dbprofiles.AbapConnect.setupDefaultJcoCommunication(AbapConnect.java:126)
at com.sap.aii.utilxi.prop.rprof.ExchangeProfileR3PropertySource.<init>(ExchangeProfileR3PropertySource.java:36)
at sun.reflect.GeneratedConstructorAccessor719.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at com.sap.aii.utilxi.prop.api.PropertySourceFactory.initServerMode(PropertySourceFactory.java:169)
... 84 more


After an upgrade you find rendering issues with your portal theme, it can happen either with custom or standard themes and the theme appears distorted after login. I will go through some of the more common scenarios and resolutions.


 

Problem with rendering of SAP standard themes:


If you find that this is happening with standard SAP themes only then a good place to start with is kba 1911990 - 'Enterprise Portal looks distorted after logon'. The resolution section contains 3 steps which should be executed in the order they appear (so first step 1, next 2 and finally 3). Its very important that after you implement each step to test the scenario again to see if the issue is resolved and themes are displaying correctly.

 

 

Problem with rendering of custom themes:

 

  1. If its happening with your custom theme only, then firstly check kba 2028300 - 'Custom portal theme distorted'.
  2. If re-importing your custom theme doesn't help, then check to see if the issue is happening on one or some nodes only. If it is then check kba 2195099 - 'Portal theme is inconsistent after upgrade' to manually synchronize all server nodes.
  3. Note 2197656 - 'Custom themes does not exist in all server nodes' includes a fix for this synchronization issue for later releases.
  4. Is note 1738135 - 'Theme inconsistency in portal after 7.3 upgrade' applicable for your version?


If none of the above helps then reproduce the issue and check the default (kba 1596214) or logwatch (kba 1593107) trace files. For theme problems you should increase the severity of the following logging locations to ALL prior to reproducing the issue:


com.sap.portal.design: ALL

com.sap.portal.themes: ALL

com.sapportals.portal.design: ALL

com.sapportals.portal.style: ALL

 


Other notes:


  • If you find the below exception in the traces after reproducing the issue, then apply kba 1959644 - 'Theme distorted after upgrade Error:LAFService.deleteTheme -> after deleteTheme'


#EP-PIN-TOL#sap.com/com.sap.portal.themes.lafservice#C0000A7EC319004B000
0022F000002B3#637167351000006463#sap.com/com.sap.portal.themes.designser
vicenotificationservice#com.sapportals.portal.prt.service.laf.LAFService
#Guest#0##A7E9808742F011E3B00B000025FA66F7#a7e9808742f011e3b00b000025fa6
6f7#a7e9808742f011e3b00b000025fa66f7#0#Application [53]#Plain##
LAFService.deleteTheme -> after deleteTheme.#


  • Or if the following exception is found in the traces, then apply kba 2044168 - Customized portal theme not displayed after the upgrade


Error in starting application [sap.com/com.sap.portal.themes.designservicenotificationservice].
[EXCEPTION]
com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error in starting application [sap.com/com.sap.portal.themes.designservicenotificationservice].
...
Caused by: com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error occurred when invoking start methods of web container extensions for

...
Caused by: java.lang.NoSuchMethodError: com.sapportals.portal.prt.service.laf.ILookAndFeelService.getApplicationName(Lcom/sapportals/portal/prt/service/laf/ThemeType;)Ljava/lang/String;



Introduction

 

By default, within the Enterprise Portal it is not possible to define a custom width for the left side Navigation Panel/DTN area of the Portal Framework Page. In this blog post, I will show you a workaround where you can set the Nav Panel to equal a specific custom width:

leftnavPanelOpen_2.png

Important information before you begin: You must have activated LESS theming mode (SAP KBA: 1997947) and use the Ajax Framework Page.

 

Creating your new theme


  1. Open the UI Theme Designer (Content Administration -> Portal Display -> UI Theme Designer) and open your theme of choice
  2. From the Theme menu choose Save As and choose a new name for your custom theme
  3. Click on the Expert Mode icon under the UI Theme Designer
  4. Filter by the property leftnavPanelOpen
  5. Adjust the value of this parameter based on your requirements (width should be specified in pixels/px)
  6. Refresh your theme display in the UI Theme Designer to observe the changes

For further details please reference the below screenshot:

leftnavPanelOpen_1.png


Testing your new theme


You can test your new theme quickly by logging out of your Portal, and calling the theme directly via the Portal URL:

http://<host>:<port>/irj/portal?theme=your_theme_id


You can locate your Theme ID either under the Portal Catalog or from within the UI Theme Designer itself:

theme-id.png

Backdrop:

 

You are utilizing a setup that involves the Universal Worklist and end-users working alongside various workitems.  In the Universal Worklist (UWL) a number of workitems are displayed within the Inbox but do not change immediately after an action is performed.


For example "New/In Progress" along with "Completed" workitems remain in the UWL Inbox despite a manual refresh or action change.


Capture1.PNG

Status Types:


  1. "New": The task is displayed in the task list of all potential owners. No potential owner has opened the task yet. When the actual owner of a task has put it back, the status of the task is also New and visible to all other potential owners.
  2. "In Progress": The task is claimed by one of the potential owners who has opened the task execution UI. When a task is opened, it is automatically claimed by the user and he or she becomes an actual owner. Thus, the task disappears from the task lists of all other potential owners.
  3. "Completed": The task is displayed in the Completed Tasks view. No other actions can be performed on the task. The Completed status focuses on the task life cycle completion, so that the task business goal is reached.


 

uwlbehaviour.PNG

 

Why is the change not immediate?

 

When you open and run the UWL Service it takes a total of 5 minutes for all the tasks to be loaded up and represented back to the end user in graphical format as this is standard behavior.

 

UWL Functional Breakdown


The UWL works using two Pull operations. Firstly tasks are pulled from the backend into the UWL cache and they are then pulled a second time from the cache into the UWL User Interface. Due to this architecture there is an inherent delay in the automatic refreshes of the UWL. There is no way, in the current architecture that the UWL can refresh instantaneously. This is upon inital load as the cache must be built first upon logon so there will always be a delay. Real time refresh in the latest versions, is only when you complete a task. The Universal Worklist Task Filters follow the standard underlying functionality of the UWL refresh mechanism.

 

Improving the Refresh Interval & Filter Return Display

 

Let us remember that if you utilize the UWL within an environment that contains hundreds of work-items and end users there will be a lot of background activity each and every time the UWL is loaded. Reviewing the UWL core parameters and striking a balance among them is one of the best methods to create an optimal setup. The standard behaviour of the UWL remains that you will need to wait for 5 minutes for these changes to be updated regarding the workitems.

So as we discussed in the first theme based troubleshooting blog posting http://scn.sap.com/people/troy.cronin2/blog/2016/02/06/ep-themes-issues--breaking-the-issue-down-high-level-analysis there are several ways to help simplify a theme based issue.

 

In this blog posting we'll move forward a little in analysis terms and outline some common issue scenarios and resolution approaches that can be applied.

 

3 Principles To Follow - If you encounter an issue


  1. Determine firstly if the issue happens in all web browser platforms (Internet Explorer, Google Chrome, Mozilla).
  2. Determine if the issue occurs in both SAP Standard Themes & Custom Themes.
  3. Determine if the issue can be reproduced in all Portal Framework & Theme Combinations

 

If you've followed the three principles above you already have a better understanding of your issue and can delve quickly into further analysis to get a solution.

 

ppt_img.gif

 

 

 

Common Issues

 

  • Custom Theme not applied
  • Application iViews & Pages appear blank i.e. they do not inherit the designated Portal Theme
  • Yellow boxes in Header Area
  • Theme Transport & Import's not functioning accordingly
  • Issues with Theme Export
  • Unable to change Font colors and display
  • Mix-up of themes and issues applying/assigning themes.

 

So as you can see there's several common issues in association to Portal Themes. What in truth seems like a simple topic offers its own distinctive avenue of complexity.

 

Patch Level Releases & SP's


If you encounter any issues similar to those posted above the first recommendation would be to review the SAP Service Marketplace to determine whether your issue is "known".


If the issue has been previously reported its quite likely a implementable fix is currently available via a Patch or Support Package.


  • https://support.sap.com/swdc
  • Important: make use of the dependency tool provided to ensure there are no system discrepancies if you implement a Patch/SP.

 

Browser Compatibility

 

If you source the theme issue to one particular web browser platform you need to make sure its utilization is supported via the PAM.

 

  • On the PAM navigate to "Technical Release Information" & "Web Browser Platforms" (Is that browser supported?)
  • https://support.sap.com/pam

 

Font Issues

 

Ok from a general perspective there are a few important points to highlight regarding any font changes with the Enterprise Portal. The font does not have to be installed to the portal, but to the users' desktops. Entering the value in the  tool e.g. Theme Editor will simply cause the font to be referenced in the portal stylesheets; the browser is the component which actually locates the font and  the page accordingly.

 

In the Theme Editor, you can go to Global Style Components > Text and choose to either 'Select a Value' or 'Enter a Value of your Choice'. Entering a valid font name in the second option updates the available entries in the dropdown, and adjusts the theme preview accordingly.

 

Note that there is no question here of installing a font to the portal; updating the theme editor merely updates the stylesheet references, so the font in question would need to be available on each client PC.

 

 

The Infamous Yellow Box

 

Are you seeing a yellow box appearing in the Masthead or DTN area or somewhere else on the Portal UI?

 

  • There is a known issue pertaining to JPG type images being ignored and thus they create empty yellow spaces (check the Patch fixes for this firstly).

 

Secondly there is the purely customization based root source of such an issue. I would suspect that you are using your branding image in the designbar instead of the masthead  or branding image containers.


You are then resizing the design bar much larger than in the standard themes supplied by SAP. The design bar is meant to be a narrow border on the extreme left hand side of the masthead.

 

However to resolve this issue is quite straight forward (and you can leave your settings as they are).

 

If you call:

 

 

You will see two drop * For the 1st one Browser, leave this as 'default'. Then the second one, locate parPrtlMastHeadNotchBgColor

 

For your theme, then set the desired colour.

 

This will set the background colour for where the yellow bars are showing and the idea is to change the background colour to white.

 

After updating the value, be sure to, click first 'Set Value' and then 'Save and Generate' to actually generate the new css files.

 

You can follow the link below for a reference on to the colours to set. http://www.w3schools.com/html/html_colors.asp

 

 

 

spraypaint.jpg

 

 

 

Assigning Themes, Theme Transports & Exports & Subsequent Imports - You have an issue


You have a custom theme created in one EP Version e.g. 7.4 SP02 and imported to SAP Portal 7.4 SP09. Now after the upgrade the theme was customized successfully e.g. using the UI Theme Designer and transported via the Transport package but the Export option in "Transport Themes" is

missing.

 

Custom themes should be saved automatically and visible within WRR and changes made within the WRR are persistent.

 

If your custom theme is based upon Corbu/GoldenReflection/BlueCrystal here you are dealing with a support issue (these are product version dependent).

 

The reason a visual display would revert back to a SAP Default/Standard theme is the omission of the parameter "Handover Portal Stylesheet".

 

The stylesheet iview parameter this is not used to specify what "sap-cssurl" to hand over to the backend, but rather to specify the type of stylesheet to use (e.g. 'ur').

 

Its not possible to disable handover of the portal stylesheet and at the same time specify a stylesheet URL in the portal.

 

You can force use of a specific stylesheet on the webdynpro side, using sap.useWebDynproStyleSheet=true and setting the sap.theme.default property to the desired theme.

 

With the Portal stylesheet the display type is obtained from the backend. In terms of the content area and navigation areas two seperate themes cannot be utilized at the same time.

 

Stylesheets

 

With portal integration the system first checks that the portal has transferred a specification for the style sheet. If the WDFORCEEXTERNALSTYLESHEET application parameter is * the specified portal style sheet is used. If, on the other hand, the WDFORCEEXTERNALSTYLESHEET application parameter is not * the versions of the style sheets are compared.

 

If the version of the portal style sheet is newer or the same as the style sheet in the SAP system, the portal style sheet is used. All four digits of the version number of each style sheet are compared.

 

For example, the version is 7.0.0.0 or 7.1.3.0. If the version of the portal style sheet does not match the style sheet in the SAP system, that is, the portal style sheet is older, then the style sheet specified in the WDTHEMEROOT application parameter is used. If no style sheet is specified here, the default style sheet is used.

 

- Setting Style Sheets: http://help.sap.com/saphelp_nw73ehp1/helpdata/en/03/1ed736f5ca44aa8dbbcbcf1406342c/content.htm

 

If you have an issue not covered in the bullet points above feel free to DM me directly or Post below and I will help out wherever possible.

 

Happy Theming

The impressively beautiful themes we create and utilize on the Enterprise Portal are not merely empty shell's but rather complex containers involving coded elements, components and segments.

 

In some instances a change occurrence such as a Portal upgrade or System Migration can cause a theme setup and display to become problematic.

 

 

theme1.PNG

 

On many occasions a change in browser utilization can often result in rendering issues also.

 

Examples of such issues include the following:

 

  • Partial rendering
  • Disappearance of elements
  • Non-delectable icons and navigation points
  • Cut screens

 

In true essence the elements which go into making a theme can become problematic due to their conjunctive complexity when grouped together.

 

Standard Theme Types

 

  • SAP_Tradeshow
  • SAP_HighContrastBlack
  • SAP_BlueCrystal
  • SAP_GoldReflection
  • SAP_Chrome
  • SAP_Streamline

 

If you encounter theme based issues there are a few avenues of analysis to follow.

 

  • One key point to check and review is whether the issue is confined to one particular web browser platform. If you are able to reproduce the issue across all browsers e.g. IE, Chrome, Mozilla etc then this would signify the "theme" itself needs troubleshooting as opposed to the environment in which it functions.

 

The second recommendation would be to ensure that the themes are being held and holstered correctly and not facing any deployment issues.

 

You check the deployment by navigating to :

 

  • \usr\sap\<sid>\<instance-id>\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment,\pcd ,\tempand \pcdContent

 

If you find any files with .err extension there, kindly remove the .errextension.

 

Then restart the J2EE engine.

 

Should the issue still not be resolved and there does not exist any.err files,kindly locate following * files in the deployment directory and remove the * extension and restart the J2EE engine.

 

com.sap.portal.design.dataprovider.par.bak
com.sap.portal.design.portaldesigndata.par.bak
com.sap.portal.design.themepartregistration.par.bak
com.sap.portal.design.urdesigndata.par.bak

 

Note: Please make sure that you do not delete the entire file,you onlyneed to remove the .err or * extension.


In cases like these the main points of analysis and investigation are to delete the standard SAP themes and then perform a restart. During the restart they will be automatically regenerated.

 

For this please ensure to do the following:

 

Make sure you have your custom themes backed up.


  1. Delete the SAP-supplied themes using the PCD Inspector.
  2. Very important - only the central instance should be up and running during the deletion of the themes
  3. Please also make sure only SAP themes and not your own custom ones are deleted as custom themes will not be regenerated.
  4. Now stop the portal.
  5. Go to the file system and delete the theme from the file system for each server node, if they have not already been deleted by the portal.

 

The paths where the themes can be found are:

 

  • \usr\sap\<SID>\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB INF\portal\portalapps\com.sap.portal.design.por t aldesigndata\themes\portal&
  • \usr\sap\<SID>\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.design.urde signdata\themes\portal

 

Restart the portal. Only the central instance should be started at this stage.

 

  • Check to see if the SAP standard themes are now working as required?

 

If not another stage of troubleshooting is required (which I will cover in another blog posting).

 

Simply following high level investigation analysis steps such as those outlined above can help you determine many key points such as:

 

  • Are you dealing with an actual theme issue or a browser issue?
  • If you are dealing with a theme issue is it confined to a custom theme/standard theme or all themes?

 

If you analyze theme issues from an overview scope you can fine-tune your investigation from the offset and help eliminate countless possibilities thus making it easier to find and attain a quick, quality resolution.

Actions

Filter Blog

By author:
By date:
By tag: