Skip to Content
avatar image
Former Member

Regenerating of PortalApps iviews in clustered environment

Recently we were asked to rebrand an SAP Portal application.

Rather than go to the trouble of redeploying all the iviews with new graphics, we decided to simply to replace the contents of the images in the deplotyed iview folders on the portal. ie. leave the graphic names the same, but replace the content.

For example, we found the images that were applicable to branding in the iview folder


so we updated those (leaving the name the same)

This worked fine in our dev an qa environments which are non-clustered, however after applying the changes to production we found that after a few days the changes were reverted back to the original. What's more, all the iview folders had been recreated! (we could tell because all the "last modified" dates were set to today's date.

NOTE: in production, we replaced the graphics on BOTH nodes of the 2 node cluster (server0 and server1)



  • \\toresportq3\r$\usr\sap\QP2\JC00\j2ee\cluster\server1\apps\\irj\servlet_jsp\irj\root\portalapps\demo_ca_apotex_clozapine_patient_graph_max\images

A couple of days later, the images in Server0 had been replaced with the old ones .... the ones in Server1 were untouched.

I am not an SAP experts but I am guessing that there is some mechanism within the SAP Portal that regenerates the iview folders in "portalapps" on-demand when it is in a cluster. Surely it doesn't re-deploy the packages though??

Hopefully someone an explain what is going on here and if there is a way to avoid this intermittent replacement of the iviews.

As a final note, we stop the portal application service every night around midnight. It would appear that the replacement occurs intermittently when we start the service up in the morning.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers