ABAP Webdynpro Screen Display Issue in Portal

[Former Member]

We have upgraded the Portal landscape from 7.0 to 7.01 sp7.

In Dev Portal system after upgrade we have not found any error for WDABAP Applications. But, in Quality portal system after upgrade, ABAP Webdynpro screens are not able to display stylesheets and everything is coming in text format even the buttons, value help etc. We have the same configurations and same patches working in our Development Portal system as well as Quality Portal system

We have followed following Steps to Debug

1)we have checked the services in portal and ECC systems and all the

sicf services are active

2)We tested the ABAPWebdynpro appl in ECC in SE80 which works fine.

3)ITS and WAS connections are also configured properly

4)We ckecked the Appl using IE6 and IE8 but its failing in both.

Best Regards,

Mahesh Das

[thomas_jung · Accepted solution]

What release/patch level is your backend ABAP system? If it is later than the portal release/patch level, then you could have a theme/style sheet mismatch. Are you using a custom theme? Have you regenerated the theme after the update? This is really more of a Portal question than a WDA one.

[Former Member · Accepted solution]

The Backend ABAP system as at the same level as Portal system - 7.01 SP7. Yes we are using custom theme. But we have not regenerated even in case of Development system where applications are running fine after Portal Upgrade.

Also if this is the case of Portal style sheets then it should affect all the portal applications but we are facing this issue only for WDABAP Applications which are created through WDABAP template in Portal. For url iviews if we are giving directly the url for the WDABAP Applications they are running fine.

Also while executing the erroneous WDABAP Application in Portal, we are getting a warning message from IE stating:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.3)

Timestamp: Thu, 7 Apr 2011 14:36:21 UTC

Message: Invalid argument.

Line: 1

Char: 2168

Code: 0

URI: http://hostname:port/sap/bc/webdynpro/SAP/ZALGW_INVENTORY_FORM/;sap-ext-sid=C0sBhUjiD4zUYnoXb8FwWwLCJvPjoVrHo4g0gsFF5yww

[thomas_jung · Accepted solution]

>Also if this is the case of Portal style sheets then it should affect all the portal applications but we are facing this issue only for WDABAP Applications which are created through WDABAP template in Portal

No it wouldnt' impact everything. WDA is unqiue in that the framework is rendering by the backend but the CSS and Theme is taken from the portal (not the backend) when running within the Portal.

>For url iviews if we are giving directly the url for the WDABAP Applications they are running fine.

This would actual seem to indicate a problem with the Portal themes even more. When ran as an URL iFrame, the portal theme is no longer used and all theme files come from the backend only.

>Yes we are using custom theme. But we have not regenerated even in case of Development system where applications are running fine after Portal Upgrade.

You should regenerate custom themes in all systems after an upgrade - especially 7.0 -> 7.01 since the switch to the lightspeend rendering for Web Dynpro ABAP.

[Former Member · Accepted solution]

Thanks for your inputs. But can you please guide us with the themes regeneration process. Basis has confirmed that they have followed the proper steps for systems upgrade both ECC and Portal. How this theme regeneartion can be done.

I am getting proper theme in SystemAdmin-> Portal Display-> Desktops& Display rules-> themes folder

[thomas_jung · Accepted solution]

I don't work with the NetWeaver Portal so I couldn't tell you the steps. I would refer you to the following OSS notes on this subject.

1494246

1446099 >> Particluarly this note as this has some nicely detailed steps on the portal side

When you upgrade from 700 portals or their styles to 70x (701, 702 and

so on) portals, the system adds new parameters without their related

values for the customer theme. This situation may lead to display

errors. This may occur in particular if WD applications run in the

"lightspeed" rendering technology during the upgrade.

[Former Member]

Hi Mahesh,

I have the exact same problem as yours.  My portal is upgrade from 7.0 SP21 to EHP2 SP11.  Everything looks fine in DEV, but in QA now the content display just plain text.  Do you resolve your problem?  If so, how do you do that? 

Your help is very appreciated.

Lillian