To prevent synchronization issues in multi-server systems, you can define that all
requests from the SAP Fiori launchpad designer are sent to the same application server.
Context
In the SAP Fiori launchpad designer, some data is stored in the application memory
specific to the application server. The synchronization of this data using the
various application servers may require up to 60 seconds. An error occurs if data is
written on one server and read on a different server before the synchronization is
complete. In that case, the system displays incorrect data after you change catalogs
or groups. As a result, for example, the title of a catalog that was created
previously is missing after you restart the launchpad designer.
To prevent this
issue, you can specify a logon group for HTTP load balancing to define that all requests
from the SAP Fiori launchpad designer are sent to the same application server.
Procedure
-
Use transaction SMLG (CCMS: Maintain Logon Groups) to configure a
logon group that is assigned to only one application server.
-
Define load balancing for services.
-
Call transaction SICF (Maintain Services).
-
Navigate to the service path
/sap/opu/odata/ui2/page_builder_cust
and switch to change mode.
-
On the Service Data tab, mark the Do
Not Include Inherited Settings checkbox.
-
In the Load Balancing field, enter the logon
group you configured in step 1.
-
Save your changes.
-
Perform the last 4 steps for the service
/sap/opu/odata/ui2/page_builder_conf.
For more information on the ICF configuration, go to
http://help.sap.com/ and search for
HTTP Load Distribution.
-
Implement SAP Note 1711354 .
Results
All requests from the SAP Fiori launchpad designer are sent to the same application server
and the synchronization problems no longer occur. For the SAP Fiori launchpad, however,
the system still takes all load balancing settings into account as before. In this case,
it uses the service
/sap/opu/odata/ui2/page_builder_pers.