Optimizing Your Consumer ProfileApplicable to: remote role assignment
You can reduce the number of runtime round-trips between consumer and producer by optimizing a dedicated service on the consumer portal; thereby improving overall performance. These settings are valid for content shared through remote role assignment mode only.
When configured, the content in a remote role is cached on the consumer’s server (not the client) when the first user on the consumer retrieves iView data from the respective producer at runtime. You also specify which languages are cached. For every subsequent user, the data for the role will already be cached on the consumer saving.

■ The settings described are global settings. You cannot define a different configuration for each producer you work with.
■ The validity of the cached content described here is determined by the settings you define in the FederatedPortalCacheservice. For more information, see Configuring Caching for the Federated Portal.
You have access to the SAP NetWeaver Administrator tool.
...
1. In the SAP NetWeaver Administrator tool, access the following portal application and service:
○ Portal application: com.sap.portal.ivs.global.jndibridge
○ Service: OptimizerC
For
information about accessing and configuring portal services in the
SAP NetWeaver Administrator tool, see
Accessing Portal
Services in SAP NetWeaver Administrator.
2. Configure the following properties:
Parameter |
Description |
Languages to retrieve by optimization |
Specify the languages to cache on the first round-trip. Apply the following guidelines: ● For each locale, enter the corresponding constants as defined in the Java Locale object in the java.util library. You may need the assistance of a portal developer to obtain this information. ● For each locale, you may enter a language only or a language and its country. ● Separate multiple entries with a semi-colon (;). ● Do not include spaces. For example: en;enUS;de;frFR |
My Portal Address |
Specify the full URL of your portal in the format: <protocol>:<full domain host name>:<port> For example: http://myportal.mydomain:53000 |
3. Save your changes.