My name is Oren Root and I’m the project lead for FPN.
In my blog I’ll try to set up a channel between development here in the labs and the outside world.
Enough with the introductions, let’s move on to some real material. One of the things FPN does is integrate remote content seamlessly into your consumer portal.An issue that keeps poping up is the environment handling in FPN. How is the locale of the remote content determined?
Well, to answer this, lets first look at the way the locale is determined in a local portal application’s runtime.
Using the ForcedRequestLanguage property, an iView can override the settings and declare its own locale. If this is not defined then the locale is taken from UME. If no locale was personalized then the locale is taken from the browser.
The locale determined is sent to the producer when we ask to render remote content.
Ok, so we understand what locale is sent to the producer, this is good. Is this now the locale we’ll see rendered in our remote application? Not necessarily. You see, if the remote application is what we call a SAP Application, integrated using the application integrator such as BW reports, WebDynpro (Java and ABAP) the runtime rendering the content knows how to accept the locale parameter (sap-locale).
The Portal Runtime on the other hand ignores this parameter and calculates the locale according to the explanation above. This affects KM content for example.
In my next post I’ll discuss theme integration in FPN. So stay connected.