C 2 concepts in load balancing:
Scenario 1:
You can start a system with many Java dispatchers, for which the SAP Web Dispatcher or a different load balancer is already activated as a Web switch.
Scenario 2:
In the Java Instance the Java Dispatcher distributes the inbound requests to the server processes to which it is connected. The Java dispatcher runs the load balancing when the first session request arrives. The dispatcher ensures that subsequent requests get to the server process that is processing this session.
Now consider a scenario where the CI or the central instance and the dialog instance are in different Operating systems, the portal needs some work and I think this is a very rare scenario where not many clients would adopt this system landscape.
lets consider the possible issues faced on the Portal in this heterogeneous system landscape and provide solutions.
Problems and solutions:
The KM iViews are severely affected and the solution is mentioned below :
Make sure the settings for the cluster environment is not deselected. System Administration > System Configuration > Knowledge Management > Content Management > Global Services > system landscape services.
the secret is here...
· In the portal, choose System Administration ® System Configuration ® Knowledge Management ® Content Management ® Repository Managers ® File System Repository.
· Open the etc entry, and then choose Edit.
· In the Root Directory parameter, enter the following value:
· $(sys.global.dir)/config/cm/etc
· Save your changes by choosing OK.
· To check the changes, open the configuration of the /etc file system repository again. The new operating system-specific path is displayed below the Root Directory parameter.
Restart the portal.
Posts
